[SOLVED] Need an advice for suspend/hibernate problem

alexmj · 2011-10-08 08:50:39

Since suspending results in a blankscreen with a cursor at top left,
I look through some forum entries and found a solution so that
create a file-/etc/pm/config.d/modules
and put the modules listed by lsmod in it as
SUSPEND_MODULES="ath9k mac80211 atl1c xhci_hcd ehci_hcd scsi_mod ......."

What about inserting all modules listed by lsmod in the above file since i dont know
which module is fighting with suspend?

Last edited by alexmj (2012-02-01 12:45:30)

eldragon · 2011-10-08 14:23:45

no, find the offending module first. even if it takes a whole day.

alexmj · 2011-10-08 18:13:09

What's the problem if all modules are listed in SUSPEND_MODULES

diederick76 · 2011-10-17 11:15:41

How do I find the offending module(s)? The only way to continue after a "suspend" in this fashion is to shut down by pressing the power button a few seconds which afaik is not sa very good way to treat a hard drive.

bernarcher · 2011-10-17 12:07:56

@diederick76,

in case you wonder where your text has been gone- it was sent to the mods because you inadvertently used the "Report" button instead of the "Edit" one. This is what we received:

I have the exact same problem (Asus Pro 36S notebook). Whenever I do a suspend I end up with a frozen system with a non blinking cursor at the top left. The only way to get the notebook to do anything again is by pressing and holding the power button to switch if off, and I don't think my hard disk likes that. Can you explain why you think it is a bad idea to just list every module?

marvn · 2011-10-17 12:10:31

diederick76 wrote:

How do I find the offending module(s)? The only way to continue after a "suspend" in this fashion is to shut down by pressing the power button a few seconds which afaik is not sa very good way to treat a hard drive.

well, you can unload them all and then try load one by one and see when it's working and when it's not. it's not elegant, but the HDD should survive that...

orschiro · 2011-10-18 01:47:17

Hello,

Since the last kernel upgrade I experience the same problem with a blinking cursor on the top left of the black screen.

I really wonder why it should be related to unloaded modules as I didn't unload modules before and it worked.

Any other ideas what could cause the problem?

Regards

EDIT:

I was able to solve it by recompiling the virtualbox module which was needed to due to my kernel upgrade.

Last edited by orschiro (2011-10-18 07:23:02)

diederick76 · 2011-10-19 09:24:10

marvn wrote:

diederick76 wrote:
How do I find the offending module(s)? The only way to continue after a "suspend" in this fashion is to shut down by pressing the power button a few seconds which afaik is not sa very good way to treat a hard drive.
well, you can unload them all and then try load one by one and see when it's working and when it's not. it's not elegant, but the HDD should survive that...

When I do that, Instead of a black screen with just a cursor sitting at the top left, I get a black screen with what to me looks like a stack/call trace about process modprobe:

