Bug 5462 - Kernel fails to boot with kernel 2.6.14-rc4-mm1
Summary: Kernel fails to boot with kernel 2.6.14-rc4-mm1
Status: REJECTED INSUFFICIENT_DATA
Alias: None
Product: Platform Specific/Hardware
Classification: Unclassified
Component: Other (show other bugs)
Hardware: i386 Linux
: P2 high
Assignee: Zwane Mwaikambo
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-18 00:30 UTC by Sharyathi
Modified: 2006-11-13 05:10 UTC (History)
5 users (show)

See Also:
Kernel Version: 2.6.14-rc4-mm1
Subsystem:
Regression: ---
Bisected commit-id:

Attachments
Normal dmesg out put (24.04 KB, text/plain)
2005-11-02 03:24 UTC, Sharyathi 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Sharyathi 2005-10-18 00:30:49 UTC 
Most recent kernel where this bug did not occur:
2.6.14-rc4
--------------------------------------------------------
Distribution:
SLES 9 SP2
--------------------------------------------------------
Hardware Environment:
2 way, Intel(R) Xeon(TM) CPU 2.80GHz, 1.5 GB
SCSI driver: IBM ServeRAID Controller
Network Driver: Broadcom Corporation NetXtreme BCM5703X Gigabit Ethernet
--------------------------------------------------------
Software Environment:
Linux x235b 2.6.14-rc4-I #1 SMP PREEMPT Mon Oct 17 08:46:32 PDT 2005 i686
i686 i386 GNU/Linux
--------------------------------------------------------
Problem Description:
 After building the kernel 2.6.14-rc4-mm1 machine fails to boot properly I had
used the same config file which worked with 2.6.14-rc4. I observed these
messages on the Serial console 

Pid: 0, comm:              swapper
EIP: 0060:[<c05bec50>] CPU: 0
EIP is at nmi_cpu_busy+0x10/0x20
 EFLAGS: 00000246    Not tainted  (2.6.14-rc4-mm1-I)
EAX: 00000000 EBX: c5d61f9c ECX: 00010000 EDX: c5d61f9c
ESI: c05bec40 EDI: 00000000 EBP: c05b3f44 DS: 007b ES: 007b
CR0: 8005003b CR2: fff3f000 CR3: 005f3000 CR4: 000006c0
 [<c01012aa>] show_regs+0x16a/0x194
 [<c0143431>] softlockup_tick+0x81/0x90
 [<c0129895>] do_timer+0x45/0xe0
 [<c01082d8>] timer_interrupt+0x78/0xa0
 [<c014364e>] handle_IRQ_event+0x3e/0x90
 [<c014372c>] __do_IRQ+0x8c/0x100
 [<c0105576>] do_IRQ+0x26/0x40
 [<c0103bb6>] common_interrupt+0x1a/0x20
 [<c0111d11>] smp_call_function_interrupt+0x41/0x70
 [<c0103c20>] call_function_interrupt+0x1c/0x24
 [<c0100eda>] cpu_idle+0x9a/0xc0
 [<c01002e4>] rest_init+0x44/0x50
 [<c05b4a3a>] start_kernel+0x17a/0x1a0
 [<c0100210>] 0xc0100210
BUG: soft lockup detected on CPU#0!
--------------------------------------------------------
Comment 1 Zwane Mwaikambo 2005-10-30 23:34:23 UTC 
Could i please get dmesg from a normal working boot?
Comment 2 Sharyathi 2005-11-02 03:24:11 UTC 
Created attachment 6445 [details]
Normal dmesg out put

This is normal dmesg out put for 2.6.14-rc5.
Comment 3 Sharyathi 2005-11-08 02:14:18 UTC 
Observed the Same bug in latest kernel 2.6.14-mm1
Comment 4 Raghuveer Raghavendra 2005-11-24 21:49:36 UTC 
Noticed the same bug in the kernel 2.6.15-rc2-mm1
Comment 5 Dave Hansen 2006-03-14 15:41:50 UTC 
Could you run this through again on a recent kernel?
Comment 6 Dave Hansen 2006-05-08 10:54:47 UTC 
Six months since last update from submitter.  Time to close?
Comment 7 Adrian Bunk 2006-11-13 05:10:52 UTC 
Please reopen this bug if it's still present in recent kernels.
Note You need to log in before you can comment on or make changes to this bug.