From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>,
Zhenyu Wang <zhenyuw@linux.intel.com>
Cc: Greg KH <greg@kroah.com>, Alek Du <alek.du@intel.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Dave Airlie <airlied@redhat.com>,
Linux-pm mailing list <linux-pm@lists.linux-foundation.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: Suspend problems in 2.6.31-rc6
Date: Fri, 21 Aug 2009 19:01:06 +0200 [thread overview]
Message-ID: <200908211901.06616.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0908211022210.2912-100000@iolanthe.rowland.org>
On Friday 21 August 2009, Alan Stern wrote:
> On Fri, 21 Aug 2009, Zhenyu Wang wrote:
>
> > > I can't understand why Alex's patch could fix for you, or because you've
> > > seen 'state_saved' is false in your testing, and Alex's patch just workaround
> > > state restore for you? I don't understand why 'state_saved' is false in your
> > > case, as pci layer should do save state for us by default, no?
>
> The PCI layer _does_ save the state, in pci_legacy_suspend_late().
> And then in pci_pm_default_resume_noirq() it restores the state and
> sets state_saved to false. That's why state_saved is false when
> agp_intel_resume() runs.
>
> > > Could you try with this one? And what's your gfx chip?
>
> 00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 03)
>
>
> > oops, here's right one for testing...
> >
> > diff --git a/drivers/char/agp/intel-agp.c b/drivers/char/agp/intel-agp.c
> > index 8c9d50d..5ed62c1 100644
> > --- a/drivers/char/agp/intel-agp.c
> > +++ b/drivers/char/agp/intel-agp.c
> > @@ -2303,6 +2303,13 @@ static void __devexit agp_intel_remove(struct pci_dev *pdev)
> > }
> >
> > #ifdef CONFIG_PM
> > +static int agp_intel_suspend(struct pci_dev *pdev, pm_message_t state)
> > +{
> > + pci_save_state(pdev);
> > + pci_set_power_state(pdev, 3);
> > + return 0;
> > +}
>
> I don't think this will help. The state _is_ getting saved, so saving
> it again won't make any difference. The problem occurs because the
> state is restored at the wrong time.
Yes. Moreover, it doesn't need to be restored at that point, because it has
already been restored earlier by the PCI bus type code.
So, Zhenyu, it is completely unnecessary to call pci_restore_state() from
a driver's ->resume() routine, because the PCI bus type driver has
already called it in its ->resume_noirq(). And please note that
pci_pm_default_resume_noirq() clears state_saved, which is why the Alek's
patch helps.
Without the Alek's patch on the Alan's system the config registers of both
PCI devices are restored twice, first by the PCI bus type at the "noirq" stage
and next by the driver. The Alek's patch turns the second restorations into
NOPs, which is fine, because they are unnecessary in general and they break
things on the Alan's system.
Thanks,
Rafael
next prev parent reply other threads:[~2009-08-21 17:01 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 15:11 Suspend problems in 2.6.31-rc6 Alan Stern
2009-08-17 18:28 ` Rafael J. Wysocki
2009-08-17 20:53 ` Alan Stern
2009-08-17 21:14 ` Greg KH
2009-08-17 21:15 ` Greg KH
2009-08-17 21:31 ` Jiri Slaby
2009-08-17 21:33 ` Jiri Slaby
2009-08-17 21:21 ` Rafael J. Wysocki
2009-08-17 21:50 ` Alan Stern
2009-08-18 16:07 ` Alan Stern
2009-08-18 23:22 ` Rafael J. Wysocki
2009-08-19 2:01 ` Zhenyu Wang
2009-08-19 14:42 ` Alan Stern
2009-08-20 1:05 ` Zhenyu Wang
2009-08-20 14:03 ` Alan Stern
2009-08-21 1:17 ` Zhenyu Wang
2009-08-20 15:34 ` Rafael J. Wysocki
2009-08-19 14:26 ` Alan Stern
2009-08-19 21:22 ` Rafael J. Wysocki
2009-08-20 15:17 ` Alan Stern
2009-08-20 16:17 ` Rafael J. Wysocki
2009-08-21 1:21 ` Zhenyu Wang
2009-08-21 3:13 ` Zhenyu Wang
2009-08-21 14:32 ` Alan Stern
2009-08-21 17:01 ` Rafael J. Wysocki [this message]
2009-08-24 2:34 ` Zhenyu Wang
2009-08-24 18:55 ` Rafael J. Wysocki
2009-08-25 0:59 ` Alan Stern
2009-08-27 14:51 ` Alan Stern
2009-08-27 16:18 ` Jesse Barnes
2009-08-24 1:30 ` Zhenyu Wang
2009-08-20 15:41 ` Rafael J. Wysocki
2009-08-20 16:05 ` Jesse Barnes
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=200908211901.06616.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=airlied@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alek.du@intel.com \
--cc=greg@kroah.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=stern@rowland.harvard.edu \
--cc=zhenyuw@linux.intel.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