From: Ralf Baechle <ralf@oss.sgi.com>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: Sanjay Jain <sjain@Sanera.net>, linux-mips@oss.sgi.com
Subject: Re: unhandled kernel unaligned access
Date: Wed, 6 Mar 2002 22:16:48 +0100 [thread overview]
Message-ID: <20020306221648.A17128@dea.linux-mips.net> (raw)
In-Reply-To: <3C867007.FB94B0D@mips.com>; from kevink@mips.com on Wed, Mar 06, 2002 at 11:37:44AM -0800
On Wed, Mar 06, 2002 at 11:37:44AM -0800, Kevin D. Kissell wrote:
> Which sources are you using? Up until pretty recently,
> there was a bug in unaligned.c which could cause this.
> I don't know when it was fixed at SGI, but the fix
> is in the 2.4.19-pre2 sources at kernel.org.
2.4.19-pre2 has most of the oss.sgi.com code as of about a week ago.
Ralf
prev parent reply other threads:[~2002-03-06 22:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-05 14:14 boot different kernels on the indy ?! Andrea Venturi
2002-03-05 23:25 ` Florian Lohoff
2002-03-06 5:24 ` Ladislav Michl
2002-03-06 9:47 ` Florian Lohoff
2002-03-06 19:26 ` unhandled kernel unaligned access Sanjay Jain
2002-03-06 19:26 ` Sanjay Jain
2002-03-06 19:37 ` Kevin D. Kissell
2002-03-06 21:16 ` 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=20020306221648.A17128@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=kevink@mips.com \
--cc=linux-mips@oss.sgi.com \
--cc=sjain@Sanera.net \
/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