[Xen-devel] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:316 dev_watchdog+0x217/0x220

[Steven Haigh <netwiz@xxxxxxxxx>]

The last couple of days running on kernel 4.9.29 and 4.9.30 with Xen
4.9.0-rc6 I've had a number of ethernet lock ups that have taken my
system off the network.

This is a new development - but I'm not sure if its kernel or xen related.

in dmesg, I see the following:
WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:316
dev_watchdog+0x217/0x220
NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
Modules linked in: bridge 8021q garp stp llc btrfs dm_mod
crct10dif_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul
glue_helper ablk_helper cryptd raid456 async_raid6_recov async_memcpy
async_pq ppdev iTCO_wdt async_xor xor iTCO_vendor_support async_tx
raid6_pq pcspkr i2c_i801 i2c_smbus pl2303 usbserial sg lpc_ich mfd_core
tpm_infineon parport_pc parport shpchp mei_me mei xenfs xen_privcmd
ip_tables xfs libcrc32c raid1 sd_mod i915 i2c_algo_bit drm_kms_helper
drm crc32c_intel serio_raw ahci libahci i2c_core r8169 mii sata_mv video
xen_acpi_processor xen_pciback xen_netback xen_gntalloc xen_gntdev
xen_evtchn ipv6 crc_ccitt autofs4
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.9.30-1.el7xen.x86_64 #1
Hardware name: Gigabyte Technology Co., Ltd. To be filled by
O.E.M./Z68M-D2H, BIOS U1f 06/13/2012
ffff880080203dd8 ffffffff81348dc5 ffff880080203e28 0000000000000000
ffff880080203e18 ffffffff81081711 0000013c80203e10 0000000000000000
ffff88000526a000 0000000000000001 0000000000000000 ffff88000526a000
Call Trace:
<IRQ>
[<ffffffff81348dc5>] dump_stack+0x63/0x8e
[<ffffffff81081711>] __warn+0xd1/0xf0
[<ffffffff8108177f>] warn_slowpath_fmt+0x4f/0x60
[<ffffffff81602e17>] dev_watchdog+0x217/0x220
[<ffffffff81602c00>] ? dev_deactivate_queue.constprop.27+0x60/0x60
[<ffffffff810e17ea>] call_timer_fn+0x3a/0x130
[<ffffffff810e2c61>] run_timer_softirq+0x191/0x420
[<ffffffff810d509a>] ? handle_percpu_irq+0x3a/0x50
[<ffffffff810d07d2>] ? generic_handle_irq+0x22/0x30
[<ffffffff816b0fe6>] __do_softirq+0xd6/0x287
[<ffffffff81087705>] irq_exit+0xa5/0xb0
[<ffffffff8141ab35>] xen_evtchn_do_upcall+0x35/0x50
[<ffffffff816af50e>] xen_do_hypervisor_callback+0x1e/0x40
<EOI>
[<ffffffff810013aa>] ? xen_hypercall_sched_op+0xa/0x20
[<ffffffff810013aa>] ? xen_hypercall_sched_op+0xa/0x20
[<ffffffff810f2239>] ? __tick_nohz_idle_enter+0x2c9/0x3c0
[<ffffffff810230c0>] ? xen_safe_halt+0x10/0x20
[<ffffffff816ada53>] ? default_idle+0x23/0xd0
[<ffffffff810373bf>] ? arch_cpu_idle+0xf/0x20
[<ffffffff816ade7c>] ? default_idle_call+0x2c/0x40
[<ffffffff810bfc5a>] ? cpu_startup_entry+0x17a/0x210
[<ffffffff816a1417>] ? rest_init+0x77/0x80
[<ffffffff81d3f0e7>] ? start_kernel+0x435/0x442
[<ffffffff81d3eaa0>] ? set_init_arg+0x55/0x55
[<ffffffff81d3e5d6>] ? x86_64_start_reservations+0x2a/0x2c
[<ffffffff81d4615c>] ? xen_start_kernel+0x547/0x553
---[ end trace 2f33c440640c78e5 ]---

All network activity out that ethernet port dies until either:
1) The ethernet cable is unplugged & replugged, or
2) I run: mii-tool -R enp5s0

Either causes the ethernet adapter to be reset.

Any suggestions if this is Xen or kernel related?

-- 
Steven Haigh

Email: netwiz@xxxxxxxxx
Web: https://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel