T60p - Unexpected death on resume from 15 minutes of standby or hibernation

Hallo!
I am diagnosing the following problem on a T60p 2007-93G:
When I let the machine go into standby or hibernation mode, or manually place it in either mode with FN+F4, respectively Fn+F12, everything looks fine. However, sometimes I could not resume from either mode by pressing the On/Off switch. Instead, within a second after pressing the On/Off switch, the battery and the AC adapter indicators turn off and the machine is dead. I need to unplug and plug the main battery to reanimate the machine (both indicators turn on). I can then start the machine using the On/Off switch.
After ensuring all Windows XP (Professional, SP3) updates are installed, and BIOS and Lenovo System Update are up-to-date, I did more systematic tests and also observed:
- The problem occurs only if the machine was in standby or hibernation mode for more than 15 minutes (several tests with less and more than 15 minutes).
- The problem occurs only if the machine is connected to the AC adapter.
Every resume from standby or hibernation within less than 15 minutes, AC adapter connected or not, even if I press and hold the I/O switch for a few seconds, makes the machine start normally.
Every resume from standby or hibernation without AC adapter, even after more than 15 minutes, also makes the machine start normally.
I have no clue about the cause of the 15 minutes window, nor about the influence on the presence of the AC adapter (ThinkVantage Power Manager 5.20 correctly identifies it as 90 W power supply).
The key question seems to me: What makes the machine to shut down (or die) when I press the On/Off switch?
Any ideas are welcome.
Thank you
Norbert

