[Bug 59321] [hsw] S4 broken with Haswell

[bugzilla-daemon at bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=59321

--- Comment #46 from Jens <jens-bugzilla.kernel.org at spamfreemail.de> ---
No crashes after 8 hibernate/resume cycles with this kernel tree. Great!

However, I got the below backtrace upon the second resume, and after that the
network was flaky (about each second resume I had not network access until I
hibernated again):


[  460.342312] r8169 0000:02:00.0 eth0: link down
[  460.342331] r8169 0000:02:00.0 eth0: link down
[  460.342369] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[  463.191127] r8169 0000:02:00.0 eth0: link up
[  463.191134] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[  559.157551] ------------[ cut here ]------------
[  559.157557] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:264
dev_watchdog+0x276/0x280()
[  559.157558] NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
[  559.157559] Modules linked in: bnep(E) rfcomm(E) bluetooth(E)
snd_hda_codec_realtek(E) snd_hda_codec_hdmi(E) snd_hda_codec_generic(E)
snd_hda_intel(E) snd_hda_controller(E) snd_hda_codec(E) snd_hwdep(E) snd_pcm(E)
snd_seq_midi(E) snd_seq_midi_event(E) snd_rawmidi(E) snd_seq(E)
snd_seq_device(E) snd_timer(E) intel_rapl(E) snd(E) soundcore(E)
x86_pkg_temp_thermal(E) intel_powerclamp(E) coretemp(E) lpc_ich(E) serio_raw(E)
kvm_intel(E) mei_me(E) mei(E) kvm(E) shpchp(E) tpm_infineon(E)
intel_smartconnect(E) mac_hid(E) parport_pc(E) ppdev(E) lp(E) parport(E)
dm_crypt(E) netconsole(E) configfs(E) crct10dif_pclmul(E) crc32_pclmul(E)
ghash_clmulni_intel(E) i915(E) mxm_wmi(E) r8169(E) i2c_algo_bit(E)
drm_kms_helper(E) hid_generic(E) aesni_intel(E) ahci(E) aes_x86_64(E) lrw(E)
gf128mul(E) glue_helper(E) libahci(E) mii(E) ablk_helper(E) usbhid(E) cryptd(E)
drm(E) hid(E) wmi(E) video(E)
[  559.157582] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G            E 
3.17.0-rc4+ #1
[  559.157583] Hardware name: MSI MS-7817/CSM-B85M-E45 (MS-7817), BIOS V10.5
05/30/2014
[  559.157584]  0000000000000009 ffff88021ea03d98 ffffffff8174630a
ffff88021ea03de0
[  559.157585]  ffff88021ea03dd0 ffffffff8106c8bd 0000000000000000
ffff88020fb4a000
[  559.157586]  ffff88020f812880 0000000000000001 0000000000000000
ffff88021ea03e30
[  559.157588] Call Trace:
[  559.157589]  <IRQ>  [<ffffffff8174630a>] dump_stack+0x45/0x56
[  559.157595]  [<ffffffff8106c8bd>] warn_slowpath_common+0x7d/0xa0
[  559.157596]  [<ffffffff8106c92c>] warn_slowpath_fmt+0x4c/0x50
[  559.157598]  [<ffffffff8166b8c6>] dev_watchdog+0x276/0x280
[  559.157600]  [<ffffffff8166b650>] ? dev_graft_qdisc+0x80/0x80
[  559.157602]  [<ffffffff810cefd6>] call_timer_fn+0x36/0x100
[  559.157603]  [<ffffffff8166b650>] ? dev_graft_qdisc+0x80/0x80
[  559.157605]  [<ffffffff810d076f>] run_timer_softirq+0x20f/0x310
[  559.157607]  [<ffffffff81070865>] __do_softirq+0xf5/0x2e0
[  559.157609]  [<ffffffff81070d25>] irq_exit+0x105/0x110
[  559.157611]  [<ffffffff81751855>] smp_apic_timer_interrupt+0x45/0x60
[  559.157612]  [<ffffffff8174f95d>] apic_timer_interrupt+0x6d/0x80
[  559.157613]  <EOI>  [<ffffffff815f4582>] ? poll_idle+0x42/0x90
[  559.157616]  [<ffffffff815f3fc5>] cpuidle_enter_state+0x55/0x170
[  559.157617]  [<ffffffff815f4197>] cpuidle_enter+0x17/0x20
[  559.157620]  [<ffffffff810aadfd>] cpu_startup_entry+0x31d/0x340
[  559.157623]  [<ffffffff81737747>] rest_init+0x77/0x80
[  559.157625]  [<ffffffff81d41084>] start_kernel+0x42f/0x43a
[  559.157626]  [<ffffffff81d40a4e>] ? set_init_arg+0x53/0x53
[  559.157628]  [<ffffffff81d40120>] ? early_idt_handlers+0x120/0x120
[  559.157629]  [<ffffffff81d405ee>] x86_64_start_reservations+0x2a/0x2c
[  559.157630]  [<ffffffff81d40733>] x86_64_start_kernel+0x143/0x152
[  559.157631] ---[ end trace 94d117e156a45de1 ]---
[  559.171533] r8169 0000:02:00.0 eth0: link up

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.