Description of problem:
The kernel locks up at boot just after these messages:
pnp: Device 00:0b activated.
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI interrupt 0000:00:03.1[A] -> GSI 11 (level, low) -> IRQ 11
Version-Release number of selected component (if applicable):
...sometimes... I had a the problem a few times in a row, and after a boot in
FC4t1 that was already on the disk, it started working again!
Steps to Reproduce:
1. pxe boot rawhide
kernel locks up.
kernel and install proceed normally
First, see here: http://bugzilla.kernel.org/show_bug.cgi?id=2300
Since I had reported the problem on kernel.org, I had installed and used
successfully a few recent distros on this machine (FC3, Ark Linux 2005,
FC4-Test1/2.6.11-1177_FC4) and it worked fine. Even up the pxe boot vmlinuz I
rsync'ed yesterday (2005/03/26 18h30 EST from mirror ftp.muug.mb.ca) worked up
to the unrelated problem I reported in bug 152265.
However, the lock up has reappeared with FC4/2.6.11-1.1202_FC4 from rawhide
today (2005/03/26 11h30 EST from the same mirror).
If I compare with dmesg from from 2.6.11-1177_FC4, the next messages are
supposed to be:
io scheduler noop registered
io scheduler anticipatory registered
If I compare a screenful of messages before that, the only difference are:
Linux agpgart interface v0.100 (c) Dave Jones
[one line that is same]
+agpgart: Maximum main memory to use for agp memory: 149M
Linux agpgart interface v0.101 (c) Dave Jones
+PNP: PS/2 Controller [PNP0303:KBD, PNP0f13:MOU] at 0x60,0x64 irq 1,12
However, I haven't seen any difference in dmesg from a successful and
unsuccessful boot of 2.6.11-1.1202_FC4... Seems to be a very subtle
hardware/software interaction problem...
still a problem with the latest kernels ?
No response, closing.