From: Jiri Slaby <jslaby@suse.cz>
To: Borislav Petkov <bp@alien8.de>,
jeffrey.t.kirsher@intel.com, "Rafael J. Wysocki" <rjw@sisk.pl>,
Bjorn Helgaas <bhelgaas@google.com>,
Konstantin Khlebnikov <khlebnikov@openvz.org>,
x86@kernel.org, lkml <linux-kernel@vger.kernel.org>,
e1000-devel@lists.sourceforge.net,
Bruce Allan <bruce.w.allan@intel.com>
Subject: Re: e1000e + suspend, 3.9-rc2
Date: Tue, 19 Mar 2013 11:16:58 +0100 [thread overview]
Message-ID: <51483B1A.9090704@suse.cz> (raw)
In-Reply-To: <20130312171745.GE5370@pd.tnic>
On 03/12/2013 06:17 PM, Borislav Petkov wrote:
> On Mon, Mar 11, 2013 at 09:25:37PM +0100, Borislav Petkov wrote:
>> Yeah, it is already upstream. And yeah, it did trigger with it.
>>
>> $ git describe
>> v3.9-rc2-112-g7c6baa304b84
>>
>> But it somehow doesn't trigger with that same kernel anymore so I'll
>> consider it a glitch and watch it over the next days.
>
> Ok, I can still see the hardware error message when suspending:
And with 3.8 plus these:
PCI/PM: Clear state_saved during suspend
e1000e: fix pci-device enable-counter balance
e1000e: fix runtime power management transitions
e1000e: fix accessing to suspended device
I sometimes see this:
pci_pm_suspend(): e1000_suspend+0x0/0x10 [e1000e] returns -2
dpm_run_callback(): pci_pm_suspend+0x0/0x140 returns -2
PM: Device 0000:00:19.0 failed to suspend async: error -2
Any ideas? Am I missing some patch still?
thanks,
--
js
suse labs
next prev parent reply other threads:[~2013-03-19 10:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 19:19 e1000e + suspend, 3.9-rc2 Borislav Petkov
2013-03-11 19:49 ` Jeff Kirsher
2013-03-11 20:25 ` Borislav Petkov
2013-03-12 17:17 ` Borislav Petkov
2013-03-19 10:16 ` Jiri Slaby [this message]
2013-03-19 10:27 ` Konstantin Khlebnikov
2013-03-19 12:22 ` Jiri Slaby
2013-03-29 18:04 ` Allan, Bruce W
2013-04-15 15:29 ` Jiri Slaby
2013-06-12 19:14 ` Jiri Slaby
2013-06-12 21:29 ` Konstantin Khlebnikov
2013-06-18 11:07 ` Jiri Slaby
2013-07-05 20:24 ` Jiri Slaby
2013-07-15 8:25 ` Jiri Slaby
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=51483B1A.9090704@suse.cz \
--to=jslaby@suse.cz \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=bruce.w.allan@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=khlebnikov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=x86@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