[Kernel-packages] [Bug 2002011] Re: drm_WARN_ON in __intel_tc_port_lock
Hi Min Idzelis, I didn't investigate this problem furhter as it didn't appear again since. -- 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/2002011 Title: drm_WARN_ON in __intel_tc_port_lock Status in linux package in Ubuntu: Confirmed Bug description: These warnings are presented in my kernel logs when I boot. [jeu. janv. 5 17:14:17 2023] [ cut here ] [jeu. janv. 5 17:14:17 2023] i915 :00:02.0: drm_WARN_ON(dig_port->tc_mode != TC_PORT_TBT_ALT && !tc_phy_is_owned(dig_port)) [jeu. janv. 5 17:14:17 2023] WARNING: CPU: 0 PID: 1606 at drivers/gpu/drm/i915/display/intel_tc.c:788 __intel_tc_port_lock+0x9c/0x120 [i915] [jeu. janv. 5 17:14:17 2023] Modules linked in: snd_seq_dummy snd_hrtimer snd_seq snd_seq_device overlay bnep binfmt_misc nls_iso8859_1 snd_ctl_led snd_soc_skl_hda_dsp snd_soc_intel_hda_dsp_common snd_soc_hdac_hdmi snd_sof_probes snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_soc_dmic snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec snd_hda_core intel_tcc_cooling snd_hwdep x86_pkg_temp_thermal btusb soundwire_bus intel_powerclamp uvcvideo iwlmvm btrtl snd_soc_core coretemp btbcm videobuf2_vmalloc kvm_intel snd_compress videobuf2_memops btintel mac80211 hid_sensor_als ac97_bus videobuf2_v4l2 joydev processor_thermal_device_pci hid_sensor_trigger libarc4 btmtk snd_pcm_dmaengine videobuf2_common proce ssor_thermal_device [jeu. janv. 5 17:14:17 2023] industrialio_triggered_buffer processor_thermal_rfim iwlwifi snd_pcm bluetooth kfifo_buf processor_thermal_mbox kvm mei_pxp videodev snd_timer ucsi_acpi mei_hdcp input_leds intel_rapl_msr cmdlinepart hid_sensor_iio_common processor_thermal_rapl rapl ecdh_generic mei_me int3403_thermal spi_nor snd typec_ucsi intel_rapl_common intel_cstate mc wmi_bmof hid_multitouch ecc cfg80211 serio_raw industrialio soundcore mei igen6_edac int340x_thermal_zone typec mtd int3400_thermal gpio_keys mac_hid acpi_thermal_rel soc_button_array acpi_pad acpi_tad msr parport_pc ppdev lp ramoops pstore_blk parport reed_solomon pstore_zone efi_pstore ip_tables x_tables autofs4 dm_crypt usbhid hid_sensor_custom hid_sensor_hub intel_ishtp_hid i915 drm_buddy i2c_algo_bit ttm drm_display_helper cec rc_core drm_kms_helper syscopyarea hid_generic sysfillrect crct10dif_pclmul crc32_pclmul ghash_clmulni_intel sysimgblt fb_sys_fops intel_lpss_pci i2c_hid_acpi aesni_intel nvme spi_intel_ pci i2c_i801 [jeu. janv. 5 17:14:17 2023] intel_ish_ipc intel_lpss xhci_pci drm i2c_hid thunderbolt crypto_simd cryptd nvme_core spi_intel i2c_smbus intel_ishtp idma64 xhci_pci_renesas wmi hid video pinctrl_tigerlake [jeu. janv. 5 17:14:17 2023] CPU: 0 PID: 1606 Comm: gnome-shell Tainted: G W 5.19.0-26-generic #27-Ubuntu [jeu. janv. 5 17:14:17 2023] Hardware name: SAMSUNG ELECTRONICS CO., LTD. 950XED/NP950XED-KA1FR, BIOS P07RGF.048.220411.ZQ 04/11/2022 [jeu. janv. 5 17:14:17 2023] RIP: 0010:__intel_tc_port_lock+0x9c/0x120 [i915] [jeu. janv. 5 17:14:17 2023] Code: 8b 5f 50 48 85 db 0f 84 8b 00 00 00 e8 7d de b2 fa 48 c7 c1 e0 0a 94 c0 48 89 da 48 c7 c7 f4 de 91 c0 48 89 c6 e8 a9 a8 00 fb <0f> 0b 5b 41 5c 41 5d 5d 31 c0 31 d2 31 c9 31 f6 31 ff c3 cc cc cc [jeu. janv. 5 17:14:17 2023] RSP: 0018:b037891efa50 EFLAGS: 00010246 [jeu. janv. 5 17:14:17 2023] RAX: RBX: 9f4b02906000 RCX: [jeu. janv. 5 17:14:17 2023] RDX: RSI: RDI: [jeu. janv. 5 17:14:17 2023] RBP: b037891efa68 R08: R09: [jeu. janv. 5 17:14:17 2023] R10: R11: R12: 0001 [jeu. janv. 5 17:14:17 2023] R13: 9f4b2627 R14: 9f4b258aa000 R15: 9f4b258aa000 [jeu. janv. 5 17:14:17 2023] FS: 7f8713e475c0() GS:9f4e7b40() knlGS: [jeu. janv. 5 17:14:17 2023] CS: 0010 DS: ES: CR0: 80050033 [jeu. janv. 5 17:14:17 2023] CR2: 55d561b160d8 CR3: 000117ee6006 CR4: 00770ef0 [jeu. janv. 5 17:14:17 2023] PKRU: 5554 [jeu. janv. 5 17:14:17 2023] Call Trace: [jeu. janv. 5 17:14:17 2023] [jeu. janv. 5 17:14:17 2023] intel_tc_port_connected+0x30/0xf0 [i915] [jeu. janv. 5 17:14:17 2023] intel_digital_port_connected+0x43/0x90 [i915] [jeu. janv. 5 17:14:17 2023] intel_hdmi_detect+0xb4/0x210 [i915] [jeu. janv. 5 17:14:17 2023] drm_helper_probe_detect+0x8e/0xc0 [drm_kms_helper] [jeu. janv. 5 17:14:17 2023]
[Kernel-packages] [Bug 2002011] [NEW] drm_WARN_ON in __intel_tc_port_lock
Public bug reported: These warnings are presented in my kernel logs when I boot. [jeu. janv. 5 17:14:17 2023] [ cut here ] [jeu. janv. 5 17:14:17 2023] i915 :00:02.0: drm_WARN_ON(dig_port->tc_mode != TC_PORT_TBT_ALT && !tc_phy_is_owned(dig_port)) [jeu. janv. 5 17:14:17 2023] WARNING: CPU: 0 PID: 1606 at drivers/gpu/drm/i915/display/intel_tc.c:788 __intel_tc_port_lock+0x9c/0x120 [i915] [jeu. janv. 5 17:14:17 2023] Modules linked in: snd_seq_dummy snd_hrtimer snd_seq snd_seq_device overlay bnep binfmt_misc nls_iso8859_1 snd_ctl_led snd_soc_skl_hda_dsp snd_soc_intel_hda_dsp_common snd_soc_hdac_hdmi snd_sof_probes snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_soc_dmic snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec snd_hda_core intel_tcc_cooling snd_hwdep x86_pkg_temp_thermal btusb soundwire_bus intel_powerclamp uvcvideo iwlmvm btrtl snd_soc_core coretemp btbcm videobuf2_vmalloc kvm_intel snd_compress videobuf2_memops btintel mac80211 hid_sensor_als ac97_bus videobuf2_v4l2 joydev processor_thermal_device_pci hid_sensor_trigger libarc4 btmtk snd_pcm_dmaengine videobuf2_common process or_thermal_device [jeu. janv. 5 17:14:17 2023] industrialio_triggered_buffer processor_thermal_rfim iwlwifi snd_pcm bluetooth kfifo_buf processor_thermal_mbox kvm mei_pxp videodev snd_timer ucsi_acpi mei_hdcp input_leds intel_rapl_msr cmdlinepart hid_sensor_iio_common processor_thermal_rapl rapl ecdh_generic mei_me int3403_thermal spi_nor snd typec_ucsi intel_rapl_common intel_cstate mc wmi_bmof hid_multitouch ecc cfg80211 serio_raw industrialio soundcore mei igen6_edac int340x_thermal_zone typec mtd int3400_thermal gpio_keys mac_hid acpi_thermal_rel soc_button_array acpi_pad acpi_tad msr parport_pc ppdev lp ramoops pstore_blk parport reed_solomon pstore_zone efi_pstore ip_tables x_tables autofs4 dm_crypt usbhid hid_sensor_custom hid_sensor_hub intel_ishtp_hid i915 drm_buddy i2c_algo_bit ttm drm_display_helper cec rc_core drm_kms_helper syscopyarea hid_generic sysfillrect crct10dif_pclmul crc32_pclmul ghash_clmulni_intel sysimgblt fb_sys_fops intel_lpss_pci i2c_hid_acpi aesni_intel nvme spi_intel_pc i i2c_i801 [jeu. janv. 5 17:14:17 2023] intel_ish_ipc intel_lpss xhci_pci drm i2c_hid thunderbolt crypto_simd cryptd nvme_core spi_intel i2c_smbus intel_ishtp idma64 xhci_pci_renesas wmi hid video pinctrl_tigerlake [jeu. janv. 5 17:14:17 2023] CPU: 0 PID: 1606 Comm: gnome-shell Tainted: G W 5.19.0-26-generic #27-Ubuntu [jeu. janv. 5 17:14:17 2023] Hardware name: SAMSUNG ELECTRONICS CO., LTD. 950XED/NP950XED-KA1FR, BIOS P07RGF.048.220411.ZQ 04/11/2022 [jeu. janv. 5 17:14:17 2023] RIP: 0010:__intel_tc_port_lock+0x9c/0x120 [i915] [jeu. janv. 5 17:14:17 2023] Code: 8b 5f 50 48 85 db 0f 84 8b 00 00 00 e8 7d de b2 fa 48 c7 c1 e0 0a 94 c0 48 89 da 48 c7 c7 f4 de 91 c0 48 89 c6 e8 a9 a8 00 fb <0f> 0b 5b 41 5c 41 5d 5d 31 c0 31 d2 31 c9 31 f6 31 ff c3 cc cc cc [jeu. janv. 5 17:14:17 2023] RSP: 0018:b037891efa50 EFLAGS: 00010246 [jeu. janv. 5 17:14:17 2023] RAX: RBX: 9f4b02906000 RCX: [jeu. janv. 5 17:14:17 2023] RDX: RSI: RDI: [jeu. janv. 5 17:14:17 2023] RBP: b037891efa68 R08: R09: [jeu. janv. 5 17:14:17 2023] R10: R11: R12: 0001 [jeu. janv. 5 17:14:17 2023] R13: 9f4b2627 R14: 9f4b258aa000 R15: 9f4b258aa000 [jeu. janv. 5 17:14:17 2023] FS: 7f8713e475c0() GS:9f4e7b40() knlGS: [jeu. janv. 5 17:14:17 2023] CS: 0010 DS: ES: CR0: 80050033 [jeu. janv. 5 17:14:17 2023] CR2: 55d561b160d8 CR3: 000117ee6006 CR4: 00770ef0 [jeu. janv. 5 17:14:17 2023] PKRU: 5554 [jeu. janv. 5 17:14:17 2023] Call Trace: [jeu. janv. 5 17:14:17 2023] [jeu. janv. 5 17:14:17 2023] intel_tc_port_connected+0x30/0xf0 [i915] [jeu. janv. 5 17:14:17 2023] intel_digital_port_connected+0x43/0x90 [i915] [jeu. janv. 5 17:14:17 2023] intel_hdmi_detect+0xb4/0x210 [i915] [jeu. janv. 5 17:14:17 2023] drm_helper_probe_detect+0x8e/0xc0 [drm_kms_helper] [jeu. janv. 5 17:14:17 2023] drm_helper_probe_single_connector_modes+0x738/0x980 [drm_kms_helper] [jeu. janv. 5 17:14:17 2023] ? drm_connector_update_edid_property+0xe3/0x160 [drm] [jeu. janv. 5 17:14:17 2023] drm_mode_getconnector+0x419/0x540 [drm] [jeu. janv. 5 17:14:17 2023] ? idr_find+0xf/0x20 [jeu. janv. 5 17:14:17 2023] ? drm_connector_property_set_ioctl+0x60/0x60 [drm] [jeu. janv. 5 17:14:17 2023] drm_ioctl_kernel+0xd3/0x180 [drm] [jeu. janv. 5
[Kernel-packages] [Bug 1874307] [NEW] Xserver crashes after resuming from sleep
Public bug reported: I am experiencing frequent Gnome-Shell crashes when resuming from sleep mode. The screen is flickering and Gnome-Shell is creating a new session instead of restoring the old one. After investigation with the Gnome team, we realized that the real issue is the X server crashing: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2495 The log messages suggest that this issue might be related to the Nvidia driver: avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE) modeset(G0): failed to set mode: No space left on device avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE) avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: Fatal server error: avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE) EnterVT failed for gpu screen 0 avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE) avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE) avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: Please consult the The X.Org Foundation support avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: at http://wiki.x.org avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: for help. avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE) Please also check the log file at "/home/wenzel/.local/share/xorg/Xorg.1.log" for additional information. avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE) avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE) Server terminated with error (1). Closing log file. Especially "EnterVT failed for gpu screen 0" ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xserver-xorg-video-nvidia-435 435.21-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 22 20:34:17 2020 InstallationDate: Installed on 2019-09-26 (209 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: nvidia-graphics-drivers-435 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-435 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1874307 Title: Xserver crashes after resuming from sleep Status in nvidia-graphics-drivers-435 package in Ubuntu: New Bug description: I am experiencing frequent Gnome-Shell crashes when resuming from sleep mode. The screen is flickering and Gnome-Shell is creating a new session instead of restoring the old one. After investigation with the Gnome team, we realized that the real issue is the X server crashing: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2495 The log messages suggest that this issue might be related to the Nvidia driver: avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE) modeset(G0): failed to set mode: No space left on device avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE) avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: Fatal server error: avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE) EnterVT failed for gpu screen 0 avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE) avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE) avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: Please consult the The X.Org Foundation support avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: at http://wiki.x.org avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: for help. avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE) Please also check the log file at "/home/wenzel/.local/share/xorg/Xorg.1.log" for additional information. avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE) avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE) Server terminated with error (1). Closing log file. Especially "EnterVT failed for gpu screen 0" ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xserver-xorg-video-nvidia-435 435.21-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 22 20:34:17 2020 InstallationDate: Installed on 2019-09-26 (209 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: nvidia-graphics-drivers-435 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to:
[Kernel-packages] [Bug 1852364] [NEW] iwlwifi: Microcode SW error detected
Public bug reported: Hi, I just had an unresponsive Wifi connexion, and checking the dmesg logs gave me this: [53468.634940] iwlwifi :00:14.3: Queue 11 is active on fifo 1 and stuck for 1 ms. SW [0, 15] HW [0, 15] FH TRB=0x0c010b000 [53468.635087] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [53468.635466] iwlwifi :00:14.3: Start IWL Error Log Dump: [53468.635471] iwlwifi :00:14.3: Status: 0x0080, count: 6 [53468.635475] iwlwifi :00:14.3: Loaded firmware version: 46.6bf1df06.0 [53468.635480] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN [53468.635484] iwlwifi :00:14.3: 0x22F0 | trm_hw_status0 [53468.635488] iwlwifi :00:14.3: 0x | trm_hw_status1 [53468.635491] iwlwifi :00:14.3: 0x004882DA | branchlink2 [53468.635495] iwlwifi :00:14.3: 0x0047932A | interruptlink1 [53468.635498] iwlwifi :00:14.3: 0x0047932A | interruptlink2 It looks like a iwlwifi firmware crash. See the dmesg log attached. Thanks. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-firmware 1.183.1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 13 02:54:38 2019 Dependencies: InstallationDate: Installed on 2019-09-26 (47 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "dmesg log" https://bugs.launchpad.net/bugs/1852364/+attachment/5304906/+files/bug_iwl.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1852364 Title: iwlwifi: Microcode SW error detected Status in linux-firmware package in Ubuntu: New Bug description: Hi, I just had an unresponsive Wifi connexion, and checking the dmesg logs gave me this: [53468.634940] iwlwifi :00:14.3: Queue 11 is active on fifo 1 and stuck for 1 ms. SW [0, 15] HW [0, 15] FH TRB=0x0c010b000 [53468.635087] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [53468.635466] iwlwifi :00:14.3: Start IWL Error Log Dump: [53468.635471] iwlwifi :00:14.3: Status: 0x0080, count: 6 [53468.635475] iwlwifi :00:14.3: Loaded firmware version: 46.6bf1df06.0 [53468.635480] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN [53468.635484] iwlwifi :00:14.3: 0x22F0 | trm_hw_status0 [53468.635488] iwlwifi :00:14.3: 0x | trm_hw_status1 [53468.635491] iwlwifi :00:14.3: 0x004882DA | branchlink2 [53468.635495] iwlwifi :00:14.3: 0x0047932A | interruptlink1 [53468.635498] iwlwifi :00:14.3: 0x0047932A | interruptlink2 It looks like a iwlwifi firmware crash. See the dmesg log attached. Thanks. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-firmware 1.183.1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 13 02:54:38 2019 Dependencies: InstallationDate: Installed on 2019-09-26 (47 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1852364/+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 1852002] [NEW] Desktop frozen for 30 seconds after Nvidia driver crash
Public bug reported: Hi, I just experienced a frozen desktop, where I could barely move the mouse, for maybe 30 seconds or more. When the desktop recovered, I looked at dmesg logs to find these lines: [ 461.937702] NVRM: GPU at PCI::01:00: GPU-734060ac-116d-fbbb-1553-d84896b846a4 [ 461.937710] NVRM: Xid (PCI::01:00): 31, pid=275, Ch 002e, intr . MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_0036d000. Fault is of type FAULT_PTE ACCESS_TYPE_VIRT_READ It looks like a fault from the Nvidia driver. I'm using the tested one "nvidia-driver-435", installed via the GUI tool. Could you report this to Nvidia please ? Thanks ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-driver-435 435.21-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 10 17:35:12 2019 InstallationDate: Installed on 2019-09-26 (45 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: nvidia-graphics-drivers-435 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-435 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1852002 Title: Desktop frozen for 30 seconds after Nvidia driver crash Status in nvidia-graphics-drivers-435 package in Ubuntu: New Bug description: Hi, I just experienced a frozen desktop, where I could barely move the mouse, for maybe 30 seconds or more. When the desktop recovered, I looked at dmesg logs to find these lines: [ 461.937702] NVRM: GPU at PCI::01:00: GPU-734060ac-116d-fbbb-1553-d84896b846a4 [ 461.937710] NVRM: Xid (PCI::01:00): 31, pid=275, Ch 002e, intr . MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_0036d000. Fault is of type FAULT_PTE ACCESS_TYPE_VIRT_READ It looks like a fault from the Nvidia driver. I'm using the tested one "nvidia-driver-435", installed via the GUI tool. Could you report this to Nvidia please ? Thanks ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-driver-435 435.21-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 10 17:35:12 2019 InstallationDate: Installed on 2019-09-26 (45 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: nvidia-graphics-drivers-435 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1852002/+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 1850776] [NEW] Kernel NULL pointer dereference on suspend
Public bug reported: Hi, I had a bug every now and then with the Nvidia proprietary driver 435 (installed via the "additionals proprietary drivers" GUI) where I try to suspend my laptop, and the system freezes. It happens from time to time, but so far, I have this issue quite frequently, as I'm often suspending my laptop, so very annoying as you can imagine. Looking at journactl -b 1, the reason is simple: kernel NULL pointer dereference: oct. 31 09:01:51 Strix kernel: BUG: kernel NULL pointer dereference, address: oct. 31 09:01:51 Strix kernel: #PF: supervisor instruction fetch in kernel mode oct. 31 09:01:51 Strix kernel: #PF: error_code(0x0010) - not-present page oct. 31 09:01:51 Strix kernel: PGD 0 P4D 0 oct. 31 09:01:51 Strix kernel: Oops: 0010 [#1] SMP PTI oct. 31 09:01:51 Strix kernel: CPU: 2 PID: 2719 Comm: Xorg Tainted: P O 5.3.0-19-generic #20-Ubuntu oct. 31 09:01:51 Strix kernel: Hardware name: ASUSTeK COMPUTER INC. Strix GL504GV_G515GV/GL504GV, BIOS GL504GV.307 07/11/2019 oct. 31 09:01:51 Strix kernel: RIP: 0010:0x0 oct. 31 09:01:51 Strix kernel: Code: Bad RIP value. oct. 31 09:01:51 Strix kernel: RSP: 0018:afb0c4077920 EFLAGS: 00010286 oct. 31 09:01:51 Strix kernel: RAX: RBX: 8db4a3fff110 RCX: c1c72060 oct. 31 09:01:51 Strix kernel: RDX: 0010 RSI: 8db4a3fff118 RDI: 8db4a3fff150 oct. 31 09:01:51 Strix kernel: RBP: 8db517aaadf0 R08: c1c720b8 R09: oct. 31 09:01:51 Strix kernel: R10: c0f0af14 R11: 8db51dea8820 R12: 8db4a3fff118 oct. 31 09:01:51 Strix kernel: R13: 8db3a87da120 R14: 8db517aaaf10 R15: 8db51ef3d028 oct. 31 09:01:51 Strix kernel: FS: 7faede56ca80() GS:8db52d88() knlGS: oct. 31 09:01:51 Strix kernel: CS: 0010 DS: ES: CR0: 80050033 oct. 31 09:01:51 Strix kernel: CR2: ffd6 CR3: 00045b712002 CR4: 003626e0 oct. 31 09:01:51 Strix kernel: Call Trace: oct. 31 09:01:51 Strix kernel: _nv004359rm+0x45/0x80 [nvidia] oct. 31 09:01:51 Strix kernel: WARNING: kernel stack frame pointer at d844b2ec in Xorg:2719 has bad value deb3a039 oct. 31 09:01:51 Strix kernel: unwind stack type:0 next_sp:93bd32f2 mask:0x2 graph_idx:0 oct. 31 09:01:51 Strix kernel: d844b2ec: 0018 (0x18) oct. 31 09:01:51 Strix kernel: 182c383c: c12f4285 (_nv004359rm+0x45/0x80 [nvidia]) oct. 31 09:01:51 Strix kernel: 0c257d20: 8db51ef3d010 (0x8db51ef3d010) oct. 31 09:01:51 Strix kernel: 18eb8076: 8db4a3fff110 (0x8db4a3fff110) oct. 31 09:01:51 Strix kernel: 58beaab6: 8db3a87da030 (0x8db3a87da030) oct. 31 09:01:51 Strix kernel: d7d391bc: c12f0c9c (_nv034838rm+0x1c/0x20 [nvidia]) oct. 31 09:01:51 Strix kernel: 3d9d3366: 8db51ef3d218 (0x8db51ef3d218) oct. 31 09:01:51 Strix kernel: eaaf8f98: c12ff249 (_nv003603rm+0x9/0x20 [nvidia]) oct. 31 09:01:51 Strix kernel: 79766f3e: 8db51ef3d028 (0x8db51ef3d028) oct. 31 09:01:51 Strix kernel: fbeb93a1: c12f425b (_nv004359rm+0x1b/0x80 [nvidia]) oct. 31 09:01:51 Strix kernel: 160c8872: c1d0 (0xc1d0) oct. 31 09:01:51 Strix kernel: 40aecac9: 8db51949c810 (0x8db51949c810) oct. 31 09:01:51 Strix kernel: 5884ca89: 8db3a87da030 (0x8db3a87da030) oct. 31 09:01:51 Strix kernel: f66282ec: c12f1897 (_nv011071rm+0x2d7/0x350 [nvidia]) oct. 31 09:01:51 Strix kernel: c77ee642: 8db517aaaf10 (0x8db517aaaf10) oct. 31 09:01:51 Strix kernel: f4fcb456: 8db3a87da030 (0x8db3a87da030) oct. 31 09:01:51 Strix kernel: ef44b1aa: c1d0 (0xc1d0) oct. 31 09:01:51 Strix kernel: 514af435: 00010049 (0x10049) oct. 31 09:01:51 Strix kernel: b0f4b16c: ... oct. 31 09:01:51 Strix kernel: 03a0e9a9: c0ce4a55 (_nv034837rm+0x1a5/0x1f0 [nvidia]) oct. 31 09:01:51 Strix kernel: 7a9ef523: 8db3a87da030 (0x8db3a87da030) oct. 31 09:01:51 Strix kernel: 27d325ee: c1d3fe20 (_nv000488rm+0x1c/0xff69a1fc [nvidia]) oct. 31 09:01:51 Strix kernel: 4163f071: 8db517aaaf10 (0x8db517aaaf10) oct. 31 09:01:51 Strix kernel: 53a31c36: ... oct. 31 09:01:51 Strix kernel: b53af793: 8db51949c810 (0x8db51949c810) oct. 31 09:01:51 Strix kernel: d5350376: c12efe6e (_nv034836rm+0x24e/0x430 [nvidia]) oct. 31 09:01:51 Strix kernel: 75b21a0d: c1d3fe80 (_nv019251rm+0x20/0xff69a1a0 [nvidia]) oct. 31 09:01:51 Strix kernel: acf63617: c1d0 (0xc1d0) oct. 31 09:01:51 Strix kernel: 6047e6a8: 00010049 (0x10049) oct. 31 09:01:51 Strix kernel: c3545543: ... oct. 31
