https://bugzilla.novell.com/show_bug.cgi?id=682779
https://bugzilla.novell.com/show_bug.cgi?id=682779#c6
--- Comment #6 from Stefan Richter 2011-06-29 19:35:42 UTC ---
Tail of the mailinglist discussion:
http://thread.gmane.org/gmane.linux.kernel.firewire.devel/14905/focus=14906
There is no indication for a transport layer problem in the logs. So far it
looks like the firmware of the device becomes unresponsive at some point. This
(always?) coincides with a segfault of packagekitd.
Thorsten noted that while this happens with OpenSuse 11.4, it does not happen
with SuSE 11.0 on the very same hardware.
Is there some nosy userland poking at the hardware with a request that lets the
firmware die?
I don't have OpenSuse myself, hence don't know what daemons and helpers run and
how to shut them down for testing. Nor have I any idea how to get the kernel's
block or SCSI layer to switch on some per-device logging in order to find out
which processes accessed the device at the moment of failure.
(Note, dual FireWire + USB to IDE or SATA bridges run entirely separate
firmwares in their FireWire and USB parts. Hence, these two firmwares don't
share their bugs. On the other hand, lowlevel Linux userland might be buggy in
the regard that it can tell USB devices apart from other SCSI devices and is
cautious with USB devices but aggressive with others, issuing requests to the
latter that never arrive in that form or order on a stock MS Windows machine.)
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
