[Solved] Kernel params for suspend - overheating(?)

I had long since given up on getting my Lenovo S10-3 to suspend - or should I say resume from suspend.
But with all the kernel updates I figured it might be time to give it another shot. The traditional methods had the traditional failings, but I found a new suggestion on the Lenovo S10 page of the arch wiki to add these three kernel parameters
hpet=disable highres=off nohz=off
I had tried the first previously, but not all three. I gave it a shot with all three and suspend and resume work perfectly.
I quickly noticed a disturbing side effect though. My netbook got notably hotter; I didn't take any sensor data, but I could feel how hot it was getting. The cpu fan remained on high continuously at idle, where without those three kernel parameters the fan almost never has to run.
I removed and replaced the parameters a few times to verify that this was the cause. Every time they were on the kernel line I had the fan/heat problems; everytime they weren't these problems didn't exist, but I couldn't resume from suspend.
Has anyone had similar issues or know of any way to get the suspend/resume benefit of these parameters without the (seemingly dangerous) side effect?
Google has not helped much on learning about these parameters. I found dozens of pages that limit their explanation to saying that "nohz=off" turns off nohz. Well thats f^%#ing helpful *sarcasm*.
Last edited by Trilby (2012-05-24 23:04:54)

Gusar wrote:They're on a wiki. Which everyone can edit. I'm sure this is not the only bad advice there.
Undoubtedly true. But I've seen them on many wiki's and forums for various distros. I have no delusion that it is good advice, but it is a technique that many are using. I'd be surprised if anyone used it if they got results like I did. Right from powering up I had a "WTF is wrong with my computer" reaction.
But that does answer my question. I'll still try the vanilla kernel tomorrow just in case, as I do still have it installed, but for now I'll put suspend back on the back-burner until I have time to look for better solutions. Working on a quick boot time has made suspending a low priority, but as it's the one thing on this machine that isn't working right I'm like a moth to a flame: "must fix irrelevant problem".
Thanks again for the insight.
UPDATE: Using the vanilla kernel makes no difference: the parameters needed for suspend cause a nasty side effect.
Last edited by Trilby (2012-05-25 15:44:42)

Similar Messages

[SOLVED] Kernel panic for an unknown reason

[Solved] Steps done to solve it:
0. Panic because I couldn't play starcraft2 (this step is sooo important! ;)
1. Updated my mirrorlist.
2. Forced a refresh on the package list from the new mirrorlist. "pacman -Syy"
3. Downgraded the kernel.
4. Deleted the latest kernel package from the pacman cache.
5. Updated the system. (pacman -Syu)
6. Thanked lilsirecho for helping out!
7. Profit
Hi all
I just did a "pacman -Syu" this afternoon and after that I'm getting kernel panics for unknown reasons.
edit: I had kernel 3.0.4 befure syu and I have kernel 3.0.7 now. I tried downgrading wine and the kernel with no success.
It first happened when I tried to run StarCraft2 with wine. I even created a post looking for help because of that.
Later on I tested another game, just in case, and it crashed too.
Looks like a wine problem, right? Or even a graphics driver problem.
That's what I thought too. But then I tried to update with "yaourt -Syu --aur" and in the first package compression it freezed once again. And it does fail everytime I try to update with yaourt during the compression phase.
What do this situations have in common?
My opinion is that they all require a lot of resources. StarCraft 2 puts my PC at 100% almost all the time. The other game is pretty old, but it freezed during an "environment loading" phase, right when the map was loading. The compression phase of yaourt also consumes a lot of resources.
This is my view of this problem, but I could be completely wrong.
What I need is help finding what is the real source of this kernel panics. I don't know where to look for the logs or the error reports when a kernel panic occurs.
I hope someone can help me trace the problem somehow. I think I'm lost
ty in advance.
cheers!
Last edited by fatum (2011-11-10 23:16:10)

lilsirecho wrote:
Possibly caused by a mirror download.
Perhaps you need to revert kernel and insure you have the latest mirrorlist and then syu again.
When I saw your response I thought: "Why should that be true? I downgraded the kernel with no success. Doesn't make much sense".
But then I did what you said:
Downgraded the kernel back to 3.0.4.
Moved the latest mirrorlist.pacnew I had to be the mirrorlist in use.
Then did a "pacman -Syyu".
And, miraculously, it works fine now.
How in the world did you know that could be the reason? It would have been the last possibility I would have thought about, no doubt about that
Thank you very much lilsirecho. Your post really helped me.
Not gonna mark this as SOLVED yet. Yesterday I marked my other thread as solved too soon and I regretted my decision.
I will leave a 1week time-frame to be 100% sure that it is fixed, just in case.

Kernel Params for Red Hat 6.0

I've been assigned to put oracle on a Dell installed RED Hat 6.0
box.
The Kernel Params are driving me nutty.
First of all, the docs are saying that SHMMAX needs to be
4294967295. I can't understand why Oracle can't just tell you
what to enter into the header straight and simple in HEX. My
hex calculator can't manipulate this magnitude. Is this
documentation even correct? It seems 2 digits too large from
everything else I'm looking at.
The rest of the kernel code is largley defined dynamically:
It looks like this.
Should I over ride all this?
#define SHMID_BITS 7
#define SHM_ID_MASK ((1<<_SHM_ID_BITS)-1)
#define SHM_IDX_SHIFT (_SHM_ID_BITS)
#define SHMIDX_BITS 15
#define SHM_IDX_MASK ((1<<_SHM_IDX_BITS)-1)
* SHMID_BITS + SHMIDX_BITS must be <= 24 on the i386 and
* SHMMAX <= (PAGE_SIZE << SHMIDX_BITS).
#define SHMMAX 0x2000000 /* max shared seg size
(bytes) */
/* Try not to change the default shipped SHMMAX - people rely on
it */
#define SHMMIN 1 /* really PAGE_SIZE */ /* min shared seg size
(bytes) */
#define SHMMNI (1<<_SHM_ID_BITS) /* max num of segs system
wide */
#define SHMALL /* max shm system wide
(pages) */ \
(1<<(_SHM_IDX_BITS+SHMID_BITS))
#define SHMLBA PAGE_SIZE /* attach addr a multiple
of this */
#define SHMSEG SHMMNI /* max shared segs per
process */
#endif /* ASMI386SHMPARAM_H */
null

