[Bug 1807096] Re: [nvidia] gnome-shell uses 100% cpu, triggered by games while using nvidia-driver
This bug doesn't belong here. I found out, that this is most probably a problem with the switching mechanism between intel and nvidia drivers, which doesn't seem to do its job fully under certain conditions. What was causing gnome-shell to do what it was doing was actually some strange bug that was preventing the fans from working properly sometime after the first CPU throttle, which affected the graphics card performance and/or CPU performance and led to overall problems. I ended up reinstalling the system twice and playing with all sorts of things, but I don't know how certain things exactly work, so I won't put this somewhere else for now (although in the end it should probably be filed under nvidia-drivers). For those who may run into a similar situation: The best bet is to install the nvidia-drivers right after the system using the built-in driver installation tool (software-properties-gtk). Don't touch anything else, don't change the drivers later! Don't use the nvidia-xconfig tool, unless you know exactly what you are doing. If you want to switch between intel and nvidia drivers, use nvidia-settings and always restart the system (don't just logout/login). If you can't switch back to nvidia drivers, use prime-switch nvidia and reboot. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1807096 Title: [nvidia] gnome-shell uses 100% cpu, triggered by games while using nvidia-driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1807096/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1807096] Re: gnome-shell uses 100% cpu, triggered by games while using nvidia-driver
One more piece of information from the syslog: dec 05 21:22:03 mobileaeris kernel: CPU0: Core temperature above threshold, cpu clock throttled (total events = 1) dec 05 21:22:03 mobileaeris kernel: CPU2: Core temperature above threshold, cpu clock throttled (total events = 1) dec 05 21:22:03 mobileaeris kernel: CPU1: Package temperature above threshold, cpu clock throttled (total events = 1) dec 05 21:22:03 mobileaeris kernel: CPU3: Package temperature above threshold, cpu clock throttled (total events = 1) dec 05 21:22:03 mobileaeris kernel: CPU2: Package temperature above threshold, cpu clock throttled (total events = 1) dec 05 21:22:03 mobileaeris kernel: CPU0: Package temperature above threshold, cpu clock throttled (total events = 1) dec 05 21:22:03 mobileaeris kernel: CPU0: Core temperature/speed normal dec 05 21:22:03 mobileaeris kernel: CPU1: Package temperature/speed normal dec 05 21:22:03 mobileaeris kernel: CPU2: Core temperature/speed normal dec 05 21:22:03 mobileaeris kernel: CPU3: Package temperature/speed normal dec 05 21:22:03 mobileaeris kernel: CPU2: Package temperature/speed normal dec 05 21:22:03 mobileaeris kernel: CPU0: Package temperature/speed normal This did happen before (with 18.04) and may be completely unrelated - it's just the normal consequence of running a graphics-intensive application. But it also may be the actual trigger... So the problem may be somewhere between Gnome, kernel and nvidia-driver... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1807096 Title: [nvidia] gnome-shell uses 100% cpu, triggered by games while using nvidia-driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1807096/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1807096] [NEW] gnome-shell uses 100% cpu, triggered by games while using nvidia-driver
Public bug reported: There's not much I can provide in terms of hard data, but maybe someone can help with getting to the bottom of this. After installing Ubuntu 18.10, I'm unable to use graphics-intensive games. My setup: ASUS F556U, with Intel® Core™ i7-7500U CPU @ 2.70GHz × 4, Intel® HD Graphics 620 (Kaby Lake GT2) + NVIDIA GeForce 940MX. While the Nvidia card is being used (Performance mode set in nvidia- settings) and I run a 3d game with Steam (happens e.g. with Black Mesa, Euro Truck Simulator 2...), everything works as expected, but after a relatively short amount of time gnome-shell starts eating up more and more CPU for some reason, effectively taking over the actual game. The game starts to stutter first, then slowly grinds to a completely unresponsive state. If I manage to quit the game, gnome-shell still does its thing. I'm sometimes even unable to enter the overview mode in Gnome. The only solution is to reboot. This does happen with nvidia-driver-390 from the standard repo, but also with nvidia-driver-410 from the graphics PPA. This was not the issue with Ubuntu 18.04. It also does not happen with nouveau, or with the Intel drivers (power saving mode in nvidia-settings). There's also nothing of note in the syslog. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 6 07:26:04 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-05 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sk_SK.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1807096 Title: gnome-shell uses 100% cpu, triggered by games while using nvidia- driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1807096/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1728055] Re: GDM3 hangs, if local home directory is not accessible
This bug seems not to be related to GDM at all. This is a problem either
with automount, or mount.nfs4.
I did spend some time today digging around this and found out that the
hang lasts for several minutes, but then the system springs back to life
and the user list in the greeter will get populated.
Related stuff from journald (user testuser is an LDAP user, remote home; user
localadmin is local - his home is not accessible):
okt 28 16:07:17 paulus systemd[1]: Starting GNOME Display Manager...
okt 28 16:07:17 paulus systemd[1]: Started Regular background program
processing daemon.
okt 28 16:07:17 paulus automount[1566]: Starting automounter version 5.1.2,
master map /etc/auto.master
okt 28 16:07:17 paulus automount[1566]: using kernel protocol version 5.02
okt 28 16:07:17 paulus automount[1566]: lookup_nss_read_master: reading master
file /etc/auto.master
okt 28 16:07:17 paulus automount[1566]: do_init: parse(sun): init gathered
global options: (null)
okt 28 16:07:17 paulus systemd[1]: Started GNOME Display Manager.
okt 28 16:07:17 paulus automount[1566]: lookup_read_master: lookup(file): read
entry /home
okt 28 16:07:17 paulus automount[1566]: master_do_mount: mounting /home
okt 28 16:07:17 paulus automount[1566]: automount_path_to_fifo: fifo name
/var/run/autofs.fifo-home
okt 28 16:07:17 paulus automount[1566]: lookup_nss_read_map: reading map file
/etc/auto.home
okt 28 16:07:17 paulus automount[1566]: do_init: parse(sun): init gathered
global options: (null)
okt 28 16:07:18 paulus automount[1566]: mounted indirect on /home with timeout
300, freq 75 seconds
okt 28 16:07:18 paulus automount[1566]: st_ready: st_ready(): state = 0 path
/home
okt 28 16:07:18 paulus systemd[1]: Started Automounts filesystems on demand.
okt 28 16:07:18 paulus systemd[1]: Reached target Multi-User System.
okt 28 16:07:18 paulus systemd[1]: Reached target Graphical Interface.
SNIP
okt 28 16:07:37 paulus automount[1566]: handle_packet: type = 3
okt 28 16:07:37 paulus automount[1566]: handle_packet_missing_indirect: token
2, name testuser, request pid 1805
okt 28 16:07:37 paulus automount[1566]: attempting to mount entry /home/testuser
okt 28 16:07:37 paulus automount[1566]: lookup_mount: lookup(file): looking up
testuser
okt 28 16:07:37 paulus automount[1566]: lookup_mount: lookup(file): testuser ->
-fstype=nfs4,rw,intr,sec=krb5 petrus.(REDACTED):/home/&
okt 28 16:07:37 paulus automount[1566]: parse_mount: parse(sun): expanded
entry: -fstype=nfs4,rw,intr,sec=krb5 petrus.(REDACTED):/home/testuser
okt 28 16:07:37 paulus automount[1566]: parse_mount: parse(sun): gathered
options: fstype=nfs4,rw,intr,sec=krb5
okt 28 16:07:37 paulus automount[1566]: parse_mount: parse(sun):
dequote("petrus.(REDACTED):/home/testuser") -> petrus.(REDACTED):/home/testuser
okt 28 16:07:37 paulus automount[1566]: parse_mount: parse(sun): core of entry:
options=fstype=nfs4,rw,intr,sec=krb5, loc=petrus.(REDACTED):/home/testuser
okt 28 16:07:37 paulus automount[1566]: sun_mount: parse(sun): mounting root
/home, mountpoint testuser, what petrus.(REDACTED):/home/testuser, fstype nfs4,
options rw,intr,sec=krb5
okt 28 16:07:37 paulus automount[1566]: mount_mount: mount(nfs): root=/home
name=testuser what=petrus.(REDACTED):/home/testuser, fstype=nfs4,
options=rw,intr,sec=krb5
okt 28 16:07:37 paulus automount[1566]: mount_mount: mount(nfs): nfs
options="rw,intr,sec=krb5", nobind=0, nosymlink=0, ro=0
okt 28 16:07:37 paulus automount[1566]: get_nfs_info: called with host
petrus.(REDACTED)(10.0.1.98) proto 6 version 0x40
okt 28 16:07:37 paulus automount[1566]: get_nfs_info: nfs v4 rpc ping time:
0.00
okt 28 16:07:37 paulus automount[1566]: get_nfs_info: host petrus.(REDACTED)
cost 0 weight 0
okt 28 16:07:37 paulus automount[1566]: prune_host_list: selected subset of
hosts that support NFS4 over TCP
okt 28 16:07:37 paulus automount[1566]: mount_mount: mount(nfs): calling
mkdir_path /home/testuser
okt 28 16:07:37 paulus automount[1566]: mount_mount: mount(nfs): calling mount
-t nfs4 -s -o rw,intr,sec=krb5 petrus.(REDACTED):/home/testuser /home/testuser
okt 28 16:07:37 paulus automount[1566]: mount_mount: mount(nfs): mounted
petrus.(REDACTED):/home/testuser on /home/testuser
okt 28 16:07:37 paulus automount[1566]: dev_ioctl_send_ready: token = 2
okt 28 16:07:37 paulus automount[1566]: mounted /home/testuser
okt 28 16:07:37 paulus automount[1566]: st_readmap: state 1 path /home
okt 28 16:07:37 paulus automount[1566]: re-reading map for /home
okt 28 16:07:37 paulus automount[1566]: lookup_nss_read_map: reading map file
/etc/auto.home
okt 28 16:07:37 paulus automount[1566]: do_init: parse(sun): init gathered
global options: (null)
okt 28 16:07:37 paulus automount[1566]: st_ready: st_ready(): state = 4 path
/home
okt 28 16:07:37 paulus automount[1566]: handle_packet: type = 3
okt 28 16:07:37 paulus automount[1566]: handle_packet_missing_indirect: token
3, name localadmin, request pid 1805
okt 28 16:07:37 paulus
[Bug 1728055] [NEW] GDM3 hangs, if local home directory is not accessible
Public bug reported: In Ubuntu 17.10 with GDM 3.26.1-3ubuntu3, the greeter will hang, if local /home directory is not accessible. Our setup: - Ubuntu Server (16.04) with DNS, LDAP, Kerberos 5 and NFS servers. The home directories are present on the server and made available via NFS with krb5 authentication. LDAP provides the user data for clients. - Ubuntu client (17.10), bound to the server, uses AutoFS to automount remote home directories under /home. This makes the otherwise present local user directories unaccessible. Expected behaviour: After system startup, the greeter should provide a way for users to log in. Actual behaviour: The system hangs before the greeter displays the user list (but it does display the top menu bar and Ubuntu logo at the bottom). Additional remarks: If the settings for local users under /var/lib/AccountsService/users contain SystemAccount=true, the greeter will work as expected (while not displaying local users). This is a workaround, that I'm using right now. BUT: if the network user will log in and invoke the authentication dialog for system-wide settings (e.g. if he will try to add a new printer, or change the system update settings), the system will hang before displaying the expected dialog window. Also if a local user will try to log in by entering his login name and password, the system will hang (it should either produce an error message, or log in without a home directory). AutoFS uses this line to mount the remote home directories under /home: * -fstype=nfs4,rw,intr,sec=krb5 FQDN:/home/& ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: artful autofs automount gdm3 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1728055 Title: GDM3 hangs, if local home directory is not accessible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1728055/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
