kernel-packages team mailing list archive

Thread
Date
[Bug 1425333] Re: Precise kernel lockup with Intel Corporation 82579LM network interfaces

To: kernel-packages@xxxxxxxxxxxxxxxxxxx
From: Rafael David Tinoco <inaddy@xxxxxxxxxx>
Date: Thu, 23 Apr 2015 17:19:07 -0000
Reply-to: Bug 1425333 <1425333@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx
With all those fixes backported we still got a kernel lockup:

Apr 21 11:55:25  kernel: [992864.965769] Pid: 0, comm: swapper/0 Tainted: P         C O 3.2.0-77-generic #112hf79117v20150224b1-Ubuntu
Apr 21 11:55:25  kernel: [992864.965772] Call Trace:
Apr 21 11:55:25  kernel: [992864.965773]  <IRQ>  [<ffffffff8106845f>] warn_slowpath_common+0x7f/0xc0
Apr 21 11:55:25  kernel: [992864.965786]  [<ffffffff8104f624>] ? __enqueue_entity+0x74/0x80
Apr 21 11:55:25  kernel: [992864.965790]  [<ffffffff81068556>] warn_slowpath_fmt+0x46/0x50
Apr 21 11:55:25  kernel: [992864.965794]  [<ffffffff81025712>] ? x86_pmu_enable+0x1f2/0x270
Apr 21 11:55:25  kernel: [992864.965800]  [<ffffffff81568e0a>] dev_watchdog+0x25a/0x270
Apr 21 11:55:25  kernel: [992864.965805]  [<ffffffff811133f0>] ? perf_rotate_context+0x110/0x220
Apr 21 11:55:25  kernel: [992864.965809]  [<ffffffff81568bb0>] ? qdisc_reset+0x50/0x50
Apr 21 11:55:25  kernel: [992864.965813]  [<ffffffff81568bb0>] ? qdisc_reset+0x50/0x50
Apr 21 11:55:25  kernel: [992864.965819]  [<ffffffff81077466>] call_timer_fn+0x46/0x160
Apr 21 11:55:25  kernel: [992864.965823]  [<ffffffff81568bb0>] ? qdisc_reset+0x50/0x50
Apr 21 11:55:25  kernel: [992864.965827]  [<ffffffff81078db2>] run_timer_softirq+0x132/0x2a0
Apr 21 11:55:25  kernel: [992864.965833]  [<ffffffff81096675>] ? ktime_get+0x65/0xe0
Apr 21 11:55:25  kernel: [992864.965836]  [<ffffffff8106fcf8>] __do_softirq+0xa8/0x210
Apr 21 11:55:25  kernel: [992864.965841]  [<ffffffff8109d714>] ? tick_program_event+0x24/0x30
Apr 21 11:55:25  kernel: [992864.965845]  [<ffffffff8166f06c>] call_softirq+0x1c/0x30
Apr 21 11:55:25  kernel: [992864.965851]  [<ffffffff810164e5>] do_softirq+0x65/0xa0
Apr 21 11:55:25  kernel: [992864.965854]  [<ffffffff810700de>] irq_exit+0x8e/0xb0
Apr 21 11:55:25  kernel: [992864.965858]  [<ffffffff8166fa1e>] smp_apic_timer_interrupt+0x6e/0x99
Apr 21 11:55:25  kernel: [992864.965863]  [<ffffffff8166d8de>] apic_timer_interrupt+0x6e/0x80
Apr 21 11:55:25  kernel: [992864.965865]  <EOI>  [<ffffffff8109c184>] ? clockevents_program_event+0x74/0x100
Apr 21 11:55:25  kernel: [992864.965873]  [<ffffffff81371a5d>] ? intel_idle+0xed/0x150
Apr 21 11:55:25  kernel: [992864.965877]  [<ffffffff81371a3f>] ? intel_idle+0xcf/0x150
Apr 21 11:55:25  kernel: [992864.965883]  [<ffffffff8150e921>] cpuidle_idle_call+0xc1/0x290
Apr 21 11:55:25  kernel: [992864.965887]  [<ffffffff8101322a>] cpu_idle+0xca/0x120
Apr 21 11:55:25  kernel: [992864.965892]  [<ffffffff8162af5e>] rest_init+0x72/0x74
Apr 21 11:55:25  kernel: [992864.965897]  [<ffffffff81cfbc0b>] start_kernel+0x3ba/0x3c7
Apr 21 11:55:25  kernel: [992864.965902]  [<ffffffff81cfb388>] x86_64_start_reservations+0x132/0x136
Apr 21 11:55:25  kernel: [992864.965907]  [<ffffffff81cfb140>] ? early_idt_handlers+0x140/0x140
Apr 21 11:55:25  kernel: [992864.965911]  [<ffffffff81cfb459>] x86_64_start_kernel+0xcd/0xdc
Apr 21 11:55:25  kernel: [992864.965914] ---[ end trace f20333a4474e470d ]---
Apr 21 11:55:25  kernel: [992864.965930] e1000e 0000:00:19.0: eth0: Reset adapter
Apr 21 11:55:29  kernel: [992868.720990] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx

It looks like network interface was restored after some time but I asked
for a kernel dump and more information regarding the network topology.

** Tags removed: verification-needed-precise
** Tags added: cts verification-failed-precise

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1425333

Title:
  Precise kernel lockup with Intel Corporation 82579LM network
  interfaces

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Precise:
  Fix Committed

Bug description:
  SRU Justification:

  Impact: e1000e driver can lockup in machine HP Z210.
  Fix: All the patches were taken from upstream.
  Testcase: To use an HP Z210 machine and wait certain conditions.

  ####

  Original Description:

  It was brought to my attention the following lockup (and error
  message):

  Feb  1 21:17:54 hostname kernel: [10461681.674619] NETDEV WATCHDOG:
  eth0 (e1000e): transmit queue 0 timed out

  """
  Feb  1 21:17:54 hostname kernel: [10461681.674613] WARNING: at /build/buildd/linux-3.2.0/net/sched/sch_generic.c:255 dev_watchdog+0x25a/0x270()
  Feb  1 21:17:54 hostname kernel: [10461681.674616] Hardware name: HP Z210 Workstation
  Feb  1 21:17:54 hostname kernel: [10461681.674619] NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out
  Feb  1 21:17:54 hostname kernel: [10461681.674622] Modules linked in: nvidia(P) btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs reiserfs ext2 openafs(P) bnep rfcomm bluetooth autofs4 parport_pc ppdev nfsd nfs binfmt_misc lockd fscache auth_rpcgss nfs_acl sunrpc snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq joydev hp_wmi snd_timer snd_seq_device snd mei(C) psmouse soundcore sparse_keymap serio_raw mac_hid wmi snd_page_alloc lp parport dm_multipath ses enclosure hid_logitech_dj usb_storage usbhid hid e1000e [last unloaded: nvidia]
  Feb  1 21:17:54 hostname kernel: [10461681.674683] Pid: 0, comm: swapper/0 Tainted: P         C O 3.2.0-69-generic #103-Ubuntu
  Feb  1 21:17:54 hostname kernel: [10461681.674684] Call Trace:
  Feb  1 21:17:54 hostname kernel: [10461681.674685]  <IRQ>  [<ffffffff8106844f>] warn_slowpath_common+0x7f/0xc0
  Feb  1 21:17:54 hostname kernel: [10461681.674692]  [<ffffffff8104f634>] ? __enqueue_entity+0x74/0x80
  Feb  1 21:17:54 hostname kernel: [10461681.674694]  [<ffffffff81068546>] warn_slowpath_fmt+0x46/0x50
  Feb  1 21:17:54 hostname kernel: [10461681.674696]  [<ffffffff81025392>] ? x86_pmu_enable+0x1f2/0x270
  Feb  1 21:17:54 hostname kernel: [10461681.674699]  [<ffffffff815684fa>] dev_watchdog+0x25a/0x270
  Feb  1 21:17:54 hostname kernel: [10461681.674701]  [<ffffffff81113310>] ? perf_rotate_context+0x110/0x220
  Feb  1 21:17:54 hostname kernel: [10461681.674703]  [<ffffffff815682a0>] ? qdisc_reset+0x50/0x50
  Feb  1 21:17:54 hostname kernel: [10461681.674705]  [<ffffffff815682a0>] ? qdisc_reset+0x50/0x50
  Feb  1 21:17:54 hostname kernel: [10461681.674708]  [<ffffffff81077456>] call_timer_fn+0x46/0x160
  Feb  1 21:17:54 hostname kernel: [10461681.674710]  [<ffffffff815682a0>] ? qdisc_reset+0x50/0x50
  Feb  1 21:17:54 hostname kernel: [10461681.674712]  [<ffffffff81078da2>] run_timer_softirq+0x132/0x2a0
  Feb  1 21:17:54 hostname kernel: [10461681.674715]  [<ffffffff81096655>] ? ktime_get+0x65/0xe0
  Feb  1 21:17:54 hostname kernel: [10461681.674717]  [<ffffffff8106fce8>] __do_softirq+0xa8/0x210
  Feb  1 21:17:54 hostname kernel: [10461681.674719]  [<ffffffff8109d664>] ? tick_program_event+0x24/0x30
  Feb  1 21:17:54 hostname kernel: [10461681.674723]  [<ffffffff8166e4ac>] call_softirq+0x1c/0x30
  Feb  1 21:17:54 hostname kernel: [10461681.674725]  [<ffffffff81016495>] do_softirq+0x65/0xa0
  Feb  1 21:17:54 hostname kernel: [10461681.674727]  [<ffffffff810700ce>] irq_exit+0x8e/0xb0
  Feb  1 21:17:54 hostname kernel: [10461681.674729]  [<ffffffff8166ee5e>] smp_apic_timer_interrupt+0x6e/0x99
  Feb  1 21:17:54 hostname kernel: [10461681.674731]  [<ffffffff8166cd1e>] apic_timer_interrupt+0x6e/0x80
  Feb  1 21:17:54 hostname kernel: [10461681.674732]  <EOI>  [<ffffffff8101d721>] ? __switch_to_xtra+0x171/0x180
  Feb  1 21:17:54 hostname kernel: [10461681.674737]  [<ffffffff813713ad>] ? intel_idle+0xed/0x150
  Feb  1 21:17:54 hostname kernel: [10461681.674739]  [<ffffffff8137138f>] ? intel_idle+0xcf/0x150
  Feb  1 21:17:54 hostname kernel: [10461681.674742]  [<ffffffff8150e001>] cpuidle_idle_call+0xc1/0x290
  Feb  1 21:17:54 hostname kernel: [10461681.674744]  [<ffffffff8101322a>] cpu_idle+0xca/0x120
  Feb  1 21:17:54 hostname kernel: [10461681.674746]  [<ffffffff8162a4fe>] rest_init+0x72/0x74
  Feb  1 21:17:54 hostname kernel: [10461681.674750]  [<ffffffff81cfcc06>] start_kernel+0x3b5/0x3c2
  Feb  1 21:17:54 hostname kernel: [10461681.674752]  [<ffffffff81cfc388>] x86_64_start_reservations+0x132/0x136
  Feb  1 21:17:54 hostname kernel: [10461681.674754]  [<ffffffff81cfc140>] ? early_idt_handlers+0x140/0x140
  Feb  1 21:17:54 hostname kernel: [10461681.674756]  [<ffffffff81cfc459>] x86_64_start_kernel+0xcd/0xdc
  Feb  1 21:17:54 hostname kernel: [10461681.674757] ---[ end trace a84a3dbc98d19bff ]---
  Feb  1 21:17:54 hostname kernel: [10461681.674762] e1000e 0000:00:19.0: eth0: Reset adapter
  Feb  1 21:17:58 hostname kernel: [10461685.529232] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
  """

  This happens with the e1000e module on HP z210 systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1425333/+subscriptions
References

[Bug 1425333] [NEW] Precise kernel lockup with Intel Corporation 82579LM network interfaces
From: Rafael David Tinoco, 2015-02-25