[drm:drm_mode_getfb] *ERROR* invalid framebuffer id (FujitsuSiemens Amilo Pi 2530 Hotkeys)

Bug #808384 reported by Raul SA on 2011-07-10
This bug affects 25 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)

Bug Description

When I press the button Fn and button F3/F4/F5 to control the volume on laptop,
the volume level notification flickers a long time without control and the desktop hangs for a while.

After, turns into normality and "dmesg" shows [drm:drm_mode_getfb] *ERROR* invalid framebuffer id

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-8-generic 2.6.38-8.42
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic
Uname: Linux 2.6.38-8-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
 /dev/snd/controlC0: raul 1379 F.... pulseaudio
 Card hw:0 'Intel'/'HDA Intel at 0xf0500000 irq 48'
   Mixer name : 'Realtek ALC883'
   Components : 'HDA:10573055,10573055,00100700 HDA:10ec0883,17341234,00100002'
   Controls : 28
   Simple ctrls : 17
Date: Sun Jul 10 17:08:22 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=e03de110-2332-484c-ab8e-07189b4935e9 ro quiet splash vt.handoff=7
 linux-restricted-modules-2.6.38-8-generic N/A
 linux-backports-modules-2.6.38-8-generic N/A
 linux-firmware 1.52
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
StagingDrivers: lirc_ite8709
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/02/2007
dmi.bios.vendor: Phoenix
dmi.bios.version: 1.03C
dmi.board.name: F42
dmi.board.vendor: FUJITSU SIEMENS
dmi.board.version: 00030D0000000001
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.modalias: dmi:bvnPhoenix:bvr1.03C:bd07/02/2007:svnFUJITSUSIEMENS:pnAMILOPi2530:pvr:rvnFUJITSUSIEMENS:rnF42:rvr00030D0000000001:cvnFUJITSUSIEMENS:ct10:cvr:
dmi.product.name: AMILO Pi 2530
dmi.sys.vendor: FUJITSU SIEMENS

Raul SA (raulsiguenza) wrote :
description: updated
Raul SA (raulsiguenza) on 2011-07-10
summary: - [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
+ [drm:drm_mode_getfb] *ERROR* invalid framebuffer id (FujitsuSiemens
+ Amilo Pi 2530 Hotkeys)
Brad Figg (brad-figg) on 2011-07-19
Changed in linux (Ubuntu):
status: New → Confirmed
Daniel_le_Rouge (ville-lumiere) wrote :

I keep having the problem after the update to Ubuntu 11.10.

Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the release candidate kernel versus the daily build. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

tags: added: needs-upstream-testing
Daniel_le_Rouge (ville-lumiere) wrote :

I have just tested it with the latest upstream kernel. The problem remains: I booted, used the hotkeys and the computer becomes inoperable.

I used 3.1.0-0301rc10 for 64bit systems and Ubuntu 11.10.

tags: added: oneiric
removed: needs-upstream-testing

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.0.0-12.20
Daniel_le_Rouge (ville-lumiere) wrote :

You are welcome and thank you for taking the time and effort to fix that problem.

Since it is the first I used the development kernel, I did not know which one to take. Now I installed 3.1.0-999 for 64 bit from the daily/current folder. I hope it is correct.

Unfortunately, the problem remains in this newer kernel version.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Confirmed → Triaged
Hernando Torque (htorque) wrote :

I'm seeing the same in Precise (but with Intel HD graphics), whenever I switch from a virtual terminal back to tty7.

Since http://bugzilla.kernel.org/ is still dead, how to proceed?

tags: added: precise
Changed in linux (Ubuntu):
importance: Undecided → Medium
Hernando Torque (htorque) wrote :

I'm no longer able to reproduce that error message, using the 3.2.0-8-generic kernel.

Hernando Torque (htorque) wrote :

Hm, 3.2.0-17-generic and I'm seeing it again. Maybe my I made a mistake when testing it the last time.

Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to boot back into the 3.2.0-8-generic kernel to see if you are again unable to reproduce? That would indicate a regression in 3.2.0-17-generic.

Hernando Torque (htorque) wrote :

With 3.2.0-8.14 it seems to be a bit harder to get, but it's there. With 3.2.0-8.15 it's like now: every switch to a VT and back produces the message.

Hernando Torque (htorque) wrote :

After a bit more testing:

* 3.2.0-8-generic → bad
* 3.2.0-17-generic → bad
* mainline 3.2.7-030207-generic → bad
* custom vanillla 3.2.7 with CONFIG_FB_VESA=y (to cover the only config difference "make oldconfig" asked about, the PPA kernel has CONFIG_FB_VESA=n)→ bad
mainline 3.3.0-999-generic #201202270405 → good

Joseph Salisbury (jsalisbury) wrote :


Can you reproduce the bug, then post your /var/log/syslog? That will give me more to search with upstream.

Searching on with only "[drm:drm_mode_getfb] *ERROR* invalid framebuffer id" Only suggests one commit, but it is related to ftrace:

ftrace: Fix regression of :mod:module function enabling
commit 43dd61c9a09bd413e837df829e6bfb42159be52a upstream.

Do you see any other errors when this happens besides "[drm:drm_mode_getfb] *ERROR* invalid framebuffer id"?

We know that this bug exists in the 3.0 until 3.2 kernels, and it is fixed in upstream 3.3.

Do you think you can test the other v3.3 release candidates? Maybe v3.3-rc1 to see if we can narrow down when the fix was introduced?

Changed in linux (Ubuntu):
importance: Medium → High
tags: added: kernel-key
Joseph Salisbury (jsalisbury) wrote :


Could you also post any errors you get in the /var/log/Xorg.0.log file?

Hernando Torque (htorque) wrote :

I did a kernel bisect between 3.2 and 3.3-rc1 and I think I found the winner:


Andy Whitcroft (apw) wrote :

@htorque -- that patch simply removes the error message you originally reported. It doesn't seem to change functionality at all so its unlikely to have fixed any functional problems you had.

Hernando Torque (htorque) wrote :

Yes, I wasn't that happy when finding that commit, but I don't get any visual or functional problems*, so I decided based on the error message showing up or not. Guess we need to wait for Raul's feedback, sorry if I hijacked this bug report!

*) However, Xorg.0.log shows (and still does in 3.3-rc5!):

