Bug 472161 - IRQ #16 disabled after turning on compositing on KDE 4.1
Summary: IRQ #16 disabled after turning on compositing on KDE 4.1
Keywords:
Status: CLOSED DUPLICATE of bug 471162
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 10
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: ---
Assignee: Dave Airlie
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-11-19 03:43 UTC by Edney Matias
Modified: 2008-12-05 16:12 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-12-04 17:04:58 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Edney Matias 2008-11-19 03:43:18 UTC
Description of problem: Whenever i try to activate compositing on KDE 4.1 i receive a message from syslog saying that irq #16 was disabled. After that, screen updates only occurs after I move my mouse. Indeed it's seems computer processing stops and only resume after i move my mouse, generating interruptions. I think it's related to 3D acceleration 'cause if i use wine to run War Craft with '-opengl' option i also get the same effect. In game i have to move my mouse to resume playing.


Version-Release number of selected component (if applicable): This problem started on kernel 2.6.27.5-101. I also noticed it on 2.6.27.5-109 and 2.6.27.5-113. Today updates removed my last kernel which used to work without problems. I don't annotated the version :(, i use to update regularly, if you take the version right before 2.6.27.5-101, maybe that's the one that used to work here. Besides this I'm running:

xorg-x11-server-Xorg-1.5.3-5.fc10.x86_64;
xorg-x11-drv-i810-2.5.0-3.fc10.x86_64;
mesa-dri-drivers-7.2-0.13.fc10.x86_64
mesa-libGLU-7.2-0.13.fc10.i386
mesa-libGL-7.2-0.13.fc10.x86_64
mesa-libGLU-7.2-0.13.fc10.x86_64
mesa-libGL-7.2-0.13.fc10.i386


How reproducible: It's seems related to 3D acceleration, so use any any 3D application or try to activate compositing and bam! IRQ #16 is disabled and system start to work only when input interruptions (mouse and keyboard) are generated. I have only kde 4.1 so can't test on gnome, maybe it's related to kwin.



Steps to Reproduce:
1. Enable desktop effect or run 'wine warIII.exe -opengl'
2. Get message saying IRQ #16 was disabled
3. Use you mouse or the keyboard to keep the computer working
  
Actual results: The computer freezes while no interruption is generated.


Expected results: I suspect i should be able to run the game or activate the desktop effects without problems.

Additional info: 
# cat /proc/interrupts

           CPU0       CPU1
  0:    1292704    1178067   IO-APIC-edge      timer
  1:       5067       1163   IO-APIC-edge      i8042
  8:          0          1   IO-APIC-edge      rtc0
  9:          1          3   IO-APIC-fasteoi   acpi
 12:      47276     345187   IO-APIC-edge      i8042
 14:      22396      22272   IO-APIC-edge      ata_piix
 15:          0          0   IO-APIC-edge      ata_piix
 16:    3405635    3394366   IO-APIC-fasteoi   i915@pci:0000:00:02.0
 17:      15572     145509   IO-APIC-fasteoi   ahci, eth0, iwl3945
 18:       7951        114   IO-APIC-fasteoi   mmc0
 19:         55         13   IO-APIC-fasteoi   firewire_ohci
 20:       4375      20724   IO-APIC-fasteoi   ehci_hcd:usb2, uhci_hcd:usb3, uhci_hcd:usb5
 21:       2625        148   IO-APIC-fasteoi   uhci_hcd:usb4, uhci_hcd:usb6, HDA Intel
 22:          0          0   IO-APIC-fasteoi   ehci_hcd:usb1, uhci_hcd:usb7
NMI:          0          0   Non-maskable interrupts
LOC:    1302608    1571956   Local timer interrupts
RES:     673359     534204   Rescheduling interrupts
CAL:        460       6863   function call interrupts
TLB:        923        723   TLB shootdowns
TRM:          0          0   Thermal event interrupts
THR:          0          0   Threshold APIC interrupts
SPU:          0          0   Spurious interrupts
ERR:          0

# tail -f -n20 /var/log/messages

Nov 19 00:49:53 r2d2 kernel: usb 5-1: USB disconnect, address 2
Nov 19 01:02:08 r2d2 kernel: irq 16: nobody cared (try booting with the "irqpoll" option)
Nov 19 01:02:08 r2d2 kernel: Pid: 0, comm: swapper Not tainted 2.6.27.5-113.fc10.x86_64 #1
Nov 19 01:02:08 r2d2 kernel:
Nov 19 01:02:08 r2d2 kernel: Call Trace:
Nov 19 01:02:08 r2d2 kernel: <IRQ>  [<ffffffff8108320f>] __report_bad_irq+0x38/0x7c
Nov 19 01:02:08 r2d2 kernel: [<ffffffff8108345b>] note_interrupt+0x208/0x26d
Nov 19 01:02:08 r2d2 kernel: [<ffffffff81083b88>] handle_fasteoi_irq+0xbb/0xeb
Nov 19 01:02:08 r2d2 kernel: [<ffffffff8101309e>] do_IRQ+0xf7/0x169
Nov 19 01:02:08 r2d2 kernel: [<ffffffff81010933>] ret_from_intr+0x0/0x2e
Nov 19 01:02:08 r2d2 kernel: <EOI>  [<ffffffff811bcc5a>] ? acpi_idle_enter_simple+0x175/0x1b4
Nov 19 01:02:08 r2d2 kernel: [<ffffffff811bcc52>] ? acpi_idle_enter_simple+0x16d/0x1b4
Nov 19 01:02:08 r2d2 kernel: [<ffffffff81286063>] ? cpuidle_idle_call+0x95/0xc9
Nov 19 01:02:08 r2d2 kernel: [<ffffffff8100f279>] ? cpu_idle+0xb2/0x10b
Nov 19 01:02:08 r2d2 kernel: [<ffffffff8131f33d>] ? rest_init+0x61/0x63
Nov 19 01:02:08 r2d2 kernel:
Nov 19 01:02:08 r2d2 kernel: handlers:
Nov 19 01:02:08 r2d2 kernel: [<ffffffffa03a246f>] (i915_driver_irq_handler+0x0/0x199 [i915])
Nov 19 01:02:08 r2d2 kernel: Disabling IRQ #16
Nov 19 01:17:52 r2d2 kernel: CE: hpet increasing min_delta_ns to 22500 nsec

Maybe it's relate to the first line of the previous block. The one stating that an USB device was disconnected. I didn't disconnected anything from my notebook, anyway here is the output of lsusb:

# lsusb

Bus 002 Device 003: ID 05a9:2640 OmniVision Technologies, Inc.       
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub       
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub       
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

That device is a embedded webcam. I already noted the sometimes the webcam led blinks as something was probing something. The webcam doesn't work on kopete or flash player for example. Indeed i don't have any program installed that correctly uses my webcam.

Don't know what else i can provide, but if you ask, i will.

Comment 1 Bug Zapper 2008-11-26 05:35:38 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Thorsten Leemhuis 2008-12-04 17:04:58 UTC

*** This bug has been marked as a duplicate of bug 471162 ***

Comment 3 Mace Moneta 2008-12-04 17:26:04 UTC
How is an open bug being marked as a duplicate of a closed bug, if the problem
is still existing?

Comment 4 Thorsten Leemhuis 2008-12-04 17:34:16 UTC
(In reply to comment #3)
> How is an open bug being marked as a duplicate of a closed bug, if the problem
> is still existing?

Sorry, if this one still exists and is different then please reopen it. It looked quite identical to the other one, hence I marked it as dupe. I apologize if this was wrong. But a small hint: You should update the bug frequently if it's still happening with current kernels -- the kernel you mentioned in the initial report is outdated.

Comment 5 Edney Matias 2008-12-05 16:12:04 UTC
Hi!

Just to let you know, I'm running kernel version 2.6.27.5-117 and the problem seems to vanished away. Don't know if it was corrected but doesn't bore me anymore.

Thank you.


Note You need to log in before you can comment on or make changes to this bug.