[Kernel-packages] [Bug 2020757] Re: Kernel BUG (null ptr dereference) with linux-image-5.19.0-42-generic (HWE kernel on 22.04)
The same issue with VirtualBox running on Windows (stupid corporate requirements). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2020757 Title: Kernel BUG (null ptr dereference) with linux-image-5.19.0-42-generic (HWE kernel on 22.04) Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: I use Ubuntu 22.04 in VMWare Player 17.0.2 (Windows host, due to corporate IT...). I installed the HWE kernel since I have an Intel CPU with P/E-cores. 3D acceleration is enabled in VMWare. With linux-image-5.19.0-41-generic it is rock solid. With linux- image-5.19.0-42-generic it invariably crashes after anything between a minute and an hour. In the journalctl after rebooting it showed that X.Org had crashed followed by a Kernel BUG/Oops due to NULL pointer dereference in drm_gem_object_release_handle. A journalctl log from the Xorg crash up until the kernel OOPS has been attached to this case. This issue happened twice with this kernel. In addition, after trying to reproduce it with kdump tools installed, I got a different issue: refcount_t: saturated; leaking memory. in the log, leading to the OOM killing everything on the system, including (based on what was printed on the terminal), systemd-udevd and journald. That OOM killing never made it into the journal however, as can be expected. I have attached what I could get from the journal for this case as well. One thing that helped trigger this bug (but not every time) was launching Firefox, but once it didn't crash from that and only crashed much much later. Unfortunately I could not get ubuntu-bug to work for this case. I tried "ubuntu-bug --package linux-image-5.19.0-42-generic" but it did absolutely nothing. I'm happy to provide any additional information you require however. $ lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 $ apt-cache policy linux-generic-hwe-22.04 linux-generic-hwe-22.04: Installed: 5.19.0.42.43~22.04.15 Candidate: 5.19.0.42.43~22.04.15 Version table: *** 5.19.0.42.43~22.04.15 500 500 http://se.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://se.archive.ubuntu.com/ubuntu jammy/main amd64 Packages $ apt-cache policy linux-image-5.19.0-42-generic linux-image-5.19.0-42-generic: Installed: 5.19.0-42.43~22.04.1 Candidate: 5.19.0-42.43~22.04.1 Version table: *** 5.19.0-42.43~22.04.1 500 500 http://se.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: No crash. What happened instead: The crash in the attached log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2020757/+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 1740736] Re: The it87.ko driver is too old and does not support newer chipsets (such as Z370).
IT8686E does not work on X470 motherboard and upstream 5.2.15 kernel. There has been no upstream movement around `linux/drivers/hwmon/it87.c` since 2 years. -- 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/1740736 Title: The it87.ko driver is too old and does not support newer chipsets (such as Z370). Status in linux package in Ubuntu: Incomplete Bug description: Summary: Thermal sensors are not accessible due to being unsupported by the it87.ko module in linux-image-extra which does not include the it8686 model line among others.. Expected behavior: $ journalctl | grep it87: Apr 20 21:36:00 lakshmi kernel: it87: it87 driver version v1.0-38-g948ad8d Apr 20 21:36:00 lakshmi kernel: it87: Found IT8686E chip at 0xa40, revision 2 Apr 20 21:36:00 lakshmi kernel: it87: Beeping is supported Apr 20 21:36:00 lakshmi kernel: it87: Found IT8792E/IT8795E chip at 0xa60, revision 3 Apr 20 21:36:00 lakshmi kernel: it87: Beeping is supported Actual behavior: $ journalctl | grep it87: Apr 20 20:56:31 lakshmi kernel: it87: Found IT8733E chip at 0xa60, revision 3 Apr 20 20:56:31 lakshmi kernel: it87: Beeping is supported Reproducing: sudo modprobe it87 journalctl | grep it87: Apr 20 20:56:31 lakshmi kernel: it87: Found IT8733E chip at 0xa60, revision 3 Apr 20 20:56:31 lakshmi kernel: it87: Beeping is supported ... sudo rmmod it87 git clone https://github.com/groeck/it87.git cd it87/ make sudo make install sudo modprobe it87 $ journalctl | grep it87: Apr 20 21:36:00 lakshmi kernel: it87: it87 driver version v1.0-38-g948ad8d Apr 20 21:36:00 lakshmi kernel: it87: Found IT8686E chip at 0xa40, revision 2 Apr 20 21:36:00 lakshmi kernel: it87: Beeping is supported Apr 20 21:36:00 lakshmi kernel: it87: Found IT8792E/IT8795E chip at 0xa60, revision 3 Apr 20 21:36:00 lakshmi kernel: it87: Beeping is supported Details: $ uname -rsv Linux 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:58:14 UTC 2018 $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 Codename: bionic $ sudo dmidecode |grep -i product | uniq Product Name: AX370-Gaming 5 Background: Filed a bug report as per question: https://answers.launchpad.net/ubuntu/+question/662421 I'm trying to run lm_sensors on my brand new motherboard (Gigabyte Technology Co., Ltd. Z370 AORUS Ultra Gaming-CF) using the Z370 chipset, and according to the author/maintainer of lm_sensors/it87 driver, fan controls would be supported by chip it8686. Currently such chip is supported only in it87 version https://github.com/groeck/it87; unfortunately both Ubuntu's new LTS Bionic and Torvalds' repositories have got an outdated version of this driver (and possible lm_sensors itself): * http://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/tree/drivers/hwmon/it87.c * https://github.com/torvalds/linux/blob/master/drivers/hwmon/it87.c Can you please update Bionic (at least) to feature this updated driver? Controlling fans speed and other motherboard parameters would be great, especially on new hardware. Thanks! Full discussion thread with driver maintainer here: https://github.com/groeck/lm-sensors/issues/44 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740736/+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 1799305] Re: No desktop after reboot when using nvidia graphics on 18.10
Possibly duplicate of https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1799305 Title: No desktop after reboot when using nvidia graphics on 18.10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: I upgraded from 18.04 to 18.10 and now the desktop does not start after a reboot. The console output ends with "Starting GNOME Display Manager". I cannot switch VTs, my keyboard and mouse are unresponsive though RESUIB sequence works to reboot. If I remote login using ssh, I can run "systemctrl restart gdm3" and I get a working login screen and can continue as expected. If I remove my nvidia drivers the desktop starts as expected after reboot. Examining /var/log/syslog appears to show the nvidia driver failing to load correctly; see below. In the failed state "systemctl status gdm3" shows: ● gdm.service - GNOME Display Manager Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: enabled) Active: active (running) since Mon 2018-10-22 22:06:38 BST; 16min ago Process: 1877 ExecStartPre=/usr/lib/gdm3/gdm-wait-for-drm (code=exited, status=0/SUCCESS) Process: 1723 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS) Main PID: 1880 (gdm3) Tasks: 3 (limit: 4915) Memory: 5.7M CGroup: /system.slice/gdm.service └─1880 /usr/sbin/gdm3 Oct 22 22:06:35 hagrid systemd[1]: Starting GNOME Display Manager... Oct 22 22:06:38 hagrid systemd[1]: Started GNOME Display Manager. Oct 22 22:06:44 hagrid gdm-launch-environment][2108]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0) Oct 22 22:06:54 hagrid gdm3[1880]: Child process -2634 was already dead. Oct 22 22:06:54 hagrid gdm3[1880]: Child process -2634 was already dead. root@hagrid:/var/log# grep 2634 syslog Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead. Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead. . . . This is a section from syslog: Oct 22 22:06:53 hagrid systemd[1]: Starting NVIDIA Persistence Daemon... Oct 22 22:06:53 hagrid nvidia-persistenced: Verbose syslog connection opened Oct 22 22:06:53 hagrid systemd[1]: Started NVIDIA Persistence Daemon. Oct 22 22:06:54 hagrid nvidia-persistenced: Now running with user ID 123 and group ID 129 Oct 22 22:06:54 hagrid [2750]: meta_kms_resources_init failed: Calling drmModeGetResources() failed, assuming we have no outputs Oct 22 22:06:54 hagrid gnome-session[2664]: gnome-session-binary[2664]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Oct 22 22:06:54 hagrid nvidia-persistenced: Started (2865) Oct 22 22:06:54 hagrid [2750]: Failed to create backend: No GPUs with outputs found Oct 22 22:06:54 hagrid nvidia-persistenced: device :01:00.0 - registered Oct 22 22:06:54 hagrid gnome-session-binary[2664]: Unrecoverable failure in required component org.gnome.Shell.desktop Oct 22 22:06:54 hagrid nvidia-persistenced: Local RPC service initialized Oct 22 22:06:54 hagrid systemd[1]: Stopping NVIDIA Persistence Daemon... Oct 22 22:06:54 hagrid kernel: [ 86.847749] virbr0: port 1(virbr0-nic) entered blocking state Oct 22 22:06:54 hagrid kernel: [ 86.847753] virbr0: port 1(virbr0-nic) entered listening state Oct 22 22:06:54 hagrid gnome-session-binary[2664]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Oct 22 22:06:54 hagrid systemd[1]: Stopped NVIDIA Persistence Daemon. Oct 22 22:06:54 hagrid nvidia-persistenced: Received signal 15 Oct 22 22:06:54 hagrid nvidia-persistenced: Socket closed. Oct 22 22:06:54 hagrid nvidia-persistenced: PID file unlocked. Oct 22 22:06:54 hagrid systemd[1]: user-runtime-dir@121.service: Unit not needed anymore. Stopping. Oct 22 22:06:54 hagrid nvidia-persistenced: PID file closed. Oct 22 22:06:54 hagrid systemd[1]: Stopping User Manager for UID 121... Oct 22 22:06:54 hagrid nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced Oct 22 22:06:54 hagrid systemd[2507]: Stopping D-Bus User Message Bus... Oct 22 22:06:54 hagrid nvidia-persistenced: Shutdown (2865) Oct 22 22:06:54 hagrid systemd[2507]: Stopped target Default. Oct 22 22:06:54 hagrid systemd[2507]: Stopped D-Bus User Message Bus. Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead. Description: Ubuntu 18.10 Release: 18.10 nvidia-driver-390: Installed: 390.87-0ubuntu1 Candidate: 390.87-0ubuntu1 Version table: *** 390.87-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu cosmic/restricted amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.10 Package:
