Re: Re: [Swsusp-devel] swsusp and ac status

["Michael Frank" <mhf-jjFNsPSvq+iXDw4h08c5KA@public.gmane.org>]

On Thu, 24 Jun 2004 17:13:51 +0200, Daniele Boffi <boffi-piYtxHxN1XRAly3Pu9w1wA@public.gmane.org> wrote:

>
>> For now, in practice all ACPI modules should be unloaded prior to
>> suspend and loaded on resume.
>>
>> I use the AC module and kernel 2.4.24 with swsusp 2.0 and it works
>> fine as long as it is removed prior to suspend.
>
> Unloading acpi modules, suspending, resuming and loading modules
> again does not help for me (2.6.7 and swsusp 2.0.0.88).
> Even after resuming, if I
>
> rmmod ac
> insmod ac

It is too late, it is already broken ;)

Please try:
rmmod AC
suspend/resume
modprobe AC

It should be OK...

>
> then I don't see the new charging state. On the other hand if, after
> resuming, I change the charging state again, then ac detection works
> OK.
>
> I tried also with 2.4.25 and swsusp 2.0 ... then it is stranger:
>
> - suspend with ac plugged
> - unplug
> - resume
> - ac is correctly detected off-line
> - next changes in ac state are not detected

Please proceed as above

>
>
> morph-XAiDara3MvRg9hUCZPvPmw@public.gmane.org said:
>> Would you mind checking to see (with top or something) whether or
>> not keventd is using 100% CPU next time this happens.
>
> It is not. CPU is about 1% (mostly used by X)
>

...As It is purely module related

	Michael


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com