radeon: [drm:drm_mode_getfb] *ERROR* invalid framebuffer id

Bug #800140 reported by Martin Wagner
64
This bug affects 14 people
Affects Status Importance Assigned to Milestone
xserver-xorg-video-ati (Ubuntu)
Expired
Low
Unassigned

Bug Description

Binary package hint: xserver-xorg-video-ati
Ubuntu version: 11.04

The Radeon driver crashes often after login. The login process stops, the unity desktop won't appear. Dmesg says mostly this:

[drm:drm_mode_getfb] *ERROR* invalid framebuffer id

Tags: natty
Revision history for this message
Martin Wagner (mawahh) wrote :
Revision history for this message
Martin Wagner (mawahh) wrote :
Revision history for this message
Martin Wagner (mawahh) wrote :
Revision history for this message
Martin Wagner (mawahh) wrote :
Revision history for this message
Martin Wagner (mawahh) wrote :
Martin Wagner (mawahh)
affects: xserver-xorg-video-intel (Ubuntu) → xserver-xorg-video-radeonhd (Ubuntu)
affects: xserver-xorg-video-radeonhd (Ubuntu) → xserver-xorg-video-ati (Ubuntu)
Martin Wagner (mawahh)
description: updated
Martin Wagner (mawahh)
description: updated
Revision history for this message
Илья (ik1995) wrote :

Confirm, there is the same problem with the graphics card ATI radeon 5450.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xserver-xorg-video-ati (Ubuntu):
status: New → Confirmed
Revision history for this message
Jonathan Hogg (jhogg41) wrote :

This bug (or similar) also seems to affect RV516 based radeon cards.
Logs in with Unity 3D, but dock and tray icons not visible.
Unity 2D works fine.

Revision history for this message
Zaris (zaris) wrote :

I see this error in syslog when switching user from locked session. Screen goes black with cursor blinking upper left corner. With ctr-alt Fn I can still get the session. I't seems lightdm (and gdm) can not switch to locked session.
This is with open source radeon. With fglrx whole system freezes with black screen and only way out is hardware reset.

11.10 and Unity 3D, ATI HD 5700

Revision history for this message
Doug Stanley (doug-stanley) wrote :

I have a similar but different problem. When I lock my screen and come back, often times the screen will wake back up, but the dialog that normally appears to unlock the screen never appears. Sometimes I can go into virtual console and kill the screen saver daemon, and get back to my desktop, but it doesn't always work.

This is with the open source driver, and it's been a problem for quite a few releases for me. I'm trying the fireglx driver next, I seem to remember having other problems with that one in the past, but I'm desparate.

Changed in xserver-xorg-video-ati (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Reinhard Tartler (siretart) wrote :

I'm experiencing similar problems with an Radeon HD 6700 graphics card: After resuming, I see the mouse pointer, but the unlock screen does not appear. In fact, it seems to be rather invisible but still active, as I am able to enter my password and unlock the screen blindly.

Switching to an text console, playing with xrandr and switching back results in screen corruption. Killing the X server with sysrq-k brings back an lightdm login screen (but obviously kills my session).

bugbot (bugbot)
tags: added: natty
Revision history for this message
Attila Pados (attila-pados) wrote :

I am experiencing the same problem with Xubuntu 12.04, Xorg open source ati driver ,and an AGP X1950Pro 256M video card.

Right after login i land to a black screen, by pressing Ctrl-Alt-F1 i can log to a tty and see what is happening in the log.
When i enter
tail -f syslog
and then switch back to CTRL-Alt-F7, and the press Ctrl-Alt-Num+ (to switch to next available resolution), then the original error message appers in the tailed log:

[drm:drm_mode_getfb radeon] *ERROR* invalid frame buffer id

Revision history for this message
Attila Pados (attila-pados) wrote :

libdrm-radeon1 version is 2.4.40+git20130114.....
libdrm2 version is the same

my problem started about a week ago or so, which is suspiciouly near to that date in the version string

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xserver-xorg-video-intel (Ubuntu):
status: New → Confirmed
Revision history for this message
Chris Wilson (ickle) wrote :

As far as the framebuffer id error message goes, that is fixed for -intel.

Changed in xserver-xorg-video-intel (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
penalvch (penalvch) wrote :

Martin Wagner, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p xserver-xorg-video-ati REPLACE-WITH-BUG-NUMBER

Please note, given that the information from the prior release is already available, doing this on a release prior to the development one would not be helpful.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

no longer affects: xserver-xorg-video-intel (Ubuntu)
Changed in xserver-xorg-video-ati (Ubuntu):
importance: Medium → Low
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for xserver-xorg-video-ati (Ubuntu) because there has been no activity for 60 days.]

Changed in xserver-xorg-video-ati (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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