Disabling IRQ #19, irqfixup code broken

Bug #993425 reported by Silviu C.
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

WORKAROUND: Disable firewire or blacklist firewire_ohci .

[39703.205343] irq 19: nobody cared (try booting with the "irqpoll" option)
[39703.205350] Pid: 0, comm: swapper/1 Tainted: P C O 3.2.0-24-generic #37-Ubuntu
[39703.205352] Call Trace:
[39703.205355] <IRQ> [<ffffffff810db37d>] __report_bad_irq+0x3d/0xe0
[39703.205367] [<ffffffff810db605>] note_interrupt+0x135/0x190
[39703.205371] [<ffffffff810d8e69>] handle_irq_event_percpu+0xa9/0x220
[39703.205375] [<ffffffff810d9031>] handle_irq_event+0x51/0x80
[39703.205379] [<ffffffff810dc05a>] handle_fasteoi_irq+0x6a/0x110
[39703.205384] [<ffffffff81015282>] handle_irq+0x22/0x40
[39703.205389] [<ffffffff8166759a>] do_IRQ+0x5a/0xe0
[39703.205394] [<ffffffff8165c92e>] common_interrupt+0x6e/0x6e
[39703.205396] <EOI> [<ffffffff8108e329>] ? enqueue_hrtimer+0x39/0xc0
[39703.205405] [<ffffffff8136b42d>] ? intel_idle+0xed/0x150
[39703.205408] [<ffffffff8136b40f>] ? intel_idle+0xcf/0x150
[39703.205413] [<ffffffff81504a01>] cpuidle_idle_call+0xc1/0x280
[39703.205417] [<ffffffff8101222a>] cpu_idle+0xca/0x120
[39703.205422] [<ffffffff8163a7fa>] start_secondary+0xd9/0xdb
[39703.205424] handlers:
[39703.205428] [<ffffffff81465f70>] ata_bmdma_interrupt
[39703.205443] [<ffffffffa006e370>] irq_handler
[39703.205446] Disabling IRQ #19

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-generic 3.2.0.24.26
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: silviu 2044 F.... pulseaudio
 /dev/snd/pcmC0D0p: silviu 2044 F...m pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xfb500000 irq 59'
   Mixer name : 'Realtek ALC892'
   Components : 'HDA:10ec0892,1043841b,00100302'
   Controls : 43
   Simple ctrls : 20
Date: Wed May 2 20:35:11 2012
HibernationDevice: RESUME=UUID=95018fd9-2d30-4d41-abf1-e925fe91c88e
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-24-generic root=UUID=30aa33df-cc67-449b-83d8-bbc33f2a3e36 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-24-generic N/A
 linux-backports-modules-3.2.0-24-generic N/A
 linux-firmware 1.79
RfKill:

SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1104
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8P67 LE
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0X
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1104:bd10/27/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8P67LE:rvrRevX.0X:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Silviu C. (silviucc) wrote :
Revision history for this message
Silviu C. (silviucc) wrote :

I keep getting that in my syslog. Does not look that good.

Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

IRQ 19 from lspci:

06:03.0 FireWire (IEEE 1394) [0c00]: VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller [1106:3044] (rev c0) (prog-if 10 [OHCI])
 Subsystem: ASUSTeK Computer Inc. M4A series motherboard [1043:81fe]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 32 (8000ns max), Cache Line Size: 64 bytes
 Interrupt: pin A routed to IRQ 19
 Region 0: Memory at fb300000 (32-bit, non-prefetchable) [size=2K]
 Region 1: I/O ports at c000 [size=128]
 Capabilities: <access denied>
 Kernel driver in use: firewire_ohci
 Kernel modules: firewire-ohci

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Can you try booting with the "irqpoll" option to see if the message goes away?

tags: added: kernel-da-key
Revision history for this message
Silviu C. (silviucc) wrote :

Did not boot with irqpoll option because of possible performance issues, but I do not see it in the log after disabling the onboard firewire controller - don't use firewire anyway.

Revision history for this message
Jeroen Van den Keybus (jeroen-vandenkeybus) wrote :

The Asus P8P67 uses the ASM1083 PCIe-PCI bridge, which seems to be involved in this issue. As a workaround I'm currently using a vanilla 3.2.16 kernel with the patch on https://lkml.org/lkml/2012/4/30/141.

Revision history for this message
Leo Trubach (leotrubach) wrote :

Hello! I had the problem when i installed geforce 210. My mouse pointer started to move with lag and some kestrokes didn't get registered when i typed quickly. After adding irqpoll option it was resolved/

Revision history for this message
Johan Andersson (jna-jna) wrote :
Download full text (4.6 KiB)

It seems this is a recurring issue, see #855199. The problem is that the irqfixup code gets broken. There is of course an underlying problem of spurious interrupts but booting with the irqpoll option should handle this. It worked for awhile but seem to have reoccured from at least kernel 3.2.0-39 in precise, possibly earlier.

I am now running quantal 3.5.0-27 and the problem remains. If the wrong IRQ gets disabled the system gets sluggish and needs rebooting. It is extremely frustrating. I am running an AMD Fusion board:
 Example dmesg output:
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.5.0-27-generic root=UUID=fc511922-937e-4b41-a891-3667495fa66e ro irqpoll irqfixup
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.5.0-27-generic root=UUID=fc511922-937e-4b41-a891-3667495fa66e ro irqpoll irqfixup
....
[37805.735959] irq 16: nobody cared (try booting with the "irqpoll" option)
[37805.737619] Pid: 2457, comm: kvm Not tainted 3.5.0-27-generic #46-Ubuntu
[37805.737623] Call Trace:
[37805.737627] <IRQ> [<ffffffff810e1a6d>] __report_bad_irq+0x3d/0xe0
[37805.737646] [<ffffffff810e1f32>] note_interrupt+0x1c2/0x210
[37805.737665] [<ffffffffa059b0d2>] ? __nf_conntrack_alloc+0x72/0x2f0 [nf_conntrack]
[37805.737673] [<ffffffff810df6d7>] handle_irq_event_percpu+0xa7/0x1f0
[37805.737683] [<ffffffffa059b0d2>] ? __nf_conntrack_alloc+0x72/0x2f0 [nf_conntrack]
[37805.737689] [<ffffffff810df86e>] handle_irq_event+0x4e/0x80
[37805.737694] [<ffffffff810e2a6a>] handle_fasteoi_irq+0x5a/0x100
[37805.737701] [<ffffffff81015082>] handle_irq+0x22/0x40
[37805.737708] [<ffffffff8168b6ca>] do_IRQ+0x5a/0xe0
[37805.737716] [<ffffffff81681c6a>] common_interrupt+0x6a/0x6a
[37805.737724] [<ffffffff8116e484>] ? kmem_cache_alloc+0x64/0x130
[37805.737733] [<ffffffffa059b0d2>] __nf_conntrack_alloc+0x72/0x2f0 [nf_conntrack]
[37805.737742] [<ffffffffa059b877>] nf_conntrack_in+0x527/0x8b0 [nf_conntrack]
[37805.737751] [<ffffffffa05af421>] ipv4_conntrack_in+0x21/0x30 [nf_conntrack_ipv4]
[37805.737757] [<ffffffff8159c3a4>] nf_iterate+0x84/0xb0
[37805.737775] [<ffffffffa04b1870>] ? br_nf_pre_routing_finish_ipv6+0x140/0x140 [bridge]
[37805.737780] [<ffffffff8159c444>] nf_hook_slow+0x74/0x130
[37805.737790] [<ffffffffa04b1870>] ? br_nf_pre_routing_finish_ipv6+0x140/0x140 [bridge]
[37805.737799] [<ffffffffa04abe70>] ? br_handle_local_finish+0x50/0x50 [bridge]
[37805.737810] [<ffffffffa04b2a58>] br_nf_pre_routing+0x5b8/0x670 [bridge]
[37805.737815] [<ffffffff8159c3a4>] nf_iterate+0x84/0xb0
[37805.737824] [<ffffffffa04abe70>] ? br_handle_local_finish+0x50/0x50 [bridge]
[37805.737829] [<ffffffff8159c444>] nf_hook_slow+0x74/0x130
[37805.737837] [<ffffffffa04abe70>] ? br_handle_local_finish+0x50/0x50 [bridge]
[37805.737847] [<ffffffffa04ac2c8>] br_handle_frame+0x1c8/0x260 [bridge]
[37805.737853] [<ffffffff81681c6a>] ? common_interrupt+0x6a/0x6a
[37805.737861] [<ffffffffa04ac100>] ? br_handle_frame_finish+0x290/0x290 [bridge]
[37805.737868] [<ffffffff81570caa>] __netif_receive_skb+0x43a/0x620
[37805.737873] [<ffffffff81571053>] netif_receive_skb+0x23/0x90
[37805.737878] [<ffffffff815714ac>] ? dev_gro_receive+0x1...

Read more...

summary: - Disabling IRQ #19
+ Disabling IRQ #19, irqfixup code broken
Revision history for this message
penalvch (penalvch) wrote :

Silviu C., this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, 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>

If reproducible, could you also please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. 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.13-rc5

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: bios-outdated-3703 needs-upstream-testing
description: updated
Changed in linux (Ubuntu):
importance: Medium → Low
status: Confirmed → 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.

Other bug subscribers

Remote bug watches

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