From: Lars Brinkhoff <lars@nocrew.org>
To: linuxppc-dev@lists.linuxppc.org
Subject: Bogus interrupt -1
Date: 20 Apr 2001 18:32:02 +0200 [thread overview]
Message-ID: <85itjzilbx.fsf@junk.nocrew.org> (raw)
I got these messages from benh's 2.4.4-pre1 running SMP:
Bogus interrupt -1 from PC = c000781c
Bogus interrupt -1 from PC = c0017ba4
Bogus interrupt -1 from PC = c0024c90
Bogus interrupt -1 from PC = c0017ba4
Bogus interrupt -1 from PC = c0017c34
Bogus interrupt -1 from PC = c0017ba4
Bogus interrupt -1 from PC = c0006e38
Bogus interrupt -1 from PC = c0006e38
Bogus interrupt -1 from PC = c0006e38
Bogus interrupt -1 from PC = c0006e38
Bogus interrupt -1 from PC = c0006e38
Bogus interrupt -1 from PC = c0006e38
According to my System.map:
c0006e38 = _nmask_and_or_msr + 0x10
c000781c = _switch_to + 0x184
c0017ba4 = schedule + 0x1084
c0017c34 = schedule + 0x1228
c0024c90 = del_timer_sync + 0x184
At first, the first six or so messages appeared, but everything seemed
fine. Later, the last messages appeared, and it seemed like one of
the two processors in my 2001 Dual G4 had wedged. According to "top",
there was always at least 50% idle time.
--
http://lars.nocrew.org/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-04-20 16:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-20 16:32 Lars Brinkhoff [this message]
2001-04-20 17:13 ` Bogus interrupt -1 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
2001-05-12 18:18 ` Success? Both CPUs running (Was: Bogus interrupt -1) Lars Brinkhoff
2001-05-12 18:25 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2001-01-20 10:17 Bogus interrupt -1 Jiri Masik
2001-01-18 23:01 Michel Dänzer
2001-01-19 9:50 ` Benjamin Herrenschmidt
2001-01-20 2:23 ` Michel Dänzer
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=85itjzilbx.fsf@junk.nocrew.org \
--to=lars@nocrew.org \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).