Bug 19345

Summary: xserver crash with vesa driver on IGP 340M
Product: xorg Reporter: Frederik Himpe <fhimpe>
Component: Server/GeneralAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED DUPLICATE QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium CC: dvgevers
Version: git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Xorg.0.log with backtrace none

Description Frederik Himpe 2008-12-31 05:52:02 UTC
Created attachment 21589 [details]
Xorg.0.log with backtrace

When I start Xserver 1.6 branch 20081222 with vesa 2.1 driver and evdev 2.1, X crashes after a few seconds. First it succeeds in outputting a blue background image, but then it crashes with this backtrace in the Xorg.0.log:

Backtrace:
0: /etc/X11/X(xorg_backtrace+0x37) [0x8134587]
1: /etc/X11/X(xf86SigHandler+0x56) [0x80c36a6]
2: [0xffffe400]
3: /etc/X11/X(CopyKeyClass+0x34) [0x8188924]
4: /etc/X11/X(mieqProcessInputEvents+0x2ec) [0x811201c]
5: /etc/X11/X(ProcessInputEvents+0x14) [0x80c4214]
6: /etc/X11/X(Dispatch+0x287) [0x8089197]
7: /etc/X11/X(main+0x395) [0x806cfb5]
8: /lib/i686/libc.so.6(__libc_start_main+0xe5) [0xb7c4d5c5]
9: /etc/X11/X [0x806c491]


In the dmesg log, there are these errors:
X:3385 conflicting memory types f8000000-f9ff0000 write-combining<->uncached-minus
reserve_memtype failed 0xf8000000-0xf9ff0000, track write-combining, req write-combining
X:3385 conflicting memory types f8000000-f9ff0000 write-combining<->uncached-minus
reserve_memtype failed 0xf8000000-0xf9ff0000, track write-combining, req write-combining
X:3420 freeing invalid memtype f8000000-f9ff0000
X:3385 conflicting memory types f8000000-f9ff0000 write-combining<->uncached-minus
reserve_memtype failed 0xf8000000-0xf9ff0000, track write-combining, req write-combining
X:3421 freeing invalid memtype f8000000-f9ff0000
X:3385 conflicting memory types f8000000-f9ff0000 write-combining<->uncached-minus
reserve_memtype failed 0xf8000000-0xf9ff0000, track write-combining, req write-combining
X:3422 freeing invalid memtype f8000000-f9ff0000
X:3385 conflicting memory types f8000000-f9ff0000 write-combining<->uncached-minus
reserve_memtype failed 0xf8000000-0xf9ff0000, track write-combining, req write-combining
X:3423 freeing invalid memtype f8000000-f9ff0000
X:3385 conflicting memory types f8000000-f9ff0000 write-combining<->uncached-minus
reserve_memtype failed 0xf8000000-0xf9ff0000, track write-combining, req write-combining
X:3424 freeing invalid memtype f8000000-f9ff0000
X:3385 conflicting memory types f8000000-f9ff0000 write-combining<->uncached-minus
reserve_memtype failed 0xf8000000-0xf9ff0000, track write-combining, req write-combining
X:3425 freeing invalid memtype f8000000-f9ff0000
X:3385 conflicting memory types f8000000-f9ff0000 write-combining<->uncached-minus
reserve_memtype failed 0xf8000000-0xf9ff0000, track write-combining, req write-combining
X:3426 freeing invalid memtype f8000000-f9ff0000
X:3385 freeing invalid memtype f8000000-f9ff0000


System is a Compaq EVO N1020v laptop with Radeon IGP 340 M graphics chip running Mandriva 2009.1 Cooker with 2.6.28 kernel.
Comment 1 Colin Guthrie 2008-12-31 08:49:34 UTC
I think this could be related to:
https://bugs.edge.launchpad.net/ubuntu/+source/xorg-server/+bug/309785
and 
http://bugs.freedesktop.org/show_bug.cgi?id=19048

This mentions http://bugs.freedesktop.org/show_bug.cgi?id=19222 I suspect therefore that this is a dupe of #19222.
Comment 2 Colin Guthrie 2008-12-31 08:50:18 UTC
I should note that I did apply that patch from #19048 in the cooker package :)
Comment 3 Dick Gevers 2008-12-31 10:20:42 UTC
Exact same backtrace as Frederik running same Mandriva Cooker 2009.1 same kernel
on a desktop/server with x11-driver-video-mga-1.4.9 for Intel Corporation 82865G/PE/P PCI to AGP Controller and Matrox Millenium MGA G550 dual head card.
Comment 4 Adam Jackson 2018-06-11 20:03:22 UTC

*** This bug has been marked as a duplicate of bug 19048 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.