[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)

Bug #304871 reported by Shirish Agarwal on 2008-12-03
228
This bug affects 20 people
Affects Status Importance Assigned to Milestone
xf86-video-intel
Fix Released
Critical
xserver-xorg-video-intel (Fedora)
Fix Released
High
xserver-xorg-video-intel (Ubuntu)
High
Unassigned
Jaunty
High
Bryce Harrington

Bug Description

Since the change from the 2.4.1 driver to 2.5.1, Jaunty now hangs during boot, with "Fatal server error: Couldn't bind memory for BO front buffer" shown in the log.

This bug is ONLY for the issue on i845 graphics. While the same symptom can be seen with 855 and 865, the workaround and solution is different.

Also discussed at this forum: https://bugs.freedesktop.org/show_bug.cgi?id=18974

[Original Report]
Binary package hint: xserver-xorg-video-intel

Hi all,
 This is in jaunty, I get no screens.

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface [8086:2560] (rev 03)
00:02.0 VGA compatible controller [0300]: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device [8086:2562] (rev 03)
     Subsystem: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device [8086:2562]

I am suffering from the very same problem. The upstream git commit seems to be already present in the latest xorg (xorg-x11-drv-i810-2.4.2-8.fc10.i386)..

X startup fails all the time. 100% reliable.

(intel 82865G controller)

Just went from F8 (X OK) to todays Rawhide, fully uptodate.

Surviving with fbdev for now...

Greetings, Konrad

Created attachment 319473
Xorg startop log

comment #7 with todays rawhide xorg-x11-drv-i810-2.4.2-9. still at
fbdev :-(

system-config-display is unable to start as well.

what can I do to track this down?
Konrad

X still does not start with the message "Fatal server error: Couldn't bind memory for BO front buffer" for a current Koji development system, featuring:

  kernel-2.6.27-3.fc10.i686
  libdrm-2.4.0-0.21.fc10.i386
  xorg-x11-drv-i810-2.4.2-10.fc10.i386
  xorg-x11-server-Xorg-1.5.2-2.fc10.i386

for an integrated graphics chipset Intel Corporation 82845G/GL[Brookdale-G]/GE.

I have a hobbled-together system using xorg-x11-drv-i810-2.4.2-1.fc10.x86_64 with acceleration disabled. Version 2.4.2-1 doesn't work with either EXA or XAA, and later versions don't work because of the "BO front buffer" error. The machines I've tested this with are G43/G45. Anyway, it sounds like they've made a bunch of stability improvements upstream recently, so it would be great to have a newer working driver. Thanks in advance to whoever is working on this bug!

ditto here: today's xorg-x11-drv-i810-2.4.2-10.fc10.i386 still only works with
NoAccel (BO front buffer) on intel 82865G.

I have another wierdness on this machine when logging in to the console
(run level 3): my user id is not being echoed the first time. after a
logout and again login it is echoed properly.

can one of the 865G people try adding

Option "Legacy3D" "false"

to the xorg.conf device section?

Created attachment 320413
X org log file

With
Option "Legacy3D" "false"
it gets further, displaying the splash login screen, sometoimes with corrupted text, and quickly freezes up. I am attaching the Xorg.0.log file just in case it is useful, but I don't think it is.

Created attachment 320483
Xorg.0.log

argh, forgot to type this comment into the attachments comment field...

Gets past the BO pin message but does not become useable.

The kde konsole background looked like a chess board (white/light grey)

My Xorg.0.log seems to be more complete, I was able to reboot the
machine via ssh.

In the kernel log I found the following lines:

Oct 15 21:25:04 f9beta1 kernel: [drm] Initialized drm 1.1.0 20060810
Oct 15 21:25:04 f9beta1 kernel: pci 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Oct 15 21:25:04 f9beta1 kernel: [drm:i915_driver_load] *ERROR* failed to enable MSI
Oct 15 21:25:04 f9beta1 kernel: [drm] Initialized i915 1.6.0 20080730 on minor 0
Oct 15 21:25:19 f9beta1 acpid: client connected from 2814[0:500]
Oct 15 21:52:46 f9beta1 kernel: konsole[3147]: segfault at 84 ip 0065057f sp bf81b120 error 4 in libkdeui.so.5.1.0[380000+360000]
Oct 15 21:52:47 f9beta1 kernel: [drm:i915_gem_idle] *ERROR* hardware wedged

what to try next? All help very much appreciated, no_accel is dog slow,
unfortunately.

Greetings,
Konrad

*** Bug 467554 has been marked as a duplicate of this bug. ***

*** Bug 465844 has been marked as a duplicate of this bug. ***

Ajax, is this a blocker ?

If it only affects intel kms and we are not enabling that by default, it might not be...

(In reply to comment #18)
> If it only affects intel kms and we are not enabling that by default, it might
> not be...

Installing F10-Snap1-i686 on Intel 82845G/GL[Brookdale-G]/GE broke X unless option "NoAccel" was added to some xorg.conf file created after completion of the install procedure, and the bug still affects current "rawhide".
It does not seem to be a matter of kernel mode setting anyway which appears to be currently disabled for Intel graphics.

Matthias, I agree with Joachim that this seems unrelated to kernel mode setting. It's a very serious problem that makes it completely impossible to start X. Not that my vote counts for anything, but I think this should be a blocker. Thanks!

Still breaks on F10-Snap3-i686. Booted to runlevel 3 and tried to start with:
  startx /usr/bin/xterm -- -logverbose 7
    (I yum installed xterm on to a live-usb stick)
The herringbone Xserver crosshatch came up, but no xterm and no mouse.
In another network login:
  xterm -display :0
and then the Xserver logs a
[mi] EQ overflowing. The server is probably stuck in an infinite loop.
and a backtrace. I've attached Xorg.0.log file, and tacked in the lines
from /var/log/messages.

Created attachment 321531
Xorg.0.log from Fedora-10-Snap3-i686-Live, no config file

This is a Dell inspiron 7500 laptop.
Fedora-10-Snap3-i686-Live, no Xorg config file (internal defaults)

Bob, yours looks like a separate bug. You should probably open up a new bug report.

This nasty problem doesn't happen only with the i810 driver but also with the "intel" driver. First of all it's not only annoying you don't get a login manager but 2nd, there should be an error telling that X can't be started. So probably 2 bugs.

rawhide version: 29-10-2008
gpu: Intel Corporation 82865G Integrated Graphics Controller

(In reply to comment #24)
> This nasty problem doesn't happen only with the i810 driver but also with the
> "intel" driver. First of all it's not only annoying you don't get a login
> manager but 2nd, there should be an error telling that X can't be started. So
> probably 2 bugs.

Just for the record, at least since F9 i810 driver is just an alias for intel driver.

(In reply to comment #23)
> Bob, yours looks like a separate bug. You should probably open up a new bug
> report.

Thanks Andrew - I've created Bug 469292 , and added more detail for my case.

Download full text (3.3 KiB)

Hello,

i do not know if this helps at all but I have a HP Compaq d330 with a intel 82865G Integrated Graphics controller an I too have the same issue described in this thread.

I have tried running F10 snapshot3 i686 KDE4 live cd. The booting of the live cd fails when starting X, nor do i get a nice graphical plymouth boot.

extract from my xorg.0.log:

X.Org X Server 1.5.2
Release Date: 10 October 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.18-92.1.10.el5 i686
Current Operating System: Linux localhost.localdomain 2.6.27.3-34.rc1.fc10.i686 #1 SMP Tue Oct
 21 01:39:53 EDT 2008 i686
Build Date: 20 October 2008 10:41:26AM
Build ID: xorg-x11-server 1.5.2-8.fc10
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Nov 3 17:28:53 2008
(EE) Unable to locate/open config file
(II) Loader magic: 0x81f3400
(II) Module ABI versions:
        X.Org ANSI C Emulation: 0.4
        X.Org Video Driver: 4.1
        X.Org XInput driver : 2.1
        X.Org Server Extension : 1.1
        X.Org Font Renderer : 0.6
(II) Loader running on linux
(++) using VT number 7

......

drmGetBusid returned ''
(II) [drm] loaded kernel module for "i915" driver.
(II) [drm] DRM interface version 1.3
(II) [drm] DRM open master succeeded.
(II) intel(0): [drm] Using the DRM lock SAREA also for drawables.
(II) intel(0): [drm] framebuffer mapped by ddx driver
(II) intel(0): [drm] added 1 reserved context for kernel
(II) intel(0): X context handle = 0x1
(II) intel(0): [drm] installed DRM signal handler
(**) intel(0): Framebuffer compression disabled
(**) intel(0): Tiling enabled
(==) intel(0): VideoRam: 131072 KB
(II) intel(0): Attempting memory allocation with tiled buffers.
(II) intel(0): Tiled allocation successful.
(II) intel(0): [drm] Registers = 0xfc400000
(II) intel(0): [drm] Initialized kernel agp heap manager, 33554432
(II) intel(0): [dri] visual configs initialized
(II) intel(0): Page Flipping disabled
(II) intel(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(II) EXA(0): Offscreen pixmap area of 34406400 bytes
(II) EXA(0): Driver registered support for the following operations:
(II) Solid
(II) Copy
(II) Composite (RENDER acceleration)
(==) intel(0): Backing store disabled
(==) intel(0): Silken mouse enabled
(II) intel(0): Initializing HW Cursor
(II) intel(0): [DRI] installation complete
(II) intel(0): xf86BindGARTMemory: bind key 0 at 0x03f2f000 (pgoffset 16175)
(II) intel(0): xf86BindGARTMemory: bind key 1 at 0x03f30000 (pgoffset 16176)
(II) intel(0): xf86BindGARTMemory: bind key 2 at 0x06000000 (pgoffset 24576)
(EE) intel(0): Failed to pin front buffer: Cannot allocate memory

Fatal server error:
Couldn't bind memory for BO front buffe...

Read more...

Do we have any hope for this working in Fedora 10? Just hoping...

Thanks.

*** Bug 469115 has been marked as a duplicate of this bug. ***

*** Bug 466801 has been marked as a duplicate of this bug. ***

*** Bug 460776 has been marked as a duplicate of this bug. ***

*** Bug 449491 has been marked as a duplicate of this bug. ***

An attempt to solve this by reverting the driver to not use the GEM system is in the works. Please stay tuned for test packages.

feel free to throw test packages at us :-). very much appreciated!

(hardware is 00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02) BTW)

Side note: with Option "Legacy3D" "no" the KDE splash screen is
being displayed properly but the X server is soon getting stuck in some
DRI ioctl .

Just launching X and starting an xterm and twm goes OK, however when
moving around the xterm there is graphics garbage left behind
(mostly thin horizontal and vertical lines). The xterm (maximized)
survives a find / -print and runs at a fine speed. Then I got
adventurous and started firefox on www.orf.at. The page got mostly
displayed but then the X server hung like above.

During boot I only get something like a progress bar in text mode
at the bottom of the screen, no nice splash image at all.

Greetings,
Konrad

The fix Jesse mentioned in comment #33 is in kernel-2.6.27.5-109.fc10. Could you please retest with that kernel (or newer) and confirm whether X starts now?

(In reply to comment #34)
> During boot I only get something like a progress bar in text mode
> at the bottom of the screen, no nice splash image at all.

That's expected. Graphical boot requires kernel modesetting. Intel modesetting drivers should appear sometime before F11.

This is on a Dell Inspiron 510M with Intel Corporation 82852/855GM Integrated Graphics Device.

Experienced same error messages as in comment #27 with kernel-2.6.27.5-109.fc10. Tested with kernel-2.6.27.5-109.fc10, I can confirm the issue is gone for me and X can be started correctly.

In comment #36, it should read "same error messages with kernel-2.6.27.5-101.fc10"

With the new kernel, I still get a black screen and hang using XAA. While EXA doesn't hang and I can login, I get screen corruption if using Compiz (or any 3D app).

Supermicro C2SEA with G45 X4500HD:

kernel-2.6.27.5-109.fc10.x86_64
xorg-x11-drv-i810-2.5.0-3.fc10.x86_64
xorg-x11-server-Xorg-1.5.3-3.fc10.x86_64
xorg-x11-server-common-1.5.3-3.fc10.x86_64

EXA is the default, as far as I can tell. So if the default case works now, we can at least move this off the blocker list.

What error messages appear in Xorg.0.log if you're using XAA?

Screen corruption using Compiz/GL stuff is a separate bug - if it's font corruption, perhaps it's bug 471537?

xorg-x11-drv-i810-2.5.0-3.fc10.i386
kernel-2.6.27.5-109.fc10.i686
Intel Corporation 82865G

Server starts now even w/o xorg.conf but text display is heavily
corrupted. (KDE konsole, Firefox, etc)
With no_accel there is no text corruption.

glxgears
[intel_init_bufmgr:592] Error initializing buffer manager.
668 frames in 5.0 seconds = 133.492 FPS

The corruption looks funny while typing: while typing the "The" at beginning
of this line the "Th" was cut about half vertically(only upper part shown) and
when I typed the "e" then the missing parts appeared.

will attach an image combined from three screen shots (KDE konqueror on www.heise.de)

Thanks for your efforts,
Konrad

Created attachment 323654
graphic glitches, see comment #40

Created attachment 323659
Xorg.0.log - comment #40

it is almost impossible to view this file in less or vi. about one third of the lines is invisible and gets visible when you move the cursor around vertically.

(In reply to comment #40)
> The corruption looks funny while typing: while typing the "The" at beginning
> of this line the "Th" was cut about half vertically(only upper part shown) and
> when I typed the "e" then the missing parts appeared.

Yes, that looks just like bug 471537. Follow up there for the graphical corruption problems.

Seems like X is starting up successfully now, and there's no mention of the original error message. Closing this bug.

Reopen *only* if X fails to start and the message "Couldn't bind memory for BO front buffer" appears in Xorg.0.log.

*** Bug 471973 has been marked as a duplicate of this bug. ***

I see this same problem with F10 release, on a Thinkpad T61 with Intel Mobile GM965/GL960 (PCI vendor/ID 8086:2a03).

EXA vs XAA doesn't matter, and neither does the suggested Legacy3D; the only workaround I've found is Option "NoAccel" "yes" in xorg.conf. Same error from dmesg:
  ...
  [drm:i915_gem_object_pin] *ERROR* Failure to bind: -12
  ...

Same error from Xorg.0.log:
  ...
  (EE) intel(0): Failed to pin front buffer: Cannot allocate memory

  Fatal server error:
  Couldn't bind memory for BO front buffer

kernel-2.6.27.5-117.fc10.x86_64
xorg-x11-drv-i810-2.5.0-3.fc10.x86_64

(Additionally there's a failure when the X server crashes that seems to disable all input, so X never exits cleanly and I can't switch to another virtual terminal. All I can do is hit the power button to cleanly reboot [i.e. the ACPI event seems to be handled properly].)

207 comments hidden view all 209 comments
Shirish Agarwal (shirishag75) wrote :
Shirish Agarwal (shirishag75) wrote :
Shirish Agarwal (shirishag75) wrote :
Shirish Agarwal (shirishag75) wrote :

I do have grub.cfg without the xforcevesa if that could be an issue?

Thank you for reporting this bug. Could you please also attche the following:
- /etc/X11/xorg.conf
- output of `lspci -vvnn`

Also, have you installed the libdrm-intel1 package? (see bug 303177)

Shirish Agarwal (shirishag75) wrote :

I have installed libdrm-intel1 package.

Attaching the output of lspci --vvnn

Shirish Agarwal (shirishag75) wrote :

Attaching the output of /etc/X11/xorg.conf

Shirish Agarwal (shirishag75) wrote :

My apt term.log

Bryce Harrington (bryce) on 2008-12-05
Changed in xserver-xorg-video-intel:
status: New → Confirmed

Created an attachment (id=20941)
Xorg.0.log

Forwarding this bug report from a Ubuntu reporter:
https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/304871
Also seen on Fedora:
http://webui.sourcelabs.com/fedora/issues/461829

[Problem]
X hangs during boot with error "Couldn't bind memory for BO front buffer"

[lspci]
00:02.0 VGA compatible controller [0300]: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device [8086:2562] (rev 03)
 Subsystem: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device [8086:2562]

[Report]
Regression since 2.4.1 driver seen in 2.5.1 driver on 82845G/GL[Brookdale-G]/GE hardware. X hangs during start up and the following error message appears in the Xorg.0.log:

(EE) intel(0): Failed to pin front buffer: Cannot allocate memory

Fatal server error:
Couldn't bind memory for BO front buffer

Two other users indicated having a matching issue; one user was also on 845, the other on undeclared hardware. http://ubuntuforums.org/showthread.php?t=998754

Bryce Harrington (bryce) on 2008-12-09
Changed in xserver-xorg-video-intel:
importance: Undecided → High

Could be a 845-specific issue (in the forums link, one user saying he had the same issue also saw it on 845; the other user didn't indicate his hardware so who knows.) Anyone on hardware other than 845 able to reproduce it?

Anyway, I've forwarded it upstream here; please subscribe, etc.:
https://bugs.freedesktop.org/show_bug.cgi?id=18974

Changed in xserver-xorg-video-intel:
status: Unknown → Confirmed
Bryce Harrington (bryce) on 2008-12-09
description: updated
Jynx97 (jynx97) wrote :

Attaching the output of lspci --vvnn .

Changed in xserver-xorg-video-intel:
status: Unknown → Fix Released
DougieFresh4U (butcheeyboy) wrote :

I have the same 'Fatal error' messege, intel865G chipset. Stuck on 'vesa'
attached ispci as well

Bryce Harrington (bryce) wrote :

Thanks, so 865 is affected as well apparently. Anyone else seeing this same exact error?

description: updated

Eric says this error appears if you've got a memory allocation setup that doesn't fit in your apperture, and DRI2 will likely fix it.

I am seeing exactly this behaviour with Jaunty and 845 chipset on an IBM machine.

This is happening with the Intel 865G chipset as well

On a Dell OptiPlex GX270 (bios A07), with a current Jaunty (including libdrm-intel1 2.4.1-0ubuntu5), I have the same problems here:

(EE) intel(0): Failed to pin front buffer: Cannot allocate memory

Fatal server error:
Couldn't bind memory for BO front buffer

00:02.0 VGA compatible controller [0300]: Intel Corporation 82865G Integrated Graphics Controller [8086:2572] (rev 02) (prog-if 00 [VGA])
 Subsystem: Dell Device [1028:0151]
 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 16
 Region 0: Memory at f0000000 (32-bit, prefetchable) [size=128M]
 Region 1: Memory at feb80000 (32-bit, non-prefetchable) [size=512K]
 Region 2: I/O ports at ed98 [size=8]
 Capabilities: [d0] Power Management version 1
  Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
 Kernel modules: intelfb

Anand Kumria (wildfire) wrote :

I was having this problem too.

I downgraded my kernel to 2.6.27 and things are working perfectly fine.

I suspect the problem is that libdrm is not correctly detecting that the kernel is not doing mode setting.

Twig (pfirth) wrote :

I confirm that downgrading to 2.6.27-8 also works for me. The desktop takes forever to load but I suspect that that is another issue.

Since I can't run X with the intel driver in its current state, I have been using the fbdev driver. Here are some details and (attached) log entries. I hope it can be of use:

sudo lspci -nnvv :

00:02.0 VGA compatible controller [0300]: Intel Corporation 82865G Integrated Graphics Controller [8086:2572] (rev 02) (prog-if 00 [VGA])
 Subsystem: Dell Device [1028:0151]
 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 16
 Region 0: Memory at f0000000 (32-bit, prefetchable) [size=128M]
 Region 1: Memory at feb80000 (32-bit, non-prefetchable) [size=512K]
 Region 2: I/O ports at ed98 [size=8]
 Capabilities: [d0] Power Management version 1
  Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
 Kernel driver in use: intelfb
 Kernel modules: intelfb

Some lines from dmesg | grep -i -e intel -e drm -e agp:

[ 21.064321] Linux agpgart interface v0.103
[ 21.160181] agpgart-intel 0000:00:00.0: Intel 865 Chipset
[ 21.160644] agpgart-intel 0000:00:00.0: detected 8060K stolen memory
[ 21.162745] agpgart-intel 0000:00:00.0: AGP aperture is 128M @ 0xf0000000

[ 74.884390] intelfb: Framebuffer driver for Intel(R) 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/945GME/965G/965GM chipsets
[ 74.884403] intelfb: Version 0.9.6
[ 74.884493] intelfb 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 74.884509] intelfb: 00:02.0: Intel(R) 865G, aperture size 128MB, stolen memory 8060kB
[ 74.888847] intelfb: Initial video mode is 1024x768-32@70.
[ 466.161347] [drm] Initialized drm 1.1.0 20060810
[ 466.201873] intelfb 0000:00:02.0: setting latency timer to 64
[ 466.210603] [drm] Initialized i915 1.6.0 20080730 on minor 0
[ 822.739357] [drm:i915_gem_object_bind_to_gtt] *ERROR* GTT full, but LRU list empty
[ 822.739365] [drm:i915_gem_object_pin] *ERROR* Failure to bind: -12<3>[drm:i915_gem_object_bind_to_gtt] *ERROR* GTT full, but LRU list empty
[ 827.341749] [drm:i915_gem_object_pin] *ERROR* Failure to bind: -12<3>[drm:i915_gem_object_bind_to_gtt] *ERROR* GTT full, but LRU list empty
[ 831.945566] [drm:i915_gem_object_pin] *ERROR* Failure to bind: -12<3>[drm:i915_gem_object_bind_to_gtt] *ERROR* GTT full, but LRU list empty
[ 1117.105987] [drm:i915_gem_object_pin] *ERROR* Failure to bind: -12<3>[drm:i915_gem_object_bind_to_gtt] *ERROR* GTT full, but LRU list empty
[ 1827.914660] [drm:i915_gem_object_pin] *ERROR* Failure to bind: -12

Created an attachment (id=21237)
intel driver failing to load on :1 while :0 is occupied with intelfb/fbdev driver

Bryce Harrington (bryce) on 2008-12-17
Changed in xserver-xorg-video-intel:
status: Confirmed → Triaged
DeJe (djenett) wrote :

I can confirm this bug with 855GM chipset.
For me, kernel 2.6.27 was working also. I cannot attach any logs cause I allready reformatted and removed Jaunty. I saw that this error still is in Alpha2 (https://wiki.ubuntu.com/JauntyJackalope/TechnicalOverview#Known%20Issues) so I wait testing Jaunty until at least X is working correctly. ;)

Jynx97 (jynx97) wrote :

Still seeing this issue, adding new Xorg log.

Mahesh Asolkar (asolkar) wrote :
Mahesh Asolkar (asolkar) wrote :

Same issue with 'Intel Corporation 82852/855GM Integrated Graphics Device rev 2'.

manzur (sl-solaris) wrote :

I can confirm this bug with i845 chipset

I was experiencing this problem with an old uniwell laptop (intel graphics), and have a partial resolution by changing the color depth from 24 to 16 bit, i.e. add
DefaultDepth 16
to the screen section of /etc/X11/xorg.conf

Partial resolution means I can achieve default resolution 1280x800 at 16 bit color using the intel driver

Created an attachment (id=21481)
Xorg.0.log

same problem here:
(EE) intel(0): Failed to pin back buffer: Cannot allocate memory

(Xorg.0.log ist attached)

lspci:
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)

kernel: 2.6.28

using 'Option "Legacy3D" "false"' I get working 2D but no 3D:
[intel_init_bufmgr:497] Error initializing buffer manager.
X Error of failed request: BadAlloc (insufficient resources for operation)
  Major opcode of failed request: 154 (GLX)
  Minor opcode of failed request: 3 (X_GLXCreateContext)
  Serial number of failed request: 24
  Current serial number in output stream: 27

This bug is also present in xf86-video-intel-2.5.99.1

Created an attachment (id=21482)
Failure log

The same on intel 855GME here,

x11-base/xorg-server-1.5.3
x11-drivers/xf86-video-intel-2.5.1
x11-libs/libdrm-2.4.1
media-libs/mesa-7.2
sys-kernels/gentoo-sources-2.6.28
Gentoo Linux

cat ~/Xorg.0.log | grep -C3 "(EE)"
 to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Dec 26 01:06:28 2008
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Simple Layout"
--
(II) intel(0): xf86BindGARTMemory: bind key 4 at 0x03bfe000 (pgoffset 15358)
(II) intel(0): xf86BindGARTMemory: bind key 5 at 0x03bff000 (pgoffset 15359)
(II) intel(0): xf86BindGARTMemory: bind key 6 at 0x059ff000 (pgoffset 23039)
(EE) intel(0): Failed to pin front buffer: Cannot allocate memory

Fatal server error:
Couldn't bind memory for BO front buffer

Marques Johansson (marques) wrote :

I tried setting the DefaultDepth to 16, but that caused X to lock up (mouse worked, could not type in the log in prompt) after a few seconds (less than 15).

I tried adding NoAccel and that is allowing me to use X at 1920x1200, without compiz.

Both logs are attached.

Marques Johansson (marques) wrote :
Marques Johansson (marques) wrote :

The errors and warnings in the NoAccel log I attached are:

(WW) intel(0): libpciaccess reported 0 rom size, guessing 64kB
(WW) intel(0): Register 0x70024 (PIPEASTAT) changed from 0x80000207 to 0x00000000
(WW) intel(0): PIPEASTAT before: status: FIFO_UNDERRUN VSYNC_INT_STATUS SVBLANK_INT_STATUS VBLANK_INT_STATUS OREG_UPDATE_STATUS
(WW) intel(0): PIPEASTAT after: status:
(EE) intel(0): Failed to init memory manager

That first error message yields some google matches. I thought EE was a dead end for X, but this log is from the active session.

Marques Johansso, can you put up your xorg.conf ?
--
          Regards,
          Shirish Agarwal
  This email is licensed under http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17

Marques Johansson (marques) wrote :

It's the vanilla xorg.conf with 'Option "NoAccel" "true"' added. I have some other junk in there, but that's all it is.

Section "Device"
 Identifier "Configured Video Device"
# when intel doesn't work, modprobe intelfb and use these instead of 'driver "intel"'
# Driver "fbdev"
# Option "UseFBDev" "true"
 Driver "intel"

 Option "NoAccel" "true" # works around LPB 304871 - probably disables the next two
 Option "XvMC" "true" # Enabled for no particular reason
 Option "TripleBuffer" "true" # Enabled for no particular reason
 Option "ModeDebug" "true" # More Verbose logging
 Option "FallbackDebug" "true" # More Verbose logging
EndSection

Section "Monitor"
 Identifier "Configured Monitor"
EndSection

Section "Screen"
# 16BPP is a possible work around for LPB 304871 that only locks me up at
# 2.6.28-3-generic, xserver-xorg-video-intel 2:2.5.1-1ubuntu7
# DefaultDepth 16
 Identifier "Default Screen"
 Monitor "Configured Monitor"
 Device "Configured Video Device"
EndSection

Marques Johansson (marques) wrote :

I've also used a daily Jaunty live CD while this bug has existed, and strangely enough, the CD which uses the latest xorg and 2.6.28 kernel doesn't give me this problem. Maybe it disables acceleration also - I didn't check.

Marques Johansson (marques) wrote :

The log shows that my XvMC is disabled, but if you are going to copy my config line per line, you may also want to make sure the file "/etc/X11/XvMCConfig" has this single line:
libIntelXvMC.so.1

Shirish Agarwal (shirishag75) wrote :

I also get few warnings

(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
(WW) intel(0): libpciaccess reported 0 rom size, guessing 64kB
(WW) intel(0): Register 0x70024 (PIPEASTAT) changed from 0x80000207 to 0x00000000
(WW) intel(0): PIPEASTAT before: status: FIFO_UNDERRUN VSYNC_INT_STATUS SVBLANK_INT_STATUS VBLANK_INT_STATUS OREG_UPDATE_STATUS
(WW) intel(0): PIPEASTAT after: status:
(WW) config/hal: device AT Translated Set 2 keyboard already added. Ignoring.

Bryce Harrington (bryce) on 2009-01-14
description: updated
Gavin Tweedie (gav-narx) wrote :

Pretty sure I'm hitting this too with an Intel 915GM/GMS/910GML chipset. Can supply logs if useful in addition to what is already attached.

Temp workaround for me was to switch to Vesa driver.

I have the same setup than Yu Yuwei, and I want to add that if I boot a 2.6.27 kernel, xorg starts without problems.
It is only with the 2.6.28 kernel that I can reproduce the failure.

manzur (sl-solaris) wrote :

i confirm this too, i can not use jaunty jackalope because of this bug, i am using:
Intel(r) 82845G/GL/GE/PE/GV Graphic Controller

Bryce Harrington (bryce) on 2009-01-30
Changed in xserver-xorg-video-intel:
status: Triaged → Incomplete
Bryce Harrington (bryce) on 2009-02-04
Changed in xserver-xorg-video-intel:
status: Incomplete → Triaged
Changed in xserver-xorg-video-intel:
assignee: nobody → bryceharrington
Bryce Harrington (bryce) on 2009-03-28
Changed in xserver-xorg-video-intel (Ubuntu Jaunty):
status: Triaged → In Progress
Bryce Harrington (bryce) on 2009-03-31
description: updated
Bryce Harrington (bryce) on 2009-03-31
Changed in xserver-xorg-video-intel (Ubuntu Jaunty):
status: In Progress → Fix Released
Changed in xserver-xorg-video-intel:
status: Confirmed → Fix Released
tags: added: iso-testing
Changed in xserver-xorg-video-intel (Ubuntu):
assignee: Bryce Harrington (bryceharrington) → nobody
Changed in xserver-xorg-video-intel:
importance: Unknown → Critical
Changed in xserver-xorg-video-intel:
importance: Critical → Unknown
Changed in xserver-xorg-video-intel:
importance: Unknown → Critical
Changed in xserver-xorg-video-intel (Fedora):
importance: Unknown → High
Displaying first 40 and last 40 comments. View all 209 comments or add a comment.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.