Norbert,
Have you solved this problem?
I, too, have a T60P with the same issue. I put it to sleep using Fn + F4. When I resume by pressing Fn, the power light turns off. To get the light to go on again, I need to unplug and replug in the power supply (I'm not using the battery). I can then restart the machine.
This behavior only started a few weeks ago. And I don't know if it's time related.
I thought it might be related to my using a docking station, but swapping docking stations made no difference.
Thanks for any tips you may have.
Michael

Similar Messages

T60 won't resume windows xp properly after standby and hibernation - shows only blank desktop

Hi
I've got aT60 195CTO which is still just in warrantee that when I hibernate or standby the laptop and when i resume it'll ask for a password after the normal wait but then it'll just sit there show desktop background with no icons etc and periodically show hardrive activity but nothing happens, the touch pad pointer works ok but nothing else, even ctrl alt del failed to do anything, have downloaded and installed all xp updates inc sp3 as well as thinkvantage updates everytime this happens i'm forced to shut down computer by holding power button and restarting this is very annoying and always has the possibility of loosing work.
There appears to be two power management schemes in operation?, one running under xp and the other under thinkvantage - not sure if there is a conflict here? I have tried going into hibernation by closing the lid, fn-F12, xp's shutdown menu and entering hibernation from the thinkvantage menu all with same final result.
I have found a number of other postings on the net about this same problem but but apart from reloading the os which failed to solve the problem no other advice appears to be available.
would really appreciate any advice from anyone who knows how to solve this problem.
Regards
Paul

No Not really had some success though completely uninstalled graphics card software and reloaded new software also found out that it was the XP wireless software was doing something when connected to my school network so quick fix was turn wireless off then log into computer then turn wireless back on to resolve this cause I always forgot to turn it off I set up the lenovo wireless manager this worked and will only periodically do it (though I never really turn my computer off unless upgrading etc and sometimes it clogs up) another problem with mine was the battery could have been a issue cause I never turned it off and let it discharge (I wouldn't t recommend doing that unless battery is in warranty) first time I did discharge it it would not recharge so I may have had a faulty battery heard about the non-rechargeable coin battery maybe another member could confirm that? This could have been contributing to the issue
Hopes this gives u a variety of solutions to try help desk at lenovo had no idea when I told them about it and couldn't do much but tell me to update bios if it continues I suggest u ask it to be looked at and before warranty expires
Just received new 9 cell battery today will update to see if that was the issue

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

Dell Vostro 1400 not resuming from pm-hibernate.

For some reason my laptop won't resume after hibernating with pm-hibernate.
I have added the resume hook to /etc/mkinitcpio.conf and the swap drive to /boot/grub/menu.lst.
Is s2disk reports no error when creating image file and the hook is run on next boot but it doesn't work.
dmesg output:
PM: Checking image partition /dev/sda6
PM: Resume from disk failed.
PM: Starting manual resume from disk
PM: Resume from partition 8:6
PM: Checking hibernation image.
PM: Error -22 checking image file
PM: Resume from disk failed.
Any ideas?

gustaf@myhost:~$ free
total used free shared buffers cached
Mem: 2062312 550380 1511932 0 39912 218132
-/+ buffers/cache: 292336 1769976
Swap: 2048252 0 2048252
gustaf@myhost:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 10M 244K 9.8M 3% /dev
/dev/disk/by-uuid/295976ce-2dec-40c7-a8ae-499184c1b9ef
4.6G 1.3G 3.1G 30% /
none 1007M 24K 1007M 1% /dev/shm
/dev/sda1 487M 21M 441M 5% /boot
/dev/sda7 22G 17G 3.9G 81% /home
/dev/sda8 4.6G 3.6G 851M 81% /usr
/dev/sda2 25G 13G 13G 49% /mnt/winsys
/dev/sda5 54G 42G 12G 78% /mnt/windata

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

T60p Win7 LCD sometimes off when resume from sleep

T60p Win7 - Sometimes when returning from sleep the LCD does not come on. When this happens sleeping and awaking again has no effect. Only solution is to hard power down.
Latest BIOS, system up to date. Any ideas?

How about including a link then to where he/she might find the answer instead of ragging them for not searching?
I am having the same problem and have searched endlessly for a solution - and none so far have resolved it. So if you know where the answer is then by all means please share that.
- Hurk

Sometimes it doesn't resume from suspend

Hey! As you may guess (!), I'm new to this. But I love the idea of learning.
Anyway, I have a laptop Acer Aspire 7741G-6426 and I'm having a little problem. See, I first installed XFCE4 with SLIM as a WM, the problem was that I couldn't resume from suspend (or sleep), all I got was a black screen. After that, I enabled autologin to XFCE, and just to tried one more time, I suspended, and the problem was 'solved'. I could resume without problems.
I'm on a fresh install now, with KDE and the same problem happened before I enabled autologin in KDM (before enabling it, the same problem described above occurred). I can suspend and resume. That is, most of the time. An hour ago I suspended the laptop, and my surprise was to find the black screen again when trying to resume. When I resumed, the disk seemed to load something and then stopped and all I could see was a black screen, the same as before. The only thing I can do when that happens is to hard shutdown the PC.
A few minutes ago I tried again, and resumed without problems. But I'm afraid it might happen again and I might lose something important. I need to find a solution.
Also, I have an AMD 6550M video card and I'm using the Catalyst driver (because the open source made the laptop too hot).
I don't know if this is related, but if I run "lsmod | grep radeon", this is the output:
radeon 989731 0
ttm 54560 1 radeon
drm_kms_helper 27529 1 radeon
drm 181991 3 radeon,ttm,drm_kms_helper
i2c_algo_bit 5239 1 radeon
i2c_core 20165 6 videodev,radeon,drm_kms_helper,drm,i2c_algo_bit,i2c_i801
Is it normal that the radeon driver is loaded? Isn't that the open source one, which I didn't installed?
Anyway, does anyone have any idea of what this is?
I don't know what kind of information I should give.
Oh, and I've been reading some logs (which I'm making myself believe I can understand, haha), and in pm-suspend.log, almost everything says "resume suspend: success", except for:
Running hook /etc/pm/sleep.d/90alsa resume suspend:
ALSA lib pulse.c:229:(pulse_connect) PulseAudio: Unable to connect: Connection refused
aplay: main:660: audio open error: Connection refused
In kernel.log, there are many (specially 'dhcpcd not running'):
Jun 29 20:03:43 localhost kernel: [ 8233.952493] ath: txq: ffff88012c2068d0 axq_qnum: 2, mac80211_qnum: 2 axq_link: ffff8800bac25ea8 pending frames: 1 axq_acq empty: 1 stopped: 0 axq_depth: 0 Attempting to restart tx logic.
Jun 29 23:34:01 localhost kernel: [ 6.727474] intel ips 0000:00:1f.6: failed to get i915 symbols, graphics turbo disabled
Jun 29 23:34:01 localhost kernel: [ 6.904533] acer_wmi: Unable to detect available WMID devices
Jun 29 23:34:14 localhost dhcpcd[955]: dhcpcd not running
Jun 29 23:34:30 localhost pulseaudio[1155]: pid.c: Daemon already running.
And also, sorry for my english (and such a long post)!
Thanks anyway.

After so many days without the problem, I got the black screen of death minutes ago. I suspended and about 40 minutes later tried to resume and got the black screen. At least this time the wifi led was on and the disk seemed more active than other times. Though unfortunately I couldn't ssh into the laptop since I didn't have sshd enabled... But I could use the SysRq key, and for the first time, I got the "ASIC hang happened". I'm thinking that this might have something to do with the "nopat" line. Since before I added this line, the wifi led was off, there was no disk activity (past the first 3-4 seconds when trying to resume) and the SysRq key wouldn't work, so I had to hard shutdown. So at least now the SysRq key works, that's something.
This is the full log from the failed resume:
Jul 14 23:46:20 localhost kernel: [ 8505.476150] PM: Syncing filesystems ... done.
Jul 14 23:46:20 localhost kernel: [ 8505.477733] PM: Preparing system for mem sleep
Jul 14 23:46:20 localhost kernel: [ 8505.477749] Freezing user space processes ... (elapsed 0.01 seconds) done.
Jul 14 23:46:20 localhost kernel: [ 8505.488608] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
Jul 14 23:46:20 localhost kernel: [ 8505.501902] PM: Entering mem sleep
Jul 14 23:46:20 localhost kernel: [ 8505.502003] Suspending console(s) (use no_console_suspend to debug)
Jul 14 23:46:20 localhost kernel: [ 8505.551975] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jul 14 23:46:20 localhost kernel: [ 8505.629234] HDA Intel 0000:02:00.1: PCI INT B disabled
Jul 14 23:46:20 localhost kernel: [ 8505.629293] ACPI handle has no context!
Jul 14 23:46:20 localhost kernel: [ 8505.629299] ehci_hcd 0000:00:1d.0: PCI INT A disabled
Jul 14 23:46:20 localhost kernel: [ 8505.629321] [fglrx] IRQ 44 Disabled
Jul 14 23:46:20 localhost kernel: [ 8505.629468] [fglrx] Preparing suspend fglrx in kernel.
Jul 14 23:46:20 localhost kernel: [ 8505.629964] ehci_hcd 0000:00:1a.0: PCI INT A disabled
Jul 14 23:46:20 localhost kernel: [ 8505.637746] kworker/u:29: page allocation failure. order:10, mode:0x4020
Jul 14 23:46:20 localhost kernel: [ 8505.637749] Pid: 8403, comm: kworker/u:29 Tainted: P 2.6.39-ARCH #1
Jul 14 23:46:20 localhost kernel: [ 8505.637751] Call Trace:
Jul 14 23:46:20 localhost kernel: [ 8505.637759] [<ffffffff810fc30f>] __alloc_pages_nodemask+0x78f/0x8c0
Jul 14 23:46:20 localhost kernel: [ 8505.637762] [<ffffffff81132673>] alloc_pages_current+0xa3/0x110
Jul 14 23:46:20 localhost kernel: [ 8505.637766] [<ffffffff810f821e>] __get_free_pages+0xe/0x50
Jul 14 23:46:20 localhost kernel: [ 8505.637769] [<ffffffff8113d81f>] kmalloc_order_trace+0x3f/0x100
Jul 14 23:46:20 localhost kernel: [ 8505.637805] [<ffffffffa06c1cf3>] ? __start_CPDMA_copy_evergreen+0xa3/0xc0 [fglrx]
Jul 14 23:46:20 localhost kernel: [ 8505.637808] [<ffffffff8113da77>] __kmalloc+0x197/0x1a0
Jul 14 23:46:20 localhost kernel: [ 8505.637820] [<ffffffffa069438e>] KCL_MEM_SmallBufferAllocAtomic+0x1e/0x20 [fglrx]
Jul 14 23:46:20 localhost kernel: [ 8505.637836] [<ffffffffa06a7da3>] firegl_save_fb+0x233/0x360 [fglrx]
Jul 14 23:46:20 localhost kernel: [ 8505.637853] [<ffffffffa06a6f35>] ? firegl_pm_save_framebuffer+0x1f5/0x280 [fglrx]
Jul 14 23:46:20 localhost kernel: [ 8505.637869] [<ffffffffa06a9b2d>] ? firegl_cail_powerdown+0x8d/0x200 [fglrx]
Jul 14 23:46:20 localhost kernel: [ 8505.637879] [<ffffffffa0691fc7>] ? fglrx_pci_suspend+0x87/0x150 [fglrx]
Jul 14 23:46:20 localhost kernel: [ 8505.637884] [<ffffffff812390f6>] ? pci_legacy_suspend+0x46/0xe0
Jul 14 23:46:20 localhost kernel: [ 8505.637886] [<ffffffff8123a3ad>] ? pci_pm_suspend+0xdd/0x130
Jul 14 23:46:20 localhost kernel: [ 8505.637890] [<ffffffff812e5b35>] ? pm_op+0x175/0x1c0
Jul 14 23:46:20 localhost kernel: [ 8505.637892] [<ffffffff812e5c32>] ? __device_suspend+0xb2/0x1a0
Jul 14 23:46:20 localhost kernel: [ 8505.637896] [<ffffffff81085b50>] ? async_schedule+0x20/0x20
Jul 14 23:46:20 localhost kernel: [ 8505.637898] [<ffffffff812e5d41>] ? async_suspend+0x21/0x50
Jul 14 23:46:20 localhost kernel: [ 8505.637900] [<ffffffff81085bcf>] ? async_run_entry_fn+0x7f/0x180
Jul 14 23:46:20 localhost kernel: [ 8505.637903] [<ffffffff81077f6e>] ? process_one_work+0x11e/0x4c0
Jul 14 23:46:20 localhost kernel: [ 8505.637905] [<ffffffff810788ff>] ? worker_thread+0x15f/0x350
Jul 14 23:46:20 localhost kernel: [ 8505.637907] [<ffffffff810787a0>] ? manage_workers.isra.29+0x230/0x230
Jul 14 23:46:20 localhost kernel: [ 8505.637909] [<ffffffff8107d6ec>] ? kthread+0x8c/0xa0
Jul 14 23:46:20 localhost kernel: [ 8505.637912] [<ffffffff813e9fe4>] ? kernel_thread_helper+0x4/0x10
Jul 14 23:46:20 localhost kernel: [ 8505.637914] [<ffffffff8107d660>] ? kthread_worker_fn+0x190/0x190
Jul 14 23:46:20 localhost kernel: [ 8505.637915] [<ffffffff813e9fe0>] ? gs_change+0x13/0x13
Jul 14 23:46:20 localhost kernel: [ 8505.637917] Mem-Info:
Jul 14 23:46:20 localhost kernel: [ 8505.637918] Node 0 DMA per-cpu:
Jul 14 23:46:20 localhost kernel: [ 8505.637919] CPU 0: hi: 0, btch: 1 usd: 0
Jul 14 23:46:20 localhost kernel: [ 8505.637921] CPU 1: hi: 0, btch: 1 usd: 0
Jul 14 23:46:20 localhost kernel: [ 8505.637922] CPU 2: hi: 0, btch: 1 usd: 0
Jul 14 23:46:20 localhost kernel: [ 8505.637923] CPU 3: hi: 0, btch: 1 usd: 0
Jul 14 23:46:20 localhost kernel: [ 8505.637924] Node 0 DMA32 per-cpu:
Jul 14 23:46:20 localhost kernel: [ 8505.637925] CPU 0: hi: 186, btch: 31 usd: 18
Jul 14 23:46:20 localhost kernel: [ 8505.637927] CPU 1: hi: 186, btch: 31 usd: 185
Jul 14 23:46:20 localhost kernel: [ 8505.637928] CPU 2: hi: 186, btch: 31 usd: 1
Jul 14 23:46:20 localhost kernel: [ 8505.637929] CPU 3: hi: 186, btch: 31 usd: 45
Jul 14 23:46:20 localhost kernel: [ 8505.637930] Node 0 Normal per-cpu:
Jul 14 23:46:20 localhost kernel: [ 8505.637931] CPU 0: hi: 186, btch: 31 usd: 185
Jul 14 23:46:20 localhost kernel: [ 8505.637932] CPU 1: hi: 186, btch: 31 usd: 158
Jul 14 23:46:20 localhost kernel: [ 8505.637934] CPU 2: hi: 186, btch: 31 usd: 151
Jul 14 23:46:20 localhost kernel: [ 8505.637935] CPU 3: hi: 186, btch: 31 usd: 44
Jul 14 23:46:20 localhost kernel: [ 8505.637938] active_anon:264255 inactive_anon:50599 isolated_anon:0
Jul 14 23:46:20 localhost kernel: [ 8505.637939] active_file:81821 inactive_file:445828 isolated_file:0
Jul 14 23:46:20 localhost kernel: [ 8505.637939] unevictable:0 dirty:11 writeback:0 unstable:0
Jul 14 23:46:20 localhost kernel: [ 8505.637940] free:33258 slab_reclaimable:12432 slab_unreclaimable:5104
Jul 14 23:46:20 localhost kernel: [ 8505.637941] mapped:66993 shmem:1158 pagetables:7761 bounce:0
Jul 14 23:46:20 localhost kernel: [ 8505.637942] Node 0 DMA free:15780kB min:264kB low:328kB high:396kB active_anon:0kB inactive_anon:64kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15676kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:0kB slab_unreclaimable:8kB kernel_stack:0kB pagetables:48kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
Jul 14 23:46:20 localhost kernel: [ 8505.637948] lowmem_reserve[]: 0 2989 3872 3872
Jul 14 23:46:20 localhost kernel: [ 8505.637950] Node 0 DMA32 free:98084kB min:51956kB low:64944kB high:77932kB active_anon:912996kB inactive_anon:57860kB active_file:243344kB inactive_file:1551960kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:3060784kB mlocked:0kB dirty:24kB writeback:0kB mapped:64464kB shmem:3904kB slab_reclaimable:30264kB slab_unreclaimable:2868kB kernel_stack:632kB pagetables:9772kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
Jul 14 23:46:20 localhost kernel: [ 8505.637956] lowmem_reserve[]: 0 0 883 883
Jul 14 23:46:20 localhost kernel: [ 8505.637958] Node 0 Normal free:19168kB min:15360kB low:19200kB high:23040kB active_anon:144024kB inactive_anon:144472kB active_file:83940kB inactive_file:231352kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:904960kB mlocked:0kB dirty:20kB writeback:0kB mapped:203508kB shmem:728kB slab_reclaimable:19464kB slab_unreclaimable:17540kB kernel_stack:2064kB pagetables:21224kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
Jul 14 23:46:20 localhost kernel: [ 8505.637964] lowmem_reserve[]: 0 0 0 0
Jul 14 23:46:20 localhost kernel: [ 8505.637965] Node 0 DMA: 1*4kB 0*8kB 0*16kB 1*32kB 2*64kB 2*128kB 2*256kB 1*512kB 2*1024kB 2*2048kB 2*4096kB = 15780kB
Jul 14 23:46:20 localhost kernel: [ 8505.637970] Node 0 DMA32: 3368*4kB 1866*8kB 1033*16kB 584*32kB 119*64kB 45*128kB 20*256kB 9*512kB 9*1024kB 1*2048kB 0*4096kB = 97984kB
Jul 14 23:46:20 localhost kernel: [ 8505.637974] Node 0 Normal: 88*4kB 179*8kB 357*16kB 133*32kB 32*64kB 4*128kB 3*256kB 4*512kB 0*1024kB 1*2048kB 0*4096kB = 19176kB
Jul 14 23:46:20 localhost kernel: [ 8505.637978] 528820 total pagecache pages
Jul 14 23:46:20 localhost kernel: [ 8505.637979] 0 pages in swap cache
Jul 14 23:46:20 localhost kernel: [ 8505.637981] Swap cache stats: add 8, delete 8, find 0/0
Jul 14 23:46:20 localhost kernel: [ 8505.637982] Free swap = 4000116kB
Jul 14 23:46:20 localhost kernel: [ 8505.637982] Total swap = 4000148kB
Jul 14 23:46:20 localhost kernel: [ 8505.648067] 1015792 pages RAM
Jul 14 23:46:20 localhost kernel: [ 8505.648069] 95954 pages reserved
Jul 14 23:46:20 localhost kernel: [ 8505.648069] 452085 pages shared
Jul 14 23:46:20 localhost kernel: [ 8505.648070] 604505 pages non-shared
Jul 14 23:46:20 localhost kernel: [ 8505.648107] sd 0:0:0:0: [sda] Stopping disk
Jul 14 23:46:20 localhost kernel: [ 8505.731612] HDA Intel 0000:00:1b.0: PCI INT A disabled
Jul 14 23:46:20 localhost kernel: [ 8505.893374] [fglrx] Suspending fglrx in kernel completed.
Jul 14 23:46:20 localhost kernel: [ 8505.893377] [fglrx] Power down the ASIC .
Jul 14 23:46:20 localhost kernel: [ 8506.356479] PM: suspend of devices complete after 843.272 msecs
Jul 14 23:46:20 localhost kernel: [ 8506.409696] PM: late suspend of devices complete after 53.343 msecs
Jul 14 23:46:20 localhost kernel: [ 8506.409993] ACPI: Preparing to enter system sleep state S3
Jul 14 23:46:20 localhost kernel: [ 8506.526263] PM: Saving platform NVS memory
Jul 14 23:46:20 localhost kernel: [ 8506.528060] Disabling non-boot CPUs ...
Jul 14 23:46:20 localhost kernel: [ 8506.672249] CPU 1 is now offline
Jul 14 23:46:20 localhost kernel: [ 8506.805254] CPU 2 is now offline
Jul 14 23:46:20 localhost kernel: [ 8506.931586] CPU 3 is now offline
Jul 14 23:46:20 localhost kernel: [ 8506.931924] Extended CMOS year: 2000
Jul 14 23:46:20 localhost kernel: [ 8506.932121] ACPI: Low-level resume complete
Jul 14 23:46:20 localhost kernel: [ 8506.932167] PM: Restoring platform NVS memory
Jul 14 23:46:20 localhost kernel: [ 8506.932608] Extended CMOS year: 2000
Jul 14 23:46:20 localhost kernel: [ 8506.932626] Enabling non-boot CPUs ...
Jul 14 23:46:20 localhost kernel: [ 8506.939427] Booting Node 0 Processor 1 APIC 0x4
Jul 14 23:46:20 localhost kernel: [ 8506.939430] smpboot cpu 1: start_ip = 97000
Jul 14 23:46:20 localhost kernel: [ 8507.055234] Switched to NOHz mode on CPU #1
Jul 14 23:46:20 localhost kernel: [ 8507.095325] NMI watchdog enabled, takes one hw-pmu counter.
Jul 14 23:46:20 localhost kernel: [ 8507.095442] CPU1 is up
Jul 14 23:46:20 localhost kernel: [ 8507.095504] Booting Node 0 Processor 2 APIC 0x1
Jul 14 23:46:20 localhost kernel: [ 8507.095505] smpboot cpu 2: start_ip = 97000
Jul 14 23:46:20 localhost kernel: [ 8507.211565] Switched to NOHz mode on CPU #2
Jul 14 23:46:20 localhost kernel: [ 8507.251738] NMI watchdog enabled, takes one hw-pmu counter.
Jul 14 23:46:20 localhost kernel: [ 8507.251873] CPU2 is up
Jul 14 23:46:20 localhost kernel: [ 8507.251962] Booting Node 0 Processor 3 APIC 0x5
Jul 14 23:46:20 localhost kernel: [ 8507.251964] smpboot cpu 3: start_ip = 97000
Jul 14 23:46:20 localhost kernel: [ 8507.367843] Switched to NOHz mode on CPU #3
Jul 14 23:46:20 localhost kernel: [ 8507.408173] NMI watchdog enabled, takes one hw-pmu counter.
Jul 14 23:46:20 localhost kernel: [ 8507.408519] CPU3 is up
Jul 14 23:46:20 localhost kernel: [ 8507.410477] ACPI: Waking up from system sleep state S3
Jul 14 23:46:20 localhost kernel: [ 8507.484393] power_supply BAT0: parent PNP0C0A:00 should not be sleeping
Jul 14 23:46:20 localhost kernel: [ 8507.597538] pcieport 0000:00:01.0: restoring config space at offset 0xf (was 0x80100, writing 0x8010b)
Jul 14 23:46:20 localhost kernel: [ 8507.597543] pcieport 0000:00:01.0: restoring config space at offset 0x7 (was 0x2020, writing 0x20002020)
Jul 14 23:46:20 localhost kernel: [ 8507.597547] pcieport 0000:00:01.0: restoring config space at offset 0x3 (was 0x10000, writing 0x10010)
Jul 14 23:46:20 localhost kernel: [ 8507.597550] pcieport 0000:00:01.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100507)
Jul 14 23:46:20 localhost kernel: [ 8507.597595] ehci_hcd 0000:00:1a.0: restoring config space at offset 0xf (was 0x100, writing 0x10b)
Jul 14 23:46:20 localhost kernel: [ 8507.597608] ehci_hcd 0000:00:1a.0: restoring config space at offset 0x4 (was 0x0, writing 0xf0606000)
Jul 14 23:46:20 localhost kernel: [ 8507.597613] ehci_hcd 0000:00:1a.0: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900102)
Jul 14 23:46:20 localhost kernel: [ 8507.597635] HDA Intel 0000:00:1b.0: restoring config space at offset 0xf (was 0x100, writing 0x107)
Jul 14 23:46:20 localhost kernel: [ 8507.597646] HDA Intel 0000:00:1b.0: restoring config space at offset 0x4 (was 0xdc000004, writing 0xf0600004)
Jul 14 23:46:20 localhost kernel: [ 8507.597650] HDA Intel 0000:00:1b.0: restoring config space at offset 0x3 (was 0x0, writing 0x10)
Jul 14 23:46:20 localhost kernel: [ 8507.597654] HDA Intel 0000:00:1b.0: restoring config space at offset 0x1 (was 0x100006, writing 0x100102)
Jul 14 23:46:20 localhost kernel: [ 8507.597673] pcieport 0000:00:1c.0: restoring config space at offset 0xf (was 0x100, writing 0x4010a)
Jul 14 23:46:20 localhost kernel: [ 8507.597680] pcieport 0000:00:1c.0: restoring config space at offset 0x9 (was 0x10001, writing 0xf011f001)
Jul 14 23:46:20 localhost kernel: [ 8507.597683] pcieport 0000:00:1c.0: restoring config space at offset 0x8 (was 0x0, writing 0xf020f020)
Jul 14 23:46:20 localhost kernel: [ 8507.597687] pcieport 0000:00:1c.0: restoring config space at offset 0x7 (was 0x0, writing 0x3030)
Jul 14 23:46:20 localhost kernel: [ 8507.597690] pcieport 0000:00:1c.0: restoring config space at offset 0x6 (was 0x0, writing 0x40300)
Jul 14 23:46:20 localhost kernel: [ 8507.597694] pcieport 0000:00:1c.0: restoring config space at offset 0x3 (was 0x810000, writing 0x810010)
Jul 14 23:46:20 localhost kernel: [ 8507.597698] pcieport 0000:00:1c.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100107)
Jul 14 23:46:20 localhost kernel: [ 8507.597721] pcieport 0000:00:1c.1: restoring config space at offset 0xf (was 0x200, writing 0x4020b)
Jul 14 23:46:20 localhost kernel: [ 8507.597728] pcieport 0000:00:1c.1: restoring config space at offset 0x9 (was 0x10001, writing 0xc011c001)
Jul 14 23:46:20 localhost kernel: [ 8507.597731] pcieport 0000:00:1c.1: restoring config space at offset 0x8 (was 0x0, writing 0xf030f030)
Jul 14 23:46:20 localhost kernel: [ 8507.597734] pcieport 0000:00:1c.1: restoring config space at offset 0x7 (was 0x0, writing 0x4040)
Jul 14 23:46:20 localhost kernel: [ 8507.597737] pcieport 0000:00:1c.1: restoring config space at offset 0x6 (was 0x0, writing 0x50500)
Jul 14 23:46:20 localhost kernel: [ 8507.597742] pcieport 0000:00:1c.1: restoring config space at offset 0x3 (was 0x810000, writing 0x810010)
Jul 14 23:46:20 localhost kernel: [ 8507.597746] pcieport 0000:00:1c.1: restoring config space at offset 0x1 (was 0x100000, writing 0x100107)
Jul 14 23:46:20 localhost kernel: [ 8507.597768] ehci_hcd 0000:00:1d.0: restoring config space at offset 0xf (was 0x100, writing 0x10b)
Jul 14 23:46:20 localhost kernel: [ 8507.597781] ehci_hcd 0000:00:1d.0: restoring config space at offset 0x4 (was 0x0, writing 0xf0607000)
Jul 14 23:46:20 localhost kernel: [ 8507.597786] ehci_hcd 0000:00:1d.0: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900102)
Jul 14 23:46:20 localhost kernel: [ 8507.597803] pci 0000:00:1e.0: restoring config space at offset 0xf (was 0x40000, writing 0x400ff)
Jul 14 23:46:20 localhost kernel: [ 8507.597810] pci 0000:00:1e.0: restoring config space at offset 0x9 (was 0x10001, writing 0x1fff1)
Jul 14 23:46:20 localhost kernel: [ 8507.597813] pci 0000:00:1e.0: restoring config space at offset 0x8 (was 0x0, writing 0xfff0)
Jul 14 23:46:20 localhost kernel: [ 8507.597816] pci 0000:00:1e.0: restoring config space at offset 0x7 (was 0x22800000, writing 0x228000f0)
Jul 14 23:46:20 localhost kernel: [ 8507.597823] pci 0000:00:1e.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100107)
Jul 14 23:46:20 localhost kernel: [ 8507.597868] ahci 0000:00:1f.2: restoring config space at offset 0xf (was 0x200, writing 0x205)
Jul 14 23:46:20 localhost kernel: [ 8507.597880] ahci 0000:00:1f.2: restoring config space at offset 0x1 (was 0x2b00007, writing 0x2b00407)
Jul 14 23:46:20 localhost kernel: [ 8507.597921] pci 0000:00:1f.6: restoring config space at offset 0xf (was 0x300, writing 0x30a)
Jul 14 23:46:20 localhost kernel: [ 8507.597936] pci 0000:00:1f.6: restoring config space at offset 0x1 (was 0x100000, writing 0x100002)
Jul 14 23:46:20 localhost kernel: [ 8507.597958] fglrx_pci 0000:02:00.0: restoring config space at offset 0xf (was 0x1ff, writing 0x10b)
Jul 14 23:46:20 localhost kernel: [ 8507.597967] fglrx_pci 0000:02:00.0: restoring config space at offset 0x8 (was 0x1, writing 0x2001)
Jul 14 23:46:20 localhost kernel: [ 8507.597971] fglrx_pci 0000:02:00.0: restoring config space at offset 0x6 (was 0x4, writing 0xcfee0004)
Jul 14 23:46:20 localhost kernel: [ 8507.597975] fglrx_pci 0000:02:00.0: restoring config space at offset 0x4 (was 0xc, writing 0xd000000c)
Jul 14 23:46:20 localhost kernel: [ 8507.597978] fglrx_pci 0000:02:00.0: restoring config space at offset 0x3 (was 0x800000, writing 0x800010)
Jul 14 23:46:20 localhost kernel: [ 8507.597982] fglrx_pci 0000:02:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100503)
Jul 14 23:46:20 localhost kernel: [ 8507.598013] HDA Intel 0000:02:00.1: restoring config space at offset 0xf (was 0x2ff, writing 0x20a)
Jul 14 23:46:20 localhost kernel: [ 8507.598024] HDA Intel 0000:02:00.1: restoring config space at offset 0x4 (was 0x4, writing 0xcfedc004)
Jul 14 23:46:20 localhost kernel: [ 8507.598028] HDA Intel 0000:02:00.1: restoring config space at offset 0x3 (was 0x800000, writing 0x800010)
Jul 14 23:46:20 localhost kernel: [ 8507.598032] HDA Intel 0000:02:00.1: restoring config space at offset 0x1 (was 0x100000, writing 0x100103)
Jul 14 23:46:20 localhost kernel: [ 8507.598116] tg3 0000:03:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10)
Jul 14 23:46:20 localhost kernel: [ 8507.598121] tg3 0000:03:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100506)
Jul 14 23:46:20 localhost kernel: [ 8507.598178] ath9k 0000:05:00.0: restoring config space at offset 0xf (was 0x1ff, writing 0x10a)
Jul 14 23:46:20 localhost kernel: [ 8507.598196] ath9k 0000:05:00.0: restoring config space at offset 0x4 (was 0x4, writing 0xf0300004)
Jul 14 23:46:20 localhost kernel: [ 8507.598200] ath9k 0000:05:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10)
Jul 14 23:46:20 localhost kernel: [ 8507.598205] ath9k 0000:05:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100107)
Jul 14 23:46:20 localhost kernel: [ 8507.598413] PM: early resume of devices complete after 0.957 msecs
Jul 14 23:46:20 localhost kernel: [ 8507.598692] ehci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Jul 14 23:46:20 localhost kernel: [ 8507.598700] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
Jul 14 23:46:20 localhost kernel: [ 8507.598705] ehci_hcd 0000:00:1a.0: setting latency timer to 64
Jul 14 23:46:20 localhost kernel: [ 8507.598708] ehci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
Jul 14 23:46:20 localhost kernel: [ 8507.598711] HDA Intel 0000:00:1b.0: setting latency timer to 64
Jul 14 23:46:20 localhost kernel: [ 8507.598715] ehci_hcd 0000:00:1d.0: setting latency timer to 64
Jul 14 23:46:20 localhost kernel: [ 8507.598746] pci 0000:00:1e.0: setting latency timer to 64
Jul 14 23:46:20 localhost kernel: [ 8507.598753] HDA Intel 0000:00:1b.0: irq 42 for MSI/MSI-X
Jul 14 23:46:20 localhost kernel: [ 8507.598765] [fglrx] Kernel supports PAT but it has been disabled
Jul 14 23:46:20 localhost kernel: [ 8507.598766] [fglrx] Using driver built-in PAT support instead
Jul 14 23:46:20 localhost kernel: [ 8507.598768] ahci 0000:00:1f.2: setting latency timer to 64
Jul 14 23:46:20 localhost kernel: [ 8507.599319] tg3 0000:03:00.0: wake-up capability disabled by ACPI
Jul 14 23:46:20 localhost kernel: [ 8507.599360] tg3 0000:03:00.0: PME# disabled
Jul 14 23:46:20 localhost kernel: [ 8507.599505] HDA Intel 0000:02:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
Jul 14 23:46:20 localhost kernel: [ 8507.599515] HDA Intel 0000:02:00.1: setting latency timer to 64
Jul 14 23:46:20 localhost kernel: [ 8507.599554] HDA Intel 0000:02:00.1: irq 43 for MSI/MSI-X
Jul 14 23:46:20 localhost kernel: [ 8507.599630] sd 0:0:0:0: [sda] Starting disk
Jul 14 23:46:20 localhost kernel: [ 8507.599912] fglrx_pci 0000:02:00.0: setting latency timer to 64
Jul 14 23:46:20 localhost kernel: [ 8507.605625] [fglrx] Power up the ASIC
Jul 14 23:46:20 localhost kernel: [ 8507.605752] [fglrx] Preparing resume fglrx in kernel.
Jul 14 23:46:20 localhost kernel: [ 8507.673839] [fglrx] Resuming fglrx in kernel completed.
Jul 14 23:46:20 localhost kernel: [ 8507.674036] [fglrx] IRQ 44 Enabled
Jul 14 23:46:20 localhost kernel: [ 8507.850159] usb 2-1.5: reset high speed USB device number 3 using ehci_hcd
Jul 14 23:46:20 localhost kernel: [ 8507.916491] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Jul 14 23:46:20 localhost kernel: [ 8507.919985] ata5.00: configured for UDMA/100
Jul 14 23:46:20 localhost kernel: [ 8510.054456] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jul 14 23:46:20 localhost kernel: [ 8510.258470] ata1.00: configured for UDMA/133
Jul 14 23:46:20 localhost kernel: [ 8510.336104] PM: resume of devices complete after 2744.342 msecs
Jul 14 23:46:20 localhost kernel: [ 8510.336358] PM: Finishing wakeup.
Jul 14 23:46:20 localhost kernel: [ 8510.336359] Restarting tasks ... done.
Jul 14 23:46:20 localhost kernel: [ 8510.344265] video LNXVIDEO:00: Restoring backlight state
Jul 14 23:46:21 localhost kernel: [ 8511.289064] tg3 0000:03:00.0: eth0: Link is down
Jul 14 23:46:23 localhost kernel: [ 8513.177532] EXT4-fs (sda5): re-mounted. Opts: commit=0
Jul 14 23:46:24 localhost kernel: [ 8513.797702] EXT4-fs (sda6): re-mounted. Opts: commit=0
Jul 14 23:46:24 localhost kernel: [ 8514.034086] tg3 0000:03:00.0: PME# enabled
Jul 14 23:46:24 localhost kernel: [ 8514.034101] tg3 0000:03:00.0: wake-up capability enabled by ACPI
Jul 14 23:46:24 localhost kernel: [ 8514.057819] tg3 0000:03:00.0: irq 45 for MSI/MSI-X
Jul 14 23:46:24 localhost kernel: [ 8514.291538] tg3 0000:03:00.0: eth0: Link is down
Jul 14 23:46:26 localhost kernel: [ 8516.531715] wlan0: authenticate with 00:1b:11:a3:7b:24 (try 1)
Jul 14 23:46:26 localhost kernel: [ 8516.533596] wlan0: authenticated
Jul 14 23:46:26 localhost kernel: [ 8516.533615] wlan0: associate with 00:1b:11:a3:7b:24 (try 1)
Jul 14 23:46:26 localhost kernel: [ 8516.536019] wlan0: RX AssocResp from 00:1b:11:a3:7b:24 (capab=0x431 status=0 aid=3)
Jul 14 23:46:26 localhost kernel: [ 8516.536021] wlan0: associated
Jul 14 23:49:21 localhost kernel: [ 8690.305910] [fglrx] ASIC hang happened
Jul 14 23:49:21 localhost kernel: [ 8690.305915] Pid: 820, comm: X Tainted: P 2.6.39-ARCH #1
Jul 14 23:49:21 localhost kernel: [ 8690.305917] Call Trace:
Jul 14 23:49:21 localhost kernel: [ 8690.305955] [<ffffffffa0698d5e>] KCL_DEBUG_OsDump+0xe/0x10 [fglrx]
Jul 14 23:49:21 localhost kernel: [ 8690.305972] [<ffffffffa06a618c>] firegl_hardwareHangRecovery+0x1c/0x50 [fglrx]
Jul 14 23:49:21 localhost kernel: [ 8690.306004] [<ffffffffa072d419>] ? _ZN4Asic9WaitUntil15ResetASICIfHungEv+0x9/0x10 [fglrx]
Jul 14 23:49:21 localhost kernel: [ 8690.306034] [<ffffffffa072d3cc>] ? _ZN4Asic9WaitUntil15WaitForCompleteEv+0x6c/0xb0 [fglrx]
Jul 14 23:49:21 localhost kernel: [ 8690.306050] [<ffffffffa0779d7f>] ? _ZN13BaseUVDEngineI18mmEngineRS780_UVD2E4idleEv+0x7f/0xc0 [fglrx]
Jul 14 23:49:21 localhost kernel: [ 8690.306081] [<ffffffffa072c55c>] ? _ZN15ExecutableUnits35flush_all_and_invalidate_HDP_cachesE12_QS_CP_RING_+0xbc/0xe0 [fglrx]
Jul 14 23:49:21 localhost kernel: [ 8690.306112] [<ffffffffa072c355>] ? _ZN15ExecutableUnits10CPRingIdleE15idle_WaitMethod12_QS_CP_RING_+0x105/0x1a0 [fglrx]
Jul 14 23:49:21 localhost kernel: [ 8690.306143] [<ffffffffa0736807>] ? _ZN11AsicCypress21initializeMicroEngineEv+0x147/0x160 [fglrx]
Jul 14 23:49:21 localhost kernel: [ 8690.306158] [<ffffffffa077a026>] ? _ZN13BaseUVDEngineI18mmEngineRS780_UVD2E14SwitchEngineHWEN8mmEngine15MM_ENGINE_STATEE+0x26/0x1d0 [fglrx]
Jul 14 23:49:21 localhost kernel: [ 8690.306190] [<ffffffffa072733a>] ? _ZN18mmEnginesContainer13assertEnginesEb+0x5a/0xa0 [fglrx]
Jul 14 23:49:21 localhost kernel: [ 8690.306220] [<ffffffffa072be78>] ? _ZN15ExecutableUnits17assertPrimaryRingEb+0x1f8/0x210 [fglrx]
Jul 14 23:49:21 localhost kernel: [ 8690.306251] [<ffffffffa073372a>] ? _ZN8AsicR6009assertPM4Eb+0x4a/0x70 [fglrx]
Jul 14 23:49:21 localhost kernel: [ 8690.306270] [<ffffffffa06c3350>] ? firegl_cmmqs_disabledriver+0xf0/0xf0 [fglrx]
Jul 14 23:49:21 localhost kernel: [ 8690.306299] [<ffffffffa07080aa>] ? CMMQS_ReinitializeHardware+0x6a/0x80 [fglrx]
Jul 14 23:49:21 localhost kernel: [ 8690.306318] [<ffffffffa06c43e0>] ? firegl_cmmqs_Enable_QS+0x70/0x110 [fglrx]
Jul 14 23:49:21 localhost kernel: [ 8690.306337] [<ffffffffa06c3370>] ? firegl_cmmqs_enableqs+0x20/0x90 [fglrx]
Jul 14 23:49:21 localhost kernel: [ 8690.306349] [<ffffffffa0694256>] ? KCL_PosixSecurityCapCheck+0x26/0x30 [fglrx]
Jul 14 23:49:21 localhost kernel: [ 8690.306365] [<ffffffffa06a1d98>] ? firegl_ioctl+0x1e8/0x250 [fglrx]
Jul 14 23:49:21 localhost kernel: [ 8690.306369] [<ffffffff8118ae62>] ? fsnotify+0x1c2/0x2a0
Jul 14 23:49:21 localhost kernel: [ 8690.306380] [<ffffffffa0692eae>] ? ip_firegl_unlocked_ioctl+0xe/0x20 [fglrx]
Jul 14 23:49:21 localhost kernel: [ 8690.306385] [<ffffffff81163b6f>] ? do_vfs_ioctl+0x8f/0x500
Jul 14 23:49:21 localhost kernel: [ 8690.306389] [<ffffffff81151f48>] ? vfs_write+0x148/0x180
Jul 14 23:49:21 localhost kernel: [ 8690.306391] [<ffffffff81164071>] ? sys_ioctl+0x91/0xa0
Jul 14 23:49:21 localhost kernel: [ 8690.306396] [<ffffffff813e8ec2>] ? system_call_fastpath+0x16/0x1b
Jul 14 23:49:21 localhost kernel: [ 8690.306399] pubdev:0xffffffffa08da080, num of device:1 , name:fglrx, major 8, minor 86.
Jul 14 23:49:21 localhost kernel: [ 8690.306402] device 0 : 0xffff88012c40c000 .
Jul 14 23:49:21 localhost kernel: [ 8690.306403] Asic ID:0x68c1, revision:0x28, MMIOReg:0xffffc900117c0000.
Jul 14 23:49:21 localhost kernel: [ 8690.306405] FB phys addr: 0xd0000000, MC :0xf00000000, Total FB size :0x40000000.
Jul 14 23:49:21 localhost kernel: [ 8690.306407] gart table MC:0xf0f941000, Physical:0xdf941000, size:0x3be000.
Jul 14 23:49:21 localhost kernel: [ 8690.306410] mc_node :FB, total 1 zones
Jul 14 23:49:21 localhost kernel: [ 8690.306411] MC start:0xf00000000, Physical:0xd0000000, size:0xfd00000.
Jul 14 23:49:21 localhost kernel: [ 8690.306414] Mapped heap -- Offset:0x0, size:0xf941000, reference count:120, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306416] Mapped heap -- Offset:0x0, size:0x1000000, reference count:1, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306418] Mapped heap -- Offset:0xf941000, size:0x3bf000, reference count:1, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306419] mc_node :INV_FB, total 1 zones
Jul 14 23:49:21 localhost kernel: [ 8690.306421] MC start:0xf0fd00000, Physical:0xdfd00000, size:0x30300000.
Jul 14 23:49:21 localhost kernel: [ 8690.306423] Mapped heap -- Offset:0x302f4000, size:0xc000, reference count:1, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306424] mc_node :GART_USWC, total 2 zones
Jul 14 23:49:21 localhost kernel: [ 8690.306426] MC start:0x3ce90000, Physical:0x0, size:0x4ac00000.
Jul 14 23:49:21 localhost kernel: [ 8690.306428] Mapped heap -- Offset:0x5030000, size:0x800000, reference count:1, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306430] Mapped heap -- Offset:0x4830000, size:0x800000, reference count:1, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306432] Mapped heap -- Offset:0x4030000, size:0x800000, reference count:1, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306434] Mapped heap -- Offset:0x3830000, size:0x800000, reference count:1, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306436] Mapped heap -- Offset:0x3030000, size:0x800000, reference count:1, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306438] Mapped heap -- Offset:0x2830000, size:0x800000, reference count:1, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306440] Mapped heap -- Offset:0x2030000, size:0x800000, reference count:1, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306442] Mapped heap -- Offset:0x30000, size:0x2000000, reference count:13, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306444] mc_node :GART_CACHEABLE, total 3 zones
Jul 14 23:49:21 localhost kernel: [ 8690.306445] MC start:0x10400000, Physical:0x0, size:0x2ca90000.
Jul 14 23:49:21 localhost kernel: [ 8690.306447] Mapped heap -- Offset:0x8100000, size:0x700000, reference count:2, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306449] Mapped heap -- Offset:0x3f00000, size:0x600000, reference count:1, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306451] Mapped heap -- Offset:0x5800000, size:0x700000, reference count:2, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306453] Mapped heap -- Offset:0x5100000, size:0x700000, reference count:2, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306455] Mapped heap -- Offset:0x7b00000, size:0x600000, reference count:1, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306457] Mapped heap -- Offset:0x7500000, size:0x600000, reference count:2, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306459] Mapped heap -- Offset:0x6f00000, size:0x600000, reference count:2, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306461] Mapped heap -- Offset:0x6900000, size:0x600000, reference count:2, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306463] Mapped heap -- Offset:0x6300000, size:0x600000, reference count:2, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306465] Mapped heap -- Offset:0x4500000, size:0x600000, reference count:2, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306467] Mapped heap -- Offset:0x4d00000, size:0x400000, reference count:2, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306469] Mapped heap -- Offset:0x3c00000, size:0x300000, reference count:2, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306471] Mapped heap -- Offset:0x3500000, size:0x700000, reference count:3, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306473] Mapped heap -- Offset:0x2e00000, size:0x700000, reference count:2, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306475] Mapped heap -- Offset:0x2700000, size:0x700000, reference count:3, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306477] Mapped heap -- Offset:0x2300000, size:0x400000, reference count:5, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306479] Mapped heap -- Offset:0x1f00000, size:0x400000, reference count:6, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306481] Mapped heap -- Offset:0x1b00000, size:0x400000, reference count:5, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306483] Mapped heap -- Offset:0x1700000, size:0x400000, reference count:3, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306485] Mapped heap -- Offset:0x1000000, size:0x700000, reference count:17, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306487] Mapped heap -- Offset:0x900000, size:0x700000, reference count:16, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306489] Mapped heap -- Offset:0x200000, size:0x700000, reference count:40, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306491] Mapped heap -- Offset:0x0, size:0x200000, reference count:16, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306494] Mapped heap -- Offset:0xef000, size:0x11000, reference count:1, mapping count:0,
Jul 14 23:49:21 localhost kernel: [ 8690.306552] GRBM : 0x3828, SRBM : 0x200000c0 .
Jul 14 23:49:21 localhost kernel: [ 8690.306555] CP_RB_BASE : 0x3cec00, CP_RB_RPTR : 0x20 , CP_RB_WPTR :0x20.
Jul 14 23:49:21 localhost kernel: [ 8690.306558] CP_IB1_BUFSZ:0x0, CP_IB1_BASE_HI:0x0, CP_IB1_BASE_LO:0x0.
Jul 14 23:49:21 localhost kernel: [ 8690.306560] last submit IB buffer -- MC :0x0. Can't found mapped physical page for this MC .
Jul 14 23:49:21 localhost kernel: [ 8690.306561] Dump the trace queue.
Jul 14 23:49:21 localhost kernel: [ 8690.306562] End of dump
Too bad we still don't know what's the cause... and why it seemed to be fine for so many days.
Update: Well, this is weird and worse and perhaps related. The first time that this happened to me was a few days ago. After 15 minutes of inactivity, the screen turns off, to save power, well, I think this is the third time that, when returning to the laptop and attempting to turn the screen back on, it doesn't. It's like the same thing that happens when resuming from sleep mode, the black screen.
I checked the logs, and in everything.log, these are the only entries from about that time:
Jul 15 18:03:01 localhost crond[820]: FILE /var/spool/cron/root USER root PID 12357 job sys-hourly
Jul 15 18:08:13 localhost kernel: [13935.470836] ath: txq: ffff88013002e8d0 axq_qnum: 2, mac80211_qnum: 2 axq_link: ffff88003782c160 pending frames: 1 axq_acq empty: 1 stopped: 0 axq_depth: 0 Attempting to restart tx logic.
Jul 15 18:15:44 localhost -- MARK --
Jul 15 18:32:02 localhost kernel: [15360.917332] SysRq : Keyboard mode set to system default
Jul 15 18:32:50 localhost kernel: [15408.634134] SysRq : Terminate All Tasks
Oh, this is so confusing, haha.
Last edited by AnnS (2011-07-15 23:18:49)

