Phil Schaffner wrote:
On Fri, 2006-05-26 at 20:26 -0400, anthony baldwin wrote:
At the risk of exposing my ignorance, what can this mean?
Message from syslogd@localhost at Fri May 26 20:20:21 2006 ...
localhost kernel: Disabling IRQ #11
I keep getting these popping up on my screen, only the IRQ # tends to vary.
I´ve never seen this kind of behaviour before.
Perhaps stating the obvious - this is a symptom of an interrupt request
and/or kernel driver problem. Running "tail -f /var/log/messages" in a
root shell console and checking the output after seeing the message, or
doing "dmesg" when it happens should give more info. May be able to
change BIOS settings (such as PNP OS or IRQ assignments - depends on
BIOS), try an older/newer kernel (did it just start happening after an
update?), or change the slots for PCI cards (any recent hardware
changes?).
A google on "Message from syslogd kernel Disabling IRQ" (without the
quotes) will perhaps give some more ideas.
Phil
Well, I´m not even sure if or how much I should be concerned.
I mean, it doesn´t appear to be hindering the functionality of anything
I do or am doing at the time the message appears.
I wondered if it was a security issue or something....
I just did this fresh install of FC5 last weekend, and have done no updates.
As per usual, I´ve spent most of my copious spare time over the past
week reconfiguring stuff to my likeing,
adding software (mostly with yum, some just by DL ing the rpms and
installing myself) that doesn´t come on the install, etc..
But haven´t done a yum update on anything.
I DLed yumex yesterday, and I think it´s choosing to update stuff on
it´s own....Not sure.
I only like using it because it makes it easy to see what´s on the repo
and pick stuff up.
(DLed a bunch of nifty games last night! I didn´t even know they existed
or were available until yumex offered them up.)
Normally I just use yum at the command line, though.
I haven´t seen the msg since last night, so opened up /var/log/msgs in a
text editor and dug around a bit.
I found the message, and am pasting in a bit before and after...
This is the most recent on I received. I know I´ve seen irq #16, and at
least one other number in the past couple of day.
It might be nearly impossible to figure out what I´ve done to affect
this, after all, I´ve done a lot of configuration.
I believe this started only two or three days ago.
Does this shed some light, perhaps? (it´s as good as Chinese to
me...which is not one of the languages I speak):
May 26 20:00:11 localhost gconfd (tony-2386): GConf server is not in
use, shutting down.
May 26 20:00:11 localhost gconfd (tony-2386): Exiting
May 26 20:05:04 localhost kernel: audit(1148688304.267:19): avc:
granted { execstack } for pid=2485 comm="kdesktop_lock"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
May 26 20:05:04 localhost kernel: audit(1148688304.267:20): avc:
granted { execmem } for pid=2485 comm="kdesktop_lock"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
*May 26 20:20:21 localhost kernel: irq 11: nobody cared (try booting
with the "irqpoll" option)
May 26 20:20:21 localhost kernel: [<c01389ab>]
__report_bad_irq+0x2b/0x69 [<c0138b6c>] note_interrupt+0x183/0x1af
May 26 20:20:21 localhost kernel: [<c01384c6>]
handle_IRQ_event+0x23/0x4c [<c0138589>] __do_IRQ+0x9a/0xcd
May 26 20:20:21 localhost kernel: [<c0104bde>] do_IRQ+0x5c/0x77
=======================
May 26 20:20:21 localhost kernel: [<c010358e>] common_interrupt+0x1a/0x20
May 26 20:20:21 localhost kernel: handlers:
May 26 20:20:21 localhost kernel: [<c025b890>] (usb_hcd_irq+0x0/0x4f)
May 26 20:20:21 localhost kernel: [<c025b890>] (usb_hcd_irq+0x0/0x4f)
May 26 20:20:21 localhost kernel: Disabling IRQ #11*
May 26 20:22:57 localhost gconfd (tony-2571): starting (version 2.13.5),
pid 2571 user 'tony'
May 26 20:22:58 localhost gconfd (tony-2571): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only
configuration source at position 0
May 26 20:22:58 localhost gconfd (tony-2571): Resolved address
"xml:readwrite:/home/tony/.gconf" to a writable configuration source at
position 1
May 26 20:22:58 localhost gconfd (tony-2571): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only
configuration source at position 2
May 26 20:23:00 localhost kernel: audit(1148689380.052:21): avc:
granted { execstack } for pid=2561 comm="mozilla-bin"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Any further assistance deeply appreciated.
tony
--
Anthony Baldwin
Translator / Court Qualified Interpreter / Certified English Teacher
http://www.baldwinlinguas.com
English, Français, Español & Português
860-399-7118 / 860-235-8233
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
