Bug 6948
Summary: | Initio 2430 sbp2 controller not properly handled | ||
---|---|---|---|
Product: | Drivers | Reporter: | piergiorgio.sartor |
Component: | IEEE1394 | Assignee: | Stefan Richter (stefanr) |
Status: | CLOSED CODE_FIX | ||
Severity: | normal | ||
Priority: | P2 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | 2.6.17.7 | Subsystem: | |
Regression: | --- | Bisected commit-id: | |
Attachments: |
[RFT PATCH 2.6.17.x] ieee1394: sbp2: handle "sbp2util_node_write_no_wait failed"
[PATCH 2.6.18-rc4-mm1 2/8] ieee1394: sbp2: handle "sbp2util_node_write_no_wait failed" |
Description
piergiorgio.sartor
2006-08-02 12:34:24 UTC
This is a known problem in sbp2. Whenever "sbp2util_node_write_no_wait failed" appears in the log, it means most certainly thet sbp2 was unable to acquire a free transaction label. I plan to rework sbp2's routine which emits that message to be able to sleep until a transaction label becomes available. This will take some time but I'm on it. Until then you could try if a different filesystem makes this condition less likely. http://sourceforge.net/mailarchive/forum.php?thread_id=25299507&forum_id=5389 The "missing header in MODE_SENSE response" business is just a sign of firmware flaws of the Initio bridge. I have a INIC-2430 based disk too which has the same flaw. Linux SCSI core was hardened to work around that, so it's no problem anymore. And it's unrelated to the "sbp2util_node_write_no_wait failed" bug. Side note. As reported in http://bugzilla.kernel.org/show_bug.cgi?id=6947#c13 an INIC-1530 is affected too, and comment #1 refers to an OXFW922 bridge. My plan as stated in the mailarchive may take more time, therefore I will try to come up with a simpler temporary solution that is quicker to implement and can be merged sooner. Created attachment 8766 [details]
[RFT PATCH 2.6.17.x] ieee1394: sbp2: handle "sbp2util_node_write_no_wait failed"
Created attachment 8787 [details]
[PATCH 2.6.18-rc4-mm1 2/8] ieee1394: sbp2: handle "sbp2util_node_write_no_wait failed"
This improved update has been posted to lkml. I will try to get it together
with patches which it directly depends on into Linux 2.6.18(-rcX).
fix went into Linux 2.6.18-git16 |