Ubuntu
xserver-xorg-video-intel package

T43 sometimes fails to resume from suspend

Bug #64033 reported by Matthew East on 2006-10-04

Affects		Status	Importance	Assigned to	Milestone
	xserver-xorg-video-intel (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

On my T43 (https://wiki.ubuntu.com/LaptopTestingTeam/ThinkpadT43-1871), I've noticed that resuming from suspend does not always work (sometimes it does). I get a screen with some scrambled video output, and then nothing. Please let me know what more info I can give. I have no idea what package this is a bug in.

matt@kalliope:~$ lspci
00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 3 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03)
00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d3)
00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03)
00:1e.3 Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Modem Controller (rev 03)
00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge (rev 03)
00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 03)
02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751M Gigabit Ethernet PCI Express (rev 11)
04:00.0 CardBus bridge: Texas Instruments PCI1510 PC card Cardbus Controller
04:02.0 Network controller: Intel Corporation PRO/Wireless 2915ABG Network Connection (rev 05)

Revision history for this message

Matthew East (mdke) wrote on 2006-10-04:

On some further research, this seems to be an xorg bug. I'll attach the contents of my /var/log/Xorg.0.log.old, which I presume to be the log file for the failed resume-from-suspend.

Revision history for this message

Matthew East (mdke) wrote on 2006-10-04:

This is the log file. Edit (67.3 KiB, text/plain)

Revision history for this message

Timo Aaltonen (tjaalton) wrote on 2007-04-17:

Have you tried on Feisty if it works there?

Changed in xorg:
status:	Unconfirmed → Needs Info

Revision history for this message

Kenty (knt-ubuntu) wrote on 2007-05-08:

I'm using Toshiba Dynabook SS20 which is almost the same as portege R200. I was having the exactly same error after suspend/resume.

Fatal server error:
lockup

After some research, I tried the following and now resuming works perfectly.

EDIT /etc/default/acpi-support:
-- SAVE_VBE_STATE=true
++ SAVE_VBE_STATE=false

(Maybe just commenting out would be fine)

I'm not sure this solves your problem, but it's worth trying, I think. Good luck!

Bryce Harrington (bryce) on 2007-06-02

Changed in xorg:
status:	Needs Info → Confirmed

Revision history for this message

Timo Aaltonen (tjaalton) wrote on 2007-12-05:

Probably a driver bug. Please try using "intel" instead of "i810", and tell us if it works better.

Changed in xorg:
status:	Confirmed → Incomplete

Revision history for this message

Bryce Harrington (bryce) wrote on 2008-02-07:

We're closing this bug since it is past the expiration date with no response. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.