If the system cats back -1 (or -273 etc) for inputs that big, I
don't how we are going to obtain a positive outcome.
The hex is not the point. The point is that 4 gig ints echoed
into the /proc directory return negitive integers.
Ruben
Mladen Gogala (guest) wrote:
: Hexcalculator is for wimps. The real programmers use bc,
: with scale, ibase and obase options. As bc is doing
: packed decimal arithmetics, it can do calculations with
: the numbers > 4GB. Increase SHMMAX to 0x4000000, relink
: the kernel (make bzImage), restart & enjoy.
: Ruben I Safir (guest) wrote:
: : Thanks Robson
: : That translates to -1 when you cat it back. That was the
same
: : thing the kde hexcalculator did. It seems that using that
many
: : bytes triggers a signed variable.
: : Ruben
: : Robson Miranda (guest) wrote:
: : : You only need to do
: : : echo 4294967295 > /proc/sys/kernel/shmmax (I think, I'm not
: on
: : : my Linux box, so can't check now).
: : : With kernel > 2.2.x, there's no need to recompile it to
: change
: : : the maximum amount of shared memory.
: : : Robson.
: : : Ruben I Safir (guest) wrote:
: : : : I've been assigned to put oracle on a Dell installed RED
: Hat
: : : 6.0
: : : : box.
: : : : The Kernel Params are driving me nutty.
: : : : First of all, the docs are saying that SHMMAX needs to be
: : : : 4294967295. I can't understand why Oracle can't just
tell
: : you
: : : : what to enter into the header straight and simple in
HEX.
: My
: : : : hex calculator can't manipulate this magnitude. Is this
: : : : documentation even correct? It seems 2 digits too large
: from
: : : : everything else I'm looking at.
: : : : The rest of the kernel code is largley defined
dynamically:
: : : : It looks like this.
: : : : Should I over ride all this?
: : : : #define SHMID_BITS 7
: : : : #define SHM_ID_MASK ((1<<_SHM_ID_BITS)-1)
: : : : #define SHM_IDX_SHIFT (_SHM_ID_BITS)
: : : : #define SHMIDX_BITS 15
: : : : #define SHM_IDX_MASK ((1<<_SHM_IDX_BITS)-1)
: : : : * SHMID_BITS + SHMIDX_BITS must be <= 24 on the i386
: and
: : : : * SHMMAX <= (PAGE_SIZE << SHMIDX_BITS).
: : : : #define SHMMAX 0x2000000 /* max shared seg
: : size
: : : : (bytes) */
: : : : /* Try not to change the default shipped SHMMAX - people
: rely
: : : on
: : : : it */
: : : : #define SHMMIN 1 /* really PAGE_SIZE */ /* min shared seg
: : size
: : : : (bytes) */
: : : : #define SHMMNI (1<<_SHM_ID_BITS) /* max num of
segs
: : : system
: : : : wide */
: : : : #define SHMALL /* max shm system
: : wide
: : : : (pages) */ \
: : : : (1<<(_SHM_IDX_BITS+SHMID_BITS))
: : : : #define SHMLBA PAGE_SIZE /* attach addr a
: : : multiple
: : : : of this */
: : : : #define SHMSEG SHMMNI /* max shared
segs
: : per
: : : : process */
: : : : #endif /* ASMI386SHMPARAM_H */
null

HP-UX Kernel Params for WLS 6.0SP2 Cluster to Avoid java.lang.outofmemory and/or thread death

          I'm running a WLS 6.0 SP2 clustered application on HP-UX 11i. I'm seeing heap and
          thread issues on start-up or invocation of my application as I deploy EJB's and create
          DB connection pools. These are fairly trivial tasks that don't give me any issues
          when starting the first node. It's only when I invoke the second node.
          I'm pretty sure that my issue is tied to the following kernel areas:
          1. Thread allocation
          2. Heap allocation
          3. Max Processes per user
          Can anyone make some kernel recommendations that might be beneficial to my deployment?
          My app runs on NT/2000 and Sun as well, and I haven't seen these issues. I typically
          allocate 50 to 100 threads per node (3 nodes on a 4 CPU machine) and allocate about
          1GB of RAM per node on a 4GB machine...
          Regards,
          Steve


I'm running a WLS 6.0 SP2 clustered application on HP-UX 11i. I'm seeing          heap and
          > thread issues on start-up or invocation of my application as I deploy
          EJB's and create
          > DB connection pools. These are fairly trivial tasks that don't give me any
          issues
          > when starting the first node. It's only when I invoke the second node.
          >
          > I'm pretty sure that my issue is tied to the following kernel areas:
          >
          > 1. Thread allocation
          > 2. Heap allocation
          > 3. Max Processes per user
          >
          > Can anyone make some kernel recommendations that might be beneficial to my
          deployment?
          > My app runs on NT/2000 and Sun as well, and I haven't seen these issues. I
          typically
          > allocate 50 to 100 threads per node (3 nodes on a 4 CPU machine) and
          allocate about
          > 1GB of RAM per node on a 4GB machine...
          HP has some kernel tuning guidelines for Java server apps on their web site,
          and BEA has some notes as well in their platform support page.
          What issues specifically are you seeing?
          Peace,
          Cameron Purdy
          Tangosol, Inc.
          Clustering Weblogic? You're either using Coherence, or you should be!
          Download a Tangosol Coherence eval today at http://www.tangosol.com/
          "Steve Feldman" <[email protected]> wrote in message
          news:3cdc046e$[email protected]..
          >

[solved] kernel configuration for clarkdale server

Update: I guess since the arch kernel config works there's really nothing to improve.
Hey everyone,
i'm about to compile a kernel for a server with intel clarkdale hardware, intel i3-530.
Up to now i only compiled kernels for my consumer laptop.
1) Is there any option in particular i should pay attention to when compiling a kernel for a server system?
And regarding the i3-530:
2) Should i just pick x86 generic cpu support or something else?
3) Are there any patches right now to improve support for clarkdale?
Thanks,
demian
P.S.: I guess i should choose 2.6.33-rc7 since real clarkdale support is supposed to come with 2.6.33? Usually i just pick the latest stable version.
Last edited by demian (2010-02-12 11:39:48)

graysky wrote:Your xfers are via scp... are the files large or numerous small files? Have you the ability to use jumbo frames on your network if the network is a GigLAN backbone? If so, you'll have to test to see if a non-standard 4000 or 9000 mtu size improves xfers.
thanks for your rapid response and i googled about it, but unfortunatelly i dont have a gigLan in the lab but usually all file transfered exceed 5GB of size.
Would the scheduler have a significant impact on performance? The servers are used individually (not sharing load like in a bewoulf cluster)
The disk I/O operations are mostly about writes into the output files (a few number of bytes per write), would reiserfs be superior to ext3 ?
PS.: i'm feeling really stupid for not reading more about the kernel26-lts for it has all the major options i was thinking about.
Last edited by Duca (2009-09-27 18:26:34)

