| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <200801080717.03467.ioe-lkml@rameria.de> Date: Tue, 8 Jan 2008 07:17:03 +0100 From: Ingo Oeser <ioe-lkml@...eria.de> To: Andi Kleen <andi@...stfloor.org> Cc: Bernd Schubert <bernd-schubert@....de>, linux-kernel@...r.kernel.org Subject: Re: sleep before boot panic On Monday 07 January 2008, Andi Kleen wrote: > Bernd Schubert <bernd-schubert@....de> writes: > > > 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. One better hopes, that keyboards never need external firmware to be loaded at this stage :-) Best Regards Ingo Oeser, who just hit the same problem yesterday... -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists