From: Johannes Stezenbach <js@convergence.de>
To: linux-mips@linux-mips.org
Subject: Re: random kernel panics with 2.4.22 running on VR4120A
Date: Tue, 11 Nov 2003 16:45:21 +0100 [thread overview]
Message-ID: <20031111154521.GA11931@convergence.de> (raw)
In-Reply-To: <20031024151325.GB22979@convergence.de>
I wrote:
>
> After the 2.4.22 merge in linux-mips.org CVS I updated our kernel,
> from 2.4.21-2003-07-08 to 2.4.22-2003-09-24, and now we are getting
> occational kernel panics at random places, either one of:
>
> Unhandled kernel unaligned access in unaligned.c::emulate_load_store_insn, line 481:
> Kernel unaligned instruction access in unaligned.c::do_ade, line 550:
>
> It happens about once per day on a box wich continously runs
> a test suite, and rather seldom on other boxes.
I've updated to 2.4.22-2003-10-27, and the test suite ran
for about a week now: The problem seems to be solved.
Johannes
prev parent reply other threads:[~2003-11-11 15:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-24 15:13 random kernel panics with 2.4.22 running on VR4120A Johannes Stezenbach
2003-11-11 15:45 ` Johannes Stezenbach [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=20031111154521.GA11931@convergence.de \
--to=js@convergence.de \
--cc=linux-mips@linux-mips.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