From: Michel Dänzer <daenzer@relog.ch>
To: linuxppc-dev@lists.linuxppc.org
Subject: Bogus interrupt -1
Date: Fri, 19 Jan 2001 00:01:04 +0100 [thread overview]
Message-ID: <3A6775B0.2108F1DE@relog.ch> (raw)
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?
Michel
--
Earthling Michel Dänzer (MrCooper) \ Debian GNU/Linux (powerpc) developer
CS student, Free Software enthusiast \ XFree86 and DRI project member
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-01-18 23:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-18 23:01 Michel Dänzer [this message]
2001-01-19 9:50 ` Bogus interrupt -1 Benjamin Herrenschmidt
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=3A6775B0.2108F1DE@relog.ch \
--to=daenzer@relog.ch \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.