Re: [Intel-wired-lan] [BUG] 4.11.0-rc1 panic on shutdown X61s

[Borislav Petkov]

(Readding Jeff Kirsher who got dropped from the CC-list at some point.)

On Tue, Mar 21, 2017 at 07:13:43PM -0700, lkml@xxxxxxxxxxx wrote:
> > This is still broken as of 4.11.0-rc3 FYI.
> > 
> > Upon resume:
> > [   45.828344] ------------[ cut here ]------------
> > [   45.828352] WARNING: CPU: 0 PID: 807 at drivers/pci/msi.c:1052 __pci_enable_msi_range+0x39c/0x3f0
> > [   45.828355] CPU: 0 PID: 807 Comm: kworker/u4:29 Not tainted 4.11.0-rc3 #52
> > [   45.828356] Hardware name: LENOVO 7668CTO/7668CTO, BIOS 7NETC2WW (2.22 ) 03/22/2011
> > [   45.828360] Workqueue: events_unbound async_run_entry_fn
> > [   45.828362] Call Trace:
> > [   45.828366]  dump_stack+0x4d/0x72
> > [   45.828369]  __warn+0xc7/0xf0
> > [   45.828371]  warn_slowpath_null+0x18/0x20
> > [   45.828372]  __pci_enable_msi_range+0x39c/0x3f0
> > [   45.828375]  ? e1000e_get_phy_info_igp+0x1c/0xf0
> > [   45.828377]  pci_enable_msi+0x15/0x30
> > [   45.828379]  e1000e_set_interrupt_capability+0xe0/0x130
> > [   45.828381]  e1000e_pm_thaw+0x1d/0x50
> > [   45.828383]  e1000e_pm_resume+0x20/0x30
> > [   45.828386]  pci_pm_resume+0x5f/0x90
> > [   45.828389]  dpm_run_callback+0x44/0x170
> > [   45.828391]  ? pci_pm_thaw+0x90/0x90
> > [   45.828393]  device_resume+0xce/0x1e0
> > [   45.828395]  async_resume+0x18/0x40
> > [   45.828396]  async_run_entry_fn+0x32/0xe0
> > [   45.828399]  process_one_work+0x13b/0x3e0
> > [   45.828400]  worker_thread+0x64/0x4a0
> > [   45.828402]  kthread+0x10f/0x150
> > [   45.828404]  ? process_one_work+0x3e0/0x3e0
> > [   45.828406]  ? __kthread_create_on_node+0x150/0x150
> > [   45.828409]  ret_from_fork+0x29/0x40
> > [   45.828411] ---[ end trace 56fad2d83af13529 ]---
> > [   45.828469] e1000e 0000:00:19.0 eth3: Failed to initialize MSI interrupts.  Falling back to legacy interrupts.
> > [   45.835944] PM: resume of devices complete after 364.406 msecs
> > [   45.836001] usb 2-1:1.0: rebind failed: -517
> > [   45.836316] PM: Finishing wakeup.
> > 
> 
> I never reported back on the results of reverting 7e54d9d063fa, it seems to fix
> the problem on my machine as well.

Right, so I think we should revert soonish. That is, if you guys don't
have a fix yet. You can always try again during the next merge window.
Right now, I'm not testing -rc kernels on this box because of this. I
can always blacklist the networking driver but what good is that box
then...

Thanks.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--