Most recent kernel where this bug did *NOT* occur: 2.6.18-gentoo-r6 Distribution: Gentoo 2006.1 Hardware Environment: 4x Dual Core AMD Opteron(tm) Processor 880 Broadcom HT1000 (with PCI-X and SATA) LSI Logic / Symbios Logic (megaraid_sas) 2x NetXtreme BCM5780 Gigabit Ethernet Intel Corporation 82541GI/PI Gigabit Ethernet Controller Software Environment: mysql server Problem Description: when server bootin up with new kernel i see on CPU1,2,3 this error: Initializing CPU#1 NMI Watchdog detected LOCKUP on CPU 1 CPU 1 Modules linked in: Pid: 0, comm: swapper Not tainted 2.6.20.2 #1 RIP: 0010:[<ffffffff802eabe2>] [<ffffffff802eabe2>] read_current_timer+0x2/0x20 RSP: 0018:ffff81021888fe60 EFLAGS: 00000297 RAX: 00000000abbcbcbf RBX: 00000000fffb6e1e RCX: 00000000c0010000 RDX: 000000000000005d RSI: 0000000000000000 RDI: ffff81021888fe90 RBP: 00000000fffb6e1d R08: 0000000000000000 R09: 00000000ffffffff R10: 00000000ffdb7817 R11: 0000000000000000 R12: 0000000000000000 R13: ffff81021888fe90 R14: 0000000000000000 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff81021886be40(0000) knlGS:0000000000000000 CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b CR2: 0000000000000000 CR3: 0000000000201000 CR4: 00000000000006a0 Process swapper (pid: 0, threadinfo ffff81021888e000, task ffff8106200a4e20) Stack: ffffffff80207905 0000000000000000 ffffffff802e903a 0000000000000001 ffff81000103d700 0000000000000000 0000005dabbcbcb5 0000005dabbcbcb5 0000000000000001 0000000000000000 0000000000000000 0000000000000000 Call Trace: [<ffffffff80207905>] calibrate_delay+0xf5/0x380 [<ffffffff802e903a>] strstr+0x3a/0x80 [<ffffffff8051b9f2>] smp_callin+0xb2/0x110 [<ffffffff8051c618>] start_secondary+0x18/0x520 Code: 48 c1 e2 20 89 c0 48 09 d0 48 89 07 31 c0 c3 66 66 66 90 66 <0>Kernel panic - not syncing: Attempted to kill the idle task! Stuck ?? Inquiring remote APIC #1... ... APIC #1 ID: 01000000 ... APIC #1 VERSION: 00040010 ... APIC #1 SPIV: 000000ff and when system is UP i see onlu cores 0,4,5,6,7 Steps to reproduce:
same with acpi=off?
Please reopen this bug if: - it is still present with kernel 2.6.21 and - you canprovide the requested information.