public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael Frank" <mhf-jjFNsPSvq+iXDw4h08c5KA@public.gmane.org>
To: Michael Frank <mhf-jjFNsPSvq+iXDw4h08c5KA@public.gmane.org>,
	Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
Cc: Daniele Boffi <boffi-piYtxHxN1XRAly3Pu9w1wA@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	Software Suspend - Mailing Lists
	<swsusp-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Re: [Swsusp-devel] swsusp and ac status
Date: Mon, 28 Jun 2004 08:50:44 +0800	[thread overview]
Message-ID: <opr994muhg4evsfm@smtp.pacific.net.th> (raw)
In-Reply-To: <opr992vyyr4evsfm-TBR8pM7LtsqkE96DxU8f+dAkNl5+tjhE@public.gmane.org>

On Mon, 28 Jun 2004 08:13:00 +0800, Michael Frank <mhf-jjFNsPSvq+iXDw4h08c5KA@public.gmane.org> wrote:

> On Mon, 28 Jun 2004 00:28:42 +0200, Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org> wrote:
>
>> Thus wrote Michael Frank:
>>> Too bad, this implies that the AC module does not get reinitialized after
>>> resume and I suspect that acpi core is broken on 2.6 in this regard.
>>
>> As far as I know, there is no need to reinitialize the AC module, as it
>> does not cache the results -- upon read, it calls the appropriate _PSR
>> method which is supposed to return the correct AC adapter state, as simple
>> as it gets. This way, any problems would indicate a faulty BIOS.
>> Best regards,
>>
>
> Sorry, the BIOS does not know about suspend.
>
> Please consider It just booted cold and the resuming kernel
> without any ACPI modules won't have touched the AC method.
>
> ----> Thus the BIOS is now in a post boot state, like before
> 	vmlinux starts on boot!

To clarify

  ----> Thus the BIOS is now in a post boot state, like _after_
  	vmlinux started on boot! and BIOS AC adapter interface
	is unchanged from pre-boot.
>
> ----> The resumed kernel is in the state it was upon suspend.
>
> Therefor IMO cause is the kernel which was resumed and
> continues to talk to the BIOS which is in a state quite different
> than what it was pefore suspend...
>
> I concur that the BIOS in this case may break, but as it worked
> prior to suspend it cannot be blamed for not handling such abuse.
>
> A simple solution is for the resumed kernel to  start talking to
> BIOS as it would have on a normal boot, perhaps executing
> just a subset of the init code.
>
> If it also would disable all modules prior to suspend, it
> would likely fix all problems eliminating the reuqirement
> to unload ACPI modules....
>
> Best Regards
>
>
>
> -------------------------------------------------------
> 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
> _______________________________________________
> Acpi-devel mailing list
> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/acpi-devel
>
>




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

  parent reply	other threads:[~2004-06-28  0:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mhf@linuxmail.org>
     [not found] ` <mhf-jjFNsPSvq+iXDw4h08c5KA@public.gmane.org>
     [not found]   ` <opr93r8ap24evsfm-TBR8pM7LtsqkE96DxU8f+dAkNl5+tjhE@public.gmane.org>
2004-06-24 15:13     ` [Swsusp-devel] swsusp and ac status Daniele Boffi
     [not found]       ` <200406241513.i5OFDpKC003189-xzhXYMPkGmXoPXhRcRtihA@public.gmane.org>
2004-06-24 17:26         ` Michael Frank
2004-06-28 20:25         ` Pavel Machek
     [not found]           ` <200406301539.i5UFdUWt011300@fermat.unipv.it>
     [not found]             ` <200406301539.i5UFdUWt011300-xzhXYMPkGmXoPXhRcRtihA@public.gmane.org>
2004-06-30 19:40               ` Pavel Machek
     [not found] ` <opr93z2ex34evsfm-TBR8pM7LtsqkE96DxU8f+dAkNl5+tjhE@public.gmane.org>
2004-06-25  7:01   ` Daniele Boffi
     [not found]     ` <200406250701.i5P71GKC006204-xzhXYMPkGmXoPXhRcRtihA@public.gmane.org>
2004-06-25  9:21       ` Nigel Cunningham
2004-06-25 11:29       ` Michael Frank
2004-06-25 23:21   ` Micha Feigin
     [not found] ` <opr95d71ln4evsfm-TBR8pM7LtsqkE96DxU8f+dAkNl5+tjhE@public.gmane.org>
2004-06-25 12:09   ` Daniele Boffi
2004-06-25 15:14   ` Stefan Seyfried
     [not found]     ` <20040625151421.GA8852-l0tNAEGuAhhzZ8+rp42Dbp9+tswZ0GTaehPwdyo5hKaELgA04lAiVw@public.gmane.org>
2004-06-30  0:33       ` Micha Feigin
2004-06-27 22:28   ` Re: [Swsusp-devel] " Karol Kozimor
     [not found]     ` <20040627222842.GB1816-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2004-06-28  0:13       ` Michael Frank
     [not found]         ` <opr992vyyr4evsfm-TBR8pM7LtsqkE96DxU8f+dAkNl5+tjhE@public.gmane.org>
2004-06-28  0:50           ` Michael Frank [this message]
     [not found]             ` <opr994muhg4evsfm-TBR8pM7LtsqkE96DxU8f+dAkNl5+tjhE@public.gmane.org>
2004-06-28  5:27               ` Karol Kozimor
     [not found]                 ` <20040628052704.GA24842-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2004-06-28 10:03                   ` Michael Frank
2004-06-28 20:29         ` [ACPI] " Pavel Machek
     [not found] <200406241233.i5OCXiKC002386@fermat.unipv.it>
     [not found] ` <200406241233.i5OCXiKC002386-xzhXYMPkGmXoPXhRcRtihA@public.gmane.org>
2004-06-24 14:37   ` [Swsusp-devel] " Michael Frank

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=opr994muhg4evsfm@smtp.pacific.net.th \
    --to=mhf-jjfnspsvq+ixdw4h08c5ka@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=boffi-piYtxHxN1XRAly3Pu9w1wA@public.gmane.org \
    --cc=swsusp-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox