Skip to contentSkip to conversation

fatal lockup, BIOS/CMOS reset?

DISCUSSION Jonathan Brugge 2 participants 2 messages Dec 10, 2000 – Dec 11, 2000

lore
Share & tools
lore
#0 lore raw

I was experimenting with Hunt, a program I found. This caused some heavy load, and my system had already quite some programs running, so I think I got out of memory (no programs got killed, shouldn't that be done by the VM?). Maybe it was for some other reason, but my system locked, I had to use CTRL-ALT-DELETE. This seemed to work, my HD made some sound and it rebooted. But then: I got a message about a bad CMOS and when I looked in my BIOS-settings I saw they were totally reset... No HD's, date was 1/1/2000, etc. After setting everything to the correct value I tried to boot again and no problem this time, not even about a partition that was unmounted incorrectly. It seems to me that no program may EVER have a chance to change things in BIOS/CMOS.I'm running kernel 2.4.0test11 with libc6-2.2.5 (Debian woody, if it matters).

1: Is it possible that a program sets options in BIOS/CMOS? 2: If so, should it be possible?
3: Any other things that could cause this to happen?

I'm not sure it's a kernel-related problem, but it's something that should never happen, in my opinion (except BIOS-flashing).

Thanks,

Jonathan Brugge

P.S.: My system: Gigabyte GA-7IXE mainboard, K7-700, 128 MB, AMD 751/756 chipset.
_____________________________________________________________________________________
Get more from the Web. FREE MSN Explorer download : http://explorer.msn.com

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/

#1 lore raw

** Reply to message from "Jonathan Brugge" <[email protected]> on Sun, 10 Dec 2000 22:49:05 +0100

Quoted 3 lines

I got a message about a bad CMOS and when I looked in my BIOS-settings I saw they were totally reset... No HD's, date was 1/1/2000, etc.

The BIOS will do this at boot time if it detects that the checksum bytes in the CMOS are incorrect. That's probably what happened - somehow, one or more bytes in your CMOS got altered, and during the reboot the BIOS detected this and reset all CMOS bytes.

The CMOS can be programmed using I/O ports 70h and 71h. Just a couple of bad I/O operations to those ports, and your CMOS is toast.

Signature · 8 lines
Timur Tabi - [email protected]
Interactive Silicon - http://www.interactivesi.com

When replying to a mailing-list message, please direct the reply to the mailing list only.  Don't send another copy to me.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/