Bug#555526: linux-image-2.6.26-2-686: 2.6.26-19lenny2 with serial console hangs on boot
Package: linux-image-2.6.26-2-686
Version: 2.6.26-19lenny2
Severity: normal
Hello,
I upgraded from (I think) 2.6.26-19lenny1 to 2.6.26-19lenny2
with the latest security update and I found my system would
hang during the boot. By 'hang' I mean that the boot
process seems to stop -- no further messages on the
console and the network never came up.
The system would not respond to ctrl-alt-del but does
respond to the <alt>-<sysrq>-cmd keys.
The last messages on the console before hang were:
ide_generic: please use "probe_mask=0x3f" module parameter for probing all legacy ISA IDE ports
ide_generic: I/O resource 0x1F0-0x1F7 not free.
ide_generic: I/O resource 0x170-0x177 not free.
I tried various combinations of things like "probe_mask=0x3f" and
"ide.probe_mask=0x3f" and "probe_mask=0x00" and "probe_mask=0x30" on
the kernel command line and nothing helped.
I also moved the hd to a different box (the one I'm reporting
this on now) and got the same behavior. (Both before and afger
rebuilding the initramfs.)
Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.26-2-686 depends on:
ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy
ii initramfs-tools [linux-initra 0.92o tools for generating an initramfs
ii module-init-tools 3.4-1 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.26-2-686 recommends:
ii libc6-i686 2.7-18 GNU C Library: Shared libraries [i
Versions of packages linux-image-2.6.26-2-686 suggests:
ii grub 0.97-47lenny2 GRand Unified Bootloader (Legacy v
pn linux-doc-2.6.26 <none> (no description available)
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
11-10-2009, 03:30 PM
dann frazier
Bug#555526: linux-image-2.6.26-2-686: 2.6.26-19lenny2 with serial console hangs on boot
On Tue, Nov 10, 2009 at 01:15:40AM -0600, Karl O. Pinc wrote:
> Package: linux-image-2.6.26-2-686
> Version: 2.6.26-19lenny2
> Severity: normal
>
> Hello,
>
> I upgraded from (I think) 2.6.26-19lenny1 to 2.6.26-19lenny2
> with the latest security update and I found my system would
> hang during the boot. By 'hang' I mean that the boot
> process seems to stop -- no further messages on the
> console and the network never came up.
Would you be able to test the 2.6.26-19lenny1 kernel to verify that it
did work? I don't see anything in 2.6.26-19lenny2 that could obviously
cause this, so it would be good to confirm that we're looking in the
right place.
--
dann frazier
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
11-10-2009, 06:13 PM
"Karl O. Pinc"
Bug#555526: linux-image-2.6.26-2-686: 2.6.26-19lenny2 with serial console hangs on boot
On 11/10/2009 10:30:54 AM, dann frazier wrote:
> On Tue, Nov 10, 2009 at 01:15:40AM -0600, Karl O. Pinc wrote:
> > Package: linux-image-2.6.26-2-686
> > Version: 2.6.26-19lenny2
> > Severity: normal
> >
> > Hello,
> >
> > I upgraded from (I think) 2.6.26-19lenny1 to 2.6.26-19lenny2
> > with the latest security update and I found my system would
> > hang during the boot.
> Would you be able to test the 2.6.26-19lenny1 kernel to verify that
> it
> did work?
I suspect the problem may not be in the kernel. Now that
I've had time to think it seems significant that once I removed
the serial console kernel parameters the system, eventually,
dropped me into single user mode due to an fsck error.
I was interacting with the the box via vga not the
serial port. Though the vga gets kernel messages
and eventually gets a getty it seems it does not
get any of the regular boot messages. So that's
where the "hang" is.
I'd like to keep this report and send is somewhere,
as an enhancement if nothing else. It sure would
be nice if there was either a way to have whichever
kernel parameter console=foo that happens to be
the one being used actually work as the console
throughout the whole boot process. (Grub does this,
which probably contributed to my confusion because
I was interacting with grub just fine.)
Karl <kop@meme.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
11-10-2009, 06:18 PM
"Karl O. Pinc"
Bug#555526: linux-image-2.6.26-2-686: 2.6.26-19lenny2 with serial console hangs on boot
Whoops. Sorry. Hit the send button by accident.
On 11/10/2009 10:30:54 AM, dann frazier wrote:
> On Tue, Nov 10, 2009 at 01:15:40AM -0600, Karl O. Pinc wrote:
> > Package: linux-image-2.6.26-2-686
> > Version: 2.6.26-19lenny2
> > Severity: normal
> >
> > Hello,
> >
> > I upgraded from (I think) 2.6.26-19lenny1 to 2.6.26-19lenny2
> > with the latest security update and I found my system would
> > hang during the boot.
> Would you be able to test the 2.6.26-19lenny1 kernel to verify that
> it
> did work?
I suspect the problem may not be in the kernel. Now that
I've had time to think it seems significant that once I removed
the serial console kernel parameters the system, eventually,
dropped me into single user mode due to an fsck error.
I was interacting with the the box via vga not the
serial port. Though the vga gets kernel messages
and eventually gets a getty it seems it does not
get any of the regular boot messages. So that's
where the "hang" is.
I'd like to keep this report and send is somewhere,
as an enhancement if nothing else. It sure would
be nice if there was either a way to have whichever
kernel parameter console=foo that happens to be
the one being used actually work as the console
throughout the whole boot process. (Grub does this,
which probably contributed to my confusion because
I was interacting with grub just fine.)
Absent that at warning would be nice. Perhaps the
kernel could emit something to those "consoles"
not available to init noting that the action is
happening elsewhere.
I would also like to see some more documentation.
I can't figure out just how it is that init
"gets" the console it does. (I suspect it takes
the last "console=foo".)
Thanks for the help.
Karl <kop@meme.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org