When experimenting with /etc/apci/sleep.sh force it was found that the
system would resume just fine, but that the resume process was locked up
performing a vbetool post. This led me to try suspending from a text
console. Using 'pmi action suspend' the machine suspends, and resumes
just fine to the text console. The act of then switching to the
X-server VT causes the lockup.
By waiting after resume the networking seems to get reinitialised which
implies network manager is waking up and doing its thing. Then can
login remotely, trying to take an strace of X to a file left me with
nothing in the file. Doing an strace over the network got me less
output than is recorded in the X11 log file for the event:
[...]
(II) AIGLX: Resuming AIGLX clients after VT switch
(II) intel(0): xf86BindGARTMemory: bind key 0 at 0x01fff000 (pgoffset 8191)
(II) intel(0): xf86BindGARTMemory: bind key 1 at 0x03a40000 (pgoffset 14912)
(II) intel(0): xf86BindGARTMemory: bind key 2 at 0x03a41000 (pgoffset 14913)
(II) intel(0): xf86BindGARTMemory: bind key 3 at 0x04851000 (pgoffset 18513)
(II) intel(0): xf86BindGARTMemory: bind key 4 at 0x05661000 (pgoffset 22113)
(II) intel(0): Fixed memory allocation layout:
(II) intel(0): 0x00000000-0x0001ffff: ring buffer (128 kB)
(II) intel(0): 0x00020000-0x00100fff: compressed frame buffer (900 kB,
0x00000000be020000 physical)
(II) intel(0): 0x00101000-0x0010afff: HW cursors (40 kB)
(II) intel(0): 0x0010b000-0x00112fff: logical 3D context (32 kB)
(II) intel(0): 0x00113000-0x00124fff: exa G965 state buffer (72 kB)
(II) intel(0): 0x00125000-0x00125fff: power context (4 kB)
(II) intel(0): 0x00200000-0x0100ffff: front buffer (14400 kB) X tiled
(II) intel(0): 0x01010000-0x03a3ffff: exa offscreen (43200 kB)
(II) intel(0): 0x01fff000: end of stolen memory
(II) intel(0): 0x03a40000-0x03a40fff: HW status (4 kB)
(II) intel(0): 0x03a41000-0x04850fff: back buffer (14400 kB) X tiled
(II) intel(0): 0x04851000-0x05660fff: depth buffer (14400 kB) Y tiled
(II) intel(0): 0x05661000-0x07660fff: classic textures (32768 kB)
(II) intel(0): 0x10000000: end of aperture
(II) intel(0): using SSC reference clock of 96 MHz
(II) intel(0): Selecting standard 18 bit TMDS pixel format.
Note that in a regular resume from VT switch we then get:
(II) intel(0): Output configuration:
(II) intel(0): Pipe A is off
(II) intel(0): Display plane A is now disabled and connected to pipe A.
(II) intel(0): Pipe B is on
(II) intel(0): Display plane B is now enabled and connected to pipe B.
(II) intel(0): Output VGA is connected to pipe none
(II) intel(0): Output LVDS is connected to pipe B
(II) intel(0): Output HDMI-1 is connected to pipe none
(II) intel(0): [drm] dma control initialized, using IRQ 2298
(II) AlpsPS/2 ALPS GlidePoint: x-axis range 0 - 1023
(II) AlpsPS/2 ALPS GlidePoint: y-axis range 0 - 767
(--) AlpsPS/2 ALPS GlidePoint touchpad found
[...]
Some other bugs on Intel graphics have recommended forcing on Pipe A,
tried this with no effect:
Option "ForceEnablePipeA" "true"
--
2.6.27 dell studio 15 resume hang
https://bugs.launchpad.net/bugs/289212
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
