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

Bug#593826: linux-image-2.6.26-2-686: Lilo reports kernal stack overlap on boot then hangs.



-------- Forwarded Message --------
From: JOHN HUNTER <jmdh01@btinternet.com>
To: Ben Hutchings <ben@decadent.org.uk>
Subject: Re: Bug#593826: linux-image-2.6.26-2-686: Lilo reports kernal stack overlap on boot then hangs.
Date: Sat, 21 Aug 2010 17:08:43 +0000 (GMT)

Hi Ben,


Answers embedded.


It would when one installs dear old lilo, the script needs to check for the presence of GRUB and adjust some config files? What should /etc/kernal-img.conf look like with lilo/


Regards,
John

--- On Sat, 21/8/10, Ben Hutchings <ben@decadent.org.uk> wrote:
        
        From: Ben Hutchings <ben@decadent.org.uk>
        Subject: Re: Bug#593826: linux-image-2.6.26-2-686: Lilo reports kernal stack overlap on boot then hangs.
        To: jmdh01@btinternet.com, 593826@bugs.debian.org
        Date: Saturday, 21 August, 2010, 15:56
        
        On Sat, 2010-08-21 at 12:09 +0100, John Hunter wrote:
        > Package: linux-2.6
        > Version: 2.6.26-24lenny1
        > Severity: critical
        > Justification: breaks the whole system
        > 
        > 
        > New version of kernal installed 20Aug2010. Tried booting this AM. The
        > new kernal could not have been tested with Lilo.
        
        Works for me.  Please send the contents of /etc/kernel-img.conf.
        ##>
        # Kernel image management overrides
        # See kernel-img.conf(5) for details
        do_symlinks = yes
        relative_links = yes
        do_bootloader = no
        do_bootfloppy = no
        do_initrd = yes
        link_in_boot = no
        postinst_hook = update-grub
        postrm_hook   = update-grub
        
        > I cannot use GRUB as it corrupts its own boot stage 1.5 in a system
        > crash or sometimes after "/sbin/halt".
        
        That sounds like a hardware problem to me.
        
        Do you have both lilo and grub packages installed?
        ##> yes.
        
        > N.B. my e-mail address is now: jmdh01@btinternet.com
        [...]
        
        Then you should put that address in ~/.reportbugrc.
        
        
        ##> Thanks, fixed.
        
        Ben.
        
        -- 
        Ben Hutchings
        Once a job is fouled up, anything done to improve it makes it worse.
        





Reply to: