On Wed, Feb 06, 2008 at 03:37:05PM +0000, Sam Morris wrote: > Since upgrading to 2.6.24, my laptop keeps locking up for short periods > of time. I have noticed that the following kernel messages are logged > about 30 times when this happens. > > Feb 6 15:31:45 tycho kernel: BUG: soft lockup - CPU#0 stuck for 11s! > [swapper:0] > Feb 6 15:31:45 tycho kernel: > Feb 6 15:31:45 tycho kernel: Pid: 0, comm: swapper Not tainted (2.6.24-1-686 > #1) > Feb 6 15:31:45 tycho kernel: EIP: 0060:[<c02bd859>] EFLAGS: 00000293 CPU: 0 > Feb 6 15:31:45 tycho kernel: EIP is at _spin_unlock_irqrestore+0xa/0x13 > Feb 6 15:31:45 tycho kernel: EAX: 00000293 EBX: 00000001 ECX: 00000293 EDX: > 00000200 > Feb 6 15:31:45 tycho kernel: ESI: ffffffff EDI: f7cd9008 EBP: 00000000 ESP: > c0373f40 > Feb 6 15:31:45 tycho kernel: DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 > Feb 6 15:31:45 tycho kernel: CR0: 8005003b CR2: f94b24e4 CR3: 1fb0f000 CR4: > 000006d0 > Feb 6 15:31:45 tycho kernel: DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: > 00000000 > Feb 6 15:31:45 tycho kernel: DR6: ffff0ff0 DR7: 00000400 > Feb 6 15:31:45 tycho kernel: [<c013c3ee>] tick_notify+0x1ce/0x2e4 > Feb 6 15:31:45 tycho kernel: [<c011da5d>] __update_rq_clock+0x1a/0xf3 > Feb 6 15:31:45 tycho kernel: [<c0138c78>] notifier_call_chain+0x2a/0x47 > Feb 6 15:31:45 tycho kernel: [<c0138cdb>] raw_notifier_call_chain+0x17/0x1a > Feb 6 15:31:45 tycho kernel: [<c013bf0e>] clockevents_notify+0x19/0x50 > Feb 6 15:31:45 tycho kernel: [<f882d615>] > acpi_idle_enter_simple+0x1a1/0x1f0 [processor] > Feb 6 15:31:45 tycho kernel: [<c024f6e4>] cpuidle_idle_call+0x5c/0x80 > Feb 6 15:31:45 tycho kernel: [<c024f688>] cpuidle_idle_call+0x0/0x80 > Feb 6 15:31:45 tycho kernel: [<c01025f3>] cpu_idle+0xab/0xcc > Feb 6 15:31:45 tycho kernel: [<c0377942>] start_kernel+0x338/0x340 > Feb 6 15:31:45 tycho kernel: [<c03770db>] unknown_bootoption+0x0/0x195 > Feb 6 15:31:45 tycho kernel: =======================
please run memtest86 for at least 24h this smells faulty hardware. crashes in cpu_idle() tend to be hardware issues. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
