Is it possible to resume from hibernate without initrd?

I succesfully build kernel without initrd dependency. It works great. Except hibernation. It can hibernate (or suspend-to-ram) but resume is not executed. It boots normally. So is it possible to resume without initrd?

Hi
As far as I know you have to press the power button in order to resume from sleep mode.
I didnt find any option or way in order to be able to wakeup the notebook pressing any keyboard button.
Greets

Similar Messages

Nex X61 Resumes from Hibernate Unexpectedly

My new X61 resumes from Hibernate without any intervention from me at completely unexpected times. Sometimes it will stay in Hibernate for several hours, other times just for a few seconds. I've only noticed the resume when the computer is docked to an Ultrabase and connected to AC power.
Does anyone have a suggestion regarding how to keep the computer in Hibernate until I want it to resume?
Thanks in Advance
X61 - Type: 7675-CTO

Are you certain you mean hibernate and not standby Deans? Hibernate is when you save the OS state and all of your open applications and files to the HD and the machine then shuts down completely.
In standby your system's state is saved to memory and then the laptop goes into a sleep state. It can be awakened from this sleep state by several things, including a depleted battery.
It's nigh unto impossible for a laptop to wake itself from hibernate absent receiving a machine specific "magic packet" via ethernet.
Regards,
James
Regards,
James
Full disclosure, I don't work for Lenovo.
James at Thinkpads dot com

USB Mouse / Keyboard doesn't work after resuming from hibernate

I am using a USB device that splits out to 2 PS2 ports, one for a mouse, one for a keyboard. It works great, but when I put my X61 into hibernate, the mouse and keyboard do not work when I resume from hibernate.
I installed all the relevant patches and power manager drivers from the driver downloads page, but my mouse still doesn't work.
Can someone point me to the correct download or shed some light on this?
Thank you!

I have this same problem with this same device. It is a "composite USB device".
What I've notice is that the problem happens mostly with USB 1.1 ports. When the device is connected to a USB 2.0 port the problem doesn't happen always.
It depends on the computer though. I added a PCMCIA USB 2.0 adaptor to my laptop that has USB 1.1 only. And when I connect the USB-to-PS/2 cable to the USB 2.0 my mouse sometimes work after suspend/hibernate but sometimes doesn't.
However, on my other desktop computer, which has integrated USB 2.0 ports, this problem has never happened (I haven't tested it exhaustively though).
This is a Windows bug of course. Everything related to USB 1.1 support is buggy in Windows. One more example is the annoying (and possibly catastrophic) "Delayed write error" that appears when you use a external hard drive plugged to a USB 1.1 port.
I guess M$ is focusing their efforts on making USB 2.0 to work well and they have forgotten about USB 1.1. Or it could a problem related to "USB composite devices", hard to know.
Message Edited by getfree on 02-22-2009 03:19 PM

Usb gone after resume from hibernate (since update?)

Hello!
Since a recent update, my wireless usb stick's interface isn't available any more after resume from hibernate. Removing it and connecting it to a different USB port does not help.
lsusb says, the device itsself is there.
I can see it being removed / added when I connect it to a different usb port.
The only interface iwconfig / ifconfig list is "lo" though. No wlan0 available.
No idea what to try next... any hints?
thx!
Last edited by whoops (2012-03-20 06:22:01)

Have there been issues with updates?
A while after that, my usb mouse/keyboard stopped working after resume, too.
Then after a few days, wifi started working...
Then usb input started working again...
Now usb input devices stopped working again -.-
I think there were updates (kernel, too) every time the behaviour changed... not sure though...
Still no idea what to do.

Ncf flaky/unpredictable when resuming from hibernate/standby onlaptops

I have noticed on my own laptop, and some of my customers are complaining about the same thing... many times when you resume from either hibernate or standby, the client firewall, either does not allow any traffic, or only some of the allowed applications.
It is simply a matter of unloading and reloading ncf to fix this, but the end-users do not like this, and each time they run into it, usually results in a call to the IT staff.
Is this a known bug? Is there any solution for it?
Thanks.

i don't know if novell has acknowledged this as a real bug or not but i
used to see this happen. it was consistent if the IP address changed
when you came out of hibernate... say you're at a hotel and it's using
DHCP to hand out IP#s for high-speed. in the AM, you check your email
and hibernate for the drive to the jobsite. Once there, you
de-hibernate and the jobsite uses DHCP as well. You grab a new IP#
from the DHCP server when the NIC comes back to life and NCF goes off
the deep end. As a consultant, I ran into this alot and wrote a couple
simple BATs to work around it:
to stop:
net stop "novell client firewall service"
PING 1.1.1.1 -n 1 -w 1000 >NUL
to start:
net start "novell client firewall service"
PING 1.1.1.1 -n 1 -w 1000 >NUL
"C:\Program Files\NovellClientFirewall\NCF.EXE" /waitservice
You run the stop right before you hibernate and then the start right
after. The downside was the minimal exposure window. All that said, I
haven't had it happen in maybe 4-5 months so you might want to check
the auto update and see if the clients are running the latest version.
Cheers!
Richard Beels
http://www.dsi-consulting.com
Collaboration without complication

Running xscreensaver in the background after resume from hibernate

I'm using hibernate-script with my tuxonice kernel. One of the things that annoys me about xscreensaver is how when I resume its always running (because the requisite time has passed), so I have to type my password again, having just typed it at BIOS level.
So I killall xscreensaver in an OnSuspend in /etc/hibernate/common.conf. However, restarting xscreensaver doesn't go to the background. What I'm using is this:-
OnResume 20 sudo -b -u MYUSERNAME /usr/bin/xscreensaver
However the terminal that I typed sudo hibernate from never returns, I have to killall xscreensaver from another terminal to get it to release. The problem does not occur when I login to a vt as root and run the same command.
Any suggestions?

I just registered for the forum so I could toss in my solution, so I hope this is what you're looking for. I fork the process and use the 'disown' command. I also use Dan Bernstein's 'setuidgid' utility because I couldn't get it to work with su (I didn't try very hard):
OnResume 70 setuidgid USERNAME xscreensaver > /dev/null 2>&1 & disown
This works for me even if I execute hibernate and resume from a terminal, despite the fact that II get a "can't find display" error from the terminal.
Of course, the stdout and stderr redirect to /dev/null is not necessary. The 'disown' command removes the subprocess from the process table, so that the subprocess is no longer a child of the parent. It is cast off, essentially. I also use a similar command for restarting gkrellm because gkrellm sometimes fails to recognize my second battery after resume.
One quirk I have found is that hibernate will halt if a kill or killall fails. I thought this was happening because the kill command had returned a non-zero exit status. But I just discovered that forking a kill command prevents hibernate from halting when a kill fails, as in:
OnSuspend 20 killall xscreensaver > /dev/null 2>&1 &

