From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: Mark Vojkovich <mvojkovich@valinux.com>
Cc: David Woodhouse <dwmw2@infradead.org>, Andi Kleen <ak@suse.de>,
Rainer Mager <rmager@vgkk.com>,
linux-kernel@vger.kernel.org
Subject: Re: Signal 11
Date: Fri, 8 Dec 2000 16:16:45 -0700 [thread overview]
Message-ID: <20001208161645.A6075@vger.timpanogas.org> (raw)
In-Reply-To: <25692.976268767@redhat.com> <Pine.LNX.4.30.0012081129140.6704-100000@beefcake.hdqt.valinux.com>
In-Reply-To: <Pine.LNX.4.30.0012081129140.6704-100000@beefcake.hdqt.valinux.com>; from mvojkovich@valinux.com on Fri, Dec 08, 2000 at 11:34:51AM -0800
On Fri, Dec 08, 2000 at 11:34:51AM -0800, Mark Vojkovich wrote:
>
>
> On Fri, 8 Dec 2000, David Woodhouse wrote:
>
> Some additional data points. It goes away on UP 2.4 kernels.
> Also, I can't recall seeing this problem on IA64. Maybe it's still
> there on IA64 and I just haven't been trying hard enough to crash
> it, but my current impression is that the problem doesn't exist on IA64.
>
> Hmmm... IA64 is a static server. I don't hear of people having
> problems on 3.3.6 servers either. I'm wondering if a non-loader
> 4.0 server would have problems on IA32 with a 2.4 kernel. That's
> something for people to try.
>
>
> Mark.
I have not seen it on UP systems either. I only see it on SMP systems.
After trying very hard last night, I was able to get my 4 x PPro system to
do it with 2.4.0-12. It seems related to loading in some way. If you
have more than two processors, the loading is less since there's more
processors, and for whatever reason, it makes it harder to produce
whatever race condition is causing it. I can get it to happen
pretty easily on a 2 x PII system.
:-)
Jeff
>
> >
> > --
> > dwmw2
> >
> > ¹ And the BP6 still falls over less frequently than the dual P3 I use at
> > work.
> > ² RH7. Don't start.
> >
> >
> >
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-08 22:52 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-07 20:03 Linux 2.2.18pre25 Alan Cox
2000-12-07 23:23 ` Miquel van Smoorenburg
2000-12-07 23:41 ` Alan Cox
2000-12-08 9:47 ` Willy Tarreau
2000-12-08 14:08 ` Alan Cox
2000-12-08 16:07 ` Miquel van Smoorenburg
2000-12-08 17:08 ` Alan Cox
2000-12-08 18:12 ` Philipp Rumpf
2000-12-08 0:20 ` Andrea Arcangeli
2000-12-08 0:27 ` Alan Cox
2000-12-08 0:41 ` Andrea Arcangeli
2000-12-08 0:47 ` Alan Cox
2000-12-08 1:27 ` Linus Torvalds
2000-12-08 0:44 ` Signal 11 Rainer Mager
2000-12-08 1:05 ` Jeff V. Merkey
2000-12-08 1:09 ` Michel LESPINASSE
2000-12-08 2:14 ` Rainer Mager
2000-12-08 1:20 ` Andi Kleen
2000-12-08 1:24 ` Jeff V. Merkey
2000-12-08 1:40 ` Andi Kleen
2000-12-08 1:43 ` Jeff V. Merkey
2000-12-08 1:55 ` Jeff V. Merkey
2000-12-08 19:20 ` Dr. Kelsey Hudson
2000-12-08 2:28 ` davej
2000-12-08 3:13 ` Jeff V. Merkey
2000-12-08 3:25 ` davej
2000-12-08 16:44 ` Matthew Vanecek
2000-12-08 19:43 ` Dr. Kelsey Hudson
2000-12-08 13:52 ` Alan Cox
2000-12-15 0:11 ` lamont
2000-12-08 1:58 ` Richard B. Johnson
2000-12-08 2:04 ` Peter Samuelson
2000-12-08 16:36 ` Matthew Vanecek
2000-12-08 16:49 ` Richard B. Johnson
2000-12-08 17:40 ` Peter Samuelson
2000-12-08 19:36 ` Dr. Kelsey Hudson
2000-12-08 9:46 ` David Woodhouse
2000-12-08 14:06 ` Alan Cox
2000-12-09 19:01 ` Matthew Vanecek
2000-12-09 19:20 ` davej
2000-12-09 23:31 ` Matthew Vanecek
2000-12-11 1:31 ` OOPS when using 4GB memory setting Rainer Mager
2000-12-11 0:58 ` Signal 11 Rainer Mager
2000-12-11 9:05 ` Rainer Mager
2000-12-11 13:33 ` Mike Galbraith
2000-12-11 23:24 ` Rainer Mager
2000-12-13 0:22 ` Signal 11 - the continuing saga Rainer Mager
2000-12-13 2:17 ` Jeff V. Merkey
2000-12-13 1:45 ` Rainer Mager
2000-12-13 4:29 ` Mike Galbraith
2000-12-13 9:34 ` Rainer Mager
2000-12-13 15:40 ` Mike Galbraith
2000-12-13 3:17 ` Linus Torvalds
2000-12-13 9:34 ` Rainer Mager
2000-12-13 17:43 ` Jeff V. Merkey
2000-12-13 12:10 ` R: " CMA
2000-12-11 14:14 ` Signal 11 davej
2000-12-08 16:21 ` Horst von Brand
2000-12-08 19:34 ` Mark Vojkovich
2000-12-08 23:16 ` Jeff V. Merkey [this message]
2000-12-08 22:24 ` David Woodhouse
2000-12-09 0:56 ` Jeff V. Merkey
2000-12-08 17:02 ` Linux 2.2.18pre25 Martin Kacer
2000-12-08 17:20 ` Alan Cox
2000-12-08 17:36 ` Martin Kacer
2000-12-08 18:08 ` Andrea Arcangeli
2000-12-08 18:30 ` Martin Kacer
2000-12-08 23:55 ` Alan Cox
2000-12-09 5:32 Signal 11 davej
2000-12-14 12:42 Clayton Weaver
2000-12-14 19:11 ` Linus Torvalds
2000-12-14 22:35 ` Alan Cox
2000-12-14 22:45 ` Linus Torvalds
2000-12-14 22:58 ` Bernhard Rosenkraenzer
2000-12-14 23:11 ` Linus Torvalds
2000-12-15 0:10 ` Miquel van Smoorenburg
2000-12-15 0:32 ` Alan Cox
2000-12-15 0:42 ` Miquel van Smoorenburg
2000-12-15 2:07 ` Michael Peddemors
2000-12-15 1:09 ` Alan Cox
2000-12-15 16:12 ` Theodore Y. Ts'o
2000-12-14 23:24 ` Alan Cox
2000-12-14 23:35 ` Jakub Jelinek
2000-12-14 23:51 ` Linus Torvalds
2000-12-15 0:11 ` Dan Egli
2000-12-14 22:46 ` Jakub Jelinek
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=20001208161645.A6075@vger.timpanogas.org \
--to=jmerkey@vger.timpanogas.org \
--cc=ak@suse.de \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mvojkovich@valinux.com \
--cc=rmager@vgkk.com \
/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;
as well as URLs for NNTP newsgroup(s).