From: "Gnea" <gnea@rochester.rr.com>
To: linux-kernel@vger.kernel.org, Gerard Sharp <gsharp@ihug.co.nz>
Subject: Re: HPT366 + SMP = slight corruption in 2.3.99 - 2.4.0-11
Date: 02 Dec 2000 11:25:48 EST [thread overview]
Message-ID: <20001202162105.AAA28297@mail2.nyroc.rr.com@celery> (raw)
In-Reply-To: <3A2785BB.EB36DDE0@ihug.co.nz>
In-Reply-To: <3A2785BB.EB36DDE0@ihug.co.nz>
On Sat, 02 Dec 2000 00:04:27 +1300, Gerard Sharp blurted forth:
> Hello.
> [1.] One line summary of the problem:
> Intermittent corruption of 4 bytes in SMP kernels using HPT366
[snip]
> [7.] Environment
> Redhat 6.2 basis.
> Abit BP6 Motherboard.
> Dual Celeron 466's
> 128 Mb ram; 13.6 Gb Seagate Barracuda HDD
> "hda: ST313620A, ATA DISK drive"
> CD-ROM on hdd
[snip]
Have you tried updating the bios on the bp6? This solved a LOT of
problems for me, and afaik, ru is the latest... if you need a hand with
it, i've put together a dos boot disk with everything you'll need at:
http://garson.org/~gnea/bp6-biosupdate.img
just dd if=bp6-biosupdate.img of=/dev/fd0 and boot it, run awdflash.exe
and tell it to use bp6_ru.bin when it asks for a file... have it back
up the current bios (just in case) and reboot when ready.. you'll of
course need to go into the bios on reboot and reset everything to
defaults, then go thru and re-tweak (this is the proper method.. not
doing so can create further problems) all of your settings until it's
satisfactorily set... also, the overclocking might be a bad thing in
this case unless you have the proper cooling for it (lm-sensors is
great for this sort of thing :) there's a neat wm applet called wmbp6
too) so u may want to try clocking it straight at 300 for awhile and
see what effect that has.. hope this helps
--
.oO gnea at rochester dot rr dot com Oo.
.oO url: http://garson.org/~gnea Oo.
"You can tune a filesystem, but you can't tuna fish" -unknown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-02 17:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-01 11:04 HPT366 + SMP = slight corruption in 2.3.99 - 2.4.0-11 Gerard Sharp
2000-12-02 16:25 ` Gnea [this message]
2000-12-04 16:10 ` Gerard Sharp
2000-12-04 20:49 ` Dan Hollis
2000-12-04 21:27 ` Richard Torkar
2000-12-04 21:41 ` Dan Hollis
2000-12-04 21:51 ` Mike Dresser
2000-12-06 10:33 ` Gerard Sharp
2000-12-06 11:23 ` kernel
2000-12-07 9:23 ` Gerard Sharp
-- strict thread matches above, loose matches on Subject: below --
2000-12-04 16:39 Gerard Sharp
2000-12-05 20:34 Winfried Truemper
2000-12-09 9:43 Gerard Sharp
2000-12-09 9:57 ` Andre Hedrick
2000-12-10 3:26 ` Gerard Sharp
2000-12-10 12:15 ` Hakan Lennestal
2000-12-10 16:25 ` David Woodhouse
2000-12-10 17:17 ` Andre Hedrick
2000-12-10 19:01 ` Hakan Lennestal
2000-12-10 21:07 ` Gerard Sharp
2000-12-11 8:03 ` Andre Hedrick
2000-12-10 3:30 ` Gerard Sharp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20001202162105.AAA28297@mail2.nyroc.rr.com@celery \
--to=gnea@rochester.rr.com \
--cc=gsharp@ihug.co.nz \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox