public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Matthias Hentges <mailinglisten@hentges.net>
Cc: Pavel Machek <pavel@ucw.cz>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: pci-resume patch from 2.6.7-rc2 breakes S3 resume on some machines
Date: Sat, 20 Nov 2004 10:06:03 +1100	[thread overview]
Message-ID: <1100905563.3812.59.camel@gaston> (raw)
In-Reply-To: <1100872578.3692.7.camel@mhcln03>


> Of course it is :) It's more a proof-óf-concept that pci-resume is
> indeed causing the problem. I have no idea how to debug this any
> further. In the meantime this patch works for me.
> 
> >  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.
> 
> Sorry, that's beyond my abilities. That's why I'm posting here. I'm not
> even sure that it's the radeon which is acting up here.

Have you tried with radeonfb in your kernel config ?

Ben.



  reply	other threads:[~2004-11-19 23:09 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 [this message]
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

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=1100905563.3812.59.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mailinglisten@hentges.net \
    --cc=pavel@ucw.cz \
    /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