From: "Kaj-Michael Lang" <milang@tal.org>
To: "Linux Kernel List" <linux-kernel@vger.kernel.org>
Subject: Raid code panic with kernel compiled for i486
Date: Tue, 9 Jan 2001 19:59:28 +0200 [thread overview]
Message-ID: <001401c07a65$e9c41040$56dc10c3@tal.org> (raw)
I was testing the 2.4.0 kernel and found out that when a kernel
compiled for processors under P3 (i486, P2/Celeron) and booting it on a P3
the kernel
panics when it's tries to test different RAID5 xor algorithms.
The panic looks something like this:
...
raid5: measuring checksuming speed
8regs : 773.430 MB/sec
32regs : 562.356 MB/sec
invalid operand: 0000
CPU: 0
EIP: 0010:[<c0259c7d>]
...
I've tried with:
2.4.0, gcc 2.95.2
2.4.0-ac4, gcc 2.95.2
2.4.0 SMP, gcc 2.95.2
2.4.0 UP, egcs 1.1.2
Kaj-Michael Lang
milang@tal.org
-
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:[~2001-01-09 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 17:59 Kaj-Michael Lang [this message]
2001-01-09 18:25 ` Raid code panic with kernel compiled for i486 Brian Gerst
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='001401c07a65$e9c41040$56dc10c3@tal.org' \
--to=milang@tal.org \
--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