Ubuntu
linux package

irq 20: nobody cared (try booting with the "irqpoll" option)

Bug #545339 reported by Brian J. Murrell
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

While booting the new Lucid kernel on my machine I got the following:

14:56:08 kernel [ 4.652692] irq 20: nobody cared (try booting with the "irqpoll" option)
14:56:08 kernel [ 4.656017] Pid: 212, comm: lvm Not tainted 2.6.32-17-generic #26-Ubuntu
14:56:08 kernel [ 4.656017] Call Trace:
14:56:08 kernel [ 4.656017] [<c0588553>] ? printk+0x1d/0x22
14:56:08 kernel [ 4.656017] [<c01a12fc>] __report_bad_irq+0x2c/0x90
14:56:08 kernel [ 4.656017] [<c019fa34>] ? handle_IRQ_event+0x54/0x150
14:56:08 kernel [ 4.656017] [<c01a14b0>] note_interrupt+0x150/0x190
14:56:08 kernel [ 4.656017] [<c01a1abc>] handle_fasteoi_irq+0xac/0xd0
14:56:08 kernel [ 4.656017] [<c01059ed>] handle_irq+0x1d/0x30
14:56:08 kernel [ 4.656017] [<c058f02c>] do_IRQ+0x4c/0xc0
14:56:08 kernel [ 4.656017] [<c0103a30>] common_interrupt+0x30/0x40
14:56:08 kernel [ 4.656017] [<c01e00d8>] ? bdi_init+0x108/0x160
14:56:08 kernel [ 4.656017] [<c01d47e5>] ? putback_lru_page+0x35/0xe0
14:56:08 kernel [ 4.656017] [<c01e70ef>] munlock_vma_page+0x9f/0xb0
14:56:08 kernel [ 4.656017] [<c01e73f8>] munlock_vma_pages_range+0x68/0xb0
14:56:08 kernel [ 4.656017] [<c01e751e>] mlock_fixup+0xde/0x180
14:56:08 kernel [ 4.656017] [<c01e7631>] do_mlockall+0x71/0x90
14:56:08 kernel [ 4.656017] [<c01e767e>] sys_munlockall+0x2e/0x50
14:56:08 kernel [ 4.656017] [<c01033ec>] syscall_call+0x7/0xb
14:56:08 kernel [ 4.656017] handlers:
14:56:08 kernel [ 4.656017] [<c0375b30>] (acpi_irq+0x0/0x2e)
14:56:08 kernel [ 4.656017] Disabling IRQ #20

# cat /proc/interrupts
           CPU0 CPU1
  0: 81 0 IO-APIC-edge timer
  1: 185 196 IO-APIC-edge i8042
  3: 1 0 IO-APIC-edge serial
  6: 2 0 IO-APIC-edge floppy
  7: 0 0 IO-APIC-edge parport0
  8: 0 0 IO-APIC-edge rtc0
 12: 60 87 IO-APIC-edge i8042
 14: 53 38 IO-APIC-edge ata_piix
 15: 0 0 IO-APIC-edge ata_piix
 16: 19066 18813 IO-APIC-fasteoi pata_pdc2027x
 18: 460759 463845 IO-APIC-fasteoi wcfxo
 19: 15765 15420 IO-APIC-fasteoi uhci_hcd:usb1, aic7xxx, eth0
 20: 99782 100219 IO-APIC-fasteoi acpi
NMI: 0 0 Non-maskable interrupts
LOC: 1033628 107443 Local timer interrupts
SPU: 0 0 Spurious interrupts
PMI: 0 0 Performance monitoring interrupts
PND: 0 0 Performance pending work
RES: 29337 25308 Rescheduling interrupts
CAL: 13116 5632 Function call interrupts
TLB: 506 530 TLB shootdowns
TRM: 0 0 Thermal event interrupts
THR: 0 0 Threshold APIC interrupts
MCE: 0 0 Machine check exceptions
MCP: 4 4 Machine check polls
ERR: 0
MIS: 0

ProblemType: Bug
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory
AplayDevices: aplay: device_list:223: no soundcards found...
Architecture: i386
ArecordDevices: arecord: device_list:223: no soundcards found...
Date: Tue Mar 23 15:06:35 2010
DistroRelease: Ubuntu 10.04
Lsusb:
 Bus 001 Device 003: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
 Bus 001 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: System Manufacturer System Name
Package: linux-image-2.6.32-17-generic 2.6.32-17.26
PciMultimedia:

ProcCmdLine: auto BOOT_IMAGE=lucid console=ttyS0,115200 console=tty0 root=/dev/rootvol/ubuntu_root --debug
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
Regression: Yes
Reproducible: Yes
SourcePackage: linux
TestedUpstream: No
Uname: Linux 2.6.32-17-generic i686
dmi.bios.date: 12/08/00
dmi.bios.vendor: Award Software, Inc.
dmi.bios.version: ASUS P2B-DS ACPI BIOS Revision 1013
dmi.board.name: P2B-DS
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: REV 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 2
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAwardSoftware,Inc.:bvrASUSP2B-DSACPIBIOSRevision1013:bd12/08/00:svnSystemManufacturer:pnSystemName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP2B-DS:rvrREV1.xx:cvnChassisManufacture:ct2:cvrChassisVersion:
dmi.product.name: System Name
dmi.product.version: System Version
dmi.sys.vendor: System Manufacturer

Revision history for this message
Brian J. Murrell (brian-interlinx) wrote :
Surbhi Palande (csurbhi)
Changed in linux (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Ricardo Fernández (koshrf) wrote :

I have this same problem, but it is with IRQ5, 4, 3 and 1.

I had to use "noapic" and it seems it worked, but now suspend doesn't work and I can't check the battery charge.

Lucid 10.04RC1

I don't have a dmesg because IRQ1 is the harddrive controller so it doesn't let write a log with the error, but it is pretty much the same as this bug.

The dmesg I'm sending is the one when it boots with noapic

Jeremy Foshee (jeremyfoshee)
tags: removed: regression-potential
Revision history for this message
penalvch (penalvch) wrote :

Brian J. Murrell, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11.1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

tags: added: latest-bios-1013
Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

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

Other bug subscribers

Remote bug watches

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