rpm_resume flags invasion in kernel log on slackware 13.1 using kernel 2.6.37
 

Using kernel 2.6.37 custom built on a slackware 13.1 (32bit) machine, I have discovered that the kernel log is literally invaded with strange messages. There must be 5000 lines like these...

Does it indicate hardware failure or kernel bug!?

Greetingz!

Check your kernel config (/proc/config.gz if you selected the option).
Do you have CONFIG_PM_VERBOSE set or CONFIG_PM_DEBUG unset?

Mmmm that did it! I reused an old config file from a machine I had activated the PM debug features and forgot to unset them...

Thanks for pointing this out to me!

SOLVED!

Just out of curiosity, I have the exact same problem on a similar machine... Do I absolutely need to recompile the kernel to disdable these functions?

I've looked and looked for a way to do this by echoing something to /sys, and I've had zero luck. So from what I can tell; Yes, you'll have to recompile the kernel.

OK sounds fair, but IMO the Linux kernel needs modernization... recompiling the whole thing just for a simple switch? No wonder linux is light years behind Mac & Windowz...

If a driver needs to be compiled with debugging options set, that makes sense to me. Just like how there's Windows Symbol Packages or a Microsoft Symbol Server needed in order to do in-depth debugging.

Now I was hoping there was a way to "deactivate" the debugging code in general, but that doesn't seem to be the case. However this could be a personal failing of mine. I'm by no means an authority on Linux Kernel internals, so feel free to dig around either google or the code itself.

Comments made in jest should have an emoticon next to them. A lesser geek might take offense at such a flippant comment, and fire back a "[citation needed]".

Yeah lets fire a few ;) to calm down people!

What I want to say is that I'm probably the only human that I personally know that is willing to play around that stuff... Everybody know linux is not for everyone.

Anyways, I'll recompile and see what happens!

OK Its been a very long time since I last posted here but I need to come back to this topic... Sadly, I implemented what was discussed here, that is, CONFIG_PM_VERBOSE & CONFIG_PM_DEBUG unset, and it fixed the problem (the invasion of rpm_resume.... messages) but I've lost the suspend to RAM function...

When I click on the icon in the shutdown window of XFCE, it does nothing. I looked at dmesg & kernel messages log and nothing.

I believe I might have deactivated too many functions in the kernel when I recompiled and accidentally removed support for Ssuspend to RAM.

Can anybody look at my .config file and tell me which flags needs to be changed? I'm pretty new to the options in the .config file and last thing I want to do is screw up more than it is...

http://pastebin.com/5HGtFLne

Thanks!

Also I just tried to shutdown and here's what happened:

The shutdown sequence went fine until I saw the last line saying "shutting down" and instead of really shutting down, I saw a line saying "system halted" and the system seems to freeze there .

This machine is an htpc that is always plugged in the outlet and requires only 2 shutdown modes: standard mode ( real shutdown) and suspend to ram ( for when it's not playing any media)

Which options in the kernel will allow me to do so? Nothing else , no power managers and nothing that will or could scale down hardware performance to save energy.

Thanks!

Greetingz!

Are you doing a "shutdown -h now" when you shutdown the box?

I solved it, but forgot to update this thread: somehow the core PM functions of the kernel got deactivated... I went through the options one by one, reconfigured and recompiled.

All is fine now!