[Kernel-packages] [Bug 1995606] Re: Upgrade thermald to 2.5.1
@Robie, 1. is it possible that users are using thermald on hardware not covered by upstream tests? [Koba] As per my test cases, the older machine than kbl would be not covered. but thermald is enabled since 2016, i thought Intel may not support the older fully. If there's a regression, we could ask user to report on launchpad and help to fix. 2. By "all the unit tests must pass in all the supported Intel CPUs", who defines "supported"? [Koba], there's a supported CPU list in the thermald source, ~~~ @src/thd_engine.cpp, supported_ids_t id_table[] = { ... >--->---{ 6, 0x97 }, // Alderlake >--->---{ 6, 0x9a }, // Alderlake >--->---{ 6, 0xb7 }, // Raptorlake >--->---{ 6, 0xba }, // Raptorlake >--->---{ 6, 0xbf }, // Raptorlake ... } ~~~ thermald is maintained by Intel and definitely Intel define "supported". 3. Is it possible that Ubuntu users have hardware not covered by that definition of "supported"? [Koba], I think it's impossible if there's one Intel platform missed in the supported list. HWE would find it at the developing stage because thermald would complain it first then HWE would check with Intel. 4. Is there any risk to users of non-Intel hardware? [Koba] There's only one chance that you add the '--ignore-cpuid-check'. by the default, thermald would not work on non-Intel hardware. 5. How complete is upstream's test coverage? [Koba] it cover all used modules and loaded policy tables. a. used modules, rapl_control, intel_pstate, intel_powerclamp, cpufreq, processor. b. load policy table from xml file or acpi tables. c. Evaluate the temperature and check if the rules act correctly after activate/escalate/deescalate the cooling devices. 6. What assurance is there that there will be no feature regressions? i could only explain there may be corner cases for PL1 min/max feature. --- for this commit, https://github.com/intel/thermal_daemon/commit/7e490fc79d784b3faf8314af98ec14981ba7fb75 1) Is this safe in relation to Ubuntu kernel versions? [Koba] I would say it's safe on Jammy/Focal ~~~ Jammy, ~~ TCC adjustment has been offloaded to kernel driver intel_tcc_cooling, it's registered as a thermal cooling device. 2eb87d75f980) thermal/drivers/intel: Introduce tcc cooling driver. This was merged to mainline since 5.13. Focal is using hwe-5.15. Ref. https://www.phoronix.com/news/Linux-5.13-Intel-Cooling-Driver ~~ #Timo has a replied for Focal, ~~ commit fdf4f2fb8e8990c131b2b1a5a9c03681bb16e87a Author: Srinivas Pandruvada Date: Mon Jul 22 18:03:02 2019 -0700 drivers: thermal: processor_thermal_device: Export sysfs interface for TCC offset so a backport to focal (which is planned) should be safe in that regard. ~~ ~~~ 2) Did this actually get checked before upload? [Koba] i checked the related kernel commits if it's landed on Focal/Jammy. 3) What in your proposed QA process would catch this kind of change to ensure that the specific requirements for each such deprecation is met in Ubuntu [Koba] I have test cases but they are generic unit tests and a stressing test. you could check the description. btw, there may be some edge cases I didn't meet, if the issue is trigged, just ask user to report the issue and help them to fix. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1995606 Title: Upgrade thermald to 2.5.1 Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Incomplete Bug description: [Justification] The purpose of this bug is that prevent the regression in the future. The automatic test scripts are better for the future SRU and is still on the planning. [Test case] For each supported CPU series (RPL/ADL/TGL/CML/CFL/KBL) the following tests will be run on machines in the CI lab: 1. Run stress-ng, and observe the temperature/frequency/power with s-tui - Temperatures should stay just below trip values - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) 2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. - this depends on if acpi_thermal_rel exist. - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto" could be landed in etc/thermald/. - if not, the user-defined xml could be created, then jump to (3). - run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly. 3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. - run thermald with --loglevel=debug,
[Kernel-packages] [Bug 1995763] Re: package linux-firmware 20220329.git681281e4-0ubuntu3.5 failed to install/upgrade: unable to stat './lib/firmware/ath11k' (which was about to be installed): Erro de
You seem to have HW problems: [ 115.420460] blk_update_request: critical medium error, dev nvme0n1, sector 806095368 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 [ 115.420488] EXT4-fs warning (device nvme0n1p2): ext4_dx_find_entry:1748: inode #17434151: lblock 10: comm preinst: error -5 reading directory block [ 115.704518] blk_update_request: critical medium error, dev nvme0n1, sector 806095368 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 [ 115.704552] EXT4-fs warning (device nvme0n1p2): ext4_dx_find_entry:1748: inode #17434151: lblock 10: comm dpkg: error -5 reading directory block ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- 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/1995763 Title: package linux-firmware 20220329.git681281e4-0ubuntu3.5 failed to install/upgrade: unable to stat './lib/firmware/ath11k' (which was about to be installed): Erro de entrada/saída Status in linux-firmware package in Ubuntu: Invalid Bug description: My mousepad isnt working ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.5 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: airton 3093 F pulseaudio /dev/snd/controlC0: airton 3093 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Sat Nov 5 10:46:30 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu3 ErrorMessage: unable to stat './lib/firmware/ath11k' (which was about to be installed): Erro de entrada/saída InstallationDate: Installed on 2022-06-14 (144 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Dell G15 5511 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=db51df0b-3234-4431-94aa-51e3a43df4f1 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. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7 SourcePackage: linux-firmware Title: package linux-firmware 20220329.git681281e4-0ubuntu3.5 failed to install/upgrade: unable to stat './lib/firmware/ath11k' (which was about to be installed): Erro de entrada/saída UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2022 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.1 dmi.board.name: 0VDFD7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.1:bd02/17/2022:br1.11:svnDellInc.:pnDellG155511:pvr:rvnDellInc.:rn0VDFD7:rvrA01:cvnDellInc.:ct10:cvr:sku0A71: dmi.product.family: GSeries dmi.product.name: Dell G15 5511 dmi.product.sku: 0A71 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1995763/+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 1975501] Re: bfq_deactivate_entity: NULL pointer dereference
Hi. Problem still appear on 5.4.0-125 kernel version. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1975501 Title: bfq_deactivate_entity: NULL pointer dereference Status in linux-hwe package in Ubuntu: New Bug description: Hello. We meet a kernel panic with next trace: bfq_insert+0x5c/0x70 [bfq] __bfq_deactivate_entity+0xe7/0x1b0 [bfq] bfq_deactivate_entity+0x5d/0xd0 [bfq] bfq_del_bfqq_busy+0xac/0x150 [bfq] __bfq_bfqq_expire+0x64/0xd0 [bfq] bfq_bfqq_expire+0x331/0x930 [bfq] ? try_to_wake_up+0x235/0x5f0 ? bfq_dispatch_request+0xf70/0xf70 [bfq] bfq_idle_slice_timer+0x6d/0xc0 [bfq] __hrtimer_run_queues+0x10f/0x280 hrtimer_interrupt+0xe7/0x230 smp_apic_timer_interrupt+0x6f/0x130 apic_timer_interrupt+0xf/0x20 After little research i found out that bug was reported by Fedora and openSUSE community earlier. https://bugzilla.redhat.com/show_bug.cgi?id=2022819 https://bugzilla.opensuse.org/show_bug.cgi?id=1192714 And patch for this bug already exist https://lore.kernel.org/all/20220401102325.17617-1-j...@suse.cz/ Since there are no similar reports in the Ubuntu community, I decided to make this report. Full dmesg log in attachments. Also have a crash dump file, can attach that file if it necessary. Environment: Distributor ID: Ubuntu Description: Ubuntu 18.04.6 LTS Release: 18.04 Codename: bionic kernel: 5.4.0-110-generic #124~18.04.1-Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1975501/+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 1956533] Re: Printing anything to /dev/lp0 makes Ubuntu Server 20.04 crash
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1956533 Title: Printing anything to /dev/lp0 makes Ubuntu Server 20.04 crash Status in linux package in Ubuntu: Expired Bug description: Whenever I try to print anything to /dev/lp0 (the parallel port of my ASUS M5A78L-M LE mainboard), my Ubuntu 20.04 server freezes completely (display gets black, no keyboard input, no network reaction). Thereby it doesn't matter whether I try printing a testpage in the webinterface of CUPS (http://localhost:631), trying to print a Windows 10 test page from a SaMBa client or try entering 'echo "Test" > /dev/lp0' on the console. When trying the latter, my HP LaserJet 6L printer prints 'Te', so a little bit of the print job seams to come out before the crash. In /var/log/syslog, there are no entries about the crash (I tried waiting 5 minutes, then do the echo test, then wait another 5 minutes before restarting to be able to isolate any possible entries caused by the crash clearly by the time stamp, but there aren't any). As a workaround, I installed a DELOCK 90413 'Serial + Parallel PCI Express x1 Card' into my server, which is recognized as /dev/lp1. When using this parallel port, printing works perfectly. In my old hardware with another mainboard, the same installation (I just changed hard disks) worked perfectly with the internal /dev/lp0. I also tried printing to the problematic parallel port on my new server hardware (the problematic one) using FreeDOS 1.3, just to confirm that my hardware is not defective, and it worked perfectly. So Ubuntu 20.04 seems to have a problem with the internal parallel port of the ASUS M5A78L-M LE mainboard. Unfortunately, I cannot tell which package is affected as I can't find any log entries. However, I guess, it's not cups, as a direct echo to /dev/lp0 also does not work. So I guess, it's something deeper. What you also need: 1) Ubuntu 20.04.3 LTS 2) I don'd know. Sorry. 3) When printing to /dev/lp0, a page should come out of the printer. 4) When printing to /dev/lp0, the whole system crashed (display black, no reaction to anything). If I can provide you further information to fix this bug, please don't hesitate to contact me. However, you need to help me how to gather it, as all my ideas are already described above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956533/+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 1982604] Re: PROBLEM: Programs
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1982604 Title: PROBLEM: Programs Status in linux package in Ubuntu: Expired Bug description: When I tried to login to the machine, the SSH login took more than 5 minutes. After login, the CPU load was 7.x for a 4 CPU machine, however the htop program did not indicate all CPUs running 100%. Many programs were showing (e.g. zsh, docker, ssh, etc). I cannot reboot using `sudo reboot` or `shutdown -r` commands. I cannot kill the docker containers. I had to hard reset the machine. Found some bug reported in the journalctl. Attached the relevant logs. uname -a : Linux skynet 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982604/+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 1987606] Re: Ubuntu 22.04 some times does not resume from sleep that I have to hard-reset the system.
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1987606 Title: Ubuntu 22.04 some times does not resume from sleep that I have to hard-reset the system. Status in linux package in Ubuntu: Expired Bug description: Sometimes the system does NOT resume from sleep properly for some reason that I have to press the power button to hard-reset. This sucks! Please see attached picture for the screen. "Timed out waiting for suspend events" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987606/+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 1995606] Re: Upgrade thermald to 2.5.1
@Timo, i have finished.thanks ~~~ [ Where problems could occur ] ~~~ ** Description changed: [Justification] The purpose of this bug is that prevent the regression in the future. The automatic test scripts are better for the future SRU and is still on the planning. [Test case] For each supported CPU series (RPL/ADL/TGL/CML/CFL/KBL) the following tests will be run on machines in the CI lab: 1. Run stress-ng, and observe the temperature/frequency/power with s-tui - Temperatures should stay just below trip values - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) 2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. - this depends on if acpi_thermal_rel exist. - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto" could be landed in etc/thermald/. - if not, the user-defined xml could be created, then jump to (3). - run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly. 3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. - run thermald with --loglevel=debug, and compare the log with xml files. - if parsed correctly, the configurations from XML files would appear in the log. 4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. - rapl.sh - intel_pstate.sh - powerclamp.sh - processor.sh 5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 6. check if system would be throttled even the temperature is under the trip-points. [ Where problems could occur ] + since the PL1 min/max is introduced, we may face the edge case in the future. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1995606 Title: Upgrade thermald to 2.5.1 Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Incomplete Bug description: [Justification] The purpose of this bug is that prevent the regression in the future. The automatic test scripts are better for the future SRU and is still on the planning. [Test case] For each supported CPU series (RPL/ADL/TGL/CML/CFL/KBL) the following tests will be run on machines in the CI lab: 1. Run stress-ng, and observe the temperature/frequency/power with s-tui - Temperatures should stay just below trip values - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) 2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. - this depends on if acpi_thermal_rel exist. - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto" could be landed in etc/thermald/. - if not, the user-defined xml could be created, then jump to (3). - run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly. 3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. - run thermald with --loglevel=debug, and compare the log with xml files. - if parsed correctly, the configurations from XML files would appear in the log. 4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. - rapl.sh - intel_pstate.sh - powerclamp.sh - processor.sh 5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 6. check if system would be throttled even the temperature is under the trip-points. [ Where problems could occur ] since the PL1 min/max is introduced, we may face the edge case in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1995606/+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 1995606] Re: Upgrade thermald to 2.5.1
@Robie, For the TCC, I have replied fo Jamssy, ~~~ TCC adjustment has been offloaded to kernel driver intel_tcc_cooling, it's registered as a thermal cooling device. 2eb87d75f980) thermal/drivers/intel: Introduce tcc cooling driver. This was merged to mainline since 5.13. Focal is using hwe-5.15. Ref. https://www.phoronix.com/news/Linux-5.13-Intel-Cooling-Driver ~~~ Timo has a replied for Focal, ~~~ commit fdf4f2fb8e8990c131b2b1a5a9c03681bb16e87a Author: Srinivas Pandruvada Date: Mon Jul 22 18:03:02 2019 -0700 drivers: thermal: processor_thermal_device: Export sysfs interface for TCC offset so a backport to focal (which is planned) should be safe in that regard. ~~~ Is there any question I missed? thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1995606 Title: Upgrade thermald to 2.5.1 Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Incomplete Bug description: [Justification] The purpose of this bug is that prevent the regression in the future. The automatic test scripts are better for the future SRU and is still on the planning. [Test case] For each supported CPU series (RPL/ADL/TGL/CML/CFL/KBL) the following tests will be run on machines in the CI lab: 1. Run stress-ng, and observe the temperature/frequency/power with s-tui - Temperatures should stay just below trip values - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) 2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. - this depends on if acpi_thermal_rel exist. - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto" could be landed in etc/thermald/. - if not, the user-defined xml could be created, then jump to (3). - run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly. 3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. - run thermald with --loglevel=debug, and compare the log with xml files. - if parsed correctly, the configurations from XML files would appear in the log. 4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. - rapl.sh - intel_pstate.sh - powerclamp.sh - processor.sh 5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 6. check if system would be throttled even the temperature is under the trip-points. [ Where problems could occur ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1995606/+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
** Summary changed: - Crash after monitor wake + kernel NULL pointer dereference after monitor wake -- 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, address: 0008 Oct 28 12:24:11 desktop kernel: #PF: supervisor read access in kernel mode Oct 28 12:24:11
[Kernel-packages] [Bug 1916988] Re: Internal microphone not being recognized on Lenovo Yoga Slim 7 after kernel upgrade
My headset microphone is not recognized on Kinetic (Bluetooth works). This is my laptop: Manufacturer: LENOVO Product Name: 82MS Version: Yoga Slim 7 Pro 14ACH5 SKU Number: LENOVO_MT_82MS_BU_idea_FM_Yoga Slim 7 Pro 14ACH5 It seems this commit fixes the issue but I didn't test it yet: https://github.com/torvalds/linux/commit/2232b2dd8cd4f1e6d554b2c3f6899ce36f791b67 Relevant discussion: https://bugzilla.kernel.org/show_bug.cgi?id=216299 ** Bug watch added: Linux Kernel Bug Tracker #216299 https://bugzilla.kernel.org/show_bug.cgi?id=216299 -- 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/1916988 Title: Internal microphone not being recognized on Lenovo Yoga Slim 7 after kernel upgrade Status in linux package in Ubuntu: Confirmed Bug description: After updating some packages which included a new version of kernel (5.8.0-44-generic) the internal microphone of my Lenovo Yoga Slim 7 does not work anymore and it doesn't seem to be recognized in Settings->Sound (I attached a screenshot) 1. ~$ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 2. ~# apt-cache policy linux-image-5.8.0-44-generic linux-image-5.8.0-44-generic: Installed: 5.8.0-44.50~20.04.1 Candidate: 5.8.0-44.50~20.04.1 Version table: *** 5.8.0-44.50~20.04.1 500 500 http://at.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 3. Expected internal microphone to work 4. Internal microphone not working --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stefan 1690 F pulseaudio /dev/snd/controlC0: stefan 1690 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-15 (10 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 82A2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=06bbabdd-494d-48b9-b17e-31cb56c8ff0f ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.187.9 Tags: focal Uname: Linux 5.8.0-44-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 01/18/2020 dmi.bios.release: 1.38 dmi.bios.vendor: LENOVO dmi.bios.version: DMCN38WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14ARE05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDMCN38WW:bd01/18/2020:br1.38:efr1.29:svnLENOVO:pn82A2:pvrYogaSlim714ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrYogaSlim714ARE05: dmi.product.family: Yoga Slim 7 14ARE05 dmi.product.name: 82A2 dmi.product.sku: LENOVO_MT_82A2_BU_idea_FM_Yoga Slim 7 14ARE05 dmi.product.version: Yoga Slim 7 14ARE05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stefan 1690 F pulseaudio /dev/snd/controlC0: stefan 1690 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-15 (10 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Package: alsa-base 1.0.25+dfsg-0ubuntu5 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: third-party-packages focal Uname: Linux 5.8.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/18/2020 dmi.bios.release: 1.38 dmi.bios.vendor: LENOVO dmi.bios.version: DMCN38WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag:
[Kernel-packages] [Bug 1995798] Re: MT7921K high latency when bluetooth headset is used
** Bug watch added: Linux Kernel Bug Tracker #216668 https://bugzilla.kernel.org/show_bug.cgi?id=216668 ** Also affects: bluez via https://bugzilla.kernel.org/show_bug.cgi?id=216668 Importance: Unknown Status: Unknown ** Project changed: bluez => linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1995798 Title: MT7921K high latency when bluetooth headset is used Status in Linux: Unknown Status in bluez package in Ubuntu: New Bug description: When I use onboard WiFi and Bluetooth headset at the same time, the latency goes from ~30-50ms to 200-6500ms Motherboard: ASUS TUF GAMING X670E-PLUS WIFI BIOS: 0809 Kernels tested: Ubuntu 22.10 downstream kernel (5.19) and upstream 6.0.[135] $ lsb_release -rd Description: Ubuntu 22.10 Release: 22.10 Also made upstream kernel bz: https://bugzilla.kernel.org/show_bug.cgi?id=216668 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: bluez 5.65-0ubuntu1 Uname: Linux 6.0.5-060005-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 6 15:44:14 2022 InstallationDate: Installed on 2022-10-15 (22 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.5-060005-generic root=/dev/mapper/vg_system-lv_root_ubuntu ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2022 dmi.bios.release: 8.9 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0809 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X670E-PLUS WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0809:bd10/23/2022:br8.9:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX670E-PLUSWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS hciconfig: hci0:Type: Primary Bus: USB BD Address: 10:6F:D9:DD:4A:B0 ACL MTU: 1021:6 SCO MTU: 240:8 UP RUNNING PSCAN RX bytes:23811976 acl:17760 sco:359584 events:24845 errors:0 TX bytes:22808883 acl:832 sco:352705 commands:4782 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1995798/+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 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)
Been using 22.10 for several days on X11, enabled Wayland and have discovered that my screen flickers and app windows fail to render correctly. Tried the 2 GRUB parameters mentioned above - with no success. Going back to X11 and a usable machine, hopefully this is fixed soon - happy to try any fixes if offered. -- 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/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later) Status in linux package in Ubuntu: Fix Released Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel paramater intel_idle.max_cstate=4 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+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 1995798] Re: MT7921K high latency when bluetooth headset is used
** Package changed: ubuntu => bluez (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1995798 Title: MT7921K high latency when bluetooth headset is used Status in bluez package in Ubuntu: New Bug description: When I use onboard WiFi and Bluetooth headset at the same time, the latency goes from ~30-50ms to 200-6500ms Motherboard: ASUS TUF GAMING X670E-PLUS WIFI BIOS: 0809 Kernels tested: Ubuntu 22.10 downstream kernel (5.19) and upstream 6.0.[135] $ lsb_release -rd Description: Ubuntu 22.10 Release: 22.10 Also made upstream kernel bz: https://bugzilla.kernel.org/show_bug.cgi?id=216668 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: bluez 5.65-0ubuntu1 Uname: Linux 6.0.5-060005-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 6 15:44:14 2022 InstallationDate: Installed on 2022-10-15 (22 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.5-060005-generic root=/dev/mapper/vg_system-lv_root_ubuntu ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2022 dmi.bios.release: 8.9 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0809 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X670E-PLUS WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0809:bd10/23/2022:br8.9:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX670E-PLUSWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS hciconfig: hci0:Type: Primary Bus: USB BD Address: 10:6F:D9:DD:4A:B0 ACL MTU: 1021:6 SCO MTU: 240:8 UP RUNNING PSCAN RX bytes:23811976 acl:17760 sco:359584 events:24845 errors:0 TX bytes:22808883 acl:832 sco:352705 commands:4782 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1995798/+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 1995798] [NEW] MT7921K high latency when bluetooth headset is used
You have been subscribed to a public bug: When I use onboard WiFi and Bluetooth headset at the same time, the latency goes from ~30-50ms to 200-6500ms Motherboard: ASUS TUF GAMING X670E-PLUS WIFI BIOS: 0809 Kernels tested: Ubuntu 22.10 downstream kernel (5.19) and upstream 6.0.[135] $ lsb_release -rd Description:Ubuntu 22.10 Release:22.10 Also made upstream kernel bz: https://bugzilla.kernel.org/show_bug.cgi?id=216668 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: bluez 5.65-0ubuntu1 Uname: Linux 6.0.5-060005-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 6 15:44:14 2022 InstallationDate: Installed on 2022-10-15 (22 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.5-060005-generic root=/dev/mapper/vg_system-lv_root_ubuntu ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2022 dmi.bios.release: 8.9 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0809 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X670E-PLUS WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0809:bd10/23/2022:br8.9:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX670E-PLUSWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS hciconfig: hci0: Type: Primary Bus: USB BD Address: 10:6F:D9:DD:4A:B0 ACL MTU: 1021:6 SCO MTU: 240:8 UP RUNNING PSCAN RX bytes:23811976 acl:17760 sco:359584 events:24845 errors:0 TX bytes:22808883 acl:832 sco:352705 commands:4782 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- MT7921K high latency when bluetooth headset is used https://bugs.launchpad.net/bugs/1995798 You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez 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 1995606] Re: Upgrade thermald to 2.5.1
Thank you for the re-upload. I think this remains blocked on answers to my questions in https://lists.ubuntu.com/archives/ubuntu- release/2022-October/005495.html ? ** Changed in: thermald (Ubuntu Jammy) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1995606 Title: Upgrade thermald to 2.5.1 Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Incomplete Bug description: [Justification] The purpose of this bug is that prevent the regression in the future. The automatic test scripts are better for the future SRU and is still on the planning. [Test case] For each supported CPU series (RPL/ADL/TGL/CML/CFL/KBL) the following tests will be run on machines in the CI lab: 1. Run stress-ng, and observe the temperature/frequency/power with s-tui - Temperatures should stay just below trip values - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) 2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. - this depends on if acpi_thermal_rel exist. - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto" could be landed in etc/thermald/. - if not, the user-defined xml could be created, then jump to (3). - run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly. 3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. - run thermald with --loglevel=debug, and compare the log with xml files. - if parsed correctly, the configurations from XML files would appear in the log. 4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. - rapl.sh - intel_pstate.sh - powerclamp.sh - processor.sh 5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 6. check if system would be throttled even the temperature is under the trip-points. [ Where problems could occur ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1995606/+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 1987269] Re: [5.18.0 mainline] mlx5 deadlock
I have received information about this issue possibly fixed by https://patchwork.kernel.org/project/netdevbpf/patch/20220510055743.118828-7-sae...@nvidia.com/ Pending confirmation ** Changed in: linux (Ubuntu) Status: Expired => Incomplete -- 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/1987269 Title: [5.18.0 mainline] mlx5 deadlock Status in linux package in Ubuntu: Incomplete Bug description: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy $ uname -a Linux pc1-rb3-n3 5.18.0-051800-generic #202205222030 SMP PREEMPT_DYNAMIC Sun May 22 20:33:46 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.735461] INFO: task ovn-controller:30439 blocked for more than 120 seconds. Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.742835] Not tainted 5.18.0-051800-generic #202205222030 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.749051] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757010] task:ovn-controller state:D stack:0 pid:30439 ppid: 1 flags:0x0002 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757019] Call Trace: Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757024] Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757031] __schedule+0x246/0x5c0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757045] schedule+0x55/0xc0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757050] schedule_preempt_disabled+0x15/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757057] __mutex_lock.constprop.0+0x2f3/0x4c0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757064] __mutex_lock_slowpath+0x13/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757069] mutex_lock+0x35/0x40 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757073] rtnetlink_rcv_msg+0x114/0x3f0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757082] ? rtnl_calcit.isra.0+0x140/0x140 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757087] netlink_rcv_skb+0x56/0x100 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757095] rtnetlink_rcv+0x15/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757099] netlink_unicast+0x236/0x350 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757104] netlink_sendmsg+0x25e/0x4d0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757109] sock_sendmsg+0x66/0x70 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757117] sys_sendmsg+0x24f/0x290 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757123] ? import_iovec+0x1b/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757130] ? sendmsg_copy_msghdr+0x7c/0xa0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757137] ___sys_sendmsg+0x81/0xc0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757143] ? ___sys_recvmsg+0x99/0x110 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757148] ? netdev_name_node_lookup_rcu+0x6b/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757155] ? fput+0x13/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757161] ? __sys_sendmsg+0x98/0xb0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757166] ? __fget_light+0xa7/0x130 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757174] __sys_sendmsg+0x62/0xb0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757180] __x64_sys_sendmsg+0x1d/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757186] do_syscall_64+0x5c/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757191] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757194] ? syscall_exit_to_user_mode+0x26/0x50 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757200] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757203] ? exit_to_user_mode_prepare+0x37/0xb0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757210] ? syscall_exit_to_user_mode+0x26/0x50 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757214] ? __x64_sys_write+0x19/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757220] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757224] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757227] entry_SYSCALL_64_after_hwframe+0x44/0xae Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757232] RIP: 0033:0x7f571f927b4d Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757239] RSP: 002b:7ffd50fa8ec0 EFLAGS: 0293 ORIG_RAX: 002e Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757246] RAX: ffda RBX: 0001 RCX: 7f571f927b4d Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757252] RDX: RSI: 7ffd50fa8f50 RDI: 0020 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757255] RBP: 7ffd50fa9c40 R08: R09: 55e1a6a66f60 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757260] R10: 0001 R11: 0293 R12: Aug 22 01:15:02 pc1-rb3-n3 kernel:
[Kernel-packages] [Bug 1995793] Re: [Dell XPS 15 9500] Cannot resume after suspend
** Attachment added: "lspci-vnvn.log, version.log and prevboot.txt (journalctl -b-1) files" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995793/+attachment/5629436/+files/debug-dell-xps.zip ** Attachment removed: "lspci-vnvn.log, version.log and prevboot.txt (journalctl -b-1) files" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995793/+attachment/5629413/+files/debug-dell-xps.zip -- 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/1995793 Title: [Dell XPS 15 9500] Cannot resume after suspend Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 22.04, system resume fails randomly with message displayed on the screen: ``` dell-xps kernel: Bluetooth: hci0: Timed out waiting for suspend events dell-xps kernel: Bluetooth: hci0: Suspend timeout bit: 6 dell-xps kernel: Bluetooth: hci0: Suspend notifier action (3) failed: -110 ``` After this, I haven't found any other solution to resume the system. Hard restart with power button is needed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-52-generic 5.15.0-52.58 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 6 12:41:53 2022 InstallationDate: Installed on 2022-02-23 (255 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. XPS 15 9500 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-52-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-10-19 (17 days ago) dmi.bios.date: 12/08/2021 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0RHXRG dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd12/08/2021:br1.12:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn0RHXRG:rvrA03:cvnDellInc.:ct10:cvr:sku097D: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995793/+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 1995793] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1995793 Title: [Dell XPS 15 9500] Cannot resume after suspend Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 22.04, system resume fails randomly with message displayed on the screen: ``` dell-xps kernel: Bluetooth: hci0: Timed out waiting for suspend events dell-xps kernel: Bluetooth: hci0: Suspend timeout bit: 6 dell-xps kernel: Bluetooth: hci0: Suspend notifier action (3) failed: -110 ``` After this, I haven't found any other solution to resume the system. Hard restart with power button is needed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-52-generic 5.15.0-52.58 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 6 12:41:53 2022 InstallationDate: Installed on 2022-02-23 (255 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. XPS 15 9500 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-52-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-10-19 (17 days ago) dmi.bios.date: 12/08/2021 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0RHXRG dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd12/08/2021:br1.12:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn0RHXRG:rvrA03:cvnDellInc.:ct10:cvr:sku097D: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995793/+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 1995793] [NEW] [Dell XPS 15 9500] Cannot resume after suspend
Public bug reported: After upgrading to Ubuntu 22.04, system resume fails randomly with message displayed on the screen: ``` dell-xps kernel: Bluetooth: hci0: Timed out waiting for suspend events dell-xps kernel: Bluetooth: hci0: Suspend timeout bit: 6 dell-xps kernel: Bluetooth: hci0: Suspend notifier action (3) failed: -110 ``` After this, I haven't found any other solution to resume the system. Hard restart with power button is needed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-52-generic 5.15.0-52.58 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 6 12:41:53 2022 InstallationDate: Installed on 2022-02-23 (255 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. XPS 15 9500 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-52-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-10-19 (17 days ago) dmi.bios.date: 12/08/2021 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0RHXRG dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd12/08/2021:br1.12:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn0RHXRG:rvrA03:cvnDellInc.:ct10:cvr:sku097D: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy ** Attachment added: "lspci-vnvn.log, version.log and prevboot.txt (journalctl -b-1) files" https://bugs.launchpad.net/bugs/1995793/+attachment/5629413/+files/debug-dell-xps.zip -- 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/1995793 Title: [Dell XPS 15 9500] Cannot resume after suspend Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 22.04, system resume fails randomly with message displayed on the screen: ``` dell-xps kernel: Bluetooth: hci0: Timed out waiting for suspend events dell-xps kernel: Bluetooth: hci0: Suspend timeout bit: 6 dell-xps kernel: Bluetooth: hci0: Suspend notifier action (3) failed: -110 ``` After this, I haven't found any other solution to resume the system. Hard restart with power button is needed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-52-generic 5.15.0-52.58 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 6 12:41:53 2022 InstallationDate: Installed on 2022-02-23 (255 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. XPS 15 9500 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-52-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-10-19 (17 days ago) dmi.bios.date: 12/08/2021 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0RHXRG dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd12/08/2021:br1.12:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn0RHXRG:rvrA03:cvnDellInc.:ct10:cvr:sku097D: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995793/+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 1995320] Re: [amdgpu] intermittent green static
** Tags added: regression-release -- 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/1995320 Title: [amdgpu] intermittent green static Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from 22.04 to 22.10 I've been seeing some display glitches. - green static appears, usually when scrolling, regular sized green blocks, like giant pixels - firefox not refreshing when full screen video plays (separate windows, separate screens) I would guess I probably have the wrong package here, but there's no way for me to tell if it's mesa, the kernel, gnome-shell, or something else. Radeon 6700XT Dual displays Wayland ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 31 21:46:03 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (1231 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2019-06-18 (1232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/infodata-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 RfKill: Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995320/+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