I wrote on 2005-10-12:
Mark Knecht wrote to linux1394-user:
scsi4 : SCSI emulation for IEEE-1394 SBP-2 Devices
ieee1394: sbp2: Error logging into SBP-2 device - login timed-out
prev->state: 2 != TASK_RUNNING??
scsi_eh_4/7835[CPU#0]: BUG in __schedule at kernel/sched.c:3326
Call Trace:<ffffffff80132221>{__WARN_ON+97}
<ffffffff803e79f0>{__schedule+608}
<ffffffff801342bf>{do_exit+1007}
<ffffffff801467c0>{keventd_create_kthread+0}
<ffffffff8010e5ed>{child_rip+15}
<ffffffff801467c0>{keventd_create_kthread+0}
<ffffffff801466b0>{kthread+0} <ffffffff8010e5de>{child_rip+0}
sbp2: probe of 0050c504e0006463-0 failed with error -16
In other words, a spinlock is held (in sbp2 or in the scsi core?) while
the eh is fired up (or teared down?). As mentioned, this is
2.6.14-rc4-rt1 but I consider it possible to occur in unpatched
2.6.14-rcX too. I will investigate further but it may take me a while.
--
Stefan Richter
-=====-=-=-= =-=- =--==
http://arcgraph.de/sr/
-
: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
