From: Ralf Baechle <ralf@uni-koblenz.de>
To: mkloppstech@freenet.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: oops, signal 11
Date: Mon, 22 Jan 2001 06:31:10 -0200 [thread overview]
Message-ID: <20010122063110.C1052@bacchus.dhis.org> (raw)
In-Reply-To: <200101201246.NAA15788@john.epistle>
In-Reply-To: <200101201246.NAA15788@john.epistle>; from mkloppstech@freenet.de on Sat, Jan 20, 2001 at 01:46:50PM +0100
On Sat, Jan 20, 2001 at 01:46:50PM +0100, mkloppstech@freenet.de wrote:
> I know that signal 11 with gcc is a sign of bad hardware; however it
> strikes me that I don't get random oopses - a whole bunch of them is appended.
The compiler tends to hammer harder on the memory than the kernel; this
is a sign of the great effort which was taken to optimize the kernel's
cache usage.
Ralf
-
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/
prev parent reply other threads:[~2001-01-23 3:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-20 12:46 mkloppstech
2001-01-22 8:31 ` Ralf Baechle [this message]
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=20010122063110.C1052@bacchus.dhis.org \
--to=ralf@uni-koblenz.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mkloppstech@freenet.de \
/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
Powered by JetHome