[solved] Kernel configuration for Heavy Calculations Servers

Hello all,
I've been using Arch on half of the dual xeon workstations of the research lab i work to (these are the only ones under my supervision) and so far they have been continuously hailed for their greater performance compared to the other machines (same configuration) running fedora.
I did some minor tweaks on makepkg.conf (and using sugested compilation flags of the software i use) and on the bios to improve memory latency but i suppose i could squeeze even more juice from those boxes if i choose the right kernel options.
Finally my questions are:
- regarding the kernel, what options could i use to improve performance (i suppose using a home-pc kernel configuration is not the best option)?
- regarding the arch linux, what else can i do?
Usage:
- only to perform molecular modeling calculations (both molecular dynamics and quantum dynamics )
- data transfer using "scp"
Below are some important info about the hardware and config files:
-lspci
00:00.0 Host bridge: Intel Corporation 5000V Chipset Memory Controller Hub (rev b1)
00:02.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 2-3 (rev b1)
00:03.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 3 (rev b1)
00:08.0 System peripheral: Intel Corporation 5000 Series Chipset DMA Engine (rev b1)
00:10.0 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev b1)
00:10.1 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev b1)
00:10.2 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev b1)
00:11.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev b1)
00:13.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev b1)
00:15.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev b1)
00:16.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev b1)
00:1c.0 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 1 (rev 09)
00:1d.0 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1 (rev 09)
00:1d.1 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2 (rev 09)
00:1d.2 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3 (rev 09)
00:1d.3 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #4 (rev 09)
00:1d.7 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller (rev 09)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d9)
00:1f.0 ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller (rev 09)
00:1f.1 IDE interface: Intel Corporation 631xESB/632xESB IDE Controller (rev 09)
00:1f.2 IDE interface: Intel Corporation 631xESB/632xESB/3100 Chipset SATA IDE Controller (rev 09)
00:1f.3 SMBus: Intel Corporation 631xESB/632xESB/3100 Chipset SMBus Controller (rev 09)
01:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Upstream Port (rev 01)
01:00.3 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X Bridge (rev 01)
02:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E1 (rev 01)
02:01.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E2 (rev 01)
02:02.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E3 (rev 01)
05:00.0 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper) (rev 01)
05:00.1 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper) (rev 01)
09:0c.0 VGA compatible controller: ATI Technologies Inc ES1000 (rev 02)
-cat /proc/cpuinfo - it's the same for the eight "processors"
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Xeon(R) CPU E5410 @ 2.33GHz
stepping : 6
cpu MHz : 2331.000
cache size : 6144 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 lahf_lm tpr_shadow vnmi flexpriority
bogomips : 4656.91
clflush size : 64
cache_alignment : 64
address sizes : 38 bits physical, 48 bits virtual
power management:
-/etc/rc.conf
MOD_AUTOLOAD="yes"
MODULES=(acpi-cpufreq )
USELVM="no"
DAEMONS=(syslog-ng hal sensorsd sshd network netfs crond)
-free -m
total used free shared buffers cached
Mem: 7968 3094 4874 0 75 2784
-/+ buffers/cache: 233 7734
Swap: 19077 0 19077
- modifications i made to the /etc/makepkg.conf
# ARCHITECTURE, COMPILE FLAGS
CARCH="x86_64"
CHOST="x86_64-unknown-linux-gnu"
#-- Exclusive: will only run on x86_64
# -march (or -mcpu) builds exclusively for an architecture
# -mtune optimizes for an architecture, but builds for whole processor family
CFLAGS="-march=native -mtune=native -03 -pipe"
CXXFLAGS="-march=native -mtune=native -03 -pipe"
#LDFLAGS=""
#-- Make Flags: change this for DistCC/SMP systems
MAKEFLAGS="-j9"
Thanks in advance
Last edited by Duca (2009-09-28 04:30:04)

graysky wrote:Your xfers are via scp... are the files large or numerous small files? Have you the ability to use jumbo frames on your network if the network is a GigLAN backbone? If so, you'll have to test to see if a non-standard 4000 or 9000 mtu size improves xfers.
thanks for your rapid response and i googled about it, but unfortunatelly i dont have a gigLan in the lab but usually all file transfered exceed 5GB of size.
Would the scheduler have a significant impact on performance? The servers are used individually (not sharing load like in a bewoulf cluster)
The disk I/O operations are mostly about writes into the output files (a few number of bytes per write), would reiserfs be superior to ext3 ?
PS.: i'm feeling really stupid for not reading more about the kernel26-lts for it has all the major options i was thinking about.
Last edited by Duca (2009-09-27 18:26:34)

[solved] Building a kernel meant for one computer on another computer?

Hi!
Is it possible to use my laptop to build a kernel meant for a much slower desktop computer?
They're both running up-to-date Arch i686.
Last edited by francisc1701 (2010-02-14 17:43:24)

Everything does after its answered. Please mark solved. And you're welcome

[SOLVED] Missing Kernel Headers for Catalyst

Hello Everyone,
I am a new Arch guy! I am from the ubuntu world. Love the new arch install, I have installed my own DE.
I use a Radeon HD 68xx so I need the catalyst drivers.
I have tried installing them via: sudo pacman -S catalyst-dkms catalyst-utils (per the wiki)
It gets to the end and gives me this message:
DKMS: add completed.
Error! echo
Your kernel headers for kernel 3.6.2-1-ARCH cannot be found at
/usr/lib/modules/3.6.2-1-ARCH/build or /usr/lib/modules/3.6.2-1-ARCH/source.
error: command failed to execute correctly
Can anybody assist on how I get the kernel headers? As far as I understood, they should be included in Arch.
Last edited by luis84 (2012-10-19 03:08:17)

drewofdoom wrote:
do this:
sudo pacman -Sy linux-headers
Don't use 'pacman -Sy foo' - it may lead to breakage https://bbs.archlinux.org/viewtopic.php?id=89328

[Solved] Basic research for arch beginner - kernel

Hello,
if i want to compile my own new kernel so i create a directory to
"/usr/src/" like "linux-2.6.17.7". So i have in some cases more like one kernel directory.
Other distributions set a symlink to the actual kernel directory with
the name "linux", because in the system is "linux" the reference.
So it easy to change the link to the actualy kernel-directory.
I have seen, that Archlinux don't use a symlink to the kernel-directory.
How can i change the reference in the system for a new kernel-directory,
because i think if i compile some modules, the system will got every time
the "old" modules directory and not the new one ?
Thank you and
best regards
bademeister

