[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux1394-user
Subject:    Re: sbp2: sbp2util_node_write_no_wait failed
From:       Stefan Richter <stefanr () s5r6 ! in-berlin ! de>
Date:       2005-11-06 17:40:41
Message-ID: 436E4019.7000709 () s5r6 ! in-berlin ! de
[Download RAW message or body]

Thorsten Holtkaemper wrote:
> exactly the same problem here with an ieee1394 harddisk. serialize_io made the 
> problem occure less but not go away. Also *not* to use the AS IO scheduler 
> helped a little bit (ATM I'm using deadline).
> 
> [...]
> kernel: ieee1394: sbp2: aborting sbp2 command
> kernel: scsi5 : destination target 0, lun 0
> kernel:         command: Test Unit Ready: 00 00 00 00 00 00
> kernel:  offline device
> kernel: scsi5 (0:0): rejecting I/O to offline device
> last message repeated 372 times

This is obviously after a lot of commands were aborted already. Did the 
message "sbp2: sbp2util_node_write_no_wait failed" appear too?

...
> In addition it usuallay needs several unload/load attemps of the firewire 
> modules (sbp2 eth1394 ohci1394 ieee1394) to make the kernel recognize the 
> harddisk at all.
> 
> I am running kernel 2.6.13.4
...
> Log for a _not_ successful login attemp:
> 
> [...]
> ieee1394: Error parsing configrom for node 0-01:1023
> ieee1394: The root node is not cycle master capable; selecting a new root node 
> and resetting...
> ieee1394: Error parsing configrom for node 0-00:1023
> ieee1394: Node changed: 0-00:1023 -> 0-01:1023
> ieee1394: Node added: ID:BUS[0-00:1023]  GUID[0050770e501e1452]
> ieee1394: unsolicited response packet received - no tlabel match
> sbp2: $Rev: 1306 $ Ben Collins <bcollins@debian.org>
> scsi2 : SCSI emulation for IEEE-1394 SBP-2 Devices
> ieee1394: sbp2: Error logging into SBP-2 device - login timed-out
> sbp2: probe of 0050770e501e1452-0 failed with error -16

You could try this patch which should apply to 2.6.13.x too:
http://me.in-berlin.de/~s5r6/linux1394/merged/available_in_2.6.14/ieee1394-reorder-activities-after-bus-reset-fixes-device-detection.patch


Although that patch is only meant to prevent _silent_ failures to 
recognize devices after "selecting a new root node and resetting", it 
may perhaps help a little bit to avoid "login timed-out" too.

BTW, the "unsolicited response packet received" is most probably caused 
by a bug of the FireWire harddisk (response to a broadcast write 
request, against the spec.), but it is harmless AFAICS.
-- 
Stefan Richter
-=====-=-=-= =-== --==-
http://arcgraph.de/sr/


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
mailing list Linux1394-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux1394-user


[prev in list] [next in list] [prev in thread] [next in thread]