A strange screen appears just before the system shuts down.
This appears to be a dump of registers and/or memory.
If someone would tell me how to capture this (it seems to
be more than one screen full.) I will be happy to pass it
This is an HP Series 4 5/133 with 48MB of memory.
The output of first few lines of dmesg.
Linux version 2.2.5-15 (email@example.com) (gcc
version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1
Mon Apr 19 22:21:09 EDT 1999
Detected 132633208 Hz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 52.84 BogoMIPS
Memory: 46920k/49152k available (996k kernel code, 412k
reserved, 764k data, 60k init)
VFS: Diskquotas version dquot_6.4.0 initialized
CPU: Intel Pentium 75 - 200 stepping 0b
Checking 386/387 coupling... OK, FPU using exception 16
Checking 'hlt' instruction... OK.
Intel Pentium with F0 0F bug - workaround enabled.
POSIX conformance testing by UNIFIX
PCI: PCI BIOS revision 2.10 entry at 0xf70dc
Really need more information about this in order to determine what is
happening with the system. Please try to post the dump that you are
How would we capture the kernel dump?
I'm experiencing the same bug. I don't consider it too serious, as it
happens when the system would normally be halted anyway. It occurs in
stock RedHat kernels for both 5.9 and 6.0. Kernels that I compile
myself have absolutely no problems.
------- Email Received From Chaim Frenkel <firstname.lastname@example.org> 05/24/99 17:01 -------
I have 2 boxes at home--one does this, the other doesn't.
On the good one, the output of halt is this (not verbatim, sorry):
INIT: changing runlevel..
Shutting down ____ (repeats a lot)
The System is halted.
(there's some new-to-2.2 "md_* awoken" messages in there, too)
On the bad system, it's the same until the last two lines:
The System is halted
Kernel Page Fault ... blah blah blah.. oops... blah blah...
So, AFAIK, the net effect is that instead of getting a single
line "Power Down", I get 2 pages of kernel error messages.
Pretty innocuous, but interesting (and ugly).
This bug is similar enough to #3100 that I'm going to coalesce.
*** This bug has been marked as a duplicate of 3100 ***