From: idalton@ferret.phonewave.net
To: linux-kernel@vger.kernel.org
Subject: Re: 2.2.19 locks up on SMP
Date: Sat, 28 Apr 2001 16:09:54 -0700 [thread overview]
Message-ID: <20010428160954.A25712@ferret.phonewave.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0104281402090.2487-100000@age.cs.columbia.edu> <20010429011604.A976@home.ds9a.nl>
In-Reply-To: <20010429011604.A976@home.ds9a.nl>; from ahu@ds9a.nl on Sun, Apr 29, 2001 at 01:16:04AM +0200
On Sun, Apr 29, 2001 at 01:16:04AM +0200, bert hubert wrote:
> On Sat, Apr 28, 2001 at 02:21:29PM -0700, Ion Badulescu wrote:
> > Hi Alan,
> >
> > Over the last week I've tried to upgrade a 4-CPU Xeon box to 2.2.19, but
> > the it keeps locking up whenever the disks are stresses a bit, e.g. when
> > updatedb is running. I get the following messages on the console:
> >
> > wait_on_bh, CPU 1:
> > irq: 1 [1 0]
> > bh: 1 [1 0]
> > <[8010af71]>
>
> Obvious question is, which compiler.
I hadn't seen any locks, but (on a dual Pmmx 200) it started crawling
right after the NIC module (tulip) was loaded. System load decided to
skyrocket.
Yadda... 2.2.19 with devfs patch.
bicycle:~# gcc -v
Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.3/specs
gcc version 2.95.3 20010315 (Debian release)
Might be the same problem.
-- Ferret
next prev parent reply other threads:[~2001-04-28 23:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-28 21:21 Ion Badulescu
2001-04-28 23:16 ` bert hubert
2001-04-28 23:09 ` idalton [this message]
2001-04-28 23:59 ` Tim Moore
2001-04-30 9:22 ` Ion Badulescu
2001-04-30 17:55 ` Alan Cox
2001-04-30 18:15 ` Andrea Arcangeli
2001-04-30 18:28 ` Andrea Arcangeli
2001-04-30 19:57 ` Alan Cox
2001-04-30 19:59 ` Ion Badulescu
2001-04-30 20:28 ` Mohammad A. Haque
2001-05-01 1:09 ` Ion Badulescu
2001-05-01 4:47 ` Ion Badulescu
2001-05-01 7:27 ` Alan Cox
2001-05-01 7:29 ` Ion Badulescu
2001-05-01 7:47 ` Ion Badulescu
2001-05-01 7:55 ` Ion Badulescu
2001-05-01 9:21 ` Ion Badulescu
2001-05-01 12:09 ` Trond Myklebust
2001-05-01 12:15 ` Ion Badulescu
2001-05-01 13:42 ` Trond Myklebust
2001-05-01 23:48 ` Ion Badulescu
2001-07-03 10:11 Scott Nursten
2001-07-03 10:48 ` Scott Nursten
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=20010428160954.A25712@ferret.phonewave.net \
--to=idalton@ferret.phonewave.net \
--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
all inboxes | Powered by JetHome®