Wifi Lost and Network Preferences Inaccessible after Resume from Sleep

Macbook Pro, shipped with Lion.
I've had a problem when Lion resumes from sleep of not being able to access any networks. Specifically, the wifi symbol in the menu bar shows the pulsating waves, when clicked it reports that it is searching for networks, however it doesn't find the standard wireless network it is normally connected to at home, nor can I choose any further options in that dropdown menu. Specifically, I cannot access Network Preferences, via any GUI based method (don't know enough CLI to know how).
Most alarming is that this has happened in a couple of different scenarios:
1) normally putting the laptop to sleep if 2 different users are logged in via fast user switching
2) if the computer shuts itself down from the sleep position because it has been unplugged for too long.
Restarting does revert everything back to normal, but I was hoping for a less drastic fix. Sorry to gripe, but I'm especially disappointed because I'm a mac newbie, and between this and other problems, have had to restart this mac due to spinning pinwheels of death and the like more in 2 months than I ever have a Sony Vaio Z running Windows 7. Kind of disappointing that Mac has the less stable operating system.

That's awkward. It may not be the Mac itself making it unstable, but yet programs on it making it unstable (lazy developers maybe). Although do remember that OS X Lion is fairly new, and a few bugs are still being ironed out.
First thing you should do is Repair permissions. Open up Disk Utility, Chose your disk on the Left and click on the Repair Permissions button. This can take about 20 minutes and fixes most problems.
Questions:
Have you installed any additonal system prefence panels?
Have you installed any programs that alter with WiFi?
Does your WiFi Access point have enough strength for where you are?
If you have installed addional system preferences then I suggest that you go to Finder, and in the top bar click on "Go" and navigate to "Go To Folder". In that box put this: "~/Library/PreferencePanes" (No quotes though - and remember the "~" ).
It'll take you to a folder, copy those into a safe location and remove the contents of that folder.
If you are an Administrator of your computer then do the same in "/Library/PreferencePanes".
Hope all goes well! Good luck!

