Re: Kernel panic with linux-headers-3.2.0-0.bpo.2-amd64
- To: Ben Hutchings <email@example.com>
- Cc: firstname.lastname@example.org
- Subject: Re: Kernel panic with linux-headers-3.2.0-0.bpo.2-amd64
- From: Nick White <email@example.com>
- Date: Wed, 28 Mar 2012 10:09:17 +0100
- Message-id: <20120328090917.GA1687@starfish>
- In-reply-to: <20120327150600.GF3650@starfish>
- References: <20120327084941.GB2284@starfish> <4F713D13.firstname.lastname@example.org> <20120327102534.GA1755@starfish> <1332858939.3500.178.camel@deadeye> <20120327144509.GE3650@starfish> <1332860260.3500.184.camel@deadeye> <20120327150600.GF3650@starfish>
On Tue, Mar 27, 2012 at 04:06:00PM +0100, Nick White wrote:
> On Tue, Mar 27, 2012 at 03:57:40PM +0100, Ben Hutchings wrote:
> > On Tue, 2012-03-27 at 15:45 +0100, Nick White wrote:
> > > On Tue, Mar 27, 2012 at 03:35:39PM +0100, Ben Hutchings wrote:
> > > > This really isn't going to be very useful without the earlier messages
> > > > which scrolled off the screen.
> > Another option is kernel parameter boot_delay=100, which will slow down
> > logging and should let you get a photograph of the first part of the
> > panic messages. The '100' specifies a 100 ms delay between lines; you
> > can increase or decrease that as necessary.
> Ah, OK, I didn't know about that, it sounds like a fine plan. I'll
> borrow a friend's camera tomorrow and get those photos.
Right, I've photographed the screen at most points of the boot
process, using that handy boot_delay method. The photos are at
Hopefully the interesting stuff is in there; if not let me know what
is considered interesting and I'll have another go.
Thanks again folks.