From: Gerard Sharp <gsharp@ihug.co.nz>
To: Gnea <gnea@rochester.rr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: HPT366 + SMP = slight corruption in 2.3.99 - 2.4.0-11
Date: Tue, 05 Dec 2000 05:10:47 +1300 [thread overview]
Message-ID: <3A2BC207.45B8EF2E@ihug.co.nz> (raw)
In-Reply-To: <3A2785BB.EB36DDE0@ihug.co.nz> <20001202162105.AAA28297@mail2.nyroc.rr.com@celery>
Gnea wrote:
> > [1.] One line summary of the problem:
> > Intermittent corruption of 4 bytes in SMP kernels using HPT366
> [snip]
> Have you tried updating the bios on the bp6? This solved a LOT of
> problems for me, and afaik, ru is the latest...
RU seems the latest. Flashed bios as per your nicely detailed
instructions.
No improvement in condition, alas.
> 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
Err. "300(66)" probably won't help too much. The cpu's are multiplier
locked (love that one, Intel); so will run at 7 * 66 (466) when set to
chip defaults - which I currently am - to rule out flaky / stressed
hardware.
Temperatures are a nice frosty 30 deg C across all the temperature
sensors lm_sensors offers; and the thermal probe I have dangling in the
psu exhaust :)
[this is with two rc5des clients running - loadavg of 2 - btw]
Back to the original topic, I've done some more 'research'; and I'm not
_certain_ of my findings, but there's a few coincidences here...
I think I'll make a more general post to lkml direct in a minute.
Gerard Sharp
Two penguins at 1024x768
-
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-04 16:42 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
2000-12-04 16:10 ` Gerard Sharp [this message]
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=3A2BC207.45B8EF2E@ihug.co.nz \
--to=gsharp@ihug.co.nz \
--cc=gnea@rochester.rr.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.