public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Trull <linmodemstudent@gmail.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-acpi@vger.kernel.org
Subject: Re: no self-refresh during S3 - any debug hints?
Date: Sun, 27 Jul 2008 13:22:53 -0700	[thread overview]
Message-ID: <200807271322.53904.linmodemstudent@gmail.com> (raw)
In-Reply-To: <685450530806190940g7bd9edb9q3d98050755aee345@mail.gmail.com>

Hi Matthew,

Did this data provide any insights?

If it seems like a hopeless case that's all right, I guess - I've moved on to 
a laptop with fully-supported hardware (courtesy Zareason) but if there's any 
chance of finding root cause I'll keep the old one for testing potential 
patches, etc.

Thanks and Regards,
Jeff Trull

On Thursday 19 June 2008 09:40:30 Jeff Trull wrote:
> Delighted to!
>
> On Thu, Jun 19, 2008 at 8:09 AM, Matthew Garrett <mjg59@srcf.ucam.org> 
wrote:
> > On Sat, May 31, 2008 at 12:15:50PM -0700, Jeff Trull wrote:
> >> I'm running kernel 2.6.20 on a laptop with an ATI IGP 320M Northbridge
> >> and an Athlon XP.  DSDT has a _PTS but no _GTS.  I'm comfortable
> >> recompiling the kernel.  Any suggestions as to how to proceed,
> >> experiments to run, etc.?
> >
> > Hi Jeff,
> >
> > Could you attach the output of lspci -vxxx -s 0:0.0 ? Needs to be run as
> > root.
> >
> > --
> > Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2008-07-27 20:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-31 19:15 no self-refresh during S3 - any debug hints? Jeff Trull
2008-05-31 20:25 ` Matthew Garrett
2008-06-19 15:09 ` Matthew Garrett
2008-06-19 16:40   ` Jeff Trull
2008-07-27 20:22     ` Jeff Trull [this message]
2008-06-19 19:02 ` Len Brown
2008-06-19 19:26   ` Jeff Trull
2008-06-19 20:10   ` Pavel Machek
2008-06-21  6:13     ` Jeff Trull
2008-06-23 10:15       ` Pavel Machek

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=200807271322.53904.linmodemstudent@gmail.com \
    --to=linmodemstudent@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mjg59@srcf.ucam.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