I915 backtrace with linux-3.10.5 on resume from hibernate

uname -a wrote:Linux zuko 3.10.5-1-ARCH #1 SMP PREEMPT Mon Aug 5 08:04:22 CEST 2013 x86_64 GNU/Linux
I have xf86-video-intel 2.21.14-2. When I hibernate and resume, everything looks fine, but there is a backtrace in the journalctl logs. Then, after about an hour, the system hard powers off with no error report I can find.
Aug 12 21:58:07 zuko kernel: ---[ end trace 22acffad91f8e49a ]---
Aug 12 21:58:07 zuko kernel: [<ffffffff8107a550>] ? kthread_create_on_node+0x120/0x120
Aug 12 21:58:07 zuko kernel: [<ffffffff814ca32c>] ret_from_fork+0x7c/0xb0
Aug 12 21:58:07 zuko kernel: [<ffffffff8107a550>] ? kthread_create_on_node+0x120/0x120
Aug 12 21:58:07 zuko kernel: [<ffffffff8107a610>] kthread+0xc0/0xd0
Aug 12 21:58:07 zuko kernel: [<ffffffff81074380>] ? manage_workers.isra.23+0x2b0/0x2b0
Aug 12 21:58:07 zuko kernel: [<ffffffff810744a1>] worker_thread+0x121/0x3a0
Aug 12 21:58:07 zuko kernel: [<ffffffff81073ae7>] process_one_work+0x167/0x450
Aug 12 21:58:07 zuko kernel: [<ffffffff81081237>] async_run_entry_fn+0x37/0x130
Aug 12 21:58:07 zuko kernel: [<ffffffff8135b6bd>] async_resume+0x1d/0x50
Aug 12 21:58:07 zuko kernel: [<ffffffff8135b576>] device_resume+0xc6/0x1f0
Aug 12 21:58:07 zuko kernel: [<ffffffff8135adf4>] dpm_run_callback+0x44/0x90
Aug 12 21:58:07 zuko kernel: [<ffffffff8129b0e0>] ? pci_pm_suspend_noirq+0x1a0/0x1a0
Aug 12 21:58:07 zuko kernel: [<ffffffff8129b144>] pci_pm_restore+0x64/0xb0
Aug 12 21:58:07 zuko kernel: [<ffffffffa07786d6>] i915_pm_resume+0x16/0x20 [i915]
Aug 12 21:58:07 zuko kernel: [<ffffffffa077867f>] i915_resume+0x6f/0xb0 [i915]
Aug 12 21:58:07 zuko kernel: [<ffffffffa0778247>] __i915_drm_thaw+0x117/0x1b0 [i915]
Aug 12 21:58:07 zuko kernel: [<ffffffff814c0152>] ? mutex_lock+0x12/0x30
Aug 12 21:58:07 zuko kernel: [<ffffffffa07acec9>] intel_modeset_setup_hw_state+0x679/0xa60 [i915]
Aug 12 21:58:07 zuko kernel: [<ffffffffa07a2f24>] __intel_set_mode+0x4b4/0xcb0 [i915]
Aug 12 21:58:07 zuko kernel: [<ffffffffa07a18b2>] ironlake_crtc_disable+0x732/0x8c0 [i915]
Aug 12 21:58:07 zuko kernel: [<ffffffffa079d6c7>] assert_pch_pll+0x177/0x1e0 [i915]
Aug 12 21:58:07 zuko kernel: [<ffffffffa0778e96>] ? i915_read32+0x66/0x170 [i915]
Aug 12 21:58:07 zuko kernel: [<ffffffff810558ec>] warn_slowpath_fmt+0x4c/0x50
Aug 12 21:58:07 zuko kernel: [<ffffffff81055881>] warn_slowpath_common+0x61/0x80
Aug 12 21:58:07 zuko kernel: [<ffffffff814bcf77>] dump_stack+0x19/0x1b
Aug 12 21:58:07 zuko kernel: Call Trace:
Aug 12 21:58:07 zuko kernel: 0000000000000000 0000000089046004 ffff8803db5f5af0 ffffffff810558ec
Aug 12 21:58:07 zuko kernel: ffffffff81055881 ffff88042561c000 ffff88042561e6d0 0000000000000000
Aug 12 21:58:07 zuko kernel: 0000000000000009 ffff8803db5f5a58 ffffffff814bcf77 ffff8803db5f5a90
Aug 12 21:58:07 zuko kernel: Workqueue: events_unbound async_run_entry_fn
Aug 12 21:58:07 zuko kernel: Hardware name: LENOVO 2359CTO/2359CTO, BIOS G4ET90WW (2.50 ) 12/20/2012
Aug 12 21:58:07 zuko kernel: CPU: 0 PID: 4424 Comm: kworker/u16:0 Tainted: G W O 3.10.5-1-ARCH #1
Aug 12 21:58:07 zuko kernel: snd_pcm snd_page_alloc snd_timer snd soundcore video ac processor ext4 crc16 mbcache jbd2 dm_mod sr_mod cdrom sd_mod ehci_pci ahci xhci_hcd ehci_hcd libahci sdhci_pci firewire_ohci libata sdhci scsi_mod firewire_core mmc_core crc_itu_t usbcore usb_common [last unloaded: psmouse]
Aug 12 21:58:07 zuko kernel: Modules linked in: psmouse fuse md5 ecb ecryptfs cbc sha256_ssse3 sha256_generic encrypted_keys sha1_ssse3 sha1_generic
Aug 12 21:58:07 zuko kernel: PCH PLL state for reg c6014 assertion failure (expected off, current on), val=89046004
Aug 12 21:58:07 zuko kernel: WARNING: at drivers/gpu/drm/i915/intel_display.c:1091 assert_pch_pll+0x177/0x1e0 [i915]()
Aug 12 21:58:07 zuko kernel: ------------[ cut here ]------------
Aug 12 21:58:07 zuko kernel: ---[ end trace 22acffad91f8e499 ]---
Aug 12 21:58:07 zuko kernel: [<ffffffff8107a550>] ? kthread_create_on_node+0x120/0x120
Aug 12 21:58:07 zuko kernel: [<ffffffff814ca32c>] ret_from_fork+0x7c/0xb0
Aug 12 21:58:07 zuko kernel: [<ffffffff8107a550>] ? kthread_create_on_node+0x120/0x120
Aug 12 21:58:07 zuko kernel: [<ffffffff8107a610>] kthread+0xc0/0xd0
Aug 12 21:58:07 zuko kernel: [<ffffffff81074380>] ? manage_workers.isra.23+0x2b0/0x2b0
Aug 12 21:58:07 zuko kernel: [<ffffffff810744a1>] worker_thread+0x121/0x3a0
Aug 12 21:58:07 zuko kernel: [<ffffffff81073ae7>] process_one_work+0x167/0x450
Aug 12 21:58:07 zuko kernel: [<ffffffff81081237>] async_run_entry_fn+0x37/0x130
Aug 12 21:58:07 zuko kernel: [<ffffffff8135b6bd>] async_resume+0x1d/0x50
Aug 12 21:58:07 zuko kernel: [<ffffffff8135b576>] device_resume+0xc6/0x1f0
Aug 12 21:58:07 zuko kernel: [<ffffffff8135adf4>] dpm_run_callback+0x44/0x90
Aug 12 21:58:07 zuko kernel: [<ffffffff8129b0e0>] ? pci_pm_suspend_noirq+0x1a0/0x1a0
Aug 12 21:58:07 zuko kernel: [<ffffffff8129b144>] pci_pm_restore+0x64/0xb0
Aug 12 21:58:07 zuko kernel: [<ffffffffa07786d6>] i915_pm_resume+0x16/0x20 [i915]
Aug 12 21:58:07 zuko kernel: [<ffffffffa077867f>] i915_resume+0x6f/0xb0 [i915]
Aug 12 21:58:07 zuko kernel: [<ffffffffa0778247>] __i915_drm_thaw+0x117/0x1b0 [i915]
Aug 12 21:58:07 zuko kernel: [<ffffffff814c0152>] ? mutex_lock+0x12/0x30
Aug 12 21:58:07 zuko kernel: [<ffffffffa07acec9>] intel_modeset_setup_hw_state+0x679/0xa60 [i915]
Aug 12 21:58:07 zuko kernel: [<ffffffffa07a2f24>] __intel_set_mode+0x4b4/0xcb0 [i915]
Aug 12 21:58:07 zuko kernel: [<ffffffffa07a1a08>] ironlake_crtc_disable+0x888/0x8c0 [i915]
Aug 12 21:58:07 zuko kernel: [<ffffffff8105595a>] warn_slowpath_null+0x1a/0x20
Aug 12 21:58:07 zuko kernel: [<ffffffff81055881>] warn_slowpath_common+0x61/0x80
Aug 12 21:58:07 zuko kernel: [<ffffffff814bcf77>] dump_stack+0x19/0x1b
Aug 12 21:58:07 zuko kernel: Call Trace:
Aug 12 21:58:07 zuko kernel: 00000000000e0300 ffff88042772e800 ffff8803db5f5b30 ffffffff8105595a
Aug 12 21:58:07 zuko kernel: ffffffff81055881 ffff880427096000 ffff88042561e6d0 ffff88042561c000
Aug 12 21:58:07 zuko kernel: 0000000000000009 ffff8803db5f5ae8 ffffffff814bcf77 ffff8803db5f5b20
Aug 12 21:58:07 zuko kernel: Workqueue: events_unbound async_run_entry_fn
Aug 12 21:58:07 zuko kernel: Hardware name: LENOVO 2359CTO/2359CTO, BIOS G4ET90WW (2.50 ) 12/20/2012
Aug 12 21:58:07 zuko kernel: CPU: 0 PID: 4424 Comm: kworker/u16:0 Tainted: G O 3.10.5-1-ARCH #1
Aug 12 21:58:07 zuko kernel: snd_pcm snd_page_alloc snd_timer snd soundcore video ac processor ext4 crc16 mbcache jbd2 dm_mod sr_mod cdrom sd_mod ehci_pci ahci xhci_hcd ehci_hcd libahci sdhci_pci firewire_ohci libata sdhci scsi_mod firewire_core mmc_core crc_itu_t usbcore usb_common [last unloaded: psmouse]
Aug 12 21:58:07 zuko kernel: Modules linked in: psmouse fuse md5 ecb ecryptfs cbc sha256_ssse3 sha256_generic encrypted_keys sha1_ssse3 sha1_generic
Aug 12 21:58:07 zuko kernel: WARNING: at drivers/gpu/drm/i915/intel_display.c:1656 ironlake_crtc_disable+0x888/0x8c0 [i915]()
Aug 12 21:58:07 zuko kernel: ------------[ cut here ]------------
Last edited by rpglover64 (2013-08-13 12:33:32)