Airport no longer works after resuming from sleep

I got a new MacIntel a month or so ago, and it has always done this, under 10.4.4 and now 10.5.5
When resuming from sleep, airport shows full strength for second, then the signal disappears. NOTHING in settings, reconnecting etc will get it to work again. (this is 'deep' sleep, not just the display turning off)
If you restart (restart not shut down), then when it comes back, airport is just gone - even the menu bar indicator. The computer now thinks it has no airport installed at all. No matter how many times you restart, there is no longer any airport.
If you shut down, wait a minute and restart, it works as normal.
Since airport is the only way I connect to the network, and I don't want to waste electricity, this is unacceptable and clearly a flaw.
I called tech support and they had me move airport to the top of the list, delete plists and other stuff, none of which made any difference. I'm thinking this is a low level system software fault, and I hope I don't have to take it back for a motherboard replacement.

I also have this problem, although, not very often.
I'm still running 10.4.4. This never happened with
prior versions. Rebooting is the only way to
correct the problem. Simply turning off Airport and
turning it back on does not help.
Thats interesting actually because I Never had any trouble on my G5 iMac of otherwise identical specification, on on intel. Hmm. I was thinking this was an intel issue.
Wonder if its a hardware problem (though I suspect not).

[SOLVED] After resume from suspend to RAM, system is slow / unstable

