home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!cs.utexas.edu!qt.cs.utexas.edu!yale.edu!ira.uka.de!math.fu-berlin.de!news.th-darmstadt.de!hp14.iti.informatik.th-darmstadt.de!herr
- From: herr@hp14.iti.informatik.th-darmstadt.de (Gabor Herr)
- Subject: Re: Rebooting and bad cache
- Sender: news@infoserver.th-darmstadt.de (The Usenet-News System)
- Message-ID: <1992Jul31.104750.45463@infoserver.th-darmstadt.de>
- Date: Fri, 31 Jul 1992 10:47:50 GMT
- References: <1992Jul29.031659.2484@news.iastate.edu>
- Nntp-Posting-Host: hp14.iti.informatik.th-darmstadt.de
- Organization: TU Darmstadt
- Lines: 53
-
- In article <1992Jul29.031659.2484@news.iastate.edu>, mhbrekke@iastate.edu (Monty H. Brekke) writes:
- > Has anyone else received a bad cache memory error after rebooting Linux?
- > Every time I reboot, my BIOS tells me that my cache memory is bad, and that
- > I should disable it. This message comes up just before the Shoelace menu
- > appears and only after I have rebotted from Linux. Rebooting from DOS does
- > not seem to produce this error. Also, if I shutdown and then C-A-D instead of
- > typing reboot, the error does not appear. Disabling the external cache seems
- > to fix the problem.
- >
- > My system configuration is as follows:
- >
- > 486-33
- > AMI BIOS/OPTi chipset
- > 256K external cache
- > 16MB memory
- > 1.44MB 3.5 inch floppy drive on /dev/fd0
- > 1.2MB 5 inch floppy drive on /dev/fd1
- > Quantum 244MB hard drive partitioned as follows:
- > ~100MB DOS partition on /dev/hda1
- > ~64MB Linux root partition on /dev/hda2
- > ~50MB Linux partition on /dev/hda3, mounted as /home
- > ~20MB Linux swap partition on /dev/hda4
- > Colorado Memory Systems 250MB tape drive
- >
-
-
- I had similar problems with a 386/40Mhz, ETEQ Chipset board with 64K cache,
- 8MB memory. Linux produced segmentation fault or general protection errors from
- time to time under heavy load. With disabled caching everything worked fine.
-
- I thougth it was a timing problem, so I went back to the vendor and exchanged my
- board for a 386/33Mhz, C&T chipset, 64K cache board. But that wasn't and I got
- the same errors. Without caching everything OK.
-
- A friend of mine has Linux running on similar board (other manufacturer but
- same proc 386/33 with identical chipset (C&T), 64K cache, 8MB memory) without
- any problems. To ensure that not the IO cards or the memory caused the errors,
- we exchanged the two boards in our machines. And what happend?
-
- His board worked with my components: 8MB SIMMs, ColorImage VGA, HD (ST3144A)
- with IDE controller. My board didn't. :-(
-
- Any ideas? Did anybody had this kind of problems?
-
- Thanks in advance.
-
- Gabor
-
-
- ############################################################################
- Gabor Herr Email: herr@iti.informatik.th-darmstadt.de
- Computer Science Department
- Technical University of Darmstadt, Germany
-