home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!unislc!erc
- From: erc@unislc.uucp (Ed Carp)
- Subject: Re: Buffer corruption problems.
- X-Newsreader: Tin 1.1 PL5
- References: <1992Aug14.013130.26395@ucunix.san.uc.edu>
- Message-ID: <1992Aug14.050229.11692@unislc.uucp>
- Organization: Unisys Corporation SLC
- Date: Fri, 14 Aug 1992 05:02:29 GMT
- Lines: 25
-
- Humberto Ortiz-Zuazaga (zuazaga@ucunix.san.uc.edu) wrote:
-
- : I get a series of "HD: read_intr: status = 0x59", "HD: read_intr:
- : error = 0x10" followed by an "HD-controller reset" on an odball
- : Western Digital + Seagate IDE when doing big compiles ever since 0.96.
- : The compilations proceed without error, however.
- :
- : > - The errors always include the same file (which is why I thought
- : >perhaps that that particular file was living on a disk block that was going
- : >belly up. I plan to rename that file to .deadblock and putting a new copy
- :
- : It may be the same file, if compiling the file excercises the bug (not
- : reading it, compiling it). Check to see how much memory is used during
- : the compile, or turn off optimization?
-
- I got these, too. I finally isolated it to two areas of the disk - one
- of the areas was where some archived files live, the other was at the
- beginning of swap space (first cylinder of the disk). I used fdisk to
- mark the first cylinder of the disk unused (slightly reducing my swap
- space allocation) and haven't had a problem since! :) :)
- --
- Ed Carp, N7EKG erc@apple.com 801/538-0177
- "This is the final task I will ever give you, and it goes on forever. Act
- happy, feel happy, be happy, without a reason in the world. Then you can love,
- and do what you will." -- Dan Millman, "Way Of The Peaceful Warrior"
-