Oct 16 09:54:47 localhost kernel: [  570.687493] atl1c 0000:05:00.0: atl1c: eth0 NIC Link is Up<100 Mbps Full Duplex>
Oct 16 09:54:47 localhost dhcpcd[778]: eth0: carrier acquired
Oct 16 09:54:47 localhost dhcpcd[778]: eth0: rebinding lease of 192.168.1.101
Oct 16 09:54:52 localhost dhcpcd[778]: eth0: carrier lost
Oct 16 09:54:53 localhost kernel: [  576.361393] ------------[ cut here ]------------
Oct 16 09:54:53 localhost kernel: [  576.361414] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x257/0x260()
Oct 16 09:54:53 localhost kernel: [  576.361419] Hardware name: U36SD
Oct 16 09:54:53 localhost kernel: [  576.361424] NETDEV WATCHDOG: eth0 (atl1c): transmit queue 0 timed out
Oct 16 09:54:53 localhost kernel: [  576.361428] Modules linked in: appletalk ipx p8022 psnap llc p8023 ipv6 ext3 jbd snd_hda_codec_hdmi snd_hda_codec_realtek nvidia(P) joydev evdev sg snd_hda
_intel snd_hda_codec snd_hwdep snd_pcm snd_timer snd arc4 soundcore iwlagn i915 mac80211 drm_kms_helper drm uvcvideo videodev media asus_nb_wmi asus_wmi sparse_keymap cfg80211 mei(C) v4l2_comp
at_ioctl32 pci_hotplug serio_raw i2c_algo_bit i2c_i801 psmouse i2c_core iTCO_wdt mxm_wmi wmi intel_agp intel_gtt atl1c pcspkr video iTCO_vendor_support snd_page_alloc rfkill thermal battery pr
ocessor ac button ext4 mbcache jbd2 crc16 sd_mod ahci libahci ehci_hcd libata scsi_mod xhci_hcd usbcore
Oct 16 09:54:53 localhost kernel: [  576.361514] Pid: 0, comm: swapper Tainted: P         C  3.0-ARCH #1
Oct 16 09:54:53 localhost kernel: [  576.361516] Call Trace:
Oct 16 09:54:53 localhost kernel: [  576.361518]  <IRQ>  [<ffffffff8105c87f>] warn_slowpath_common+0x7f/0xc0
Oct 16 09:54:53 localhost kernel: [  576.361526]  [<ffffffff8105c976>] warn_slowpath_fmt+0x46/0x50
Oct 16 09:54:53 localhost kernel: [  576.361529]  [<ffffffff8106d451>] ? mod_timer+0x141/0x360
Oct 16 09:54:53 localhost kernel: [  576.361533]  [<ffffffff81350bc7>] dev_watchdog+0x257/0x260
Oct 16 09:54:53 localhost kernel: [  576.361536]  [<ffffffff8106c991>] run_timer_softirq+0x131/0x440
Oct 16 09:54:53 localhost kernel: [  576.361539]  [<ffffffff81350970>] ? qdisc_reset+0x50/0x50
Oct 16 09:54:53 localhost kernel: [  576.361543]  [<ffffffff81012eb9>] ? read_tsc+0x9/0x20
Oct 16 09:54:53 localhost kernel: [  576.361546]  [<ffffffff81063e40>] __do_softirq+0xb0/0x270
Oct 16 09:54:53 localhost kernel: [  576.361550]  [<ffffffff81091068>] ? tick_dev_program_event+0x48/0x110
Oct 16 09:54:53 localhost kernel: [  576.361552]  [<ffffffff8109114f>] ? tick_program_event+0x1f/0x30
Oct 16 09:54:53 localhost kernel: [  576.361555]  [<ffffffff813f5e9c>] call_softirq+0x1c/0x30
Oct 16 09:54:53 localhost kernel: [  576.361558]  [<ffffffff8100da75>] do_softirq+0x65/0xa0
Oct 16 09:54:53 localhost kernel: [  576.361560]  [<ffffffff8106434e>] irq_exit+0x9e/0xc0
Oct 16 09:54:53 localhost kernel: [  576.361563]  [<ffffffff813f67de>] smp_apic_timer_interrupt+0x6e/0x99
Oct 16 09:54:53 localhost kernel: [  576.361567]  [<ffffffff813f5653>] apic_timer_interrupt+0x13/0x20
Oct 16 09:54:53 localhost kernel: [  576.361568]  <EOI>  [<ffffffff81273d7b>] ? intel_idle+0xcb/0x120
Oct 16 09:54:53 localhost kernel: [  576.361574]  [<ffffffff81273d5d>] ? intel_idle+0xad/0x120
Oct 16 09:54:53 localhost kernel: [  576.361578]  [<ffffffff81313e3d>] cpuidle_idle_call+0x9d/0x350
Oct 16 09:54:53 localhost kernel: [  576.361582]  [<ffffffff8100a21a>] cpu_idle+0xba/0x100
Oct 16 09:54:53 localhost kernel: [  576.361585]  [<ffffffff813d1f52>] rest_init+0x96/0xa4
Oct 16 09:54:53 localhost kernel: [  576.361588]  [<ffffffff81748c23>] start_kernel+0x3de/0x3eb
Oct 16 09:54:53 localhost kernel: [  576.361590]  [<ffffffff81748347>] x86_64_start_reservations+0x132/0x136
Oct 16 09:54:53 localhost kernel: [  576.361593]  [<ffffffff81748140>] ? early_idt_handlers+0x140/0x140
Oct 16 09:54:53 localhost kernel: [  576.361595]  [<ffffffff8174844d>] x86_64_start_kernel+0x102/0x111
Oct 16 09:54:53 localhost kernel: [  576.361598] ---[ end trace 5f840dc55c3d6a78 ]---
Oct 16 09:54:53 localhost kernel: [  576.382131] atl1c 0000:05:00.0: atl1c: eth0 NIC Link is Up<100 Mbps Full Duplex>
Oct 16 09:54:53 localhost dhcpcd[778]: eth0: carrier acquired
Oct 16 09:54:53 localhost dhcpcd[778]: eth0: rebinding lease of 192.168.1.101
Oct 16 09:54:53 localhost dhcpcd[778]: eth0: acknowledged 192.168.1.101 from 192.168.1.1
Oct 16 09:54:54 localhost dhcpcd[778]: eth0: checking for 192.168.1.101
Oct 16 09:54:59 localhost dhcpcd[778]: eth0: leased 192.168.1.101 for 86400 seconds

