From: "Joachim Deguara" <joachim.deguara@amd.com>
To: "Michael Chan" <mchan@broadcom.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"lkml List" <linux-kernel@vger.kernel.org>,
"Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>,
"netdev" <netdev@vger.kernel.org>,
linux-acpi@vger.kernel.org
Subject: Re: [REGRESSION] tg3 dead after s2ram
Date: Thu, 2 Aug 2007 10:05:44 +0200 [thread overview]
Message-ID: <200708021005.45773.joachim.deguara@amd.com> (raw)
In-Reply-To: <1186002023.18322.7.camel@dell>
On Wednesday 01 August 2007 23:00:23 Michael Chan wrote:
> On Wed, 2007-08-01 at 10:47 -0700, Michael Chan wrote:
> > You have 2 Broadcom devices in your system. 07:00.0 is a wireless
> > device, I think. 8:4.0 is the tg3 device.
> >
> > It's clear that the tg3 device is still in D3 state after resume and
> > that explains why all register accesses fail. tg3_resume() should put
> > the device back in D0 state in a very straight forward way and I don't
> > see how that can fail. It worked for me when I tested it last night.
> > Can you add some printk() to tg3_resume() to see what's happening? Let
> > me know if you want me to send you some debug patches to do that.
>
> I misread the PCI registers below. The power state was ok.
>
> The problem is that memory enable and bus master were not set in PCI
> register 4 after resume. This also explains the register access
> failures.
>
> In tg3_resume(), we call pci_restore_state() which should re-enable
> those 2 bits in PCI register 4. Can you add some printk() to see why
> those bits are not restored after pci_restore_state()?
Reading pci_restore_state() it looks already instrumented. Sorry about the
wrong pci device, looking at my BCM5788 it is pci device 08:04.0 and looking
at the log from my first post there is nothing restored in the first 64
bytes! Otherwise it would have said "PM: Writing back..."
Is this what you are looking for or should I do other printk instrumentation?
-Joachim
next prev parent reply other threads:[~2007-08-02 8:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200707311128.32528.joachim.deguara@amd.com>
2007-08-01 0:45 ` [REGRESSION] tg3 dead after s2ram Andrew Morton
2007-08-01 7:53 ` Michael Chan
2007-08-01 8:01 ` Joachim Deguara
2007-08-01 17:47 ` Michael Chan
2007-08-01 21:00 ` Michael Chan
2007-08-02 8:05 ` Joachim Deguara [this message]
2007-08-02 9:15 ` Joachim Deguara
2007-08-02 9:23 ` David Miller
2007-08-02 19:10 ` Michael Chan
2007-08-02 22:06 ` David Miller
2007-08-02 23:38 ` Michael Chan
2007-08-03 9:47 ` Joachim Deguara
2007-08-04 3:57 ` David Miller
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=200708021005.45773.joachim.deguara@amd.com \
--to=joachim.deguara@amd.com \
--cc=akpm@linux-foundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchan@broadcom.com \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=netdev@vger.kernel.org \
/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).