On Tue, Mar 03, 2026 at 04:33:56PM +0100, Ramiro Aceves wrote: > [ 1,046744] pci0 at mainbus0 bus 0: configuration mode 1 > [ 1,046744] pci0: i/o space, memory space enabled, rd/line, rd/mult, > wr/inv ok > [ 1,046744] pchb0 at pci0 dev 0 function 0: Intel Pineview Host Bridge > (rev. 0x00) > [ 1,046744] agp0 at pchb0: Pineview chipset > [ 1,046744] agp0: detected 7164k stolen memory > [ 1,046744] agp0: aperture at 0x80000000, size 0x10000000 > [ 1,046744] i915drmkms0 at pci0 dev 2 function 0: Intel Pineview > Integrated Graphics Device (rev. 0x00) > [ 1,046744] Intel Pineview Integrated Graphics Device (miscellaneous > display) at pci0 dev 2 function 1 not configured [..] > [ 4,387451] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). > [ 4,387451] [drm] Driver supports precise vblank timestamp query. > [ 4,396195] i915drmkms0: interrupting at ioapic0 pin 16 (i915drmkms0) > [ 4,427449] [drm] Initialized overlay support. > [ 4,427449] [drm] Initialized i915 1.6.0 20200114 for i915drmkms0 on > minor 0 > [ 4,437453] intelfb0 at i915drmkms0 > [ 4,447454] [drm] DRM_I915_DEBUG enabled > [ 4,447454] [drm] DRM_I915_DEBUG_GEM enabled > [ 4,447454] intelfb0: framebuffer at 0x80009000, size 1024x600, depth 32, > stride 4096 > [ 5,207450] wsdisplay0 at intelfb0 kbdmux 1: console (default, vt100 > emulation), using wskbd0
That looks all good, and i915drmkms has no excuse for being slow. I wonder if this is causing trouble: [ 1,046744] alc0: interrupting at ioapic0 pin 16 Does "vmstat -i" report high interrupt rates for that interrupt? Martin
