mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Craig Bradney <cbradney@zip.com.au>
To: Disconnect <lkml@sigkill.net>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [2.4] Nforce2 oops and occasional hang (tried the lockups patch, no difference)
Date: Fri, 19 Dec 2003 21:22:19 +0100	[thread overview]
Message-ID: <1071865339.9969.3.camel@athlonxp.bradney.info> (raw)
In-Reply-To: <1071854664.6110.21.camel@slappy>

On Fri, 2003-12-19 at 18:24, Disconnect wrote:
> On Thu, 2003-12-18 at 13:52, Disconnect wrote:
> > memory/cpu timings.  (Even underclocked it to 133 and 1G with no
> > change.)  So its unfortunately back on a stock 2.4.23-pre9 with
> > noapic/noacpi. (It disables one of the sets of usb ports, as I recall,
> > but it mostly works...)
> 
> Update: Underclocked from 1.8G to 1.2G (whups, meant to go down only
> 2-300mhz) and its been vaguely stable for about 1.5 days.  I don't have
> another week (yet..) to run it under its normal load and wait for a
> crash, so what I'm going to do is:
>  - Move the workload (web/mail/..) to a different machine so this one
> can be down for an extended period
>  - Replace the ram with new sticks (they arrived this morning)
>  - Reclock everything to stock (1.83G cpu, 200mhz ram and verify the
> timings from kingston)
>  - Replace the video card
>  - Memtest86 until it cries
>  - If it passes, bonnie++ on the new drives
>  - If that passes, usb/acpi/apic testing with the associated patches
> 
> Anyone still watching this?  Tips and suggestions on what else might be
> useful/informative are more than welcome.  The tests above mostly
> replicate what I did when building this box, and it passed them then..
> 
> Recap:
>  Epox 8rda+ nforce2 mobo
>  AMD Athlon XP 2500+ (Barton) 1.83G
>  Kingston HyperX PC3200
>  WD Caviar WD1200JB 8M/UDMA100
>  Antec case w/ 350W AMD-certified PSU
> 
> Oopses and occasional hangs, usually in do_generic_file_read, using
> stock kernel.org 2.4.2x kernels.  Hardware passed testing (memtest86,
> bonnie++) before I put Linux on it.

Does this not relate directly to the APIC/IOAPIC issues with 2.6 kernel
and nforce chipset motherboards? 

Craig


  reply	other threads:[~2003-12-19 20:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-13  2:25 Ross Dickson
2003-12-13  5:02 ` Bob
2003-12-15 16:40 ` Disconnect
2003-12-18 18:52   ` Disconnect
2003-12-19 17:24     ` Disconnect
2003-12-19 20:22       ` Craig Bradney [this message]
2003-12-19 20:32         ` Disconnect
2003-12-20 12:30         ` Voicu Liviu
  -- strict thread matches above, loose matches on Subject: below --
2003-12-11 16:16 Disconnect
2003-12-11 16:38 ` Josh McKinney
2003-12-11 17:19   ` Disconnect
2003-12-11 17:22 ` Disconnect

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=1071865339.9969.3.camel@athlonxp.bradney.info \
    --to=cbradney@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@sigkill.net \
    /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

all inboxes | Powered by JetHome®