Messages in this thread | | | Date | Tue, 19 Mar 2013 11:16:58 +0100 | From | Jiri Slaby <> | Subject | Re: e1000e + suspend, 3.9-rc2 |
| |
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
| |