You are not logged in.
- Topics: Active | Unanswered
#1 2011-04-26 18:52:57
- ddr
- Member
- Registered: 2011-04-14
- Posts: 8
Sandy Bridge desktop (P67) fails to resume after suspend (s3)
I installed Archlinux x64 with latest kernel (2.6.38-4) and all available updates, but resuming after suspend does not work at all.
Hardware:
i5 2500K, Asus P8P67-M Pro, Asus Nvidia GT210, 8GB DDR3
This mainboard is the corrected B3 stepping version with latest BIOS (708), it does not have a video output, thus I'm using a separate graphics card.
What happens:
The machine properly suspends, video signal goes off, all fans stop, but when resuming (power button, keyboard press) it gets completely stuck:
Video signal won't come back, machine does not respond to ssh logins or even pings and telling from listening to the harddisk, it restarts itself 1-3 times.
Settings:
To somewhat limit the problem, I deactivated onboard sound, USB3 ports and eventually LAN port, but no success. No overclocking settings present. Reporting of C1, C3, C6 states is enabled.
I also tried not using any USB peripheral and using wake on lan to resume. Still no success.
From software side, I tried with and without proprietary Nvidia display drivers, no graphical environment installed. To suspend the machine, I used pm-suspend (with and without quirks) from terminal.
Frankly, on Windows 7 x64, resume & suspend works with onboard sound, USB3 and LAN.
Any hints on what to try next? Did anyone manage to properly suspend and resume on any Sandy Bridge mainboard? I'm running out of ideas... 
Here's my pm-suspend.log:
Initial commandline parameters:
Tue Apr 26 20:02:06 CEST 2011: Running hooks for suspend.
Running hook /usr/lib/pm-utils/sleep.d/00logging suspend suspend:
Linux myhost 2.6.38-ARCH #1 SMP PREEMPT Fri Apr 22 20:29:33 CEST 2011 x86_64 Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz GenuineIntel GNU/Linux
Module Size Used by
usb_storage 42951 0
uas 7824 0
ext2 62258 1
hid_apple 5026 0
usbhid 33814 0
hid 76802 2 hid_apple,usbhid
snd_hda_codec_hdmi 22378 4
snd_hda_intel 21738 0
snd_hda_codec 73739 2 snd_hda_codec_hdmi,snd_hda_intel
snd_seq_dummy 1455 0
snd_seq_oss 28052 0
snd_seq_midi_event 5332 1 snd_seq_oss
snd_seq 48705 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 5100 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss 37890 0
nvidia 10488718 0
snd_mixer_oss 14851 1 snd_pcm_oss
ehci_hcd 39177 0
snd_hwdep 6134 1 snd_hda_codec
snd_pcm 71032 4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_timer 18992 2 snd_seq,snd_pcm
snd 55132 11 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_hwdep,snd_pcm,snd_timer
eeepc_wmi 5297 0
soundcore 5986 1 snd
sparse_keymap 2952 1 eeepc_wmi
rfkill 14810 1 eeepc_wmi
usbcore 134859 5 usb_storage,uas,usbhid,ehci_hcd
intel_agp 10480 0
snd_page_alloc 7017 2 snd_hda_intel,snd_pcm
wmi 8083 1 eeepc_wmi
intel_gtt 13943 1 intel_agp
i2c_i801 7987 0
processor 23608 0
evdev 9178 0
iTCO_wdt 11053 0
iTCO_vendor_support 1857 1 iTCO_wdt
psmouse 52944 0
pcspkr 1843 0
serio_raw 4222 0
sg 24917 0
i2c_core 18740 2 nvidia,i2c_i801
button 4794 0
ext4 332976 1
mbcache 5649 2 ext2,ext4
jbd2 69632 1 ext4
crc16 1321 1 ext4
sd_mod 26276 4
ahci 20441 3
libahci 17966 1 ahci
libata 167694 2 ahci,libahci
scsi_mod 123282 5 usb_storage,uas,sg,sd_mod,libata
total used free shared buffers cached
Mem: 8181496 223132 7958364 0 7852 20528
-/+ buffers/cache: 194752 7986744
Swap: 15623208 0 15623208
/usr/lib/pm-utils/sleep.d/00logging suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/00powersave suspend suspend:
/usr/lib/pm-utils/sleep.d/00powersave suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/01grub suspend suspend:
/usr/lib/pm-utils/sleep.d/01grub suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/11netcfg suspend suspend:
/usr/lib/pm-utils/sleep.d/11netcfg suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend:
/usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/75modules suspend suspend:
/usr/lib/pm-utils/sleep.d/75modules suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/90clock suspend suspend:
/usr/lib/pm-utils/sleep.d/90clock suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend:
/usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/95led suspend suspend:
/usr/lib/pm-utils/sleep.d/95led suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend:
nVidia binary video drive detected, not using quirks.
/usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/99video suspend suspend:
kernel.acpi_video_flags = 0
/usr/lib/pm-utils/sleep.d/99video suspend suspend: success.
Tue Apr 26 20:02:07 CEST 2011: performing suspend
-------- file ends here ---------Update: Removed graphics card and Nvidia drivers (i.e. headless), triggered pm-suspend via ssh. Same effect as above.
Update 2: I added "memory_corruption_check_size=128K" / "...256K" to the kernel line in grub and tested pm-suspend in kernel 2.6.32 (lts), kernel 2.6.38.4 and 2.6.39.rc5. No combination worked.
Last edited by ddr (2011-04-30 18:16:05)
Offline
#2 2011-05-06 09:39:51
- lkraav
- Member
- Registered: 2011-04-08
- Posts: 37
Re: Sandy Bridge desktop (P67) fails to resume after suspend (s3)
i am experiencing same thing on gentoo, where 2.6.38.2 worked solid. can you try 2.6.38.2 and let me know how that works on your system?
Offline
#3 2011-05-09 20:17:54
- ddr
- Member
- Registered: 2011-04-14
- Posts: 8
Re: Sandy Bridge desktop (P67) fails to resume after suspend (s3)
Sorry for the late reply. I just tested downgrading to 2.6.38.2, but unfortunately it didn't work for me.
Which mainboard do you have? How do you initiate suspend? Back when it worked, did you use any quirks/kernel parameters/... ?
Offline
#4 2011-05-09 20:42:16
- lkraav
- Member
- Registered: 2011-04-08
- Posts: 37
Re: Sandy Bridge desktop (P67) fails to resume after suspend (s3)
i bisected my issue down to a commit that does saving radio states between reboots in acer-wmi. it doesnt look like you have a laptop that uses that.
Offline
#5 2011-05-09 20:46:10
- ddr
- Member
- Registered: 2011-04-14
- Posts: 8
Re: Sandy Bridge desktop (P67) fails to resume after suspend (s3)
Thanks for your answer. Yes, I have a desktop machine and only very few components (mainboard, cpu, graphics card, 1x hdd).
For networking, I use onboard LAN (which I disabled once, but didn't help).
Last edited by ddr (2011-05-09 20:47:39)
Offline
#6 2011-05-09 21:42:31
- phildg
- Member
- Registered: 2006-03-10
- Posts: 146
Re: Sandy Bridge desktop (P67) fails to resume after suspend (s3)
I have the same issue on a Asus P8P67 LE.
Google tells me it's a firmware/chipset bug. Apparantely if you disable Internal PLL voltage overclock, and upgrade to the latest BIOS suspen works. However, I haven't had any joy thus far.
Offline
#7 2011-05-09 22:09:45
- ddr
- Member
- Registered: 2011-04-14
- Posts: 8
Re: Sandy Bridge desktop (P67) fails to resume after suspend (s3)
@phildg
This is interesting. I've read reports from users with Asus P8P67 and P8P67 Pro boards, where suspend works. Note, the BIOS version across all boards is different.
What I came across so far:
* "Internal PLL overvoltage overclock" must be disabled, otherwise also Windows has problems suspending.
* CPU overclocking above a certain multiplier may cause suspend to fail both in Linux and in Windows.
* Earlier kernels had problems with the USB3 module. Kernel 2.6.37+ has such a module built in, so no manual unloading needed.
* "Wake up on PCIe - enabled" might help with suspend issues.
* Some mainboards leave low mem in a corrupt state when suspending/resuming. Adding "... memory_corruption_check_size=128K ..." to kernel line in /boot/grub/menu.lst forces the kernel to scan a larger area for corruptions (default 64K)
* Ubuntu has an option to trace kernel actions when performing a suspend:
sudo sh -c "sync; echo 1 > /sys/power/pm_trace; pm-suspend"
After waking up, the trace can be checked by dmesg output. Lines with "hash matches" may give hints to which modules might break the process.
* Ubuntu: By
sudo sh -c "echo 'core' > /sys/power/pm_test"
before performing a suspend, the machine does everything except for actually calling the lowest level hardware actions and thus wakes up after a few seconds. It is useful for finding bad modules.
* Command s2ram has a few combinations of options, which can be tried. So far, I had no success.
* One person on a sandy bridge laptop had success by disabling the virtualisation option in BIOS settings.
I'm guessing, my mainboard's BIOS has buggy ACPI related code, which Windows 7 correctly understands.
Still, I'm happy for any hint that could help.
Last edited by ddr (2011-05-09 22:11:41)
Offline
#8 2011-05-09 22:24:04
- phildg
- Member
- Registered: 2006-03-10
- Posts: 146
Re: Sandy Bridge desktop (P67) fails to resume after suspend (s3)
It sounds like you're much further down this path than me!!
I'd be interested to hear if/when you find a solution, and I'll do the same.
Another thing I've read is that 4GB DIMMS could cause a problem with suspend - I have 4 of them.
I've not had mine very long and currently the PSU is too underpowered so I've not done much investigation yet for fear of damaging it. Next week I'll have a proper go at it.
Offline
#9 2011-05-09 22:34:46
- ddr
- Member
- Registered: 2011-04-14
- Posts: 8
Re: Sandy Bridge desktop (P67) fails to resume after suspend (s3)
Nice to see somebody else is also working on it!
I know for a fact, that suspend/resume works flawlessly in Windows 7 with 2x 4GB DIMMs. It does hibernation and suspend to ram at the same time (tested it).
Keep in mind that the current Nvidia driver (is one of many that) may break suspend. In any case, test it from bash without Gnome/KDE.
Also, this bug report is helpful: https://bugs.launchpad.net/ubuntu/+sour … bug/760842
Offline
#10 2011-05-23 00:45:38
- dimpard
- Member
- Registered: 2008-12-30
- Posts: 10
Re: Sandy Bridge desktop (P67) fails to resume after suspend (s3)
I have a Toshiba Satellite U500 laptop ( nvidia GeForce 310M) running Arch and having the same pm-suspend.log as yours.
I've also tried a lot different suggestions with no success. Finally I' ve found this fix: http://thecodecentral.com/2011/01/18/fi … rking-bug/ which works fine for the suspend - hibernate problem.
Offline
#11 2011-05-23 06:20:06
- 65kid
- Member
- From: Germany
- Registered: 2011-01-26
- Posts: 663
Re: Sandy Bridge desktop (P67) fails to resume after suspend (s3)
I had the same problem on an Intel DH67GD (B2 and B3), updating my BIOS fixed it for me, see also https://bugs.freedesktop.org/show_bug.cgi?id=35462 .
If a BIOS update doesn't fix it for you, you should comment on this bug. Although I wouldn't be surprised if ASUS simple hasn't fixed this in their BIOS yet.
Offline
#12 2011-05-23 16:33:52
- Drexya
- Member
- Registered: 2009-07-28
- Posts: 23
Re: Sandy Bridge desktop (P67) fails to resume after suspend (s3)
Wow, many thanks for the link dimpard, the script worked on a desktop computer with an Asus P5QL-Pro motherboard!
Sorry for my poor english.
Offline
#13 2011-05-24 21:46:02
- ddr
- Member
- Registered: 2011-04-14
- Posts: 8
Re: Sandy Bridge desktop (P67) fails to resume after suspend (s3)
Thanks for all your answers!
@dimpard: I've seen that this fixes suspend for many people. Still, I believe, it's targeted at the buggy USB3 support we had before kernel 2.6.37. The most recent kernel includes an USB3 modul ("ehci" if I'm not mistaken). Unfortunately it didn't work in my case.
@65kid: That bugreport is really helpful! So, it definitely is a BIOS bug. As you said, up until now, ASUS hasn't addressed this issue (because it's not present in Windows...). I'm curious to try out the mentioned kernel patches, although I'm not yet sure how to do it and if it works for non-Intel mainboards. I'll report back, if I manage to pull it off!
Offline
#14 2011-05-25 17:20:50
- ddr
- Member
- Registered: 2011-04-14
- Posts: 8
Re: Sandy Bridge desktop (P67) fails to resume after suspend (s3)
With the help of Arch-wiki I patched the kernel and compiled it from source. However, it was no success, probably because it's targeted at the Intel video driver (that I don't use).
I commented on the freedesktop bugtracker and maybe there'll be progress.
Offline
#15 2011-07-28 14:49:45
- hirnsaege
- Member
- Registered: 2011-07-28
- Posts: 1
Re: Sandy Bridge desktop (P67) fails to resume after suspend (s3)
Hello,
is there any progress on this issue?
My setup:
Kernel 2.6.39 from core
Asus P8H67-M Pro
Intel Core i5 2500S
ATI Radeon 5670 (Sapphire)
8 GB Crucial RAM (2x 4GB DDR3-1333MHz)
1 TB SATA 6GBit HDD (2x)
Workarounds I've tried on this without success:
* Disabling USB 3.0 in EFI
* Disabling Intel Virtualization Technology in EFI
* Enabling Wake from PCIE in EFI
* Resetting EFI to default values
* Removing acpi_cpufreq prior to suspending
* Switching from radeon to catalyst
* Various switches for s2ram (not all, to be honest, but many)
Symptoms are the same as the OP's:
1) Machine suspends fine, disks spin down, fans stop spinning.
2) Upon wakeup, disks are spun up, fans start blowing, then, after 1 second or so the whole thing powers down again.
3) This repeats 2-3 times (interval between powerdown and powerup is about 30 secs).
4) After a few "tries", the computer stays powered up but the screen doesn't come back on - caps lock, num lock etc don't work.
5) Hard reset helps to exit from this state.
Offline
#16 2011-07-29 23:10:46
- button
- Member
- Registered: 2011-07-29
- Posts: 2
Re: Sandy Bridge desktop (P67) fails to resume after suspend (s3)
Hi, I have the same issue on P8P67 LE, so it is not only P8H67-M mobos problem. It looks exactly like @hirnsaege and predecessors described. Most important think is, that it works with Windows 7, which probably, in contrast to Linux, can handle some ACPI bugs in bios.
Offline
#17 2011-07-30 02:06:22
- Griemak
- Member
- Registered: 2011-05-10
- Posts: 46
Re: Sandy Bridge desktop (P67) fails to resume after suspend (s3)
I have an Asus P8P67 and have not noticed these symptoms, though I hibernate rarely, it has successfully done it when I do. I did notice a difference in kernel modules compared to you.
ipv6 262525 28
coretemp 4994 0
nvidia 11779389 40
snd_hda_codec_hdmi 21872 4
eeepc_wmi 2207 0
asus_wmi 12644 1 eeepc_wmi
joydev 9671 0
sparse_keymap 2984 1 asus_wmi
intel_agp 10608 0
intel_gtt 13911 1 intel_agp
i2c_i801 7329 0
snd_hda_codec_realtek 292575 1
firewire_ohci 28469 0
ide_pci_generic 2996 0
rfkill 14650 1 asus_wmi
snd_hda_intel 21418 4
firewire_core 48103 1 firewire_ohci
ide_core 72718 1 ide_pci_generic
iTCO_wdt 12557 0
i2c_core 18681 2 nvidia,i2c_i801
iTCO_vendor_support 1825 1 iTCO_wdt
snd_hda_codec 73639 3 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel
pci_hotplug 24832 1 asus_wmi
sg 25045 0
evdev 9210 6
psmouse 52912 0
r8169 38899 0
mii 3795 1 r8169
serio_raw 4062 0
pcspkr 1811 0
snd_hwdep 6006 1 snd_hda_codec
snd_pcm 71224 4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
snd_timer 18768 1 snd_pcm
snd 54632 14 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
soundcore 5986 1 snd
crc_itu_t 1321 1 firewire_core
wmi 8243 1 asus_wmi
snd_page_alloc 6825 2 snd_hda_intel,snd_pcm
button 4238 0
cpufreq_ondemand 5996 4
acpi_cpufreq 5665 1
freq_table 2379 2 cpufreq_ondemand,acpi_cpufreq
processor 23320 1 acpi_cpufreq
mperf 1267 1 acpi_cpufreq
ext4 363298 3
mbcache 5585 1 ext4
jbd2 69132 1 ext4
crc16 1321 1 ext4
dm_mod 63753 9
usbhid 33860 0
hid 78179 1 usbhid
sr_mod 14471 0
cdrom 35945 1 sr_mod
sd_mod 26771 3
ahci 20665 2
libahci 18077 1 ahci
xhci_hcd 64515 0
ehci_hcd 38383 0
usbcore 135813 4 usbhid,xhci_hcd,ehci_hcd
scsi_mod 125860 4 sg,sr_mod,sd_modASUS P8P67
ASUS DVD/CD SATA drive (Sata II port used)
Seagate SATA III drive (Sata III 6 Gbps AHCI port used: one of the Intel ones)
I5-2500K
Nvidia GT560ti
8GB memory, 2 4GB modules (1600, I think, haven't been in BIOS in a while)
The thing that pops out at me are the 'asus_wmi' and 'xhci_hcd' modules are missing. According to this:
http://lwn.net/Articles/429993/
the asus_wmi kernel module has all of the eeepc wmi instructions + new ones. You are missing the "cleaned-up" and "new" parts of the module. Perhaps this may help? I also point out xhci hcd module, as this is the support for USB 3.0.
In addition, snd_oss is running, which is odd. The Intel HD Audio on all of our Asus boards shouldn't load this way... The "HD HDMI" audio stuff I have is for my Nvidia card, as it can output audio on the HDMI port (ignore, move along, lol)
There are only two ways to live your life: One is as though nothing is a miracle. The other is as though everything is a miracle. - Albert Einstein
How wonderful it is that nobody need wait a single moment before starting to improve the world. - Anne Frank
Offline
#18 2011-08-03 21:03:59
- button
- Member
- Registered: 2011-07-29
- Posts: 2
Re: Sandy Bridge desktop (P67) fails to resume after suspend (s3)
There are my modules:
msr 12759 0
pci_stub 12429 1
vboxpci 19059 0
vboxnetadp 13202 0
vboxnetflt 23595 0
acpi_cpufreq 13009 1
mperf 12453 1 acpi_cpufreq
cpufreq_powersave 12454 0
cpufreq_stats 12862 0
cpufreq_userspace 12576 0
cpufreq_conservative 13147 0
vboxdrv 194054 3 vboxpci,vboxnetadp,vboxnetflt
decnet 65647 0 [permanent]
fuse 62334 3
lm75 12722 0
coretemp 12939 0
loop 22711 0
firewire_sbp2 18062 0
firewire_core 48371 1 firewire_sbp2
crc_itu_t 12347 1 firewire_core
snd_hda_codec_hdmi 26321 1
arc4 12458 2
snd_hda_codec_realtek 278027 1
hid_a4tech 12524 0
radeon 648372 3
snd_hda_intel 26140 10
snd_hda_codec 72699 3 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel
rtl8180 35526 0
snd_seq 45208 0
snd_hwdep 13186 1 snd_hda_codec
ttm 52979 1 radeon
snd_pcm 68104 5 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
snd_seq_device 13137 1 snd_seq
i2c_i801 16870 0
mac80211 182631 1 rtl8180
snd_timer 22581 4 snd_seq,snd_pcm
drm_kms_helper 27216 1 radeon
snd 52823 25 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_seq,snd_seq_device,snd_pcm,snd_timer
drm 163231 5 radeon,ttm,drm_kms_helper
eeprom_93cx6 12455 1 rtl8180
eeepc_wmi 12519 0
psmouse 55656 0
asus_wmi 18554 1 eeepc_wmi
i2c_algo_bit 12850 1 radeon
soundcore 13152 1 snd
sparse_keymap 12795 1 asus_wmi
cfg80211 132564 2 rtl8180,mac80211
pci_hotplug 27232 1 asus_wmi
evdev 17558 11
mxm_wmi 12473 0
serio_raw 12846 0
snd_page_alloc 13043 2 snd_hda_intel,snd_pcm
pcspkr 12579 0
rfkill 19080 2 asus_wmi,cfg80211
i2c_core 23909 6 lm75,radeon,i2c_i801,drm_kms_helper,drm,i2c_algo_bit
power_supply 13475 1 radeon
wmi 13243 2 asus_wmi,mxm_wmi
processor 27942 9 acpi_cpufreq
button 12930 0
thermal_sys 17949 1 processor
ext4 313917 2
mbcache 13066 1 ext4
jbd2 62574 1 ext4
crc16 12343 1 ext4
usbhid 40516 0
hid 73172 2 hid_a4tech,usbhid
sg 25985 0
sd_mod 36259 5
sr_mod 21811 0
cdrom 35093 1 sr_mod
crc_t10dif 12348 1 sd_mod
ahci 25089 3
libahci 22767 1 ahci
libata 149043 2 ahci,libahci
scsi_mod 162442 5 firewire_sbp2,sg,sr_mod,sd_mod,libata
ehci_hcd 40090 0
r8169 42411 0
mii 12675 1 r8169
usbcore 124242 3 usbhid,ehci_hcdCPU: i7 2600K
Motherboard: Asus P8P67 LE
Video: Radeon 5770
2x4GB DDR3@1600
Suspend works only on Windows 7. I tried clean system, default bios setup, disabled PLL Overvoltage, turning on hotplug on SATAs, anything works 2-3 restarts and after that no signal on screen, can't connect via SSH.
Offline
#19 2011-08-22 18:48:52
- ddr
- Member
- Registered: 2011-04-14
- Posts: 8
Re: Sandy Bridge desktop (P67) fails to resume after suspend (s3)
These are my modules (specs as in the 1st post):
fuse 67290 3
appletalk 26298 0
ipx 20363 0
p8022 1171 1 ipx
psnap 1973 2 appletalk,ipx
llc 3761 2 p8022,psnap
p8023 1068 1 ipx
ipv6 290407 28
ext2 63674 1
snd_hda_codec_hdmi 22092 4
nvidia 11490300 42
autofs4 23735 0
eeepc_wmi 2247 0
nfs 306935 0
sg 25557 0
asus_wmi 13644 1 eeepc_wmi
lockd 73392 1 nfs
sparse_keymap 3088 1 asus_wmi
snd_hda_codec_realtek 294224 1
rfkill 15402 2 asus_wmi
snd_hda_intel 22122 4
pci_hotplug 25672 1 asus_wmi
snd_hda_codec 77927 3 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel
evdev 9530 12
mei 31249 0
i2c_i801 8187 0
psmouse 55224 0
mxm_wmi 1393 0
pcspkr 1819 0
serio_raw 4294 0
snd_hwdep 6325 1 snd_hda_codec
snd_pcm 73856 4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
snd_timer 19416 1 snd_pcm
i2c_core 20133 2 nvidia,i2c_i801
snd 57786 14 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
soundcore 6146 1 snd
snd_page_alloc 7121 2 snd_hda_intel,snd_pcm
intel_agp 10904 0
intel_gtt 14423 1 intel_agp
iTCO_wdt 12717 0
iTCO_vendor_support 1929 1 iTCO_wdt
button 4470 0
wmi 8411 2 asus_wmi,mxm_wmi
fscache 40810 1 nfs
auth_rpcgss 41587 1 nfs
nfs_acl 2327 1 nfs
sunrpc 196793 4 nfs,lockd,auth_rpcgss,nfs_acl
vboxdrv 1786526 0
cpufreq_ondemand 6132 4
acpi_cpufreq 5877 1
freq_table 2451 2 cpufreq_ondemand,acpi_cpufreq
processor 24256 1 acpi_cpufreq
mperf 1275 1 acpi_cpufreq
ext4 369556 1
mbcache 5817 2 ext2,ext4
jbd2 71074 1 ext4
crc16 1297 1 ext4
xts 2493 4
gf128mul 5890 1 xts
usbhid 35256 0
hid 81635 2 hid_apple,usbhid
raid456 51997 1
async_raid6_recov 5454 1 raid456
async_pq 3510 2 raid456,async_raid6_recov
raid6_pq 78386 2 async_raid6_recov,async_pq
async_xor 2401 3 raid456,async_raid6_recov,async_pq
xor 4837 1 async_xor
async_memcpy 1366 2 raid456,async_raid6_recov
async_tx 1870 5 raid456,async_raid6_recov,async_pq,async_xor,async_memcpy
raid1 20960 1
md_mod 94833 4 raid456,raid1
sd_mod 28307 9
ahci 20865 6
libahci 18885 1 ahci
libata 173297 2 ahci,libahci
scsi_mod 131482 3 sg,sd_mod,libata
ehci_hcd 39511 0
usbcore 142544 3 usbhid,ehci_hcd
r8169 42643 0
mii 3995 1 r8169
aes_x86_64 7476 8
aes_generic 26106 1 aes_x86_64
dm_crypt 15945 1
dm_mod 67038 9 dm_cryptLast edited by ddr (2011-08-22 18:49:05)
Offline
#20 2011-11-28 21:23:35
- beta990
- Member
- Registered: 2011-07-10
- Posts: 207
Re: Sandy Bridge desktop (P67) fails to resume after suspend (s3)
Any solution? Have the same board..
Thanks! 
Offline
#21 2011-12-06 22:14:19
- ams
- Member
- Registered: 2011-12-06
- Posts: 12
Re: Sandy Bridge desktop (P67) fails to resume after suspend (s3)
I'm having the same problem with an Asus Z68 motherboard (P8Z68-V LX).
Has anyone been able to solve this (for any of the boards - P67, H67 or Z68).
Thanks.
Offline
#22 2011-12-20 16:20:57
- beta990
- Member
- Registered: 2011-07-10
- Posts: 207
Re: Sandy Bridge desktop (P67) fails to resume after suspend (s3)
Any solution?
@ams: did you managed to get suspend working again?
Offline
#23 2012-01-04 03:07:27
- pbhenson
- Member
- Registered: 2012-01-04
- Posts: 6
Re: Sandy Bridge desktop (P67) fails to resume after suspend (s3)
I have two Asus P8P67-M Pro systems which also fail to suspend. I suspect it is a BIOS issue.
Question -- when you try to suspend yours, does the power light blink slowly as it normally does when suspended? On both of mine, the power light just goes out completely and stays off when I try to suspend.
Also, when booting, mine log the following:
ACPI Error: [RAMB] Namespace lookup failure, AE_NOT_FOUND
(20110413/psargs-359)
ACPI Exception: AE_NOT_FOUND, Could not execute arguments for [RAMW]
(Region) (20110413/nsinit-349)
And while testing suspend, a similar ACPI error is logged:
[ 896.963921] ACPI: Preparing to enter system sleep state S3
[ 896.963973] ACPI Error: [RAMB] Namespace lookup failure, AE_NOT_FOUND
(20110112/ps
args-359)
[ 896.963982] ACPI Error: Method parse/execution failed [\_PTS] (Node
f3029e40), AE_
NOT_FOUND (20110112/psparse-536)
I have an open ticket with Asus but they've been less than helpful. I'm quite curious if your system logs the same ACPI errors, which would reinforce my belief they've got a buggy BIOS.
Offline
#24 2012-01-04 15:54:00
- beta990
- Member
- Registered: 2011-07-10
- Posts: 207
Re: Sandy Bridge desktop (P67) fails to resume after suspend (s3)
@pbhenson: Yes, I have the same problem. System goes off, so no blinking power-led.
When resuming the system goes on and off, and stays on - but does nothing to respone. The screen stays blank, cpu-fan goes to high speed.
I have already mailed to ASUS, also with all the logs + links to bug reports.
This is the answer:
Dear sir/ madam **,
Thank you for your email.
Do notice that we do not provide direct support for systems running Linux.
This doesn't mean that you cannot run Linux but it means that we cannot provide support for this.
As you found out there are no problems using Windows so there shouldn't be any problems with the mainboard.
It looks like the problem lies within the combination with Linux or in the Linux settings.
But as stated we cannot help you with problems under Linux.
I hope to have informed you enough.
Kind regards,
Asus TSD.
With other words no hope.
Last edited by beta990 (2012-01-04 15:54:30)
Offline
#25 2012-01-04 20:00:15
- ams
- Member
- Registered: 2011-12-06
- Posts: 12
Re: Sandy Bridge desktop (P67) fails to resume after suspend (s3)
I have the same ACPI errors on my log. Can't figure out what they refer to.
@pbhenson: could you please post the link on which you filled the ticket with Asus. I would like to fill one myself.
Last edited by ams (2012-01-04 22:35:49)
Offline