On Fri, Feb 12, 2010 at 08:28:24PM +0000, bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote: > --- Comment #3 from Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> 2010-02-12 20:28:19 --- > I'll reassign this regression to scsi. > > I reattached the most interesting jpg screenshot: scsi_async_scan got stuck. This probably isn't anything to do with the scsi async scan (boot with scsi_mod.scan=sync to eliminate the possibility). It's probably a driver failing to finish the scan. Probably the reason for that is broken interrupt routing. But that's a lot of probables, so some investigation with scsi_mod.scan=sync should be used to confirm the first hypothesis before assigning the blame elsewhere. -- Matthew Wilcox Intel Open Source Technology Centre "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step." -- To unsubscribe from this list: 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
