From: Andrey Borzenkov <arvidjaar@mail.ru>
To: "Lebedev, Vladimir P" <vladimir.p.lebedev@intel.com>
Cc: linux-acpi@vger.kernel.org, linux-pm@lists.osdl.org,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.19: ACPI reports AC not present after resume from STD
Date: Sat, 24 Feb 2007 12:55:01 +0300 [thread overview]
Message-ID: <200702241255.02073.arvidjaar@mail.ru> (raw)
In-Reply-To: <200702132116.05404.arvidjaar@mail.ru>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Вторник 13 февраля 2007, Andrey Borzenkov wrote:
> On Четверг 07 декабря 2006, Lebedev, Vladimir P wrote:
> > Please register new bug, attach acpidump and dmesg.
>
> http://bugzilla.kernel.org/show_bug.cgi?id=7995
>
> regards
>
Well, this starts looking like ACPI is not at fault.
When reporting AC state ACPI just reads contents of system memory (I presume
it gets updated by BIOS/ACPI when AC state changes). It looks like this
memory area is restored during resume from STD. I updated mentioned bug
report with more detailed description. Now if someone could suggest a way to
catch if specific physical address gets saved/restored this would finally
explain it.
Gratefully waiting for patches to test :)
- -andrey
> > -----Original Message-----
> > From: Alexey Starikovskiy [mailto:alexey.y.starikovskiy@linux.intel.com]
> >
> > Sent: Thursday, December 07, 2006 10:49 PM
> > To: Rafael J. Wysocki
> > Cc: Karasyov, Konstantin A; Andrey Borzenkov;
> > linux-acpi@vger.kernel.org; Lebedev, Vladimir P
> > Subject: Re: 2.6.19: ACPI reports AC not present after resume from STD
> >
> > Rafael J. Wysocki wrote:
> > > Hi,
> > >
> > > On Thursday, 7 December 2006 19:57, Karasyov, Konstantin A wrote:
> > >> Hi,
> > >>
> > >> Unfortunately, I cannot reproduce this bug on my system, but the
> >
> > problem
> >
> > >> could be solved by adding a resume handler for AC adapter device.
> >
> > Could
> >
> > >> you try the attached patch to see if it helps.
> > >
> > > I can reproduce it and the patch doesn't help.
> > >
> > > Greetings,
> > > Rafael
> >
> > Any ACPI errors in dmesg?
> >
> > Regards,
> > Alex.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFF4At2R6LMutpd94wRAnZGAJ9bGd98+gzCDfhIaFctH2u99M2uqQCfUzNz
7RqieTu7v4Z83jjeY79vnMw=
=GQZ6
-----END PGP SIGNATURE-----
_______________________________________________
linux-pm mailing list
linux-pm@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/linux-pm
next parent reply other threads:[~2007-02-24 9:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8E389A5F2FEABA4CB1DEC35A25CB39CE82FE9F@mssmsx411>
[not found] ` <200702132116.05404.arvidjaar@mail.ru>
2007-02-24 9:55 ` Andrey Borzenkov [this message]
2007-02-24 19:46 ` 2.6.19: ACPI reports AC not present after resume from STD Rafael J. Wysocki
2007-02-24 23:26 ` Andrey Borzenkov
2007-02-25 10:17 ` Rafael J. Wysocki
2007-02-25 10:37 ` Andrey Borzenkov
2007-02-25 10:51 ` Rafael J. Wysocki
2007-02-25 17:14 ` Andrey Borzenkov
2007-02-25 18:58 ` Rafael J. Wysocki
2007-02-26 20:35 ` Andrey Borzenkov
2007-02-26 21:23 ` Rafael J. Wysocki
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=200702241255.02073.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=vladimir.p.lebedev@intel.com \
/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