public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arkadiusz Miskiewicz <arekm@pld-linux.org>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.24 SMP lockups
Date: Fri, 9 Jan 2004 23:20:19 +0100	[thread overview]
Message-ID: <200401092320.19500.arekm@pld-linux.org> (raw)
In-Reply-To: <20040109210450.GA31404@netnation.com>

On Friday 09 of January 2004 22:04, Simon Kirby wrote:
> 'lo all,
>
> We've had about 6 cases of this now, across 4 separate boxes. 
I had several such cases with 2.4.23 on two separate boxes. First is dual PIII 
1GHz Intel SRMK2 platform - 
http://www.intel.com/support/motherboards/server/srmk2/ with 1,5GB RAM, 
reiserfs as filesystem, scsi disks and Adaptec AIC-7899P U160/m controller.

Second was UP PIII 500MHz machine on some Intel BX mainboard, 256MB RAM, ext3 
as filesystem, software raid 5 on scsi disks using aic7xxx (Adaptec AIC-7892B 
U160/m).

First one was locking up few times per day (pretty big load), second one maybe 
once per day/two (lower load).

Both machines are working _fine_ with 2.4.21 kernel (one was also using 2.4.22 
for some time and no problems occured).

kernels on both machines were exactly the same (just copied) but using 
different modules - kernel was compiled using 2.95.4 (3+some parts from 2.95 
branch of gcc cvs)

> These boxes are all dual CPU, and the failure case shows up suddenly with
> no warning.  Sysreq-P works, but only reports from one CPU no matter how
> many times I try.  In normal operation, every machine distributes all
> IRQs across both CPUs, and Sysreq-P reports from both CPUs.
Similar here - but sometimes even sysrq wasn't working (on second machine).

> Even on boxes with nmi_watchdog=1, nothing is reported from the NMI
> watchdog.
Exactly same here.
append=" console=tty0 console=ttyS0,9600n81 panic=60 nmi_watchdog=1"

I was thinking that maybe that's due to some problem in aic7xxx driver and 
updated it on one machine to latest available version (these in kernel are 
very old) but that didn't help.

> Simon-

-- 
Arkadiusz Miśkiewicz    CS at FoE, Wroclaw University of Technology
arekm.pld-linux.org AM2-6BONE, 1024/3DB19BBD, arekm(at)ircnet, PLD/Linux

  reply	other threads:[~2004-01-09 22:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-09 21:04 2.4.24 SMP lockups Simon Kirby
2004-01-09 22:20 ` Arkadiusz Miskiewicz [this message]
2004-01-10 15:51 ` Thomas Zehetbauer
     [not found] ` <Pine.LNX.4.58L.0401101719400.1310@logos.cnet>
2004-01-10 22:40   ` Andrew Morton
2004-01-11  4:12     ` Rik van Riel
2004-01-11 13:16       ` Marcelo Tosatti
2004-01-12 12:18       ` Marcelo Tosatti
2004-01-12 12:43         ` Thomas Zehetbauer
2004-01-11  8:55     ` Simon Kirby
2004-01-11  9:30       ` Willy Tarreau
2004-01-14 17:07   ` Simon Kirby
2004-01-14 17:56     ` Marcelo Tosatti
2004-01-16  2:34       ` Philippe Troin
2004-01-14 18:28     ` David Woodhouse
2004-01-14 21:01       ` David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2004-01-10 19:58 Marcelo Tosatti
2004-01-11  9:01 ` Simon Kirby
2004-01-14 16:23   ` Marcelo Tosatti
2004-01-15 14:35     ` Thomas Zehetbauer

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=200401092320.19500.arekm@pld-linux.org \
    --to=arekm@pld-linux.org \
    --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