[Kernel-packages] [Bug 2042301] Re: Windows are slow to open shortly after login under X11 session
** Description changed: On Ubuntu 23.10 after I install the Nvidia driver v535 I get noticeable latency of about 10-15 seconds after I click on any application, be it Nautilus, Terminal, Firefox. The problem lasts for about one minute. More precise steps: 1. Install Nvidia drivers (using sudo ubuntu-drivers install) 2. Reboot 3. Login to X11 session (which becomes the default when Nvidia drivers are installed) 4. Quickly open Nautilus, Firefox and Terminal by clicking on their icons 5. The mouse cursor turns to circle. After 10-15 seconds, some window will appear After about one minute opening any of these apps will open immediately, as expected. If I logout and login to Wayland the issue is not present. If I logout and login into X11 the issue can be reproduced, so it is not related to boot but to login. If I uninstall nvidia drivers the issue is gone. It might be an issue with mutter or gnome-shell. $ apt list nvidia-driver-535 mutter gnome-shell Listing... Done gnome-shell/mantic,now 45.0-1ubuntu2 amd64 [installed,automatic] mutter/mantic,now 45.0-3ubuntu3 amd64 [installed,automatic] nvidia-driver-535/mantic,now 535.113.01-0ubuntu3 amd64 [installed] The following might be related. If I open the GUI app Logs I see the following error: Failed to start xdg-desktop-portal.service - Portal service. If I write the following command: $ journalctl --user --unit=xdg-desktop-portal I get: Oct 31 18:19:20 my-pc-hostname systemd[39536]: Starting xdg-desktop-portal.service - Portal service... - Oct 31 18:20:10 my-pc-hostname xdg-desktop-por[44027]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was r> - Oct 31 18:20:35 my-pc-hostname xdg-desktop-por[44027]: Failed to create file chooser proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout w> + Oct 31 18:20:10 lenovo-legion-5 xdg-desktop-por[44027]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached + Oct 31 18:20:35 lenovo-legion-5 xdg-desktop-por[44027]: Failed to create file chooser proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached Oct 31 18:20:35 my-pc-hostname xdg-desktop-por[44027]: No skeleton to export Oct 31 18:20:50 my-pc-hostname systemd[39536]: xdg-desktop-portal.service: start operation timed out. Terminating. Oct 31 18:20:50 my-pc-hostname systemd[39536]: xdg-desktop-portal.service: Failed with result 'timeout'. Oct 31 18:20:50 my-pc-hostname systemd[39536]: Failed to start xdg-desktop-portal.service - Portal service. Oct 31 18:21:21 my-pc-hostname systemd[39536]: Starting xdg-desktop-portal.service - Portal service... Oct 31 18:21:21 my-pc-hostname systemd[39536]: Started xdg-desktop-portal.service - Portal service. Oct 31 18:23:46 my-pc-hostname systemd[39536]: Stopping xdg-desktop-portal.service - Portal service... Oct 31 18:23:46 my-pc-hostname systemd[39536]: Stopped xdg-desktop-portal.service - Portal service. So during one login and logout the service fails to start at first, but succeeds to start later. ** Description changed: On Ubuntu 23.10 after I install the Nvidia driver v535 I get noticeable latency of about 10-15 seconds after I click on any application, be it Nautilus, Terminal, Firefox. The problem lasts for about one minute. More precise steps: 1. Install Nvidia drivers (using sudo ubuntu-drivers install) 2. Reboot 3. Login to X11 session (which becomes the default when Nvidia drivers are installed) 4. Quickly open Nautilus, Firefox and Terminal by clicking on their icons 5. The mouse cursor turns to circle. After 10-15 seconds, some window will appear After about one minute opening any of these apps will open immediately, as expected. If I logout and login to Wayland the issue is not present. If I logout and login into X11 the issue can be reproduced, so it is not related to boot but to login. If I uninstall nvidia drivers the issue is gone. It might be an issue with mutter or gnome-shell. $ apt list nvidia-driver-535 mutter gnome-shell Listing... Done gnome-shell/mantic,now 45.0-1ubuntu2 amd64 [installed,automatic] mutter/mantic,now 45.0-3ubuntu3 amd64 [installed,automatic] nvidia-driver-535/mantic,now 535.113.01-0ubuntu3 amd64 [installed] The following might be related. If I open the GUI app Logs I see the following error: Failed to start xdg-desktop-portal.service - Portal service. If I write the following command: $ journalctl --user --unit=xdg-desktop-portal I get: Oct 31 18:19:20 my-pc-hostname systemd[39536]: Starting xdg-desktop-portal.service - Portal service... - Oct 31 18:20:10 lenovo-legion-5 xdg-desktop-por[44027]: Failed to create settings proxy: Error calling
[Kernel-packages] [Bug 2042301] Re: Windows are slow to open shortly after login under X11 session
** Also affects: xdg-desktop-portal (Ubuntu) Importance: Undecided Status: New ** Description changed: On Ubuntu 23.10 after I install the Nvidia driver v535 I get noticeable latency of about 10-15 seconds after I click on any application, be it Nautilus, Terminal, Firefox. The problem lasts for about one minute. More precise steps: 1. Install Nvidia drivers (using sudo ubuntu-drivers install) 2. Reboot 3. Login to X11 session (which becomes the default when Nvidia drivers are installed) 4. Quickly open Nautilus, Firefox and Terminal by clicking on their icons 5. The mouse cursor turns to circle. After 10-15 seconds, some window will appear After about one minute opening any of these apps will open immediately, as expected. If I logout and login to Wayland the issue is not present. If I logout and login into X11 the issue can be reproduced, so it is not related to boot but to login. If I uninstall nvidia drivers the issue is gone. It might be an issue with mutter or gnome-shell. $ apt list nvidia-driver-535 mutter gnome-shell Listing... Done gnome-shell/mantic,now 45.0-1ubuntu2 amd64 [installed,automatic] mutter/mantic,now 45.0-3ubuntu3 amd64 [installed,automatic] nvidia-driver-535/mantic,now 535.113.01-0ubuntu3 amd64 [installed] The following might be related. If I open the GUI app Logs I see the following error: Failed to start xdg-desktop-portal.service - Portal service. If I write the following command: $ journalctl --user --unit=xdg-desktop-portal I get: Oct 31 18:19:20 my-pc-hostname systemd[39536]: Starting xdg-desktop-portal.service - Portal service... Oct 31 18:20:10 my-pc-hostname xdg-desktop-por[44027]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was r> Oct 31 18:20:35 my-pc-hostname xdg-desktop-por[44027]: Failed to create file chooser proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout w> Oct 31 18:20:35 my-pc-hostname xdg-desktop-por[44027]: No skeleton to export Oct 31 18:20:50 my-pc-hostname systemd[39536]: xdg-desktop-portal.service: start operation timed out. Terminating. Oct 31 18:20:50 my-pc-hostname systemd[39536]: xdg-desktop-portal.service: Failed with result 'timeout'. Oct 31 18:20:50 my-pc-hostname systemd[39536]: Failed to start xdg-desktop-portal.service - Portal service. Oct 31 18:21:21 my-pc-hostname systemd[39536]: Starting xdg-desktop-portal.service - Portal service... Oct 31 18:21:21 my-pc-hostname systemd[39536]: Started xdg-desktop-portal.service - Portal service. Oct 31 18:23:46 my-pc-hostname systemd[39536]: Stopping xdg-desktop-portal.service - Portal service... Oct 31 18:23:46 my-pc-hostname systemd[39536]: Stopped xdg-desktop-portal.service - Portal service. So during one login and logout the service fails to start at first, but - succeeds to tart later. + succeeds to start later. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2042301 Title: Windows are slow to open shortly after login under X11 session Status in nvidia-graphics-drivers-535 package in Ubuntu: New Status in xdg-desktop-portal package in Ubuntu: New Bug description: On Ubuntu 23.10 after I install the Nvidia driver v535 I get noticeable latency of about 10-15 seconds after I click on any application, be it Nautilus, Terminal, Firefox. The problem lasts for about one minute. More precise steps: 1. Install Nvidia drivers (using sudo ubuntu-drivers install) 2. Reboot 3. Login to X11 session (which becomes the default when Nvidia drivers are installed) 4. Quickly open Nautilus, Firefox and Terminal by clicking on their icons 5. The mouse cursor turns to circle. After 10-15 seconds, some window will appear After about one minute opening any of these apps will open immediately, as expected. If I logout and login to Wayland the issue is not present. If I logout and login into X11 the issue can be reproduced, so it is not related to boot but to login. If I uninstall nvidia drivers the issue is gone. It might be an issue with mutter or gnome-shell. $ apt list nvidia-driver-535 mutter gnome-shell Listing... Done gnome-shell/mantic,now 45.0-1ubuntu2 amd64 [installed,automatic] mutter/mantic,now 45.0-3ubuntu3 amd64 [installed,automatic] nvidia-driver-535/mantic,now 535.113.01-0ubuntu3 amd64 [installed] The following might be related. If I open the GUI app Logs I see the following error: Failed to start xdg-desktop-portal.service - Portal service. If I write the following command: $ journalctl --user --unit=xdg-desktop-portal I get: Oct 31 18:19:20 my-pc-hostname systemd[39536]: Starting xdg-desktop-portal.service - Portal service... Oct 31 18:20:10 my-pc-hostname
[Kernel-packages] [Bug 2042301] [NEW] Windows are slow to open shortly after login under X11 session
Public bug reported: On Ubuntu 23.10 after I install the Nvidia driver v535 I get noticeable latency of about 10-15 seconds after I click on any application, be it Nautilus, Terminal, Firefox. The problem lasts for about one minute. More precise steps: 1. Install Nvidia drivers (using sudo ubuntu-drivers install) 2. Reboot 3. Login to X11 session (which becomes the default when Nvidia drivers are installed) 4. Quickly open Nautilus, Firefox and Terminal by clicking on their icons 5. The mouse cursor turns to circle. After 10-15 seconds, some window will appear After about one minute opening any of these apps will open immediately, as expected. If I logout and login to Wayland the issue is not present. If I logout and login into X11 the issue can be reproduced, so it is not related to boot but to login. If I uninstall nvidia drivers the issue is gone. It might be an issue with mutter or gnome-shell. $ apt list nvidia-driver-535 mutter gnome-shell Listing... Done gnome-shell/mantic,now 45.0-1ubuntu2 amd64 [installed,automatic] mutter/mantic,now 45.0-3ubuntu3 amd64 [installed,automatic] nvidia-driver-535/mantic,now 535.113.01-0ubuntu3 amd64 [installed] ** Affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2042301 Title: Windows are slow to open shortly after login under X11 session Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: On Ubuntu 23.10 after I install the Nvidia driver v535 I get noticeable latency of about 10-15 seconds after I click on any application, be it Nautilus, Terminal, Firefox. The problem lasts for about one minute. More precise steps: 1. Install Nvidia drivers (using sudo ubuntu-drivers install) 2. Reboot 3. Login to X11 session (which becomes the default when Nvidia drivers are installed) 4. Quickly open Nautilus, Firefox and Terminal by clicking on their icons 5. The mouse cursor turns to circle. After 10-15 seconds, some window will appear After about one minute opening any of these apps will open immediately, as expected. If I logout and login to Wayland the issue is not present. If I logout and login into X11 the issue can be reproduced, so it is not related to boot but to login. If I uninstall nvidia drivers the issue is gone. It might be an issue with mutter or gnome-shell. $ apt list nvidia-driver-535 mutter gnome-shell Listing... Done gnome-shell/mantic,now 45.0-1ubuntu2 amd64 [installed,automatic] mutter/mantic,now 45.0-3ubuntu3 amd64 [installed,automatic] nvidia-driver-535/mantic,now 535.113.01-0ubuntu3 amd64 [installed] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2042301/+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 1779827] Re: failure to boot with linux-image-4.15.0-24-generic
I am also affected by this, and it is most likely the issue with entropy for randomness, because if I mash some random keys, I get to boot. -- 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/1779827 Title: failure to boot with linux-image-4.15.0-24-generic Status in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in The Bionic Beaver: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: This was the last OK then my 18.04 hangs after an update this morning. 07:00 AM CEST Last Ok in boot was Started gnome display manager. dispatcher service .. tem changes.pp link was shut down Tried install lightdm from command line and the response was lastest already installed. Probably it is what is coming after the lastest OK which is to be the error. And here I have lots of guesses.. Any Ideas ? I need to do some work and I may not be waiting long. Search and browsed and now close to give up. Yeah it is a Lenovo. Guys: turn of auto update it is a machine killer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1779827/+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 1779476] Re: Ubuntu 18.04: gdm3 does not switch to graphics after update
I think I got hit by this bug too after the kernel update to 4.15.0-24-generic. Found this on askubuntu https://askubuntu.com/questions/1051555/after-security-update- to-4-15-0-24-generic-26-ubuntu-screen-shows-log-content which solves the problem. Switcing to another tty and then switching to lightdm solved. -- 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/1779476 Title: Ubuntu 18.04: gdm3 does not switch to graphics after update Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: After update of gdm and kernel gdm3 no longer enables graphics. What happens: = With and without: WaylandEnable=false in /etc/gdm3/custom.conf gdm3 does not switch to graphics. In both cases I case the X process running (Xwayland or Xorg) but no vt has it. lightdm does work, but barely. It takes up to a minute to get to the login screen. What I expected to happen: == gdm3 switching to graphics in ~20 after boot like pre-update. Release: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ apt-cache policy kernel-common gdm3 lightdm xorg xwayland kernel-common: Installed: (none) Candidate: 13.018+nmu1 Version table: 13.018+nmu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic/universe i386 Packages gdm3: Installed: 3.28.2-0ubuntu1.3 Candidate: 3.28.2-0ubuntu1.3 Version table: *** 3.28.2-0ubuntu1.3 500 500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.28.2-0ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 3.28.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status xorg: Installed: 1:7.7+19ubuntu7 Candidate: 1:7.7+19ubuntu7 Version table: *** 1:7.7+19ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status xwayland: Installed: 2:1.19.6-1ubuntu4 Candidate: 2:1.19.6-1ubuntu4 Version table: *** 2:1.19.6-1ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Attaching journalctl -b. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-27 (673 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) NonfreeKernelModules: wl Package: gdm3 3.28.2-0ubuntu1.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Tags: bionic package-from-proposed Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-27 (674 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) NonfreeKernelModules: wl Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Tags: bionic package-from-proposed Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.gdm3.custom.conf: [modified] mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1779476/+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 1645631] Re: Sending files fails because obex not loaded
Happens in Zesty too. Updated from previous distribution versions 16.04->16.10->17.04. Manually starting the service fixes the problem until reboot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1645631 Title: Sending files fails because obex not loaded Status in bluez package in Ubuntu: Confirmed Status in gnome-bluetooth package in Ubuntu: Confirmed Bug description: If I run bluetooth-sendto from command line and try to send the file, it quits after selecting the target device with following command line output: "Acquiring proxy failed: Error calling StartServiceByName for org.bluez.obex: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.obex.service not found." After I run "systemctl --user start obex", it proceeds to send the file. Even then it for some reason gets stuck, but I do not know what causes it and it is probably a different problem. This system is upgraded from xenial. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-bluetooth 3.20.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Tue Nov 29 11:04:11 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-12 (77 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=fi TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to yakkety on 2016-11-01 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1645631/+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 1626436] Re: [4.8 regression] boot has become very slow
I booted to 4.8 again and saw the dmesg. This is the error: [3.375735] ... [ 12.768084] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:26:pipe A] flip_done timed out Apparently it is a known problem https://bbs.archlinux.org/viewtopic.php?id=218581 related to the Intel video driver in 4.8. -- 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/1626436 Title: [4.8 regression] boot has become very slow Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: With yakkety's recent update from linux 4.4 to 4.8 booting has become a lot slower. It's not one service in particular, but without "quiet" and "splash" you can now easily read every single line instead of that whole wall of text zipping by. It now takes over 20s instead of ~10 seconds to boot. This is even more dramatic when factoring out the recent boot hang of NetworkManager (bug 1622893) and disabling lightdm: sudo systemctl mask NetworkManager NetworkManager-wait-online lightdm then booting with 4.4 takes 1.5s and with 4.8 19.5s (!). Some excerps from systemd-analyze blame: 4.4: 474ms postfix@-.service 395ms lxd-containers.service 305ms networking.service 4.8: 4.578s postfix@-.service 7.300s lxd-containers.service 6.285s networking.service I attach the full outputs of critical-chain and analyze for 4.4 and 4.8 for reference. This is much less noticeable in the running system. There is no immediate feeling of sluggishness (although my system is by and large idle). I compared the time of sbuilding colord under similar circumstances (-j4, building on tmpfs, thus no hard disk delays; running with fully pre-loaded apt-cacher-ng thus no random network delays), and with 4.4 it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit slower, but much less dramatically than during boot, so this is either happening when a lot of processes run in parallel, or is perhaps related to setting up cgroups. One thing I noticed that during sbuild in 4.8 "top" shows ridiculous loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that doesn't reflect in actual sluggishness, so this might be just an unrelated bug. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-11-generic 4.8.0-11.12 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: martin 3049 F...m pulseaudio /dev/snd/pcmC0D0p: martin 3049 F...m pulseaudio /dev/snd/controlC0: martin 3049 F pulseaudio Date: Thu Sep 22 09:42:56 2016 EcryptfsInUse: Yes MachineType: LENOVO 2324CTO ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ systemd.debug-shell RelatedPackageVersions: linux-restricted-modules-4.8.0-11-generic N/A linux-backports-modules-4.8.0-11-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET95WW (2.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324CTO dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2324CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626436/+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 1626436] Re: [4.8 regression] boot has become very slow
For completeness, the latest mainline. 4.10.0rc6 Startup finished in 15.387s (kernel) + 25.344s (userspace) = 40.731s We can definitely conclude something happens between 4.7.10 and 4.8.0rc1. Detailed bisection should happen there. -- 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/1626436 Title: [4.8 regression] boot has become very slow Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: With yakkety's recent update from linux 4.4 to 4.8 booting has become a lot slower. It's not one service in particular, but without "quiet" and "splash" you can now easily read every single line instead of that whole wall of text zipping by. It now takes over 20s instead of ~10 seconds to boot. This is even more dramatic when factoring out the recent boot hang of NetworkManager (bug 1622893) and disabling lightdm: sudo systemctl mask NetworkManager NetworkManager-wait-online lightdm then booting with 4.4 takes 1.5s and with 4.8 19.5s (!). Some excerps from systemd-analyze blame: 4.4: 474ms postfix@-.service 395ms lxd-containers.service 305ms networking.service 4.8: 4.578s postfix@-.service 7.300s lxd-containers.service 6.285s networking.service I attach the full outputs of critical-chain and analyze for 4.4 and 4.8 for reference. This is much less noticeable in the running system. There is no immediate feeling of sluggishness (although my system is by and large idle). I compared the time of sbuilding colord under similar circumstances (-j4, building on tmpfs, thus no hard disk delays; running with fully pre-loaded apt-cacher-ng thus no random network delays), and with 4.4 it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit slower, but much less dramatically than during boot, so this is either happening when a lot of processes run in parallel, or is perhaps related to setting up cgroups. One thing I noticed that during sbuild in 4.8 "top" shows ridiculous loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that doesn't reflect in actual sluggishness, so this might be just an unrelated bug. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-11-generic 4.8.0-11.12 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: martin 3049 F...m pulseaudio /dev/snd/pcmC0D0p: martin 3049 F...m pulseaudio /dev/snd/controlC0: martin 3049 F pulseaudio Date: Thu Sep 22 09:42:56 2016 EcryptfsInUse: Yes MachineType: LENOVO 2324CTO ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ systemd.debug-shell RelatedPackageVersions: linux-restricted-modules-4.8.0-11-generic N/A linux-backports-modules-4.8.0-11-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET95WW (2.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324CTO dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2324CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626436/+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 1626436] Re: [4.8 regression] boot has become very slow
I decided to test with some of the mainline kernel images posted at http://kernel.ubuntu.com/~kernel-ppa/mainline/ 4.6.4 Startup finished in 4.991s (kernel) + 23.504s (userspace) = 28.496s 4.6.6 Startup finished in 5.019s (kernel) + 24.044s (userspace) = 29.064s 4.6.7 Startup finished in 5.063s (kernel) + 24.008s (userspace) = 29.072s 4.7.0rc1 Startup finished in 6.260s (kernel) + 24.199s (userspace) = 30.460s ^^ we see the first small jump here in 4.7rc1 4.7.0rc7 Startup finished in 6.800s (kernel) + 22.748s (userspace) = 29.548s 4.7.10 Startup finished in 5.718s (kernel) + 23.185s (userspace) = 28.904s Startup finished in 6.632s (kernel) + 22.865s (userspace) = 29.498s 4.8.0rc1 Startup finished in 17.619s (kernel) + 23.272s (userspace) = 40.892s Startup finished in 17.364s (kernel) + 29.914s (userspace) = 47.278s ^^ first large jump in 4.8rc1 4.8.0 Startup finished in 16.631s (kernel) + 23.861s (userspace) = 40.493s -- 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/1626436 Title: [4.8 regression] boot has become very slow Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: With yakkety's recent update from linux 4.4 to 4.8 booting has become a lot slower. It's not one service in particular, but without "quiet" and "splash" you can now easily read every single line instead of that whole wall of text zipping by. It now takes over 20s instead of ~10 seconds to boot. This is even more dramatic when factoring out the recent boot hang of NetworkManager (bug 1622893) and disabling lightdm: sudo systemctl mask NetworkManager NetworkManager-wait-online lightdm then booting with 4.4 takes 1.5s and with 4.8 19.5s (!). Some excerps from systemd-analyze blame: 4.4: 474ms postfix@-.service 395ms lxd-containers.service 305ms networking.service 4.8: 4.578s postfix@-.service 7.300s lxd-containers.service 6.285s networking.service I attach the full outputs of critical-chain and analyze for 4.4 and 4.8 for reference. This is much less noticeable in the running system. There is no immediate feeling of sluggishness (although my system is by and large idle). I compared the time of sbuilding colord under similar circumstances (-j4, building on tmpfs, thus no hard disk delays; running with fully pre-loaded apt-cacher-ng thus no random network delays), and with 4.4 it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit slower, but much less dramatically than during boot, so this is either happening when a lot of processes run in parallel, or is perhaps related to setting up cgroups. One thing I noticed that during sbuild in 4.8 "top" shows ridiculous loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that doesn't reflect in actual sluggishness, so this might be just an unrelated bug. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-11-generic 4.8.0-11.12 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: martin 3049 F...m pulseaudio /dev/snd/pcmC0D0p: martin 3049 F...m pulseaudio /dev/snd/controlC0: martin 3049 F pulseaudio Date: Thu Sep 22 09:42:56 2016 EcryptfsInUse: Yes MachineType: LENOVO 2324CTO ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ systemd.debug-shell RelatedPackageVersions: linux-restricted-modules-4.8.0-11-generic N/A linux-backports-modules-4.8.0-11-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET95WW (2.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324CTO dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2324CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to:
[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow
I had slow boot with 16.10 few months ago. I moved back to 16.04. Today I had time to test some of the kernels above from the bisection process. These are the results 4.4.0-59-generic# Ubuntu 16.04 official January 2017 Startup finished in 4.889s (kernel) + 28.001s (userspace) = 32.890s 4.6.0-040600-generic# from comment 29 ... actually from #34 Startup finished in 5.274s (kernel) + 23.561s (userspace) = 28.836s 4.6.0-040600-generic# comment 36 Startup finished in 5.111s (kernel) + 25.192s (userspace) = 30.304s 4.6.0-040600rc1-generic # comment 54 Startup finished in 4.979s (kernel) + 21.904s (userspace) = 26.883s 4.8.0-26-generic# official Ubuntu 16.10 at November 2016 Startup finished in 15.025s (kernel) + 35.067s (userspace) = 50.093s 4.8.0-29-generic# comment 61 Startup finished in 14.808s (kernel) + 32.516s (userspace) = 47.325s Startup finished in 15.674s (kernel) + 26.293s (userspace) = 41.967s 4.8.0-34-generic# Official 16.04 repo, apt install linux-generic-hwe-16.04-edge Startup finished in 15.717s (kernel) + 26.583s (userspace) = 42.301s Basically the two patches on my (old) laptop reduce the total boot from 50 to 40 something. Obviously there is another issue. On 4.8 kernels (with or without the two patches) I get a short freeze of 1-2 secs when I open a window of System Settings. I'd suggest we should continue the bisection that Joseph Salisbury started. We should continue after the kernel in comment 54 which is GOOD. -- 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/1626436 Title: [4.8 regression] boot has become very slow Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: With yakkety's recent update from linux 4.4 to 4.8 booting has become a lot slower. It's not one service in particular, but without "quiet" and "splash" you can now easily read every single line instead of that whole wall of text zipping by. It now takes over 20s instead of ~10 seconds to boot. This is even more dramatic when factoring out the recent boot hang of NetworkManager (bug 1622893) and disabling lightdm: sudo systemctl mask NetworkManager NetworkManager-wait-online lightdm then booting with 4.4 takes 1.5s and with 4.8 19.5s (!). Some excerps from systemd-analyze blame: 4.4: 474ms postfix@-.service 395ms lxd-containers.service 305ms networking.service 4.8: 4.578s postfix@-.service 7.300s lxd-containers.service 6.285s networking.service I attach the full outputs of critical-chain and analyze for 4.4 and 4.8 for reference. This is much less noticeable in the running system. There is no immediate feeling of sluggishness (although my system is by and large idle). I compared the time of sbuilding colord under similar circumstances (-j4, building on tmpfs, thus no hard disk delays; running with fully pre-loaded apt-cacher-ng thus no random network delays), and with 4.4 it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit slower, but much less dramatically than during boot, so this is either happening when a lot of processes run in parallel, or is perhaps related to setting up cgroups. One thing I noticed that during sbuild in 4.8 "top" shows ridiculous loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that doesn't reflect in actual sluggishness, so this might be just an unrelated bug. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-11-generic 4.8.0-11.12 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: martin 3049 F...m pulseaudio /dev/snd/pcmC0D0p: martin 3049 F...m pulseaudio /dev/snd/controlC0: martin 3049 F pulseaudio Date: Thu Sep 22 09:42:56 2016 EcryptfsInUse: Yes MachineType: LENOVO 2324CTO ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ systemd.debug-shell RelatedPackageVersions: linux-restricted-modules-4.8.0-11-generic N/A linux-backports-modules-4.8.0-11-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET95WW (2.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324CTO dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro
