[Bug 190186] [patch] i915 driver: enable opregion handling

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190186

jan.kokemueller at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jan.kokemueller at gmail.com

--- Comment #15 from jan.kokemueller at gmail.com ---
When I test the new i915 code (r270990 snapshot iso or backported to 10-stable,
doesn't matter) on my gen4 Intel GPU (GMA 4500MHD), I'm getting reproducible
interrupt storms from "irq16: uhci0" after loading the i915kms module. It does
not matter if I start X or not. This looks very similar to the situation here:

https://lists.freebsd.org/pipermail/freebsd-hackers/2014-June/045369.html

Setting hw.drm.msi=0 in /boot/loader.conf doesn't help. One suspend/resume
cycle makes the problem go away. When I revert commit r270516 (the opregion
changes) the problem goes away, too. Then there is no irq16 at all in the
output of "vmstat -i".

Some more info:

$ grep 'irq 16' /var/run/dmesg.boot
vgapci0: <VGA-compatible display> port 0x1800-0x1807 mem
0xf2400000-0xf27fffff,0xd0000000-0xdfffffff irq 16 at device 2.0 on pci0
uhci0: <Intel 82801I (ICH9) USB controller> port 0x1820-0x183f irq 16 at device
26.0 on pci0
sdhci_pci0: <JMicron JMB38X SD> mem 0xf2300400-0xf23004ff irq 16 at device 0.2
on pci2
pcib2: <ACPI PCI-PCI bridge> irq 16 at device 28.1 on pci0
pcib6: <ACPI PCI-PCI bridge> irq 16 at device 28.5 on pci0


pciconf -lvc for vgapci0:

vgapci0 at pci0:0:2:0:     class=0x030000 card=0x213a17aa chip=0x2a428086 rev=0x07
hdr=0x00
    vendor     = 'Intel Corporation'
    device     = 'Mobile 4 Series Chipset Integrated Graphics Controller'
    class      = display
    subclass   = VGA
    cap 05[90] = MSI supports 1 message enabled with 1 message
    cap 01[d0] = powerspec 3  supports D0 D3  current D0


Should I open a new bug? Can somebody reproduce? Let me know if you need more
logs.

-- 
You are receiving this mail because:
You are the assignee for the bug.