I think this means I removed a module that I shouldn't have. Am I correct?

Oddly, while I was looking at that screen, the FN-keys which allow me to set the screen brightness still worked. Does that mean that the system is not frozen at all? Still, nothing else seemed to work, so turning off the computer by pressing the power button for a few seconds was the only way to continue.

After this happened to me, I removed a few module names from the SUSPEND_MODULES string, leaving these:

SUSPEND_MODULES="snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec joydev snd_hwdep snd_pcm snd_timer snd soundcore iwlagn snd_page_alloc asus_nb_wmi asus_wmi nvidia rfkill uvcvideo videodev media v4l2_compat_ioctl32 i2c_algo_bit i2c_i801 pcspkr button atl1c wmi i2c_core"

It still happened. Which of these could be the one I definately shouldn't unload?

diederick76 · 2011-10-19 09:38:26

Just yet, I found my dmesg output contained this line:

[   16.173877] mei: module is from the staging directory, the quality is unknown, you have been warned.

And now it appears, that if I remove that module, I can in fact suspend the notebook :-)

I should also mention, that my /etc/pm/sleep.d directory contains a file 20_custom-ehci_hcd which I got from http://thecodecentral.com/2011/01/18/fi … orking-bug

This isn't my thread, but I think I will consider this one solved for Asus U36SD notebooks.

Can someone tell me where I can find what this module actually does?

Last edited by diederick76 (2011-10-19 15:10:36)

alexmj · 2012-02-01 12:43:39

In my case the offending module was vboxdrv.So I edited
/etc/pm/config.d/modules as
SUSPEND_MODULES="vboxdrv"

Now suspend works fine.

Arch Linux

#1 2011-10-08 08:50:39

[SOLVED] Need an advice for suspend/hibernate problem

#2 2011-10-08 14:23:45

Re: [SOLVED] Need an advice for suspend/hibernate problem

#3 2011-10-08 18:13:09

Re: [SOLVED] Need an advice for suspend/hibernate problem

#4 2011-10-17 11:15:41

Re: [SOLVED] Need an advice for suspend/hibernate problem

#5 2011-10-17 12:07:56

Re: [SOLVED] Need an advice for suspend/hibernate problem

#6 2011-10-17 12:10:31

Re: [SOLVED] Need an advice for suspend/hibernate problem

#7 2011-10-18 01:47:17

Re: [SOLVED] Need an advice for suspend/hibernate problem

#8 2011-10-19 09:24:10

Re: [SOLVED] Need an advice for suspend/hibernate problem

#9 2011-10-19 09:38:26

Re: [SOLVED] Need an advice for suspend/hibernate problem

#10 2012-02-01 12:43:39

Re: [SOLVED] Need an advice for suspend/hibernate problem

Board footer