KT4V doesn't resume from S3 with Keyboard/Mouse

Hi there,
I have a problem with a KT4V, I can get into S3 state without problem and resume by using the power switch.
However, it refuses to resume using the keyboard. I have tried setting the "wake from keyboard" option in the bios to any key or to a specific key with no luck. ACPI is ON, APM is on, the bios settings are otherwise unchanged from their default config.
I'm using a "no brand" PS2 keyboard, which has a "sleep" and "wake" buttons, and the "sleep" button works fine. I have tried with other keyboards (mistubishi...) with the same result. My mouse is a MS intellimouse optical on the PS2 port. The light at the tail of the mouse is off while in S3 state.
My config is pretty standard: Windows XP SP1, GForce2MX, 512MB, Athlon 2100+... the box is otherwise stable and good.
ok, you might say I'm being picky, but the case is under the desk and behind some casing, and it's a bit of a pain to access the power switch :-)
Thanks
eric

Quote from: Fredrik on 30-December-08, 04:12:24
Bet you have a power supply unit, too.
When or how did the trouble start?
Well, I have 2 of them. The main is Thermaltake PurePower 750W and the auxiliary (powering drives and case fans) is Hiper Type-R 480W in 3R Systems R900 chassis.
The problem is there from the start and the same setup (except for motherboard) worked perfectly with Asus M2N32-SLI Deluxe motherboard.
I've recently tried Vista x64 - with the same symptoms.

Similar Messages

[solved] resume from s3 by keyboard/mouse input

PC wouldn't resume via keyboard input. It works after a BIOS reset now. I must have set a wrong option somewhere.
I also had to do "echo USBE >> /proc/acpi/wakeup".
Last edited by demian (2010-05-06 15:25:46)

I tried with [OS] and the USB devices do receive power during sleep but can't bring the computer out of sleep.
Can anyone with BIOS 1.6 on a 890gxm confirm that the USB box is available?
Quote from: foo_fighter on 30-May-10, 04:47:22
Yup, that selection is grayed out and I cannot even select it, it just passes right over it. Unlike the cell menu where its gray but you can still select it and change the voltages.
I will try switching to [OS] and hopefully that helps.

Crashes when resuming from standby with Bluetooth mouse

Unless I turn off my Logitech Bluetooth mouse BEFORE entering sleep, the Mac crashes completely when trying to wake it up. the screen doesn't turn on, unless I plug in an external display adapter -- in which case it just turns on into a blank blue desktop.
So long as I remember to turn off the mouse before sleep and back on after resuming, all is well. But it's a pain to remember and if I forget, I have to physically reset--loosing all unsaved work.
Any ideas?

if you are having a sleep issue you could possibly try this troubleshooting step of resetting your SMC http://docs.info.apple.com/article.html?artnum=303319

Mountain lion download doesn't resume from where it left after an error occur

I'm trying to download mountain lion but the download doesn't resume from where it stopped when I encounter a drop in my Internet connection/get disconnected. Also I face that after this sequence of events: Internet error occur > surprisingly download resume from where it left > pause the download > resume the download after a few hours. My questions are: how can I solve this issue ? Does the downloaded file/app get corrupted when the download encounters an error which is actually making it restart the whole download? It's really frustrating, I've been downloading for the last couple of days and the downloads restarts even after downloading over one gigabyte. P.s: my Mac meets with the hardware and software requirements for downloading mountain lion.

Does the downloaded file/app get corrupted
A slow internet connection for huge files like Mountain LIon (4.34 GB), can time out before the file is completely downloaded.
Try this... from the App Store menu bar top of your screen click Store > Check for Unfinished Downloads.
Something to keep in mind if you need to repair the startup disk or reinstall OS X.
"Reinstalling OS X Lion or OS X Mountain Lion via OS X Recovery requires broadband access to the Internet via Wi-Fi or an Ethernet connection. OS X is downloaded over the Internet from Apple when OS X Recovery is used for reinstallation."
From here > OS X Lion: About Lion Recovery
So if it's possible, contact your ISP to see if you can upgrade to a faster connection.

MacBook Pro resumes from sleep, but keyboard types symbols as opposed to correct letters

Hi, all,
Having been a mac owner for a few years now, I guess it actually shows the quality of the product that this is the first time I've had to post on this site.
I've recently upgraded from my 2008 model MacBook to an early 2011 model MacBook Pro 17" with Lion. This machine was brand new when I purchased it, and is a very lovely bit of kit.
The problem comes from the sleep functionality. Approximately one time of three, when I resume from sleep, the keyboard will be malfunctioning. What I mean by this is that when I type letters, they come out as symbols instead. I haven't been sharp enough to get a direct mapping of A-Z yet (I will do next time), but these aren't the 'ALT' key symbols (å∂ß∫å˙∂©ß), they're more like this (which is what I typed into Notepad last time this happened) =
ƒ∆∂∆ßåß∂ƒ∂∆ß∆å˚¬ß∆¬ß
In order to resolve this, I need to restart the computer, which, thus far, has resolved the issue every time. That said, it's a bit of a pain, so would like to know what's going on and if there is any way to prevent it.
All the software on the mac is up to date at time of writing, there have been no expansions to the machine (yet), so it's exactly as shipped. It's the 2.2GHz i7 Quad Core device, and is the first one supporting the thunderbolt graphics connector.
Does anyone have any idea about this? Could it be a hardware problem (if so, I want to return it asap to get it sorted). I've looked all over google for this, but not found a single result, so was keen to see if anyone on here had experienced it before I start the arduous process of working out if it's a hardware issue.
Cheers,
SB

No one else experienced anything like this, then?

Pc doesn't resume from suspend to ram anymore (new 3.4.2 kernel)

hi.
I was using nouveau without problem and with the little trick of using acpi_os_name="Microsoft Windows NT" kernel parameter, I was able to suspend to ram from gnome, and resume the pc without problem
Not anymore. Now, if I suspend to ram, the pc does not resume. It correctly wake up the dvd drive, the hard-drive, began to read stuff on the hdd but the led of the power button stays blinking and the screen is not waken up.
I am thinking this is due to the update of nouveau and a new regression but this seems related to the bios or hardware. For example. If after the broken resume, I hold down 10 seconds the power button to power off, and press it again to power on, the led is still blinking and it does not boot. I need to power off by removing the power cord.
Is it because I run (to test it) the nvida-173xx, and that did something to the graphic card ?
Did anyone got similar problem with the new nouveau driver ?
I tried to downgrade libgl, libdrm, libdrm-nouveau, nouveau-dri, xf86-video-nouveau and mesa but I still got the problem. so ?
I have a geforce 8300 GS. the pc is an inspiron 531
Last edited by solstice (2012-06-18 08:56:49)

Probably I have the same issue with geforce GTS250.
After upgrading to kernel 3.4.2 or so, my system doesn't resume from suspend, only black screen and cannot switch to other ttys.
I first thought this problem be caused by the kernel, but downgrading nvidia to 295.53-2 solved this problem on kernel 3.4.3 so this likely is caused by nvidia 302.17.
In my case there is something like error in pm-suspend.log when resume failed:
Fri Jun 22 05:36:12 JST: Awake.
Fri Jun 22 05:36:12 JST: Running hooks for resume
Running hook /usr/lib/pm-utils/sleep.d/99video resume suspend:
/usr/lib/pm-utils/sleep.d/99video resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler resume suspend:
/usr/lib/pm-utils/sleep.d/98video-quirk-db-handler resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/95led resume suspend:
/usr/lib/pm-utils/sleep.d/95led resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/94cpufreq resume suspend:
/usr/lib/pm-utils/sleep.d/94cpufreq resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/90clock resume suspend:
/usr/lib/pm-utils/sleep.d/90clock resume suspend: success.
Running hook /etc/pm/sleep.d/90alsa resume suspend:
xcb_connection_has_error() returned true
And curiously, if I had launched vlc media player before suspend, resume worked well even on nvidia 302.17.

Computer with Z68A-GD65 (G3) mainboard doesn't resume from sleep

Hi,
Recently I've been having a lot of trouble with my Z68A-GD65 (G3) / Geforce GTX 550 Ti combination, starting after Microsoft updated my graphic drivers to the latest version.
BSOD, hangups , mouse freezes were there all the time so I did a few things to make things stable again, installing older drivers and updating the BIOS of the mainboard to the latest I could find , being 7681vP8.zip
After this the system became stable again, but I have this weird problem that I never had before: sleep mode works, and most of the time it resumes, but not after a longer period of sleep, lets say a whole night....
When I try to resume from sleep mode after a night, the system boots but I can't see anything on the screen , the graphic card doesn't resume.
Does anyone know what this could be?

Matt GB, Certain aspects of OC'ing and updating software are best done manually in any case.
Your initial disappointment reflects to an extent my own, but with a bit of testing and patience the confidence in the board returned and I am now pretty pleased with the results so far. Please check my feedback in the Beta BIOS thread after the last N31 release.
May I suggest that you take the time and report your personal findings to MSI technical so that they can address your concerns. Just complaining about what you are unable to achieve serves absolutely no purpose at all. We are all here to contribute to finding solutions.
>>How to contact MSI.<<

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)

Msi Z68 GD65 (B3) will not resume from sleep with multiplier above 43

I have an i5 2500k that is otherwise stable (can pass prime95 for hours) at 4.4 ghz, but no matter what I do I cannot get my computer to resume from sleep properly when I go over 4.3 ghz. At 4.3 ghz it resumes from sleep fine, but once the multiplier goes over 43 it simply will not resume. The monitor stays in standby mode, but my PC's fans spin up and my keyboard backlight turns on.
I have tried disabling and enabling pll overvoltage, but it does not help.
It resumes from hibernation fine, but that takes quite a bit longer than resuming from sleep because the POST on this board isn't particularly fast.
This happened both with my previous card (560 ti) and my current card (7950), so I seriously doubt it is a GPU issue. I have a seasonic x750 PSU, so I doubt it is a power issue. I have very good cpu cooling and my temperatures are pretty low even under load. Is this a board defect? I see that ASUS boards had a similar issue that was apparently fixed, but I can't find as much info about an MSI isssue.

Being an experienced OC'er, then you know that trial and error is the tried and true time honored method in the attempt to solve problems. The solution I would recommend is to accept an OC of 4.3, stick with hibernation, or continue with experimentation of combinations of settings, or you can hope someone comes along that 'may' know of a 'solution'.
Quote
I see that xxxx boards had a similar issue that was apparently fixed, but I can't find as much info about an MSI isssue.
Big difference between 'apparently' fixed and actually fixed. You might try MSI Technical, but it may be interesting what they say once they know OC'ing is involved.
>> How To Contact MSI <<
Quote
Thank you for the patronizing response. Does anyone have a response that is actually useful instead of generic "you don't know what OCing does" comments? I have been OCing for years; I know what it does to a system. I am looking for SOLUTIONS here.
Some friendly advice is to watch the attitude, or not many will be inclined to offer any assistance at all. Yours is not a situation that the mainboard is non functional, and is more related to an OC'ing behavior.

USB ports don't work after resuming from standby with Windows 8 on X230 tablet

I have just done a clean install of Windows 8 on my X230 tablet. Before installing Windows 8 I installed the most recent BIOS for this machine (version 2.50). After installing Windows 8 I installed System Update from the Lenovo Website and downloaded all the recommended drivers and other files. I've also installed all the latest Windows 8 updates.
Here are the symptoms of my problem: After resuming from standby/sleep mode, my USB ports do not work. My computer has two USB 3.0 ports and one USB 2.0 ports. All exhibit the same behavior. After resuming from standby mode I have tried inserting both my mouse and a USB thumbdrive, but neither are recognized. After restarting Windows, the USB ports work again... until I resume from standby mode again.
I hope there is a solution to this issue. It is very frustrating.

Thanks for the suggestion about tweaking the "Allow this computer to turn off this device" feature. I un-checked that box for every entry I could find under "Universal Serial Bus Controllers" in the Devide Manager. Unfortunately, the same symptoms of my problem persisted.
I went back and looked at the README file associated with the BIOS 2.50 download on Lenvo's support site. At the bottom of the file it gives a "Summary of Changes". Under version 2.03 of the BIOS (the version just before version 2.50), it says:
- (Fix) Fixed an issue where USB device might not detected when system resume from sleep mode.
This indicates that Lenovo support was already aware of such issues. The problem was intended to be fixed in version 2.03 of the BIOS. However, the issue persists on my machine, even with the latest BIOS.
Hopefully someone from Lenovo can comment here.

BSOD on resume from suspend with sandisk extreme ssd

Hello folks!
Has anyone had this happen?
After buying the sandisk extreme ssd and installing it, i get bsod every time when resuming from suspend.
I have tried other hdd with no problem, and tried a fresh install with win7 x64, but still have this problem with the sandisk..
Any ideas anyone would be aprreciated, thanks

I developed a waking problem from sleep mode when I changed out my ram to bigger. My Lenovo loses about 600mb of 'something' from memory between entering the sleep mode .. to waking up? I still haven't figured it out. You might want to try changing the memory sleep/suspend setting to just hibernate. You should wake up plenty fast from hibernate on that ssd. If using it.. you might also read up on the intel rapid storage technology. I read that needs uninstall/reinstall sometimes when changing to ssd.

Satellite Pro A100 - Resume from Sleep with IR multimedia remote control or keyboard

Hi Guys
I have dedicated my Satellite Pro A100 to be a media center that sits under the TV and can play networked media and DVD's etc.
This is using Vista.
The set up I want is that the lid is shut 24/7 365 and when I want to use it I just press "SLEEP" or power button from the remote control or keyboard and it fires up ready for action.
POINT TO NOTE. I successfully did this with my OLD Tecra M3. However was too slow for media center and vista
However I have set the power settings as I want etc, shut lid do nothing, and enabled hybrid sleep (preferred sleep).
Now I CAN put it to sleep with the multimedia keyboard or remote control. BUT can I wake it?...NO!. I have thought of everything possible....gone to device manager and made sure all the options for the remote and the keyboard and the USB reciever are set to WAKE FROM SLEEP. The only thing to wake it is the power button - which defeats the purpose of it being sat there like a dvd player.
when awake the remote and the keyboard function fine - I have made sure the batteries are recharged.
I have the latest BIOS and speaking of BIOS's there are no S3 power options I noticed , but then there werent on the M3 and that worked fine in terms of sleep and waking with the IR.
I come to the forum because although I know some older systems will not work with vista - IF the M3 will work - I am sure the twice as new and powerful A100 will.
Has anyone had this before - what have I missed it must be staring me in the face.
Thanks in advance.
P.S Also of late the touch pad has been playing up i.e the left and right clickers swap function so one second your working as normal next minute you left click and the right clikc menu appears. Reset BIOS - rebuilt - reinstalled synaptic - no difference.
When I worked in support for a big company when this started happening it wasnt good news - is it bad news?

Hi
Im not quite sure why it doesnt on your Sat Pro A100 and why it works on M3.
But fact is that Satellite Pro A100 doesnt support the FIR (Fast InfraRed) port and the
Tecra M3 supports the Fast InfraRed port.
Maybe this could be the reason why you cannot enable the notebook using the infrared multimedia remote control.
Greets

Geforce GTX 550 Ti doesn't resume from sleep mode sometimes after BIOS update

Hi there,
I updated the BIOS of my main board Z68A GD65 (G3) yesterday to the latest version on the MSI site (E7681IMS.P80) and I noticed that my PC doesn't always resume correctly from sleep mode now.
It seems that it works when I resume immediately, but after a nights rest the display remains black, although it looks like the PC itself is starting correctly (mouse, keyboard hdd etc)
Anyone know what this could be? Should i change a setting in the BIOS maybe?
Marcel

I`ve updated BIOS but problem wasn`t solved.
Did someine else face with problem?
Thanks.

Resuming from suspend with Ubuntu 11.04 fails on Thinkpad 121e when using OCZ Agility 3 SSD

Hi,
On my Thinkpad 121e (model 30515RG), Ubuntu 11.04 worked flawlessly with the stock hdd. Suspend and resume were fine. After I replaced the hdd with an Agility 3 120 GB drive, the system will suspend fine (pulsating leds, etc) After I attempt to resume, I get the thinkpad beep, the resume starts and than fails. The filesystem used in both cases is ext4.
If I suspend before I log in, while only gdm is running, the system will come up, but will not function as it can not read any file from the disk, reporting missing inodes, etc.
If I suspend after being logged in, I might get a visible cursor, but nothing more.
The drive has the latest version of firmware installed. Any suggestions ?
Thanks!
Gori

I though bugs should not be submitted for testing. Anyways, here it was http://bugs.archlinux.org/task/13651

Toggle Play and Resume System Variables with Keyboard Shortcut

Hey Folks,
In many popular video applications (YouTube, Vimeo, Hulu, etc), the Spacebar is used to Play (and then) Pause the movie and I want my project to stay consistent with this.
I'd like to have a single keyboard shortcut (maybe to a hidden button on a Master Slide) that,Plays or Pauses (depending on what is happening) a slide video (or the entire project really), and I want that shortcut to be the Spacebar.
I will be having slide videos (user clicks an Image to go to a slide video, not event video). Playbar will be visible during this time.
In trying to accomplish this, I see that cpCmndPause is an available System Variable. I would assume cpCmndResume is the counterpart to that, or is cpCmndPause=0 the counterpart?
Anyone have an idea how to accomplish this?
Thanks,
Tom

Spacebar cannot be assigned as a shortcut key. probably because it will be reclaimed by browser. The toggle part is easier.
Toggle Shape buttons - Captivate 6 - Captivate blog
Custom Play/Pause button in Captivate - Captivate blog

KT4V doesn't resume from S3 with Keyboard/Mouse

Similar Messages

Maybe you are looking for