Re: Harddrive(s) not properly recognized

[Eric L. <ela...@te...>]

Sorry about the repeated message... I believe that I posted to the incorrect list...

I am working with Magnus La on the issue that he reported a while back:
We are still trying to get this to work...
http://sourceforge.net/p/linux1394/mailman/message/33270726/

I am using the same hardware (nitrogen6x, with a Freescale iMX6q processor) and the same PCI card (which works flawlessly on my desktop running Fedora 19)
for the nitrogen6x board, we are using the following kernel sources:
git://github.com/boundarydevices/linux-imx6.git
branch: boundary-imx_3.10.17_1.0.2_ga
revision/commit: fdf3d06333f2c4ae8aa8bac9bca2e5c15041f22e

As far as I can tell, the firewire driver appears to be unmodified from the mainline 3.10.17 sources.

From there, I added a few printk statements to help see what was going on... the patch is here:
http://pastebin.com/Ney1WfiQ

on bootup (or if I remove and reinstall the firewire_ohci module) I get the following:

root@nitrogen6x<mailto:root@nitrogen6x>:~# dmesg | grep -e firewire -e sbp2 -e scsi -e pcie
imx6q-pcie 1ffc000.pcie: Link up, Gen=1
imx6q-pcie 1ffc000.pcie: PCI host bridge to bus 0000:00
scsi0 : ahci_platform
firewire_ohci 0000:02:00.0: added OHCI v1.10 device as card 0, 8 IR + 8 IT contexts, quirks 0x2
firewire_core 0000:02:00.0: created device fw0: GUID 0001b713000039db, S800
firewire_core 0000:02:00.0: created device fw1: GUID 0014520300501763, S800
firewire_core 0000:02:00.0: phy config: new root=ffc0, gap_count=5
scsi1 : SBP-2 IEEE-1394
firewire_sbp2 fw1.0: logged in to LUN 0000 (0 retries)
sbp2_login: command_block_agent_address is 281470681743360, generation is 2
sbp2_set_busy_timeout returned rcode 0x0 (no error)
sbp2_agent_reset: command_block_agent_address is 281470681743360, generation is 2
sbp2_agent_reset returned rcode 0x7 (address error)
scsi_probe_and_add_lun: scsi_device_lookup_by_target(0xD268AC00, 0x0) returned sdev of 0x0
sbp2-complete_transaction: complete_transaction() sending NULL status due to rcode != RCODE_COMPLETE
sbp2-complete_command_orb: Setting DID_BUS_BUSY due to status == NULL
sbp2-complete_transaction: complete_transaction() sending NULL status due to rcode != RCODE_COMPLETE
sbp2-complete_command_orb: Setting DID_BUS_BUSY due to status == NULL
sbp2-complete_transaction: complete_transaction() sending NULL status due to rcode != RCODE_COMPLETE
sbp2-complete_command_orb: Setting DID_BUS_BUSY due to status == NULL
sbp2-complete_transaction: complete_transaction() sending NULL status due to rcode != RCODE_COMPLETE
sbp2-complete_command_orb: Setting DID_BUS_BUSY due to status == NULL
scsi_probe_and_add_lun: scsi_probe_lun returned non 0!
__scsi_add_device: scsi_probe_add_lun returned 0(0x0): sdev = -19 (0xFFFFFFED)
sbp2_login: scsi sdev = -19(0xFFFFFFED)
sbp2_login: IS_ERR(sdev) is true... attempt logout_login
sbp2_login: out_logout_login: sending SBP2_LOGOUT_REQUEST.
sbp2_login: out_logout_login: rescheduling login.

after this there are no more messages...

If I remove the firewire_sbp2 and firewire_ohci modules and re-install the firewire_ohci using "modprobe firewire_ohci debug=8", I get the following:
root@nitrogen6x<mailto:root@tads_nitrogen6x>:~# modprobe firewire_ohci debug=8
firewire_ohci 0000:02:00.0: added OHCI v1.10 device as card 0, 8 IR + 8 IT contexts, quirks 0x2

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<mailto: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
...
the last line repeats very rapidly until the kernel eventually crashes (using a serial port, my guess is that this message is overflowing the output).
Either way, once I start with debug=8 I cannot do anything else.

it looks to me like the bus resets are not allowing the sbp2_login function to complete (in fact the rescheduled login never happens).
I have also tried this using a Lacie portable firewire hard drive with the exact same results.

I am stuck at this point... any help or pointers would be greatly appreciated.

Eric