[SOLVED] CENTOS 6.4 : kernel:Disabling IRQ #16 and then mouse is drunk

General support questions
Post Reply
avraamjack
Posts: 26
Joined: 2012/06/29 00:22:12
Location: Portsmouth,Va USA

[SOLVED] CENTOS 6.4 : kernel:Disabling IRQ #16 and then mouse is drunk

Post by avraamjack » 2013/03/11 22:51:56

Hi all,

Just upgraded to 6.4 via yum

Twice I have received this message: kernel:Disabling IRQ #16 , showed up on all open terminals and the syslog

Then the mouse is kind of drunk, moves slowly, and blinks in and out, similar to what you might see with very high cpu load

I guess it will probably be fixed shortly but I thought I would mention it.

Avraam Jack Dectis

PS : This showed up in the syslog

-----------------------------------------------------------------------

Mar 11 18:30:27 jack kernel: irq 16: nobody cared (try booting with the "irqpoll" option)
Mar 11 18:30:27 jack kernel: Pid: 0, comm: swapper Not tainted 2.6.32-358.0.1.el6.x86_64 #1
Mar 11 18:30:27 jack kernel: Call Trace:
Mar 11 18:30:27 jack kernel: irq 16: nobody cared (try booting with the "irqpoll" option)
Mar 11 18:30:27 jack kernel: Pid: 0, comm: swapper Not tainted 2.6.32-358.0.1.el6.x86_64 #1
Mar 11 18:30:27 jack kernel: Call Trace:
Mar 11 18:30:27 jack kernel: [] ? __report_bad_irq+0x2b/0xa0
Mar 11 18:30:27 jack kernel: [] ? note_interrupt+0x18c/0x1d0
Mar 11 18:30:27 jack kernel: [] ? handle_fasteoi_irq+0xcd/0xf0
Mar 11 18:30:27 jack kernel: [] ? handle_irq+0x49/0xa0
Mar 11 18:30:27 jack kernel: [] ? do_IRQ+0x6c/0xf0
Mar 11 18:30:27 jack kernel: [] ? ret_from_intr+0x0/0x11
Mar 11 18:30:27 jack kernel: [] ? intel_idle+0xde/0x170
Mar 11 18:30:27 jack kernel: [] ? intel_idle+0xc1/0x170
Mar 11 18:30:27 jack kernel: [] ? cpuidle_idle_call+0xa7/0x140
Mar 11 18:30:27 jack kernel: [] ? cpu_idle+0xb6/0x110
Mar 11 18:30:27 jack kernel: [] ? rest_init+0x7a/0x80
Mar 11 18:30:27 jack kernel: [] ? start_kernel+0x424/0x430
Mar 11 18:30:27 jack kernel: [] ? x86_64_start_reservations+0x125/0x129
Mar 11 18:30:27 jack kernel: [] ? x86_64_start_kernel+0xfa/0x109
Mar 11 18:30:27 jack kernel: handlers:
Mar 11 18:30:27 jack kernel: [] (usb_hcd_irq+0x0/0x90)
Mar 11 18:30:27 jack kernel: [] (ath_isr+0x0/0x260 [ath9k])
Mar 11 18:30:27 jack kernel: Disabling IRQ #16
Mar 11 18:30:27 jack kernel: [] ? __report_bad_irq+0x2b/0xa0
Mar 11 18:30:27 jack kernel: [] ? note_interrupt+0x18c/0x1d0
Mar 11 18:30:27 jack kernel: [] ? handle_fasteoi_irq+0xcd/0xf0
Mar 11 18:30:27 jack kernel: [] ? handle_irq+0x49/0xa0
Mar 11 18:30:27 jack kernel: [] ? do_IRQ+0x6c/0xf0
Mar 11 18:30:27 jack kernel: [] ? ret_from_intr+0x0/0x11
Mar 11 18:30:27 jack kernel: [] ? intel_idle+0xde/0x170
Mar 11 18:30:27 jack kernel: [] ? intel_idle+0xc1/0x170
Mar 11 18:30:27 jack kernel: [] ? cpuidle_idle_call+0xa7/0x140
Mar 11 18:30:27 jack kernel: [] ? cpu_idle+0xb6/0x110
Mar 11 18:30:27 jack kernel: [] ? rest_init+0x7a/0x80
Mar 11 18:30:27 jack kernel: [] ? start_kernel+0x424/0x430
Mar 11 18:30:27 jack kernel: [] ? x86_64_start_reservations+0x125/0Mar 11 18:30:29 jack abrtd: Can't open file '/var/spool/abrt/oops-2013-03-11-18:30:28-3143-1/uid': No such file or directory
Mar 11 18:30:53 jack abrtd: Sending an email...
Mar 11 18:30:53 jack abrtd: Sending an email...
Mar 11 18:30:54 jack sendmail[7627]: r2BMUr9u007627: from=user@localhost, size=913, class=0, nrcpts=1, msgid=, relay=root@localhost
Mar 11 18:30:54 jack sendmail[7628]: r2BMUsY2007628: from=, size=1053, class=0, nrcpts=1, msgid=, proto=ESMTP, daemon=MTA, relay=localhost [127.0.0.1]
Mar 11 18:30:54 jack sendmail[7627]: r2BMUr9u007627: to=root@localhost, delay=00:00:01, xdelay=00:00:00, mailer=relay, pri=30913, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (r2BMUsY2007628 Message accepted for delivery)
Mar 11 18:30:54 jack abrtd: Email was sent to: root@localhost
Mar 11 18:30:54 jack abrtd: Email was sent to: root@localhost
Mar 11 18:30:54 jack abrtd: Duplicate: UUID
Mar 11 18:30:54 jack abrtd: Duplicate: UUID
Mar 11 18:30:54 jack abrtd: DUP_OF_DIR: /var/spool/abrt/oops-2012-12-28-13:13:12-3071-4
Mar 11 18:30:54 jack abrtd: DUP_OF_DIR: /var/spool/abrt/oops-2012-12-28-13:13:12-3071-4
Mar 11 18:30:54 jack abrtd: Corrupted or bad directory '/var/spool/abrt/oops-2013-03-11-18:30:28-3143-1', deleting
Mar 11 18:30:54 jack abrtd: Corrupted or bad directory '/var/spool/abrt/oops-2013-03-11-18:30:28-3143-1', deleting
Mar 11 18:30:55 jack sendmail[7629]: r2BMUsY2007628: to=, delay=00:00:01, xdelay=00:00:01, mailer=local, pri=31222, dsn=2.0.0, stat=Sent
Mar 11 18:40:01 jack CROND[7736]: (root) CMD (/usr/lib64/sa/sa1 1 1)
Mar 11 18:43:07 jack su: pam_unix(su-l:session): session opened for user root by avraam(uid=500)

