2.6.35-rc6 to 2.6.32.16: JuJu firewire issues
in [Kernel]
|
Prev: hw-breakpoints, kgdb, x86: add a flag to passDIE_DEBUG notification
Next: x86/pci Oops with CONFIG_SND_HDA_INTEL
From: Stefan Richter on 23 Jul 2010 18:00 Stefan Richter wrote: > Your dmesg shows multiple bus resets and one of the three nodes > disappearing from the bus from time to time. This points to a probelm > at the physical layer (i.e. highly unreliable hardware) which > fundamentally cannot be solved by software. PS: If you want, you can for example run the small utility "firecontrol" (requires libraw1394) in a console while you have the FireWire disk attached. Firecontrol will show all bus resets that happen as well as how many nodes are present on the bus after each reset. During usage of a FireWire disk, there should be only about two or so bus resets early on when the disk is plugged in, but then not anymore. The drivers do handle subsequent bus resets (firewire-sbp2 + firewire-core much better than sbp2 + ieee1394, obviously) but they cannot do much if very frequent bus resets happen and the target node even disappears from the bus due to electrical problems or whatever reasons. According to your dmesg, I expect firecontrol to show series of resets, some of them with a node going away and coming back. The most likely cause for that is buggy or defective hardware. -- Stefan Richter -=====-==-=- -=== =-=== http://arcgraph.de/sr/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Stefan Richter on 24 Jul 2010 04:10 Stefan Richter wrote: > Martin Mokrejs wrote at LKML: >> Hi Jay, >> Jay Fenlason wrote: >>> On Fri, Jul 23, 2010 at 04:09:21PM +0200, Martin Mokrejs wrote: >>>> Hi, >>>> I bought a external harddrive with firewire and USB interfaces (IcyBOX IB-250StUE-B). >>>> If I connect it to a desktop computer A I get kernel crash during boot (see >>>> both attached dmesg-*.txt files). > > The crash which you reported is in sbp2 (of the old ieee1394 stack alias > linux1394, not in firewire-sbp2 (of the new firewire stack alias juju). I have logged your report as https://bugzilla.kernel.org/show_bug.cgi?id=16452 nodemgr, sbp2: NULL pointer dereference in sbp2_update but set its status to WILL_NOT_FIX for now. The bug seems to be in the nodemgr component of the ieee1394 core driver. This is one of the things that were rewritten from scratch in firewire-core with a fundamentally different implementation, for good reasons. Perhaps somebody else wants to look into a possible fix for this bug, but this seems very unlikely. (Basically, a bug fix already exists in the form of firewire-core.) -- Stefan Richter -=====-==-=- -=== ==--- http://arcgraph.de/sr/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Martin Mokrejs on 24 Jul 2010 08:10 Hi Stefan, thank you for your care of this issue. I have just returned the crappy IcyBOX IB-250StUE-B back to the reseller. On the circuit board there was Apr 2008 timestamp (regarding the JMicron JMB 353 chip doing the SATA to FireWire 1394a + USB 2.0 conversion). I tried in the morning to connect the IcyBox to this laptops internal Ricoh Co Ltd R5C552 IEEE 1394 Controller but had issues to power-up the drive at all. Not even using USB hub to supply power to it. I connected it to the ricoh chip via a 6 to 4 pin cable but also tried the not very good Kouwell 7004 PCMCIA card (which does not supply enough power unless I buy external, optional power supply of unknown specs and plug it into the PCMCIA card). Many thanks for your care, Martin P.S.: Yes, laptop (computer B) is a single-core, old P4-M computer with ICH3 chipset. Stefan Richter wrote: > Stefan Richter wrote: >> Martin Mokrejs wrote at LKML: >>> Hi Jay, >>> Jay Fenlason wrote: >>>> On Fri, Jul 23, 2010 at 04:09:21PM +0200, Martin Mokrejs wrote: >>>>> Hi, >>>>> I bought a external harddrive with firewire and USB interfaces (IcyBOX IB-250StUE-B). >>>>> If I connect it to a desktop computer A I get kernel crash during boot (see >>>>> both attached dmesg-*.txt files). >> >> The crash which you reported is in sbp2 (of the old ieee1394 stack alias >> linux1394, not in firewire-sbp2 (of the new firewire stack alias juju). > > I have logged your report as > https://bugzilla.kernel.org/show_bug.cgi?id=16452 > nodemgr, sbp2: NULL pointer dereference in sbp2_update > but set its status to WILL_NOT_FIX for now. > > The bug seems to be in the nodemgr component of the ieee1394 core > driver. This is one of the things that were rewritten from scratch in > firewire-core with a fundamentally different implementation, for good > reasons. > > Perhaps somebody else wants to look into a possible fix for this bug, > but this seems very unlikely. (Basically, a bug fix already exists in > the form of firewire-core.) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Stefan Richter on 24 Jul 2010 08:20
Martin Mokrejs wrote: > I tried in the morning to connect the IcyBox to this laptops internal > Ricoh Co Ltd R5C552 IEEE 1394 Controller but had issues to power-up the drive > at all. Not even using USB hub to supply power to it. I connected it to > the ricoh chip via a 6 to 4 pin cable but also tried the not very good > Kouwell 7004 PCMCIA card (which does not supply enough power unless I > buy external, optional power supply of unknown specs and plug it into the > PCMCIA card). FireWire CardBus cards do not (or more precisely, must not) provide bus power at all, unless if they have a power input port and a fitting PSU is connected to it. If a CardBus card puts power onto the FireWire bus without any extra PSU connected, then this card is miswired and not spec compliant. A FireWire bus power provider is required to be able to deliver 1.5 A current or more, at 8 V or more. That can't be done via CardBus. 4-pin FireWire ports OTOH do not provide bus power of course; they lack the respective pins. Some FireWire disk enclosures can optionally be powered via USB, but we all know how unreliable USB bus power is. Prefer either a dedicated PSU or regular FireWire bus power. -- Stefan Richter -=====-==-=- -=== ==--- http://arcgraph.de/sr/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |