All of lore.kernel.org
 help / color / mirror / Atom feed
From: grendel@thanes.org (Grendel)
To: Matt Bernstein <mb/lkml@dcs.qmul.ac.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: GA-7DX+ crashes
Date: Wed, 14 Aug 2002 14:49:40 +0200	[thread overview]
Message-ID: <20020814124940.GB1824@thanes.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0208141239380.1472-100000@r2-pc.dcs.qmul.ac.uk>

[-- Attachment #1: Type: text/plain, Size: 1876 bytes --]

On Wed, Aug 14, 2002 at 01:12:43PM +0100, Matt Bernstein scribbled:
> Hi,
> 
> We're very much at a loss as to why the 60 new PCs we've bought largely
> don't run Linux (various 2.4 kernels including 2.4.19, limbo1-BOOT) for
[snip]
> Has anyone else had success or failure stories in particular with this 
> motherboard? We don't really have a significant number of data points just 
> yet, but are willing to try pretty much anything anyone might suggest!
> 
> Matt
> 
> symptoms
> - random data corruption (sometimes memory, more often HDD)
> - somtimes oopsing, but never in the same place
> 
> what we think we've ascertained so far
> - they pass memtest86
> - we've tried different HDDs, no effect
> - tried ide=nodma, possibly makes it crash after longer
> - tried noapic, no effect
> - tried all sorts of BIOS settings, no effect (except--possibly--turning 
> 	off the on board IDE controller and playing nfsroot games)
> - ..and yet they seem to run that other OS fine :-(
> - extra cooling/underclocking doesn't seem to help
> - seems to be fs-independent (tried ext3, reiserfs, jfs)
I've had very similar (actually identical) problems with the ASUS A7V333
mobo. The mobo is completely VIA-based (both north and south) but the
southbridge seems to be much the same. What I did to make the machine run
stable was to - turn the USB2 support off (by hardware, a solder point on
the mobo) and short the solder point which is responsible for the CPU
functional settings data readout (the ROMSIP setting) to read the data from
a BIOS table instead of from the CPU itself. That seemed to have been enough
for me - now the mobo is stable (I'm gonna get rid of it, though...).

Another thing you might check is the CPU voltage - make sure it is the
standard 3.3 and not 3.5 as some manufacturers set it.

hope that helps a bit,

marek

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2002-08-14 12:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-14 12:12 GA-7DX+ crashes Matt Bernstein
2002-08-14 12:35 ` Alan Cox
2002-08-16 12:17   ` Matt Bernstein
2002-08-14 12:49 ` Grendel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-08-14 17:08 Alex Davis
2002-08-14 18:41 Mikael Pettersson

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=20020814124940.GB1824@thanes.org \
    --to=grendel@thanes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mb/lkml@dcs.qmul.ac.uk \
    /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.