Bug 702155

Created attachment 496935 [details]
Xorg.0.log

Created attachment 496936 [details]
/var/log/messages

my smolt HW profile: http://www.smolts.org/client/show/pub_56adb9dd-c210-4a9d-870e-6ebef7f8d37a

Reassigning to correct component.

(In reply to comment #0)
> Created attachment 496934 [details]
> output of dmesg
> 
> Description of problem:
> When hybernating computer and waking it up, some error messages appear on
> screen. One of them is
> 
> [drm:drm_mode_getfb] *ERROR* invalid framebuffer id

Is there any other presentation of this issue? Does anything actually break or is it just a message?

(In reply to comment #5)
> Is there any other presentation of this issue? Does anything actually break or
> is it just a message?

It is just a message. If you have ideas what could be broken, I'd be happy to check it, but so far everything I touch after this error works as before

BTW: Does reporting such messages make sense? There is one more suspend related error message (without any apparent ill effects) I have, so should I report it here?

(In reply to comment #6)
> BTW: Does reporting such messages make sense? There is one more suspend related
> error message (without any apparent ill effects) I have, so should I report it
> here?

Sure it makes sense, obviously there is something broken somewhere which would be nice if fixed. However, this will get severity Low (because it is so).

Thank you for filing the bug.

Created attachment 500937 [details]
X log - external monitor attached at 358

I get the same error message but in a more serious situation:

When I start my laptop without external monitor I get gnome3 shell and it works fine. But when I then attach an external monitor and run the display configuration tool I get digital noise on both screens and this line in the log. Ctrl-alt-f2 works fine. When I kill Xorg it starts again but this time in the old gnome desktop - not shell. Rebooting makes no change - only a power off returns it to a state where I can run gnome shell.

I would expect gnome shell to work on 2 displays - that would be awesome.

http://www.smolts.org/client/show/pub_6ee23250-8a78-44b8-a4ec-9a0b999ebbe1

****  Jun 21 07:36:24 thinkpad kernel: [498172.827906]
 [drm:drm_mode_getfb] *ERROR* invalid framebuffer id ****

   Fedora-15 on my T60p Lenovo thinkpad laptop, it goes
 dark/unresponsive on  restoring after the  screen-saver has  kicked in
 and powered down the LCD.  It is running gnome-shell 3.   Screen stays
 Blanked on restore.

   In this blanked state,  I can see the Hard-disk light blink time to
 time, to make me think that the system is alive.  I then go to  a
 different  Root-Shell window, and can see the box is basically alive
 and well.  The dmesg shows the   ' drm invalid framebuffer id'
 message.  On the  gnome-shell screen, the display stays dark. (Except for the top status line with   Day/Time  and Login-name).

   For the next minute to 10 mins,  then go through a funny mix of various keyboard-hits and mouse-clicks.  Something hits right, and the  video frame is then restored.

   My laptop uses ATI video card. Has been working fine with previous Fedora releases (verified upto Fedora-13.)

   Note:   the problem on my thinkpad T60p  is not  related to
 hibernation.   Happens when coming back from a basic  screen-saver power-save
 mode.  Usually after long duration  >= 30 mins. After long absence from laptop, the screen is not restored, and I get the  frame-buff invalid error.

The problem I have at my ASUS F3k with ati x2300 video card looking some different, but I have same message in /var/log/messages.
After I upgrade my Fedora14 to Fedora15 with GNOME3 sometimes my screen freeze, only mouse pointer able to move, no react to mouse click, no react to keyboard events. It is possible only to switch to text console by Ctrl+Alt+F2. I can see message " invalid framebuffer id " in /var/log/messages.
The problem looks with kernel radeon module and GNOME3. If I set radeon.modeset=none when I start kernel, I could not get GNOME3 and I have not the freeze problem

I added symptoms for my Thinkpad T60p above.  On more searching recently found:


https://bugzilla.gnome.org/show_bug.cgi?id=654482

which describes the same problem and points eventually to:

https://bugzilla.gnome.org/show_bug.cgi?id=651378


So there we have it.   Tons of bogus Wireless AP entries getting in the queue, and then taking time to be checked and flushed, after screen-saver resumed. My  .xsession-errors has all those entries, and is about 339M.

Workarounds:

1.  switch to ethernet
2.  Turn off Wireless Switch, before stepping away from the laptop.

I have this error too when I launch the game Enemy Territory: QUAKE Wars.

**
kernel: 2.6.40.3-0.fc15
libdrm: 2.4.26-1.fc15
xorg-x11-drv-ati: 6.14.1-2.20110525gitfe5c42f51.fc15
xorg-x11-server: 1.10.3-1.fc15
mesa-libGL: 7.11-1.fc15
libtxc_dxtn: 1.0.0-1.fc15
GPU: RV770 (Radeon 4850)
Arch: x86-64 (with 32-bit GL libs to play ETQW)
**

Moreover the game doesn't work anymore but I don't know if it is related to this message.

I have the same problem as described in comment 10

Screen freezes, only mouse moves, ctrl-f2 works. Nothing unusual in "top" or the logs (except this error messages).
ctrl-alt-backspace and login again works fine.

Seems to mostly happen while scrolling on a javascript or flash-heavy web page in firefox, but that might be a coincidence as that is mostly what I do at work...

I get these with Fedora 16 and RV620 [Radeon HD 3450] and I'm trying to track down sporadic freezes when booting Fedora 15 and 16: bug 749250

# grep ERROR /var/log/messages 
Nov  4 12:24:22 localhost kernel: [   42.803410] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
Nov  4 12:25:02 localhost kernel: [   82.389168] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
Nov  4 12:27:16 localhost kernel: [  217.099029] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id

Hello,
I found following commit in the vanilla kernel tree.
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=acb4b992d8a13728044f430b47b9199aa45993e9

> drm: remove some potentially dangerous DRM_ERRORs
> 
> Each of these error messages can be caused by a broken or malicious
> userspace wanting to spam the dmesg with useless info.  They're really
> not worthy of DRM_DEBUG statements either; those are generally only
> useful during bringup of new hardware or versions, and ought to be
> removed before going upstream anyway.

It tells that this message is not harmful.

Yes this message is not harmful. Please each people on this bug if you have a real issue open your own bug. One person, one bug that's the rule for gpu.