[Xorg 7.3, FreeBSD 7.0 RC1 i386] Hello, With the driver Intel version 2.2.0 (compiled by hand), X crashs at startup with a "signal 11". It works fine with the version 2.1.1 I tried with a fresh xorg.conf (X -configure), with the same result. I don't know if it is related, but the driver seems to have some problem to allocate memory. With version 2.2.0 : (==) intel(0): VideoRam: 131072 KB (**) intel(0): Framebuffer compression enabled (**) intel(0): Tiling enabled (==) intel(0): Write-combining range (0xfaf80000,0x80000) was already clear (II) intel(0): Attempting memory allocation with tiled buffers. (WW) intel(0): xf86AllocateGARTMemory: allocation of 10 pages failed (Cannot allocate memory) (WW) intel(0): xf86AllocateGARTMemory: allocation of 4 pages failed (Cannot allocate memory) With version 2.1.1, it seems ok : (==) intel(0): VideoRam: 131072 KB (==) intel(0): Write-combining range (0xfaf80000,0x80000) was already clear (II) intel(0): Attempting memory allocation with tiled buffers and large DRI memory manager reservation: (II) intel(0): Allocating 5112 scanlines for pixmap cache (II) intel(0): Success. (II) intel(0): Memory allocation layout: (II) intel(0): 0x00000000-0x0001ffff: ring buffer (128 kB) [...] Complete Xorg's log Intel 2.1.1 : http://user.lamaiziere.net/patrick/intel211.log.txt Intel 2.2.0 : http://user.lamaiziere.net/patrick/intel220.log.txt Best regards.
Created attachment 13460 [details] Trace of the core dump I managed to get a backtrace of the core dump, let me know if i shall provide more informations or testing.
So this only occurs on BSD? Eric, have you tried 2.2.0 recently? Any ideas about this one?
Created attachment 13554 [details] [review] test patch This should fix the xserver fault if hw cursor memory allocation fails. I don't know the detail on randr-1.2 relate cursor code, so this patch might still fail someplace, or there's a better complete approach.
(In reply to comment #3) > Created an attachment (id=13554) [details] > test patch > > This should fix the xserver fault if hw cursor memory allocation fails. > I don't know the detail on randr-1.2 relate cursor code, so this patch might > still fail someplace, or there's a better complete approach. Thanks. With your patch, Xorg starts well and it seems to work quite fine. I loose the DRI acceleration because HW cursor are not allocated. And i've got an error message from the FreeBSD's module i915.ko : drm0: <Intel i852GM/i855GM GMCH> on vgapci0 info: [drm] AGP at 0xf0000000 128MB info: [drm] Initialized i915 1.5.0 20060119 drm1: <Intel i852GM/i855GM GMCH> on vgapci1 info: [drm] AGP at 0xf0000000 128MB info: [drm] Initialized i915 1.5.0 20060119 error: [drm:pid1432:i915_getparam] *ERROR* i915_getparam called with no initialization New Xorg.log with this patch : (In reply to comment #3) > Created an attachment (id=13554) [details] > test patch > > This should fix the xserver fault if hw cursor memory allocation fails. > I don't know the detail on randr-1.2 relate cursor code, so this patch might > still fail someplace, or there's a better complete approach. Thanks! With this patch Xorg starts and it seems to work quite fine. My new Xorg.log with patch : http://user.lamaiziere.net/patrick/intel2.2-patch.txt I loose the DRI rendering because HW cursors are disabled and i've got an error message from the FreeBSD module i915.ko (drm) : ----- drm0: <Intel i852GM/i855GM GMCH> on vgapci0 info: [drm] AGP at 0xf0000000 128MB info: [drm] Initialized i915 1.5.0 20060119 drm1: <Intel i852GM/i855GM GMCH> on vgapci1 info: [drm] AGP at 0xf0000000 128MB info: [drm] Initialized i915 1.5.0 20060119 error: [drm:pid1432:i915_getparam] *ERROR* i915_getparam called with no initialization ----- Regards and happy new year.
The fact that your AGP driver is refusing to allocate the physical-addressed memory for the cursors should be reported to FreeBSD. But, the patch to fix your issue that resulted from it has been pushed.
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.