rpglover64, when pasting configs, code or command output, please use [ code ] tags, not [ quote ] tags https://bbs.archlinux.org/help.php#bbcode
like this
It makes the code more readable and - in case of longer listings - more convenient to scroll through.

Kernel panic when resuming from hibernate with SSD drive

Hi,
i've got a the system described down below.
And because i've got another hd in my laptop (instead of the superdrive) i need to hibernate otherwise my mac will crash after few seconds i make it wake up from sleep.
I've removed the 2nd hd and tried hibernating and it crashes after a little while the progress bar appears. And the the "please hold the power button" screen appears.
Here is what i get:
Interval Since Last Panic Report: 215163 sec
Panics Since Last Report: 2
Anonymous UUID: A67D237A-36E8-4FCD-B352-F20B3E537B23
Mon Oct 25 12:56:21 2010
panic(cpu 0 caller 0x528e19): "Hibernate restore error e00002d5"@/SourceCache/xnu/xnu-1504.7.4/iokit/Kernel/IOHibernateIO.cpp:2403
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
A lot of people with other SSD and newer MacBook Pros seem to have the same issue!
http://forum.corsair.com/v3/showthread.php?p=470361
Is there a software/setting solution or is it an SSD/Apple hardware issue??
THANKS

Disconnect all peripherals from your computer & try the suggestions mentioned in User Tips: Kernel Panics.