Hello,
I have come across some strangeness when trying to suspend my system. The
computer is a lenovo U350. I have read a lot of threads on these subjects,
but I never found one that quite matched the experiences I'm having, so I felt
compelled to make a new post.
Here's what's going on: I boot into the terminal, and then run pm-suspend.
Within a few seconds, the computer goes to sleep, just as I had hoped. The
problem is that my computer seems a little groggy when I wake it back up.
Usually, when running a command like ps aux | less, the screen fills up very
quickly. After I resume from sleep, running ps aux | less is noticeably slow.
It takes a full second (+/- epsilon) to fill the screen. Other symptoms: if I
suspend / resume in the terminal, and then start a window manager (KDE), the
graphics will be slow and choppy, and when I try to exit the window manager, I
usually end up having to perform the dreaded REISUB after getting stuck on a
blank screen with a non-blinking cursor in the upper left hand corner.
Suspend / resume from KDE will result in either the black, non-responsive
screen as soon as I try to resume, or in the choppy graphics, followed by the
non-responsive black screen when I log out.
I looked at the process list before and after, and noticed that when the
system is first resumed, there are around 50-60 additional kworker processes
running than when I put it to sleep. I don't know if this is normal or not.
Also, hci0 has been killed, and a new hci0 process has taken its place. The
same goes for one of the udevd processes. About 40-50 of the kworker
processes finish after a few minutes, but this does not change the slowness of
ps aux | less, nor does it help with my window manager issues.
I ran a few (not so precise) performance tests before and after doing a
suspend, and got the same results (the test was just to compile some LaTeX,
which took about 4-5 seconds either way).
I examined the pm-suspend.log, and everything looked peachy. All of the
hooks returned success for the suspend, as well as the resume. I'm happy to
post this if needed. I did not change any of the default settings for
pm-suspend.
Anyhow, I've read a lot of threads, and seen a lot of suggestions, e.g.:
https://bbs.archlinux.org/viewtopic.php?id=137682
https://bbs.archlinux.org/viewtopic.php?id=136292 (use vbetool?)
https://bbs.archlinux.org/viewtopic.php?id=126174 (suspend tons of modules?)
https://bbs.archlinux.org/viewtopic.php?id=131827 (hpet=disable ?)
However, I'm not that confident in any of them, since no one had quite the
same issue. I was hoping that someone could point me in the right direction
before I start blindly walking through all the candidate fixes and risk
unleashing chaos into my system. Many thanks in advance for your help.
Oh, and in case this post was not yet long enough, here is some system
information:
lspci:
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 03)
00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03)
00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
03:00.0 Network controller: Intel Corporation PRO/Wireless 5100 AGN [Shiloh] Network Connection
08:00.0 Ethernet controller: Broadcom Corporation NetLink BCM57780 Gigabit Ethernet PCIe (rev 01)
lsmod:
Module Size Used by
aes_x86_64 7508 3
cryptd 8309 0
aes_generic 26138 1 aes_x86_64
coretemp 5590 0
cpufreq_ondemand 6164 2
acpi_cpufreq 5877 1
mperf 1275 1 acpi_cpufreq
freq_table 2515 2 acpi_cpufreq,cpufreq_ondemand
arc4 1410 2
joydev 9895 0
snd_hda_codec_hdmi 24121 1
iwlwifi 248196 0
i915 420018 3
snd_hda_codec_conexant 47300 1
uvcvideo 64311 0
mac80211 228527 1 iwlwifi
videodev 82101 1 uvcvideo
snd_hda_intel 23375 0
snd_hda_codec 89389 3 snd_hda_intel,snd_hda_codec_conexant,snd_hda_codec_hdmi
broadcom 7270 0
tg3 134884 0
ideapad_laptop 8534 0
snd_hwdep 6389 1 snd_hda_codec
snd_pcm 74780 3 snd_hda_codec,snd_hda_intel,snd_hda_codec_hdmi
snd_page_alloc 7153 2 snd_pcm,snd_hda_intel
snd_timer 19544 1 snd_pcm
snd 59214 7 snd_timer,snd_pcm,snd_hwdep,snd_hda_codec,snd_hda_intel,snd_hda_codec_conexant,snd_hda_codec_hdmi
iTCO_wdt 11885 0
v4l2_compat_ioctl32 8316 1 videodev
i2c_i801 8187 0
i2c_algo_bit 5263 1 i915
drm_kms_helper 26137 1 i915
intel_agp 10904 1 i915
btusb 11385 0
cfg80211 172260 2 mac80211,iwlwifi
bluetooth 151999 1 btusb
sparse_keymap 3120 1 ideapad_laptop
soundcore 6210 1 snd
drm 188499 4 drm_kms_helper,i915
rfkill 15498 3 bluetooth,cfg80211,ideapad_laptop
serio_raw 4429 0
iTCO_vendor_support 1961 1 iTCO_wdt
media 10597 2 videodev,uvcvideo
psmouse 61311 0
libphy 16985 2 tg3,broadcom
i2c_core 20492 6 drm,drm_kms_helper,i2c_algo_bit,i2c_i801,videodev,i915
intel_gtt 14519 3 intel_agp,i915
pcspkr 1819 0
evdev 9530 8
thermal 7799 0
wmi 8475 0
battery 6453 0
ac 2344 0
video 11164 1 i915
button 4470 1 i915
processor 25582 3 acpi_cpufreq
ext4 420412 3
crc16 1359 2 ext4,bluetooth
jbd2 71499 1 ext4
mbcache 5881 1 ext4
sd_mod 28307 5
ahci 20037 4
libahci 19559 1 ahci
libata 166654 2 libahci,ahci
scsi_mod 133676 2 libata,sd_mod
uhci_hcd 23116 0
ehci_hcd 40698 0
usbcore 146113 5 ehci_hcd,uhci_hcd,btusb,uvcvideo
usb_common 954 1 usbcore
Last edited by wes (2012-04-06 21:34:43)

I did try reinstalling, actually. But I did not think to remove the battery and the ram... I'm very curious now: what is the rationale / intuition for that? Or is it just that empirical evidence suggests this may be a good idea?
Anyhow, the reinstall by itself did not help. I tried it out with a pretty bare-bones setup and had the same results. Here are a few other things I noticed:
- After the suspend, one of the cores is always running at the maximum clock frequency, according to powertop (although, according to ps aux, no one is doing any work).
- Even if I ssh to a nearby machine, I get the same experience when running `ls`. The screen fills very slowly. That narrows things down a little bit, but I was already guessing it would be graphics-related.
I have also tried a few random kernel boot parameters after reading things online, but none of those worked, and several stopped the machine from booting at all.
Thanks for your help.

T440S OSD Brightness control failure after resume from Sleep

Hi,
I have owned a T440S since late 2013.
Relevant Details:
T440S
Model : 20AQCTO1WW
OS : Windows 7 professional (original installation by Lenovo)
Latest Drivers installed as of June 2014 - including HotKey and Power Management
HotKey ver : 8.30
Power Managment : 6.65.1
Since receiving this laptop, OSD birightness control has always failed to work, i.e. does not appear on the screen
when using the Fn+F5/F6 key combination nor does it control actual screen brightness AFTER FIRST resuming from sleep
mode.
Sequence of steps that demonstrates the above symptom:
1. OSD brightness works fine after reboot
2. Putting the machine to sleep (I do not use hibernate) for a duration longer than a few minutes
3. Open lid the first time, hit Fn to resume machine
4. Pressing Fn+F5/F6 key combo does not display the brightness slider nor does it control brightness
5. Closing the lid and opening it again, causes OSD brightness slider to flash brifely and is now fully functional
using Fn+F5/F6 keys
Your tech department should easily be able to re-create this issue on any stock T440S/Win7pro machine, as
I have seen others comment about this very issue across other T440/OS variants.
This very same behavior has been there since the beginning.
When is Lenovo going to FINALLY FIX IT ONCE AND FOR ALL?
Thx,
--Alon
Solved!
Go to Solution.

