From: davej@suse.de
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Signal 11
Date: Sat, 9 Dec 2000 05:32:54 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.21.0012090527490.9650-100000@neo.local> (raw)
David Woodhouse (dwmw2@infradead.org) wrote...
> Can you reproduce it with bcrl's patch below:
Did nothing for me. gcc still got a sig11 after a while.
Took three runs of 'make bzImage' before it completed.
I wondered if I'd been unlucky enough to have been sent a
replacement K6-2 which was also screwed, but as I mentioned
earlier, this box runs fine under 2.2
btw, I was unsubscribed from all lists at vger yesterday,
for reasons currently unknown to me. Did this happen to anyone
else, or did my mail setup break something?
regards,
Davej.
--
| Dave Jones <davej@suse.de> http://www.suse.de/~davej
| SuSE Labs
-
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 reply other threads:[~2000-12-09 6:03 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-09 5:32 davej [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-14 12:42 Signal 11 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
2000-12-08 0:27 Linux 2.2.18pre25 Alan Cox
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 0:58 ` 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-11 14:14 ` 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
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=Pine.LNX.4.21.0012090527490.9650-100000@neo.local \
--to=davej@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).