[Kernel-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
^^^ Bug 1717878 -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: Fix Released Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released Status in linux source package in Mantic: Triaged Status in mutter source package in Mantic: Fix Released Bug description: [ Impact ] gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, sometimes when the screen locks, sometimes when launching particular apps. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Test Plan ] Not all Ryzen systems (including one I just purchased) are able to reproduce the bug. We have no choice but to leave final verification to the community. Anyone affected should try locking their screen and verify they are not instantly returned to the login screen. [ Where problems could occur ] Anywhere in frame scheduling and particularly for mouse cursor movement since that's what the real-time thread exists to optimize. [ Original Description ] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+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 2042868] Re: Kernel 6.2.0-36 broke RTW88 solution
Which kernel from where are you running now? The article you linked gives bad advice. You should *not* install from ppa:canonical-kernel- team/ppa. >From https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa: This ppa is used for building pre-release and test kernels. It IS NOT RECOMMENDED that you subscribe to this PPA. -- 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/2042868 Title: Kernel 6.2.0-36 broke RTW88 solution Status in linux package in Ubuntu: New Bug description: On my Linux Mint (derived from Ubuntu) system, I relied on the excellent rtw88 solution from lwfinger (https://github.com/lwfinger/rtw88) to 'fix' my Realtek Wifi Driver whenever a new kernel comes out. As I understand it, the github repository normally is 'ahead' of any kernels, so if and when I do a 'git pull' of his repository before installing the new rtw88, it should work. And this has worked for quite some time, until the 6.2.0-36 kernel came along. As lwfinger himself (?) states, "Ubuntu often modifies kernel APIs, which can cause build issues. You'll need to manually adjust the source code or look for solutions specific to your distribution. We cannot support these types of issues.", so asking him is not an option. Help? Result from version: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 (Well, this the kernel version in which I have Wifi and thus internet, the 'does not work' kernel is 6.2.0-36, supported till February 2024) Result from lscpi-vnvn (also when running the version that still has internet) as an attachment. Kind regards, Roel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042868/+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 2040524] Re: openvswitch fails on raspberry pi 4
Is the openvswitch module (and its dependencies) the only modules that is required from -extra or are there others? Can you post the output of lsmod? ** Changed in: linux-raspi (Ubuntu) Status: New => Incomplete ** Changed in: microovn Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2040524 Title: openvswitch fails on raspberry pi 4 Status in microovn: Invalid Status in linux-raspi package in Ubuntu: Incomplete Bug description: I have a homelab and I'm experimenting with adding arm nodes to my existing cluster. MicroOVN works fine on my x86_64 nodes but fails on my arm nodes (raspberry pi 4). I am using microovn 22.03/stable (rev 295). When I run "microovn init" on the arm nodes, I get the error Error: Post "http://control.socket/cluster/control": context deadline exceeded The output from "snap services microovn" is: Service Startup Current Notes microovn.central disabled inactive - microovn.chassis enabled active- microovn.daemon enabled active- microovn.ovn-northd disabled inactive - microovn.ovn-ovsdb-server-nb disabled inactive - microovn.ovn-ovsdb-server-sb disabled inactive - microovn.refresh-expiring-certs enabled inactive timer-activated microovn.switch enabled inactive - The output from "systemctl | grep ovn" is: run-snapd-ns-microovn.mnt.mount loaded active mounted /run/snapd/ns/microovn.mnt snap-microovn-301.mount loaded active mounted Mount unit for microovn, revision 301 snap.microovn.chassis.service loaded active running Service for snap application microovn.chassis snap.microovn.daemon.service loaded active running Service for snap application microovn.daemon ● snap.microovn.switch.service loaded failed failedService for snap application microovn.switch snap.microovn.refresh-expiring-certs.timer loaded active waiting Timer refresh-expiring-certs for snap application microovn.refresh-expiring-certs The output from "journalctl -b -u snap.microovn.switch.service" is (in relevant part): Oct 25 10:55:27 pi01 systemd[1]: Started Service for snap application microovn.switch. Oct 25 10:55:28 pi01 microovn.switch[7315]: * /var/snap/microovn/common/data/switch/db/conf.db does not exist Oct 25 10:55:28 pi01 microovn.switch[7315]: * Creating empty database /var/snap/microovn/common/data/switch/db/conf.db Oct 25 10:55:28 pi01 microovn.switch[7315]: * Starting ovsdb-server Oct 25 10:55:28 pi01 ovs-vsctl[7338]: ovs|1|vsctl|INFO|Called as ovs-vsctl --no-wait -- init -- set Open_vSwitch . db-version=8.3.0 Oct 25 10:55:28 pi01 ovs-vsctl[7348]: ovs|1|vsctl|INFO|Called as ovs-vsctl --no-wait set Open_vSwitch . ovs-version=2.17.7 "external-ids:system-id=\"pi01\"" "external-ids:rundir=\"/var/snap/microovn/> Oct 25 10:55:28 pi01 microovn.switch[7315]: * Configuring Open vSwitch system IDs Oct 25 10:55:28 pi01 microovn.switch[7380]: /snap/microovn/301/share/openvswitch/scripts/ovs-kmod-ctl: 112: modprobe: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/microovn/+bug/2040524/+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 2043964] [NEW] New China SRRC compliance readiness check for Realtek WLAN
Public bug reported: New China SRRC compliance readiness check Proposed Change: - China SRRC updates the testing requirement for 2.4/5GHz, the major changes are the in-band RSE limit, and EIRP limits. - The SRRC updates impact both WLAN modules and platforms. The WLAN modules need to complete the new SRRC testing then platform can start to apply / renew the new SRRC cert. If platform took several WLAN modules but not all of the modules have completed the new SRRC testing updates, platform cannot renew/apply the new SRRC cert. - The platforms which apply/renew SRRC new standards need to ensure the TX power can meet the new RSE/EIRP limits. IHV confirmed below driver version can support these requirements. Realtek: The upstream driver can support SRRC compliance. https://lore.kernel.org/linux-wireless/20230927072156.26336-1-pks...@realtek.com/T/#m4d8acb2697ff2bc07485a6119839e1f96a822340 [lore.kernel.org] ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-2042990 somerville ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => Won't Fix ** Tags added: oem-priority originate-from-2042990 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2043964 Title: New China SRRC compliance readiness check for Realtek WLAN Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.5 source package in Jammy: New Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: Invalid Bug description: New China SRRC compliance readiness check Proposed Change: - China SRRC updates the testing requirement for 2.4/5GHz, the major changes are the in-band RSE limit, and EIRP limits. - The SRRC updates impact both WLAN modules and platforms. The WLAN modules need to complete the new SRRC testing then platform can start to apply / renew the new SRRC cert. If platform took several WLAN modules but not all of the modules have completed the new SRRC testing updates, platform cannot renew/apply the new SRRC cert. - The platforms which apply/renew SRRC new standards need to ensure the TX power can meet the new RSE/EIRP limits. IHV confirmed below driver version can support these requirements. Realtek: The upstream driver can support SRRC compliance. https://lore.kernel.org/linux-wireless/20230927072156.26336-1-pks...@realtek.com/T/#m4d8acb2697ff2bc07485a6119839e1f96a822340 [lore.kernel.org] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2043964/+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 2043962] [NEW] [Mediatek] mt8195-demo: enable CONFIG_COMMON_CLK_MT8188 and CONFIG_MTK_PMIC_WRAP
Public bug reported: [SRU Justification] [Impact] emmc storage is not usable after booting. [Fix] CONFIG_COMMON_CLK_MT8188 and CONFIG_MTK_PMIC_WRAP need to be built-in to supply clock and power as early as possible, in order to have the emmc storage for further installation. [Test Case] 1. build test. 2. testing on the target device, mediatek g1200 evk board, and check the emmc storage could be recognize and mountable after booting. [Where problems could occur] the risk would be low because both drivers are only used on mediatek platform. [Other info] the purpose of this is to make ubuntu as an arm systemready ir distribution for mediatek platform. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Invalid => Incomplete ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: Incomplete ** Changed in: linux (Ubuntu Noble) Status: Incomplete => New -- 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/2043962 Title: [Mediatek] mt8195-demo: enable CONFIG_COMMON_CLK_MT8188 and CONFIG_MTK_PMIC_WRAP Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: [SRU Justification] [Impact] emmc storage is not usable after booting. [Fix] CONFIG_COMMON_CLK_MT8188 and CONFIG_MTK_PMIC_WRAP need to be built-in to supply clock and power as early as possible, in order to have the emmc storage for further installation. [Test Case] 1. build test. 2. testing on the target device, mediatek g1200 evk board, and check the emmc storage could be recognize and mountable after booting. [Where problems could occur] the risk would be low because both drivers are only used on mediatek platform. [Other info] the purpose of this is to make ubuntu as an arm systemready ir distribution for mediatek platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043962/+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 2043905] Re: VT6307 IEEE1394 card causes reboot loop
** Summary changed: - Mantic reboot loop before splash screen is displayed + VT6307 IEEE1394 card causes reboot loop -- 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/2043905 Title: VT6307 IEEE1394 card causes reboot loop Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: used the live USB for Kubuntu and UbuntuStudio 23.10 as well as upgraded to Mantic 6.5.0-10-generic from a Lunar 6.2.0-36 that works... all of the 6.5.0 64 bit kernel versions do a reboot loop prior to the splash screen display. Processor is an AMD Ryzen 5600X, MSI MPG B550 GAMING PLUS Motherboard with 64 gig 3200 ddr4 ram. AMD Radeon RX6600 graphics... latest BIOS firmware is installed, "fwupdmrg refresh --force && fwupdmrg update" in root terminal reports no available updates. in the advanced options of grub I can boot into mantic with the lunar 6.2.0-36 kernel. Cell phone video capture of the bad boot included... Further testing found that a Mantic beta July 3rd build will boot (6.3 kernel) booting to the current live Kubuntu USB with the 6.5.0-9 kernel and removing hardware 1 piece at a time then replacing if the loop occurred found that as soon as a VT6307 PCIe card is removed the 6.5.0-9 and 6.5.0-10 kernels will boot properly. as soon as the card is reinstalled the panic reboot loop starts up again... If there was a log generated from the loop I have been unable to find one in the /var/log directory... I have been unable to get kdump to work... To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2043905/+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 2043905] Re: Mantic reboot loop before splash screen is displayed
** Bug watch added: Linux Kernel Bug Tracker #217993 https://bugzilla.kernel.org/show_bug.cgi?id=217993 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=217993 Importance: Unknown Status: Unknown -- 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/2043905 Title: Mantic reboot loop before splash screen is displayed Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: used the live USB for Kubuntu and UbuntuStudio 23.10 as well as upgraded to Mantic 6.5.0-10-generic from a Lunar 6.2.0-36 that works... all of the 6.5.0 64 bit kernel versions do a reboot loop prior to the splash screen display. Processor is an AMD Ryzen 5600X, MSI MPG B550 GAMING PLUS Motherboard with 64 gig 3200 ddr4 ram. AMD Radeon RX6600 graphics... latest BIOS firmware is installed, "fwupdmrg refresh --force && fwupdmrg update" in root terminal reports no available updates. in the advanced options of grub I can boot into mantic with the lunar 6.2.0-36 kernel. Cell phone video capture of the bad boot included... Further testing found that a Mantic beta July 3rd build will boot (6.3 kernel) booting to the current live Kubuntu USB with the 6.5.0-9 kernel and removing hardware 1 piece at a time then replacing if the loop occurred found that as soon as a VT6307 PCIe card is removed the 6.5.0-9 and 6.5.0-10 kernels will boot properly. as soon as the card is reinstalled the panic reboot loop starts up again... If there was a log generated from the loop I have been unable to find one in the /var/log directory... I have been unable to get kdump to work... To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2043905/+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 1995150] Re: kernel NULL pointer dereference after monitor wake
Interesting that others are seeing this now. I continued to build and use a custom patched kernel for the entirety of 22.10. But from 23.04 onward, I've not had any issues. I'm currently running 23.10 with kernel 6.5.0-10-generic. -- 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/1995150 Title: kernel NULL pointer dereference after monitor wake Status in linux package in Ubuntu: Confirmed Bug description: I ran into a bug shortly after upgrading from 22.04 to 22.10. I have 2 monitors connected to a Radeon R9 FURY / NANO Series via DP cables. When returning to the PC after a screen lock (when both monitors had entered a power saving mode), the second monitor did not wake up. I see the following warning and `kernel NULL pointer dereference` in the systemd journal: Oct 28 12:24:11 desktop kernel: [ cut here ] Oct 28 12:24:11 desktop kernel: WARNING: CPU: 12 PID: 91 at drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dce110/dce110_clk_mgr.c:140 dce110_fill_display_configs+0x83/0x2e0 [amdgpu] Oct 28 12:24:11 desktop kernel: Modules linked in: xt_multiport tls nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter nvme_fabrics rfcomm snd_seq_dummy snd_hrtimer xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat n> Oct 28 12:24:11 desktop kernel: gigabyte_wmi rapl drm_kms_helper fb_sys_fops snd_timer syscopyarea iwlwifi(O) ccp sysfillrect snd sysimgblt k10temp soundcore cfg80211(O) iwlwifi_compat(O) mac_hid msr parport_pc ppdev lp parport drm ramoops pstore_blk reed_solomon pstore_zone efi_> Oct 28 12:24:11 desktop kernel: CPU: 12 PID: 91 Comm: kworker/12:0H Tainted: G O 5.19.0-23.24-justin-stock-generic #stock Oct 28 12:24:11 desktop kernel: Hardware name: Gigabyte Technology Co., Ltd. X570 AORUS PRO WIFI/X570 AORUS PRO WIFI, BIOS F21 07/31/2020 Oct 28 12:24:11 desktop kernel: Workqueue: events_highpri dm_irq_work_func [amdgpu] Oct 28 12:24:11 desktop kernel: RIP: 0010:dce110_fill_display_configs+0x83/0x2e0 [amdgpu] Oct 28 12:24:11 desktop kernel: Code: 89 dd 31 db 4c 63 f3 49 83 fe 05 0f 87 80 01 00 00 4d 39 65 00 0f 84 29 01 00 00 83 c3 01 49 81 c5 10 08 00 00 83 fb 06 75 da <0f> 0b 31 db 45 0f b6 ac 24 c8 03 00 00 41 80 fd 01 0f 87 fd 55 19 Oct 28 12:24:11 desktop kernel: RSP: 0018:b291404dfa90 EFLAGS: 00010246 Oct 28 12:24:11 desktop kernel: RAX: 0110 RBX: 0006 RCX: Oct 28 12:24:11 desktop kernel: RDX: RSI: 908acdcd2980 RDI: 908acdcc Oct 28 12:24:11 desktop kernel: RBP: b291404dfae0 R08: 908acdcc R09: Oct 28 12:24:11 desktop kernel: R10: 908acdcd2980 R11: 908acdcc01f0 R12: 908aa3478000 Oct 28 12:24:11 desktop kernel: R13: 908acdcc3250 R14: 0005 R15: Oct 28 12:24:11 desktop kernel: FS: () GS:90911ed0() knlGS: Oct 28 12:24:11 desktop kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 12:24:11 desktop kernel: CR2: 7f36aced3098 CR3: 0001a3e6c000 CR4: 00350ee0 Oct 28 12:24:11 desktop kernel: Call Trace: Oct 28 12:24:11 desktop kernel: Oct 28 12:24:11 desktop kernel: ? dce_get_required_clocks_state+0x25/0x140 [amdgpu] Oct 28 12:24:11 desktop kernel: dce_update_clocks+0xdb/0x170 [amdgpu] Oct 28 12:24:11 desktop kernel: dce100_prepare_bandwidth+0x3e/0x50 [amdgpu] Oct 28 12:24:11 desktop kernel: commit_planes_for_stream+0xd54/0x1060 [amdgpu] Oct 28 12:24:11 desktop kernel: ? dc_resource_state_copy_construct+0x167/0x2b0 [amdgpu] Oct 28 12:24:11 desktop kernel: dc_commit_updates_for_stream+0x1e8/0x5b0 [amdgpu] Oct 28 12:24:11 desktop kernel: set_all_streams_dpms_off_for_link+0x159/0x190 [amdgpu] Oct 28 12:24:11 desktop kernel: ? detect_link_and_local_sink+0x5f2/0xc40 [amdgpu] Oct 28 12:24:11 desktop kernel: verify_link_capability.isra.0+0x260/0x300 [amdgpu] Oct 28 12:24:11 desktop kernel: dc_link_detect+0x35/0x1d0 [amdgpu] Oct 28 12:24:11 desktop kernel: handle_hpd_irq_helper+0x106/0x1d0 [amdgpu] Oct 28 12:24:11 desktop kernel: handle_hpd_irq+0xe/0x20 [amdgpu] Oct 28 12:24:11 desktop kernel: dm_irq_work_func+0x19/0x30 [amdgpu] Oct 28 12:24:11 desktop kernel: process_one_work+0x225/0x400 Oct 28 12:24:11 desktop kernel: worker_thread+0x50/0x3e0 Oct 28 12:24:11 desktop kernel: ? rescuer_thread+0x3c0/0x3c0 Oct 28 12:24:11 desktop kernel: kthread+0xe9/0x110 Oct 28 12:24:11 desktop kernel: ? kthread_complete_and_exit+0x20/0x20 Oct 28 12:24:11 desktop kernel: ret_from_fork+0x22/0x30 Oct 28 12:24:11 desktop kernel: Oct 28 12:24:11 desktop kernel: ---[ end trace ]--- Oct 28 12:24:11 desktop kernel: BUG: kernel NULL pointer dereference
[Kernel-packages] [Bug 2043945] Re: kworker takes around 25% cpu usage permanently
** Package changed: ubuntu => linux-hwe-6.2 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2043945 Title: kworker takes around 25% cpu usage permanently Status in linux-hwe-6.2 package in Ubuntu: New Bug description: The problem appeared when I upgraded my linux kernel from 6.2.0-26-generic to 6.2.0-36-generic. Observing the output of the top command, the processes that show up at the top are : - kworker/0:x+kacpid - kworker/0:x-kacpi_notify where x changing from 0 to 3. CPU usage of those tasks varies between 20% and 25%. List of packages related to the new kernel (from grep " install " /var/log/dpkg.log) linux-modules-6.2.0-36-generic:amd64 6.2.0-36.37~22.04.1 inux-image-6.2.0-36-generic:amd64 6.2.0-36.37~22.04.1 linux-modules-extra-6.2.0-36-generic:amd64 6.2.0-36.37~22.04.1 linux-hwe-6.2-headers-6.2.0-36:all 6.2.0-36.37~22.04.1 inux-headers-6.2.0-36-generic:amd64 6.2.0-36.37~22.04.1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-36-generic 6.2.0-36.37~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Sun Nov 19 23:22:28 2023 InstallationDate: Installed on 2023-11-19 (0 days ago) InstallationMedia: Ubuntu-MATE 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2043945/+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 2043945] [NEW] kworker takes around 25% cpu usage permanently
You have been subscribed to a public bug: The problem appeared when I upgraded my linux kernel from 6.2.0-26-generic to 6.2.0-36-generic. Observing the output of the top command, the processes that show up at the top are : - kworker/0:x+kacpid - kworker/0:x-kacpi_notify where x changing from 0 to 3. CPU usage of those tasks varies between 20% and 25%. List of packages related to the new kernel (from grep " install " /var/log/dpkg.log) linux-modules-6.2.0-36-generic:amd64 6.2.0-36.37~22.04.1 inux-image-6.2.0-36-generic:amd64 6.2.0-36.37~22.04.1 linux-modules-extra-6.2.0-36-generic:amd64 6.2.0-36.37~22.04.1 linux-hwe-6.2-headers-6.2.0-36:all 6.2.0-36.37~22.04.1 inux-headers-6.2.0-36-generic:amd64 6.2.0-36.37~22.04.1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-36-generic 6.2.0-36.37~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Sun Nov 19 23:22:28 2023 InstallationDate: Installed on 2023-11-19 (0 days ago) InstallationMedia: Ubuntu-MATE 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- kworker takes around 25% cpu usage permanently https://bugs.launchpad.net/bugs/2043945 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. -- 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 1995150] Re: kernel NULL pointer dereference after monitor wake
I'm also seeing a variant of this bug (22.04 with kernel 6.2.0-36-generic) with amdgpu driving a dual-head setup. The crash occurs for me consistently on system wake, and becomes entirely unresponsive (I'm unable to drop to other runlevels to bring it back). Like the original report, the crash appears to occur due a NULL dereference in `dce110_fill_display_configs` -- 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/1995150 Title: kernel NULL pointer dereference after monitor wake Status in linux package in Ubuntu: Confirmed Bug description: I ran into a bug shortly after upgrading from 22.04 to 22.10. I have 2 monitors connected to a Radeon R9 FURY / NANO Series via DP cables. When returning to the PC after a screen lock (when both monitors had entered a power saving mode), the second monitor did not wake up. I see the following warning and `kernel NULL pointer dereference` in the systemd journal: Oct 28 12:24:11 desktop kernel: [ cut here ] Oct 28 12:24:11 desktop kernel: WARNING: CPU: 12 PID: 91 at drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dce110/dce110_clk_mgr.c:140 dce110_fill_display_configs+0x83/0x2e0 [amdgpu] Oct 28 12:24:11 desktop kernel: Modules linked in: xt_multiport tls nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter nvme_fabrics rfcomm snd_seq_dummy snd_hrtimer xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat n> Oct 28 12:24:11 desktop kernel: gigabyte_wmi rapl drm_kms_helper fb_sys_fops snd_timer syscopyarea iwlwifi(O) ccp sysfillrect snd sysimgblt k10temp soundcore cfg80211(O) iwlwifi_compat(O) mac_hid msr parport_pc ppdev lp parport drm ramoops pstore_blk reed_solomon pstore_zone efi_> Oct 28 12:24:11 desktop kernel: CPU: 12 PID: 91 Comm: kworker/12:0H Tainted: G O 5.19.0-23.24-justin-stock-generic #stock Oct 28 12:24:11 desktop kernel: Hardware name: Gigabyte Technology Co., Ltd. X570 AORUS PRO WIFI/X570 AORUS PRO WIFI, BIOS F21 07/31/2020 Oct 28 12:24:11 desktop kernel: Workqueue: events_highpri dm_irq_work_func [amdgpu] Oct 28 12:24:11 desktop kernel: RIP: 0010:dce110_fill_display_configs+0x83/0x2e0 [amdgpu] Oct 28 12:24:11 desktop kernel: Code: 89 dd 31 db 4c 63 f3 49 83 fe 05 0f 87 80 01 00 00 4d 39 65 00 0f 84 29 01 00 00 83 c3 01 49 81 c5 10 08 00 00 83 fb 06 75 da <0f> 0b 31 db 45 0f b6 ac 24 c8 03 00 00 41 80 fd 01 0f 87 fd 55 19 Oct 28 12:24:11 desktop kernel: RSP: 0018:b291404dfa90 EFLAGS: 00010246 Oct 28 12:24:11 desktop kernel: RAX: 0110 RBX: 0006 RCX: Oct 28 12:24:11 desktop kernel: RDX: RSI: 908acdcd2980 RDI: 908acdcc Oct 28 12:24:11 desktop kernel: RBP: b291404dfae0 R08: 908acdcc R09: Oct 28 12:24:11 desktop kernel: R10: 908acdcd2980 R11: 908acdcc01f0 R12: 908aa3478000 Oct 28 12:24:11 desktop kernel: R13: 908acdcc3250 R14: 0005 R15: Oct 28 12:24:11 desktop kernel: FS: () GS:90911ed0() knlGS: Oct 28 12:24:11 desktop kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 12:24:11 desktop kernel: CR2: 7f36aced3098 CR3: 0001a3e6c000 CR4: 00350ee0 Oct 28 12:24:11 desktop kernel: Call Trace: Oct 28 12:24:11 desktop kernel: Oct 28 12:24:11 desktop kernel: ? dce_get_required_clocks_state+0x25/0x140 [amdgpu] Oct 28 12:24:11 desktop kernel: dce_update_clocks+0xdb/0x170 [amdgpu] Oct 28 12:24:11 desktop kernel: dce100_prepare_bandwidth+0x3e/0x50 [amdgpu] Oct 28 12:24:11 desktop kernel: commit_planes_for_stream+0xd54/0x1060 [amdgpu] Oct 28 12:24:11 desktop kernel: ? dc_resource_state_copy_construct+0x167/0x2b0 [amdgpu] Oct 28 12:24:11 desktop kernel: dc_commit_updates_for_stream+0x1e8/0x5b0 [amdgpu] Oct 28 12:24:11 desktop kernel: set_all_streams_dpms_off_for_link+0x159/0x190 [amdgpu] Oct 28 12:24:11 desktop kernel: ? detect_link_and_local_sink+0x5f2/0xc40 [amdgpu] Oct 28 12:24:11 desktop kernel: verify_link_capability.isra.0+0x260/0x300 [amdgpu] Oct 28 12:24:11 desktop kernel: dc_link_detect+0x35/0x1d0 [amdgpu] Oct 28 12:24:11 desktop kernel: handle_hpd_irq_helper+0x106/0x1d0 [amdgpu] Oct 28 12:24:11 desktop kernel: handle_hpd_irq+0xe/0x20 [amdgpu] Oct 28 12:24:11 desktop kernel: dm_irq_work_func+0x19/0x30 [amdgpu] Oct 28 12:24:11 desktop kernel: process_one_work+0x225/0x400 Oct 28 12:24:11 desktop kernel: worker_thread+0x50/0x3e0 Oct 28 12:24:11 desktop kernel: ? rescuer_thread+0x3c0/0x3c0 Oct 28 12:24:11 desktop kernel: kthread+0xe9/0x110 Oct 28 12:24:11 desktop kernel: ? kthread_complete_and_exit+0x20/0x20 Oct 28 12:24:11 desktop kernel: ret_from_fork+0x22/0x30 Oct 28 12:24:11 desktop kernel:
[Kernel-packages] [Bug 2039570] Re: [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black screen (no screen detected)
I opened a report here in freedesktop:
https://gitlab.freedesktop.org/drm/amd/-/issues/2993#note_2172154
And as Michel Dänzer says, it's possible this is an issue related to
Mutter. Here in these logs from journalctl gnome-shell I attach here,
you can see the messages that appear just when, upon opening a game in
fullscreen, the screen 'disconnects'.
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2993
https://gitlab.freedesktop.org/drm/amd/-/issues/2993
** Attachment added: "journalctl gnome shell when fullscreen.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039570/+attachment/5721046/+files/journalctl%20gnome%20shell%20when%20fullscreen.txt
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
--
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/2039570
Title:
[amdgpu] Fullscreen in any Wayland / Xwayland window shows a black
screen (no screen detected)
Status in linux package in Ubuntu:
Confirmed
Status in mutter package in Ubuntu:
New
Bug description:
When I go into "fullscreen" watching a video while browsing in Firefox
or when playing a game through Steam (fullscreen mode), the screen
goes black.
The workaround I have discovered to get back is to enter the gdm from
"Ctrl + alt + F1" and then return to the session you were in
(normally, "Ctrl + alt + F2).
Edit: It happens when I connect a second monitor and use it as the
primary display while the laptop screen is disabled.
MSI laptop.
CPU: AMD Ryzen 7 Series 4000
GPU: AMD Radeon RX 5600m
RAM: 16GB
NVM: 1TB.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: noctis 2095 F wireplumber
/dev/snd/controlC0: noctis 2095 F wireplumber
/dev/snd/seq:noctis 2090 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 15:00:55 2023
InstallationDate: Installed on 2023-10-13 (4 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB:
0 amdgpudrmfb
1 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=fb325c2c-11c5-43e3-aceb-e921d5a7b323 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/26/2020
dmi.bios.release: 1.1
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E17EKAMS.101
dmi.board.asset.tag: Default string
dmi.board.name: MS-17EK
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrE17EKAMS.101:bd10/26/2020:br1.1:svnMicro-StarInternationalCo.,Ltd.:pnAlpha17A4DEK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17EK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku17EK.1:
dmi.product.family: Al
dmi.product.name: Alpha 17 A4DEK
dmi.product.sku: 17EK.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039570/+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 2038998] Re: [amdgpu] Screen artifacts/UI oddities on Wayland
How much do we have to wait if this fix is already released but not in
Ubuntu 23.10?
--
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/2038998
Title:
[amdgpu] Screen artifacts/UI oddities on Wayland
Status in GNOME Shell:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Confirmed
Bug description:
Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
Ryzen 7 PRO 5850U
with Radeon (RX Vega 8?) integrated graphics
16 GB RAM
Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
2023 from a daily-live/current .iso generated on October 4, 2023.
Wayland
Kernel 6.5.0-9-generic
* * * * *
Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
day, was going through setting up and testing the usual programs.
Installed Steam through apt from the 'mantic' repositories. Installed
Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
compatible titles.
Screen corruption (white and grey streaks) present in-game when GNOME
UI elements appeared on-screen (e.g., volume, brightness, and keyboard
backlight indicators) and omnipresent after closing either game.
Artifacts remain on screen until log-out or reboot. Artifacts were not
present beforehand.
Artifacts only appeared in Wayland session; not X11/Xorg.
I previously had been running the same games on Ubuntu 22.04 LTS
(GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
computer without issue (kernel 6.2).
* * * * *
Please see subsequent posts for video/images.
Happy to provide any other information as needed. Thanks!
* * * * *
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 11 01:17:43 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series]
[17aa:509b]
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2023
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET54W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A00068US
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias:
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A00068US
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2038998/+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 2037214] Re: evict_inodes inode xxx, i_count = 1, was skipped!
These messages get triggered randomly (I suspect on unmounting NFS
mounts, which are managed by systemd automounter) on my Ubuntu 23.10
machines and end up in systemd journal and kern.log (gigabytes of
messages), system uses 4 CPUs completely and gets unresponsive.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2037214
Title:
evict_inodes inode xxx, i_count = 1, was skipped!
Status in linux package in Ubuntu:
Confirmed
Status in linux-oem-6.5 package in Ubuntu:
Confirmed
Bug description:
Hi,
during boot the kernel logs the following messages:
# dmesg | grep evict_inodes
[ 12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped!
[ 12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 8ff8e64c, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 194d080e, i_count = 1, was skipped!
[ 12.784812] evict_inodes inode 09b77b7b, i_count = 1, was skipped!
[ 12.811217] evict_inodes inode ec873c71, i_count = 1, was skipped!
[ 12.811222] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[ 12.811223] evict_inodes inode b42b829a, i_count = 1, was skipped!
[ 12.811224] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[ 13.412667] evict_inodes inode 61a23a39, i_count = 1, was skipped!
[ 13.412671] evict_inodes inode b42b829a, i_count = 1, was skipped!
[ 13.412671] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[ 13.412672] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[ 13.412673] evict_inodes inode ec873c71, i_count = 1, was skipped!
Those messages are not displayed when I boot my system with a mainline Linux
kernel.
Moreover, in the mainline Linux source code, I do not find the lines where
such a message could be printed.
Therefore, those messages are probably caused by an Ubuntu patch.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-5-generic 6.5.0-5.5
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bonnaudl 4827 F wireplumber
/dev/snd/seq:bonnaudl 4808 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 14:39:10 2023
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash
vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-5-generic N/A
linux-backports-modules-6.5.0-5-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214/+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 2043469] Re: Low-latency kernel can't boot to desktop
Hi icaria36, Your configuration boots to nouveau instead of the nvidia driver when you boot into -lowlatency. As seen in the below Xserver logs: ... Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: (==) Matched nouveau as autoconfigured driver 0 ... Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: (II) LoadModule: "nouveau" Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: (II) Module nouveau: vendor="X.Org Foundation" Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: compiled for 1.21.1.3, module version = 1.0.17 Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: Module class: X.Org Video Driver Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: ABI class: X.Org Video Driver, version 25.2 ... Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: (II) NOUVEAU driver Date: Sat Jan 23 12:24:42 2021 -0500 Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: (II) NOUVEAU driver for NVIDIA chipset families : Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: RIVA TNT (NV04) Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: RIVA TNT2 (NV05) Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: GeForce 256 (NV10) Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: GeForce 2 (NV11, NV15) Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: GeForce 4MX (NV17, NV18) Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: GeForce 3 (NV20) Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: GeForce 4Ti (NV25, NV28) Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: GeForce FX (NV3x) Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: GeForce 6 (NV4x) Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: GeForce 7 (G7x) Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: GeForce 8 (G8x) Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: GeForce 9 (G9x) Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: GeForce GTX 2xx/3xx (GT2xx) Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: GeForce GTX 4xx/5xx (GFxxx) Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: GeForce GTX 6xx/7xx (GKxxx) Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: GeForce GTX 9xx (GMxxx) Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: GeForce GTX 10xx(GPxxx) ... Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: xf86EnableIO: failed to enable I/O ports -03ff (Operation not permitted) Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: (EE) [drm] Failed to open DRM device for pci::01:00.0: -19 Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: (WW) Falling back to old probe method for modesetting Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: (II) modeset(1): using default device ... Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: (EE) Unable to find a valid framebuffer device ... Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: Fatal server error: Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: (EE) Cannot run in framebuffer mode. Please specify busIDsfor all framebuffer devices ... Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: (EE) Server terminated with error (1). Closing log file. Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4027]: Unable to run X server Nov 17 11:59:24 quiet gdm-launch-environment][3922]: pam_unix(gdm-launch-environment:session): session closed for user gdm Nov 17 11:59:24 quiet gdm3[1404]: Gdm: GdmDisplay: Session never registered, failing Nov 17 11:59:24 quiet systemd[1]: session-c2.scope: Deactivated successfully. Nov 17 11:59:24 quiet systemd-logind[1036]: Session c2 logged out. Waiting for processes to exit. Nov 17 11:59:24 quiet systemd-logind[1036]: Removed session c2. Later on, when all your services are shutting down, it tries to modprobe the nvidia driver, but its missing. Is it installed for the -lowlatency variant, or just -generic only? Maybe check to see if it was built correctly in dkms logs. Nov 17 11:59:44 quiet gdm3[4175]: modprobe: FATAL: Module nvidia not found in directory /lib/modules/6.5.0-10-lowlatency Nov 17 11:59:55 quiet gdm3[4199]: modprobe: FATAL: Module nvidia not found in directory /lib/modules/6.5.0-10-lowlatency Nov 17 12:00:05 quiet gdm3[4221]: modprobe: FATAL: Module nvidia not found in directory /lib/modules/6.5.0-10-lowlatency Nov 17 12:00:11 quiet wpa_supplicant[1101]: wlp6s0: WPA: Group rekeying completed with 3c:a6:2f:c7:23:5b [GTK=CCMP] Nov 17 12:00:15 quiet gdm3[4243]: modprobe: FATAL: Module nvidia not found in directory /lib/modules/6.5.0-10-lowlatency Nov 17 12
[Kernel-packages] [Bug 2041558] Re: failed to load firmware renesas_usb_fw.mem
If this firmware file is missing renesas_usb_fw.mem I have an issue with a PCIE to USB 3.0 card ( Renesas Technology Corp. uPD720201 ) which stops working at 22 hourts after boot withtout this firmware file. If I manually add it to /lib/firmaware/renesas_usb_fw.mem and load the firmware by reinitializing the PCIE card it works. It is best if the firmware file is there and is loadded after boot. Please, fix it -- 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/2041558 Title: failed to load firmware renesas_usb_fw.mem Status in linux-firmware package in Ubuntu: Won't Fix Status in linux-hwe-5.15 package in Ubuntu: Invalid Bug description: the log show below: xhci_hcd :27:00.0: failed to load firmware renesas_usb_fw.mem, fallback to ROM From this below, it seems just need to add renesas_usb_fw.mem into the initrd. https://bbs.archlinux.org/viewtopic.php?pid=1922549#p1922549 When the firmware is required and is not present, kernel message: Direct firmware load for renesas_usb_fw.mem failed with error When the firmware is required and is an empty file, kernel message: FW has invalid version, followed by the above message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2041558/+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 2043924] [NEW] Apparently empty files when writing to NTFS partition
Public bug reported:
For some time now I have been observing strange effects on my dual-boot
system when writing to a shared NTFS partition. It is only for data and
not the partition on which Windows is installed.
The drive is mounted with these parameters:
/dev/sda1 on /media/tom/DATA type ntfs3
(rw,nosuid,nodev,relatime,uid=1000,gid=1000,iocharset=utf8,uhelper=udisks2)
[DATA]
This is my test scenario. Simply writing a file on this drive and check
the contents:
ls >ls.txt
ls -l ls*
-rw-rw-r-- 1 tom tom 0 Nov 19 11:53 ls.txt
The output of ls shows an empty file.
Checking it with more ./ls.txt shows nothing. File seems to be empty
After unmounting and mounting the drive an empty file is still shown.
Same as above.
But when I reboot the system ls shows us that the file is not empty at
all:
-rw-rw-r-- 1 tom tom 425 Nov 19 11:53 ls.txt
The content of the file is as expected.
This was working in the past. Did not tracked it but may the problems
started with the change to ntfs3 driver. I have noticed it also in
Version 23.04. Hibernation/Fast Boot is not active neither on Linux nor
on Windows.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: tom2181 F wireplumber
/dev/snd/seq:tom2167 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 19 13:55:23 2023
InstallationDate: Installed on 2018-07-01 (1967 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 001 Device 002: ID 04f2:b56d Chicony Electronics Co., Ltd HP Wide Vision HD
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=de_DE.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=1e8886f5-f232-49b1-af56-f83caee82bba ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.2
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-04 (15 days ago)
dmi.bios.date: 11/10/2020
dmi.bios.release: 15.62
dmi.bios.vendor: Insyde
dmi.bios.version: F.62
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 81D2
dmi.board.vendor: HP
dmi.board.version: KBC Version 87.21
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 87.21
dmi.modalias:
dmi:bvnInsyde:bvrF.62:bd11/10/2020:br15.62:efr87.21:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81D2:rvrKBCVersion87.21:cvnHP:ct10:cvrChassisVersion:skuZ6J78EA#ABD:
dmi.product.family: 103C_5335KV
dmi.product.name: HP ENVY Notebook
dmi.product.sku: Z6J78EA#ABD
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic wayland-session
** Description changed:
For some time now I have been observing strange effects on my dual-boot
system when writing to a shared NTFS partition. It is only for data and
not the partition on which Windows is installed.
- The drive ist mounted with these parameters:
+ The drive is mounted with these parameters:
/dev/sda1 on /media/tom/DATA type ntfs3
(rw,nosuid,nodev,relatime,uid=1000,gid=1000,iocharset=utf8,uhelper=udisks2)
[DATA]
This is my test scenario. Simply writing a file on this drive and check
the contents:
ls >ls.txt
ls -l ls*
-rw-rw-r-- 1 tom tom 0 Nov 19 11:53 ls.txt
The output of ls shows an empty file.
Checking it with more ./ls.txt shows nothing. File seems to be empty
After unmounting and mounting the drive an empty file is still shown.
Same as above.
But when I reboot the system ls shows us that the file is not empty at
all:
-rw-rw-r-- 1 tom tom 425 Nov 19 11:53 ls.txt
The content of the file is as expected.
This was working in the past. Did not tracked it but may the problems
started with the change to ntfs3 driver. I have noticed it also in
Version 23.04. Hibernation/Fast Boot is not active neither on Linux nor
on Windows.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6
[Kernel-packages] [Bug 2042868] Re: Kernel 6.2.0-36 broke RTW88 solution
I finally worked around my problem, by installing a 6.5 kernel. This again made my 'rtw88' solution work. As I see no simple way to check whether the 'official driver' would have worked for the 6.2 kernel, and I have a working 6.5 kernel (6.5.0-9-generic), I guess it might be best to close this 'bug'. For future reference/others with a similar problem: I installed the 'latest' kernel using info from https://tecadmin.net/install-linux-kernel-on-ubuntu/ Kind regards, Roel P.S. And, again, thank you Juerg for working with me on my problem. Unfortunately I am not 'fluent' enough in kernels&drivers to really test whether your advise would have worked. -- 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/2042868 Title: Kernel 6.2.0-36 broke RTW88 solution Status in linux package in Ubuntu: New Bug description: On my Linux Mint (derived from Ubuntu) system, I relied on the excellent rtw88 solution from lwfinger (https://github.com/lwfinger/rtw88) to 'fix' my Realtek Wifi Driver whenever a new kernel comes out. As I understand it, the github repository normally is 'ahead' of any kernels, so if and when I do a 'git pull' of his repository before installing the new rtw88, it should work. And this has worked for quite some time, until the 6.2.0-36 kernel came along. As lwfinger himself (?) states, "Ubuntu often modifies kernel APIs, which can cause build issues. You'll need to manually adjust the source code or look for solutions specific to your distribution. We cannot support these types of issues.", so asking him is not an option. Help? Result from version: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 (Well, this the kernel version in which I have Wifi and thus internet, the 'does not work' kernel is 6.2.0-36, supported till February 2024) Result from lscpi-vnvn (also when running the version that still has internet) as an attachment. Kind regards, Roel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042868/+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
