Hi! > >>>I just switched to libata (pata) on my laptop and the > >>>immediate panic made it impossible to figure out why > >>>my boot partition wasn't available. > >>>After applying this little patch I could check boot > >>>printk output and then saw everything was properly > >>>recognized and only scsi-disk support was missing. > >>The correct fix would be to make scroll back (and > >>sysrq) still work > >>after panic. It's a little more complicated, but > >>possible (essentially > >>it needs a polled keyboard handler) > > > >Customer: "This system could not find the root fs." > >Support: "Oh, yeah, just connect a (USB-) keyboard and > >scroll back." > > > >Hmm, device detection works after panic? > > > >I really like the "soft" panic better, where you still > >can operate the kernel debugging features, but just > >have no user space supporting it.
ACK. 'scheduling in interrupt' is very different from 'cant mount root'. > Of course, if we'd been using kinit, "soft panic" would > have been done exclusively in userspace... What's the status of kinit, btw? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/