From: Brian Gerst <bgerst@didntduck.org>
To: Kaj-Michael Lang <milang@tal.org>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Raid code panic with kernel compiled for i486
Date: Tue, 09 Jan 2001 13:25:03 -0500 [thread overview]
Message-ID: <3A5B577F.DB1726B7@didntduck.org> (raw)
In-Reply-To: <001401c07a65$e9c41040$56dc10c3@tal.org>
Kaj-Michael Lang wrote:
>
> 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>]
> ...
>
Try 2.4.1-pre1. It's choking because SSE hasn't been enabled since it's
compiled for a 486.
--
Brian Gerst
-
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-09 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 17:59 Raid code panic with kernel compiled for i486 Kaj-Michael Lang
2001-01-09 18:25 ` Brian Gerst [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=3A5B577F.DB1726B7@didntduck.org \
--to=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=milang@tal.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