From: Ryan Reich <ryanr@uchicago.edu>
To: linux-kernel@vger.kernel.org
Subject: Re: is nForce2 good choice under Linux?
Date: Sun, 15 Feb 2004 08:59:51 -0600 [thread overview]
Message-ID: <402F8967.1050405@uchicago.edu> (raw)
In-Reply-To: <1pt6s-686-9@gated-at.bofh.it>
Sander wrote:
> Jesse Allen wrote (ao):
>
>> On Fri, Feb 13, 2004 at 11:01:45PM +0200, aviv bergman wrote:
>>> i had very frequent lockups after upgrading to 2.6.0, flashed to the
>>> latest bios, and the system is rock stable since (2.6.1 w/apic)
>>
>> Wow, another fixed shuttle board? Looks like shuttle knows what the
>> bug is then.
>
>
> I've never read the Shuttle boards where unstable. I thought people had
> problems with the normal size boards from Asus and others.
I have a Shuttle AN35N-Ultra with an Athlon 2600+ on it which had the
infamous lockups under 2.4 until I figured out that it was the APIC and
turned that off. I just flashed the BIOS with the latest on Shuttle's site
and they seem to have gone, at least for now. Someone claims that he got
one after five days uptime, but I'm a wimp and turn my computer off every
night so I'll never see that.
--
Ryan Reich
ryanr@uchicago.edu
next parent reply other threads:[~2004-02-15 14:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1oRXf-7zC-13@gated-at.bofh.it>
[not found] ` <1oSgx-7QJ-11@gated-at.bofh.it>
[not found] ` <1oSJA-8nw-17@gated-at.bofh.it>
[not found] ` <1oTPp-YO-25@gated-at.bofh.it>
[not found] ` <1pt6s-686-9@gated-at.bofh.it>
2004-02-15 14:59 ` Ryan Reich [this message]
2004-02-13 20:10 is nForce2 good choice under Linux? Grzegorz Kulewski
2004-02-13 20:32 ` Daniel Drake
2004-02-13 21:01 ` aviv bergman
2004-02-13 21:36 ` Grzegorz Kulewski
2004-02-13 22:17 ` Jesse Allen
2004-02-13 22:36 ` Craig Bradney
2004-02-15 11:53 ` Sander
2004-02-14 0:37 ` John Dee
2004-02-13 21:24 ` Grzegorz Kulewski
2004-02-13 22:05 ` Daniel Drake
2004-02-13 22:12 ` Jesse Allen
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=402F8967.1050405@uchicago.edu \
--to=ryanr@uchicago.edu \
--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