[Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
I tried the mainline kernel and the error is gone. What next? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
here comes the error: [ 60.259403] [ cut here ] [ 60.259405] NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out [ 60.259416] WARNING: CPU: 6 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 [ 60.259417] Modules linked in: vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter bpfilter aufs overlay nls_iso8859_1 snd_hda_codec_hdmi intel_rapl_msr mei_hdcp snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi intel_rapl_common bridge x86_pkg_temp_thermal intel_powerclamp stp snd_seq llc coretemp kvm_intel snd_seq_device kvm input_leds snd_timer intel_cstate intel_rapl_perf eeepc_wmi asus_wmi sparse_keymap wmi_bmof snd soundcore mei_me mei mac_hid acpi_pad sch_fq_codel parport_pc ppdev lp parport nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid uas usb_storage crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel [ 60.259438] crypto_simd i915 mxm_wmi i2c_algo_bit cryptd glue_helper drm_kms_helper nvme syscopyarea sysfillrect sysimgblt fb_sys_fops r8169 i2c_i801 drm nvme_core ahci realtek libahci wmi video [ 60.259444] CPU: 6 PID: 0 Comm: swapper/6 Tainted: G OE 5.4.0-33-generic #37-Ubuntu [ 60.259445] Hardware name: bluechip Computer AG BUSINESSline/Z170-K, BIOS 3805 05/16/2018 [ 60.259446] RIP: 0010:dev_watchdog+0x258/0x260 [ 60.259447] Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 ef f6 e7 00 01 e8 6d bb fa ff 44 89 e9 4c 89 fe 48 c7 c7 40 73 e3 8f 48 89 c2 e8 03 30 71 ff <0f> 0b eb 80 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 d7 [ 60.259448] RSP: 0018:af7200234e30 EFLAGS: 00010286 [ 60.259448] RAX: RBX: 9c6ded99fa00 RCX: 0006 [ 60.259449] RDX: 0007 RSI: 0096 RDI: 9c6df6b978c0 [ 60.259449] RBP: af7200234e60 R08: 04a0 R09: 0004 [ 60.259450] R10: R11: 0001 R12: 0001 [ 60.259450] R13: R14: 9c6defed4480 R15: 9c6defed4000 [ 60.259451] FS: () GS:9c6df6b8() knlGS: [ 60.259451] CS: 0010 DS: ES: CR0: 80050033 [ 60.259452] CR2: 1a62928112d0 CR3: 0009e1e0a002 CR4: 003606e0 [ 60.259452] DR0: DR1: DR2: [ 60.259453] DR3: DR6: fffe0ff0 DR7: 0400 [ 60.259453] Call Trace: [ 60.259454] [ 60.259456] ? pfifo_fast_enqueue+0x150/0x150 [ 60.259458] call_timer_fn+0x32/0x130 [ 60.259459] __run_timers.part.0+0x180/0x280 [ 60.259461] ? timerqueue_add+0x68/0xb0 [ 60.259462] ? enqueue_hrtimer+0x3d/0x90 [ 60.259464] ? recalibrate_cpu_khz+0x10/0x10 [ 60.259465] ? ktime_get+0x3e/0xa0 [ 60.259466] run_timer_softirq+0x2a/0x50 [ 60.259467] __do_softirq+0xe1/0x2d6 [ 60.259468] ? hrtimer_interrupt+0x13b/0x220 [ 60.259469] irq_exit+0xae/0xb0 [ 60.259470] smp_apic_timer_interrupt+0x7b/0x140 [ 60.259472] apic_timer_interrupt+0xf/0x20 [ 60.259472] [ 60.259473] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [ 60.259474] Code: ff e8 9f 04 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 f2 74 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d c8 48 8d [ 60.259475] RSP: 0018:af72000efe38 EFLAGS: 0246 ORIG_RAX: ff13 [ 60.259475] RAX: 9c6df6baad00 RBX: 90159dc0 RCX: 001f [ 60.259476] RDX: RSI: 1fef9fcd RDI: [ 60.259476] RBP: af72000efe78 R08: 000e07bd779e R09: 0335 [ 60.259477] R10: 9c6df6ba9a00 R11: 9c6df6ba99e0 R12: 9c6df6bb5700 [ 60.259477] R13: 0002 R14: 0002 R15: 9c6df6bb5700 [ 60.259478] ? cpuidle_enter_state+0xa1/0x450 [ 60.259479] cpuidle_enter+0x2e/0x40 [ 60.259480] call_cpuidle+0x23/0x40 [ 60.259481] do_idle+0x1dd/0x270 [ 60.259482] cpu_startup_entry+0x20/0x30 [ 60.259483] start_secondary+0x167/0x1c0 [ 60.259485] secondary_startup_64+0xa4/0xb0 [ 60.259486] ---[ end trace acbef11636a70d66 ]--- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com
[Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
I can confirm this error on my system after upgrade from bionic to focal. System works "normaly" but error appears in the logs. Adding "pcie_aspm=off" does not help in my case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839317] Re: Grub fails to chainload the Windows Boot Manager
I'm also facing the same problem and I found a solution which worked for me on amd64. My system is using UEFI without secure boot from a gpt partitioned drive. Please try to install the package shim-signed. This fixed the problem for me. Chainloading Windows even works after uninstalling the package again. So I expect it is something related to the installation process of the package. Maybe it leaves some important files in /boot after uninstalling. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839317 Title: Grub fails to chainload the Windows Boot Manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1839317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822048] Re: cluster report not displayed
I have the same issue and the upstream patch fixes it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822048 Title: cluster report not displayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ganglia-web/+bug/1822048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs
Hi Brian, thank you for providing this fix. It works fine on a minimal 18.10 server. I installed systemd 239-7ubuntu10.5 on a updated system. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804603 Title: systemd-tmpfiles-setup.service fails on btrfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs
I just checked 18.10 with systemd 239-7ubuntu10.4 and it fails with the same error message. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804603 Title: systemd-tmpfiles-setup.service fails on btrfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs
** Attachment added: "apt log with 'Bad file descriptor' error" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+attachment/5218416/+files/term.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804603 Title: systemd-tmpfiles-setup.service fails on btrfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804603] Re: systemd-tmpfiles-setup.service fails
I did some tests. This issue is clearly related to btrfs, because I can not reproduce this with ext4. If you have a different filesystem, you have a different issue, maybe the one in https://launchpad.net/bugs/1804847. How to reproduce this: 1) clean install from 'ubuntu-18.04.1-live-server-amd64.iso', all settings default but change root filesystem to btrfs. 2) system starts fine after reboot 3) issue 'apt install systemd' and get the 'Bad file descriptor' error allready during installation (attached log) 4) reboot with failing systemd-tmpfiles-setup.service I will also attach a log of the errors during apt install. ** Summary changed: - systemd-tmpfiles-setup.service fails + systemd-tmpfiles-setup.service fails on btrfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804603 Title: systemd-tmpfiles-setup.service fails on btrfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804603] Re: systemd-tmpfiles-setup.service fails
Yes but only because they have reverted the changes from CVE-2018-6954. This will come back very soon. Have a look at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.10 and https://launchpad.net/bugs/1804847 . ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-6954 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804603 Title: systemd-tmpfiles-setup.service fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804847] Re: systemd=229-4ubuntu21.8 use of fchownat failes on some systems (openvz)
Could someone please have a look at https://launchpad.net/bugs/1804603 because the changes made to fix CVE-2018-6954 break systemd-tmpfiles also in a different way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804847 Title: systemd=229-4ubuntu21.8 use of fchownat failes on some systems (openvz) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804611] [NEW] systemd-networkd is stuck in 'configuring' with DHCP and no default route
Public bug reported: In our network setup systemd-networkd fails to configure everything correctly. Our systems have two NIC which are configured via DHCP. One NIC is in a service network without a default route. With this setup we get systemd-networkd-wait-online.service failing after timeout and the service NIC stuck in 'configuring'. Besides that, everything is working as expected. Our config: # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy systemd systemd: Installiert: 237-3ubuntu10.9 Installationskandidat: 237-3ubuntu10.9 Versionstabelle: *** 237-3ubuntu10.9 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Package # cat /etc/systemd/network/ens160.network [Match] Name=ens160 [Network] DHCP=ipv4 [DHCP] UseMTU=true RouteMetric=100 ClientIdentifier=mac # cat /etc/systemd/network/ens192.network [Match] Name=ens192 [Network] DHCP=ipv4 [DHCP] UseMTU=true RouteMetric=100 ClientIdentifier=mac UseRoutes=false UseDNS=false networkctl status -a ● 1: lo Link File: n/a Network File: n/a Type: loopback State: carrier (unmanaged) Address: 127.0.0.1 ::1 ● 2: ens160 Link File: n/a Network File: /etc/systemd/network/ens160.network Type: ether State: routable (configured) Path: pci-:03:00.0 Vendor: VMware Model: VMXNET3 Ethernet Controller HW Address: 00:50:56:a4:98:4c (VMware, Inc.) Address: 10.22.0.30 fe80::250:56ff:fea4:984c Gateway: 10.22.200.254 (Hewlett Packard Enterprise) DNS: 10.22.0.2 Search Domains: xxx ● 3: ens192 Link File: n/a Network File: /etc/systemd/network/ens192.network Type: ether State: routable (configuring) Path: pci-:0b:00.0 Vendor: VMware Model: VMXNET3 Ethernet Controller HW Address: 00:50:56:a4:c0:42 (VMware, Inc.) Address: 10.23.0.30 fe80::250:56ff:fea4:c042 Search Domains: This also happens in other configurations, which are more complex as soon as I add the service NIC which has no default route. systemd 239 from ubuntu 16.10 works fine. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804611 Title: systemd-networkd is stuck in 'configuring' with DHCP and no default route To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804603] [NEW] systemd-tmpfiles-setup.service fails on btrfs
Public bug reported: After update to systemd 237-3ubuntu10.9 systemd-tmpfiles-setup.service fails with: Nov 21 13:44:12 node-blc49 systemd[1]: Starting Create Volatile Files and Directories... Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/var": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/home": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/srv": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Nov 21 13:44:12 node-blc49 systemd[1]: Failed to start Create Volatile Files and Directories. This happens on btrfs root filesystems in real hardware and on our virtualized servers as well. 237-3ubuntu10.6 didnt show this errors and going back to 237-3ubuntu10 removes them as well. # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy systemd systemd: Installiert: 237-3ubuntu10.9 Installationskandidat: 237-3ubuntu10.9 Versionstabelle: *** 237-3ubuntu10.9 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804603 Title: systemd-tmpfiles-setup.service fails on btrfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787948] [NEW] environment-modules should depend on tcl and not on tcl8.6
Public bug reported: # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy environment-modules environment-modules: Installiert: 4.1.1-1 Installationskandidat: 4.1.1-1 Versionstabelle: *** 4.1.1-1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status Installing environment-modules on a clean server install pulls in tcl8.6 as a dependency. After installation no tclsh is available, but its needed by e.g. /usr/share/modules/init/bash. Installing tcl makes /usr/bin/tclsh available. ** Affects: modules (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787948 Title: environment-modules should depend on tcl and not on tcl8.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modules/+bug/1787948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
