public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Resume from mem state == Reboot (Averatec)
Date: Mon, 14 Mar 2005 22:45:36 +0000	[thread overview]
Message-ID: <1110840337.8136.82.camel@tyrosine> (raw)
In-Reply-To: <87k6oaug4a.fsf-mMfbam+mt929kzlf/Hu3QdBPR1lH4CV8@public.gmane.org>

On Mon, 2005-03-14 at 12:28 -0800, Jason Dagit wrote:

> I would like to debug/fix this problem.  After a fair bit of googling
> it would appear than everyone with this model of laptop has the some
> problem.  I'm not very experienced with debugging the kernel, and I'm
> even less experienced with acpi.  What should I do to find out more
> about this?  Are there commands I can run and information to provide
> the list with to get to the next step in finding the problem?  If I
> include my dsdt or other information what is the best way to send that
> info to the list?  Should I use an email attachment?

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

-- 
Matthew Garrett | mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org



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

  parent reply	other threads:[~2005-03-14 22: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 [this message]
2005-03-21  6:45     ` Jason Dagit
     [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=1110840337.8136.82.camel@tyrosine \
    --to=mjg59-1xo5oi07kqx4cg9nei1l7q@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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