From: Willy Tarreau <willy@w.ods.org>
To: Erik Mouw <J.A.K.Mouw@its.tudelft.nl>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
"John W. M. Stevens" <john@betelgeuse.us>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Defect (Bug) Report
Date: Sun, 2 Feb 2003 13:57:45 +0100 [thread overview]
Message-ID: <20030202125745.GD19346@alpha.home.local> (raw)
In-Reply-To: <20030202124911.GC30830@arthur.ubicom.tudelft.nl>
On Sun, Feb 02, 2003 at 01:49:11PM +0100, Erik Mouw wrote:
> On Sun, Feb 02, 2003 at 09:42:41AM +0000, Alan Cox wrote:
> > > Any other suggestions, or recommendations to get more info?
> >
> > Three starting points
> >
> > 1. Run memtest86 on the box for a bit. I don't think its bad RAM however
> > 2. Plug in a PS/2 mouse if the box doesn't have one already. That avoids
> > a hardware flaw on the AMD that we don't current work around in software
> > 3. Check if 2.4.20 behaves the same way. I think it may fix your short
> > pauses but I don't think its going to fix the hang alas. It would be
> > useful to know however
>
> What's the current wisdom with dual Athlon boards to get them stable?
> This is my list so far (for Asus A7M266-D):
>
> - Plug in a PS/2 mouse even though you don't use it. It fixes certain
> hardware problems.
> - Select "PnP OS = no" in the BIOS so all PCI devices (even the ones
> behind the PCI-PCI bridge) get properly initialised.
> - Boot Linux with "noapic" to avoid random hangs.
I think it really depends on the motherboard revision. I bought one of the very
first ones, with buggy bios, unusable USB, etc..., but at least I have none of
the 3 problems you cite here. I have no PS/2 mouse plugged, and happily use it
in APIC mode. The 'pnp os' setup doesn't seem to have any effect either. But I
do have other problems, such as a DL2000 card hanging very quickly if plugged
into a 64bit PCI slot, so I use it in a 32bits one.
And it's a pain to say, but although I really like this machine, I wouldn't
recommend it for mission critical applications.
> Exact BIOS revision doesn't seem to matter. Any more suggestions?
Perhaps try to stabilize it with minimal hardware first, then add all
peripherals one by one and adjust the bios for each one.
Good luck,
Willy
next prev parent reply other threads:[~2003-02-02 12:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-02 1:12 Defect (Bug) Report John W. M. Stevens
2003-02-02 9:42 ` Alan Cox
2003-02-02 12:49 ` Erik Mouw
2003-02-02 12:57 ` Willy Tarreau [this message]
2003-02-02 14:21 ` Alan Cox
2003-02-02 13:35 ` Erik Mouw
2003-02-02 14:52 ` Alan Cox
2003-02-02 14:05 ` Jens Axboe
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=20030202125745.GD19346@alpha.home.local \
--to=willy@w.ods.org \
--cc=J.A.K.Mouw@its.tudelft.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=john@betelgeuse.us \
--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