On 02/26/2007 11:40 AM somebody named Roger.Munoz wrote:

On 02/26/2007 09:22 AM somebody named Roger.Munoz wrote:

...

...

solving this one?

Roger I have almost the same problem on my Dell. When I switch from mains to battery, there's a CPU spike which lasts for several minutes. I believe it's due to hald, its being confused, perhaps in some loop which takes a lot of processing to resolve.

The video is "jerky" probably because it's not getting enough CPU. Try running "top" in a terminal before changing the power source and see what's running.

Ken

I've had a look at top and nothing jumps out to suggest anything is wrong. I think the problem lies with acpi because if I turn off acpi at boot, every thing is ok (apart from the fact the powersave functions are disabled).

Any more ideas?

So turning off acpi is good. I'd suggest turning it back on and shutting down powersaved just to see if you get the same results. If so, read "man powersave/d" and try performing some commands manually. Also have a look at /var/log/messages; you might find some error messages for powersaved there. For example, I occasionally get

WARNING in Function handleHWEventRequest; line 108: Could not read from hwEvent fd: 4, error: Connection reset by peer

What version of powersaved are you running?

Sorry about that but I don't send many an email to opensuse, in fact this is the first time in about 2 years!

I am running powersave-0.15.11-0.2

I've disabled powersave but I still encounter the same problem, so it seems acpi is definitely the culprit IMO.

Here is output from /var/log/acpid

Feb 26 16:18:53 wolverine [acpid]: received event "battery BAT0 00000080 00000001" Feb 26 16:18:53 wolverine [acpid]: notifying client 3278[101:102] Feb 26 16:18:53 wolverine [acpid]: notifying client 3638[0:0] Feb 26 16:18:53 wolverine [acpid]: completed event "battery BAT0 00000080 00000001" Feb 26 16:18:53 wolverine [acpid]: received event "processor CPU0 00000080 00000000" Feb 26 16:18:53 wolverine [acpid]: notifying client 3278[101:102] Feb 26 16:18:53 wolverine [acpid]: notifying client 3638[0:0] Feb 26 16:18:53 wolverine [acpid]: completed event "processor CPU0 00000080 00000000" Feb 26 16:18:53 wolverine [acpid]: received event "processor CPU0 00000081 00000000" Feb 26 16:18:53 wolverine [acpid]: notifying client 3278[101:102] Feb 26 16:18:53 wolverine [acpid]: notifying client 3638[0:0] Feb 26 16:18:53 wolverine [acpid]: completed event "processor CPU0 00000081 00000000" Feb 26 16:18:56 wolverine [acpid]: received event "battery BAT0 00000080 00000001" Feb 26 16:18:56 wolverine [acpid]: notifying client 3278[101:102] Feb 26 16:18:56 wolverine [acpid]: notifying client 3638[0:0] Feb 26 16:18:56 wolverine [acpid]: completed event "battery BAT0 00000080 00000001" Feb 26 16:18:56 wolverine [acpid]: received event "processor CPU0 00000080 00000000" Feb 26 16:18:56 wolverine [acpid]: notifying client 3278[101:102] Feb 26 16:18:56 wolverine [acpid]: notifying client 3638[0:0] Feb 26 16:18:56 wolverine [acpid]: completed event "processor CPU0 00000080 00000000" Feb 26 16:18:57 wolverine [acpid]: received event "processor CPU0 00000081 00000000" Feb 26 16:18:57 wolverine [acpid]: notifying client 3278[101:102] Feb 26 16:18:57 wolverine [acpid]: notifying client 3638[0:0] Feb 26 16:18:57 wolverine [acpid]: completed event "processor CPU0 00000081 00000000"

There are no errors in the messages file BTW.

It seems, then, that you and I are looking at different problems, so I guess we can't work on it together. As an afterthought, you might try disabling acpi's reporting on battery and other status reports (one at a time) to see if one of them is hanging your bootup. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org