Random reboots when resuming from disk (aka hibernation)

Hi,
I've noticed that since the Linux 3.17.1-1 upgrade, my laptop frequently fails to resume from disk : after I turn the system on, GRUB kicks in and the system immediately reboots itself (which leads to fsck checking the filesystem). The weird thing is that it seems to be a completely random behavior, as at least half of the time resuming from disk works as it always had.
Of course, the logs don't show anything about it as the failure occurs before the kernel is loaded. However, there's a couple of ACPI-related warnings that I wonder whether they're trying to tell me something:
[ 0.174166] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 0.174557] ACPI: Dynamic OEM Table Load:
[ 0.174565] ACPI: SSDT 0xFFFF880118886000 000853 (v01 PmRef Cpu0Cst 00003001 INTL 20051117)
[ 0.184302] ACPI: Dynamic OEM Table Load:
[ 0.184308] ACPI: SSDT 0xFFFF880118A47800 000303 (v01 PmRef ApIst 00003000 INTL 20051117)
[ 0.197523] ACPI: Dynamic OEM Table Load:
[ 0.197528] ACPI: SSDT 0xFFFF880118A70800 000119 (v01 PmRef ApCst 00003000 INTL 20051117)
[ 0.211364] ACPI: Interpreter enabled
[ 0.211372] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20140724/hwxface-580)
[ 0.211377] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20140724/hwxface-580)
[ 0.211392] ACPI: (supports S0 S3 S4 S5)
[ 0.211394] ACPI: Using IOAPIC for interrupt routing
[ 0.211419] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 0.228928] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
[ 0.230264] pci 0000:00:14.0: System wakeup disabled by ACPI
[ 0.230682] pci 0000:00:1a.0: System wakeup disabled by ACPI
[ 0.230879] pci 0000:00:1b.0: System wakeup disabled by ACPI
[ 0.231061] pci 0000:00:1c.0: System wakeup disabled by ACPI
[ 0.231413] pci 0000:00:1c.3: System wakeup disabled by ACPI
[ 0.231628] pci 0000:00:1d.0: System wakeup disabled by ACPI
[ 0.232566] pci 0000:02:00.0: System wakeup disabled by ACPI
[ 0.237796] pci 0000:03:00.0: System wakeup disabled by ACPI
[ 0.244692] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 11 12) *0, disabled.
[ 0.244743] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 12) *0, disabled.
[ 0.244792] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 12) *0, disabled.
[ 0.244840] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 12) *0, disabled.
[ 0.244888] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 12) *0, disabled.
[ 0.244937] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 12) *0, disabled.
[ 0.244988] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 12) *0, disabled.
[ 0.245037] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 12) *0, disabled.
[ 0.245197] ACPI: Enabled 4 GPEs in block 00 to 3F
[ 0.245273] ACPI : EC: GPE = 0x19, I/O: command/status = 0x66, data = 0x62
[ 0.245532] PCI: Using ACPI for IRQ routing
[ 0.255510] pnp: PnP ACPI init
[ 0.255639] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
[ 0.255784] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.255816] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
[ 0.255869] system 00:03: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
[ 0.255919] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.255980] pnp 00:05: Plug and Play ACPI device, IDs ETD0108 SYN0a00 SYN0002 PNP0f03 PNP0f13 PNP0f12 (active)
[ 0.256020] pnp 00:06: Plug and Play ACPI device, IDs ATK3001 PNP030b (active)
[ 0.256221] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.256296] system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.256438] system 00:09: Plug and Play ACPI device, IDs PNP0c01 (active)
[ 0.256470] pnp: PnP ACPI: found 10 devices
[ 0.393967] ACPI: Lid Switch [LID]
[ 0.394093] ACPI: Sleep Button [SLPB]
[ 0.394201] ACPI: Power Button [PWRF]
[ 1.254778] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
[ 1.337375] asus_wmi: Backlight controlled by ACPI video driver
[ 1.362831] ACPI: bus type USB registered
[ 1.732186] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 1.733010] ata3.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
[ 1.733040] ata3.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[ 1.733714] ata1.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
[ 1.733725] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[ 1.737970] ata3.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
[ 1.737979] ata3.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[ 1.793602] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 1.793992] ata1.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
[ 1.794003] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[ 8.830064] ACPI: Battery Slot [BAT0] (battery present)
[ 8.830950] ACPI: AC Adapter [AC0] (off-line)
[ 8.919453] ACPI: Thermal Zone [THRM] (37 C)
[ 9.007936] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042f conflicts with OpRegion 0x0000000000000400-0x000000000000044f (\GPIS) (20140724/utaddress-258)
[ 9.007942] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042f conflicts with OpRegion 0x0000000000000400-0x000000000000047f (\PMIO) (20140724/utaddress-258)
[ 9.007946] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 9.007950] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054f conflicts with OpRegion 0x0000000000000500-0x000000000000057f (\GPIO) (20140724/utaddress-258)
[ 9.007953] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GP01) (20140724/utaddress-258)
[ 9.007956] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 9.007957] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053f conflicts with OpRegion 0x0000000000000500-0x000000000000057f (\GPIO) (20140724/utaddress-258)
[ 9.007960] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GP01) (20140724/utaddress-258)
[ 9.007963] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 9.007964] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052f conflicts with OpRegion 0x0000000000000500-0x000000000000057f (\GPIO) (20140724/utaddress-258)
[ 9.007967] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GP01) (20140724/utaddress-258)
[ 9.007969] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 9.027976] ACPI Warning: SystemIO range 0x000000000000f040-0x000000000000f05f conflicts with OpRegion 0x000000000000f040-0x000000000000f04f (\SMB0) (20140724/utaddress-258)
[ 9.027985] ACPI Warning: SystemIO range 0x000000000000f040-0x000000000000f05f conflicts with OpRegion 0x000000000000f040-0x000000000000f04f (\_SB_.PCI0.SBUS.SMBI) (20140724/utaddress-258)
[ 9.027991] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
I use the asus_wmi module in this system and, as it is an Intel chipset, I've proceeded to load the intel-ucode as the first initramfs as recommended. Tell me if you need further information.
Thanks in advance!
Last edited by nvteighen (2014-10-27 12:17:34)

