From: "Jeff V. Merkey" <jmerkey@timpanogas.org>
To: Andi Kleen <ak@suse.de>
Cc: Rainer Mager <rmager@vgkk.com>, linux-kernel@vger.kernel.org
Subject: Re: Signal 11
Date: Thu, 07 Dec 2000 18:24:34 -0700 [thread overview]
Message-ID: <3A303852.790E3CE4@timpanogas.org> (raw)
In-Reply-To: <E144BOL-0003Eg-00@the-village.bc.nu> <NEBBJBCAFMMNIHGDLFKGMEFHCIAA.rmager@vgkk.com> <20001208022044.A6417@gruyere.muc.suse.de>
Andi,
It's related to some change in 2.4 vs. 2.2. There are other programs
affected other than X, SSH also get's spurious signal 11's now and again
with 2.4 and glibc <= 2.1 and it does not occur on 2.2.
Jeff
Andi Kleen wrote:
>
> On Fri, Dec 08, 2000 at 09:44:29AM +0900, Rainer Mager wrote:
> > I recently upgraded to a new machine. It is running RedHat 6.2 Linux (with
> > a SMP 2.4.0test[8-11] kernel) and has a Matrox G400 in it. X is 4.0.1.
> > Anyway, about once every 2-3 days X will spontaneously die and the only info
> > I get back is that it was because of signal 11.
> > I've heard that signal 11 can be related to bad hardware, most often
> > memory, but I've done a good bit of testing on this and the system seems ok.
> > What I did was to run the VA Linux Cerberos(sp?) test for 15 hours+ with no
> > errors. Actually this only worked when running from the console. When
> > running from X the machine locked up (although no signal 11).
> > The only info I've gotten back from the XFree86 mailing lists so far is
> > that there are known and wide spread problems with SMP and these types of
> > problems. Can anyone comment on this? Are there known SMP problems? What is
> > the current resolution plan?
>
> signal 11 just means that the program crashed with a segmentation fault.
>
> Sounds like a X Server bug. You should probably contact XFree86, not
> linux-kernel
>
> -Andi
> -
> 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 2:00 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 [this message]
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
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=3A303852.790E3CE4@timpanogas.org \
--to=jmerkey@timpanogas.org \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--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).