Bug 126803
Summary: | kernel panic during boot with SMP 2.6.6.-1.435 kernel | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Steve Underwood <steveu> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED NEXTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 2 | CC: | pfrields |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-04-16 04:17:45 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Steve Underwood
2004-06-27 13:00:44 UTC
I have seen this problem as well. When I try to boot with the 435 or 435.2.3 smp kernel, i get a null pointer crash in the kernel immediately on bootup. it doesn't get as far as the ps/2 code. I have seen this too, so here's some more information. The system is a dual Intel(R) Xeon(TM) CPU 3.20GHz with hyperthreading. Under the original 2.6.5-1.358 SMP kernel the machine booted but the keyboard and mouse were somewhat mixed up (in text mode the keyboard worked if plugged into the mouse port, but under X11 both the PS/2 ports behaved as mouse ports and a USB keyboard had to be used - luckily this machine is a server, so doesn't usually need a keyboard attached). 2.6.6-1.435smp and (just recently) 2.6.7-1.494.2.2smp both fail to boot, although the single-processor versions do work. The crash dumps differ (sometimes mentioning badness in do_unblank_screen at drivers/char/vt.c:2860), but here's a typical one (via scribbling on a piece of paper, so I haven't copied down all the symbolic locations or the whole stack dump). mice: PS/2 mouse device common for all mice Failed to disable AUX port, but continuing anyway... is this a SiS? If AUX port is really absent please use the 'i8042.noaux' option. serio: i8042 AUX port at 0x60,0x64 irq 12 serio: i8042 KBD port at 0x60,0x64 irq 1 Unable to handle kernel NULL pointer dereference at virtual address 00000000 printing eip: 00000000 *pde=00003001 Oops: 0000[#1] SMP Modules linked in: CPU: 0 EIP: 0060:[<00000000>] Not tainted EFLAGS: 00010217 (2.6.7-1.494.2.2smp) EIP is at 0x0 eax: 39e74000 ebx: 39e74000 ecx: 00000000 edx: 00000000 esi: 00000000 edi: 0234b6a0 ebp: 0234b6a0 esp: 81f30f04 ds: 007b es: 007b ss: 0068 process swapper (pid: 1, threadinfo=81f30000 task=39ff16f0) Stack: 0226adb3 00000000 00000000 0234b440 00000000 39e746f0 0226ce48 00000000 Call Trace: [<0226adb3>] psmouse_interrupt + 0x1c1/0x272 [<0226ce48>] serio_interrupt + 0x21/0x53 [<0226d6a2>] i8042_interrupt + 0x158/0x16b [<0226d4b8>] i8042_open + 0xf/0x23 [<0226d0b5>] [<0226b5f3>] [<0226cb07>] [<0226ceaf>] [<023aaa21>] [<023aabb7>] [<023917ec>] do_initcalls + 0x49/0x97 [<021004f1>] init + 0xc2/0x1b8 [<0210042f>] init + 0x0/0x1b8 [<021041f1>] kernel_thread_helper + 0x5/0x6 Code: bad EIP value <0> kernel panic: Attempted to kill init! Anyway, Bug 124138 mentions going into the BIOS and turning off "legacy USB support". Now I've done that the machine boots successfully and also correctly recognises the keyboard and mouse. Before I did that, I also tried booting with a bunch of i8042.* kernel parameters (namely: direct, noaux, nomux and reset all at once). The result of that was the message: kernel: i8042.c: i8042 controller selftest failed. (0x0 != 0x55) and no keyboard or mouse support at all, but at least it did boot. mass update for old bugs: Is this still a problem with the 2.6.9 based update kernel ? Fedora Core 2 has now reached end of life, and no further updates will be provided by Red Hat. The Fedora legacy project will be producing further kernel updates for security problems only. If this bug has not been fixed in the latest Fedora Core 2 update kernel, please try to reproduce it under Fedora Core 3, and reopen if necessary, changing the product version accordingly. Thank you. |