From: Ingo Oeser <ioe-lkml@rameria.de>
To: Andi Kleen <andi@firstfloor.org>
Subject: Re: sleep before boot panic
Date: Tue, 8 Jan 2008 07:17:03 +0100
User-Agent: KMail/1.9.6 (enterprise 0.20070907.709405)
Cc: Bernd Schubert <bernd-schubert@gmx.de>, linux-kernel@vger.kernel.org
References: <200801061908.43010.bernd-schubert@gmx.de> <p731w8ts70k.fsf@bingen.suse.de>
In-Reply-To: <p731w8ts70k.fsf@bingen.suse.de>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200801080717.03467.ioe-lkml@rameria.de>
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1325
Lines: 33

On Monday 07 January 2008, Andi Kleen wrote:
> Bernd Schubert <bernd-schubert@gmx.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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/