Hide Forgot
After booting, I noticed that within the first few minutes, I get this crash message. The adapter works normally afterwards, but all network activity stops until after this crash message. If it matters, this is using jumbo frames (MTU 9000). [ 179.289531] ------------[ cut here ]------------ [ 179.289547] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:306 dev_watchdog+0x235/0x240 [ 179.289551] NETDEV WATCHDOG: enp5s0 (sky2): transmit queue 0 timed out [ 179.289554] Modules linked in: rfcomm ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_security ip6table_mangle ip6table_raw ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 iptable_security iptable_mangle iptable_raw iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ebtable_filter ebtables ip6table_filter ip6_tables bnep nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) snd_hda_codec_hdmi ir_lirc_codec lirc_dev r820t rtl2832 i2c_mux iTCO_wdt iTCO_vendor_support snd_hda_codec_realtek snd_hda_codec_generic coretemp kvm_intel snd_hda_intel dvb_usb_rtl28xxu drm_kms_helper btusb dvb_usb_v2 btrtl btbcm snd_hda_codec drm btintel dvb_core kvm snd_hda_core snd_hwdep bluetooth snd_seq snd_seq_device [ 179.289601] irqbypass rc_core joydev snd_pcm rfkill snd_timer snd i7core_edac i2c_i801 lpc_ich soundcore shpchp edac_core i5500_temp asus_atk0110 acpi_cpufreq tpm_tis tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc mxm_wmi crc32c_intel serio_raw sky2 hid_microsoft fjes wmi [ 179.289623] CPU: 0 PID: 0 Comm: swapper/0 Tainted: P IOE 4.6.6-300.fc24.x86_64 #1 [ 179.289625] Hardware name: System manufacturer System Product Name/P6X58D-E, BIOS 0803 08/06/2012 [ 179.289627] 0000000000000286 60d93611ea8ce70a ffff8801b9203d98 ffffffff813dbf2f [ 179.289630] ffff8801b9203de8 0000000000000000 ffff8801b9203dd8 ffffffff810a741b [ 179.289632] 0000013281c6c8c0 0000000000000000 ffff8801b580b000 0000000000000000 [ 179.289635] Call Trace: [ 179.289636] <IRQ> [<ffffffff813dbf2f>] dump_stack+0x63/0x84 [ 179.289645] [<ffffffff810a741b>] __warn+0xcb/0xf0 [ 179.289648] [<ffffffff810a749f>] warn_slowpath_fmt+0x5f/0x80 [ 179.289651] [<ffffffff816ec5e5>] dev_watchdog+0x235/0x240 [ 179.289654] [<ffffffff816ec3b0>] ? qdisc_rcu_free+0x40/0x40 [ 179.289657] [<ffffffff81112e85>] call_timer_fn+0x35/0x120 [ 179.289660] [<ffffffff816ec3b0>] ? qdisc_rcu_free+0x40/0x40 [ 179.289662] [<ffffffff811134ce>] run_timer_softirq+0x21e/0x2d0 [ 179.289666] [<ffffffff817e3ce2>] __do_softirq+0x112/0x2e7 [ 179.289668] [<ffffffff810ad145>] irq_exit+0x105/0x110 [ 179.289671] [<ffffffff817e3ae2>] smp_apic_timer_interrupt+0x42/0x50 [ 179.289674] [<ffffffff817e1c1c>] apic_timer_interrupt+0x8c/0xa0 [ 179.289675] <EOI> [<ffffffff81675120>] ? cpuidle_enter_state+0x110/0x2b0 [ 179.289681] [<ffffffff816752f7>] cpuidle_enter+0x17/0x20 [ 179.289684] [<ffffffff810eb1ea>] call_cpuidle+0x2a/0x50 [ 179.289687] [<ffffffff810eb5d3>] cpu_startup_entry+0x2a3/0x350 [ 179.289690] [<ffffffff817d3b07>] rest_init+0x77/0x80 [ 179.289694] [<ffffffff81d69006>] start_kernel+0x453/0x474 [ 179.289697] [<ffffffff81d68120>] ? early_idt_handler_array+0x120/0x120 [ 179.289700] [<ffffffff81d68346>] x86_64_start_reservations+0x2a/0x2c [ 179.289703] [<ffffffff81d68494>] x86_64_start_kernel+0x14c/0x16f [ 179.289705] ---[ end trace 387d5665812891f6 ]--- [ 179.289710] sky2 0000:05:00.0 enp5s0: tx timeout [ 179.289717] sky2 0000:05:00.0 enp5s0: transmit ring 125 .. 0 report=125 done=125 [ 179.295228] sky2 0000:05:00.0 enp5s0: checksum offload not possible with jumbo frames [ 182.388925] sky2 0000:05:00.0 enp5s0: Link is up at 1000 Mbps, full duplex, flow control rx
This still occurs with kernel 4.7.2-201.fc24.x86_64
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs. Fedora 25 has now been rebased to 4.10.9-100.fc24. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.