Re: Harddrive(s) not properly recognized
Brought to you by:
aeb,
bencollins
From: Stefan R. <st...@s5...> - 2015-01-24 21:18:32
|
On Jan 23 Magnus La wrote: > The system itself is a ARM board running the Dizzy release of Yocto linux. I suppose you discovered a bug of the 1394 + scsi stack of drivers in conjunction with that ARM platform. > The PCI-e firewire controller seems to be this card (PCI-E, firewire 800, TI chipset): http://www.syba.com/index.php?controller=Product&action=Info&Id=995 > > Linux nitrogen6x 3.10.17-1.0.2_ga+yocto+g0d7db21 #1 SMP Tue Dec 9 15:15:03 CET 2014 armv7l GNU/Linux > > # lspci > 00:00.0 PCI bridge: Device 16c3:abcd (rev 01) > 01:00.0 PCI bridge: Texas Instruments XIO2213A/B/XIO2221 PCI Express to PCI Bridge [Cheetah Express] (rev 01) > 02:00.0 FireWire (IEEE 1394): Texas Instruments XIO2213A/B/XIO2221 IEEE-1394b OHCI Controller [Cheetah Express] (rev 01) XIO2213A/B are generally rather good for SBP-2 I/O. > # lspci -vv | grep firewire > Kernel driver in use: firewire_ohci > > When a firewire drive (I've tried several with the same results) is connected the following information is logged: > firewire_core 0000:02:00.0: rediscovered device fw0 > firewire_core 0000:02:00.0: phy config: new root=ffc1, gap_count=5 > firewire_core 0000:02:00.0: phy config: new root=ffc1, gap_count=5 > scsi1 : SBP-2 IEEE-1394 > firewire_core 0000:02:00.0: created device fw1: GUID 0030e0f5e0100a94, S400 > firewire_sbp2 fw1.0: logged in to LUN 0000 (0 retries) > > (I tried the same but when enabling debug output via "echo -1 > /sys/module/firewire_ohci/parameters/debug", the log is a bit verbose so I posted it here: http://pastebin.com/skm6ZBYw) [...] The stock kernel log shows that Self-ID reception DMA, request transmit DMA, response reception DMA (which are needed to get the disk probed by firewire-core), physical response DMA, and request reception DMA (which together with the former DMAs are need for firewire-sbp2 to perform SBP-2 transactions work as they are intended to work. The verbose kernel log additionally shows a few more SBP-2 transactions happening after the log in management transaction succeeded. Those subsequent transactions should be ones issued by scsi core, notably SCSI Inquiry, and then read requests to discover the medium size and the contents of the partition table (if present). However, I wonder why there is no message from the SCSI subsystem, not even anything about failed SCSI requests. Did you filter the log through grep or something like that? If so, please provide a full log with messages from any and all kernel subsystems, even if they seem totally unrelated. Best would be a kernel log beginning from actual boot. Don't remove anything, except lines which you can't expose for privacy reasons. -- Stefan Richter -=====-===== ---= ==--- http://arcgraph.de/sr/ |