[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#505609: marked as done (Unbootable after kernel upgrade: Lilo can't load kernel)



Your message dated Fri, 14 Nov 2008 12:42:22 +0100
with message-id <20081114114222.GB15565@wavehammer.waldi.eu.org>
and subject line Re: Bug#505609: Unbootable after kernel upgrade: Lilo can't load kernel
has caused the Debian Bug report #505609,
regarding Unbootable after kernel upgrade: Lilo can't load kernel
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
505609: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505609
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.26-1-amd64
Version: 2.6.26-10
Severity: critical

I've did an upgrade on 2008-11-09, on a new installed system, upgrading kernel 
2.6.26-09 to 2.6.26.10. Apt was also upgraded.
I've seen nothing strange during upgrade and in the apt and dpkg logs. The 
system is entirely on LVM partitions.

When reboting I obtain this message from Lilo:
"Loading LinuxEBDA is big; kernel setup stack overlaps LILO second stage".
and the computer halt.


regards
-- 
Xavier
xavier@alternatif.org



--- End Message ---
--- Begin Message ---
On Thu, Nov 13, 2008 at 08:54:32PM +0100, Xavier Brochard wrote:
> When reboting I obtain this message from Lilo:
> "Loading LinuxEBDA is big; kernel setup stack overlaps LILO second stage".
> and the computer halt.

Bug in lilo. It does not properly check the size of the initrd and fails
to load it.

Bastian

-- 
The sight of death frightens them [Earthers].
		-- Kras the Klingon, "Friday's Child", stardate 3497.2


--- End Message ---

Reply to: