NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: kern/56608: i915drmkms0: info: [drm] Cannot find any crtc or sizes



The following reply was made to PR kern/56608; it has been noted by GNATS.

From: Patrick Welche <prlw1%talktalk.net@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/56608: i915drmkms0: info: [drm] Cannot find any crtc or
 sizes
Date: Thu, 26 May 2022 12:30:34 +0100

 On Thu, Jan 06, 2022 at 03:45:00PM +0000, prlw1%cam.ac.uk@localhost wrote:
 > >Description:
 > An old Ivy Bridge box seems unhappy with the new drm code, complaining that:
 > 
 > kern info: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
 > kern info: [drm] Driver supports precise vblank timestamp query.
 > i915drmkms0: interrupting at msi4 vec 0 (i915drmkms0)
 > kern info: [drm] Initialized i915 1.6.0 20200114 for i915drmkms0 on minor 0
 > i915drmkms0: info: [drm] Cannot find any crtc or sizes
 > kern info: [drm] DRM_I915_DEBUG enabled
 > kern info: [drm] DRM_I915_DEBUG_GEM enabled
 > i915drmkms0: info: [drm] Cannot find any crtc or sizes
 > 
 > 
 > Before the change, with a 9.99.2 kernel of 30 November:
 > 
 > kern info: [drm] Memory usable by graphics device = 2048M
 > kern info: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
 > kern info: [drm] Driver supports precise vblank timestamp query.
 > kern info: [drm] failed to find VBIOS tables
 > i915drmkms0: interrupting at msi4 vec 0 (i915drmkms0)
 > intelfb0 at i915drmkms0
 > intelfb0: framebuffer at 0xe0064000, size 1280x1024, depth 32, stride 5120
 > kern error: [drm:(../../../../external/bsd/drm2/dist/drm/i915/intel_fifo_underrun.c:229)cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder A
 > kern error: [drm:(../../../../external/bsd/drm2/dist/drm/i915/intel_fifo_underrun.c:380)intel_pch_fifo_underrun_irq_handler] *ERROR* PCH transcoder A FIFO underrun
 > kern error: [drm:(../../../../external/bsd/drm2/dist/drm/i915/intel_fifo_underrun.c:175)ivybridge_set_fifo_underrun_reporting] *ERROR* uncleared fifo underrun on pipe A
 > kern error: [drm:(../../../../external/bsd/drm2/dist/drm/i915/intel_fifo_underrun.c:362)intel_cpu_fifo_underrun_irq_handler] *ERROR* CPU pipe A FIFO underrun
 > wsdisplay0 at intelfb0 kbdmux 1
 
 With yesterday's 9.99.97 the lack of crtc/sizes error is gone!
 
 kern info: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
 kern info: [drm] Driver supports precise vblank timestamp query.
 i915drmkms0: interrupting at msi4 vec 0 (i915drmkms0)
 kern info: [drm] Initialized i915 1.6.0 20200114 for i915drmkms0 on minor 0
 intelfb0 at i915drmkms0
 kern info: [drm] DRM_I915_DEBUG enabled
 kern info: [drm] DRM_I915_DEBUG_GEM enabled
 intelfb0: framebuffer at 0xe0005000, size 1280x1024, depth 32, stride 5120
 {drm:netbsd:intel_set_cpu_fifo_underrun_reporting+0x29c} *ERROR* uncleared fifo underrun on pipe A
 {drm:netbsd:intel_cpu_fifo_underrun_irq_handler+0x5c} *ERROR* CPU pipe A FIFO underrun
 {drm:netbsd:intel_set_pch_fifo_underrun_reporting+0x14e} *ERROR* uncleared pch fifo underrun on pch transcoder A
 {drm:netbsd:cpt_irq_handler+0x1dd} *ERROR* PCH transcoder A FIFO underrun
 
 (I have a blank screen though, whereas I used to have an xdm prompt. I have
 a vague recollection that using a serial console could cause this. This
 is with installboot option com0kbd, and I tried without the serial cable
 but that might not have been enough, or it is a red herring.)
 


Home | Main Index | Thread Index | Old Index