On Fri, May 12, 2006 at 04:25:04AM -0700, Andrew Morton wrote: > Matthew Wilcox <matthew@xxxxxx> wrote: > > > scsi0 : sym-2.2.3 > > > 0:0:0:0: ABORT operation started. > > > 0:0:1:0: ABORT operation started. > > > 0:0:2:0: ABORT operation started. > > > > > > ad infinitum. How come? > > > > Are you sure it's ad infinitum or just once for every device? > > I have a single card talking to a single disk. I whacked it after a couple > of minutes. Sure, but it has to probe each device to find out it's not there. See the target number increasing in the snippet I left above? > > Anyway, this looks like a fairly classic "sym2 isn't getting any > > interrupts" scenario. > > It is - Len found that one. Cool. I'd love sym2 to behave more sanely in the 'no interrupts' case because it means I get a lot of bug reports directed my way from people with bad setups. I don't see a nice way to do it though ... - : 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
