From: Tim Moore <timothymoore@bigfoot.com>
To: idalton@ferret.phonewave.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.2.19 locks up on SMP
Date: Sat, 28 Apr 2001 16:59:37 -0700 [thread overview]
Message-ID: <3AEB5969.6FB678B4@bigfoot.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0104281402090.2487-100000@age.cs.columbia.edu> <20010429011604.A976@home.ds9a.nl> <20010428160954.A25712@ferret.phonewave.net>
> > 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.
Twin Abit BP6's, 2.2.19 + 9-Apr ide patch, no problems.
egcs-2.91.66
tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov
eth0: Lite-On 82c168 PNIC rev 32 at 0xc800, 00:A0:CC:57:89:93, IRQ 16.
--
| 650.390.9613 | 6502247437@messaging.cellone-sf.com
next prev parent reply other threads:[~2001-04-29 0:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-28 21:21 2.2.19 locks up on SMP Ion Badulescu
2001-04-28 23:16 ` bert hubert
2001-04-28 23:09 ` idalton
2001-04-28 23:59 ` Tim Moore [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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=3AEB5969.6FB678B4@bigfoot.com \
--to=timothymoore@bigfoot.com \
--cc=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 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.