FS#16974 - [xf86-video-intel] 845GM/855GM kernel panic with DRI enabled, KMS disabled
Attached to Project:
Arch Linux
Opened by Daniele C. (legolas558) - Monday, 02 November 2009, 09:05 GMT
Last edited by Allan McRae (Allan) - Saturday, 02 June 2012, 11:58 GMT
Opened by Daniele C. (legolas558) - Monday, 02 November 2009, 09:05 GMT
Last edited by Allan McRae (Allan) - Saturday, 02 June 2012, 11:58 GMT
|
Details
Description:
Xorg instantly crashes with the new xf86-video-intel and (presumably) only Intel 855GM hardware. Xorg.0.log (attached) talks about DRM issues: (II) intel(0): [drm] removed 1 reserved context for kernel (II) intel(0): [drm] unmapping 8192 bytes of SAREA 0xe0956000 at 0xb71ce000 (II) intel(0): [drm] Closed DRM master. then there is a kernel panic, not recoverable by any means (neither SysRq) Packages: xf86-video-intel-2.9.1-1 xorg-server-1.7.1 xf86-input-evdev-2.3.0 I am using vanilla kernel 2.6.31.5 Steps to reproduce: Start X server (startx) |
This task depends upon
can this crash be related to KMS? my kernel has KMS support but I have disabled it with 'nomodeset' kernel command line option because I had other issues with it enabled
relevant lspci lines:
00:00.0 Host bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:00.1 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:00.3 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
- xorg 1.7.1 + xf86-video-intel-2.9.1 with KMS enabled: crash within 2-3 seconds from Xorg start
- xorg 1.7.1 + xf86-video-intel-2.9.1 with KMS disabled (nomodeset in kernel command line): instant crash, no Xorg.0.log produced
- xorg-server-1.6.3.901 + xf86-video-intel-legacy-2.3.2: only possible working combination, using old packages (this configuration also requires outdated packages xf86-input-synaptics-1.1.3 and xf86-input-evdev-2.2.5 to work)
Please note that this is different from #14594 since crash happens instantly
thanks
You should get a working system with this:
-----
pacman -R xorg-server xf86-video-intel xf86-input-evdev xf86-input-synaptics && \
cd /var/cache/pacman/pkg/ && \
pacman -U xf86-input-evdev-2.2.5-1-i686.pkg.tar.gz xf86-input-synaptics-1.1.3-1-i686.pkg.tar.gz xf86-video-intel-legacy-2.3.2-3-i686.pkg.tar.gz xorg-server-1.6.3.901-1-i686.pkg.tar.gz
-----
If you miss one of these packages then download it from internet
https://bugs.freedesktop.org/show_bug.cgi?id=20901
I think kernel 2.6.32 will fix the remaining KMS fixes. Also note that the next major driver version will no longer work without KMS.
With KMS enabled, X crashes after a few seconds (but looks OK before the crash).
Without KMS (nomodeset or i915.modeset=0), X hangs the system (no SysRQ) and does not write log.
There are a few interesting lines in dmesg from i915/drm:
[drm] DAC-6: set mode 640x480 0
render error detected, EIR: 0x00000010
[drm:i915_handle_error] *ERROR* EIR stuck: 0x00000010, masking
render error detected, EIR: 0x00000010
[drm] LVDS-8: set mode 1280x768 e
Console: switching to colour frame buffer device 160x48
[drm] fb0: inteldrmfb frame buffer device
But fb console works fine, so i doubt it's relevant.
I tested using kernel 2.6.32-rc5-git6 and the problem is still present. Also, i915 in that kernel seems to be broken for me (doesn't set up fb console properly).
It seems newer kernel versions in the 2.6.31.x series cause trouble. With any 2.6.31.x kernel, X does not start if KMS is disabled. When KMS is enabled, X will hang after a few seconds with kernels 2.6.31.2 to 2.6.31.5. However, with kernel 2.6.31.1, X is much more stable (I've had uptimes of several hours) but still occasionally freezes. There is no XVideo, though.
Since the status of the intel driver is what it is, I think an ideal solution would be to maintain xf86-video-intel-legacy package that is compatible with xorg-server 1.7.x.
Fatal server error:
no screens found
See also attachment.
I realize that my hardware has just been locked out of the supported series and the tip is "buy new hardware" :(
@intel? @LKML? other distros?
this reminds me of when the i810 driver (v2.3.2) was discontinued and we lost the TV-OUT feature..
https://bugs.freedesktop.org/show_bug.cgi?id=24789
The more frequent freezing of X seems to be a result of the "Fix the pre-9xx chipset flush" patch:
http://lists.freedesktop.org/archives/intel-gfx/2009-September/004122.html
I tested this by patching a vanilla 2.6.31.1 kernel with the above patch. The resulting kernel hangs almost instantly after starting X. From the Ubuntu bugzilla, it looks like this patch has fixed problems with the i865 chipset but made them worse for i855.
P.S. title should be corrected "i855GM/i915" and not "i855G" (which does not exist)
(EE) intel(0): No kernel modesetting driver detected.
but booting with KMS enabled leads to a black screen of death (display turned off). I have asked for help on intel-gfx freedesktop mailing list, but if somebody is also following this path please give me any pointer...
@JGC: as soon as this development stack is working I'd start trying some patches, so please consider my hardware as available for tests
Thanks
I'd like to see the KMS-enabled kernel boot correctly...should by initramfs have something special inside? for what I've read around I think the framebuffer console is totally broken
I managed to enable KMS with an Intel i915 mobile board but when I log into any DE my system freezes after 2 seconds without any possibility of recovery.
I tried with drivers from AUR:
xf86-video-intel-newest
xf86-video-intel-git
But nothing changed.
bYe,
wandrian
http://bugs.archlinux.org/task/17123?only_watched=1&type[0]=&sev[0]=&due[0]=&cat[0]=&status[0]=open&percent[0]=&reported[0]=
Not sure if it's related, because the hardware is slightly different (845 vs 855), but I figured I'd add it here too just in case.
Scott
I use 2.6.31-ARCH
xf86-video-intel 2.9.1-1
xorg-server 1.7.3.902-1
Is this an arch specific problem or does it occur on other distributions like debian, ubuntu etc. too?
https://bugs.freedesktop.org/show_bug.cgi?id=24789
I am still waiting for somebody to update the title of the issue: it should be 845GM/855GM
I am currently using the intel driver on arch linux with KMS enabled, on a 855GM. Even XV works (never worked before).
Note that with KMS enabled, if i use the vesa driver it still freezes o.O but the intel one works fine now!
Can you provide more details? What kernel .config are you using?
I have just reported on the kernel bug entry that it only works with FC12+FC13_kernel+nolid.patch, so for me it must be either:
1) a weird situation triggered only by my kernel .config
2) some FC12/FC13 kernel patch fixes DRM issues very well
However even with the software used in the kernel bugzilla entry I get a crash
I am using 2.6.33-rc8 from kernel.org + nolid patch (i typed it by hand in the source but i assume its the same patch: i return status connected and skip the check)
i am not on my laptop right now however: its a CF-R3 with a 855GM chipset, kernel was stripped down to minimum config with kms/dri/agpart, i915 dri, vesa and i915 fb drivers.
i can now play 720p with xv and -hardframedrop on mplayer.. it looks nice, don't notice the frame dropping.
However, i used the laptop for 30min to make sure yesterday and more problems arised:
- opengl display is broken
- after using opengl, fonts get garbled on screen
- after a while, it freezes much like before (sysreq doesnt work) the bug that made it "not work at all"
haven't tried without using opengl.. will try tonight i guess
of course, i use arch, not fc12, no other patches, and xf86-intel (not legacy)
1) with kernel .config in http://bugzilla.kernel.org/attachment.cgi?id=25049 (my original one) I get all the above mentioned troubles
2) with kernel .config in http://bugzilla.kernel.org/attachment.cgi?id=25064 (FC13) I get a working Xorg 1.7 + KMS
I have asked on kernel bugzilla why this is happening.
Also, I have noticed that glxgears reports 200 FPS (it should be much higher) and that fonts memory is sometimes garbled
I will also keep testing and possibly find out what's happening
1) using modular AGP (in your kernel .config) will cause the OFF display issue and subsequent Xorg crash, I am gonna file an Arch bug for this since AGP module should have some priority over DRM and video card module
2) the KMS/Xorg crashes seem to be totally fixed on i8xx hardware by using 855nolid.patch + drm-intel-big-hammer.patch
Only the garbled fonts issue remains for me now
Perhaps they could add a notice to the kernel configuration help text...and we could also add this to Arch Linux documentation, since it seems to be an issue of latest kernels (since when DRM entered the stage)
Also, the "OFF display" issue happened exactly during udev rules processing, so perhaps we can add a special udev rule which loads agp modules first?
P.S. I have verified that building AGP as built-in fixes the issue, but I have not verified that DRM necessarily needs to be built-in (although I am using it as built-in to prevent further issues), so perhaps only agp module needs priority
P.S. I have added a kernel documentation bug also http://bugzilla.kernel.org/show_bug.cgi?id=15340
It *is* a separate bug because the Arch Linux stock kernel won't work on these boxes with i855GM.
(EE) intel(0): No kernel modesetting driver detected.
Is KMS disabled in latest kernel?
Anyway the i855GM issues have just been radically fixed by Daniel Vetter, you can find the patch and the complete kernel sources archive here:
http://www.iragan.com/linux/i855GM/
Patch has not yet been pushed upstream so it will take a lot of time before seeing it in regularly released kernel; all people interested can get the patch and/or the patched kernel which I have put above.
The bug should be closed as soon as the patch is accepted in linus' tree (it still has to get to drm-intel-next).
Let's see if 'i915.powersave=0' helps.
Edit: Nah, it doesn't help.
Without shadowfb, 3D acceleration is sort of working at the cost of some serious flickering. After a few minutes, artefacts start appearing on the screen and the fonts look corrupted, so the system is not really usable.
xorg-server 1.9.2-2
xf86-video-intel 2.13.0-4
kernel 2.6.36.1
On my test machines that run Arch as thinclient solution, shadowFB was required to get X to start the 2nd time. Without it, X would just hang or corrupt the whole screen. AFAIK DRI should work with ShadowFB enabled though.