Description of problem: I installed updates and I restarted my computer and this error displayed to me. Additional info: reporter: libreport-2.9.5 NETDEV WATCHDOG: enp0s29f7u1 (rndis_host): transmit queue 0 timed out WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:473 dev_watchdog+0x1f3/0x200 Modules linked in: ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle iptable_raw iptable_security ebtable_filter ebtables ip6table_filter ip6_tables sunrpc b43 bcma mac80211 cfg80211 coretemp joydev iTCO_wdt iTCO_vendor_support i2c_i801 snd_hda_codec_conexant snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_seq ssb snd_seq_device lpc_ich snd_pcm jmb38x_ms memstick ideapad_laptop sparse_keymap rfkill snd_timer shpchp snd soundcore acpi_cpufreq nouveau tg3 mxm_wmi wmi i2c_algo_bit drm_kms_helper sdhci_pci ttm serio_raw cqhci sdhci rndis_host cdc_ether usbnet uas ptp ata_generic pata_acpi drm mmc_core mii pps_core usb_storage video CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.16.13-300.fc28.x86_64 #1 Hardware name: LENOVO 4153/200 /JIWA1, BIOS 0CCN52WW(V1.18) 03/26/2009 RIP: 0010:dev_watchdog+0x1f3/0x200 RSP: 0018:ffff91baff603e80 EFLAGS: 00010282 RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000006 RDX: 0000000000000007 RSI: 0000000000000086 RDI: ffff91baff616930 RBP: ffff91ba766b6478 R08: 0000000000000058 R09: 00000000000003ab R10: 0000000000000000 R11: 0000000000000001 R12: ffff91ba766b6000 R13: 0000000000000000 R14: ffff91baff603ed0 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff91baff600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007ff3ad22d000 CR3: 00000000b936c000 CR4: 00000000000006f0 Call Trace: <IRQ> ? pfifo_fast_reset+0x110/0x110 call_timer_fn+0x2b/0x120 run_timer_softirq+0x3a9/0x3e0 __do_softirq+0xe3/0x2d4 irq_exit+0xeb/0xf0 do_IRQ+0x7d/0xc0 common_interrupt+0xf/0xf </IRQ> RIP: 0010:cpuidle_enter_state+0xb6/0x2a0 RSP: 0018:ffffffffb6203e90 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffcf RAX: ffff91baff620b80 RBX: 000000208964728d RCX: 000000208964728d RDX: 000000208964728d RSI: 00000020896471a8 RDI: 0000000000000000 RBP: ffff91ba76507600 R08: fffffffffff0be0e R09: 0000000000000051 R10: 00000000000001a4 R11: ffff91baff61f984 R12: 0000000000000002 R13: ffffffffb62d7838 R14: 00000020895e8b7f R15: 000000000005ef77 do_idle+0x1a8/0x1d0 cpu_startup_entry+0x6f/0x80 start_kernel+0x4dd/0x4fd secondary_startup_64+0xa5/0xb0 Code: 46 00 48 63 4d e8 eb 93 4c 89 e7 c6 05 8c 08 ba 00 01 e8 81 26 fd ff 89 d9 4c 89 e6 48 c7 c7 f0 4f 15 b6 48 89 c2 e8 67 46 91 ff <0f> 0b eb c0 66 0f 1f 84 00 00 00 00 00 66 66 66 66 90 41 57 41 Potential duplicate: bug 1584278
Created attachment 1449032 [details] File: dmesg
*********** 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 28 kernel bugs. Fedora 28 has now been rebased to 4.17.7-200.fc28. 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 experience different issues, please open a new bug report for those.
*** Bug 1615115 has been marked as a duplicate of this bug. ***
We apologize for the inconvenience. There is 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 28 kernel bugs. Fedora 28 has now been rebased to 4.18.10-300.fc28. 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 29, and are still experiencing this issue, please change the version to Fedora 29. If you experience different issues, please open a new bug report for those.
I am receiving this email: ------------------------ The following is a list of bugs or attachments to bugs in which a user has been waiting more than 7 days for a response from you. Please take action on these requests as quickly as possible. (Note that some of these bugs might already be closed, but a user is still waiting for your response.) We'll remind you again in another 7 days if these requests are still outstanding, or if there are any new requests where users have been waiting more than 7 days for your response. needinfo -------------------- I don't have any more information for this bug. So, what are the next options for this bug, me, the emails?
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days