Xfce4 will not lock screen after resume from hibernate/suspend

There have been a lot previous threads about this issue.
I cannot fix it. Furthermore, it's somewhat confusing.
Since this is a single user system (literally), I can get away with a systemd powered hack:
[Unit]
Description=Lock screen before switching power state
Before=sleep.target
[Service]
Type=oneshot
ExecStart=/usr/bin/sudo -u gebruiker xscreensaver-command -lock
[Install]
WantedBy=sleep.target
Is this a bug? Anyone who can report this functionality works?. I have:
xflock4 installed and working
xscreensaver installed and working
systemd working properly
no errors in ~/.xsession-errors
both config items ticked in
- xfce4-session
- xfce4-power-manager
Anyone?

Anyone who can report this functionality works?
Using the first option from the xscreensaver wiki article:
[Unit]
Description=Lock X session using xscreensaver
Before=sleep.target
[Service]
Type=oneshot
ExecStart=/usr/bin/xuserrun /usr/bin/xscreensaver-command -lock
[Install]
WantedBy=sleep.target
...in conjunction with:
both config items ticked in
- xfce4-session
- xfce4-power-manager
...and fade to and fade from disabled, works here for me.

Resume from Sleep / Hibernate issues

Hi all,
First time poster. I have a Helix and am running into a heap of resume from sleep (and hibernate) issues.
The sleep issues tend to happen overnight - I do not have this issue if I sleep the machine and then wake it up 5-10 minutes later (e.g. moving between meetings at work). However, when I attempt to wake the machine up in the morning, it fails to resume from sleep, and instead boots from scratch.
Typically, when the unit is in this state, the status led on the lid is rapidly blinking (which I believe means that it's trying to enter sleep) Since there is nothing in the Windows event log during the overnight period, I'm wondering whether it's trying to enter a deeper sleep mode and failing.
This happens every second day or so. Which is really frustrating as a tend to lose some work.
I tried enabling hibernate as a trial, to see if that would avoid the issue, but resuming from hibernate fails as well. At least I get a Windows event log entry for this (source: kernel-power. The unit fails to resume from hibernate with status 0xC000000D)
I have the September 10 BIOS update, and am running Windows 8.1 Enterprise (though I had the issue with Windows 8 as well).
Any ideas on how I can troubleshoot this?
Regards
AC

Windows 8: In Windows 8, the default shutdown behavior puts the system into hybrid shutdown (S4) and all devices are put into D3. Remote wake from hybrid shutdown (S4) or classic shutdown (S5) is completely unsupported. In Windows 8, NICs are explicitly not armed for wake in both the classic shutdown (S5) and hybrid shutdown (S4) cases because users expect zero power consumption and battery drain in the shutdown state. This behavior removes the possibility of spurious wakes when explicit shutdown was requested. As a result, Wake-On-LAN is only ever supported from sleep (S3) or hibernate (S4) in Windows 8.
Note that in Windows 8, hybrid shutdown (S4) stops user sessions but the contents of kernel sessions are written to hard disk. This enables faster boot.
http://msdn.microsoft.com/en-us/library/windows/desktop/aa373229(v=vs.85).aspx
From the Helix User Guide:
•Slow blinking: The tablet is in sleep mode.
•Fast blinking: The tablet is entering hibernation mode or sleep mode.
That was my reason for clarifying if hybrid-sleep was enabled; since it's the default setting and you noted that the LED was blinking fast. Does the LED ever stop blinking fast?
There can/may be multiple log entries during a normal sleep operation, because "the system uses the lowest-powered sleep state supported by all enabled wake-up devices." If one of those devices wakes the system (this does not mean power on) then the logs will report the devices and will likely return to a another level of sleep, but this does not mean full power loss or empty logs.
If the system has successfully entered sleep state, then you should see the following message in System Event logs.
Event 42, Kernel - Power
This system is entering sleep.
Sleep Reason: Button or lid
When the system is successfully woke you will see a System Event Log similar to this:
Event 1, Power - Troubleshooter
The system has returned from a low power state.
Sleep time: 2013-10-08T01:42:25.XXXXXXXX
Wake time: 2013-10-08T05:53:21.XXXXXXXX
However, there will be other events in the logs after sleep and prior to this wake period, such as hardware device issues(My helix has Bluetooth device warnings, nfc driver warnings and some other nondescript hardware errors), kernel messages (about boot manager, boot options, etc.).
Have you changed the behavior of the power button?
You also can program the power buttons so that by pressing the power button you can shutdown the tablet or put it into sleep or hibernation mode. To achieve this, you need to change your power plan settings. To access power plan settings, do the following:
From the desktop, tap the battery status icon in the Windows notification area.
Tap More power options.
In the navigation panel, tap Choose what the power buttons do
Follow the onscreen instructions to configure settings.
Lastly, when you updated to Windows 8.1, did you format the whole C:\ (mSATA) drive?
Helix: 3697 CTO.
Thinkpad user since IBM. I do not work for Lenovo or any entity working for Lenovo.

Lenovo N500 and Win7 x64: fails to resume from sleep or hibernate

Hello!
First of all, sorry for my bad english. I have bought an N500 laptop on the previous week. I'm using Windows 7 x64 on my desktop PC for months without any problem, so i thought i give it a try on my new notebook to. I choosed the x64 edition because my notebook has 4GB of memory plus the 256MB dedicated memory of the GeForce IGP. The installation went fine, it detected all the hardware in the laptop (except the memory card reader, but i found out that the Vista driver works fine with it). My only problem is, that if i try to hibernate the machine, or put the notebook into sleep state, most of the times it doesn't wake up from it, just simply reboots. If i resume from hibernate it provides me the option to delete the restoration data and do a clean boot. It's very annoying because defaultly if i close the lid or just simple leave the machine for a while, it goes to sleep automatically (i turned it off for now of course, but i like to use). It does it even after a fresh install, if i didn't install anything by hand. Windows Update offers me prelease GeForce drivers, but if i install those the problem still remains. As is see there isn't any Windows 7 drivers for this laptop, just Thinkpad series have Beta drivers for this OS. Or just i didn't find them on the site? I will try to install Windows 7 x86 this afternoon to check it's the 64bit OS which makes the problem or not.
Can somebody suggest me something to solve this problem?

I have the same problem here. lenovo N500 Windows 7 7100 64bit. Have Mobile Intel 4 Series Express Chipset Family, That recently got official driver from intel (I dont think that's the problem anyway).
Everything work fine with 32bit.
Look around everywhere, no Success yet

Sound Problems After Restore from Hibernate Using uswsusp and pm-utils

I see mention of using /etc/pm/config.d/module to recycle certain kernel modules during suspend. Do I need to suspend all modules?
**** List of PLAYBACK Hardware Devices ****
card 0: MID [HDA Intel MID], device 0: CS4206 Analog [CS4206 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: MID [HDA Intel MID], device 1: CS4206 Digital [CS4206 Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
[aj@mbp62 ~]$ lsmod | grep snd
snd_hda_codec_cirrus 8790 1
snd_hda_intel 36904 1
snd_hda_codec 149633 2 snd_hda_intel,snd_hda_codec_cirrus
snd_hwdep 6340 1 snd_hda_codec
snd_pcm 77709 2 snd_hda_codec,snd_hda_intel
snd_page_alloc 7242 2 snd_pcm,snd_hda_intel
snd_timer 18726 1 snd_pcm
snd 59173 8 snd_hwdep,snd_timer,snd_pcm,snd_hda_codec,snd_hda_intel,snd_hda_codec_cirrus
soundcore 5450 1 snd
[aj@mbp62 ~]$ cat /etc/pm/config.d/module
SUSPEND_MODULES="bcma b43 snd_hda_intel"
SLEEP_MODULE=uswsusp
Any pointers?

This morning, I rebooted for half an hour without success:
After resume from hibernate, most of my machine froze like described above.
After first reboot, it worked for 1 minute, then I had a full freeze (nothing worked... no mouse, no normal keys, no magic keys, screen frozen...)
After second reboot, my wifi adapter was gone. It showed up in lspci and looked like this:
04:07.0 Network controller: Atheros Communications Inc. AR5416 Wireless Network Adapter [AR5008 802.11(a)bgn] (rev 01)
Subsystem: Atheros Communications Inc. Device 3071
Flags: 66MHz, medium devsel, IRQ 22
Memory at feb70000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [40] #80 [0000]
...but not in ifconfig. I found the following in dmesg:
[ 7.106070] ath: phy0: address test failed addr: 0x00008000 - wr:0x00080008 != rd:0x00000008
[ 7.106181] ath: phy0: Unable to initialize hardware; initialization status: -19
[ 7.106287] ath9k 0000:04:07.0: Failed to initialize device
Problem persisted over 10 poweroffs/reboots (also hit the "on" button a few times with the pwoer cable disconnected, trying to make it "reset" or something. Did not help this time, might have been coincidence the last time that worked.

Access Violation in aapltp.sys when resuming from sleep.

Hello,
*I have diagnosed an issue in the aapltp.sys (touch pad) driver included with the MacOS 10.6.2 DVD. This issue causes a illegal access to be performed by this driver when the computer resumes from sleep (I have never reproduced it when resuming from hibernate or during normal operation). This issue occurs about once in every 10 resume operations, with both Windows 7 and Windows Vista. I have not experimented other versions of the OS.*
*The version of this driver included with 10.5.x DVD does not have this issue - this is a new regression.*
*In summary, KeyMagic (another apple driver) running on a system thread calls the OS for a dispatch (FxDevice::Dispatch). This ends up being routed to aapltp. While executing, aapltp dereferences a memory position offseted from a register that contains NULL. This causes an Access Violation which escalates into a BugCheck.*
*AFAIK Apple does not distribute driver symbols so I was unable to dig into the cause for the fault in this driver. I am appending some additional crashdump information that might be useful. If you require additional information, let me know. I can either provide you with the full crashdump of perform further analysis if you make the symbols available.*
* Bugcheck Analysis *
SYSTEMTHREAD_EXCEPTION_NOTHANDLED (7e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88004a7ea74, The address that the exception occurred at
Arg3: fffff88005134718, Exception Record Address
Arg4: fffff88005133f70, Context Record Address
Debugging Details:
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
aapltp+ca74
fffff880`04a7ea74 807e5b01 cmp byte ptr [rsi+5Bh],1
EXCEPTION_RECORD: fffff88005134718 -- (.exr 0xfffff88005134718)
ExceptionAddress: fffff88004a7ea74 (aapltp+0x000000000000ca74)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 000000000000005b
Attempt to read from address 000000000000005b
CONTEXT: fffff88005133f70 -- (.cxr 0xfffff88005133f70)
rax=0000000000000000 rbx=0000000000000004 rcx=fffffa80057899e0
rdx=0000057ffa876618 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004a7ea74 rsp=fffff88005134950 rbp=fffffa8005789d50
r8=fffff88004a7b140 r9=0000000000000000 r10=fffffa80056809e0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000057ffa99e188 r15=0000057ffa99e188
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
aapltp+0xca74:
fffff880`04a7ea74 807e5b01 cmp byte ptr [rsi+5Bh],1 ds:002b:00000000`0000005b=??
Resetting default scope
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 000000000000005b
READ_ADDRESS: 000000000000005b
FOLLOWUP_IP:
aapltp+ca74
fffff880`04a7ea74 807e5b01 cmp byte ptr [rsi+5Bh],1
BUGCHECK_STR: 0x7E
DEFAULTBUCKETID: NULLCLASS_PTRDEREFERENCE
LASTCONTROLTRANSFER: from fffff88000e52f90 to fffff88004a7ea74
STACK_TEXT:
fffff880`05134950 fffff880`00e52f90 : fffffa80`05661e70 0000057f`fa9443a8 fffffa80`056809e0 fffffa80`056bbc50 : aapltp+0xca74
fffff880`051349b0 fffff880`00e5299f : 00000000`00000000 fffffa80`05661e70 fffffa80`056bbc50 fffffa80`056bbc50 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x4b8
fffff880`05134a30 fffff880`00e51f98 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`05661fc2 : Wdf01000!FxIoQueue::DispatchEvents+0x4df
fffff880`05134aa0 fffff880`00e57558 : fffffa80`04e2fb00 fffffa80`05661e70 fffffa80`04e2fb00 fffffa80`05661e70 : Wdf01000!FxIoQueue::QueueRequest+0x2bc
fffff880`05134b10 fffff880`00e41245 : fffffa80`05661e70 fffffa80`04160c30 fffffa80`04e8ea58 00000000`000f2008 : Wdf01000!FxPkgIo::Dispatch+0x37c
fffff880`05134b90 fffff880`04a672f6 : fffffa80`04160c30 fffffa80`056bcc90 00000000`00000000 00000000`000007ff : Wdf01000!FxDevice::Dispatch+0xa9
fffff880`05134bc0 fffff880`04a6660b : fffffa80`056bcc90 fffffa80`04e8c010 fffffa80`08897640 fffffa80`04e8ec20 : KeyMagic+0x32f6
fffff880`05134c30 fffff800`03334166 : fffffa80`04e00040 00000000`00000080 fffffa80`03cd1740 fffffa80`04e00040 : KeyMagic+0x260b
fffff880`05134d40 fffff800`0306f486 : fffff800`03209e80 fffffa80`04e00040 fffffa80`03ce6680 fffff880`0122ca90 : nt!PspSystemThreadStartup+0x5a
fffff880`05134d80 00000000`00000000 : fffff880`05135000 fffff880`0512f000 fffff880`05134770 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_NAME: aapltp+ca74
MODULE_NAME: aapltp
IMAGE_NAME: aapltp.sys
DEBUGFLR_IMAGETIMESTAMP: 49c7fb1c

Thanks for posting this information in this forum. You just saved me a couple thousand dollars!
Based on my experience if you want to get this problem fixed as soon as possible you need to do the following:
1. www.apple.com/feedback
2. Post a video of the problem on www.youtube.com
3. Send www.apple.com/feedback a link to the video on youtube.
4. Encourage others to visit your youtube video and to post their own.
Good luck!

MacBook blanks out when Resuming from Sleep

Hello.
I am having a problem with my MacBook. If i have it closed and asleep for a little while (about 15 minutes or more) and i come back and open it up, the screen will come on as usual and i will see my desktop, but after about a second, my screen will go blank and fade back to my desktop, as if my screen saver was shutting off. It is kind of annoying because my computer will wake with the screensaver off. i was wondering if there was anything i can do to fix this. thanks.

If openning the lid at the same time just after power is plugged in - the same effect.
Sorry, I will correct myself: actually, it works if openning the lid at the same time just after power is plugged in. But if you will close the lid again after few seconds (that will not allow to resume from hibernate completely, probably) - the same effect after this, i.e. it will hand on consequent lid open.

Ethernet not connecting when resuming from sleep/hibernate

I use my mac (Win7) in clamshell mode quite often, and I leave the cables connected (ethernet, power, display, etc). I have noticed since installing the 3.0 Boot Camp drivers that the ethernet connection is not recognized after resuming from sleep/hibernate. I need to disconnect the cable and re-plug it in for the system to recognize the network. Anyone else seeing this?

Look through Power Options for sleep and network. There should be sleep, low power, etc. And if possible, maybe you can manually update drivers from the vendor (not Apple). And if Windows or your update doesn't work as well, then you can just as easy use Device Manager and "rollback" the last driver upgrade - a great feature. Also, use those Create/Restore Check Points.
I use to have trouble, got tired of having this issue, and bought a new modem to replace my 5 yr old model. Problem gone. Same can happen regarding routers, sometimes a firmware update, but I had one router that had been superceeded by 4th generation and no firmware patch anymore.

Is it possible to resume from hibernate without initrd?

Similar Messages

Maybe you are looking for