|Summary:||[drm:i915_driver_load] *ERROR* failed to init modeset, EINVAL|
|Product:||Drivers||Reporter:||Ferenc Wágner (wferi)|
|Component:||Video(DRI - Intel)||Assignee:||drivers_video-dri-intel (drivers_video-dri-intel)|
|Severity:||normal||CC:||chris, florian, maciej.rutecki, rjw|
|Bug Depends on:|
dmesg after modprobe i915 modeset=1 (with no modules loaded beforehand)
dmesg with drm.debug=0xf under 2.6.38-rc3
lspci under 2.6.38-rc3
Where does it go wrong?
dmesg with drm.debug=0xf under 2.6.38-rc3 with the WARN patch applied
full lspci output
Only bind to function 0
Description Ferenc Wágner 2011-02-01 15:18:39 UTC
Created attachment 45792 [details] dmesg after modprobe i915 modeset=1 (with no modules loaded beforehand) Under 2.6.37, modprobe i915 modeset=1 switched to 128x48 all right. Under 2.6.38-rc3, it garbles the screen: there's an irregularly blinking narrow rectangle spanning the full height of the screen in the column of the cursor. The machine otherwise works. The wastly overheight cursor advances on each keypress but no single letter is visible on the screen, apart from some faint broken lines flying away during heavy scrolling. Full dmesg attached, but it ends with: [ 13.585039] i915 0000:00:02.1: BAR 6: can't assign [??? 0x00000000 flags 0x0] (bogus alignment) [ 13.585168] [drm] failed to find VBIOS tables [ 13.597709] [drm] initialized overlay support [ 13.597779] vga_switcheroo: disabled [ 13.597898] [drm:i915_driver_load] *ERROR* failed to init modeset [ 13.598562] i915: probe of 0000:00:02.1 failed with error -22
Comment 1 Ferenc Wágner 2011-02-01 15:23:25 UTC
Maybe it's only prudent to add that the machine is a ThinkPad R50e with an Intel 855GM chipset.
Comment 2 Chris Wilson 2011-02-01 15:30:25 UTC
drm.debug=0xf if you please.
Comment 3 Chris Wilson 2011-02-01 15:33:22 UTC
My suspicion is that drm_irq_install() is the one returning EINVAL, probably due to drm_dev_to_irq() returning an error. Is the IRQ for the igfx disabled on your machine? [lspci?]
Comment 4 Ferenc Wágner 2011-02-01 16:07:24 UTC
I'll shortly reboot into 2.6.38-rc3 with drm.debug=0xf, but until then the lspci output taken under 2.6.37: 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) (prog-if 00 [VGA controller]) Subsystem: IBM ThinkPad R50e Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx+ Latency: 0 Interrupt: pin A routed to IRQ 11 Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M] Region 1: Memory at d0000000 (32-bit, non-prefetchable) [size=512K] Region 2: I/O ports at 1800 [size=8] Expansion ROM at <unassigned> [disabled] Capabilities: [d0] Power Management version 1 Flags: PMEClk- DSI+ D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: i915 IRQ 11 doesn't seem disabled now: $ fgrep 11 /proc/interrupts 11: 57470 XT-PIC-XT-PIC ehci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3, uhci_hcd:usb4, i915, Intel 82801DB-ICH4 Modem, yenta, ipw2200, Intel 82801DB-ICH4, utp Is there a way to get some readable screen back after the module loading failure? That would help me tremendously (this is a standalone machine), the only output is the LVDS and a handful of LEDs...
Comment 5 Ferenc Wágner 2011-02-01 16:56:37 UTC
Created attachment 45822 [details] dmesg with drm.debug=0xf under 2.6.38-rc3 I spent approx 70 seconds at the initramfs prompt before loading i915. Then I let the boot proceed with garbled screen, eventually trying to start X. Ctrl-Alt-F1 gave me back the blinking vertical strip, where I logged in and saved the dmesg and the lspci outputs, then rebooted the machine.
Comment 6 Ferenc Wágner 2011-02-01 16:58:35 UTC
Created attachment 45832 [details] lspci under 2.6.38-rc3 This is identical to the one found in the working system under 2.6.37.
Comment 7 Chris Wilson 2011-02-01 17:17:36 UTC
Created attachment 45842 [details] Where does it go wrong? Ok, that didn't really tell me anything more. (Except for the part where we fail to unload the module after an error, and explains more than anything else why everything is screwed up afterwards. Which I'm going to ignore for now...) The attached should hopefully pinpoint the reason why it fails. Hopefully.
Comment 8 Ferenc Wágner 2011-02-01 18:18:23 UTC
Created attachment 45852 [details] dmesg with drm.debug=0xf under 2.6.38-rc3 with the WARN patch applied This is with the patch in attachment 45842 [details] applied. It indeed provoked a WARNING: at drivers/gpu/drm/drm_irq.c:328 drm_irq_install+0x56/0x219 [drm]()
Comment 9 Chris Wilson 2011-02-01 18:38:02 UTC
Can you attach the complete lspci? The trouble begins when we start initializing the 2.1 device... !!!
Comment 10 Ferenc Wágner 2011-02-01 19:21:20 UTC
Created attachment 45882 [details] full lspci output My bad, sorry, 00:02.1 is indeed relevant, it's a Display controller...
Comment 11 Chris Wilson 2011-02-01 19:52:50 UTC
Created attachment 45892 [details] Only bind to function 0 This looks to be the right idea, but I've yet to test it...
Comment 12 Chris Wilson 2011-02-01 20:16:42 UTC
It survived booting on 945GME which also has the useless 2.1 function.
Comment 13 Ferenc Wágner 2011-02-01 21:22:41 UTC
It also works for me! Good (and quick) job, thanks a lot! As far as I'm concerned, this bug is resolved now.
Comment 14 Rafael J. Wysocki 2011-02-01 23:56:57 UTC
Patch : https://bugzilla.kernel.org/attachment.cgi?id=45892 Handled-By : Chris Wilson <firstname.lastname@example.org>
Comment 15 Rafael J. Wysocki 2011-02-12 22:43:11 UTC
Fixed by commit 5fe49d86f9d01044abf687a8cd21edef636d58aa .