mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gaudenz Steinlin <gaudenz@soziologie.ch>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: commit "radeonfb: Fix resume from D3Cold on some platforms" breaks resume from RAM on PowerBook
Date: Fri, 6 Mar 2009 12:41:49 +0100	[thread overview]
Message-ID: <20090306114149.GA5371@soziologie.ch> (raw)
In-Reply-To: <1236333440.7260.136.camel@pasglop>

On Fri, Mar 06, 2009 at 08:57:20PM +1100, Benjamin Herrenschmidt wrote:
> 
> > So you are able to resume with my minimal config + CPU_FREQ? This would
> > be really strange if it is really the exact same model.
> 
> Yes, it appears to be :-)
> 
> > To verify if we really have the same model I included some data below. I
> > also included the gcc and binutils versions.
> > 
> > Please tell me if you have any further ideas on what to test.
> 
> In the commmit your revert, I added a function that "tests" if the chip
> appears to need to be POSTed: radeon_check_power_loss(). Try commenting
> out the content and make it always return 1.

This does not help.

> 
> Another thing you can try in radeonfb_pci_resume():
> 
>         if (pdev->dev.power.power_state.event == PM_EVENT_SUSPEND) {
> +		pci_restore_state(pdev);

Adding this fixes the bug. Apparently the PCI core does not fully
restore the state. Before your suggestions I also tried to find out
which part of your commit breaks resume and I found out that if I
reinsert the parts to save and restore the pci configuration the bug is
fixed. It seems that somehow the PCI coniguration is not fully restored [1].  

> +		pci_enable_device(pdev);

This does not help.

> +		pci_set_master(pdev);

This does not help.

Gaudenz

[1] These are just my wild guesses. I don't really understand much of
the code involved.

-- 
Ever tried. Ever failed. No matter.
Try again. Fail again. Fail better.
~ Samuel Beckett ~

  reply	other threads:[~2009-03-06 11:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-04  8:38 Gaudenz Steinlin
2009-03-04 23:22 ` Benjamin Herrenschmidt
2009-03-05 10:25   ` Gaudenz Steinlin
2009-03-05  2:25 ` Benjamin Herrenschmidt
2009-03-05 12:59   ` Gaudenz Steinlin
2009-03-06  5:50     ` Benjamin Herrenschmidt
2009-03-06  9:09       ` Gaudenz Steinlin
2009-03-06  9:57         ` Benjamin Herrenschmidt
2009-03-06 11:41           ` Gaudenz Steinlin [this message]
2009-03-06 21:26             ` Benjamin Herrenschmidt
2009-03-09 22:37             ` Benjamin Herrenschmidt
2009-03-10  9:32               ` Rafael J. Wysocki
2009-03-10 15:01                 ` Gaudenz Steinlin
2009-03-10 20:58                   ` Benjamin Herrenschmidt
2009-03-10 21:27                     ` Gaudenz Steinlin
2009-03-10 21:30               ` Gaudenz Steinlin
2009-03-10 22:07                 ` Benjamin Herrenschmidt
2009-03-10 23:04                   ` Rafael J. Wysocki
2009-03-11  0:34                     ` Benjamin Herrenschmidt
2009-03-09 22:49             ` Benjamin Herrenschmidt

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=20090306114149.GA5371@soziologie.ch \
    --to=gaudenz@soziologie.ch \
    --cc=akpm@linux-foundation.org \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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

all inboxes | Powered by JetHome®