Display resolution (and other things?) wrong after resume from suspend to RAM

[vasek125]

Binary package hint: xorg

After resume from suspend to RAM i get wrong screen resolution. And I could not report this bug before pc reboot becouse I cant connect to wifi (probably caused by the same something?).

[GdmLog2.txt]
[mi] EQ overflowing. The server is probably stuck in an infinite loop.

Backtrace:
0: /usr/bin/X (xorg_backtrace+0x28) [0x4a3248]
1: /usr/bin/X (mieqEnqueue+0x1f4) [0x4a2ac4]
2: /usr/bin/X (xf86PostMotionEventP+0xc4) [0x47cea4]
3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fce986ed000+0x53cf) [0x7fce986f23cf]
4: /usr/bin/X (0x400000+0x6fca7) [0x46fca7]
5: /usr/bin/X (0x400000+0x11d1f3) [0x51d1f3]
6: /lib/libpthread.so.0 (0x7fce9cc09000+0xf8f0) [0x7fce9cc188f0]
7: /usr/bin/X (0x400000+0x65700) [0x465700]
8: /lib/libpthread.so.0 (0x7fce9cc09000+0xf8f0) [0x7fce9cc188f0]
9: /usr/bin/X (0x400000+0x39b40) [0x439b40]
10: /usr/bin/X (0x400000+0x3e7bd) [0x43e7bd]
11: /usr/bin/X (0x400000+0xdf83b) [0x4df83b]
12: /usr/bin/X (0x400000+0x1008ca) [0x5008ca]
13: /usr/bin/X (mieqProcessDeviceEvent+0x1e2) [0x4a2692]
14: /usr/bin/X (mieqProcessInputEvents+0x60) [0x4a2710]
15: /usr/bin/X (ProcessInputEvents+0x9) [0x46fe69]
16: /usr/bin/X (0x400000+0x30943) [0x430943]
17: /usr/bin/X (0x400000+0x261aa) [0x4261aa]
18: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7fce9b901c4d]
19: /usr/bin/X (0x400000+0x25d59) [0x425d59]
[/GdmLog2.txt]

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xorg 1:7.5+5ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
Architecture: amd64
Date: Thu May 20 09:18:54 2010
DkmsStatus:
 virtualbox-ose, 3.1.6, 2.6.32-22-generic, x86_64: installed
 virtualbox-ose, 3.1.6, 2.6.32-21-generic, x86_64: installed
 virtualbox-ose-guest, 3.1.6, 2.6.32-22-generic, x86_64: installed
 virtualbox-ose-guest, 3.1.6, 2.6.32-21-generic, x86_64: installed
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
MachineType: Hewlett-Packard HP Compaq 6730b (GB990EA#AKB)
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-22-generic root=/dev/mapper/data-system ro quiet splash
ProcEnviron:
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
dmi.bios.date: 03/19/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PDD Ver. F.0D
dmi.board.name: 30DD
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 96.19
dmi.chassis.asset.tag: CNU8390XVY
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68PDDVer.F.0D:bd03/19/2009:svnHewlett-Packard:pnHPCompaq6730b(GB990EA#AKB):pvrF.0D:rvnHewlett-Packard:rn30DD:rvrKBCVersion96.19:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq 6730b (GB990EA#AKB)
dmi.product.version: F.0D
dmi.sys.vendor: Hewlett-Packard
system:
 distro: Ubuntu
 codename: lucid
 architecture: x86_64
 kernel: 2.6.32-22-generic

[penalvch (penalvch)]

vasek125, 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 linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12-rc2

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Launchpad Janitor (janitor)]

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