Bug 2015 - Kernel halt (desktop freeze) during access to parallel port printer on AMD SB785 mainboard
Summary: Kernel halt (desktop freeze) during access to parallel port printer on AMD SB...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard: MGA1TOO
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-03 20:47 CEST by Jürgen PreuÃ
Modified: 2013-11-23 16:16 CET (History)
3 users (show)

See Also:
Source RPM: kernel 3.3.6-2.mga2.src.rpm
CVE:
Status comment:


Attachments

Description Jürgen Preuà 2011-07-03 20:47:06 CEST
Description of problem:

Not able to print on Asrock 785G/SB710 (939A785GMH/128M) mainboard on parallel port to Epson Stylus Color 850 printer.

Printing from MS Windows7/64Bit with same hardware combination is ok.

Printing from Mandriva 2010.2 (i586/x64) also with cooker kernels and normal udev/cups packages not possible (same symptoms).

In Detail:

Printer will be detected if powered on during Boot/Reboot.

/var/log/messages:
...
Jul  3 18:56:27 Max kernel: parport_pc 00:0a: reported by Plug and Play ACPI
Jul  3 18:56:27 Max kernel: parport0: PC-style at 0x378 (0x778), irq 7, dma 1 [PCSPP,TRISTATE,COMPAT,ECP,DMA]
...
Jul  3 18:56:27 Max kernel: ppdev: user-space parallel port driver
Jul  3 18:56:27 Max kernel: parport0: Printer, EPSON Stylus COLOR 850
...

lspci:
00:00.0 Host bridge: Advanced Micro Devices [AMD] RS880 Host Bridge
00:01.0 PCI bridge: ASRock Incorporation Device 9602
00:0a.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 5)
00:11.0 SATA controller: ATI Technologies Inc SB700/SB800 SATA Controller [AHCI mode]
00:12.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller
00:12.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller
00:12.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
00:13.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller
00:13.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller
00:13.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 3c)
00:14.1 IDE interface: ATI Technologies Inc SB700/SB800 IDE Controller
00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA)
00:14.3 ISA bridge: ATI Technologies Inc SB700/SB800 LPC host controller
00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge
00:14.5 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI2 Controller
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:05.0 VGA compatible controller: ATI Technologies Inc RS880 [Radeon HD 4200]
01:05.1 Audio device: ATI Technologies Inc RS880 Audio Device [Radeon HD 4200]
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)

lsusb:
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 03f0:2003 Hewlett-Packard 
Bus 001 Device 004: ID 0fe6:811e Kontron (Industrial Computer Source / ICS Advent) 
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

To recognize printer device during boot there must happen an minimum of signaling and handshake. After full initialization of user mode (init 5) any write action is blocking/stopping kernel.

I've tested parallel printing also from laptops (Intel Chipsets) to same printer from Mandriva 2010.2 (i586). It's properly working (beside wizards not knowing URI "parallel:" or "serial:"). That's why I believe in errors specific to chipset or BIOS/ACPI implementation.
Beside the problem in parallel printing I've also detected malfunction of serial port. Serial mouse from Logitech (Marble Mouse) won't work with Mageia/Mandriva, but with Win7. Both devices are using legacy interfaces, possibly errors are also connected/shared. If necessary, I can file another bug report.

Version-Release number of selected component (if applicable):

   ASROCK Bios Version 1.00 from 30/9/2009 (no newer available)

How reproducible:
Very. Each time of trying.

Steps to Reproduce:
1. Power on printer.
2. Boot up system.
3. Try to print anything (i.e. "cat /etc/passwd > /dev/lp0" or print testpage from printer installation wizard)
4. Immediate freezing of system (including mouse cursor).

Thanks in advance,

Jürgen
Comment 1 Manuel Hiebel 2011-10-04 18:41:47 CEST
Thomas, if you have an idea.

(Sorry it was probably a missing one bug :/ )

CC: (none) => tmb
Source RPM: kernel-source-2.6.38.7-1.mga => kernel-source

Comment 2 Marja Van Waes 2011-12-05 08:22:45 CET
@ Jürgen

ouch, sorry, we are very short on triagers and miss things :(

And now it's five months later, and the problem may have gotten solved through an update, anyway.

Did it get solved?

In case the bug is still there, I'll put our printing magician in the cc of this report.

CC: (none) => doktor5000, marja11

Comment 3 Marja Van Waes 2012-01-26 18:36:32 CET
Reporter, could you please reply to the previous question? If you won't reply within two weeks from now, I will have to close this bug as OLD. Thank you.

Keywords: (none) => NEEDINFO

Comment 4 Jürgen Preuà 2012-02-07 18:03:46 CET
(In reply to comment #3)
> Reporter, could you please reply to the previous question? If you won't reply
> within two weeks from now, I will have to close this bug as OLD. Thank you.

Here I am.

Sorry for long delay. Errors are not resolved and continue.

Last tested with kernels 2.6.38.8-desktop-10.mga and 3.1.6-desktop-nrj.69mib. Entire distribution is actually patched.

Thank you for your efforts.

with regards,

Juergen.
Comment 5 Florian Hubold 2012-02-07 23:00:44 CET
(In reply to comment #4)
> and 3.1.6-desktop-nrj.69mib.
> Entire distribution is actually patched.

What do you mean by that? Also you can't expect us to do some support for a 3rd party kernel, or why do you mention an MIB kernel here? If you installed many 3rd party packages, then please complain to the 3rd party packages for bugfixes, we can only support official mageia packages.
Comment 6 Jürgen Preuà 2012-02-09 12:57:43 CET
(In reply to comment #5)
> (In reply to comment #4)
> > and 3.1.6-desktop-nrj.69mib.
> > Entire distribution is actually patched.
> 
> What do you mean by that? Also you can't expect us to do some support for a 3rd
> party kernel, or why do you mention an MIB kernel here? If you installed many
> 3rd party packages, then please complain to the 3rd party packages for
> bugfixes, we can only support official mageia packages.

Hallo Florian,

sorry for your inconvenience.

I wanted to say, that I'm regularly/daily check for patches and deploy them. 
Because I'm an long time consumer of Mandriva, I also tried to resolve my 
printing and mousing problems with actual kernels borrowed by siblings of MIB. 
But MIB kernels inserted in Mageia1 and a separate complete installation of 
MDV 2011 on this mainboard are showing the same blocking behavior in case of 
output to parallel device. For completeness of information I'll send you the 
list of installed MIB packages. You shouldn't fix them.

[root@Max ~]# rpm -qa|grep mib
kernel-nrj-desktop-devel-latest-3.1.6-nrj.69mib2010.2
dkms-fglrx-8.881-69.1mib2010.2
fglrx-control-center-8.881-69.1mib2010.2
kernel-nrj-desktop-devel-3.1.6-nrj.69mib-1-1mib2010.2
kernel-firmware-20110314-69mib2010.2
x11-driver-video-fglrx-8.881-69.1mib2010.2
kernel-firmware-extra-20110517-69mib2010.2
kernel-nrj-desktop-3.1.6-nrj.69mib-1-1mib2010.2
kernel-nrj-desktop-latest-3.1.6-nrj.69mib2010.2

If there is anything to do for Your support, I'm glad to hear of it.

Thanks,

Juergen
Comment 7 Marja Van Waes 2012-02-24 23:24:29 CET
@ tmb

assigning to you. The last Mageia kernel the reporter tried with is the actual one in Mageia 1

Keywords: NEEDINFO => (none)
Assignee: bugsquad => tmb
Source RPM: kernel-source => kernel-2.6.38.8-10.mga1.src.rpm

Comment 8 Marja Van Waes 2012-06-06 22:13:42 CEST
3-monthly ping

@ Jürgen

If this bug is still valid, is it valid for Mageia 2, too?
Comment 9 Jürgen Preuà 2012-06-11 23:28:37 CEST
Hi Marja,

thank you for remembering this open tasks.

In this case, there are actually no good news. Again testet with MGA2 (release kernel 3.3.6-2, all updates applied). The system freezes immediately.

Tested on console with "cat /etc/hosts > /dev/lp0". The printer initialized (positioned paper) and stopped before printing first char.

Is there any advice to produce an dump or core file?

Good evening,

with regards, Jürgen
Comment 10 Marja Van Waes 2012-06-30 08:04:38 CEST
(In reply to comment #9)

> 
> In this case, there are actually no good news. Again testet with MGA2 (release
> kernel 3.3.6-2, all updates applied). The system freezes immediately.
> 
> Tested on console with "cat /etc/hosts > /dev/lp0". The printer initialized
> (positioned paper) and stopped before printing first char.
> 
> Is there any advice to produce an dump or core file?
> 

@ tmb

(or @ anybody else who knows)

Can you please answer that question?

Version: 1 => 2
Source RPM: kernel-2.6.38.8-10.mga1.src.rpm => kernel 3.3.6-2.mga2.src.rpm
Whiteboard: (none) => MGA1TOO

Comment 11 Marja Van Waes 2012-07-06 15:06:12 CEST
Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D
Comment 12 Manuel Hiebel 2013-10-22 12:20:56 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad
Comment 13 Manuel Hiebel 2013-11-23 16:16:27 CET
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.