giddie wrote:You might want to try removing the intel-ucode package (and amending your initrd config so that it won't complain) and see if the problem persists?
OK, I've made a try by deleting all references to the intel-ucode initrd at /boot/grub/grub.cfg, so that the microcode update is not applied. Afterwards, I rebooted the system so that there is no trace of the microcode update left on the system and proceeded to do some normal usage of the laptop. Then, I've hibernated it, left it like that for a couple of hours and then, turned it on again. The process failed again without warning whatsoever and rebooted to a normal boot sequence.
Looking at all the suspend-to-RAM issues that people are also posting in these forums, I believe this is a bug in Linux 3.17, unrelated to the microcode thing.

Similar Messages

[SOLVED: clear CMOS] Reboot when resuming from sleep mode!

Hello all,
System Specs(Desktop):
uname: Linux 3.10.10-1-ARCH #1 SMP PREEMPT 2013 x86_64 GNU/Linux
GPU: nVidia GTX-550 Ti - Drivers: 325.15
The sleep and hibernate modes work as they should. But lately whenever I tap a key or press the power button to wake the pc from using either of the suspend modes, it reboots instead of turning on(hardware) and prompting with the loging screen like my laptop does.
I've check the wiki and searched the forums but nothing is close to what I'm experiencing.
Any help or links to something I might missed is greatly appreciated.
Last edited by youngunix (2013-09-15 03:33:48)

youngunix wrote:
cfr wrote:
What does "every OS" include? Just thinking if it includes something like Windows, say, that would point to something rather different than if the problem only manifests in Linux.
Have you seen if the problem occurs if you use the nouveau drivers?
I'm sorry dude, but there is something wrong with you!! In every thread, you just ask or make lame @$$ statements.
cfr is a regular presence around here and helps quite a lot of people. He was trying to get clarification so that your problem could be further debugged. You may think that his statements are "lame ass" but you attitude is "asshole". Don't come here looking for help and then tell those trying to help you that their help sucks. If that is how you show your appreciation for support, you should go elsewhere.

X220 very slow reconnecting to WiFi when resuming from sleep

So my X220 with the Intel 6205 card is having issues reconnecting to WiFi when resuming from sleep or hibernation. It takes about a minute for it to do so, though occasionally it will reconnect right away. Maybe 1 out of 20. When doing a cold boot or restart, it connects immediately upon the desktop showing up.
This was not always the case, in fact when I first got my X220 in June, I have not had this issue.... In fact, I don't know when it started happening, but it was maybe a couple months ago. I just thought it was my old router going bad. Well I got a new router, and it still happens. I have the latest Intel WiFi drivers from Lenovo, and I even tried downgrading to the previous driver from Intel's site. Still the same problem. I tried setting a default profile in access connections, and that does not help. In fact, it behaves the same way if I totally uninstall access connections as well. In fact I tried this on three different brand routers, and I can reproduce it on all of them (Asus, Netgear & TP-Link) so I think this is not a router issue. Other devices in the house reconnect right away with no issues (iPhone 4, PS3, Mac desktop, Dell laptop).
I currently have BIOS 1.24, but this was happening with 1.21 and 1.23 as well. My X220 originally came with 1.16, and I haven't updated it until 1.21. Unfortunately I don't remember that far back, if the problem started occuring then.
There was a brief discussion about this in another thread, but it went nowhere so perhaps this will get more attention. At least one other user reported the same issue.
Here's a clip of exactly what happens. When i press the button or open the lid from sleep, the windows wifi icon will start spinning for a few seconds, then turn into an X. then only about a minute later, does it quickly connect to the wifi and I have full signal. Manually clicking on the icon and selecting the access point does not speed up the process. It will only connect when it wants to, about a minute after resuming from sleep/hibernation.
http://youtu.be/dmboeA7HBgg
| X220 i7-2620M | 12.5" IPS | Intel 520 Series 180GB Main SSD | Mushkin 120GB mSATA SSD | 8GB RAM | Intel 6205 WiFi | BT | Win7 Pro 64 SP1 |
Solved!
Go to Solution.

Normally when a laptop running windows tries to connect to a network, it may also seek to identify certain components on the network, for example, asking the router "Who are you?". In your case, maybe the config are corrupted because the network address entries are messed up. Queries send out to the network come back with no replies, and the computer waited for the default time till timeout and it gives up.
Try this one at a time, reboot, or try all at once and reboot
TCP/IP stack repair options for use with Vista or 7.
Start, Programs\Accessories and right click on Command Prompt, select "Run as Administrator" to open a command prompt.
Reset WINSOCK entries to installation defaults: netsh winsock reset catalog
Reset IPv4 TCP/IP stack to installation defaults. netsh int ipv4 reset reset.log
Reset IPv6 TCP/IP stack to installation defaults. netsh int ipv6 reset reset.log
Reboot the machine.

10.6.4 complete system freeze when resuming from screensaver-VMWare Fusion

I have a Macbook Pro, 3,1. I just upgraded to 10.6.4 and noticed the following symptoms:
Shortly after launching VMWare Fusion 3.1 running a Windows XP VM (from a Bootcamp partition), a series of pop up messages were complaining about a bad OpenGL driver. The message popped up repeatedly and wouldn't let me out, even though I kept pressing "Ok". I had to force quit Fusion, which caused a chkdsk on relaunch of the XP VM.
After a complete reboot, I started VMWare again. The Fusion complaints haven't shown up again, but when resuming from the screensaver, the system either completely freezes up, or the screen login window starts to flash rapidly and seize up. I'm running Spaces with 6 virtual screens. Whether I'm in the Fusion Spaces screen or any other Spaces screen, the system freaks out when resuming from a screensaver.
I use this system at work, so I have to be able to lock my screen when I leave my cube. The only way I've been able to ensure the system doesn't freeze up and cause a hard reset of the XP VM is to completely disable the screensaver and power saver features, such as Start Screen Saver = Never, Computer Sleep = Never, Display Sleep = Never and launch the login window by clicking on my user name in the upper right corner of the screen on the menu bar. Even that causes a sluggish screen and I'm not confident it will keep working. I also made sure (from day one) that the Windows XP screensaver functions were all completely disabled. I prefer to use the OS X screensaver for everything, if for no other reason than having a single screen locking/unlocking point for when I step away.
This was all working properly in 10.6.3. The only nit-nat I noticed about Fusion in 10.6.3 was that it had to be launched in the "Primary Window", which seems to be the upper leftmost Spaces desktop. If I ever moved it to, or started in any other Spaces desktop, it would also exhibit the same random lockups. Keeping it in the "primary" space seems to have stopped the lockups.
I noticed that there seemed to be significant updates to the OpenGL drivers in 10.6.4. I am experiencing an unfortunate side effect of these updates and hope I'm not alone and that a fix is coming soon. Looking at the other posts, there seem to be a lot of similar problems. I wanted to describe my configuration in case the Apple dev team reads these posts. Thanks.

I ended up doing an erase and fresh install of Snow Leopard (10.6.0), upgraded to 10.6.4 with the combo update, then a fresh install of all my apps, including VMware 3.1. Everything has been solid for 2 days now. I'm guessing that my system had a magic combination of issues that weren't visible in 10.6.3 but became obvious only after upgrading to 10.6.4. I had been upgrading my OS since 10.5.0 over the last 2 years and needed to do a clean re-install for some time now.
I'm guessing that others who are noticing problems with the 10.6.4 update have a similar situation with their installations. Think back on all the times a software installation failed, or the system required a hard boot. Plus, I had a lot of 3rd party apps on my box that never posted updates for later Snow Leopard releases, so who knows? Anyway, it's good to have a clean and snappy system again. A lot of my apps launch a lot faster now and survive the screen saver and power saver modes just fine.
Message was edited by: mausoleum

Minor lag from GUI when resume from sleep

Hey people!
I've been on archlinux for a couple of months now and I have fixed bugs here and there but something I have just noticed yesterday (it would happen before but I couldn't say when it would occur) is that after my system resume from sleep (it's not slow, it takes 1 or 2 secs) gnome GUI is a bit slow and it doesn't stop till I reboot my pc (it doesn't occur until my pc resumes from sleep).
It's not that bad but quite annoying. I don't really know how to approach that kind of problem. I think it would be related to something like "gnome is not completly reloaded when resume from sleep and there are some infinite loop going on"...
I hope someone has a clue in here!

hey, sorry to revive an old thread, but this was the only other person I could find with this issue.
I had originally reinstalled power manager and the the pm driver because it wouldn't save any custom power settings. When I finally got it working, it wouldnt wake up from sleep just like the above user's issue.
Machine is relatively new win7x64 install with all updates (lenovo updates too) installed.
Would like to avoid a total reinstall if at all possible.

T61p: Vista - BSOD when resume from sleep / hibernate, casued by classpnp.sys

I've got a T61p (Type: 6457) with preinstalled Vista, later upgraded with SP1. Everything worked like a charm, untill a week or so, when the BSOD appeared when either resuming from sleep or hibernation.
I've checked the minidump, and it seems as the classpnp.sys is causing the trouble, however, I've yet not found a good solution to fix the problem (I'm close to doing a restore to factory install, but would like to avoid if possible
Anyone?
edit: typos
Message Edited by birwi on 04-12-2009 06:38 PM

There's an issue with your GPU, video driver or both...try running this for a while:
http://freestone-group.com/video-card-stability-test.htm
If there's an underlying problem, this test will reveal it. And when I say "a while" I mean for an hour or more...
Please be advised that if your GPU is on its way out (I've had them fail on T60p due to VRAM corruption) this test might just finish it and push it over the edge. Proceed at your own risk.
Good luck.
Cheers,
George
In daily use: R60F, R500F, T61, T410
Collecting dust: T60
Enjoying retirement: A31p, T42p,
Non-ThinkPads: Panasonic CF-31 & CF-52, HP 8760W
Starting Thursday, 08/14/2014 I'll be away from the forums until further notice. Please do NOT send private messages since I won't be able to read them. Thank you.

When resuming from standby mouse-click/keyboard doesn't work.

When resuming from standby about 80% of the time the mouse on my Macbook Pro (Early 2011) stops working. I think it is a software issue. It appears that the mouse will do a click or click and drag but will not let go when removing my fingers. The issue only happens within 5seconds of waking up. The issue is only fixed with a hard reboot. I can bring up the shutdown menu, but am unable to slect shut down as the mouse/keyboard won't give input. This issue was present in Lion and was gone for the first few months of Mavericks but appeared again this week.
I can freely move around the mouse cursor and enter expose with three fingers but cannot select anything.
Any help would be appreciated.
Thanks.

You can use viewToModel() method to get caret position for x, y location. No need to click.
Regards,
Stas

When resuming from screensaver

When resuming from screensaver screen is pixelated in large blocks about a quarter inch square. I can put in my password after i roll the cursor around enough to see where to click to put in my password. Is there a fix for that yet?

Just wanted to say that i got an adwise in the thread that i posted earlier that has worked for me.
Adwise form Softwater:
Try deleting this file:
~/Library/Preferences/com.apple.screensaver.plist
and then re-starting your mac.
Don’t worry, deleting the file is harmless. It will just recreate itself to default settings when the computer reboots. It may be that the current file is corrupt.
Note: to get to this file in Lion, you have to chose ‘Go’ menu from the Finder menubar at the top of the screen, while keeping the ‘option’ key held down. When you do this, you will see ‘Library’ in the Go menu bar. Click on it and navigate to Preferences and look for the filecom.apple.screensaver.plist and trash it.

A problem with a macbook retina when resuming from sleep.

After many questions and a complete reinstall at an apple store I stil have the problem. When resuming from sleep, and sometimes seemingly at random, the machine swaps to a different application. I run several desktops full screen and it will swap to a different desktop virtually every time I resume. Not a huge deal but annoying. It seemed to start happening when I installed Office for Mac, but that might just be coincidence. I'm not running anything weird in the background, just a utility to show when the graphics card is active. Any help would he greatly appreciated.

Running games at full resolution may produce occasionally-choppy video, but nothing that would prevent you from playing. I mayself have played Portal and Left 4 Dead 2 on mine, and I haven't noticed any problems.

Airport Card turned off when resuming from sleep - New since 10.6.6

I use safe sleep regularly, as I use my laptop at both work and home. Ever since the update to 10.6.6 though, I have had to manually turn my Airport connection back on after resuming from sleep.
Previously, although it was unreliable about connecting to a preferred network (an unrelated, but equally frustrating issue*) at least it would remain on. Now I've had to add the icon to my Menu bar just so I don't have to dig into System Preferences every single time I reawaken my laptop.
Does anyone know why this is happening, and if there is anything I can do to prevent it? I apologize if this has been asked before, but when I searched I was unable to find anything.
*This issue is unrelated and not the focus of my post, but if you happen to know about it I would absolutely appreciate your input.
When resuming from sleep, despite being between 5-20 feet from my preferred router I will often receive a dialog asking me to select from a list of SSIDs and enter a password even though that information is already saved. Then, once I complete this information Airport doesn't actually connect and the only way to resolve the issue is to turn Airport off and then back on. After this, it will automatically connect with no problems and remain connected until I put the computer into Sleep mode again.

Maybe check in your keychain and verify the password saved is correct for your wireless router?
Do you broadcast the network name?
Could you describe "unreliable about connecting to a preferred network"?
Is "use secure virtual memory" checked in the Security preference pane? If so try unchecking that maybe? If it's a hibernation issue sometimes that could cause weirdness.

Kernel panic when resuming from sleep

I've been getting random kernel panics on my MacBook Pro when resuming from sleep. That is, only when resuming from sleep - otherwise the computer is fine.
I read some other discussions on here regarding kernel panics, but it seems that an inspection of the panic.log file usually uncovered a bad USB driver or something of that nature. I have no extra peripherals on my machine, and the panic.log is fairly vanilla. In fact, every entry in the log looks like this:
Fri May 4 21:33:43 2007
panic(cpu 0 caller 0x001A429B): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x30219fbe, CR3: 0x00dd9000, CR4: 0x000006e0
EAX: 0x00000001, EBX: 0x30219fbf, ECX: 0x0041e700, EDX: 0x00188fbe
CR2: 0x30219fbe, EBP: 0x253b3ca8, ESI: 0x00188fbf, EDI: 0x03d30e40
EFL: 0x00010246, EIP: 0x003c067d, CS: 0x00000008, DS: 0x253b0010
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x253b3ad8 : 0x128d08 (0x3cb134 0x253b3afc 0x131de5 0x0)
0x253b3b18 : 0x1a429b (0x3d0e4c 0x0 0xe 0x3d0670)
0x253b3c28 : 0x19ada4 (0x253b3c38 0xe 0xe 0x3c190048)
0x253b3ca8 : 0x3c176a (0x3cf4c40 0x3d30e40 0x3ef424 0x1628d8)
0x253b3ce8 : 0x38665a (0x3e5dd40 0x3d30e40 0x253b3d28 0x3c1002)
0x253b3d08 : 0x389e5b (0x393a100 0x3d30e40 0x393a104 0x393a100)
0x253b3d28 : 0x3b1448 (0x393a100 0x3d30e40 0x253b3d58 0x3bdfd9)
0x253b3d78 : 0x188511 (0x393a100 0x39e82b4 0x39e82c8 0x11cc32)
0x253b3db8 : 0x12b4c3 (0x4de87b4 0x39e8298 0x0 0x0)
0x253b3df8 : 0x124b17 (0x4de8700 0x0 0x18 0x253b3edc)
0x253b3f08 : 0x195a42 (0x253b3f44 0x0 0x0 0x0)
0x253b3fc8 : 0x19b21e (0x4678c9c 0x0 0x19e0b5 0x46947a0) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbffff358
Kernel version:
Darwin Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007; root:xnu-792.18.15~1/RELEASE_I386
Yes, every log entry ends with that "invalid frame pointer 0xbffff358" bit.
The only thing I can surmise is that the memory (factory installed) is faulty, given that the frame pointer address is always the same.
Can anyone shed some light on this i.e. does this sound like I'm on the right track?
MacBook Pro Mac OS X (10.4.9)

> I've installed all the latest updates (and I've been getting these same kernel panics since Oct 13).
AH HA ! Then yes the combo updater is a good first step. It's not the same as applying all the smaller updates as they come out, using this ensures that every aspect of the OS is current. Before and after you use it, Repair Permissions ...

Resume from suspend or hibernation doesn't work if wlan is enabled

I have Samsung n310 -netbook with rtl8192e wlan chip. If I have wireless connection enabled I get a screen with blinking cursor when I try to resume from suspend or hibernation. If I put wlan down before suspend resume works fine.
How do I configure pm-utils to put wlan connection down when suspending and back up on resume? I've tried searching wiki and forum but haven't found an answer.

you can write your own hook to do that: http://wiki.archlinux.org/index.php/Pm- … _own_hooks

"PM: Resume from disk failed." in dmesg.log

Hi,
I have noticed strange failed message in my dmesk.lg/kernel.log lately, which says "PM: Resume from disk failed". This happens everytime I boot, even after a clean shutdown. I guess, it has been there since some update of mkinitcpio... The strange thing is that I don't have resume hook in mkinitcpio, so should I understand it as mkinitcpio automagically inserts the above hook?
Thanks.

tomk wrote:
Arch wiki wrote:The hooks in this directory will be called in alphabetic order during suspend (that's the reason their names all start with 2 digits, to make the ordering explicit) and in the reverse order during resume.
That seems clear to me. What else are you looking for?
But pm-hibernate does some of its own work for hibernation/thawing. I'd like to know where in relation to *that* the hooks are run. Ie, during hibernation, are they run before or after the vanilla pm-hibernate functionality?

Rebooting when waking from sleep

Hello all, my early 2009 Mini reboots when waking from sleep. How can I get it to wake up normally? thanks,

In the interest of getting better advice, can you add a little more information to your post?
How is the mini being put to sleep? What's the procedure being used?
Does the front panel white LED slowly pulsate as it should when the mini is sleeping?
How is the mini being awakened from sleep?
Describe as best you can the chain of events going from the sleeping mini to reboot.

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!

Random reboots when resuming from disk (aka hibernation)

Similar Messages

Maybe you are looking for