mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Nick Urbanik <nicku@vtc.edu.hk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Debugging hard lockups (hardware?)
Date: 06 Apr 2003 19:34:09 +0100	[thread overview]
Message-ID: <1049654048.1600.11.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <3E8FC9FB.A030ACFB@vtc.edu.hk>

On Sul, 2003-04-06 at 07:32, Nick Urbanik wrote:
> This machine locks up solid every few days.  Caps Lock, Num Lock, Scroll Lock do
> not respond.  The NMI watchdog does not kick in.

For the NMI watchdog to fail (if you have it enabled) requires pretty
major disaster to have occurred since the NMI will be delivered through
any kind of system hang

> I guess hardware.  But memtest run exhaustively shows no problem.

Memory errors normally generate "Oops" type lines rather than other
stuff

> I have six 80 G IDE disks, software RAID, LVM on top.  On Red Hat 8.0 and 9.
> 
> Any hints on how to troubleshoot this (besides replacing motherboard and other
> components I cannot afford to replace?)

Is your PSU up to scratch for six disks ?

> /dev/md3:
>  Timing buffer-cache reads:   128 MB in  0.35 seconds =365.71 MB/sec
>  Timing buffered disk reads:  64 MB in 21.93 seconds =  2.92 MB/sec
> (last horribly. slow; get zillions of lines in syslog saying stuff like:
> Apr  6 14:08:50 nicksbox kernel: raid5: switching cache buffer size, 0 --> 4096
> Apr  6 14:08:50 nicksbox kernel: raid5: switching cache buffer size, 0 --> 1024
> Apr  6 14:08:50 nicksbox kernel: raid5: switching cache buffer size, 1024 -->

Im not sure what this one indicates actually

> Any pointers to web sites, information that may help, any hints, suggestions,
> ideas,... all most welcome.  Actually, if replacing the motherboard would fix
> it, I'd do it, but I cannot guess why it should help; Asus motherboards have
> always been good to me before.

Your choice of components looks fine, its all stuff I trust, even if the
ethernet card is not good for performance it ought to be fine in
general. If it is a faulty part most likely its a one off fault.

Which bits of the system are not being used (sound, video, network ?)


  parent reply	other threads:[~2003-04-06 19:21 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-06  6:32 Nick Urbanik
2003-04-06  6:39 ` Nick Urbanik
2003-04-06  9:27 ` John Bradford
2003-04-06 10:55 ` Bruce Harada
2003-04-06 18:34 ` Alan Cox [this message]
2003-04-06 20:29   ` Arador
2003-04-06 21:04     ` Alan Cox
2003-04-17 16:12       ` Arador
2003-04-06 20:31   ` Dave Jones
2003-04-06 22:02     ` Nick Urbanik
2003-04-06 23:15       ` Dave Jones
2003-04-08  3:33     ` Andre Hedrick
2003-04-08 12:35       ` Dave Jones
2003-09-15  8:49   ` Debugging hard lockups (hardware?): Power Supply! Nick Urbanik
2003-09-15 19:57     ` Resident Boxholder
2003-04-06 10:12 Debugging hard lockups (hardware?) mikpe
2003-04-06 16:01 ` Nick Urbanik
2003-04-07 23:24 Richard J Moore
2003-04-09  1:24 ` Nick Urbanik
2003-04-08 18:36 Scott Lee
2003-04-11 18:08 Scott Lee
2003-04-11 19:22 ` Bernd Eckenfels

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=1049654048.1600.11.camel@dhcp22.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicku@vtc.edu.hk \
    /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®