Bug 21341 - second X server does not wake up after sleep
Summary: second X server does not wake up after sleep
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: 7.4 (2008.09)
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-22 10:04 UTC by Dobai-Pataky Balint
Modified: 2018-06-12 18:43 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Dobai-Pataky Balint 2009-04-22 10:04:00 UTC 
sleeping S3 is fine, waking up is fine, except i run two X servers from gdm, and the second monitor remains in standby.

# ps -ef |grep X
root      3363  3359  1 17:26 tty7     00:01:37 /usr/bin/X :0 -ac -br -auth /var/gdm/:0.Xauth vt7
root      4023  4020  0 19:46 ?        00:00:00 /usr/bin/X :1 :1 -ac -br -layout Second -sharevts -novtswitch -auth /var/gdm/:1.Xauth vt8

# kill -9 4023
and second X appears.

# uname -a
Linux anubis 2.6.29-gentoo-r1 #2 SMP PREEMPT Wed Apr 22 17:13:56 EEST 2009 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 5600+ AuthenticAMD GNU/Linux

some logs:
Apr 22 19:45:26 anubis PCI-DMA: Resuming GART IOMMU
Apr 22 19:45:26 anubis PCI-DMA: Restoring GART aperture settings
Apr 22 19:45:26 anubis pci 0000:00:00.0: restoring config space at offset 0xf (was 0x0, writing 0xff)
Apr 22 19:45:26 anubis pci 0000:00:00.0: restoring config space at offset 0xb (was 0x0, writing 0x50001458)
Apr 22 19:45:26 anubis pci 0000:00:00.1: restoring config space at offset 0xb (was 0x0, writing 0x50001458)
Apr 22 19:45:26 anubis pci 0000:00:00.1: restoring config space at offset 0x1 (was 0x40200100, writing 0x200100)
Apr 22 19:45:26 anubis pci 0000:00:00.2: restoring config space at offset 0xb (was 0x0, writing 0x50001458)
Apr 22 19:45:26 anubis pci 0000:00:00.3: restoring config space at offset 0xf (was 0x0, writing 0xff)
Apr 22 19:45:26 anubis pci 0000:00:00.3: restoring config space at offset 0xb (was 0x0, writing 0x50001458)
Apr 22 19:45:26 anubis pci 0000:00:00.4: restoring config space at offset 0xf (was 0x0, writing 0xff)
Apr 22 19:45:26 anubis pci 0000:00:00.4: restoring config space at offset 0xb (was 0x0, writing 0x50001458)
Apr 22 19:45:26 anubis pci 0000:00:00.5: restoring config space at offset 0xf (was 0x0, writing 0xff)
Apr 22 19:45:26 anubis pci 0000:00:00.5: restoring config space at offset 0xb (was 0x0, writing 0x50001458)
Apr 22 19:45:26 anubis pci 0000:00:00.6: restoring config space at offset 0xb (was 0x0, writing 0x50001458)
Apr 22 19:45:26 anubis pci 0000:00:00.6: restoring config space at offset 0x1 (was 0x200100, writing 0x200102)
Apr 22 19:45:26 anubis pci 0000:00:00.7: restoring config space at offset 0xb (was 0x0, writing 0x50001458)
Apr 22 19:45:26 anubis pcieport-driver 0000:00:04.0: restoring config space at offset 0x7 (was 0x1f1, writing 0x200001f1)
Apr 22 19:45:26 anubis pcieport-driver 0000:00:04.0: restoring config space at offset 0x1 (was 0x100007, writing 0x100407)
Apr 22 19:45:26 anubis pci 0000:00:08.0: restoring config space at offset 0xf (was 0x0, writing 0xff)
...
Apr 22 19:45:26 anubis pcieport-driver 0000:00:15.0: restoring config space at offset 0x1 (was 0x100007, writing 0x100407)
Apr 22 19:45:26 anubis pcieport-driver 0000:00:17.0: restoring config space at offset 0x7 (was 0x1f1, writing 0x200001f1)
Apr 22 19:45:26 anubis pcieport-driver 0000:00:17.0: restoring config space at offset 0x1 (was 0x100007, writing 0x100407)
Apr 22 19:45:26 anubis nvidia 0000:01:00.0: restoring config space at offset 0x3 (was 0x8, writing 0x0)
Apr 22 19:45:26 anubis nvidia 0000:01:00.0: restoring config space at offset 0x1 (was 0x100007, writing 0x100006)
Apr 22 19:45:26 anubis nvidia 0000:04:00.0: restoring config space at offset 0xf (was 0x100, writing 0x107)
Apr 22 19:45:26 anubis nvidia 0000:04:00.0: restoring config space at offset 0x7 (was 0x4, writing 0xe9000004)
Apr 22 19:45:26 anubis nvidia 0000:04:00.0: restoring config space at offset 0x5 (was 0xc, writing 0xd000000c)
Apr 22 19:45:26 anubis nvidia 0000:04:00.0: restoring config space at offset 0x4 (was 0x0, writing 0xe8000000)
Apr 22 19:45:26 anubis nvidia 0000:04:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100006)
Apr 22 19:45:26 anubis Enabling non-boot CPUs ...
Apr 22 19:45:26 anubis SMP alternatives: switching to SMP code
Apr 22 19:45:26 anubis Booting processor 1 APIC 0x1 ip 0x6000
Apr 22 19:45:26 anubis Initializing CPU#1
Apr 22 19:45:26 anubis Calibrating delay using timer specific routine.. 5826.90 BogoMIPS (lpj=2913454)
Apr 22 19:45:26 anubis CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
Apr 22 19:45:26 anubis CPU: L2 Cache: 512K (64 bytes/line)
Apr 22 19:45:26 anubis CPU 1/0x1 -> Node 0
Apr 22 19:45:26 anubis CPU: Physical Processor ID: 0
Apr 22 19:45:26 anubis CPU: Processor Core ID: 1
Apr 22 19:45:26 anubis x86 PAT enabled: cpu 1, old 0x7040600070406, new 0x7010600070106
Apr 22 19:45:26 anubis CPU1: AMD Athlon(tm) 64 X2 Dual Core Processor 5600+ stepping 02
Apr 22 19:45:26 anubis CPU0 attaching NULL sched-domain.
Apr 22 19:45:26 anubis Switched to high resolution mode on CPU 1
Apr 22 19:45:26 anubis CPU0 attaching sched-domain:
Apr 22 19:45:26 anubis domain 0: span 0-1 level CPU
Apr 22 19:45:26 anubis groups: 0 1
Apr 22 19:45:26 anubis CPU1 attaching sched-domain:
Apr 22 19:45:26 anubis domain 0: span 0-1 level CPU
Apr 22 19:45:26 anubis groups: 1 0
Apr 22 19:45:26 anubis CPU1 is up
Apr 22 19:45:26 anubis ACPI: Waking up from system sleep state S3
Apr 22 19:45:26 anubis pcieport-driver 0000:00:04.0: setting latency timer to 64
Apr 22 19:45:26 anubis nForce2_smbus 0000:00:09.1: PME# disabled
..
Apr 22 19:45:26 anubis pcieport-driver 0000:00:15.0: setting latency timer to 64
Apr 22 19:45:26 anubis pcieport-driver 0000:00:17.0: setting latency timer to 64
Comment 1 Julien Cristau 2009-04-22 12:00:52 UTC 
the log you pasted seems to suggest you're using the nvidia driver.
that's not supported here.
Comment 2 Dobai-Pataky Balint 2009-04-22 22:20:10 UTC 
ok, but if i kill X than it works, that does not look like a nvidia hardware or driver problem to me. is it?
is this situation working with supported drivers?
should i test it with nv?
Comment 3 Adam Jackson 2018-06-12 18:43:31 UTC 
Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please file a new report if you continue to experience issues with a current server.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.