User avatar
AlanBartlett
Forum Moderator
Posts: 9345
Joined: 2007/10/22 11:30:09
Location: ~/Earth/UK/England/Suffolk
Contact:

[SOLVED] CENTOS 6.4 : kernel:Disabling IRQ #16 and then mo

Post by AlanBartlett » 2013/03/12 01:26:18

The very first line from your system log, shown above, has a suggestion to try --

[quote]
Mar 11 18:30:27 jack kernel: irq 16: nobody cared ([color=0000ff]try booting with the "[b]irqpoll[/b]" option[/color])
[/quote]
Just edit your [b]/etc/grub.conf[/b] file and append [b]irqpoll[/b] to the end of the kernel boot line. Assuming it currently reads --

[code]
[i]blah-blah[/i] rhgb quiet
[/code]
-- then change it to be --

[code]
[i]blah-blah[/i] rhgb quiet [color=0000ff][b]irqpoll[/b][/color]
[/code]
Now reboot the system and see if that has had any effect.

avraamjack
Posts: 26
Joined: 2012/06/29 00:22:12
Location: Portsmouth,Va USA

Re: CENTOS 6.4 : kernel:Disabling IRQ #16 and then mouse is drunk

Post by avraamjack » 2013/03/12 23:05:33

Hi Alan,

Moving my mouse to the USB 3.0 port on my Vostro 470 has cleared up the issue.

I am guessing others will be affected since the Vostro is an Ivy Bridge recent PC.

Hopefully these posts will help them in that case.

Jack

User avatar
AlanBartlett
Forum Moderator
Posts: 9345
Joined: 2007/10/22 11:30:09
Location: ~/Earth/UK/England/Suffolk
Contact:

Re: [SOLVED] CENTOS 6.4 : kernel:Disabling IRQ #16 and then mouse is drunk

Post by AlanBartlett » 2013/03/13 01:25:43

Thank you for reporting back with details of your success.

On your behalf and for posterity, this thread is now marked [SOLVED].

Post Reply