From: "Kevin B. Hendricks" <kevin.hendricks@sympatico.ca>
To: "Michel Dänzer" <michel@daenzer.net>, linuxppc-dev@lists.linuxppc.org
Subject: Re: Weird interrupt problem
Date: Wed, 7 Aug 2002 20:28:01 -0400 [thread overview]
Message-ID: <200208072028.01216.kevin.hendricks@sympatico.ca> (raw)
In-Reply-To: <1028761518.1262.1236.camel@tibook>
Hi,
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.
Kevin
On August 7, 2002 07:05, Michel Dänzer wrote:
> Today this happened to me the second time: All of a sudden, the USB
> mouse stopped working. At the same time this appeared in the syslog:
>
> Aug 7 17:19:57 tibook kernel: Unhandled interrupt 1d, disabled
>
> Plugging the mouse to the other socket worked, but it wouldn't work
> again in the original one. As you can see in the attached
> /proc/interrupts, interrupt 29 (=1d) is unknown. Interestingly,
> interrupt 28 seems to be for the USB socket which stopped working (I
> think it was the same one when the first problem first occured, might be
> coincidence though). Was it somehow rewarded for its 100'000th
> occurence? ;) Seriously, is it possible that the number changed somehow?
>
>
> This wouldn't be all that bad, if the whole system wasn't very sluggish
> afterwards. When it occured the first time, I had CONFIG_TAU enabled in
> the kernel, which Ben said might cause the sluggishness at least. But
> now it's disabled.
>
>
> This is on a TiBook III/667 running 2.4.18-ben0-lotsanicestuff if it
> matters. The first occurence was with 2.4.19-presomething-ben0.
>
>
> Has anyone experienced anything similar?
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-08-08 0:28 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 [this message]
2002-08-08 11:04 ` Michel Dänzer
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=200208072028.01216.kevin.hendricks@sympatico.ca \
--to=kevin.hendricks@sympatico.ca \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=michel@daenzer.net \
/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).