[Kernel-packages] [Bug 1824038] Re: Network adapter doesn't work after returning from suspend
Confirmed. The same behaviour in the original kernel 4.18.0-17. -- 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/1824038 Title: Network adapter doesn't work after returning from suspend Status in linux package in Ubuntu: Confirmed Bug description: Fresh install of Ubuntu 18.04 (Linux kernel 4.18.0-17-generic #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:12 UTC 2019). Network adapter does not resume after suspend. Wifi not available. References to a fix for r8169 driver found. Tried the following fixes: 1. sudo service network-manager restart. This did not work. 2. Script in /lib/systemd/system-sleep/r8169-refresh as described in https://askubuntu.com/questions/1029250/ubuntu-18-04-ethernet-disconnected-after-suspend This did not work. 3. Updated kernel to 4.20.17. This did not work. There is reference to r8169 fixes in version 4.21, but this is not available on the ubuntu mainline kernels https://kernel.ubuntu.com/~kernel-ppa/mainline/ Possibly related to bug #1752772 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-04-08 (2 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: linux (not installed) Tags: bionic Uname: Linux 4.20.17-042017-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824038/+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 1824038] Re: Network adapter doesn't work after returning from suspend
An update on this. I installed kernel 5.0, but the same issue occured. I did notice that my wi-fi can be re-activated using the keyboard wireless switch (Fn-Wifi). I have 2 wi-fi networks available, the normal one and the 5G one. I had been using the 5G one, but switched to use the normal one. My wi-fi came back up, and resumes ok after being in standby. I re-booted using the kernel 5.1.rc4, and it works ok as above. I don't remember trying the physical wi-fi function key before, so it is possible it would have worked in the Ubuntu current mainline kernel 4.18, which I will test next. Could the issue be 5G wifi specific? -- 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/1824038 Title: Network adapter doesn't work after returning from suspend Status in linux package in Ubuntu: Confirmed Bug description: Fresh install of Ubuntu 18.04 (Linux kernel 4.18.0-17-generic #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:12 UTC 2019). Network adapter does not resume after suspend. Wifi not available. References to a fix for r8169 driver found. Tried the following fixes: 1. sudo service network-manager restart. This did not work. 2. Script in /lib/systemd/system-sleep/r8169-refresh as described in https://askubuntu.com/questions/1029250/ubuntu-18-04-ethernet-disconnected-after-suspend This did not work. 3. Updated kernel to 4.20.17. This did not work. There is reference to r8169 fixes in version 4.21, but this is not available on the ubuntu mainline kernels https://kernel.ubuntu.com/~kernel-ppa/mainline/ Possibly related to bug #1752772 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-04-08 (2 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: linux (not installed) Tags: bionic Uname: Linux 4.20.17-042017-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824038/+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 1824038] Re: Network adapter doesn't work after returning from suspend
Can you tell me how I would do that. I added the first name to the subscription list, but I can't do it with the second two. -- 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/1824038 Title: Network adapter doesn't work after returning from suspend Status in linux package in Ubuntu: Confirmed Bug description: Fresh install of Ubuntu 18.04 (Linux kernel 4.18.0-17-generic #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:12 UTC 2019). Network adapter does not resume after suspend. Wifi not available. References to a fix for r8169 driver found. Tried the following fixes: 1. sudo service network-manager restart. This did not work. 2. Script in /lib/systemd/system-sleep/r8169-refresh as described in https://askubuntu.com/questions/1029250/ubuntu-18-04-ethernet-disconnected-after-suspend This did not work. 3. Updated kernel to 4.20.17. This did not work. There is reference to r8169 fixes in version 4.21, but this is not available on the ubuntu mainline kernels https://kernel.ubuntu.com/~kernel-ppa/mainline/ Possibly related to bug #1752772 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-04-08 (2 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: linux (not installed) Tags: bionic Uname: Linux 4.20.17-042017-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824038/+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 1824038] Re: Network adapter doesn't work after returning from suspend
Sorry, typo. 2. Re-tested with 5.1-rc4. Problem still occurs. -- 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/1824038 Title: Network adapter doesn't work after returning from suspend Status in linux package in Ubuntu: Confirmed Bug description: Fresh install of Ubuntu 18.04 (Linux kernel 4.18.0-17-generic #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:12 UTC 2019). Network adapter does not resume after suspend. Wifi not available. References to a fix for r8169 driver found. Tried the following fixes: 1. sudo service network-manager restart. This did not work. 2. Script in /lib/systemd/system-sleep/r8169-refresh as described in https://askubuntu.com/questions/1029250/ubuntu-18-04-ethernet-disconnected-after-suspend This did not work. 3. Updated kernel to 4.20.17. This did not work. There is reference to r8169 fixes in version 4.21, but this is not available on the ubuntu mainline kernels https://kernel.ubuntu.com/~kernel-ppa/mainline/ Possibly related to bug #1752772 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-04-08 (2 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: linux (not installed) Tags: bionic Uname: Linux 4.20.17-042017-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824038/+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 1824038] Re: Network adapter doesn't work after returning from suspend
1. Removed the r8169-refresh script 2. Rested with 5.1-rc4 Problem still occurs. See updated dmesg log. ** Attachment added: "dmesg1.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824038/+attachment/5254609/+files/dmesg1.log -- 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/1824038 Title: Network adapter doesn't work after returning from suspend Status in linux package in Ubuntu: Confirmed Bug description: Fresh install of Ubuntu 18.04 (Linux kernel 4.18.0-17-generic #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:12 UTC 2019). Network adapter does not resume after suspend. Wifi not available. References to a fix for r8169 driver found. Tried the following fixes: 1. sudo service network-manager restart. This did not work. 2. Script in /lib/systemd/system-sleep/r8169-refresh as described in https://askubuntu.com/questions/1029250/ubuntu-18-04-ethernet-disconnected-after-suspend This did not work. 3. Updated kernel to 4.20.17. This did not work. There is reference to r8169 fixes in version 4.21, but this is not available on the ubuntu mainline kernels https://kernel.ubuntu.com/~kernel-ppa/mainline/ Possibly related to bug #1752772 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-04-08 (2 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: linux (not installed) Tags: bionic Uname: Linux 4.20.17-042017-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824038/+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 1824038] Re: Network adapter doesn't work after returning from suspend
dmesg output as requested ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824038/+attachment/5254598/+files/dmesg.log -- 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/1824038 Title: Network adapter doesn't work after returning from suspend Status in linux package in Ubuntu: Confirmed Bug description: Fresh install of Ubuntu 18.04 (Linux kernel 4.18.0-17-generic #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:12 UTC 2019). Network adapter does not resume after suspend. Wifi not available. References to a fix for r8169 driver found. Tried the following fixes: 1. sudo service network-manager restart. This did not work. 2. Script in /lib/systemd/system-sleep/r8169-refresh as described in https://askubuntu.com/questions/1029250/ubuntu-18-04-ethernet-disconnected-after-suspend This did not work. 3. Updated kernel to 4.20.17. This did not work. There is reference to r8169 fixes in version 4.21, but this is not available on the ubuntu mainline kernels https://kernel.ubuntu.com/~kernel-ppa/mainline/ Possibly related to bug #1752772 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-04-08 (2 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: linux (not installed) Tags: bionic Uname: Linux 4.20.17-042017-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824038/+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 1824038] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1824038/+attachment/5254570/+files/ProcEnviron.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1824038 Title: Network adapter doesn't work after returning from suspend Status in linux package in Ubuntu: Confirmed Bug description: Fresh install of Ubuntu 18.04 (Linux kernel 4.18.0-17-generic #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:12 UTC 2019). Network adapter does not resume after suspend. Wifi not available. References to a fix for r8169 driver found. Tried the following fixes: 1. sudo service network-manager restart. This did not work. 2. Script in /lib/systemd/system-sleep/r8169-refresh as described in https://askubuntu.com/questions/1029250/ubuntu-18-04-ethernet-disconnected-after-suspend This did not work. 3. Updated kernel to 4.20.17. This did not work. There is reference to r8169 fixes in version 4.21, but this is not available on the ubuntu mainline kernels https://kernel.ubuntu.com/~kernel-ppa/mainline/ Possibly related to bug #1752772 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-04-08 (2 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: linux (not installed) Tags: bionic Uname: Linux 4.20.17-042017-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824038/+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 1824038] Re: Network adapter doesn't work after returning from suspend
apport information ** Tags added: apport-collected bionic ** Description changed: Fresh install of Ubuntu 18.04 (Linux kernel 4.18.0-17-generic #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:12 UTC 2019). Network adapter does not resume after suspend. Wifi not available. References to a fix for r8169 driver found. Tried the following fixes: 1. sudo service network-manager restart. This did not work. 2. Script in /lib/systemd/system-sleep/r8169-refresh as described in https://askubuntu.com/questions/1029250/ubuntu-18-04-ethernet-disconnected-after-suspend This did not work. 3. Updated kernel to 4.20.17. This did not work. There is reference to r8169 fixes in version 4.21, but this is not available on the ubuntu mainline kernels https://kernel.ubuntu.com/~kernel-ppa/mainline/ Possibly related to bug #1752772 + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.6 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2019-04-08 (2 days ago) + InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) + Package: linux (not installed) + Tags: bionic + Uname: Linux 4.20.17-042017-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1824038/+attachment/5254569/+files/ProcCpuinfoMinimal.txt -- 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/1824038 Title: Network adapter doesn't work after returning from suspend Status in linux package in Ubuntu: Confirmed Bug description: Fresh install of Ubuntu 18.04 (Linux kernel 4.18.0-17-generic #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:12 UTC 2019). Network adapter does not resume after suspend. Wifi not available. References to a fix for r8169 driver found. Tried the following fixes: 1. sudo service network-manager restart. This did not work. 2. Script in /lib/systemd/system-sleep/r8169-refresh as described in https://askubuntu.com/questions/1029250/ubuntu-18-04-ethernet-disconnected-after-suspend This did not work. 3. Updated kernel to 4.20.17. This did not work. There is reference to r8169 fixes in version 4.21, but this is not available on the ubuntu mainline kernels https://kernel.ubuntu.com/~kernel-ppa/mainline/ Possibly related to bug #1752772 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-04-08 (2 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: linux (not installed) Tags: bionic Uname: Linux 4.20.17-042017-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824038/+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 1824038] Re: Network adapter doesn't work after returning from suspend
** Attachment added: "Syslog resume (modprobe fail).png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824038/+attachment/5254562/+files/Syslog%20resume%20%28modprobe%20fail%29.png -- 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/1824038 Title: Network adapter doesn't work after returning from suspend Status in linux package in Ubuntu: Incomplete Bug description: Fresh install of Ubuntu 18.04 (Linux kernel 4.18.0-17-generic #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:12 UTC 2019). Network adapter does not resume after suspend. Wifi not available. References to a fix for r8169 driver found. Tried the following fixes: 1. sudo service network-manager restart. This did not work. 2. Script in /lib/systemd/system-sleep/r8169-refresh as described in https://askubuntu.com/questions/1029250/ubuntu-18-04-ethernet-disconnected-after-suspend This did not work. 3. Updated kernel to 4.20.17. This did not work. There is reference to r8169 fixes in version 4.21, but this is not available on the ubuntu mainline kernels https://kernel.ubuntu.com/~kernel-ppa/mainline/ Possibly related to bug #1752772 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824038/+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 1824038] Re: Network adapter doesn't work after returning from suspend
** Attachment added: "lsb_release.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824038/+attachment/5254559/+files/lsb_release.log -- 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/1824038 Title: Network adapter doesn't work after returning from suspend Status in linux package in Ubuntu: New Bug description: Fresh install of Ubuntu 18.04 (Linux kernel 4.18.0-17-generic #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:12 UTC 2019). Network adapter does not resume after suspend. Wifi not available. References to a fix for r8169 driver found. Tried the following fixes: 1. sudo service network-manager restart. This did not work. 2. Script in /lib/systemd/system-sleep/r8169-refresh as described in https://askubuntu.com/questions/1029250/ubuntu-18-04-ethernet-disconnected-after-suspend This did not work. 3. Updated kernel to 4.20.17. This did not work. There is reference to r8169 fixes in version 4.21, but this is not available on the ubuntu mainline kernels https://kernel.ubuntu.com/~kernel-ppa/mainline/ Possibly related to bug #1752772 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824038/+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 1824038] Re: Network adapter doesn't work after returning from suspend
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824038/+attachment/5254560/+files/lspci-vnvn.log -- 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/1824038 Title: Network adapter doesn't work after returning from suspend Status in linux package in Ubuntu: New Bug description: Fresh install of Ubuntu 18.04 (Linux kernel 4.18.0-17-generic #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:12 UTC 2019). Network adapter does not resume after suspend. Wifi not available. References to a fix for r8169 driver found. Tried the following fixes: 1. sudo service network-manager restart. This did not work. 2. Script in /lib/systemd/system-sleep/r8169-refresh as described in https://askubuntu.com/questions/1029250/ubuntu-18-04-ethernet-disconnected-after-suspend This did not work. 3. Updated kernel to 4.20.17. This did not work. There is reference to r8169 fixes in version 4.21, but this is not available on the ubuntu mainline kernels https://kernel.ubuntu.com/~kernel-ppa/mainline/ Possibly related to bug #1752772 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824038/+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 1824038] Re: Network adapter doesn't work after returning from suspend
** Attachment added: "uname.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824038/+attachment/5254561/+files/uname.log -- 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/1824038 Title: Network adapter doesn't work after returning from suspend Status in linux package in Ubuntu: New Bug description: Fresh install of Ubuntu 18.04 (Linux kernel 4.18.0-17-generic #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:12 UTC 2019). Network adapter does not resume after suspend. Wifi not available. References to a fix for r8169 driver found. Tried the following fixes: 1. sudo service network-manager restart. This did not work. 2. Script in /lib/systemd/system-sleep/r8169-refresh as described in https://askubuntu.com/questions/1029250/ubuntu-18-04-ethernet-disconnected-after-suspend This did not work. 3. Updated kernel to 4.20.17. This did not work. There is reference to r8169 fixes in version 4.21, but this is not available on the ubuntu mainline kernels https://kernel.ubuntu.com/~kernel-ppa/mainline/ Possibly related to bug #1752772 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824038/+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 1824038] [NEW] Network adapter doesn't work after returning from suspend
Public bug reported: Fresh install of Ubuntu 18.04 (Linux kernel 4.18.0-17-generic #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:12 UTC 2019). Network adapter does not resume after suspend. Wifi not available. References to a fix for r8169 driver found. Tried the following fixes: 1. sudo service network-manager restart. This did not work. 2. Script in /lib/systemd/system-sleep/r8169-refresh as described in https://askubuntu.com/questions/1029250/ubuntu-18-04-ethernet-disconnected-after-suspend This did not work. 3. Updated kernel to 4.20.17. This did not work. There is reference to r8169 fixes in version 4.21, but this is not available on the ubuntu mainline kernels https://kernel.ubuntu.com/~kernel-ppa/mainline/ Possibly related to bug #1752772 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "lshw.log" https://bugs.launchpad.net/bugs/1824038/+attachment/5254558/+files/lshw.log -- 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/1824038 Title: Network adapter doesn't work after returning from suspend Status in linux package in Ubuntu: New Bug description: Fresh install of Ubuntu 18.04 (Linux kernel 4.18.0-17-generic #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:12 UTC 2019). Network adapter does not resume after suspend. Wifi not available. References to a fix for r8169 driver found. Tried the following fixes: 1. sudo service network-manager restart. This did not work. 2. Script in /lib/systemd/system-sleep/r8169-refresh as described in https://askubuntu.com/questions/1029250/ubuntu-18-04-ethernet-disconnected-after-suspend This did not work. 3. Updated kernel to 4.20.17. This did not work. There is reference to r8169 fixes in version 4.21, but this is not available on the ubuntu mainline kernels https://kernel.ubuntu.com/~kernel-ppa/mainline/ Possibly related to bug #1752772 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824038/+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 1752772] Re: r8169 ethernet card don't work after returning from suspension
Is this issue fixed in 4.18.0-17-generic #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:12 UTC 2019? I have just done a fresh install. Modprobe workaround doesn't seem to work. Happy to provide any information required. gordon:~$ sudo lshw -C network *-network description: Wireless interface product: Wireless 7260 vendor: Intel Corporation physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 73 serial: 0c:8b:fd:48:fe:40 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.18.0-17-generic firmware=17.948900127.0 ip=192.168.69.113 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:46 memory:e350-e3501fff *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0.1 bus info: pci@:03:00.1 logical name: enp3s0f1 version: 12 serial: 78:45:c4:c9:4e:61 size: 10Mbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl8411-2_0.0.1 07/08/13 latency=0 link=no multicast=yes port=MII speed=10Mbit/s resources: irq:19 ioport:4000(size=256) memory:e3404000-e3404fff memory:e340-e3403fff -- 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/1752772 Title: r8169 ethernet card don't work after returning from suspension Status in Linux: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: ===SRU Justification=== [Impact] Ethernet r8169 stops working after system resumed from suspend. [Test] User confirmed these patches fix the issue. r8169 continues to work after resume from suspend. [Regression Potential] Medium. The fix is limited to one device, all patches are in mainline. The WOL default change might cause regression for users that depend on BIOS settings. We can advice them to use userspace tool (systemd, ethtool, etc.) instead. ===Original Bug Report=== I have noticed that the network stopped working on my desktop after I've suspended the system and woke it up. On dmesg there are messages like: [ 150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready [ 150.944101] do_IRQ: 3.37 No irq handler for vector [ 150.944105] r8169 :01:00.0 enp1s0: link down [ 150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready When using Xenial (from a different install), this problem is not happening. This is happening on Bionic. There are only two ways to restore connectivity: 1) Reboot the system; 2) Remove the r8169 module and reinsert it with modprobe. The motherboard is a AsRock H55M-LE and the Ethernet controller is: 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.172 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Mar 2 00:21:57 2018 Dependencies: InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-10-generic. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1153 F pulseaudio /dev/snd/controlC1: usuario1153 F pulseaudio Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26' Mixer name : 'VIA VT1818S' Components : 'HDA:11060440,18492818,0010' Controls : 40 Simple ctrls : 17 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 7 Simple ctrls : 1 Card1.Amixer.values: Simple
[Kernel-packages] [Bug 1283938] Re: [Samsung NP535U4X-S01TH] Ubuntu 14.04 blank screen after wakeup from sleep
The solution in message #6 of the thread below solved this issue for me. http://ubuntuforums.org/showthread.php?t=1978290 -- 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/1283938 Title: [Samsung NP535U4X-S01TH] Ubuntu 14.04 blank screen after wakeup from sleep Status in “linux” package in Ubuntu: Incomplete Bug description: In 14.04 after wakeup from suspend, the notebook screen goes blank while the OS and the hardware is awake (I can also press Ctrl+F1 and Ctrl+Alt+Del to reboot the system). Changeing quiet splash to nomodeset in /etc/default/grub allows the wakeup, but the pc is really slow (can't be used). WORKAROUND: This problem is not happening with the AMD property drivers. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Feb 24 12:58:07 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7500G] [1002:990a] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c660] Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] [1002:6841] (rev ff) (prog-if ff) InstallationDate: Installed on 2014-02-22 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140218) MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U4C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic root=UUID=9f8c7e92-a6ea-41fd-9489-a256c8b9f5d5 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P06RAF.N93.130403.LEO dmi.board.asset.tag: No Asset Tag dmi.board.name: NP535U4X-S01TH dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP06RAF.N93.130403.LEO:bd04/03/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn535U4C:pvrP06RAF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP535U4X-S01TH:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 535U4C dmi.product.version: P06RAF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Feb 24 12:54:54 2014 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu6 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283938/+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 1322407] Re: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly
I confirm also that the proposed kernel changes #56 fixes this issue. Problem still occurs with #55. See attached package versions which work. Sorry, took me ages to work out how to install proposed kernel changes to test this. :-) ** Attachment added: Unbutu Server 14.04 Linux Package versions https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322407/+attachment/4151505/+files/Screenshot%20from%202014-07-13%2012%3A38%3A14.png -- 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/1322407 Title: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Bug description: This concerns the server edition of 14.04. I have set up a NFS server. Once I attach at least one client, one kworker process starts to use 100% CPU. The runaway kworker returns to idle when I reset the NFS server daemon with service nfs-kernel-server stop followed by service nfs-kernel-server start. With the nfs kernel server stopped, the CPU remains idle. With the nfs kernel server running, as soon as one client requests a connection, the kworker process jumps to 100% CPU again. After some random time, the nfs kernel server no longer accepts requests from clients. Restarting the service allows clients to reconnect. The syslog shows no relevant information. This problem has never appeared on a very similar server setup with 12.04. Configration: The svcgssd is not running. I played with various configurations (enabling/disabling NFSv3 and NFSv4), but it makes no difference. I tried to enable event debugging: # echo workqueue:workqueue_queue_work /sys/kernel/debug/tracing/set_event # cat /sys/kernel/debug/tracing/trace_pipe /var/tmp/kerntrace.txt and found the following kernel trace in a tight loop: [...] kworker/2:1-86[002] d... 161940.910668: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910674: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910675: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910681: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910682: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910688: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910689: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910695: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910696: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910702: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 [...] At present, I have to consider NFS fubar. Thanks, Mark ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-24-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Date: Thu May 22 22:48:48 2014 HibernationDevice: RESUME=UUID=adcdeef5-9b46-4ea4-b9f4-b6e642ea91e8
[Kernel-packages] [Bug 1322407] Re: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly
I appear to still having this issue, despite the fix being release. 3.13.0-29-generic Happy to provide more details. -- 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/1322407 Title: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: In Progress Bug description: This concerns the server edition of 14.04. I have set up a NFS server. Once I attach at least one client, one kworker process starts to use 100% CPU. The runaway kworker returns to idle when I reset the NFS server daemon with service nfs-kernel-server stop followed by service nfs-kernel-server start. With the nfs kernel server stopped, the CPU remains idle. With the nfs kernel server running, as soon as one client requests a connection, the kworker process jumps to 100% CPU again. After some random time, the nfs kernel server no longer accepts requests from clients. Restarting the service allows clients to reconnect. The syslog shows no relevant information. This problem has never appeared on a very similar server setup with 12.04. Configration: The svcgssd is not running. I played with various configurations (enabling/disabling NFSv3 and NFSv4), but it makes no difference. I tried to enable event debugging: # echo workqueue:workqueue_queue_work /sys/kernel/debug/tracing/set_event # cat /sys/kernel/debug/tracing/trace_pipe /var/tmp/kerntrace.txt and found the following kernel trace in a tight loop: [...] kworker/2:1-86[002] d... 161940.910668: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910674: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910675: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910681: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910682: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910688: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910689: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910695: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910696: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910702: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 [...] At present, I have to consider NFS fubar. Thanks, Mark ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-24-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Date: Thu May 22 22:48:48 2014 HibernationDevice: RESUME=UUID=adcdeef5-9b46-4ea4-b9f4-b6e642ea91e8 InstallationDate: Installed on 2014-05-12 (10 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3 ProcEnviron: TERM=xterm
[Kernel-packages] [Bug 1322407] Re: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly
Problem exists on 3.13.0-29-generic. Clean 14.04 server install. Export of root sub folder. NFSv4. Client 12.04 mount. Kworker 100% every time the folder is accessed. Testing on a single server and single client. -- 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/1322407 Title: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: In Progress Bug description: This concerns the server edition of 14.04. I have set up a NFS server. Once I attach at least one client, one kworker process starts to use 100% CPU. The runaway kworker returns to idle when I reset the NFS server daemon with service nfs-kernel-server stop followed by service nfs-kernel-server start. With the nfs kernel server stopped, the CPU remains idle. With the nfs kernel server running, as soon as one client requests a connection, the kworker process jumps to 100% CPU again. After some random time, the nfs kernel server no longer accepts requests from clients. Restarting the service allows clients to reconnect. The syslog shows no relevant information. This problem has never appeared on a very similar server setup with 12.04. Configration: The svcgssd is not running. I played with various configurations (enabling/disabling NFSv3 and NFSv4), but it makes no difference. I tried to enable event debugging: # echo workqueue:workqueue_queue_work /sys/kernel/debug/tracing/set_event # cat /sys/kernel/debug/tracing/trace_pipe /var/tmp/kerntrace.txt and found the following kernel trace in a tight loop: [...] kworker/2:1-86[002] d... 161940.910668: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910674: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910675: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910681: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910682: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910688: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910689: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910695: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910696: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910702: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 [...] At present, I have to consider NFS fubar. Thanks, Mark ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-24-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Date: Thu May 22 22:48:48 2014 HibernationDevice: RESUME=UUID=adcdeef5-9b46-4ea4-b9f4-b6e642ea91e8 InstallationDate: Installed on 2014-05-12 (10 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) IwConfig: eth0 no wireless extensions. lono wireless extensions.
[Kernel-packages] [Bug 1322406] Re: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly
*** This bug is a duplicate of bug 1322407 *** https://bugs.launchpad.net/bugs/1322407 Problem exists on 3.13.0-29-generic. Clean 14.04 server install. Export of root sub folder. NFSv4. Client 12.04 mount. Kworker 100% every time the folder is accessed. Testing on a single server and single client. -- 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/1322406 Title: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly Status in “linux” package in Ubuntu: Confirmed Bug description: This concerns the server edition of 14.04. I have set up a NFS server. Once I attach at least one client, one kworker process starts to use 100% CPU. The runaway kworker returns to idle when I reset the NFS server daemon with service nfs-kernel-server stop followed by service nfs-kernel-server start. With the nfs kernel server stopped, the CPU remains idle. With the nfs kernel server running, as soon as one client requests a connection, the kworker process jumps to 100% CPU again. After some random time, the nfs kernel server no longer accepts requests from clients. Restarting the service allows clients to reconnect. The syslog shows no relevant information. Configration: The svcgssd is not running. I played with various configurations (enabling/disabling NFSv3 and NFSv4), but it makes no difference. I tried to nable event debugging: # echo workqueue:workqueue_queue_work /sys/kernel/debug/tracing/set_event # cat /sys/kernel/debug/tracing/trace_pipe /var/tmp/kerntrace.txt and found the following kernel trace in a tight loop: [...] kworker/2:1-86[002] d... 161940.910668: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910674: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910675: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910681: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910682: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910688: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910689: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910695: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910696: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910702: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 [...] At present, I have to consider NFS fubar. Thanks, Mark ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-24-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Date: Thu May 22 22:48:48 2014 HibernationDevice: RESUME=UUID=adcdeef5-9b46-4ea4-b9f4-b6e642ea91e8 InstallationDate: Installed on 2014-05-12 (10 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd.
[Kernel-packages] [Bug 1318116] Re: kworker uses 100% CPU when nfs-kernel-server is active
*** This bug is a duplicate of bug 1322407 *** https://bugs.launchpad.net/bugs/1322407 ** This bug has been marked a duplicate of bug 1322407 NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly -- 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/1318116 Title: kworker uses 100% CPU when nfs-kernel-server is active Status in “linux” package in Ubuntu: Triaged Bug description: I have a clean install of 14.04 on an i7-860 with 16GB RAM. I'm using NFS to share a home directory. The volume is ~2TB, formatted JFS, and it has a single client. I recently noticed that I had a [kworker] process using 100% CPU: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 9253 root 20 0 0 0 0 R 99.9 0.0 0:30.17 [kworker/3:1] Rebooting didn't help. After some troubleshooting I found that it went away immediately when I stopped the nfs-kernel-server daemon. When I start it, it comes back after a minute or two, still using 99-100% CPU. The load goes away when the client is turned off and the NFS server is restarted, but it comes back as soon as it reconnects. The only line in /etc/exports is: /home 192.168.1.0/24(rw,sync,no_root_squash) version_signature: Ubuntu 3.13.0-24.47-generic 3.13.9 # dpkg -l nfs-kernel-server Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---== ii nfs-kernel-ser 1:1.2.8-6ubu amd64support for NFS kernel server Description:Ubuntu 14.04 LTS Release:14.04 I don't think this is related to my hardware but I can provide lspci output if necessary. --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: username 4414 F pulseaudio username 4778 F pulseaudio /dev/snd/controlC0: username 4414 F pulseaudio username 4778 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=de6e2d52-86c9-4867-8d37-31964953e1e6 InstallationDate: Installed on 2014-05-01 (9 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P55A-UD4P NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/hostname-newestroot ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 RfKill: Tags: trusty Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/16/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F3 dmi.board.name: P55A-UD4P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd10/16/2009:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD4P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD4P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P55A-UD4P dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318116/+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 1322407] Re: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly
FIX CONFIRMED. I can confirm that Stefan's fix in #18 resolves my issue, and is unrelated to Trados. Many thanks Stefan. -- 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/1322407 Title: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: In Progress Bug description: This concerns the server edition of 14.04. I have set up a NFS server. Once I attach at least one client, one kworker process starts to use 100% CPU. The runaway kworker returns to idle when I reset the NFS server daemon with service nfs-kernel-server stop followed by service nfs-kernel-server start. With the nfs kernel server stopped, the CPU remains idle. With the nfs kernel server running, as soon as one client requests a connection, the kworker process jumps to 100% CPU again. After some random time, the nfs kernel server no longer accepts requests from clients. Restarting the service allows clients to reconnect. The syslog shows no relevant information. This problem has never appeared on a very similar server setup with 12.04. Configration: The svcgssd is not running. I played with various configurations (enabling/disabling NFSv3 and NFSv4), but it makes no difference. I tried to enable event debugging: # echo workqueue:workqueue_queue_work /sys/kernel/debug/tracing/set_event # cat /sys/kernel/debug/tracing/trace_pipe /var/tmp/kerntrace.txt and found the following kernel trace in a tight loop: [...] kworker/2:1-86[002] d... 161940.910668: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910674: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910675: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910681: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910682: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910688: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910689: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910695: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d... 161940.910696: workqueue_queue_work: work struct=8804140675e0 function=xs_tcp_setup_socket [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 kworker/2:1-86[002] d.s. 161940.910702: workqueue_queue_work: work struct=8800cef9f488 function=rpc_async_schedule [sunrpc] workqueue=8800cfbb6a00 req_cpu=256 cpu=2 [...] At present, I have to consider NFS fubar. Thanks, Mark ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-24-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Date: Thu May 22 22:48:48 2014 HibernationDevice: RESUME=UUID=adcdeef5-9b46-4ea4-b9f4-b6e642ea91e8 InstallationDate: Installed on 2014-05-12 (10 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3 ProcEnviron: TERM=xterm
