Re: new kernel fails to boot due to DRM lock issue (intel)

[Riccardo Mottola <riccardo.mottola%libero.it@localhost>]

Hi,

maya%netbsd.org@localhost wrote:
> Yeah, I've seen this too. BTW, it does work if you disable 'options
> LOCKDEBUG'. not that it's not a bug, but it gives a usable setup.

well, you are saying.. to shut eyes and go straight :)

Anyway.. I tried disabling i815drmkms and the kernel boots and X runs 
(although in vesa mode). That's good, it means at least that the issue 
is video only.

Then I updated sources, noticed that there were some commits and now it 
doesn't lock anymore! I do get several errors which remains in dmesg though:

First:
[    1.000502] acpivga0 at acpi0 (GFX0): ACPI Display Adapter
[    1.000502] acpiout0 at acpivga0 (DD01, 0x0100): ACPI Display Output 
Device
[    1.000502] acpiout1 at acpivga0 (DD02, 0x0400): ACPI Display Output 
Device
[    1.000502] acpiout1: brightness levels: 
[0,5,10,15,20,25,30,33,36,40,43,46,50,55,60,65,70,75,80,83,86,90,93,96,100]
[    1.000502] acpiout2 at acpivga0 (DD03, 0x0200): ACPI Display Output 
Device
[    1.000502] acpiout3 at acpivga0 (DD04, 0x0300): ACPI Display Output 
Device
[    1.000502] acpiout4 at acpivga0 (DD05, 0x0005): ACPI Display Output 
Device
[    1.000502] acpivga0: autoconfiguration error: unknown output device 
acpiout0
[    1.000502] acpivga0: autoconfiguration error: unknown output device 
acpiout2
[    1.000502] acpivga0: autoconfiguration error: unknown output device 
acpiout3
[    1.000502] acpivga0: autoconfiguration error: unknown output device 
acpiout4
[    1.000502] acpivga0: connected output devices:
[    1.000502] acpivga0:   0x0400 (acpiout1): Unknown Output Device, head 0


then:
[    6.059118] i915drmkms0: interrupting at ioapic0 pin 16 (i915drmkms0)
[    6.099140] ral0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
[    6.099140] ral0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 
12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
[    6.489346] warning: 
/usr/src/sys/external/bsd/drm2/dist/drm/drm_irq.c:1510: vblank wait 
timed out on crtc 0
[    6.549377] kern error: 
[drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_fifo_underrun.c:363)intel_cpu_fifo_underrun_irq_handler] 
*ERROR* CPU pipe A FIFO underrun
[    6.649430] warning: 
/usr/src/sys/external/bsd/drm2/dist/drm/drm_irq.c:1510: vblank wait 
timed out on crtc 0
[    6.749483] warning: 
/usr/src/sys/external/bsd/drm2/dist/drm/drm_irq.c:1510: vblank wait 
timed out on crtc 0
[    6.799509] intelfb0 at i915drmkms0
[    6.799509] intelfb0: framebuffer at 0xffffc88066fd0000, size 
1366x768, depth 32, stride 5504
[    7.850064] wsdisplay0 at intelfb0 kbdmux 1: console (default, vt100 
emulation), using wskbd0
[    7.850064] wsmux1: connecting to wsdisplay0
[    7.880080] init: copying out path `/sbin/init' 11
[   12.002258] wsdisplay0: screen 1 added (default, vt100 emulation)
[   12.012267] wsdisplay0: screen 2 added (default, vt100 emulation)
[   12.012267] wsdisplay0: screen 3 added (default, vt100 emulation)
[   12.012267] wsdisplay0: screen 4 added (default, vt100 emulation)
[   16.904847] kern error: 
[drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_fifo_underrun.c:363)intel_cpu_fifo_underrun_irq_handler] 
*ERROR* CPU pipe A FIFO underrun


the CPU pipe looks much worse than the ACPI stuff :)

Riccardo