From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: <michdaen@iiic.ethz.ch>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Bogus interrupt -1
Date: Fri, 19 Jan 2001 10:50:46 +0100 [thread overview]
Message-ID: <19341214032230.10260@mailhost.mipsys.com> (raw)
In-Reply-To: <3A6775B0.2108F1DE@relog.ch>
>I have tons of messages like this in my logs:
>
>Jan 18 23:06:54 pismo kernel: Bogus interrupt -1 from PC = c00065d0
>
>Anyone knows where these (may) come from?
Which kernel ?
We do get tons of "short" interrupts on the Pismo and the iBook. I don't
know why exactly. I used to filter out the error message, it looks like
someone put it back.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-19 9:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-18 23:01 Bogus interrupt -1 Michel Dänzer
2001-01-19 9:50 ` Benjamin Herrenschmidt [this message]
2001-01-20 2:23 ` Michel Dänzer
-- strict thread matches above, loose matches on Subject: below --
2001-01-20 10:17 Jiri Masik
2001-04-20 16:32 Lars Brinkhoff
2001-04-20 17:13 ` Benjamin Herrenschmidt
2001-04-23 9:52 ` Lars Brinkhoff
2001-04-23 12:18 ` Tony Mantler
2001-04-23 12:24 ` Lars Brinkhoff
2001-04-23 12:47 ` Tony Mantler
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=19341214032230.10260@mailhost.mipsys.com \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=michdaen@iiic.ethz.ch \
/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;
as well as URLs for NNTP newsgroup(s).