Bug 14397

Summary:	EIP is at acpi_idle_enter_simple+0x11d/0x161
Product:	ACPI	Reporter:	Tony White (tonywhite100)
Component:	Power-Processor	Assignee:	Venkatesh Pallipadi (venki)
Status:	CLOSED UNREPRODUCIBLE
Severity:	normal	CC:	lenb, rui.zhang, yakui.zhao
Priority:	P1
Hardware:	All
OS:	Linux
Kernel Version:	2.6.31.2	Subsystem:
Regression:	No	Bisected commit-id:
Attachments:	dmidecode lspci

Description Tony White 2009-10-13 01:46:00 UTC

I've got a back trace :

sysrq: show backtrace of all active cpus
cpu0:
pid: 0,comm : swapper not tainted (2.6.31.2#1) m3n
EIP: 0060 : [<c0668706>] EFLAGS: 00000246 cpu :0
EIP is at acpi_idle_enter_simple+0x11d/0x161
EAX: 00000000 EBX: 0000095e ECX: 00000007 EDX: 9640cf68
ESI: 00000000 EDI: f6d7ad5c EBP: c09dff48 ESP: c09dff24
DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
CR0: 8005003b CR2: 084511e4 CR3: 00c2e000 CR4: 000006d0
DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
DR6: ffff0ff0 DR7: 00000400
Call Trace:
[<c066842f>] acpi_idle_enter_bm+0xd2/0x28c
[<c075692a>] ? menu_select+0x48/0xc2
[<c0755a36>] cpu_idle_call+0x73/0xbd
[<c040286c>] cpu_idle+0xac/0xcc
[<c080a62a>] rest_init+0x66/0x79
[<c0a71a6b>] start_kernel+036f/0x385
[<c0a7107e>] i386_start_kernel+0x7e/0x96

I had to copy it onto paper and then type it out but it should be accurate.
It caused the kernel to crash.

Comment 1 Tony White 2009-10-13 01:48:58 UTC

Created attachment 23369 [details]
dmidecode

Comment 2 Tony White 2009-10-13 01:50:54 UTC

Created attachment 23370 [details]
lspci

Comment 3 ykzhao 2009-11-30 13:29:13 UTC

Hi, Tony
    Will you please describe the back-trace more clearly? For example: how to trigger it?  It will be great if you can attach the output of dmesg when the oops happens.
   thanks.

Comment 4 Zhang Rui 2009-12-04 03:49:35 UTC

re-assign to venki. :)

Comment 5 Zhang Rui 2009-12-22 03:44:28 UTC

ping Venki....

Comment 6 Venkatesh Pallipadi 2009-12-23 22:15:42 UTC

The message looks to be coming from sysrq handler (drivers/char/sysrq.c) for sysrq magic + l.

I don't see anything wrong with the log.

Tony, did you see this during boot? or something during runtime to trigger it?

Comment 7 Tony White 2009-12-24 10:48:55 UTC

Booting off a usb stick. I can't really add much more than that, it was a while ago and I don't even think the latest Linux kernels boot to X on this machine any more, so wouldn't be able to try to reproduce it. It's not a testing machine.
I've seen at least one regression per release over the last year on this machine which went from running Linux flawlessly to just about with a lot of work, therefore I've stopped tracking the Linux kernel on this machine.
For now, the machine is pretty much a won't fix.

Comment 8 Venkatesh Pallipadi 2009-12-29 21:55:16 UTC

OK. Closing the bug as UNREPRODUCIBLE for now. Feel free to reopen if you see this problem again either on same or on any other systems.