From: ralf@uni-koblenz.de
To: Ariel Faigon <ariel@cthulhu.engr.sgi.com>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: The perennial bus error IRQ :-)
Date: Tue, 13 Jan 1998 02:50:04 +0100 [thread overview]
Message-ID: <19980113025004.46983@uni-koblenz.de> (raw)
In-Reply-To: <199801122148.NAA59443@oz.engr.sgi.com>; from Ariel Faigon on Mon, Jan 12, 1998 at 01:48:46PM -0800
On Mon, Jan 12, 1998 at 01:48:46PM -0800, Ariel Faigon wrote:
> :Going over the linux archives I see over 5 emails
> :[deleted]
>
> Sorry for following up my own message... I realize that
> there can be multiple reasons for this bus error IRQ.
> I just have the feeling some people are hitting bus
> errors that were already fixed just because they are
> using an old precompiled kernel.
I think all the bus errors have been fixed. I also think I know the
reason for the reported ``--UNEXPECTED INTERRUPT'' thing on reboot.
Not tested, though, no time ... Just move the cli() calls in the
functions in arch/mips/sgi/prom/misc.c up before reseting the wd33c93.
Ralf
next prev parent reply other threads:[~1998-01-13 1:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-12 21:30 The perennial bus error IRQ :-) Ariel Faigon
1998-01-12 21:30 ` Ariel Faigon
1998-01-12 21:48 ` Ariel Faigon
1998-01-13 1:50 ` ralf [this message]
1998-01-13 1:45 ` ralf
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=19980113025004.46983@uni-koblenz.de \
--to=ralf@uni-koblenz.de \
--cc=ariel@cthulhu.engr.sgi.com \
--cc=linux@cthulhu.engr.sgi.com \
/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