[ 9676.085] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 9677.915] (II) Open ACPI successful (/var/run/acpid.socket)
[ 9677.915] (II) AIGLX: Resuming AIGLX clients after VT switch
[ 9677.915] (EE) intel(0): Couldn't create pixmap for fbcon
[ 9677.968] (II) intel(0): EDID vendor "LEN", prod id 16561
[ 9677.968] (II) intel(0): Printing DDC gathered Modelines:
[ 9677.968] (II) intel(0): Modeline "1600x900"x0.0 106.00 1600 1664 1706 1930 900 903 906 912 -hsync -vsync (54.9 kHz)
[ 9677.968] (II) intel(0): Modeline "1600x900"x0.0 106.00 1600 1664 1706 2324 900 903 906 912 -hsync -vsync (45.6 kHz)

every time I perform a switch back to VT7.

Joseph Salisbury (jsalisbury) wrote :


Drm shouldn't be the root cause. You may have the key press without key release problem with multimedia keys common with many machines/laptops with multimedia keys, so after a key press there is no release event, userspace gets confused thinking the key is still pressed.

To confirm/see which keys don't get release events, running "showkey -s" as root and pressing the multimedia keys on a vt should do it (you can also use showkey -k as it's more readable to just see what key don't get the release event).

It appears your issue may be different than Raul's. If that is the case, we probably want to open a new bug report for your issue, so it can be tracked/addressed properly.

Raul SA (raulsiguenza) wrote :

I'm sorry, but I can't prove it, because my Amilo Pi 2530 laptop is broken.

Joseph Salisbury (jsalisbury) wrote :

Thanks for the update, Raul. For now I'll mark this bug as Incomplete unless you are able to test again at some point.


It may be best to open a separate bug for your issue. I will keep an eye out for it.

tags: removed: kernel-key
Changed in linux (Ubuntu):
status: Triaged → Incomplete
importance: High → Low

Is this bug specifically for FujitsuSiemens Amilo Pi 2530 Hotkeys or the "[drm:drm_mode_getfb] *ERROR* invalid framebuffer id" error? If the former, then #783993 and #893815 are not dupes.

(I also have the drm_mode_getfb error when switching vts after an upgrade to Precise)

alexus (alexus-m) wrote :

I have the same bug on Fujitsu-Siemens S7020.
I could try to provide you with a set of required symptoms in case you advice me what and how.

alexus (alexus-m) wrote :

I have checked appearance of the issue some times and found that behaviour is like in posts #12 and #22:
The *ERROR* appears in kernel.log each time when I switched from VT1-6 (with virtual text console) to VT7 (with X.org session opened).

alexus (alexus-m) wrote :

I'm sorry for the flood but I could suggest that current system behaviour described in my posts #23 and #24 is more related to Bug #943625.

Marco Ciampa (ciampix) wrote :

Error at every console switch here too.

Precise Pangolin amd64 on Intel Core 2 Duo with Intel graphics...

I also have this problem.

alexus (alexus-m) wrote :

@ Joseph Salisbury (jsalisbury):
You have marked the bug report as Incomplete.
  I have the same bug on Fujitsu-Siemens S7020 and could try to provide you with a set of required symptoms in case you advice me what and how.
What can I collect to move the status into Confirmed and start an investigation again?

Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers