public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Dagit <dagit-LP0vGzdgvNwj5TC/SZClsA@public.gmane.org>
To: Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Resume from mem state == Reboot (Averatec)
Date: Sun, 20 Mar 2005 22:45:54 -0800	[thread overview]
Message-ID: <87eke94hul.fsf@www.codersbase.com> (raw)
In-Reply-To: <1110840337.8136.82.camel@tyrosine> (Matthew Garrett's message of "Mon, 14 Mar 2005 22:45:36 +0000")

Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org> writes:

> This is likely to be the same problem as
> http://bugzilla.kernel.org/show_bug.cgi?id=3691

Has anyone made progress on this bug?  I've been trying various things
on my system to get an understanding of the problem.  But I don't
really know what I'm doing and I could really use some guidance.

What sort of information would be useful in troubleshooting this?
I've attached all the diagnostic output I know how to generate to the
bug listed above, but there must be something else I can do or try.

Today when I was poking around I did discover in tbconvert.c inside
the function acpi_tb_build_common_facs that
acpi_gbl_common_fACS.firmware_waking_vector is 0x0de8000c.  But in
acpi_pm_prepare the function acpi_set_firmware_waking_vector is given
a physical address of 0x00001000, which comes from a virtual address
of 0xc0001000.  Is there something I can inspect or disassemble to
find out what the firmware_waking_vector should be?

Thanks,
Jason


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-03-21  6:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-14 20:28 Resume from mem state == Reboot (Averatec) Jason Dagit
     [not found] ` <87k6oaug4a.fsf-mMfbam+mt929kzlf/Hu3QdBPR1lH4CV8@public.gmane.org>
2005-03-14 22:45   ` Matthew Garrett
2005-03-21  6:45     ` Jason Dagit [this message]
     [not found]       ` <87eke94hul.fsf-mMfbam+mt929kzlf/Hu3QdBPR1lH4CV8@public.gmane.org>
2005-03-22  8:12         ` Jason Dagit

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=87eke94hul.fsf@www.codersbase.com \
    --to=dagit-lp0vgzdgvnwj5tc/szclsa@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=mjg59-1xO5oi07KQx4cg9Nei1l7Q@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