From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Simon Arlott <simon@fire.lp0.eu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
jgarzik@redhat.com, netdev@vger.kernel.org,
linux-pm@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, ranma+kernel@tdiedrich.de
Subject: Re: [linux-pm] forcedeth 10de:0373 doesn't work on resume
Date: Mon, 18 Aug 2008 23:39:39 +0200 [thread overview]
Message-ID: <200808182339.40403.rjw@sisk.pl> (raw)
In-Reply-To: <48A9E8B3.4040800@simon.arlott.org.uk>
On Monday, 18 of August 2008, Simon Arlott wrote:
> On 18/08/08 22:13, Rafael J. Wysocki wrote:
> > On Monday, 18 of August 2008, Andrew Morton wrote:
> >> On Tue, 05 Aug 2008 20:29:44 +0100
> >> Simon Arlott <simon@fire.lp0.eu> wrote:
> >> >
> >>
> >> [two weeks pass...]
> >
> > [Must have missed this message.]
> >
> > I have a box with forcedeth that evidently works after a resume from
> > hibernation. Unfortunately, so far I haven't been able to make the box
>
> With hibernation would it re-initialise the devices differently?
Yes. Usually the BIOS does something to devices in that case.
> > resume from suspend to RAM. I'll do my best to try again tomorrow, but there's
> > a little hope. :-(
>
> Mine doesn't either, try standby?
OK, I will.
> >> > My NIC stops working after resuming from standby, it's not receiving any interrupts:
> >> > Commit 25d90810ff49d2a63475776f24c74c6bb49b045f ([netdrvr] forcedeth: reorder suspend/resume code)
> >> > introduces pci_disable_device to nv_suspend, but there's no corresponding pci_enable_device in
> >> > nv_resume - so I added one (copied from e1000):
> >> >
> >> > diff --git a/drivers/net/forcedeth.c b/drivers/net/forcedeth.c
> >> > index 01b38b0..db4f875 100644
> >> > --- a/drivers/net/forcedeth.c
> >> > +++ b/drivers/net/forcedeth.c
> >> > @@ -5922,6 +5922,13 @@ static int nv_resume(struct pci_dev *pdev)
> >> >
> >> > pci_set_power_state(pdev, PCI_D0);
> >> > pci_restore_state(pdev);
> >> > + rc = pci_enable_device(pdev);
> >> > + if (rc) {
> >> > + printk(KERN_ERR "forcedeth: Cannot enable PCI device from suspend\n");
> >> > + return rc;
> >> > + }
> >> > + pci_set_master(pdev);
> >> > +
> >> > /* ack any pending wake events, disable PME */
> >> > pci_enable_wake(pdev, PCI_D0, 0);
> >> >
> >>
> >> That seems like a sensible change.
> >>
>
> With this applied, I can resume from standby *without MSI* and the
> NIC still works. I haven't tested it without MSI and without the
> patch... mostly because I got a BUG when I tried to recompile.
That's interesting. I'll try to reproduce it.
> >> > This results in interrupts being re-enabled after suspend:
> >> > However, the NIC still doesn't work after resume.
> >
> > Simon, I'd prefer the full dmesg to the grepped forcedeth messages.
> >
>
> Attached. (The previous email has all the standby/resume log output.)
>
> > I guess this was resume from suspend to RAM?
>
> Standby - resume from RAM is completely broken for my system.
>
> >> Is it still broken in current kernels?
> >
> > It probably is.
>
> If I have MSI enabled, it still doesn't work.
Hm. I wonder if that's specific to forcedeth or other drivers may be affected.
Thanks,
Rafael
next prev parent reply other threads:[~2008-08-18 21:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 19:29 forcedeth 10de:0373 doesn't work on resume Simon Arlott
2008-08-18 20:48 ` Andrew Morton
2008-08-18 21:13 ` Rafael J. Wysocki
2008-08-18 21:25 ` [linux-pm] " Simon Arlott
2008-08-18 21:34 ` Yinghai Lu
2008-08-18 21:42 ` Rafael J. Wysocki
2008-08-18 21:43 ` Simon Arlott
2008-08-18 21:48 ` Rafael J. Wysocki
2008-08-18 21:39 ` Rafael J. Wysocki [this message]
2008-08-21 12:34 ` Rafael J. Wysocki
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=200808182339.40403.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=jgarzik@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=netdev@vger.kernel.org \
--cc=ranma+kernel@tdiedrich.de \
--cc=simon@fire.lp0.eu \
/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).