Bug#656824: "cannot read the Linux header" trying to boot linux 3.2.1-1

To: James Robertson <j@mesrobertson.com>
Cc: 656824@bugs.debian.org, Friedemann Stoyan <fstoyan@swapon.de>
Subject: Bug#656824: "cannot read the Linux header" trying to boot linux 3.2.1-1
From: Jonathan Nieder <jrnieder@gmail.com>
Date: Sun, 29 Jan 2012 04:07:31 -0600
Message-id: <[🔎] 20120129100731.GB14790@burratino>
Reply-to: Jonathan Nieder <jrnieder@gmail.com>, 656824@bugs.debian.org
In-reply-to: <[🔎] CAMALoy9N74W69U1BBC0x+_xmNdWFiK2CEUU8wdOZnt4uPdW2SA@mail.gmail.com>
References: <[🔎] CAMALoy9qkioqNEMDy2x2zryE2z=347A72N+=3sBDJ3CE-NBXsQ@mail.gmail.com> <[🔎] 1327232827.8004.113.camel@deadeye> <[🔎] CAMALoy9N74W69U1BBC0x+_xmNdWFiK2CEUU8wdOZnt4uPdW2SA@mail.gmail.com>

James Robertson wrote:

> I upgraded to 3.2.1-2 and it booted fine.

Weird.  So it only happens sometimes, I guess.

Friedemann, is the result of upgrading the kernel the same for you?
(Please back up /boot first in case we have questions about it.)

Reply to:

Follow-Ups:
- Bug#656824: "cannot read the Linux header" trying to boot linux 3.2.1-1
  - From: Friedemann Stoyan <fstoyan@swapon.de>

References:
- Bug#656824: Reinstalling GRUB did not help
  - From: James Robertson <j@mesrobertson.com>
- Bug#656824: Reinstalling GRUB did not help
  - From: Ben Hutchings <ben@decadent.org.uk>
- Bug#656824: Reinstalling GRUB did not help
  - From: James Robertson <j@mesrobertson.com>

Prev by Date: Processed: Re: linux-image-2.6.32-5-amd64: cdrom stops working
Next by Date: Bug#657612: linux-image-3.2.0-1-amd64: scheduling while atomic: swapper/2/0/0x10000100
Previous by thread: Bug#656824: Reinstalling GRUB did not help
Next by thread: Bug#656824: "cannot read the Linux header" trying to boot linux 3.2.1-1
Index(es):
- Date
- Thread