irq 20: nobody cared

Bug #1578552 reported by Ivan Kurnosov
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Hi, I'm running ubuntu 16.04 (since january) and relatively recently (after another kernel upgrade during alpha-beta stage) I've started experience problems with the mouse (it's a radio-powered one). After checking the syslog that is what I've found:

May 5 16:39:03 lyu-ubuntu kernel: [11999.623139] irq 20: nobody cared (try booting with the "irqpoll" option)
May 5 16:39:03 lyu-ubuntu kernel: [11999.623157] CPU: 1 PID: 0 Comm: swapper/1 Tainted: P OE 4.4.0-21-generic #37-Ubuntu
May 5 16:39:03 lyu-ubuntu kernel: [11999.623159] Hardware name: ASUSTeK Computer Inc. K50IN /K50IN , BIOS 222 01/22/2010
May 5 16:39:03 lyu-ubuntu kernel: [11999.623163] 0000000000000086 87c743a25af182af ffff8800bfa83cf8 ffffffff813e93c3
May 5 16:39:03 lyu-ubuntu kernel: [11999.623168] ffff8800b57abe00 ffff8800b57abeb4 ffff8800bfa83d20 ffffffff810dd3a3
May 5 16:39:03 lyu-ubuntu kernel: [11999.623171] ffff8800b57abe00 0000000000000000 0000000000000014 ffff8800bfa83d58
May 5 16:39:03 lyu-ubuntu kernel: [11999.623176] Call Trace:
May 5 16:39:03 lyu-ubuntu kernel: [11999.623178] <IRQ> [<ffffffff813e93c3>] dump_stack+0x63/0x90
May 5 16:39:03 lyu-ubuntu kernel: [11999.623192] [<ffffffff810dd3a3>] __report_bad_irq+0x33/0xc0
May 5 16:39:03 lyu-ubuntu kernel: [11999.623196] [<ffffffff810dd737>] note_interrupt+0x247/0x290
May 5 16:39:03 lyu-ubuntu kernel: [11999.623199] [<ffffffff810da9c7>] handle_irq_event_percpu+0x167/0x1d0
May 5 16:39:03 lyu-ubuntu kernel: [11999.623202] [<ffffffff810daa6e>] handle_irq_event+0x3e/0x60
May 5 16:39:03 lyu-ubuntu kernel: [11999.623206] [<ffffffff810ddca6>] handle_fasteoi_irq+0x96/0x150
May 5 16:39:03 lyu-ubuntu kernel: [11999.623211] [<ffffffff8103115a>] handle_irq+0x1a/0x30
May 5 16:39:03 lyu-ubuntu kernel: [11999.623215] [<ffffffff81826edb>] do_IRQ+0x4b/0xd0
May 5 16:39:03 lyu-ubuntu kernel: [11999.623220] [<ffffffff81824fc2>] common_interrupt+0x82/0x82
May 5 16:39:03 lyu-ubuntu kernel: [11999.623439] [<ffffffffc1411c50>] ? _nv013458rm+0x30/0x30 [nvidia]
May 5 16:39:03 lyu-ubuntu kernel: [11999.623446] [<ffffffff8108591e>] ? __do_softirq+0x7e/0x290
May 5 16:39:03 lyu-ubuntu kernel: [11999.623450] [<ffffffff81085ca3>] irq_exit+0xa3/0xb0
May 5 16:39:03 lyu-ubuntu kernel: [11999.623454] [<ffffffff81826ee4>] do_IRQ+0x54/0xd0
May 5 16:39:03 lyu-ubuntu kernel: [11999.623458] [<ffffffff81824fc2>] common_interrupt+0x82/0x82
May 5 16:39:03 lyu-ubuntu kernel: [11999.623460] <EOI> [<ffffffff816bb9ee>] ? cpuidle_enter_state+0x10e/0x2b0
May 5 16:39:03 lyu-ubuntu kernel: [11999.623468] [<ffffffff816bbbc7>] cpuidle_enter+0x17/0x20
May 5 16:39:03 lyu-ubuntu kernel: [11999.623473] [<ffffffff810c3d52>] call_cpuidle+0x32/0x60
May 5 16:39:03 lyu-ubuntu kernel: [11999.623476] [<ffffffff816bbba3>] ? cpuidle_select+0x13/0x20
May 5 16:39:03 lyu-ubuntu kernel: [11999.623480] [<ffffffff810c4010>] cpu_startup_entry+0x290/0x350
May 5 16:39:03 lyu-ubuntu kernel: [11999.623485] [<ffffffff810516f4>] start_secondary+0x154/0x190
May 5 16:39:03 lyu-ubuntu kernel: [11999.623487] handlers:
May 5 16:39:03 lyu-ubuntu kernel: [11999.623492] [<ffffffff8160c440>] usb_hcd_irq
May 5 16:39:03 lyu-ubuntu kernel: [11999.623495] Disabling IRQ #20

The currently running kernel version is 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
---
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: lyulyu 1730 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=9cae2df7-f2e2-4b1e-9abc-c7a72011d3f8
InstallationDate: Installed on 2016-02-23 (71 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
Lsusb:
 Bus 001 Device 003: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC Webcam / CNF7129
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: ASUSTeK Computer Inc. K50IN
NonfreeKernelModules: nvidia_uvm nvidia
Package: linux (not installed)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=4a825d1e-bfce-46f1-ae82-565557acdab2 ro quiet splash
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-21-generic N/A
 linux-backports-modules-4.4.0-21-generic N/A
 linux-firmware 1.157
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: xenial
Uname: Linux 4.4.0-21-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm lpadmin sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 222
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K50IN
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr222:bd01/22/2010:svnASUSTeKComputerInc.:pnK50IN:pvr1.0:rvnASUSTeKComputerInc.:rnK50IN:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
dmi.product.name: K50IN
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1578552

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Ivan Kurnosov (zerkms) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected xenial
description: updated
Revision history for this message
Ivan Kurnosov (zerkms) wrote : CRDA.txt

apport information

Revision history for this message
Ivan Kurnosov (zerkms) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Ivan Kurnosov (zerkms) wrote : IwConfig.txt

apport information

Revision history for this message
Ivan Kurnosov (zerkms) wrote : JournalErrors.txt

apport information

Revision history for this message
Ivan Kurnosov (zerkms) wrote : Lspci.txt

apport information

Revision history for this message
Ivan Kurnosov (zerkms) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Ivan Kurnosov (zerkms) wrote : ProcEnviron.txt

apport information

Revision history for this message
Ivan Kurnosov (zerkms) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Ivan Kurnosov (zerkms) wrote : ProcModules.txt

apport information

Revision history for this message
Ivan Kurnosov (zerkms) wrote : PulseList.txt

apport information

Revision history for this message
Ivan Kurnosov (zerkms) wrote : UdevDb.txt

apport information

Revision history for this message
Ivan Kurnosov (zerkms) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Does the issue go away if you boot into the previous kernel?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.6 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc6-wily/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Ivan Kurnosov (zerkms) wrote :

> Does the issue go away if you boot into the previous kernel?

I'm not sure the other kernel is available (I mean if it was not autoremoved - I just keep 3 latest)

Yep, I'll try the latest available, thanks

penalvch (penalvch)
tags: added: bios-outdated-223
Revision history for this message
Ivan Kurnosov (zerkms) wrote :

My apologies that I did not send it before, but seems like just another upgrade solved it.

Changed in linux (Ubuntu):
status: Incomplete → Fix Released
status: Fix Released → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.