brain0 wrote:
What does "the actual kernel-directory" mean? There is absolutely no part of the system that looks for /usr/src/linux.
You only need the source (or at least part of it) to compile external modules. The necessary headers are located via the /lib/modules/$(uname -r)/build/ directory.
As said above, you should use abs for kernel compilation so that pacman can keep track of the files.
The best solution for 99% of the users is using the stock kernel anyway, as it is slim and modular, supports all you need and there are tons of precompiled kernel modules for it in the repos.
Hi brain0,
"the actual kernel-directory" means, which directory is now use by the system.
For example, if i download the kernel and place it to /usr/src/linux-2.6.17.7, so i have two directories. With the old kernel before (linux-2.6.17-ARCH) and my new one.
"uname -r" show me the reference directory, now with "2.6.17-ARCH", also
all modules will loaded from: /lib/modules/2.6.17-ARCH/.
Now i compile the new kernel (linux-2.6.17.7-NEW) and during the compilation, all modules will be copied to the new module directory:
/lib/modules/2.6.17-NEW/.
If i look to the reference directory with "uname -r", so i get
2.6.17-ARCH again. All kind of modules will be loaded from the old directory.
So i'm looking for a solution to switch the reference directory, that
all modules will be loaded from "/lib/modules/2.6.17-NEW/".
Regards
bademeister

[SOLVED] Wireless fails after suspending (Realtek 8192se)

This problem is already solved on the first post: I spent so long trying to solve it that I thought people should know the solution.
I have a Lenovo X100e with a Realtek 8192SE wireless card. I'm running kernel 3.0. The machine has, since upgrading to the 3.0 kernel had the annoying problem of failing wireless connections after suspending: I'll have a running wireless connection, then suspend the machine, and then wake the machine up and the machine cannot connect to any wireless network (perhaps the same one I was connected to before, in the same place).
Things that did not work:
Installing the Realtek drivers from their website
Downgrading the kernel from 3.1 to 3.0
Using wicd instead of networkmanager
Walking around
Other distributions
The solution was to put an entry in /etc/pm/config.d/config:
SUSPEND_MODULES="rtl8192se rtlwifi mac80211 cfg80211"
Now the machine reconnects with no problems.
This may be the solution to the other big problem I was having with the 3.1 kernel: I would suspend the machine by any means and the screen goes black and the machine becomes non-responsive without actually suspending. I may try upgrading to the 3.1 kernel and adding radeon to the SUSPEND_MODULES list above.

Found out more which might be significant for madwifi users:
According to the wiki I loaded the following modules in rc.conf: ath-hal, ath9k, wlan
Beside this one line in the modprobe.conf should be added: alias ath0 ath_pci. This way wicd as well as networkmanager used ath0 for connecting to wireless.
After the update I noticed that there is another wifi device in ifconfig listed: wlan0. So I suspected that 2 devices pointing at the same hardware may cause the instability, but de-activating one by ifconfig didn't help. Now I noticed by loading the modules one by one that the new ath9k is already defining wlan0 and the wireless starts working without loading the module wlan. It looks stable so far, but if I should be right I'm impossibly the only one having this trouble.
Confirmation would be nice, but I will mark this thread "solved" now.

[SOLVED] Can't get suspend to ram to work (pm-utils)

It suspends, but then when I wake up my desktop the display is black. I followed the wiki, did things like add the resume hook, remove the autodetect hook, pm-is-supported returns empty, and I can't see from the pm-suspend.log what the issue could be
Initial commandline parameters:
Fri Jun 15 12:19:28 EDT 2012: Running hooks for suspend.
Running hook /usr/lib/pm-utils/sleep.d/00logging suspend suspend:
Linux dump9 3.4.2-3-ck #1 SMP PREEMPT Tue Jun 12 23:20:36 EDT 2012 x86_64 GNU/Linux
Module Size Used by
fuse 68256 3
dm_mod 70374 5
it87 28605 0
hwmon_vid 3164 1 it87
btusb 11604 0
bluetooth 187319 2 btusb
rfkill 15508 1 bluetooth
joydev 9895 0
usbhid 36046 0
hid 84805 1 usbhid
cx18_alsa 6389 1
mxl5005s 35031 1
s5h1409 9894 1
tuner_simple 13257 1
tuner_types 11121 1 tuner_simple
cs5345 2939 1
tda9887 8613 1
tda8290 12426 0
snd_hda_codec_hdmi 23640 4
tuner 16616 2
nvidia 12291043 30
nfs 274536 1
nfs_acl 2327 1 nfs
cx18 113932 1 cx18_alsa
lockd 62244 1 nfs
snd_hda_codec_via 37603 1
tveeprom 13777 1 cx18
i2c_algo_bit 5359 1 cx18
auth_rpcgss 32135 1 nfs
videobuf_vmalloc 4319 1 cx18
sunrpc 182965 8 nfs,auth_rpcgss,lockd,nfs_acl
fscache 40835 1 nfs
microcode 12281 0
firewire_ohci 31197 0
edac_mce_amd 12373 0
firewire_core 51008 1 firewire_ohci
powernow_k8 13360 1
edac_core 36624 0
mperf 1235 1 powernow_k8
videobuf_core 16007 2 cx18,videobuf_vmalloc
cx2341x 16956 1 cx18
dvb_core 94139 1 cx18
v4l2_common 5338 4 cx18,cx2341x,tuner,cs5345
videodev 92446 5 cx18,cx2341x,tuner,cs5345,v4l2_common
media 10117 1 videodev
snd_hda_intel 23765 5
snd_hda_codec 93089 3 snd_hda_codec_hdmi,snd_hda_codec_via,snd_hda_intel
snd_hwdep 6204 1 snd_hda_codec
snd_pcm 74574 5 cx18_alsa,snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
snd_page_alloc 7249 2 snd_pcm,snd_hda_intel
snd_timer 18774 1 snd_pcm
snd 58325 19 cx18_alsa,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_via,snd_pcm,snd_hda_codec,snd_hda_intel
i2c_piix4 8224 0
soundcore 5378 1 snd
i2c_core 20241 14 cx18,tuner,i2c_piix4,tda8290,tda9887,i2c_algo_bit,cs5345,s5h1409,nvidia,v4l2_common,tveeprom,mxl5005s,tuner_simple,videodev
ohci_hcd 21400 0
ehci_hcd 40546 0
usbcore 146125 5 btusb,ohci_hcd,ehci_hcd,usbhid
usb_common 954 1 usbcore
k10temp 2915 0
r8169 48842 0
crc_itu_t 1363 1 firewire_core
mii 4059 1 r8169
ppdev 5806 0
parport_pc 30541 0
parport 31139 2 ppdev,parport_pc
processor 26567 1 powernow_k8
wmi 8411 0
sp5100_tco 4504 0
psmouse 70248 0
evdev 9722 26
serio_raw 4621 0
button 4502 0
hfsplus 78321 0
loop 18000 0
autofs4 23767 2
ext4 422063 4
jbd2 73535 1 ext4
mbcache 5977 1 ext4
crc16 1359 2 ext4,bluetooth
sr_mod 14663 0
sd_mod 29047 11
cdrom 35488 1 sr_mod
pata_acpi 3376 0
pata_atiixp 4000 5
ahci 20517 2
ata_generic 3295 0
libahci 19959 1 ahci
libata 165627 5 ahci,pata_acpi,libahci,ata_generic,pata_atiixp
scsi_mod 132142 3 libata,sd_mod,sr_mod
total used free shared buffers cached
Mem: 8182220 2086832 6095388 0 65592 1007076
-/+ buffers/cache: 1014164 7168056
Swap: 2104476 0 2104476
/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/49bluetooth suspend suspend:
/usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/75modules suspend suspend:
Unloading kernel module ehci_hcd...Done.
/usr/lib/pm-utils/sleep.d/75modules suspend suspend: success.
Running hook /etc/pm/sleep.d/90alsa suspend suspend:
/etc/pm/sleep.d/90alsa 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/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:
nVidia binary video drive 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:
kernel.acpi_video_flags = 0
/usr/lib/pm-utils/sleep.d/99video suspend suspend: success.
Fri Jun 15 12:19:29 EDT 2012: performing suspend
Last edited by boast (2012-06-16 21:21:45)

