From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx> Date: Fri, 16 Jan 2009 13:48:53 -0500 > On Fri, 2009-01-16 at 09:09 -0800, Andrew Morton wrote: > > Doing a panic() after we've already detected an error is plain nasty. > > Is there no way in which we can allow the kernel to continue? > > There's a long thread discussing this very point on linux-scsi. The > short version is "no, it's only used for debugging firmware and if > you've corrupted your firmware to this point you need the machine > halting". Long thread or not, taking out one's entire system because one device hits a fail state is always wrong. If I have other block devices which are working, all I want is for this specific controller and it's block devices to fail. This way I can get the failure log message and actually do something with that data without rebooting. Or I guess digital cameras and serial/net consoles are the only sanctioned way to record kernel failure log messages of this kind? Give me a break. :) -- 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
