Seeing sysrq-t stack traces might help debugging. On Sat, Jul 23, 2005 at 09:58:18PM +0200, Stefan Richter wrote: > I wrote: > >Problem 1) Hot unplugging of SBP-2 hangs ieee1394's nodemgr > [...] > >[unplug disk] > >Jul 23 20:08:53 shuttle kernel: ieee1394: Node changed: 1-01:1023 -> > >1-00:1023 > >Jul 23 20:08:53 shuttle kernel: ieee1394: Node suspended: > >ID:BUS[1-00:1023] GUID[0001d202e0200ef1] > >Jul 23 20:08:53 shuttle kernel: ieee1394: sbp2: sbp2_remove > >Jul 23 20:08:53 shuttle kernel: Synchronizing SCSI cache for disk sda: > > I should provide perhaps a little more background about nodemgr. It waits > for > events on the FireWire bus. If it detects physical removal of a node, it > calls > remove callbacks from IEEE 1394 protocol drivers such as sbp2. That's where > sbp2_remove() kicks in. So it all happens in nodemgr's process context, > although > the hang occurs somewhere in the scsi mid or high level, or perhaps in the > driver > core when it is called from scsi. - : 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
