From: "Michel Dänzer" <michel@daenzer.net>
To: linuxppc-dev@lists.linuxppc.org
Subject: Weird interrupt problem
Date: 08 Aug 2002 01:05:17 +0200 [thread overview]
Message-ID: <1028761518.1262.1236.camel@tibook> (raw)
[-- Attachment #1: Type: text/plain, Size: 1269 bytes --]
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?
--
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member / CS student, Free Software enthusiast
[-- Attachment #2: interrupts.BAD --]
[-- Type: text/plain, Size: 735 bytes --]
CPU0
1: 1908 OpenPIC Edge Built-in Sound out
2: 0 OpenPIC Edge Built-in Sound in
19: 132189 OpenPIC Level ide0
20: 51 OpenPIC Level ide1
25: 1557896 OpenPIC Level VIA-PMU
26: 226 OpenPIC Level keywest i2c
27: 33611 OpenPIC Level usb-ohci
28: 108865 OpenPIC Level usb-ohci
41: 1800835 OpenPIC Level eth0
42: 0 OpenPIC Level keywest i2c
47: 398650 OpenPIC Level GPIO1/ADB
55: 0 OpenPIC Edge NMI - XMON
57: 19 OpenPIC Level Airport
61: 1 OpenPIC Edge Headphone detect
BAD: 1
next reply other threads:[~2002-08-07 23:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-07 23:05 Michel Dänzer [this message]
2002-08-07 23:14 ` Weird interrupt problem Michel Dänzer
2002-08-08 0:28 ` Kevin B. Hendricks
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=1028761518.1262.1236.camel@tibook \
--to=michel@daenzer.net \
--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).