Bug#487634: linux-image-2.6.24-1-686: computer freezes when idle
On Mon, Jun 23, 2008 at 01:23:41PM +0400, Alexander Polakov wrote:
> Package: linux-image-2.6.24-1-686
> Version: 2.6.24-7
> Severity: important
>
>
> Computer freezes after a period of inactivity.
>
> Jun 22 06:47:04 pinnsvin syslogd 1.5.0#4: restart.
> Jun 22 06:50:37 pinnsvin kernel: 060:[<c02bdbe9>] EFLAGS: 00000293 CPU: 0
> Jun 22 06:50:37 pinnsvin kernel: EIP is at _spin_unlock_irqrestore+0xa/0x13
> Jun 22 06:50:37 pinnsvin kernel: EAX: 00000293 EBX: 00000001 ECX: 00000293 EDX: 00000200
> Jun 22 06:50:37 pinnsvin kernel: ESI: ffffffff EDI: da313808 EBP: 00000000 ESP: c0373f40
> Jun 22 06:50:37 pinnsvin kernel: DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
> Jun 22 06:50:37 pinnsvin kernel: CR0: 8005003b CR2: b757f000 CR3: 1a72e000 CR4: 000006d0
> Jun 22 06:50:37 pinnsvin kernel: DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
> Jun 22 06:50:37 pinnsvin kernel: DR6: ffff0ff0 DR7: 00000400
> Jun 22 06:50:37 pinnsvin kernel: [<c013c4b2>] tick_notify+0x1ce/0x2e4
> Jun 22 06:50:37 pinnsvin kernel: [<c011da71>] __update_rq_clock+0x1a/0xf3
> Jun 22 06:50:37 pinnsvin kernel: [<c0138d3c>] notifier_call_chain+0x2a/0x47
> Jun 22 06:50:37 pinnsvin kernel: [<c0138d9f>] raw_notifier_call_chain+0x17/0x1a
> Jun 22 06:50:37 pinnsvin kernel: [<c013bfd2>] clockevents_notify+0x19/0x50
> Jun 22 06:50:37 pinnsvin kernel: [<dc829625>] acpi_idle_enter_simple+0x1a1/0x1f0 [processor]
> Jun 22 06:50:37 pinnsvin kernel: [<c024fa50>] cpuidle_idle_call+0x5c/0x80
> Jun 22 06:50:37 pinnsvin kernel: [<c024f9f4>] cpuidle_idle_call+0x0/0x80
> Jun 22 06:50:37 pinnsvin kernel: [<c01025f3>] cpu_idle+0xab/0xcc
> Jun 22 06:50:37 pinnsvin kernel: [<c0377942>] start_kernel+0x338/0x340
> Jun 22 06:50:37 pinnsvin kernel: [<c03770db>] unknown_bootoption+0x0/0x195
> Jun 22 06:50:37 pinnsvin kernel: =======================
> Jun 22 06:50:37 pinnsvin kernel:
> Jun 22 06:50:37 pinnsvin kernel: Pid: 0, comm: swapper Not tainted (2.6.24-1-686 #1)
hmm please try 2.6.25 from unstable, afaik those oopses are hard to
trace and not yet fixed upstream.
best regards
--
maks
Reply to: