Resume from suspend broken after upgrade

Hi, I'm having a hardware issue noone else seems to be having. I mean, I can't find any discussions or bug reports about it anywhere. :-(
The specifics:
Resume from suspend broke after an upgrade. X starts, windows appear, and I can move the cursor around, but everything else is frozen. The only way out is to hit C-A-F1 to switch to the virtual console and restart X or reboot.
Please, any help will be greatly appreciated.
I'm running:
local/lib32-nouveau-dri 9.1.1-1
extra/nouveau-dri 9.1.1-1
extra/xf86-video-nouveau 1.0.7-1 (xorg-drivers xorg)
local/linux-ck 3.8.6-1
local/linux-ck-headers 3.8.6-1
An extract of my Xorg.0.log during suspend/resume:
[    43.750] (II) AIGLX: Suspending AIGLX clients for VT switch
[    43.750] (II) NOUVEAU(0): NVLeaveVT is called.
[    53.660] (II) AIGLX: Resuming AIGLX clients after VT switch
[    53.660] (II) NOUVEAU(0): NVEnterVT is called.
[    53.694] (II) NOUVEAU(0): EDID vendor "PHL", prod id 2151
[    53.694] (II) NOUVEAU(0): Using hsync ranges from config file
[    53.694] (II) NOUVEAU(0): Using vrefresh ranges from config file
[    53.694] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[    53.694] (II) NOUVEAU(0): Modeline "1920x1200"x0.0  154.00  1920 1968 2000 2080  1200 1203 1209 1235 +hsync +vsync (74.0 kHz eP)
[    53.694] (II) NOUVEAU(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[    53.694] (II) NOUVEAU(0): Modeline "800x600"x0.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
[    53.694] (II) NOUVEAU(0): Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
[    53.694] (II) NOUVEAU(0): Modeline "640x480"x0.0   31.50  640 664 704 832  480 489 492 520 -hsync -vsync (37.9 kHz e)
[    53.694] (II) NOUVEAU(0): Modeline "640x480"x0.0   30.24  640 704 768 864  480 483 486 525 -hsync -vsync (35.0 kHz e)
[    53.694] (II) NOUVEAU(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[    53.694] (II) NOUVEAU(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
[    53.694] (II) NOUVEAU(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[    53.694] (II) NOUVEAU(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[    53.694] (II) NOUVEAU(0): Modeline "1024x768"x0.0   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz e)
[    53.694] (II) NOUVEAU(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[    53.694] (II) NOUVEAU(0): Modeline "832x624"x0.0   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync (49.7 kHz e)
[    53.694] (II) NOUVEAU(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
[    53.694] (II) NOUVEAU(0): Modeline "800x600"x0.0   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz e)
[    53.694] (II) NOUVEAU(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
[    53.694] (II) NOUVEAU(0): Modeline "1152x864"x60.0   81.62  1152 1216 1336 1520  864 865 868 895 -hsync +vsync (53.7 kHz e)
[    53.694] (II) NOUVEAU(0): Modeline "1280x960"x0.0  108.00  1280 1376 1488 1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
[    53.694] (II) NOUVEAU(0): Modeline "1280x720"x60.0   74.48  1280 1336 1472 1664  720 721 724 746 -hsync +vsync (44.8 kHz e)
[    53.694] (II) NOUVEAU(0): Modeline "1440x900"x0.0   88.75  1440 1488 1520 1600  900 903 909 926 +hsync -vsync (55.5 kHz e)
[    53.694] (II) NOUVEAU(0): Modeline "1440x900"x0.0  136.75  1440 1536 1688 1936  900 903 909 942 -hsync +vsync (70.6 kHz e)
[    53.694] (II) NOUVEAU(0): Modeline "1600x1200"x0.0  162.00  1600 1664 1856 2160  1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
[    53.694] (II) NOUVEAU(0): Modeline "1680x1050"x0.0  119.00  1680 1728 1760 1840  1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
[    53.694] (II) NOUVEAU(0): Modeline "1920x1200"x0.0  154.00  1920 1968 2000 2080  1200 1203 1209 1235 +hsync -vsync (74.0 kHz e)
[    60.180] (II) AIGLX: Suspending AIGLX clients for VT switch
[    60.180] (II) NOUVEAU(0): NVLeaveVT is called.
[   131.086] (II) evdev: Logitech USB Optical Mouse: Close
[   131.087] (II) UnloadModule: "evdev"
[   131.087] (II) evdev: Microsoft Wired Keyboard 400: Close
[   131.087] (II) UnloadModule: "evdev"
[   131.087] (II) evdev: Power Button: Close
[   131.087] (II) UnloadModule: "evdev"
[   131.087] (II) evdev: Power Button: Close
[   131.087] (II) UnloadModule: "evdev"
[   131.089] (II) NOUVEAU(0): Closed GPU channel 0
[   131.092] Server terminated successfully (0). Closing log file.
(looks error free)

Thank you for your reply, pyther. I figured it was a kernel bug, too, but now I'm not so sure. Surprisingly, in Ubuntu 11.04 (which uses kernel 2.6.38), suspend works fine on my laptop. Figuring that perhaps this was due to an Ubuntu-specific patch, I tried booting the 2.6.38-8-generic kernel that ships with Ubuntu 11.04 on my Arch installation, but found that it was subject to the same issue described above, where the system fails to resume from suspend. I also tried disabling laptop-mode-tools, but to no avail.
Clearly, the problem is related somewhat to the kernel, as in my Arch installation, suspend works fine in 2.6.36, is somewhat problematic in 2.6.37, and is completely broken in 2.6.38. Yet I don't think it's entirely due to the kernel, as suspend works fine in Ubuntu 11.04, but is broken when I boot my Arch installation with Ubuntu's kernel. Performing a bit bisect to determine the bad commit sounds like it might help, but given that suspend functionality seems to have gotten progressively worse for me since 2.6.36, I'm not sure how I would go about locating a specific commit that is the source of my issues. Is there anything else I might try?

Similar Messages

  • Resume from suspend broken

    Hi guys,
    i have an old acer 5920G laptop with an NVIDIA 8600M GT with arch linux, nvidia proprietary drivers and kde4, all up to date.
    suspend to ram/resume has worked perfectly for years.
    after an update that could have happened about an year ago (can't tell anything better, 'cause i wrongly  thought that was a temporary issue that the following updates would solve) now when i resume my notebook, I get the kde login screen instead of my previous session.
    i took a look at the Xorg log file, journalctl, dmesg, but can't find any real error log message regarding the resume stuff.
    do you have any suggestion on where i can start digging to debug this?

    I have the same problem. You are using a Nvidia card, I guess? A temporary fix is to hit Alt+F2 and type 'r' if you are really annoyed by this. I just set my background to a solid color. There are bugreports already see here and here. It seems that some people using nouveau drivers are also affected, others are not. You may try them as a fix.
    Nvidia says: "Our current software architecture doesn't preserve the contents of FBOs across
    modeswitches or power events. As a result, our implementation relies on
    applications re-rendering to their FBOs every frame. This is a fundamental
    limitation of our design that will be fixed in the future."
    So we'll just have to wait.
    John
    EDIT: Btw. there is a post concerning the same issue on the first page of Applications & Desktop Envs: Gnome 3.14 Nvidia Wallpaper Artifacts it's about GNOME 3 but afaik Cinnamon is a fork of Gnome. At least it's based on GTK+ as well.
    Last edited by JohnKapri (2014-12-20 14:00:49)

  • Office 2013 - Word cannot establish a connection with this document after the system resumed from suspend mode

    Hiya!
    This issue has been answered numerous times for Office 2010 and Office 2007, but I have yet to any solutions or Hotfixes that work for Office 2013 (x64) on Win7.
    How to replicate the issue:
    Open a file from a network share.
    Edit file.
    Leave computer on with file open. Computer goes to sleep or into stand-by mode.
    Wait a bit
    Wake up computer
    CPU opens file in Read-Only mode and gives you the following error "Word cannot establish a network connection with this document after the system resumed from suspend mode. Save the document into a different file to keep any changes."
    What I've tried:
    http://support.microsoft.com/kb/2434898 - Office 2007 registry fixes. Does not apply.
    http://support.microsoft.com/kb/2413659 - Office 2010 problem. This exact issue. Says 'No microsoft products that match this hotfix are installed'
    Work Around:
    I can saving new versions of these files overrides this issue, but this is sometimes not possible for end-users who only have specific access to ONE SPECIFIC FILE in a particular network share.
    Please let me know how I can alleviate this issue!
    Thanks
    -Chris

    Hi,
    Are those problematic documents created via previous versions of Office?
    Please also try to run a repair of your Office 2013 installtion and check if it helps. See:
    http://office.microsoft.com/en-in/excel-help/repair-office-programs-HA010357402.aspx
    Regards,
    Steve Fan
    TechNet Community Support

  • System freeze after resume from suspend to RAM

    Hi,
    since quite a while (probably ever) I am unable to suspend my computer to RAM because everytime it freezes a few seconds after resuming, never to become alive again until a reboot. After some investigation, I managed to get kernel logs by taking a picture of my screen. The logs were not written to disk, hence I didn't see anything before. I had to write these by hand, I hope I didn't insert any mistakes:
    kernel: sas: Enter sas_scsi_recover_host busy: 2 failed: 2
    kernel: sas: trying to find task 0xfff880008b5b680
    kernel: sas: sas_scsi_find_task: aborting task 0xfff880008b5b680
    kernel: sas: sas_scsi_find_task: task 0xfff880008b5b680 is aborted
    kernel: sas: sas_eh_handle_sas_errors: task 0xfff880008b5b680 is aborted
    kernel: sas: trying to find task 0xffff8804606ccb40
    kernel: sas: sas_scsi_find_task: aborting task 0xffff8804606ccb40
    kernel: sas: sas_scsi_find_task: task 0xffff8804606ccb40 is aborted
    kernel: sas: sas_eh_handle_sas_errors: task 0xffff8804606ccb40 is aborted
    kernel: sas: ata7: end_device-0:0: cmd error handler
    kernel: sas: ata8: end_device-0:1: cmd error handler
    kernel: sas: ata7: end_device-0:0: dev error handler
    kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    kernel: ata7.00: failed command: READ VERIFY SECTOR(S)
    kernel: ata7.00: cmd 40/00:01:00:00:00/00:00:00:00:00/e0 tag 11
    res 40/00:48:a0:79:88/00:00:07:00:00/40 Emask 0x4 (timeout)
    kernel: ata7.00: status { DRDY }
    kernel: ata7: hard resetting link
    kernel: sas: ata8: end_device-0:1: dev error handler
    kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    kernel: ata8.00: failed command: READ VERIFY SECTOR(S)
    kernel: ata8.00: cmd 40/00:01:00:00:00/00:00:00:00:00/e0 tag 11
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    kernel: ata8.00: status { DRDY }
    kernel: ata8: hard resetting link
    This issue seems to be related to disk failures like bad sectors but I am quite sure, that my SSDs are in a good shape. I ran some SMART tests, they all turned out to be okay. Suspending from my dual-booted Windows works fine as well (although if the bad sector would be on the linux partition, it would probably not affect Windows).
    Here's my setup:
    $ lsblk -St
    NAME HCTL TYPE VENDOR MODEL REV TRAN NAME ALIGNMENT MIN-IO OPT-IO PHY-SEC LOG-SEC ROTA SCHED RQ-SIZE RA WSAME
    sda 1:0:0:0 disk ATA Corsair Force 3 2 sata sda 0 512 0 512 512 0 cfq 128 128 0B
    sdb 7:0:0:0 disk ST1000DM 003-9YN162 NDP3 usb sdb 0 512 0 512 512 1 cfq 128 128 0B
    sdc 0:0:0:0 disk ATA OCZ-REVODRIVE3 2.25 sas sdc 0 512 0 512 512 0 cfq 128 128 0B
    sdd 0:0:1:0 disk ATA OCZ-REVODRIVE3 2.25 sas sdd 0 512 0 512 512 0 cfq 128 128 0B
    sr0 2:0:0:0 rom TSSTcorp CDDVDW SH-222AL SB00 sata sr0 0 512 0 512 512 1 cfq 128 128 0B
    $ lsblk -f
    NAME FSTYPE LABEL UUID MOUNTPOINT
    sda
    ├─sda1 ntfs Recovery 567437B974379B27
    ├─sda2 vfat DC2D-099E /boot
    ├─sda3
    ├─sda4 ntfs FEBED982BED933BD
    ├─sda5 ext4 arch 41bad924-84a2-4e0a-9cd4-4ea723a2a5a3 /
    └─sda6 swap 793fb3c1-8bec-4023-a7c3-ee94eee2e67a [SWAP]
    sdb
    └─sdb1 ntfs HDDRIVE2GO 2212E50812E4E231
    sdc
    └─sdc1 linux_raid_member home:0 208937dc-2904-e71c-435a-9928671e07a3
    └─md0 ext4 revodrive ffe9d38f-87f2-44e1-ae26-f36c910af3c5 /home
    sdd
    └─sdd1 linux_raid_member home:0 208937dc-2904-e71c-435a-9928671e07a3
    └─md0 ext4 revodrive ffe9d38f-87f2-44e1-ae26-f36c910af3c5 /home
    I am not sure which one of the disks causes the freeze but I assume it's the revodrive because the logs talk about two drives. The Revodrive internally holds two drives, which are set up to operate in a RAID 0. Windows is installed on the Corsair drive, and has no access to the Revodrive. However, I used to run Windows on the Revodrive a few years ago, and it worked just fine.
    Another interesting thing is that when I try to test suspend to RAM, the system does not freeze, nor produce errors. This only happens if none is written to /sys/power/pm_test (which means no automated wake-up, no testing).
    Any ideas on how I could narrow down this issue? Thanks a lot!
    EDIT
    I just checked and confirmed that this issue is originating from the OCZ Revodrive:
    $ dmesg | grep ata7.00 | head
    [ 7.136432] ata7.00: ATA-8: OCZ-REVODRIVE3, 2.25, max UDMA/133
    [ 7.136436] ata7.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 31/32)
    [ 7.146442] ata7.00: configured for UDMA/133
    $ dmesg | grep ata8.00 | head
    [ 7.310018] ata8.00: ATA-8: OCZ-REVODRIVE3, 2.25, max UDMA/133
    [ 7.310023] ata8.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 31/32)
    [ 7.320022] ata8.00: configured for UDMA/133
    Last edited by tuttiarch (2015-01-31 15:54:29)

    Thank you for the link, unfortunally I don't have a NVIDIA card but use the Intel IGP (HD4600, Haswell) - maybe I should have mentioned that...
    And other than in this bug report I cannot kill X or anything because neither other TTYs work - I cannot input anything (although the hotkeys work weird enough) nor is SSHD running because the system is completely frozen...
    Very funny thing is that for the last 2 days my system didnt freeze once (suspended about 6-7 times during one boot), even though for the 2 weeks prior to that, it froze EVERY SINGLE TIME I resumed from suspend, it didnt work once...

  • Touchpad permanently not working after resuming from suspend

    I lost touchpad and trackpoint functionality after resuming from suspend on my ThinkPad E530 (3259CTO).
    Even after a complete power off (with the battery removed), the touchpad is detected but doesn't send any event, and the trackpoint is not detected.
    In Windows, in the UltraNav control panel, the touchpad is marked as enabled and cannot be disabled, the trackpoint is grayed.
    In Linux, I can see the difference is kernel traces when the driver is loaded.
    Before : psmouse serio1: synaptics: Touchpad model: 1, fw: 8.0, id: 0x1e2b1, caps: 0xd001a3/0x940300/0x120c00
    Now    : psmouse serio1: synaptics: Touchpad model: 1, fw: 8.0, id: 0x1e2b1, caps: 0xd001a3/0x0/0x0
    After looking at https://gerrit.chromium.org/gerrit/#/c/31105/ and Synaptics public documentation, I was able to get more information : the device status register (F01_RMI_Data0) is 0x45, which means the touchpad is in flash programming mode since there is a firmware CRC failure.
    It looks like http://code.google.com/p/chromium-os/issues/detail?id=24298, so it's probably not a Lenovo specific problem, but a bug in Synaptics firmware.
    Can Lenovo provide the firmware to flash like http://forums.lenovo.com/t5/X-Series-ThinkPad-Laptops/X220-Touchpad-jumpy-response-when-used-with-90... which would hopefully make my touchpad working again ?
    The original firmware should work, but an updated one would be better, if it avoids losing the touchpad again later.

     I don't know why, but this made me think of the episode of the simpsons when home tries to get over 300 pounds so he can work from home.  When he tries to dial the phone he hist all the buttons and gets a recording that says "We're sorry, you're fingers are too fat. To obtain a special dialing wand, please mash the keypad now."
    BTW, sorry I can't help... but at least I am entertained easily.

  • No sound in Flash after resuming from suspend

    After I resume from a suspend or sleep there is no sound in Flash and there is no networking.
    The only way is to restart my browser to reestablish the sound.
    Is there a solution for this problem?
    Thanks.

    This does not happen with Firefox in Ubuntu, as an example. So something must be wrong somewhere.
    I can confirm this happens to me in Arch with Firefox 4.0b7 and Chromium 7.0.517.44. I noticed that after resuming from suspend, not only sound (in Flash) is missing, but Flash is behaving weirdly (YouTube video plays much faster) and CPU usage goes crazy without doing any particular action.
    Last edited by Niavlys (2010-12-05 23:34:30)

  • Dell Inspiron 7537 - Sound only works after resuming from suspend

    Hello,
    So my sound does not work after boot, only once I resume from suspend. So, once I turn on my computer, and I load sound, nothing work (everything is unmuted in Alsa) - then if I suspend my computer and resume - the sound works every time.
    I use Alsa and here is my amixer output (before and after suspend is the same) :
    eric@archlinux ~> amixer
    Simple mixer control 'Master',0
    Capabilities: pvolume pswitch pswitch-joined
    Playback channels: Front Left - Front Right
    Limits: Playback 0 - 65536
    Mono:
    Front Left: Playback 5358 [8%] [off]
    Front Right: Playback 5358 [8%] [off]
    Simple mixer control 'Capture',0
    Capabilities: cvolume cswitch cswitch-joined
    Capture channels: Front Left - Front Right
    Limits: Capture 0 - 65536
    Front Left: Capture 11003 [17%] [on]
    Front Right: Capture 11003 [17%] [on]
    What gets rebooted when I do a suspend, but not when I reboot? Does not seem to make sense to me.
    Thanks.

    Is there any additional information I can include to help figure this out?

  • System freeze after resume from suspend

    I am running arch for about 5 month now and I always had freezes after resuming from suspend (to ram - systemctl suspend) every once in a while (like once a week or less). The freezes increased massively over the last month or so and for about 2 weeks now it happens 95% of the times I resume from suspend.
    The monitor turns on and shows things exactly how I left them, but is completely unresponsible EXCEPT for I can switch to another TTY (Ctrl+Shift+F*), however I cannot type or do anything in it...
    It doesnt have anything to do with the X server as it also happens after I suspend from TTY (without any X running).
    I also checked journalctl -b -1 (shows previous boot, since I always have to hard-reset the system) but it doesnt show anything after:
    Mar 13 17:16:54 Ununhaswellium systemd-sleep[3624]: Suspending system...
    (the suspend event before resuming)
    Are there any log files that could give a hint on what exactly goes on after the resume?
    Im running the latest official 3.13.6-1 kernel and updated my BIOS to the latest beta version yesterday - didnt help either...
    Ive read pretty much every thread on the internet by now about freezes after resume from suspend but none really helped
    Last edited by CharlieBra7o (2014-03-15 09:58:51)

    Thank you for the link, unfortunally I don't have a NVIDIA card but use the Intel IGP (HD4600, Haswell) - maybe I should have mentioned that...
    And other than in this bug report I cannot kill X or anything because neither other TTYs work - I cannot input anything (although the hotkeys work weird enough) nor is SSHD running because the system is completely frozen...
    Very funny thing is that for the last 2 days my system didnt freeze once (suspended about 6-7 times during one boot), even though for the 2 weeks prior to that, it froze EVERY SINGLE TIME I resumed from suspend, it didnt work once...

  • Desktop visible after resume (from suspend) and before screen is locke

    My desktop becomes visible for brief period (<1s) when the system resumes from suspended state. My desktop env. is XFCE4, it happens with both xscreensaver and gnome-screensaver (also with slimlock and i3lock), therefore I think it's not locker dependent. It's a major security flaw because sensitive information may be exposed (not just porn). Using both XFCE provided locking facilities (suspend/resume lock options in Power Manager and Session settings), and systemd suspend/resume hooks yields same result. I remember back then when I was using Gnome, I haven't had this issues. Does anyone have any idea how to prevent this desktop expose?

    Have you tried this --> https://wiki.archlinux.org/index.php/Pm … or_suspend ?

  • No sound in flash after resume from suspend (linux debian)

    Using 10.0.r42, iceweael and linux 2.6.32 kernel.
    If I close the lid on my HP laptop which causes it to suspend, and the resume from suspend, other audio playing programs work, but I cant get any sound from iceweasel/flash until I kill all instances of iceweasel and restart the web browser.
    Is this a bug that is tied to flash?

    What a coincidence, mine is also from scratch.
    Good question about how sound is handled. ldd libflashplayer.so doen't give an answer.
    So somehow xulrunner can catch the sound.
    Libxpcom is linked to libasound. components/libmozgnome.so to libesd in my case.
    Maybe you can try fuser /dev/snd/* to identify which process is locking the device.

  • Resuming from suspend breaks function key on laptop

    I have an Asus K40IN laptop.  Up until a few days ago, suspending worked perfectly.  However, now when I resume from suspend, my function key no longer works.  I use it for some global shortcuts like play/pause, volume up/down, brightness up/down, etc.  I checked in xev, and it's actually registering no key press at all.  However, if I press it twice quickly, it will start registering infinite presses of the d key (keycode 43).  This also completely incapacitates the keyboard -- many keys do not do what they should.  It stops if I press the actual d key once.
    I'm guessing the most likely cause is a recent update.  Here's my recent /var/log/pacman.log:
    [2010-01-08 14:45] upgraded kernel26-firmware (2.6.32.2-2 -> 2.6.32.3-1)
    [2010-01-08 14:45] >>> Updating module dependencies. Please wait ...
    [2010-01-08 14:45] >>> MKINITCPIO SETUP
    [2010-01-08 14:45] >>> ----------------
    [2010-01-08 14:45] >>> If you use LVM2, Encrypted root or software RAID,
    [2010-01-08 14:45] >>> Ensure you enable support in /etc/mkinitcpio.conf .
    [2010-01-08 14:45] >>> More information about mkinitcpio setup can be found here:
    [2010-01-08 14:45] >>> http://wiki.archlinux.org/index.php/Mkinitcpio
    [2010-01-08 14:45]
    [2010-01-08 14:45] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
    [2010-01-08 14:45] ==> Building image "default"
    [2010-01-08 14:45] ==> Running command: /sbin/mkinitcpio -k 2.6.32-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
    [2010-01-08 14:45] :: Begin build
    [2010-01-08 14:45] :: Parsing hook [base]
    [2010-01-08 14:45] :: Parsing hook [udev]
    [2010-01-08 14:45] :: Parsing hook [autodetect]
    [2010-01-08 14:45] :: Parsing hook [pata]
    [2010-01-08 14:45] :: Parsing hook [scsi]
    [2010-01-08 14:45] :: Parsing hook [sata]
    [2010-01-08 14:45] :: Parsing hook [lvm2]
    [2010-01-08 14:45] :: Parsing hook [filesystems]
    [2010-01-08 14:45] :: Generating module dependencies
    [2010-01-08 14:45] :: Generating image '/boot/kernel26.img'...SUCCESS
    [2010-01-08 14:45] ==> SUCCESS
    [2010-01-08 14:45] ==> Building image "fallback"
    [2010-01-08 14:45] ==> Running command: /sbin/mkinitcpio -k 2.6.32-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
    [2010-01-08 14:45] :: Begin build
    [2010-01-08 14:45] :: Parsing hook [base]
    [2010-01-08 14:45] :: Parsing hook [udev]
    [2010-01-08 14:45] :: Parsing hook [pata]
    [2010-01-08 14:46] :: Parsing hook [scsi]
    [2010-01-08 14:46] :: Parsing hook [sata]
    [2010-01-08 14:46] :: Parsing hook [lvm2]
    [2010-01-08 14:46] :: Parsing hook [filesystems]
    [2010-01-08 14:46] :: Generating module dependencies
    [2010-01-08 14:46] :: Generating image '/boot/kernel26-fallback.img'...SUCCESS
    [2010-01-08 14:46] ==> SUCCESS
    [2010-01-08 14:46] upgraded kernel26 (2.6.32.2-2 -> 2.6.32.3-1)
    [2010-01-08 14:46] upgraded zlib (1.2.3.3-3 -> 1.2.3.4-3)
    [2010-01-09 03:18] synchronizing package lists
    [2010-01-09 03:19] starting full system upgrade
    [2010-01-09 03:44] warning: /etc/arno-iptables-firewall/firewall.conf installed as /etc/arno-iptables-firewall/firewall.conf.pacnew
    [2010-01-09 03:44] upgraded arno-iptables-firewall (1.9.2g-1 -> 1.9.2h-1)
    [2010-01-09 20:46] synchronizing package lists
    [2010-01-09 20:47] starting full system upgrade
    [2010-01-09 20:47] starting full system upgrade
    [2010-01-10 03:06] synchronizing package lists
    [2010-01-10 03:06] starting full system upgrade
    [2010-01-10 03:08] In order to use the new nvidia module, exit Xserver and unload it manually.
    [2010-01-10 03:08] upgraded nvidia (190.53-1 -> 190.53-3)
    [2010-01-10 03:32] synchronizing package lists
    [2010-01-10 03:32] starting full system upgrade
    [2010-01-10 03:32] upgraded nvidia (190.53-3 -> 190.53-3)
    [2010-01-10 16:05] synchronizing package lists
    [2010-01-10 16:06] starting full system upgrade
    [2010-01-10 22:50] synchronizing package lists
    [2010-01-10 22:50] starting full system upgrade
    [2010-01-10 22:50] starting full system upgrade
    [2010-01-10 22:50] upgraded freeglut (2.4.0-4 -> 2.6.0-1)
    [2010-01-10 22:51] upgraded kid3 (1.2-1 -> 1.3-1)
    [2010-01-10 23:16] upgraded x264-git (20100107-1 -> 20100110-1)
    [2010-01-10 23:20] upgraded ffmpeg-svn (21082-1 -> 21132-1)
    [2010-01-10 23:27] upgraded mplayer-mt-git (20100107-1 -> 20100110-1)
    [2010-01-10 23:39] upgraded amarok-git (20100107-1 -> 20100110-1)
    [2010-01-10 23:39] upgraded depot_tools-svn (35767-1 -> 35900-1)
    [2010-01-11 00:25] upgraded chromium-svn (35770-1 -> 35902-1)
    [2010-01-11 02:19] installed speedcrunch (0.10.1-1)
    [2010-01-11 06:01] synchronizing package lists
    [2010-01-11 06:01] starting full system upgrade
    [2010-01-11 15:12] synchronizing package lists
    [2010-01-11 15:13] starting full system upgrade
    [2010-01-11 15:14] upgraded x264-git (20100110-1 -> 20100111-1)
    [2010-01-11 15:16] upgraded ffmpeg-svn (21132-1 -> 21152-1)
    [2010-01-11 15:19] upgraded mplayer-mt-git (20100110-1 -> 20100111-1)
    [2010-01-11 17:04] synchronizing package lists
    [2010-01-11 17:04] starting full system upgrade
    [2010-01-11 17:04] starting full system upgrade
    [2010-01-11 17:04] upgraded qtcurve-gtk2 (1.0.0-1 -> 1.0.1-1)
    [2010-01-12 15:32] synchronizing package lists
    [2010-01-12 15:33] starting full system upgrade
    [2010-01-12 15:33] starting full system upgrade
    [2010-01-12 15:34] upgraded dhcpcd (5.1.3-1 -> 5.1.4-1)
    [2010-01-12 15:34] upgraded live-media (2009.09.28-2 -> 2010.01.11-1)
    [2010-01-12 15:34] upgraded strigi (0.7.0-1 -> 0.7.1-1)
    Any ideas?

    Well I still haven't been able to fix it, but here's what I've figured out:
    - Some of the buttons (for example brightness adjust and turn screen off) do not have keycodes.  They seem to work directly through the bios, not through the operating system.  Other buttons (like volume control) do have keycodes, and do work through the OS.
    - If I unload the kernel module asus_laptop, the OS-dependent buttons stop working, but the others continue to work.
    - When I suspend and resume, all the buttons stop working.
    - Putting asus_laptop in SUSPEND_MODULES for pm-utils does not help.
    - Using s2ram from uswsusp does not help.
    - After a suspend and resume (so the buttons are all broken), when I press a button twice and start getting infinite presses of d, I get the following message in dmesg:
    Jan 17 10:45:53 firefly kernel: atkbd.c: Unknown key released (translated set 2, code 0xe1 on isa0060/serio0).
    Jan 17 10:45:53 firefly kernel: atkbd.c: Use 'setkeycodes e061 <keycode>' to make it known.
    I tried running the suggested command using a keycode for a volume button, but it didn't help.  It did stop this message from coming up in dmesg for that particular button, but the other behaviors were the same.
    I can't think of anything else to do to fix it.  Does this mean anything to anyone?

  • 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.

  • [SOLVED] Cannot resume from suspend but hibernate works fine

    Please help me figuring out what can be the issues..
    I cannot resume from suspend while "sudo pm-hibernate" works fine..
    When I use "sudo pm-suspend", the system (samsung N210 netbook) goes to sleep and I can see the power light blinking as expected. But, when I try to resume the system from suspend by pressing the power button, the screen remains black with no HDD activity. Only thing I can see is the power LED on.
    After I do "sudo pm-suspend" and try to resume from suspend but fails. So, I do a HARD reboot and then this is the content of  /var/log/pm-suspend.log
    Initial commandline parameters:
    Thu Dec 16 12:00:27 IST 2010: Running hooks for suspend.
    Running hook /usr/lib/pm-utils/sleep.d/00logging suspend suspend:
    Linux archlinux-N210 2.6.36-ARCH #1 SMP PREEMPT Fri Dec 10 20:32:37 CET 2010 x86_64 Intel(R) Atom(TM) CPU N450 @ 1.66GHz GenuineIntel GNU/Linux
    Module Size Used by
    dm_mod 66662 0
    rfcomm 34874 4
    sco 8828 2
    bnep 8726 2
    l2cap 42585 16 rfcomm,bnep
    ipv6 281833 24
    nls_utf8 1288 0
    cifs 242984 0
    fscache 39915 1 cifs
    fuse 64259 3
    arc4 1378 2
    snd_seq_dummy 1431 0
    snd_hda_codec_realtek 275887 1
    uvcvideo 61404 0
    videodev 64318 1 uvcvideo
    v4l1_compat 15578 2 uvcvideo,videodev
    ecb 2041 2
    snd_seq_oss 28760 0
    ath9k 80424 0
    joydev 10055 0
    btusb 11385 2
    v4l2_compat_ioctl32 10212 1 videodev
    bluetooth 52419 9 rfcomm,sco,bnep,l2cap,btusb
    snd_seq_midi_event 5436 1 snd_seq_oss
    mac80211 196159 1 ath9k
    ath9k_common 3624 1 ath9k
    ath9k_hw 290909 2 ath9k,ath9k_common
    snd_hda_intel 22285 1
    snd_hda_codec 79384 2 snd_hda_codec_realtek,snd_hda_intel
    ath 8822 2 ath9k,ath9k_hw
    snd_seq 50082 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
    snd_seq_device 5297 3 snd_seq_dummy,snd_seq_oss,snd_seq
    snd_pcm_oss 39221 0
    cfg80211 143110 3 ath9k,mac80211,ath
    snd_hwdep 6110 1 snd_hda_codec
    uhci_hcd 21926 0
    easy_slow_down_manager 3185 0
    snd_mixer_oss 17106 2 snd_pcm_oss
    snd_pcm 71921 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
    snd_timer 19265 2 snd_seq,snd_pcm
    cpufreq_powersave 958 0
    sky2 46293 0
    rfkill 15882 3 bluetooth,cfg80211
    led_class 2331 1 ath9k
    snd 57562 11 snd_hda_codec_realtek,snd_seq_oss,snd_hda_intel,snd_hda_codec,snd_seq,snd_seq_device,snd_pcm_oss,snd_hwdep,snd_mixer_oss,snd_pcm,snd_timer
    psmouse 52592 0
    cpufreq_ondemand 8215 2
    soundcore 5969 2 snd
    ehci_hcd 36988 0
    tpm_tis 7928 0
    shpchp 26453 0
    sg 25652 0
    phc_intel 9527 1
    battery 10231 0
    tpm 10957 1 tpm_tis
    samsung_backlight 2844 0
    serio_raw 4486 0
    snd_page_alloc 7249 2 snd_hda_intel,snd_pcm
    usbcore 137570 5 uvcvideo,btusb,uhci_hcd,ehci_hcd
    ac 3105 0
    pci_hotplug 24319 1 shpchp
    tpm_bios 5505 1 tpm
    i2c_i801 8550 0
    freq_table 2323 2 cpufreq_ondemand,phc_intel
    pcspkr 1819 0
    thermal 12242 0
    evdev 8519 14
    processor 25936 1 phc_intel
    mperf 1243 1 phc_intel
    ext4 313574 1
    mbcache 5722 1 ext4
    jbd2 69002 1 ext4
    crc16 1297 2 l2cap,ext4
    sd_mod 25856 4
    ahci 20353 3
    libahci 17982 1 ahci
    libata 156316 2 ahci,libahci
    scsi_mod 124891 3 sg,sd_mod,libata
    i915 321187 3
    drm_kms_helper 25963 1 i915
    drm 175314 3 i915,drm_kms_helper
    i2c_algo_bit 4911 1 i915
    button 4834 1 i915
    i2c_core 18726 6 videodev,i2c_i801,i915,drm_kms_helper,drm,i2c_algo_bit
    video 19305 1 i915
    output 1940 1 video
    intel_agp 29459 2 i915
    total used free shared buffers cached
    Mem: 2046212 603128 1443084 0 11400 258660
    -/+ buffers/cache: 333068 1713144
    Swap: 2250748 0 2250748
    /usr/lib/pm-utils/sleep.d/00logging suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/00powersave suspend suspend:
    /usr/lib/pm-utils/sleep.d/00powersave suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/01grub suspend suspend:
    /usr/lib/pm-utils/sleep.d/01grub suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/01laptop-mode suspend suspend:
    /usr/lib/pm-utils/sleep.d/01laptop-mode suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/11netcfg suspend suspend:
    /usr/lib/pm-utils/sleep.d/11netcfg suspend suspend: success.
    Running hook /etc/pm/sleep.d/20_samsung-tools suspend suspend:
    /etc/pm/sleep.d/20_samsung-tools suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend:
    /usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/75modules suspend suspend:
    /usr/lib/pm-utils/sleep.d/75modules suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/90clock suspend suspend:
    /usr/lib/pm-utils/sleep.d/90clock suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/91wicd suspend suspend:
    /usr/lib/pm-utils/sleep.d/91wicd suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend:
    /usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/95led suspend suspend:
    /usr/lib/pm-utils/sleep.d/95led suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend:
    Kernel modesetting video driver detected, not using quirks.
    /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/99video suspend suspend:
    /usr/lib/pm-utils/sleep.d/99video suspend suspend: success.
    Thu Dec 16 12:00:31 IST 2010: performing suspend
    Since, the last time I checked about suspend was 1.5 months back, I cant really make out as to what package caused the issue as I had a few upgrades since that time.
    I am no expert but it seems like it is the log of suspending the system, it seems like the system didnt even go to initial stage of resuming.
    Last edited by shadyabhi (2010-12-27 17:54:19)

    Well this is a long shot... But my laptop had some issues with suspending due to low-power governors preventing it from fully working at times.
    Because of that I manually suspend with the following script:
    #!/bin/bash
    clear
    cpufreq-set -g performance
    cpufreq-info
    echo "Continue? y/n? ";read bevestiging
    if [ $bevestiging = "y" ]
    then
    echo "System going down for suspension NOW!"
    pm-suspend
    else
    echo "Exiting..."
    exit 0
    fi
    exit 0
    All it really does in the end, is change the governer from which it's currently on to "performance", thus allowing maximum clock speed.
    I've also added in a little confirmation dialog to check whether it's properly switched.
    Of course, this will only work for you if you're also using laptop-mode and cpufrequtils.
    Edit: You need to run this script with sudo or as the root user.
    Last edited by Aeva (2010-12-16 14:16:32)

  • 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)

  • Resume from suspend/ibernation sometimes freeze

    When closing the lid of my laptop, my system is set to freeze.
    Sometimes when i open the lid i see the graphics turn on (on the login screen) BUT everything is frozen, even the keyboard. If i close and reopen the lid, it somehow turn back to normal.
    this message is in dmegs:
    ------------[ cut here ]------------
    [ 4366.308099] WARNING: CPU: 0 PID: 0 at drivers/gpu/drm/i915/intel_display.c:9713 intel_check_page_flip+0xda/0xf0 [i915]()
    [ 4366.308100] Kicking stuck page flip: queued at 261481, now 261490
    [ 4366.308101] Modules linked in: joydev mousedev ecb arc4 nls_iso8859_1 nls_cp437 vfat fat coretemp intel_rapl iosf_mbi x86_pkg_temp_thermal iwlmvm intel_powerclamp kvm_intel snd_hda_codec_hdmi kvm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core crct10dif_pclmul crc32_pclmul iTCO_wdt v4l2_common crc32c_intel btusb iTCO_vendor_support videodev amdkfd ghash_clmulni_intel mac80211 bluetooth amd_iommu_v2 media aesni_intel aes_x86_64 lrw gf128mul radeon glue_helper ablk_helper cryptd iwlwifi pcspkr evdev psmouse cfg80211 rtsx_pci_ms mac_hid r8169 sparse_keymap ttm serio_raw led_class snd_hda_codec_realtek i2c_i801 memstick ac toshiba_bluetooth thermal toshiba_haps i915 hwmon mii rfkill wmi battery snd_hda_codec_generic button video drm_kms_helper snd_hda_intel snd_hda_controller drm snd_hda_codec
    [ 4366.308125]  snd_hwdep intel_gtt snd_pcm i2c_algo_bit i2c_core snd_timer ie31200_edac snd mei_me edac_core mei lpc_ich shpchp soundcore processor sch_fq_codel nfs lockd grace sunrpc fscache ext4 crc16 mbcache jbd2 sd_mod rtsx_pci_sdmmc mmc_core atkbd libps2 ahci libahci xhci_pci ehci_pci libata xhci_hcd ehci_hcd usbcore scsi_mod rtsx_pci usb_common i8042 serio
    [ 4366.308143] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.19.3-3-ARCH #1
    [ 4366.308144] Hardware name: TOSHIBA SATELLITE P50-B-115/VG20SQ, BIOS 1.50 12/09/2014
    [ 4366.308145]  0000000000000000 886cbefc2155fb8d ffff88032fa03d18 ffffffff8155d19f
    [ 4366.308146]  0000000000000000 ffff88032fa03d70 ffff88032fa03d58 ffffffff81073a4a
    [ 4366.308147]  ffff88032fa03d58 ffff88032127c000 ffff88031f735000 ffff88031f7351a0
    [ 4366.308149] Call Trace:
    [ 4366.308150]  <IRQ>  [<ffffffff8155d19f>] dump_stack+0x4c/0x6e
    [ 4366.308159]  [<ffffffff81073a4a>] warn_slowpath_common+0x8a/0xc0
    [ 4366.308161]  [<ffffffff81073ad5>] warn_slowpath_fmt+0x55/0x70
    [ 4366.308168]  [<ffffffffa051258a>] intel_check_page_flip+0xda/0xf0 [i915]
    [ 4366.308175]  [<ffffffffa04df968>] ironlake_irq_handler+0x2e8/0xfe0 [i915]
    [ 4366.308178]  [<ffffffff812be8e0>] ? timerqueue_add+0x60/0xb0
    [ 4366.308181]  [<ffffffff810dcd69>] ? enqueue_hrtimer+0x29/0xa0
    [ 4366.308184]  [<ffffffff810cc01e>] handle_irq_event_percpu+0x3e/0x1f0
    [ 4366.308185]  [<ffffffff810cc211>] handle_irq_event+0x41/0x70
    [ 4366.308187]  [<ffffffff810cf30e>] handle_edge_irq+0x9e/0x110
    [ 4366.308191]  [<ffffffff81018242>] handle_irq+0x22/0x40
    [ 4366.308193]  [<ffffffff8156557f>] do_IRQ+0x4f/0xf0
    [ 4366.308195]  [<ffffffff8156352d>] common_interrupt+0x6d/0x6d
    [ 4366.308195]  <EOI>  [<ffffffff814215d5>] ? cpuidle_enter_state+0x65/0x190
    [ 4366.308198]  [<ffffffff814215c1>] ? cpuidle_enter_state+0x51/0x190
    [ 4366.308200]  [<ffffffff814217e7>] cpuidle_enter+0x17/0x20
    [ 4366.308201]  [<ffffffff810b4aa8>] cpu_startup_entry+0x388/0x410
    [ 4366.308203]  [<ffffffff815536b5>] rest_init+0x85/0x90
    [ 4366.308205]  [<ffffffff818fe020>] start_kernel+0x48e/0x4af
    [ 4366.308207]  [<ffffffff818fd120>] ? early_idt_handlers+0x120/0x120
    [ 4366.308208]  [<ffffffff818fd4d7>] x86_64_start_reservations+0x2a/0x2c
    [ 4366.308210]  [<ffffffff818fd62b>] x86_64_start_kernel+0x152/0x175
    [ 4366.308210] ---[ end trace e9f540c04cbb56d5 ]---

    This happens to me 100% of the time with 3.11.6 and 3.10.17, resuming from suspend results in naught but an underscore top left. VT switching appears to work temporarily, I was able to enter in my user name in the VT, but then everything hung on pressing enter. Not sure about earlier kernel versions because this is a fresh install on this hardware. Happens with and without X.
    Hibernate results in an underscore before the computer is able to shut down. I tried using pm_trace and dumping logs before/after as recommended around the internet, pm_trace didn't match any hashes & there are no logs after suspend that get written out as far as I can tell. The computer is also unresponsive to the network. I also tried using pm_debug but I wasn't really sure what I was doing, running the core test I thought shouldn't cause the computer to actually suspend, but it did & there was my underscore again in all its glory.
    Wish I knew a way to get some more information..

Maybe you are looking for

  • HP Printer Driver not currently available from Software Update server

    I have an iMac (early 2009) and an HP OfficeJet 6100 Series printer.  I just upgraded my Apple Extreme Base Station and when I try to add the printer again thru the new Base Station the iMac says the software is available from the Apple Server but af

  • V600 Midlet Suite Missing Midlet and Icons

    I developed a Midlet suite application about 3 years ago and have not used it for at least 2 years. I just rebuilt the suite with Java Studio and it runs perfectly in the emulators. When I tried to download the suite via a WAP page using T-mobile on

  • Self adjusting levels

    I have a video that was, it looks like, recorded without lighting and with rapid cloud formation changes going on outside. The video varies from bright enough to too dark, with this going up and down many times in this ten minute clip. Is there a vid

  • Ipod Seems a Bit Slow (Laggy?)

    I have filled up my 60gb ipod a little over half of it with just music. It seems a bit slow now trying to explore through menus... is this normal? If not, how can I go about fixing or improving it? It's getting a bit tedious now because it's hard to

  • Cystal Report Formula

    In Crystal Report at footer there are two things VAT amount and CST amount. I want to do like in same place ther will be VAT / CST...if VAT amount is there it will show VAT 1500 if CST amount is there it will show CST 1600 How to do? in pld i think w