Red Hat Bugzilla – Bug 28195
poweroff halts system, then ctl-alt-del causes oops
Last modified: 2007-04-18 12:31:32 EDT
build: qa0217.0 upgraded 7.0 system to 7.1 # poweroff .... Unmounting file systems: Unmounting proc file system: The system is halted stopping all md devices. Power down. (system does not powerdown) type CTL-ALT-DEL stopping all md devices. NMI Watchdog detected LOCKUP on CPU2, registers: CPU: 2 EIP: 0010:[<c0209f62>] EFLAGS: 00000097 eax: 4ea21ab1 ebx: 00079f2c ecx: 4ea16b1b edx: 00000038 esi: 00000000 edi: 00000001 ebp: c02ffe40 esp: c213fe94 ds: 0018 es: 0018 ss: 0018 Process swapper (pid: 0, stackpage=c213f000) Stack: 0000000d c01c076b 00079f2c c027ac78 c0122865 c027ac78 00000001 00000000 00000002 0000f20c 0000006f c0122da8 c02cfde4 00000001 00000000 c018d9d1 c018d30e 0000000c 00000000 6f000020 00000000 00000053 0000270f c213e000 Call Trace: [<c01c076b>] [<c0122865>] [<c0122da8>] [<c018d9d1>] [<c018d30e>] [< [<c0120776>] [<c018e5ec>] [<c010aa1e>] [<c010ac21>] [<c0107290>] [<c0109 [<c01072bc>] [<c0107342>] [<c0118e95>] Code: 29 c8 39 d8 72 f8 5b c3 8d b6 00 00 00 00 8b 44 24 04 eb 0a console shuts up ...
Congratulations, your bios doesn't like the kernel.
Try "apm=realmode" on the lilo "append" line, or on the lilo commandline
"linux apm=realmode" seemed to work OK. FWIW, I wasn't able to reproduce the oops when I booted with linux-up.
Were you using the apm=power-off option ?
This defect is considered MUST-FIX for Florence Gold release
no. the system is running with a default lilo.conf file. I just tried passing the apm=power-off option, and I didn't get an oops. Here are all of my results: linux-up --> no problems linux apm=realmode --> no problems linux apm=power-off --> no problems linux --> oops I just realized that some of the Call Trace was not included in my original posting. Let me know if you need me to attach another copy.
No need for the call-trace, it's the bios that faults. You seem to be the (un)lucky owner of a machine with a crappy bios. We can revert back to beta3 behavior, but that breaks for a hole lot of other people. The basic dilemma was <it doesn't work for a lot of people> vs <it oopses for a few, but we can give them the commandline option> Now, it woud be nice if we could make this PCI id dependend, so please post lspci and lspci -n here. (and also the brand of the motherboard + bios version is possible, as well as the dmesg output so we might be able to trigger on that)
The original oops was from a Dell PowerEdge 6300 server with 4 xeon cpus. BIOS: Phoenix ROM BIOS PLUS 1.10 A06. (Haven't determined the motherboard information yet.) The problem is also reproducible on an Acer Altos with 2 cpus. BIOS: ((I assume Acer...any other brandname wasn't obvious) v3.0 (R01-C4 01 EN) I know this is kind of cryptic, but the information is straight from the BIOS product information screen) MOTHERBOARD: Acer M19A The lspci and dmesg information will be attached below.
Created attachment 10760 [details] Dell PowerEdge lspci/lspci -n
Created attachment 10761 [details] Dell PowerEdge dmesg
Created attachment 10762 [details] Acer Altos lspci/lspci -n
Created attachment 10763 [details] Acer Altos dmesg
SMP poweroff is not supported.
closing.