[Kernel-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
Another +1 on -proposed mutter. It solves the problem for me too. -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: Fix Released Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released Status in linux source package in Mantic: Triaged Status in mutter source package in Mantic: Fix Committed Bug description: [ Impact ] gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, sometimes when the screen locks, sometimes when launching particular apps. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Test Plan ] Not all Ryzen systems (including one I just purchased) are able to reproduce the bug. We have no choice but to leave final verification to the community. Anyone affected should try locking their screen and verify they are not instantly returned to the login screen. [ Where problems could occur ] Anywhere in frame scheduling and particularly for mouse cursor movement since that's what the real-time thread exists to optimize. [ Original Description ] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766377] Re: Ethernet E1000 Controller Hangs
I have reported this multiple upstream places, still waiting for a fix... Gave up on canonical to fix this many years ago. -- 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/1766377 Title: Ethernet E1000 Controller Hangs Status in linux package in Ubuntu: Expired Status in linux source package in Bionic: Expired Bug description: With Bionic kernel 4.15.0-15 and 4.15.0-17 I am experiencing periodic hanging of the LAN connection. This is happening on an Asus X99-DELUX motherboard, controller specifications: Intel® I218V, 1 x Gigabit LAN Controller(s) Intel® I211-AT, 1 x Gigabit LAN Dual Gigabit LAN controllers- 802.3az Energy Efficient Ethernet (EEE) appliance Support Teaming Technology ASUS Turbo LAN Utility The CPU is an i7-6850 and it is configured with 128GB of DDR4 RAM. This machine has a number of Qemu/KVM virtual guests and is using a software bridge to share the interface. This did not happen with 17.10 and 4.13.0 kernel. It is happening on multiple machines here. Here are the messages from dmesg: 1016198.957850] e1000e :00:19.0 eno1: Detected Hardware Unit Hang: TDH TDT <2d> next_to_use <2d> next_to_clean buffer_info[next_to_clean]: time_stamp <13c8d0008> next_to_watch jiffies <13c8d0880> next_to_watch.status <0> MAC Status <80083> PHY Status <796d> PHY 1000BASE-T Status <3c00> PHY Extended Status<3000> PCI Status <10> [1016200.942072] e1000e :00:19.0 eno1: Detected Hardware Unit Hang: TDH TDT <2d> next_to_use <2d> next_to_clean buffer_info[next_to_clean]: time_stamp <13c8d0008> next_to_watch jiffies <13c8d1040> next_to_watch.status <0> MAC Status <80083> PHY Status <796d> PHY 1000BASE-T Status <3c00> PHY Extended Status<3000> PCI Status <10> [1016202.413607] e1000e :00:19.0 eno1: Reset adapter unexpectedly [1016202.413701] bridge0: port 1(eno1) entered disabled state [1016202.413732] bridge0: topology change detected, propagating [1016206.76] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [1016206.666708] bridge0: port 1(eno1) entered blocking state [1016206.666712] bridge0: port 1(eno1) entered listening state [1016216.750911] bridge0: port 1(eno1) entered learning state [1016232.110291] bridge0: port 1(eno1) entered forwarding state [1016232.110294] bridge0: topology change detected, sending tcn bpdu [1017834.390579] cfg80211: Loading compiled-in X.509 certificates for regulatory database [1017834.390770] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [1017834.414792] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [1017834.414794] cfg80211: failed to load regulatory.db If there is any other information I can provide to aid in resolution, please contact me, nan...@eskimo.com. Thank you! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15 Uname: Linux 4.15.0-15-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: MATE Date: Mon Apr 23 16:45:30 2018 HibernationDevice: RESUME=UUID=963cb206-8962-4fc0-82a1-fc4f02a9b5c5 InstallationDate: Installed on 2017-05-05 (353 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: ASUS All Series ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-lowlatency root=UUID=28825f5b-a6fd-4e09-982c-0513ae4d2842 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running,
[Kernel-packages] [Bug 1766377] Re: Ethernet E1000 Controller Hangs
I made a workaround for this. That is basically just disable tso. This fix persists across boots. Copy the following script and save it as /etc/systemd/system/disable- tso@enp0s25.service ## [Unit] Description=Disable TSO for %i BindsTo=sys-subsystem-net-devices-%i.device After=sys-subsystem-net-devices-%i.device [Service] Type=oneshot ExecStart=/sbin/ethtool -K %i tso off [Install] WantedBy=sys-subsystem-net-devices-%i.device ## Run "systemctl enable disable-tso@enp0s25" with your interface name instead of "enp0s25" that is what mine is named. If you have more problematic interfaces just enable service for those as well. -- 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/1766377 Title: Ethernet E1000 Controller Hangs Status in linux package in Ubuntu: Expired Status in linux source package in Bionic: Expired Bug description: With Bionic kernel 4.15.0-15 and 4.15.0-17 I am experiencing periodic hanging of the LAN connection. This is happening on an Asus X99-DELUX motherboard, controller specifications: Intel® I218V, 1 x Gigabit LAN Controller(s) Intel® I211-AT, 1 x Gigabit LAN Dual Gigabit LAN controllers- 802.3az Energy Efficient Ethernet (EEE) appliance Support Teaming Technology ASUS Turbo LAN Utility The CPU is an i7-6850 and it is configured with 128GB of DDR4 RAM. This machine has a number of Qemu/KVM virtual guests and is using a software bridge to share the interface. This did not happen with 17.10 and 4.13.0 kernel. It is happening on multiple machines here. Here are the messages from dmesg: 1016198.957850] e1000e :00:19.0 eno1: Detected Hardware Unit Hang: TDH TDT <2d> next_to_use <2d> next_to_clean buffer_info[next_to_clean]: time_stamp <13c8d0008> next_to_watch jiffies <13c8d0880> next_to_watch.status <0> MAC Status <80083> PHY Status <796d> PHY 1000BASE-T Status <3c00> PHY Extended Status<3000> PCI Status <10> [1016200.942072] e1000e :00:19.0 eno1: Detected Hardware Unit Hang: TDH TDT <2d> next_to_use <2d> next_to_clean buffer_info[next_to_clean]: time_stamp <13c8d0008> next_to_watch jiffies <13c8d1040> next_to_watch.status <0> MAC Status <80083> PHY Status <796d> PHY 1000BASE-T Status <3c00> PHY Extended Status<3000> PCI Status <10> [1016202.413607] e1000e :00:19.0 eno1: Reset adapter unexpectedly [1016202.413701] bridge0: port 1(eno1) entered disabled state [1016202.413732] bridge0: topology change detected, propagating [1016206.76] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [1016206.666708] bridge0: port 1(eno1) entered blocking state [1016206.666712] bridge0: port 1(eno1) entered listening state [1016216.750911] bridge0: port 1(eno1) entered learning state [1016232.110291] bridge0: port 1(eno1) entered forwarding state [1016232.110294] bridge0: topology change detected, sending tcn bpdu [1017834.390579] cfg80211: Loading compiled-in X.509 certificates for regulatory database [1017834.390770] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [1017834.414792] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [1017834.414794] cfg80211: failed to load regulatory.db If there is any other information I can provide to aid in resolution, please contact me, nan...@eskimo.com. Thank you! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15 Uname: Linux 4.15.0-15-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0',
[Kernel-packages] [Bug 997605] Re: Disabling IPv6 autoconfiguration in sysctl.conf doesn't affect boot process
Is this going to be fixed in 16.04? -- 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/997605 Title: Disabling IPv6 autoconfiguration in sysctl.conf doesn't affect boot process Status in linux package in Ubuntu: Confirmed Bug description: When you put the following lines in sysctl.conf net.ipv6.conf.all.autoconf = 0 net.ipv6.conf.all.accept_ra = 0 the expeced result is to disable IPv6 autoconfiguration at bootup, but, actually, it does nothing, because sysctl.conf network settings are applied after network has been started. So what happens: 1. Network interfaces are started by /etc/init.d/networking 1a. IPv6 uses autocnfiguratin, because it is enabled at this point 2. Sysctl.conf settings are applied by /etc/init/procps.conf I don't know if there is an easy solution, because inverting order things are called could break something else. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/997605/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1391674] Re: "Reset adapter unexpectedly" - NIC hangs using e1000e driver under average I/O
Any progress on this, i know a lot of users still is experiencing this bug. ** Changed in: linux (Ubuntu) Status: Expired => New -- 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/1391674 Title: "Reset adapter unexpectedly" - NIC hangs using e1000e driver under average I/O Status in linux package in Ubuntu: New Bug description: Using ubuntu 14.04 LTS > uname -a Linux argeste 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux /var/log/syslog: Nov 11 23:29:00 argeste kernel: [846163.967778] e1000e :00:19.0 eth1: Reset adapter unexpectedly Nov 11 23:29:01 argeste kernel: [846163.982417] xen-br1: port 1(eth1) entered disabled state Nov 11 23:29:05 argeste kernel: [846168.028959] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Nov 11 23:29:05 argeste kernel: [846168.029085] xen-br1: port 1(eth1) entered forwarding state Nov 11 23:29:05 argeste kernel: [846168.029094] xen-br1: port 1(eth1) entered forwarding state Nov 11 23:29:08 argeste kernel: [846171.956810] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: Nov 11 23:29:08 argeste kernel: [846171.956810] TDH <0> Nov 11 23:29:08 argeste kernel: [846171.956810] TDT <1> Nov 11 23:29:08 argeste kernel: [846171.956810] next_to_use <1> Nov 11 23:29:08 argeste kernel: [846171.956810] next_to_clean<0> Nov 11 23:29:08 argeste kernel: [846171.956810] buffer_info[next_to_clean]: Nov 11 23:29:08 argeste kernel: [846171.956810] time_stamp <10c9ab819> Nov 11 23:29:08 argeste kernel: [846171.956810] next_to_watch<0> Nov 11 23:29:08 argeste kernel: [846171.956810] jiffies <10c9ab9d1> Nov 11 23:29:08 argeste kernel: [846171.956810] next_to_watch.status <0> Nov 11 23:29:08 argeste kernel: [846171.956810] MAC Status <40080183> Nov 11 23:29:08 argeste kernel: [846171.956810] PHY Status <796d> Nov 11 23:29:08 argeste kernel: [846171.956810] PHY 1000BASE-T Status <3800> Nov 11 23:29:08 argeste kernel: [846171.956810] PHY Extended Status<3000> Nov 11 23:29:08 argeste kernel: [846171.956810] PCI Status <10> Nov 11 23:29:10 argeste kernel: [846173.956722] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: Nov 11 23:29:10 argeste kernel: [846173.956722] TDH <0> Nov 11 23:29:10 argeste kernel: [846173.956722] TDT <1> Nov 11 23:29:10 argeste kernel: [846173.956722] next_to_use <1> Nov 11 23:29:10 argeste kernel: [846173.956722] next_to_clean<0> Nov 11 23:29:10 argeste kernel: [846173.956722] buffer_info[next_to_clean]: Nov 11 23:29:10 argeste kernel: [846173.956722] time_stamp <10c9ab819> Nov 11 23:29:10 argeste kernel: [846173.956722] next_to_watch<0> Nov 11 23:29:10 argeste kernel: [846173.956722] jiffies <10c9abbc5> Nov 11 23:29:10 argeste kernel: [846173.956722] next_to_watch.status <0> Nov 11 23:29:10 argeste kernel: [846173.956722] MAC Status <40080183> Nov 11 23:29:10 argeste kernel: [846173.956722] PHY Status <796d> Nov 11 23:29:10 argeste kernel: [846173.956722] PHY 1000BASE-T Status <3800> Nov 11 23:29:10 argeste kernel: [846173.956722] PHY Extended Status<3000> Nov 11 23:29:10 argeste kernel: [846173.956722] PCI Status <10> Nov 11 23:29:12 argeste kernel: [846175.956759] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: Nov 11 23:29:12 argeste kernel: [846175.956759] TDH <0> Nov 11 23:29:12 argeste kernel: [846175.956759] TDT <1> Nov 11 23:29:12 argeste kernel: [846175.956759] next_to_use <1> Nov 11 23:29:12 argeste kernel: [846175.956759] next_to_clean<0> Nov 11 23:29:12 argeste kernel: [846175.956759] buffer_info[next_to_clean]: Nov 11 23:29:12 argeste kernel: [846175.956759] time_stamp <10c9ab819> Nov 11 23:29:12 argeste kernel: [846175.956759] next_to_watch<0> Nov 11 23:29:12 argeste kernel: [846175.956759] jiffies <10c9abdb9> Nov 11 23:29:12 argeste kernel: [846175.956759] next_to_watch.status <0> Nov 11 23:29:12 argeste kernel: [846175.956759] MAC Status <40080183> Nov 11 23:29:12 argeste kernel: [846175.956759] PHY Status <796d> Nov 11 23:29:12 argeste kernel: [846175.956759] PHY 1000BASE-T Status <3800> Nov 11 23:29:12 argeste kernel: [846175.956759] PHY Extended Status<3000> Nov 11 23:29:12 argeste kernel: [846175.956759] PCI Status <10> Nov 11 23:29:14 argeste kernel: [846177.956686] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: Nov 11 23:29:14 argeste kernel: [846177.956686] TDH <0> Nov 11
