public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Gryniewicz <dang@fprintf.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: Shawn Starr <shawn.starr@rogers.com>,
	linux-kernel@vger.kernel.org, Len Brown <len.brown@intel.com>,
	acpi-devel@lists.sourceforge.net
Subject: Re: [ACPI] [ACPI][2.6.10-rc3][SUSPEND] S3 mode - Cannot resume from PCI devices
Date: Thu, 16 Dec 2004 13:15:24 -0500	[thread overview]
Message-ID: <1103220924.23829.8.camel@athena.fprintf.net> (raw)
In-Reply-To: <20041214181819.GB5267@openzaurus.ucw.cz>

On Tue, 2004-12-14 at 19:18 +0100, Pavel Machek wrote:
> Hi!
> 
> > > > This isn't a nice regression.
> > > 
> > > So what was the last kernel where it worked?
> > 
> > For me, 2.6.9-rc4.  I've tried every -rc and -mm since, and it cannot
> > resume.  (I get no video on resume, even with 2.6.9-rc4, until X
> 
> Okay, perhaps you are lucky, diff between 2.6.9-rc4 and 2.6.9
> should be fairly small. Could you find which changeset is responsible?
> bkcvs should be really usefull here.
> 
> 				Pavel

So, I started out by building 2.6.9 to test it failed.  It failed.
Then, I started binary searching between 2.6.9-rc4 and 2.6.9, and worked
my way all the way back up to 2.6.9 with it working.  I'm now running
the current CVS as of yesterday, with no problems, and with suspend and
resume working.  I have no idea what changed between the original build
of 2.6.9 that failed, and the final build that worked, but it would
appear to have been something that was my fault.

Now if I could only get 10-rc4-ck1 to not hang on boot...

Daniel

      reply	other threads:[~2004-12-16 18:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-10  8:15 [ACPI][2.6.10-rc3][SUSPEND] S3 mode - Cannot resume from PCI devices Shawn Starr
2004-12-10 14:20 ` Pavel Machek
2004-12-13 12:18 ` Matthew Garrett
2004-12-14 11:06 ` [ACPI] " Pavel Machek
2004-12-14 15:55   ` Daniel Gryniewicz
2004-12-14 18:18     ` Pavel Machek
2004-12-16 18:15       ` Daniel Gryniewicz [this message]

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=1103220924.23829.8.camel@athena.fprintf.net \
    --to=dang@fprintf.net \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=shawn.starr@rogers.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