From: Emmanuel Fleury <fleury@cs.auc.dk>
To: linux-kernel@vger.kernel.org
Subject: spurious 8259A interrupt
Date: Tue, 16 Mar 2004 19:35:55 +0100 [thread overview]
Message-ID: <1079462154.24676.29.camel@rade7.s.cs.auc.dk> (raw)
Hi,
I noticed today that I had several "spurious 8259A interrupt":
Dec 20 15:02:45 hermes vmunix: spurious 8259<3>[drm:radeon_cp_init]
*ERROR* radeon_cp_init called without lock held
...
Dec 20 16:54:17 hermes vmunix: spurious 8259A interrupt: IRQ7.
...
Jan 3 11:29:06 hermes vmunix: spurious 8259A interrupt: I<6>cs: memory
probe 0xa0000000-0xa0ffffff: clean.
...
Feb 29 12:59:39 hermes vmunix: spurious 8259A in<4>atkbd.c: Keyboard on
isa0060/serio0 reports too many keys pressed.
...
Mar 1 00:03:12 hermes vmunix: spurious 8259A interrupt:
I<3>[drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held
...
Mar 8 03:11:24 hermes vmunix: spurious 8259A interrupt:
I<7>orinoco_lock() called with hw_unavailable (dev=d5a80000)
After some Googling, I found out this:
http://test.linuxfromscratch.org/faq/#spurious-8259A-interrupt
So, I know it is no harm. But, it is possibly due to a device driver
which is not properly doing its job. Can somebody tell me how to correct
this bug (without have the work around of tingling klogd).
Regards
--
Emmanuel Fleury
Computer Science Department, | Office: B1-201
Aalborg University, | Phone: +45 96 35 72 23
Fredriks Bajersvej 7E, | Fax: +45 98 15 98 89
9220 Aalborg East, Denmark | Email: fleury@cs.auc.dk
next reply other threads:[~2004-03-16 18:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-16 18:35 Emmanuel Fleury [this message]
2004-03-16 20:32 Robert_Hentosh
2004-03-19 13:06 ` Jamie Lokier
2004-03-19 13:16 ` Russell King
2004-03-19 13:39 ` Jamie Lokier
2004-03-19 14:04 ` Anton Blanchard
2004-03-19 14:56 ` Jamie Lokier
2004-03-19 13:48 ` Richard B. Johnson
2004-03-19 14:39 ` Jamie Lokier
2004-03-21 17:58 ` Hans-Peter Jansen
2004-03-22 9:12 ` Maciej W. Rozycki
2004-03-22 12:29 ` Richard B. Johnson
2004-03-24 15:28 ` Jamie Lokier
2004-03-24 15:50 ` Gabriel Paubert
2004-03-24 15:57 ` Richard B. Johnson
2004-03-19 13:28 ` Maciej W. Rozycki
2004-03-19 22:01 ` Guennadi Liakhovetski
2004-03-22 9:02 ` Maciej W. Rozycki
2004-03-22 21:16 ` Guennadi Liakhovetski
2004-03-22 22:13 ` Richard B. Johnson
2004-03-22 23:09 ` Guennadi Liakhovetski
2004-03-22 23:38 ` Richard B. Johnson
2004-03-23 10:32 ` Maciej W. Rozycki
2004-03-23 10:42 ` Maciej W. Rozycki
2004-03-23 21:10 ` Guennadi Liakhovetski
2004-03-23 10:29 ` Maciej W. Rozycki
2004-03-23 10:26 ` Maciej W. Rozycki
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=1079462154.24676.29.camel@rade7.s.cs.auc.dk \
--to=fleury@cs.auc.dk \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome