From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Lars Brinkhoff <lars@nocrew.org>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Bogus interrupt -1
Date: Fri, 20 Apr 2001 19:13:27 +0200 [thread overview]
Message-ID: <20010420171327.26883@mailhost.mipsys.com> (raw)
In-Reply-To: <85itjzilbx.fsf@junk.nocrew.org>
>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.
Did you enable distribution of IRQs to all CPUs ?
I don't think it's completely safe yet.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-04-20 17:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-20 16:32 Bogus interrupt -1 Lars Brinkhoff
2001-04-20 17:13 ` Benjamin Herrenschmidt [this message]
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=20010420171327.26883@mailhost.mipsys.com \
--to=benh@kernel.crashing.org \
--cc=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 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.