Re: Harddrive(s) not properly recognized
Brought to you by:
aeb,
bencollins
From: Stefan R. <st...@s5...> - 2015-07-23 18:22:58
|
On Jul 22 Eric Lamphear wrote: > On Thu, 2015-06-25 at 20:10 -0500, Eric Lamphear wrote: [...] > > firewire_ohci 0000:02:00.0: IRQ 00030010 selfID AR_req busReset > > firewire_ohci 0000:02:00.0: IRQ 00020000 busReset > > firewire_ohci 0000:02:00.0: IRQ 00020000 busReset > > firewire_ohci 0000:02:00.0: IRQ 00020000 busReset > > root@tads_nitrogen6x:~# firewire_ohci 0000:02:00.0: IRQ 00020000 > > busReset > > firewire_ohci 0000:02:00.0: IRQ 00020000 busReset > > firewire_ohci 0000:02:00.0: IRQ 00020000 busReset > > firewire_ohci 0000:02:00.0: IRQ 00020000 busReset > > firewire_ohci 0000:02:00.0: IRQ 00020000 busReset > > firewire_ohci 0000:02:00.0: IRQ 00020000 busReset [...] > OK, not sure why this is being ignored, but I really do need help to get > this resolved? I am not familiar with Linux drivers or kernel > development, so I am afraid that I will make things worse if I start > hacking around looking for a fix (which I already have by adding the > printk statements in the patch mentioned above)... > if anyone is willing to help, I can, at the very least, provide the > hardware. Long series of bus reset events, more so ones without following selfIDcomplete events, mean that the bus is electrically unstable (i.e. too much noise on the bus). I.e. the hardware is defect. Another possible cause of many bus resets which prevent normal access to the bus would be the presence of several Texas Instruments TSB81BA3 phys which have a long list of errata (up to chip revision C inclusive). However, in my experience the TSB81BA3 errata cause bus resets with many selfIDcomplete events, unlike your log. Several of the TSB81BA3 errata can be worked around by adding a 1394a-only phy to the bus. -- Stefan Richter -=====-===== -=== =-=== http://arcgraph.de/sr/ |