From: "Michel Dänzer" <michel@daenzer.net>
To: "Kevin B. Hendricks" <kevin.hendricks@sympatico.ca>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Weird interrupt problem
Date: 08 Aug 2002 13:04:29 +0200 [thread overview]
Message-ID: <1028804670.1109.1318.camel@tibook> (raw)
In-Reply-To: <200208072028.01216.kevin.hendricks@sympatico.ca>
On Thu, 2002-08-08 at 02:28, Kevin B. Hendricks wrote:
>
> Twice now I have seen something that may be related. The whole system
> becomes very sluggish with either one or both cpus consuming 99% of
> capacity while receiving funny interrupt messages.
>
> I literally had to shutdown the system which took forever (I had to keep
> hitting <return> to allow the second cpu to have a chance at things).
>
> This is with an almost stock ben 2.4.19-pre10 kernel compiled for SMP on a
> Dual G4 1-gig machine. I have never seen anything in the message logs
> that provides a good hint at why this is happening.
>
> Again it has only happended twice now but it is very annoying (the system
> becomes so sluggish you almost think it has hung completely).
>
> I have no idea if this is related but it may be.
I'm not sure, as this really seems to be related to USB, the CPU isn't
hogged and while the system is very jerky, it still runs at about half
the normal speed. No problem shutting down.
--
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member / CS student, Free Software enthusiast
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-08-08 11:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-07 23:05 Weird interrupt problem Michel Dänzer
2002-08-07 23:14 ` Michel Dänzer
2002-08-08 0:28 ` Kevin B. Hendricks
2002-08-08 11:04 ` Michel Dänzer [this message]
2002-08-08 12:07 ` Benjamin Herrenschmidt
2002-08-10 8:45 ` Anton Blanchard
2002-08-16 17:01 ` 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=1028804670.1109.1318.camel@tibook \
--to=michel@daenzer.net \
--cc=kevin.hendricks@sympatico.ca \
--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).