ewaller wrote:I have no experience with nVidia controllers; sorry. Does anyone know if it is normal to skip the quirks for that display?
Yes, that's normal and should work.
Looking at the module list maybe try stopping the video4linux before suspend.
To double check: boast, you rebuilt the kernel, yes?

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

[solved] Unloading modules before suspend to disk

Hi, I'm trying to get my Asus U36jc to suspend to disk and resume. Suspending seems to go fine, but after resuming I get an unresponsive notebook (no response on key presses or ping) showing a black screen. Then immediately the fan gets louder and the notebook gets warmer.
Just before the machine goes to sleep, I see this in my screen:
xhci_hcd 0000:04:00.0: PCI post-resume error -110!
xhci_hcd 0000:04:00.0: HC died; cleaning up
xhci_hcd 0000:04:00.0: HC died; cleaning up
dpm_run_callback(): pci_pm_resume+0x0/0xb0 returns -110
PM: Device 0000:04:00.0 failed to resume async: error -110
hda-codec: out of range cmd 0:20:400:fffff7ff
I found this guide (https://www.kernel.org/doc/Documentatio … ugging.txt) and using that I determined that when I first remove modules ehci_pci, ehci_hcd and xhci_hcd, suspend to disk and resume seem to work fine.
I found out here (https://wiki.archlinux.org/index.php/Pm … end_to_RAM) how to unload modules prior to suspending to RAM, but that doesn't seem to work for suspend to disk, and I can't find how to unload modules prior to that. Can someone tell me how to do that?
Thanks for any help!
Last edited by diederick76 (2013-09-25 20:27:36)

I'm not sure if pm-utils is deprecated, it doesn't say so here (https://wiki.archlinux.org/index.php/Pm-utils). In any case its a dependency of upower, which is a dependency of kdelibs, so as long as I want to use KDE my harddrive is stuck with it.
However, I decided to try your suggestion to use systemd:
# asus36JC.service
[Unit]
Description=Script upon suspend/resume
Before=sleep.target
StopWhenUnneeded=no
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/home/diederick/bin/no_modules
ExecStop=/home/diederick/bin/modules
[Install]
WantedBy=sleep.target
It seemed to work perfectly for a couple of times in a row (modules were there before and afterwards) until I restarted the notebook, when the problem was back. But then I remembered to enable the service and now it works. Thanks a lot!

[SOLVED] Laptop resumes from suspend while lid is still closed

Hi all,
I'm having some weird issue ever since I installed arch on my new laptop (Haswell).
When I put my computer to suspend by closing the lid, all goes well.
But the computer resumes by itself after a while. I have no idea why, WoL is disabled on both ethernet and wifi.
Can someone help figure out what is causing the computer to resume?
For example here is a magic wake up after 1 hour asleep.
Feb 15 00:37:15 jitte systemd[1]: Starting TLP suspend/resume...
Feb 15 00:37:15 jitte tlp[24682]: grep: /sys/devices/platform/dock.?/type: No such file or directory
Feb 15 00:37:15 jitte systemd[1]: Started TLP suspend/resume.
Feb 15 00:37:15 jitte systemd[1]: Starting Sleep.
Feb 15 00:37:15 jitte systemd[1]: Reached target Sleep.
Feb 15 00:37:15 jitte systemd[1]: Starting Suspend...
Feb 15 00:37:15 jitte systemd-sleep[24748]: Suspending system...
Feb 15 00:37:15 jitte kernel: PM: Syncing filesystems ... done.
Feb 15 00:37:15 jitte kernel: PM: Preparing system for mem sleep
Feb 15 00:37:15 jitte kernel: bbswitch: enabling discrete graphics
Feb 15 01:34:26 jitte kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Feb 15 01:34:26 jitte systemd[1]: Time has been changed
Feb 15 01:34:26 jitte kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Feb 15 01:34:26 jitte kernel: PM: Entering mem sleep
Feb 15 01:34:26 jitte kernel: Suspending console(s) (use no_console_suspend to debug)
Feb 15 01:34:26 jitte kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Feb 15 01:34:26 jitte kernel: sd 0:0:0:0: [sda] Stopping disk
Feb 15 01:34:26 jitte kernel: mei_me 0000:00:16.0: suspend
Feb 15 01:34:26 jitte kernel: PM: suspend of devices complete after 220.139 msecs
Feb 15 01:34:26 jitte systemd[607]: Time has been changed
Feb 15 01:34:26 jitte kernel: PM: late suspend of devices complete after 0.115 msecs
Feb 15 01:34:26 jitte kernel: ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
Feb 15 01:34:26 jitte kernel: PM: noirq suspend of devices complete after 66.764 msecs
Feb 15 01:34:26 jitte kernel: ACPI: Preparing to enter system sleep state S3
Feb 15 01:34:26 jitte kernel: PM: Saving platform NVS memory
Feb 15 01:34:26 jitte kernel: Disabling non-boot CPUs ...
Feb 15 01:34:26 jitte kernel: smpboot: CPU 1 is now offline
Feb 15 01:34:26 jitte kernel: smpboot: CPU 2 is now offline
Feb 15 01:34:26 jitte kernel: smpboot: CPU 3 is now offline
Feb 15 01:34:26 jitte kernel: ACPI: Low-level resume complete
Feb 15 01:34:26 jitte kernel: PM: Restoring platform NVS memory
Feb 15 01:34:26 jitte kernel: Enabling non-boot CPUs ...
Feb 15 01:34:26 jitte kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
Feb 15 01:34:26 jitte kernel: Intel pstate controlling: cpu 1
Feb 15 01:34:26 jitte kernel: CPU1 is up
Feb 15 01:34:26 jitte kernel: smpboot: Booting Node 0 Processor 2 APIC 0x2
Feb 15 01:34:26 jitte kernel: Intel pstate controlling: cpu 2
Feb 15 01:34:26 jitte kernel: CPU2 is up
Feb 15 01:34:26 jitte kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
Feb 15 01:34:26 jitte kernel: Intel pstate controlling: cpu 3
Feb 15 01:34:26 jitte kernel: CPU3 is up
Feb 15 01:34:26 jitte kernel: ACPI: Waking up from system sleep state S3
Feb 15 01:34:26 jitte kernel: ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI
Feb 15 01:34:26 jitte kernel: PM: noirq resume of devices complete after 130.807 msecs
Feb 15 01:34:26 jitte kernel: PM: early resume of devices complete after 0.108 msecs
Feb 15 01:34:26 jitte kernel: i915 0000:00:02.0: setting latency timer to 64
Feb 15 01:34:26 jitte kernel: mei_me 0000:00:16.0: irq 57 for MSI/MSI-X
Feb 15 01:34:26 jitte kernel: snd_hda_intel 0000:00:03.0: irq 61 for MSI/MSI-X
Feb 15 01:34:26 jitte kernel: ehci-pci 0000:00:1d.0: setting latency timer to 64
Feb 15 01:34:26 jitte kernel: ahci 0000:00:1f.2: setting latency timer to 64
Last edited by jtheoof (2014-03-16 19:15:02)

So here's the update for today: sudo journalctl -amb.
Feb 25 13:39:00 jitte kernel: ACPI: \_SB_.PCI0: ACPI_NOTIFY_BUS_CHECK event
Feb 25 13:39:00 jitte kernel: ACPI: \_SB_.PCI0: ACPI_NOTIFY_BUS_CHECK event
Feb 25 13:39:00 jitte systemd-logind[276]: Lid closed.
Feb 25 13:39:00 jitte systemd-logind[276]: Suspending...
Feb 25 13:39:00 jitte NetworkManager[273]: <info> sleep requested (sleeping: no enabled: yes)
Feb 25 13:39:00 jitte NetworkManager[273]: <info> sleeping or disabling...
Feb 25 13:39:00 jitte NetworkManager[273]: <info> (wlp2s0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37]
Feb 25 13:39:00 jitte NetworkManager[273]: <info> (wlp2s0): deactivating device (reason 'sleeping') [37]
Feb 25 13:39:00 jitte dhcpcd[22409]: received SIGTERM from PID 273, stopping
Feb 25 13:39:00 jitte dhcpcd[22409]: wlp2s0: removing interface
Feb 25 13:39:00 jitte dhcpcd[22409]: exited
Feb 25 13:39:00 jitte NetworkManager[273]: <info> (wlp2s0): canceled DHCP transaction, DHCP client pid 22409
Feb 25 13:39:00 jitte NetworkManager[273]: <info> Removing DNS information from /usr/bin/resolvconf
Feb 25 13:39:00 jitte kernel: wlp2s0: deauthenticating from 00:24:d4:5f:dc:d8 by local choice (reason=3)
Feb 25 13:39:00 jitte kernel: cfg80211: Calling CRDA to update world regulatory domain
Feb 25 13:39:00 jitte NetworkManager[273]: <info> (wlp2s0): cleaning up...
Feb 25 13:39:00 jitte NetworkManager[273]: <info> (wlp2s0): taking down device.
Feb 25 13:39:00 jitte NetworkManager[273]: <info> NetworkManager state is now ASLEEP
Feb 25 13:39:00 jitte NetworkManager[273]: <info> (enp3s0f1): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]
Feb 25 13:39:00 jitte NetworkManager[273]: <info> (enp3s0f1): cleaning up...
Feb 25 13:39:00 jitte NetworkManager[273]: <info> (enp3s0f1): taking down device.
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-north".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-east".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-south".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-west".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-cycle".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-north".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-east".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-south".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-west".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-cycle".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-north".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-east".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-south".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-west".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-cycle".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-north".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-east".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-south".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-west".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-cycle".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-north".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-east".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-south".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-west".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-cycle".
Feb 25 13:39:00 jitte dbus[278]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Feb 25 13:39:00 jitte systemd[1]: Starting Network Manager Script Dispatcher Service...
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-north".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-east".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-south".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-west".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-cycle".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-north".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-east".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-south".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-west".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-cycle".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-north".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-east".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-south".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-west".
Feb 25 13:39:00 jitte gnome-session[1672]: Window manager warning: Trying to remove non-existent keybinding "move-focus-cycle".
Feb 25 13:39:00 jitte dbus[278]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb 25 13:39:01 jitte systemd[1]: Started Network Manager Script Dispatcher Service.
Feb 25 13:39:01 jitte gnome-session[1672]: Window manager warning: Log level 16: gsignal.c:2593: instance '0x15b1e20' has no handler with id '468541'
Feb 25 13:39:05 jitte systemd-logind[276]: Delay lock is active but inhibitor timeout is reached.
Feb 25 13:39:05 jitte systemd[1]: Starting Sleep.
Feb 25 13:39:05 jitte systemd[1]: Reached target Sleep.
Feb 25 13:39:05 jitte systemd[1]: Starting Suspend...
Feb 25 13:39:05 jitte systemd-sleep[22893]: Suspending system...
Feb 25 13:39:05 jitte kernel: PM: Syncing filesystems ... done.
Feb 25 13:39:05 jitte kernel: PM: Preparing system for mem sleep
Feb 25 13:39:05 jitte kernel: bbswitch: enabling discrete graphics
Feb 25 17:22:59 jitte kernel: Freezing user space processes ... (elapsed 0.002 seconds) done.
Feb 25 17:22:59 jitte systemd[1]: Time has been changed
Feb 25 17:22:59 jitte systemd[1666]: Time has been changed
Feb 25 17:22:59 jitte kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Feb 25 17:22:59 jitte kernel: PM: Entering mem sleep
Feb 25 17:22:59 jitte kernel: Suspending console(s) (use no_console_suspend to debug)
Feb 25 17:22:59 jitte kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Feb 25 17:22:59 jitte kernel: sd 0:0:0:0: [sda] Stopping disk
Feb 25 17:22:59 jitte kernel: PM: suspend of devices complete after 1098.028 msecs
Feb 25 17:22:59 jitte kernel: PM: late suspend of devices complete after 0.504 msecs
Feb 25 17:22:59 jitte kernel: pcieport 0000:00:1c.3: System wakeup enabled by ACPI
Feb 25 17:22:59 jitte kernel: ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
Feb 25 17:22:59 jitte kernel: PM: noirq suspend of devices complete after 66.728 msecs
Feb 25 17:22:59 jitte kernel: ACPI: Preparing to enter system sleep state S3
Feb 25 17:22:59 jitte kernel: PM: Saving platform NVS memory
Feb 25 17:22:59 jitte kernel: Disabling non-boot CPUs ...
Feb 25 17:22:59 jitte kernel: kvm: disabling virtualization on CPU1
Feb 25 17:22:59 jitte kernel: smpboot: CPU 1 is now offline
Feb 25 17:22:59 jitte kernel: kvm: disabling virtualization on CPU2
Feb 25 17:22:59 jitte kernel: smpboot: CPU 2 is now offline
Feb 25 17:22:59 jitte kernel: kvm: disabling virtualization on CPU3
Feb 25 17:22:59 jitte kernel: smpboot: CPU 3 is now offline
Feb 25 17:22:59 jitte kernel: ACPI: Low-level resume complete
Feb 25 17:22:59 jitte kernel: PM: Restoring platform NVS memory
Feb 25 17:22:59 jitte kernel: Enabling non-boot CPUs ...
Feb 25 17:22:59 jitte kernel: x86: Booting SMP configuration:
Feb 25 17:22:59 jitte kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
Feb 25 17:22:59 jitte kernel: kvm: enabling virtualization on CPU1
Feb 25 17:22:59 jitte kernel: Intel pstate controlling: cpu 1
Feb 25 17:22:59 jitte kernel: CPU1 is up
Feb 25 17:22:59 jitte kernel: smpboot: Booting Node 0 Processor 2 APIC 0x2
Feb 25 17:22:59 jitte kernel: kvm: enabling virtualization on CPU2
Feb 25 17:22:59 jitte kernel: Intel pstate controlling: cpu 2
Feb 25 17:22:59 jitte kernel: CPU2 is up
Feb 25 17:22:59 jitte kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
Feb 25 17:22:59 jitte kernel: kvm: enabling virtualization on CPU3
Feb 25 17:22:59 jitte kernel: Intel pstate controlling: cpu 3
Feb 25 17:22:59 jitte kernel: CPU3 is up
Feb 25 17:22:59 jitte kernel: ACPI: Waking up from system sleep state S3
Feb 25 17:22:59 jitte kernel: ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI
Feb 25 17:22:59 jitte kernel: PM: noirq resume of devices complete after 132.766 msecs
Feb 25 17:22:59 jitte systemd[1666]: Service bluetooth.target is not needed anymore. Stopping.
Feb 25 17:22:59 jitte systemd[1]: Service bluetooth.target is not needed anymore. Stopping.
Feb 25 17:22:59 jitte systemd[1666]: Stopping Bluetooth.
Feb 25 17:22:59 jitte systemd[1666]: Stopped target Bluetooth.
Feb 25 17:22:59 jitte systemd[1]: Stopping Bluetooth.
Feb 25 17:22:59 jitte systemd[1]: Stopped target Bluetooth.
Feb 25 17:22:59 jitte systemd[1666]: Starting Bluetooth.
Feb 25 17:22:59 jitte systemd[1666]: Reached target Bluetooth.
Feb 25 17:22:59 jitte systemd[1]: Starting Bluetooth.
Feb 25 17:22:59 jitte systemd[1]: Reached target Bluetooth.
Feb 25 17:22:59 jitte kernel: PM: early resume of devices complete after 0.347 msecs
Feb 25 17:22:59 jitte kernel: hpet1: lost 2539 rtc interrupts
Feb 25 17:22:59 jitte kernel: mei_me 0000:00:16.0: irq 58 for MSI/MSI-X
Feb 25 17:22:59 jitte kernel: usb usb1: root hub lost power or was reset
Feb 25 17:22:59 jitte kernel: usb usb2: root hub lost power or was reset
Feb 25 17:22:59 jitte kernel: snd_hda_intel 0000:00:03.0: irq 61 for MSI/MSI-X
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: irq 62 for MSI/MSI-X
Feb 25 17:22:59 jitte kernel: snd_hda_intel 0000:00:1b.0: irq 63 for MSI/MSI-X
Feb 25 17:22:59 jitte kernel: pcieport 0000:00:1c.3: System wakeup disabled by ACPI
Feb 25 17:22:59 jitte kernel: dpm_run_callback(): pnp_bus_resume+0x0/0xa0 returns -19
Feb 25 17:22:59 jitte kernel: PM: Device 00:07 failed to resume: error -19
Feb 25 17:22:59 jitte kernel: usb 3-1: reset high-speed USB device number 2 using ehci-pci
Feb 25 17:22:59 jitte kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 25 17:22:59 jitte kernel: ata1.00: ACPI cmd ef/10:09:00:00:00:b0 (SET FEATURES) succeeded
Feb 25 17:22:59 jitte kernel: ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
Feb 25 17:22:59 jitte kernel: ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
Feb 25 17:22:59 jitte kernel: ata1.00: ACPI cmd ef/10:09:00:00:00:b0 (SET FEATURES) succeeded
Feb 25 17:22:59 jitte kernel: ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
Feb 25 17:22:59 jitte kernel: ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
Feb 25 17:22:59 jitte kernel: ata1.00: configured for UDMA/133
Feb 25 17:22:59 jitte kernel: sd 0:0:0:0: [sda] Starting disk
Feb 25 17:22:59 jitte kernel: usb 1-5: reset high-speed USB device number 2 using xhci_hcd
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800af174f00
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800af174f40
Feb 25 17:22:59 jitte kernel: usb 1-6: reset full-speed USB device number 3 using xhci_hcd
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800af143780
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800af1437c0
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800af143800
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802320b0900
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802320b0940
Feb 25 17:22:59 jitte kernel: usb 1-7: reset full-speed USB device number 5 using xhci_hcd
Feb 25 17:22:59 jitte kernel: [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88022dc25300
Feb 25 17:22:59 jitte kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88022dc25340
Feb 25 17:22:59 jitte kernel: usb 1-7: ep 0x2 - rounding interval to 64 microframes, ep desc says 80 microframes
Feb 25 17:22:59 jitte kernel: PM: resume of devices complete after 1355.352 msecs
Feb 25 17:22:59 jitte kernel: PM: Finishing wakeup.
Feb 25 17:22:59 jitte kernel: Restarting tasks ...
Feb 25 17:22:59 jitte kernel: iwlwifi 0000:02:00.0: no hotplug settings from platform
Feb 25 17:22:59 jitte kernel: rtsx_pci 0000:03:00.0: no hotplug settings from platform
Feb 25 17:22:59 jitte kernel: r8169 0000:03:00.1: no hotplug settings from platform
Feb 25 17:22:59 jitte kernel: pci 0000:04:00.0: no hotplug settings from platform
Feb 25 17:22:59 jitte kernel: done.
Feb 25 17:22:59 jitte kernel: video LNXVIDEO:00: Restoring backlight state
Feb 25 17:22:59 jitte kernel: video LNXVIDEO:01: Restoring backlight state
Feb 25 17:22:59 jitte kernel: bbswitch: disabling discrete graphics
Feb 25 17:22:59 jitte kernel: ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
Feb 25 17:22:59 jitte kernel: Bluetooth: hci0: read Intel version: 370710018002030d00
Feb 25 17:22:59 jitte kernel: Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
Feb 25 17:22:59 jitte kernel: Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
Feb 25 17:22:59 jitte bluetoothd[272]: Failed to set mode: Blocked through rfkill (0x12)
Feb 25 17:22:59 jitte systemd-sleep[22893]: System resumed.
Feb 25 17:22:59 jitte systemd[1]: Started Suspend.
Feb 25 17:22:59 jitte systemd[1]: Requested transaction contradicts existing jobs: File exists
Feb 25 17:22:59 jitte systemd[1]: Service sleep.target is not needed anymore. Stopping.
Feb 25 17:22:59 jitte systemd[1]: Stopping Sleep.
Feb 25 17:22:59 jitte systemd[1]: Stopped target Sleep.
Feb 25 17:22:59 jitte systemd[1]: Reached target Suspend.
Feb 25 17:22:59 jitte systemd-logind[276]: Operation finished.
Feb 25 17:22:59 jitte NetworkManager[273]: <info> wake requested (sleeping: yes enabled: yes)
Feb 25 17:22:59 jitte NetworkManager[273]: <info> waking up and re-enabling...
Feb 25 17:22:59 jitte NetworkManager[273]: <info> (wlp2s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Feb 25 17:22:59 jitte NetworkManager[273]: <info> (wlp2s0): bringing up device.
Feb 25 17:22:59 jitte kernel: iwlwifi 0000:02:00.0: L1 Enabled; Disabling L0S
Feb 25 17:22:59 jitte kernel: iwlwifi 0000:02:00.0: L1 Enabled; Disabling L0S
Feb 25 17:22:59 jitte kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Feb 25 17:22:59 jitte NetworkManager[273]: <info> (wlp2s0): preparing device.
Feb 25 17:22:59 jitte NetworkManager[273]: <info> (wlp2s0): deactivating device (reason 'managed') [2]
Feb 25 17:22:59 jitte NetworkManager[273]: <info> NetworkManager state is now DISCONNECTED
Feb 25 17:22:59 jitte NetworkManager[273]: <info> (enp3s0f1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Feb 25 17:22:59 jitte NetworkManager[273]: <info> (enp3s0f1): bringing up device.
Feb 25 17:22:59 jitte kernel: r8169 0000:03:00.1 enp3s0f1: link down
Feb 25 17:22:59 jitte kernel: IPv6: ADDRCONF(NETDEV_UP): enp3s0f1: link is not ready
Feb 25 17:22:59 jitte NetworkManager[273]: <info> (enp3s0f1): preparing device.
Feb 25 17:22:59 jitte NetworkManager[273]: <info> (enp3s0f1): deactivating device (reason 'managed') [2]
Feb 25 17:23:00 jitte NetworkManager[273]: <info> (wlp2s0) supports 5 scan SSIDs
Feb 25 17:23:00 jitte NetworkManager[273]: <info> (wlp2s0): supplicant interface state: starting -> ready
Feb 25 17:23:00 jitte NetworkManager[273]: <info> (wlp2s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Feb 25 17:23:00 jitte NetworkManager[273]: <warn> Trying to remove a non-existant call id.
Feb 25 17:23:00 jitte NetworkManager[273]: <info> (wlp2s0): supplicant interface state: ready -> disconnected
Feb 25 17:23:00 jitte NetworkManager[273]: <info> (wlp2s0) supports 5 scan SSIDs
Feb 25 17:23:02 jitte kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0).
Feb 25 17:23:02 jitte kernel: atkbd serio0: Use 'setkeycodes e00d <keycode>' to make it known.
What's really odd is that the laptop woke up at the exact same time as yesterday. What could be causing that?
I'm using gnome-shell v3.10.3-1, linux-mainline v3.14rc3-1.

Hi all, I upgraded my MBP to Lion , but on the screen where i need to type my password, click on my photo and it does not appear the place for me to type my password and it stay stuck there. Can anyone solve this problem for me?

Hi all, I upgraded my MBP to Lion , but on the screen where i need to type my password, click on my photo and it does not appear the place for me to type my password and it stay stuck there. Can anyone solve this problem for me?

Reboot the machine holding Command and r keys down, you'll boot into Lion Recovery Partition
In there will be Disk Utility, use that to select your Lion OS X Partition and Repair Permissions.
After that is done reboot the machine and see if you can log in.
If not repeat the above steps to get into Lion Recovery, get online and reinstall Lion again, it will overwrite the installed version and hopefully after that it wil work.
Reboot and try again.
If not follow my steps to create a Snow Leopard Data Recovery drive, then option boot from it and grab a copy of your files off the machine.
Then reinstall all your programs onto the external drive like setting up a new machine, then use Disk Utility to erase the entire internal boot drive (select the drive media on the far left, not the partiton slightly indented) format Option: GUID , 1 partition OS X Extended and then use Carbon Copy Cloner to clone the external to the newly formatted internal drive. Once that is finished reboot and disconnect the external drive.
Once you go that, boot into Snow Leopard and update to 10.6.8, use the AppStore and option click on Purchases and download Lion again and install.
Lots of work, but there is no Lion disks.
https://discussions.apple.com/message/16276201#16276201

[Solved] Kernel params for suspend - overheating(?)

Similar Messages

Maybe you are looking for