Try this hotfix:
https://support.microsoft.com/kb/2752407
W520: i7-2720QM, Q2000M at 1080/688/1376, 21GB RAM, 500GB + 750GB HDD, FHD screen
X61T: L7500, 3GB RAM, 500GB HDD, XGA screen, Ultrabase
Y3P: 5Y70, 8GB RAM, 256GB SSD, QHD+ screen

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.

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.

T60 Type 2623 Blue Screen on Resume from Sleep Mode problem solved - XP Pro

I hope that this post ends some frustrations for some people.
I hope that IBM deals with this issue by getting ATI to fix the video driver issue.
After three months of tracking down blue screens when resuming from Sleep Mode and some lockups while working, I have identified the problem on my T60 Type 2623 running Windows XP-Pro and all service packs and updates. The Sleep Mode resume issues were intermittant and it would be fine for a day or two and then reboot on Resume or reboot every time I used Resume for a while. For months the Blue Screen would reboot and attempt to send the message to Microsoft using the logs, but the logs were always corrupted. I disabled every driver that I could and the problem continued for months.
The problem solution came about when I decided to try my Rhapsody Music account after many months of not using it. I kept getting a message about DRM (Digital Right Management) being disabled and Rhapsody software could not self-fix this. So I finally called Rhapsody and they spent over an hour with me trying to get Rhapsody to work. The support person asked me about my computer and I noted that it was an IBM T60. He then asked about my Video Card and I responded that it was an ATI Mobility Radeon X1300. After a few minutes on hold he asked about my driver version which was 8.442.3-080103a1-057754C the set from January 31, 2008. He noted that there is a known problem wit the 8.4 driver and it interferes with DRM. He had me go to control panel Settings and Hardware and then roll-back the driver to the prior version.
After a reboot, the DRM issue was solved and I soon discovered that my resume from Sleep mode no longer crashed. In fact it has been fine and crash free for over a month now. I have noted that the older driver can sometimes resize my screen to something like 600 X 800 if I close the lid under certain circumstances, but that is just a function key reset to get my normal desktop resolution back. At least it is not a blue screen reboot with a corrupted log file.
Message Edited by retro74 on 07-05-2008 08:50 AM
Solved!
Go to Solution.

Unfortunately I could not fix the problem so I wiped my system and loaded all new drivers before I found this posting.
Is there a way to get the old ATI driver that works? The only one available on the ATI and Lenovo website is the latest one with the problem. I agree with you David, Lenovo should have fixed this problem already with ATI.
John

White screen when resuming from standby

Hey,
For about a week when I resume from standby by opening the lid I get a white screen.
I'm using a MacBook Pro 2,7 GHz, Intel Core i7 with 4 GB ram bought in September this year (2011). Fully updated as of today.
Basically, I close the lid of the laptop before I go to sleep and when I open it the next day the screen goes white. So far I have remedied this by pushing the power button which forces the Shut Off options to appear and the white screen is gone.
Is this something I should be concerned about? I've read about the "White Screen of Death."
Anyone else have this issue?

Please read this whole message before doing anything.
This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of this exercise is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login. Boot in safe mode and log in to the account with the problem. First, disconnect all wired peripherals except keyboard, mouse, and monitor, if applicable, and remove all aftermarket expansion cards. The instructions provided by Apple are as follows:
Be sure your Mac is shut down.
Press the power button.
Immediately after you hear the startup tone, hold the Shift key. The Shift key should be held as soon as possible after the startup tone, but not before the tone.
Release the Shift key when you see the gray Apple icon and the progress indicator (looks like a spinning gear).
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Safe mode is much slower to boot and run than normal, and some things won’t work at all, including your login items.
Test. Same problem(s)?
After testing, reboot as usual (i.e., not in safe mode.)

T60p - Unexpected death on resume from 15 minutes of standby or hibernation

Similar Messages

Maybe you are looking for