linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Matthias Hentges <mailinglisten@hentges.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: pci-resume patch from 2.6.7-rc2 breakes S3 resume on some machines
Date: Fri, 19 Nov 2004 12:56:13 +0100	[thread overview]
Message-ID: <20041119115613.GC1030@elf.ucw.cz> (raw)
In-Reply-To: <1100811950.3470.23.camel@mhcln03>

Hi!

> I'm in the process of debugging S3 on my notebook and found out that I
> can resume from S3 with every kernel up to (and including) 2.6.7-rc1
> ( patch-2.6.6-bk8-bk9.bz2 ).
> 
> After 2.6.7-rc1, my notebook freezes upon a resume from S3. Tested with
> 2.6.7-rc2, -rc3, 2.6.8.1, 2.6.9 and some 2.6.10-rcX-bkX kernels.
> 
> Please note that these tests were run in single user mode with a
> barebone kernel
> .config (attached) just enough to boot (ie no modules, no usb etc)
> 
> I have found a hint on the web that the pci-resume code, which was
> included in 2.6.7-rc2, might cause this problem. I removed the call to
> pci_default_resume in drivers/pci/pci-driver.c and my laptop resumed
> into a working state again ( tested
> with 2.6.7 and 2.6.9 ).
> 
> I've written an email to Arjan van de Ven, the author of the resume
> patch and he suggested positing here, along with a full lspci output
> (attached)
> He thinks that some device is misbehaving and causing trouble if
> resumed.

Okay, patch is way too ugly. You probably should provide resume method
for your radeon that just does nothing. That should confirm your
theory, fix the crash, and you'll avoid touching common code with it.

								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!

      parent reply	other threads:[~2004-11-19 11:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-18 21:05 pci-resume patch from 2.6.7-rc2 breakes S3 resume on some machines Matthias Hentges
2004-11-19 11:55 ` Pavel Machek
2004-11-19 13:56   ` Matthias Hentges
2004-11-19 23:06     ` Benjamin Herrenschmidt
2004-11-20  2:43       ` Matthew Garrett
2004-11-20  3:36         ` Matthias Hentges
2004-11-20  7:34           ` Benjamin Herrenschmidt
2004-11-20  8:01             ` Matthias Hentges
2004-11-20 22:27               ` Benjamin Herrenschmidt
2004-11-21  8:50                 ` Matthias Hentges
2004-11-21 21:39                   ` Benjamin Herrenschmidt
2004-11-22  4:34                     ` Matthias Hentges
2004-11-22  4:52                       ` Benjamin Herrenschmidt
2004-11-20  7:33         ` Benjamin Herrenschmidt
2004-11-20 22:29         ` Pavel Machek
2004-11-19 11:56 ` Pavel Machek [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=20041119115613.GC1030@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mailinglisten@hentges.net \
    /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;
as well as URLs for NNTP newsgroup(s).