Ubuntu
libdrm package

lose X display periodiclly; switching VT's restores it

Bug #572986 reported by Matt Price on 2010-05-01

This bug report is a duplicate of: Bug #572995: [arrandale] X hijacks Alt-Fn and Alt-Arrow to switch VTs. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	intel	New	Undecided	Unassigned
	libdrm (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

after recent updates I get this bug periodically. X display disappears and is replaced by error-log output; in the log I see this message:
[drm:drm_mode_getfb] *ERROR* invalid framebuffer id

switching VT's restores the display, but this behaviour repeats on average about every 10 minutes.

Around the same time I started having problems with hotkeys as well -- X hijacks Alt-Fn and Alt-Tab as though they wre Ctrl-Alt-Fn and Ctrl-Alt-Tab - reporting that now in a separate bug but noting here in case it's related.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: libdrm2 2.4.18-1ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-21.32~ppa1-generic-tuxonice 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic-tuxonice x86_64
Architecture: amd64
Date: Sat May 1 07:48:13 2010
DkmsStatus:
rtl8192se, 2.6.0015.0127.2010, 2.6.32-21-generic-tuxonice, x86_64: installed
rtl8192se, 2.6.0015.0127.2010, 2.6.33-020633-generic, x86_64: built
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
Lsusb:
Bus 002 Device 002: ID 8087:0020
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 17ef:480f Lenovo
Bus 001 Device 002: ID 8087:0020
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 2516CTO
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic-tuxonice root=UUID=08517b2d-d32a-45d4-b574-a6d38f0dde9c ro crashkernel=384M-2G:64M,2G-:128M quiet splash
ProcEnviron:
LANG=en_CA.utf8
SHELL=/bin/bash
SourcePackage: libdrm
dmi.bios.date: 01/07/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6IET49WW (1.09 )
dmi.board.name: 2516CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6IET49WW(1.09):bd01/07/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2516CTO
dmi.product.version: ThinkPad T410
dmi.sys.vendor: LENOVO
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: lucid
architecture: x86_64
kernel: 2.6.32-21-generic-tuxonice

Tags:

Revision history for this message

Matt Price (matt-price) wrote on 2010-05-01:

BootDmesg.txt Edit (53.0 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (245.6 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (476 bytes, text/plain; charset="utf-8")
GdmLog.txt Edit (52.4 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (27.2 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (49.3 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (14.7 KiB, text/plain; charset="utf-8")
PciDisplay.txt Edit (667 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.3 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.2 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.5 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (118.0 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (241.2 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (54.5 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (31.0 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (8.3 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (233 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (19.1 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (44.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Matt Price (matt-price) wrote on 2010-05-01:

the possibly-related VT-switching bug described above is here:
lp:572995

Bryce Harrington (bryce) on 2010-05-02

Changed in libdrm (Ubuntu):
status:	New → Confirmed

Revision history for this message

Matt Price (matt-price) wrote on 2010-05-09:

i can see there are some more severe intel-related bugs but this one is not insignificant for me -- it means among other things that none of my family members can ever use my computer, since they can't reset the vt. Are there any workarounds or suggestions? Would it make sense to try oneo f the many ppas wtih newer intel drivers, e.g. the 2.11git ppa (https://launchpad.net/~glasen/+archive/intel-driver)? Alternatively cn i do some testing? Thanks,
Matt