[Kernel-packages] [Bug 2017955] [NEW] Realtek Ethernet 8125 will disconnect randomly from Ethernet
Public bug reported: Will leave on a youtube vid overnight playing music and sometime during the night the ethernet will turn off and i have to reboot the machine to get back out to the internet. It will not reconnect to the hardware. Sometimes it's 10 mins till it turns off, sometimes it's an hour or more. Been playing with kernels and picked the 6.1.5 kernel at random and there are no disconnects My hardware is an Aorus Elite Z690 AX DDR4 running the F22 kernel. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-40-generic 5.19.0-40.41~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 27 23:46:06 2023 InstallationDate: Installed on 2022-03-05 (418 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2017955 Title: Realtek Ethernet 8125 will disconnect randomly from Ethernet Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: Will leave on a youtube vid overnight playing music and sometime during the night the ethernet will turn off and i have to reboot the machine to get back out to the internet. It will not reconnect to the hardware. Sometimes it's 10 mins till it turns off, sometimes it's an hour or more. Been playing with kernels and picked the 6.1.5 kernel at random and there are no disconnects My hardware is an Aorus Elite Z690 AX DDR4 running the F22 kernel. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-40-generic 5.19.0-40.41~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 27 23:46:06 2023 InstallationDate: Installed on 2022-03-05 (418 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2017955/+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 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
I'm getting increasingly frustrated by this bug. I've been patiently monitoring this bug since it began, with no audio on my media and games server and having to learn how to revert to previous kernels (which was actually fun) just to get audio. I am a developer myself and understand the problems with point release distro's. But for something as crucial as having sound over HDMI, I find it crazy that so many users are waiting for nearly 2 months now (almost a month after the fix was released to mainline). I'm getting very close to formatting the entire hard drive and replacing Ubuntu with a rolling release arch distro. -- 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/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Committed Bug description: [Impact] For amdgpu/i915, hdmi audio output device has disappeared. [Fix] The latest fix for the non-contiguous memalloc helper changed the allocation method for a non-IOMMU system to use only the fallback allocator. This should have worked, but it caused a problem sometimes when too many non-contiguous pages are allocated that can't be treated by HD-audio controller. As a quirk workaround, go back to the original strategy: use dma_alloc_noncontiguous() at first, and apply the fallback only when it fails, but only for non-IOMMU case [Test Case] 1. boot with kernel applied the patches. 2. check the cards in /proc/asound/cards. Get the hdmi cards. 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xe232 irq 137 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xe226 irq 134 [Where problems could occur] Low, this is just workaround and may have a better solution in the future. [Misc] All patches has been landed on OEM-6.1 and lunar. ~~ CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. Currently known affected cards: * HD 7700 (comment 8) * R9 290 (comment 21) * RX 550 (LP: #2012141, and comment 27) * RX 570 (mine) * RX 580 (LP: #2009276, and comment 28) * WX 3200 (comment 29) * RX 6600 (LP: #2009542) * RX 6700 (LP: #2009275) [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 1069350] Re: suspicious /.rpmdb root directory
** Changed in: dkms (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1069350
Title:
suspicious /.rpmdb root directory
Status in RPM:
Opinion
Status in dkms package in Ubuntu:
Confirmed
Status in rpm package in Ubuntu:
Fix Released
Status in dkms source package in Trusty:
Confirmed
Status in rpm source package in Trusty:
Confirmed
Status in dkms package in Debian:
Fix Released
Status in rpm package in Debian:
Fix Released
Bug description:
I have the following directory structure on my system which conflicts
to the LSB standard:
ls -ld /.rpmdb/{,*}
drwxr-xr-x 2 root root 4096 Okt 21 2011 /.rpmdb/
-rw-r--r-- 1 root root 8192 Okt 21 2011 /.rpmdb/Basenames
-rw-r--r-- 1 root root 8192 Okt 21 2011 /.rpmdb/Conflictname
-rw-r--r-- 1 root root24576 Apr 27 00:52 /.rpmdb/__db.001
-rw-r--r-- 1 root root 4096000 Apr 27 00:52 /.rpmdb/__db.002
-rw-r--r-- 1 root root 83894272 Apr 27 00:52 /.rpmdb/__db.003
-rw-r--r-- 1 root root 811008 Apr 27 00:52 /.rpmdb/__db.004
-rw-r--r-- 1 root root 8192 Okt 21 2011 /.rpmdb/Dirnames
-rw-r--r-- 1 root root 8192 Okt 21 2011 /.rpmdb/Group
-rw-r--r-- 1 root root 8192 Okt 21 2011 /.rpmdb/Installtid
-rw-r--r-- 1 root root 8192 Okt 21 2011 /.rpmdb/Name
-rw-r--r-- 1 root root 8192 Okt 21 2011 /.rpmdb/Obsoletename
-rw-r--r-- 1 root root12288 Okt 21 2011 /.rpmdb/Packages
-rw-r--r-- 1 root root 8192 Okt 21 2011 /.rpmdb/Providename
-rw-r--r-- 1 root root 8192 Okt 21 2011 /.rpmdb/Requirename
-rw-r--r-- 1 root root 8192 Okt 21 2011 /.rpmdb/Sha1header
-rw-r--r-- 1 root root 8192 Okt 21 2011 /.rpmdb/Sigmd5
-rw-r--r-- 1 root root 8192 Okt 21 2011 /.rpmdb/Triggername
Afaik, this directory belongs to rpm or alien. Maybe it appears
because of a lack of environment variables (e.g. $HOME not set) in
particular situations.
As you can see in the listing, the directory is not used frequently,
but I'm not sure if it's save to delete it. Maybe the problem is
already solved in the current version of ubuntu (at last the time the
files were touched I was running Ubuntu 11.10), but I think it's
important to have this bug registered so other users can find it.
There is an active thread about it at ubuntuforums:
http://ubuntuforums.org/showthread.php?t=1864423
To manage notifications about this bug go to:
https://bugs.launchpad.net/rpm/+bug/1069350/+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 2007579] Re: Raptor Lake Thermald ITMT version 2 support
@ahasenack, i didn't mention the test plan section. just run the candidate on the target and observe the behavior. I will check it. -- 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/2007579 Title: Raptor Lake Thermald ITMT version 2 support Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Bionic: Won't Fix Status in thermald source package in Focal: Won't Fix Status in thermald source package in Jammy: In Progress Status in thermald source package in Kinetic: Fix Committed Status in thermald source package in Lunar: Fix Released Bug description: == SRU Justification Kinetic == Raptor Lake system uses ITMT v2 instead of V1 for thermal configuration via GDDV. This was observed on Dell XPS 9320 system. Because thermald can't parse V2 table, it is not getting correct thermal threshold temperature and power limits. == The Fix == This is fixed in upstream thermald by the patch: https://github.com/intel/thermal_daemon/commit/90d56bc06cdcf78e7398ea7da389401516591774 This fix is part of Thermald 2.5.2 release. The fix applies cleanly and this is already in Ubuntu Lunar in thermald 2.5.2. The fix checks for illegal ITMT version and handles version 2 as a specific exceptional case. == Regression Risks == For systems that do not used ITMT, no change in behaviour will occur. Systems with versions > 2 (currently not valid) will not have ITMT parsed anymore; this will avoid misinterpreting unsupported ITMT data. Finally, version 2 of ITMT will be now parsed differently and additional fields will be parsed and these will be ignored as intended. == Test Plan == Test against a Dell XPS 9320 system. See if it handles the ITMT correctly. The thermald log should indicate version 2 is being used with the message: "ignore dummy_str: ds d1 d2 d3 " where ds = a string, d1 .. d3 are uint64 values that are parsed and ignored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2007579/+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 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
@Korba, I have to repeat me, I did work for Avionic, Automotive Industry, but if someone would voice this statement : "If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed." The caller would be dropped ! -- 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/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Committed Bug description: [Impact] For amdgpu/i915, hdmi audio output device has disappeared. [Fix] The latest fix for the non-contiguous memalloc helper changed the allocation method for a non-IOMMU system to use only the fallback allocator. This should have worked, but it caused a problem sometimes when too many non-contiguous pages are allocated that can't be treated by HD-audio controller. As a quirk workaround, go back to the original strategy: use dma_alloc_noncontiguous() at first, and apply the fallback only when it fails, but only for non-IOMMU case [Test Case] 1. boot with kernel applied the patches. 2. check the cards in /proc/asound/cards. Get the hdmi cards. 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xe232 irq 137 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xe226 irq 134 [Where problems could occur] Low, this is just workaround and may have a better solution in the future. [Misc] All patches has been landed on OEM-6.1 and lunar. ~~ CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. Currently known affected cards: * HD 7700 (comment 8) * R9 290 (comment 21) * RX 550 (LP: #2012141, and comment 27) * RX 570 (mine) * RX 580 (LP: #2009276, and comment 28) * WX 3200 (comment 29) * RX 6600 (LP: #2009542) * RX 6700 (LP: #2009275) [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 for Jammy (22.04)
Hi there! Sorry for the delay in getting to this. Some review: *) It'd be easier to review if debian/changelog mentioned each of the patches and what they do. For example, rather than having the changelog entry: * Support ITMTv2 for Raptor Lake (LP: #2007579) you could have the changelog entries: * debian/patches/0003-Parse-ITMT-Table.patch: * debian/patches/0006-Install-ITMT-target.patch: * debian/patches/0018-Process-ITMT-v2.patch: - Support ITMTv2 for Raptor Lake (LP: #2007579) Since you know why you selected the patches you've added, this means I don't need to try and reverse-engineer what bug each of the patches is trying to address. *) 0015-Ensure-there-is-one-trips-element-per-zone.patch: Why is this patch here? It looks to me like it's patching code that we don't build? Overall this looks like it's mostly there; it's not entirely clear to me what *all* the patches are for, but it looks like they're (mostly) sensible patches. -- 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 for Jammy (22.04) Status in OEM Priority Project: New Status in thermald package in Ubuntu: New 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 these 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, there may have some cases that don't check the minimum of PL1 then make PL1 to smaller and smaller and throttle the CPU. this may cause machines run like the old behavior that doesn't have PL1 min/max. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+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 2017944] Re: Screen Periodicly Flickering
Why does the your bug report give away information like my username and hostname? I have tried to edit them away, but some sort of bot keeps updating it. I would rather not have my hostname and username just being displayed publicly to the world -- 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/2017944 Title: Screen Periodicly Flickering Status in linux package in Ubuntu: Confirmed Bug description: This bug happens to me on fresh install of Kubuntu 22.10. I am running AMD not Intel and have the same issue. I have yet to find a solution that works, but I am testing different configs as I type. Here are my specs: OS: Kubuntu 22.10 Kernel: Ubuntu 5.19.0-41.42-generic 5.19.17 CPU: Virtual KVM 16-Core with Host Profile Applied (Ryzen 9 3950X) RAM: 64GB GPU: PCIE-Passthru NVIDIA RTX 3080 KVM BIOS: OVMF-UEFI (Q35) Monitors: Two, one is configured to run at 75MHz Similar to this bug (except I do not have an Intel CPU/GPU in the mix): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 ^ None of the fixes listed in the similar bug worked ^ --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: user1843 F wireplumber /dev/snd/controlC2: user1843 F wireplumber /dev/snd/controlC1: user1843 F wireplumber /dev/snd/seq:user1842 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2023-04-01 (26 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. enp6s18 no wireless extensions. MachineType: QEMU Standard PC (Q35 + ICH9, 2009) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=/dev/mapper/vgkubuntu-root ro quiet splash i915.enable_dc=0 intel_idle.max_cstate=2 i915.enable_psr=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-41-generic N/A linux-backports-modules-5.19.0-41-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.5 RfKill: Tags: kinetic Uname: Linux 5.19.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/04/2023 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 3.20230228-2 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.2 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr3.20230228-2:bd04/04/2023:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.2:cvnQEMU:ct1:cvrpc-q35-7.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017944/+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 2017944] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2017944/+attachment/5669307/+files/acpidump.txt ** Description changed: This bug happens to me on fresh install of Kubuntu 22.10. I am running AMD not Intel and have the same issue. I have yet to find a solution that works, but I am testing different configs as I type. Here are my specs: OS: Kubuntu 22.10 Kernel: Ubuntu 5.19.0-41.42-generic 5.19.17 CPU: Virtual KVM 16-Core with Host Profile Applied (Ryzen 9 3950X) RAM: 64GB GPU: PCIE-Passthru NVIDIA RTX 3080 KVM BIOS: OVMF-UEFI (Q35) Monitors: Two, one is configured to run at 75MHz Similar to this bug (except I do not have an Intel CPU/GPU in the mix): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 ^ None of the fixes listed in the similar bug worked ^ - --- + --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC3: zax1843 F wireplumber - /dev/snd/controlC2: zax1843 F wireplumber - /dev/snd/controlC1: zax1843 F wireplumber - /dev/snd/seq:zax1842 F pipewire + USERPID ACCESS COMMAND + /dev/snd/controlC3: user1843 F wireplumber + /dev/snd/controlC2: user1843 F wireplumber + /dev/snd/controlC1: user1843 F wireplumber + /dev/snd/seq:user1842 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2023-04-01 (26 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: - lono wireless extensions. - - enp6s18 no wireless extensions. + lono wireless extensions. + + enp6s18 no wireless extensions. MachineType: QEMU Standard PC (Q35 + ICH9, 2009) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: - + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=/dev/mapper/vgkubuntu-root ro quiet splash i915.enable_dc=0 intel_idle.max_cstate=2 i915.enable_psr=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 RelatedPackageVersions: - linux-restricted-modules-5.19.0-41-generic N/A - linux-backports-modules-5.19.0-41-generic N/A - linux-firmware 20220923.gitf09bebf3-0ubuntu1.5 + linux-restricted-modules-5.19.0-41-generic N/A + linux-backports-modules-5.19.0-41-generic N/A + linux-firmware 20220923.gitf09bebf3-0ubuntu1.5 RfKill: - + Tags: kinetic Uname: Linux 5.19.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/04/2023 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 3.20230228-2 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.2 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr3.20230228-2:bd04/04/2023:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.2:cvnQEMU:ct1:cvrpc-q35-7.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.2 dmi.sys.vendor: QEMU ** Changed in: linux (Ubuntu) Status: Incomplete => 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/2017944 Title: Screen Periodicly Flickering Status in linux package in Ubuntu: Confirmed Bug description: This bug happens to me on fresh install of Kubuntu 22.10. I am running AMD not Intel and have the same issue. I have yet to find a solution that works, but I am testing different configs as I type. Here are my specs: OS: Kubuntu 22.10 Kernel: Ubuntu 5.19.0-41.42-generic 5.19.17 CPU: Virtual KVM 16-Core with Host Profile Applied (Ryzen 9 3950X) RAM: 64GB GPU: PCIE-Passthru NVIDIA RTX 3080 KVM BIOS: OVMF-UEFI (Q35) Monitors: Two, one is configured to run at 75MHz Similar to this bug (except I do not have an Intel CPU/GPU in the mix): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 ^ None of the fixes listed in the similar bug worked ^ --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: user1843 F wireplumber /dev/snd/controlC2: user1843 F wireplumber /dev/snd/controlC1: user1843 F wireplumber /dev/snd/seq:user1842 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2023-04-01 (26 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64
[Kernel-packages] [Bug 2017944] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2017944/+attachment/5669306/+files/WifiSyslog.txt -- 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/2017944 Title: Screen Periodicly Flickering Status in linux package in Ubuntu: Confirmed Bug description: This bug happens to me on fresh install of Kubuntu 22.10. I am running AMD not Intel and have the same issue. I have yet to find a solution that works, but I am testing different configs as I type. Here are my specs: OS: Kubuntu 22.10 Kernel: Ubuntu 5.19.0-41.42-generic 5.19.17 CPU: Virtual KVM 16-Core with Host Profile Applied (Ryzen 9 3950X) RAM: 64GB GPU: PCIE-Passthru NVIDIA RTX 3080 KVM BIOS: OVMF-UEFI (Q35) Monitors: Two, one is configured to run at 75MHz Similar to this bug (except I do not have an Intel CPU/GPU in the mix): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 ^ None of the fixes listed in the similar bug worked ^ --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: user1843 F wireplumber /dev/snd/controlC2: user1843 F wireplumber /dev/snd/controlC1: user1843 F wireplumber /dev/snd/seq:user1842 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2023-04-01 (26 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. enp6s18 no wireless extensions. MachineType: QEMU Standard PC (Q35 + ICH9, 2009) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=/dev/mapper/vgkubuntu-root ro quiet splash i915.enable_dc=0 intel_idle.max_cstate=2 i915.enable_psr=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-41-generic N/A linux-backports-modules-5.19.0-41-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.5 RfKill: Tags: kinetic Uname: Linux 5.19.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/04/2023 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 3.20230228-2 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.2 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr3.20230228-2:bd04/04/2023:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.2:cvnQEMU:ct1:cvrpc-q35-7.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017944/+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 2017944] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2017944/+attachment/5669305/+files/UdevDb.txt -- 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/2017944 Title: Screen Periodicly Flickering Status in linux package in Ubuntu: Confirmed Bug description: This bug happens to me on fresh install of Kubuntu 22.10. I am running AMD not Intel and have the same issue. I have yet to find a solution that works, but I am testing different configs as I type. Here are my specs: OS: Kubuntu 22.10 Kernel: Ubuntu 5.19.0-41.42-generic 5.19.17 CPU: Virtual KVM 16-Core with Host Profile Applied (Ryzen 9 3950X) RAM: 64GB GPU: PCIE-Passthru NVIDIA RTX 3080 KVM BIOS: OVMF-UEFI (Q35) Monitors: Two, one is configured to run at 75MHz Similar to this bug (except I do not have an Intel CPU/GPU in the mix): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 ^ None of the fixes listed in the similar bug worked ^ --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: user1843 F wireplumber /dev/snd/controlC2: user1843 F wireplumber /dev/snd/controlC1: user1843 F wireplumber /dev/snd/seq:user1842 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2023-04-01 (26 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. enp6s18 no wireless extensions. MachineType: QEMU Standard PC (Q35 + ICH9, 2009) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=/dev/mapper/vgkubuntu-root ro quiet splash i915.enable_dc=0 intel_idle.max_cstate=2 i915.enable_psr=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-41-generic N/A linux-backports-modules-5.19.0-41-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.5 RfKill: Tags: kinetic Uname: Linux 5.19.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/04/2023 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 3.20230228-2 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.2 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr3.20230228-2:bd04/04/2023:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.2:cvnQEMU:ct1:cvrpc-q35-7.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017944/+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 2017944] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2017944/+attachment/5669303/+files/ProcInterrupts.txt -- 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/2017944 Title: Screen Periodicly Flickering Status in linux package in Ubuntu: Confirmed Bug description: This bug happens to me on fresh install of Kubuntu 22.10. I am running AMD not Intel and have the same issue. I have yet to find a solution that works, but I am testing different configs as I type. Here are my specs: OS: Kubuntu 22.10 Kernel: Ubuntu 5.19.0-41.42-generic 5.19.17 CPU: Virtual KVM 16-Core with Host Profile Applied (Ryzen 9 3950X) RAM: 64GB GPU: PCIE-Passthru NVIDIA RTX 3080 KVM BIOS: OVMF-UEFI (Q35) Monitors: Two, one is configured to run at 75MHz Similar to this bug (except I do not have an Intel CPU/GPU in the mix): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 ^ None of the fixes listed in the similar bug worked ^ --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: user1843 F wireplumber /dev/snd/controlC2: user1843 F wireplumber /dev/snd/controlC1: user1843 F wireplumber /dev/snd/seq:user1842 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2023-04-01 (26 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. enp6s18 no wireless extensions. MachineType: QEMU Standard PC (Q35 + ICH9, 2009) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=/dev/mapper/vgkubuntu-root ro quiet splash i915.enable_dc=0 intel_idle.max_cstate=2 i915.enable_psr=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-41-generic N/A linux-backports-modules-5.19.0-41-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.5 RfKill: Tags: kinetic Uname: Linux 5.19.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/04/2023 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 3.20230228-2 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.2 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr3.20230228-2:bd04/04/2023:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.2:cvnQEMU:ct1:cvrpc-q35-7.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017944/+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 2017944] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2017944/+attachment/5669304/+files/ProcModules.txt -- 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/2017944 Title: Screen Periodicly Flickering Status in linux package in Ubuntu: Confirmed Bug description: This bug happens to me on fresh install of Kubuntu 22.10. I am running AMD not Intel and have the same issue. I have yet to find a solution that works, but I am testing different configs as I type. Here are my specs: OS: Kubuntu 22.10 Kernel: Ubuntu 5.19.0-41.42-generic 5.19.17 CPU: Virtual KVM 16-Core with Host Profile Applied (Ryzen 9 3950X) RAM: 64GB GPU: PCIE-Passthru NVIDIA RTX 3080 KVM BIOS: OVMF-UEFI (Q35) Monitors: Two, one is configured to run at 75MHz Similar to this bug (except I do not have an Intel CPU/GPU in the mix): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 ^ None of the fixes listed in the similar bug worked ^ --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: user1843 F wireplumber /dev/snd/controlC2: user1843 F wireplumber /dev/snd/controlC1: user1843 F wireplumber /dev/snd/seq:user1842 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2023-04-01 (26 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. enp6s18 no wireless extensions. MachineType: QEMU Standard PC (Q35 + ICH9, 2009) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=/dev/mapper/vgkubuntu-root ro quiet splash i915.enable_dc=0 intel_idle.max_cstate=2 i915.enable_psr=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-41-generic N/A linux-backports-modules-5.19.0-41-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.5 RfKill: Tags: kinetic Uname: Linux 5.19.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/04/2023 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 3.20230228-2 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.2 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr3.20230228-2:bd04/04/2023:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.2:cvnQEMU:ct1:cvrpc-q35-7.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017944/+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 2017944] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2017944/+attachment/5669302/+files/ProcEnviron.txt -- 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/2017944 Title: Screen Periodicly Flickering Status in linux package in Ubuntu: Confirmed Bug description: This bug happens to me on fresh install of Kubuntu 22.10. I am running AMD not Intel and have the same issue. I have yet to find a solution that works, but I am testing different configs as I type. Here are my specs: OS: Kubuntu 22.10 Kernel: Ubuntu 5.19.0-41.42-generic 5.19.17 CPU: Virtual KVM 16-Core with Host Profile Applied (Ryzen 9 3950X) RAM: 64GB GPU: PCIE-Passthru NVIDIA RTX 3080 KVM BIOS: OVMF-UEFI (Q35) Monitors: Two, one is configured to run at 75MHz Similar to this bug (except I do not have an Intel CPU/GPU in the mix): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 ^ None of the fixes listed in the similar bug worked ^ --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: user1843 F wireplumber /dev/snd/controlC2: user1843 F wireplumber /dev/snd/controlC1: user1843 F wireplumber /dev/snd/seq:user1842 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2023-04-01 (26 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. enp6s18 no wireless extensions. MachineType: QEMU Standard PC (Q35 + ICH9, 2009) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=/dev/mapper/vgkubuntu-root ro quiet splash i915.enable_dc=0 intel_idle.max_cstate=2 i915.enable_psr=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-41-generic N/A linux-backports-modules-5.19.0-41-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.5 RfKill: Tags: kinetic Uname: Linux 5.19.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/04/2023 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 3.20230228-2 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.2 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr3.20230228-2:bd04/04/2023:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.2:cvnQEMU:ct1:cvrpc-q35-7.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017944/+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 2017944] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2017944/+attachment/5669301/+files/ProcCpuinfoMinimal.txt -- 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/2017944 Title: Screen Periodicly Flickering Status in linux package in Ubuntu: Confirmed Bug description: This bug happens to me on fresh install of Kubuntu 22.10. I am running AMD not Intel and have the same issue. I have yet to find a solution that works, but I am testing different configs as I type. Here are my specs: OS: Kubuntu 22.10 Kernel: Ubuntu 5.19.0-41.42-generic 5.19.17 CPU: Virtual KVM 16-Core with Host Profile Applied (Ryzen 9 3950X) RAM: 64GB GPU: PCIE-Passthru NVIDIA RTX 3080 KVM BIOS: OVMF-UEFI (Q35) Monitors: Two, one is configured to run at 75MHz Similar to this bug (except I do not have an Intel CPU/GPU in the mix): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 ^ None of the fixes listed in the similar bug worked ^ --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: user1843 F wireplumber /dev/snd/controlC2: user1843 F wireplumber /dev/snd/controlC1: user1843 F wireplumber /dev/snd/seq:user1842 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2023-04-01 (26 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. enp6s18 no wireless extensions. MachineType: QEMU Standard PC (Q35 + ICH9, 2009) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=/dev/mapper/vgkubuntu-root ro quiet splash i915.enable_dc=0 intel_idle.max_cstate=2 i915.enable_psr=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-41-generic N/A linux-backports-modules-5.19.0-41-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.5 RfKill: Tags: kinetic Uname: Linux 5.19.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/04/2023 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 3.20230228-2 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.2 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr3.20230228-2:bd04/04/2023:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.2:cvnQEMU:ct1:cvrpc-q35-7.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017944/+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 2017944] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2017944/+attachment/5669300/+files/ProcCpuinfo.txt -- 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/2017944 Title: Screen Periodicly Flickering Status in linux package in Ubuntu: Confirmed Bug description: This bug happens to me on fresh install of Kubuntu 22.10. I am running AMD not Intel and have the same issue. I have yet to find a solution that works, but I am testing different configs as I type. Here are my specs: OS: Kubuntu 22.10 Kernel: Ubuntu 5.19.0-41.42-generic 5.19.17 CPU: Virtual KVM 16-Core with Host Profile Applied (Ryzen 9 3950X) RAM: 64GB GPU: PCIE-Passthru NVIDIA RTX 3080 KVM BIOS: OVMF-UEFI (Q35) Monitors: Two, one is configured to run at 75MHz Similar to this bug (except I do not have an Intel CPU/GPU in the mix): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 ^ None of the fixes listed in the similar bug worked ^ --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: user1843 F wireplumber /dev/snd/controlC2: user1843 F wireplumber /dev/snd/controlC1: user1843 F wireplumber /dev/snd/seq:user1842 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2023-04-01 (26 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. enp6s18 no wireless extensions. MachineType: QEMU Standard PC (Q35 + ICH9, 2009) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=/dev/mapper/vgkubuntu-root ro quiet splash i915.enable_dc=0 intel_idle.max_cstate=2 i915.enable_psr=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-41-generic N/A linux-backports-modules-5.19.0-41-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.5 RfKill: Tags: kinetic Uname: Linux 5.19.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/04/2023 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 3.20230228-2 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.2 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr3.20230228-2:bd04/04/2023:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.2:cvnQEMU:ct1:cvrpc-q35-7.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017944/+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 2017944] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2017944/+attachment/5669298/+files/Lsusb-t.txt -- 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/2017944 Title: Screen Periodicly Flickering Status in linux package in Ubuntu: Confirmed Bug description: This bug happens to me on fresh install of Kubuntu 22.10. I am running AMD not Intel and have the same issue. I have yet to find a solution that works, but I am testing different configs as I type. Here are my specs: OS: Kubuntu 22.10 Kernel: Ubuntu 5.19.0-41.42-generic 5.19.17 CPU: Virtual KVM 16-Core with Host Profile Applied (Ryzen 9 3950X) RAM: 64GB GPU: PCIE-Passthru NVIDIA RTX 3080 KVM BIOS: OVMF-UEFI (Q35) Monitors: Two, one is configured to run at 75MHz Similar to this bug (except I do not have an Intel CPU/GPU in the mix): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 ^ None of the fixes listed in the similar bug worked ^ --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: user1843 F wireplumber /dev/snd/controlC2: user1843 F wireplumber /dev/snd/controlC1: user1843 F wireplumber /dev/snd/seq:user1842 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2023-04-01 (26 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. enp6s18 no wireless extensions. MachineType: QEMU Standard PC (Q35 + ICH9, 2009) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=/dev/mapper/vgkubuntu-root ro quiet splash i915.enable_dc=0 intel_idle.max_cstate=2 i915.enable_psr=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-41-generic N/A linux-backports-modules-5.19.0-41-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.5 RfKill: Tags: kinetic Uname: Linux 5.19.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/04/2023 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 3.20230228-2 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.2 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr3.20230228-2:bd04/04/2023:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.2:cvnQEMU:ct1:cvrpc-q35-7.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017944/+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 2017944] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2017944/+attachment/5669299/+files/Lsusb-v.txt -- 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/2017944 Title: Screen Periodicly Flickering Status in linux package in Ubuntu: Confirmed Bug description: This bug happens to me on fresh install of Kubuntu 22.10. I am running AMD not Intel and have the same issue. I have yet to find a solution that works, but I am testing different configs as I type. Here are my specs: OS: Kubuntu 22.10 Kernel: Ubuntu 5.19.0-41.42-generic 5.19.17 CPU: Virtual KVM 16-Core with Host Profile Applied (Ryzen 9 3950X) RAM: 64GB GPU: PCIE-Passthru NVIDIA RTX 3080 KVM BIOS: OVMF-UEFI (Q35) Monitors: Two, one is configured to run at 75MHz Similar to this bug (except I do not have an Intel CPU/GPU in the mix): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 ^ None of the fixes listed in the similar bug worked ^ --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: user1843 F wireplumber /dev/snd/controlC2: user1843 F wireplumber /dev/snd/controlC1: user1843 F wireplumber /dev/snd/seq:user1842 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2023-04-01 (26 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. enp6s18 no wireless extensions. MachineType: QEMU Standard PC (Q35 + ICH9, 2009) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=/dev/mapper/vgkubuntu-root ro quiet splash i915.enable_dc=0 intel_idle.max_cstate=2 i915.enable_psr=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-41-generic N/A linux-backports-modules-5.19.0-41-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.5 RfKill: Tags: kinetic Uname: Linux 5.19.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/04/2023 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 3.20230228-2 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.2 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr3.20230228-2:bd04/04/2023:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.2:cvnQEMU:ct1:cvrpc-q35-7.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017944/+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 2017944] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2017944/+attachment/5669297/+files/Lsusb.txt -- 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/2017944 Title: Screen Periodicly Flickering Status in linux package in Ubuntu: Confirmed Bug description: This bug happens to me on fresh install of Kubuntu 22.10. I am running AMD not Intel and have the same issue. I have yet to find a solution that works, but I am testing different configs as I type. Here are my specs: OS: Kubuntu 22.10 Kernel: Ubuntu 5.19.0-41.42-generic 5.19.17 CPU: Virtual KVM 16-Core with Host Profile Applied (Ryzen 9 3950X) RAM: 64GB GPU: PCIE-Passthru NVIDIA RTX 3080 KVM BIOS: OVMF-UEFI (Q35) Monitors: Two, one is configured to run at 75MHz Similar to this bug (except I do not have an Intel CPU/GPU in the mix): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 ^ None of the fixes listed in the similar bug worked ^ --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: user1843 F wireplumber /dev/snd/controlC2: user1843 F wireplumber /dev/snd/controlC1: user1843 F wireplumber /dev/snd/seq:user1842 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2023-04-01 (26 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. enp6s18 no wireless extensions. MachineType: QEMU Standard PC (Q35 + ICH9, 2009) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=/dev/mapper/vgkubuntu-root ro quiet splash i915.enable_dc=0 intel_idle.max_cstate=2 i915.enable_psr=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-41-generic N/A linux-backports-modules-5.19.0-41-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.5 RfKill: Tags: kinetic Uname: Linux 5.19.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/04/2023 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 3.20230228-2 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.2 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr3.20230228-2:bd04/04/2023:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.2:cvnQEMU:ct1:cvrpc-q35-7.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017944/+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 2017944] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2017944/+attachment/5669296/+files/Lspci-vt.txt -- 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/2017944 Title: Screen Periodicly Flickering Status in linux package in Ubuntu: Confirmed Bug description: This bug happens to me on fresh install of Kubuntu 22.10. I am running AMD not Intel and have the same issue. I have yet to find a solution that works, but I am testing different configs as I type. Here are my specs: OS: Kubuntu 22.10 Kernel: Ubuntu 5.19.0-41.42-generic 5.19.17 CPU: Virtual KVM 16-Core with Host Profile Applied (Ryzen 9 3950X) RAM: 64GB GPU: PCIE-Passthru NVIDIA RTX 3080 KVM BIOS: OVMF-UEFI (Q35) Monitors: Two, one is configured to run at 75MHz Similar to this bug (except I do not have an Intel CPU/GPU in the mix): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 ^ None of the fixes listed in the similar bug worked ^ --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: user1843 F wireplumber /dev/snd/controlC2: user1843 F wireplumber /dev/snd/controlC1: user1843 F wireplumber /dev/snd/seq:user1842 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2023-04-01 (26 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. enp6s18 no wireless extensions. MachineType: QEMU Standard PC (Q35 + ICH9, 2009) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=/dev/mapper/vgkubuntu-root ro quiet splash i915.enable_dc=0 intel_idle.max_cstate=2 i915.enable_psr=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-41-generic N/A linux-backports-modules-5.19.0-41-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.5 RfKill: Tags: kinetic Uname: Linux 5.19.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/04/2023 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 3.20230228-2 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.2 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr3.20230228-2:bd04/04/2023:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.2:cvnQEMU:ct1:cvrpc-q35-7.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017944/+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 2017944] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2017944/+attachment/5669295/+files/Lspci.txt -- 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/2017944 Title: Screen Periodicly Flickering Status in linux package in Ubuntu: Confirmed Bug description: This bug happens to me on fresh install of Kubuntu 22.10. I am running AMD not Intel and have the same issue. I have yet to find a solution that works, but I am testing different configs as I type. Here are my specs: OS: Kubuntu 22.10 Kernel: Ubuntu 5.19.0-41.42-generic 5.19.17 CPU: Virtual KVM 16-Core with Host Profile Applied (Ryzen 9 3950X) RAM: 64GB GPU: PCIE-Passthru NVIDIA RTX 3080 KVM BIOS: OVMF-UEFI (Q35) Monitors: Two, one is configured to run at 75MHz Similar to this bug (except I do not have an Intel CPU/GPU in the mix): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 ^ None of the fixes listed in the similar bug worked ^ --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: user1843 F wireplumber /dev/snd/controlC2: user1843 F wireplumber /dev/snd/controlC1: user1843 F wireplumber /dev/snd/seq:user1842 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2023-04-01 (26 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. enp6s18 no wireless extensions. MachineType: QEMU Standard PC (Q35 + ICH9, 2009) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=/dev/mapper/vgkubuntu-root ro quiet splash i915.enable_dc=0 intel_idle.max_cstate=2 i915.enable_psr=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-41-generic N/A linux-backports-modules-5.19.0-41-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.5 RfKill: Tags: kinetic Uname: Linux 5.19.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/04/2023 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 3.20230228-2 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.2 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr3.20230228-2:bd04/04/2023:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.2:cvnQEMU:ct1:cvrpc-q35-7.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017944/+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 2017944] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2017944/+attachment/5669294/+files/CurrentDmesg.txt -- 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/2017944 Title: Screen Periodicly Flickering Status in linux package in Ubuntu: Confirmed Bug description: This bug happens to me on fresh install of Kubuntu 22.10. I am running AMD not Intel and have the same issue. I have yet to find a solution that works, but I am testing different configs as I type. Here are my specs: OS: Kubuntu 22.10 Kernel: Ubuntu 5.19.0-41.42-generic 5.19.17 CPU: Virtual KVM 16-Core with Host Profile Applied (Ryzen 9 3950X) RAM: 64GB GPU: PCIE-Passthru NVIDIA RTX 3080 KVM BIOS: OVMF-UEFI (Q35) Monitors: Two, one is configured to run at 75MHz Similar to this bug (except I do not have an Intel CPU/GPU in the mix): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 ^ None of the fixes listed in the similar bug worked ^ --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: user1843 F wireplumber /dev/snd/controlC2: user1843 F wireplumber /dev/snd/controlC1: user1843 F wireplumber /dev/snd/seq:user1842 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2023-04-01 (26 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. enp6s18 no wireless extensions. MachineType: QEMU Standard PC (Q35 + ICH9, 2009) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=/dev/mapper/vgkubuntu-root ro quiet splash i915.enable_dc=0 intel_idle.max_cstate=2 i915.enable_psr=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-41-generic N/A linux-backports-modules-5.19.0-41-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.5 RfKill: Tags: kinetic Uname: Linux 5.19.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/04/2023 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 3.20230228-2 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.2 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr3.20230228-2:bd04/04/2023:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.2:cvnQEMU:ct1:cvrpc-q35-7.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017944/+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 2017944] Re: Screen Periodicly Flickering
apport information ** Tags added: apport-collected kinetic ** Description changed: This bug happens to me on fresh install of Kubuntu 22.10. I am running AMD not Intel and have the same issue. I have yet to find a solution that works, but I am testing different configs as I type. Here are my specs: OS: Kubuntu 22.10 Kernel: Ubuntu 5.19.0-41.42-generic 5.19.17 CPU: Virtual KVM 16-Core with Host Profile Applied (Ryzen 9 3950X) RAM: 64GB GPU: PCIE-Passthru NVIDIA RTX 3080 KVM BIOS: OVMF-UEFI (Q35) Monitors: Two, one is configured to run at 75MHz Similar to this bug (except I do not have an Intel CPU/GPU in the mix): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 ^ None of the fixes listed in the similar bug worked ^ + --- + ProblemType: Bug + ApportVersion: 2.23.1-0ubuntu3.2 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC3: zax1843 F wireplumber + /dev/snd/controlC2: zax1843 F wireplumber + /dev/snd/controlC1: zax1843 F wireplumber + /dev/snd/seq:zax1842 F pipewire + CRDA: N/A + CasperMD5CheckResult: pass + CurrentDesktop: KDE + DistroRelease: Ubuntu 22.10 + InstallationDate: Installed on 2023-04-01 (26 days ago) + InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) + IwConfig: + lono wireless extensions. + + enp6s18 no wireless extensions. + MachineType: QEMU Standard PC (Q35 + ICH9, 2009) + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=/dev/mapper/vgkubuntu-root ro quiet splash i915.enable_dc=0 intel_idle.max_cstate=2 i915.enable_psr=0 vt.handoff=7 + ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 + RelatedPackageVersions: + linux-restricted-modules-5.19.0-41-generic N/A + linux-backports-modules-5.19.0-41-generic N/A + linux-firmware 20220923.gitf09bebf3-0ubuntu1.5 + RfKill: + + Tags: kinetic + Uname: Linux 5.19.0-41-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 04/04/2023 + dmi.bios.release: 0.0 + dmi.bios.vendor: EFI Development Kit II / OVMF + dmi.bios.version: 3.20230228-2 + dmi.chassis.type: 1 + dmi.chassis.vendor: QEMU + dmi.chassis.version: pc-q35-7.2 + dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr3.20230228-2:bd04/04/2023:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.2:cvnQEMU:ct1:cvrpc-q35-7.2:sku: + dmi.product.name: Standard PC (Q35 + ICH9, 2009) + dmi.product.version: pc-q35-7.2 + dmi.sys.vendor: QEMU ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2017944/+attachment/5669293/+files/AlsaInfo.txt -- 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/2017944 Title: Screen Periodicly Flickering Status in linux package in Ubuntu: Confirmed Bug description: This bug happens to me on fresh install of Kubuntu 22.10. I am running AMD not Intel and have the same issue. I have yet to find a solution that works, but I am testing different configs as I type. Here are my specs: OS: Kubuntu 22.10 Kernel: Ubuntu 5.19.0-41.42-generic 5.19.17 CPU: Virtual KVM 16-Core with Host Profile Applied (Ryzen 9 3950X) RAM: 64GB GPU: PCIE-Passthru NVIDIA RTX 3080 KVM BIOS: OVMF-UEFI (Q35) Monitors: Two, one is configured to run at 75MHz Similar to this bug (except I do not have an Intel CPU/GPU in the mix): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 ^ None of the fixes listed in the similar bug worked ^ --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: user1843 F wireplumber /dev/snd/controlC2: user1843 F wireplumber /dev/snd/controlC1: user1843 F wireplumber /dev/snd/seq:user1842 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2023-04-01 (26 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. enp6s18 no wireless extensions. MachineType: QEMU Standard PC (Q35 + ICH9, 2009) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=/dev/mapper/vgkubuntu-root ro quiet splash i915.enable_dc=0 intel_idle.max_cstate=2 i915.enable_psr=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-41-generic N/A
[Kernel-packages] [Bug 2017944] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2017944 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => 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/2017944 Title: Screen Periodicly Flickering Status in linux package in Ubuntu: Incomplete Bug description: This bug happens to me on fresh install of Kubuntu 22.10. I am running AMD not Intel and have the same issue. I have yet to find a solution that works, but I am testing different configs as I type. Here are my specs: OS: Kubuntu 22.10 Kernel: Ubuntu 5.19.0-41.42-generic 5.19.17 CPU: Virtual KVM 16-Core with Host Profile Applied (Ryzen 9 3950X) RAM: 64GB GPU: PCIE-Passthru NVIDIA RTX 3080 KVM BIOS: OVMF-UEFI (Q35) Monitors: Two, one is configured to run at 75MHz Similar to this bug (except I do not have an Intel CPU/GPU in the mix): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 ^ None of the fixes listed in the similar bug worked ^ --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: zax1843 F wireplumber /dev/snd/controlC2: zax1843 F wireplumber /dev/snd/controlC1: zax1843 F wireplumber /dev/snd/seq:zax1842 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2023-04-01 (26 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. enp6s18 no wireless extensions. MachineType: QEMU Standard PC (Q35 + ICH9, 2009) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=/dev/mapper/vgkubuntu-root ro quiet splash i915.enable_dc=0 intel_idle.max_cstate=2 i915.enable_psr=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-41-generic N/A linux-backports-modules-5.19.0-41-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.5 RfKill: Tags: kinetic Uname: Linux 5.19.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/04/2023 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 3.20230228-2 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.2 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr3.20230228-2:bd04/04/2023:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.2:cvnQEMU:ct1:cvrpc-q35-7.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017944/+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 2017929] Re: Kernel 5.15.0-71 fails to boot on Ubuntu 22.04 (possibly specific to Ryzen APUs)
The bug (or possibly class of bug) in amdgpu that precedes this issue for me is this one: https://gitlab.freedesktop.org/drm/amd/-/issues/934. However, it is unlikely that they are related as the linked graphics bug has existed ever since I bought the hardware, but this kernel booting bug only appeared this week. ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #934 https://gitlab.freedesktop.org/drm/amd/-/issues/934 -- 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/2017929 Title: Kernel 5.15.0-71 fails to boot on Ubuntu 22.04 (possibly specific to Ryzen APUs) Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 5.15.0-71 a couple of days ago, my PC sporadically fails to boot. I see the following error messages: "error: cannot allocate kernel buffer error: you need to load the kernel first. Press any key to continue..._ " I am then returned to the GRUB boot menu. This has also been experienced by two other AskUbuntu users: https://askubuntu.com/questions/1465460/after-kernel-update-error- cannot-allocate-kernel-buffer-you-need-to-load-kern . The common theme appears to be Ryzen APUs; two of us have 3400Gs and one has a 7600. In my case, the issue appears to be more likely to occur when I have to force-reboot because the system is frozen (due to a separate bug which I will link when I can find it again). But I have not yet reproduced it. Also the log files attached to this report may not contain relevant information as the last couple of boots worked correctly. I will try to capture a relevant kernel log now that I know this is a kernel issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-71-generic 5.15.0-71.78 ProcVersionSignature: Ubuntu 5.15.0-71.78-generic 5.15.92 Uname: Linux 5.15.0-71-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matthew1288 F pulseaudio /dev/snd/controlC0: matthew1288 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 27 17:49:11 2023 InstallationDate: Installed on 2022-01-14 (467 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Micro-Star International Co., Ltd. MS-7B89 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-71-generic root=UUID=7348d288-7351-45cd-8da2-592c59a4f7dd ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.15.0-71-generic N/A linux-backports-modules-5.15.0-71-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-05-26 (336 days ago) dmi.bios.date: 09/28/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.E3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.E3:bd09/28/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 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/2017929/+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 2017944] [NEW] Screen Periodicly Flickering
Public bug reported: This bug happens to me on fresh install of Kubuntu 22.10. I am running AMD not Intel and have the same issue. I have yet to find a solution that works, but I am testing different configs as I type. Here are my specs: OS: Kubuntu 22.10 Kernel: Ubuntu 5.19.0-41.42-generic 5.19.17 CPU: Virtual KVM 16-Core with Host Profile Applied (Ryzen 9 3950X) RAM: 64GB GPU: PCIE-Passthru NVIDIA RTX 3080 KVM BIOS: OVMF-UEFI (Q35) Monitors: Two, one is configured to run at 75MHz Similar to this bug (except I do not have an Intel CPU/GPU in the mix): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 ^ None of the fixes listed in the similar bug worked ^ ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Attachment added: "lspci log" https://bugs.launchpad.net/bugs/2017944/+attachment/5669291/+files/lspci-vnvn.log ** Description changed: This bug happens to me on fresh install of Kubuntu 22.10. I am running AMD not Intel and have the same issue. I have yet to find a solution that works, but I am testing different configs as I type. Here are my specs: OS: Kubuntu 22.10 Kernel: Ubuntu 5.19.0-41.42-generic 5.19.17 CPU: Virtual KVM 16-Core with Host Profile Applied (Ryzen 9 3950X) RAM: 64GB GPU: PCIE-Passthru NVIDIA RTX 3080 KVM BIOS: OVMF-UEFI (Q35) - + Monitors: Two, one is configured to run at 75MHz Similar to this bug (except I do not have an Intel CPU/GPU in the mix): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 ^ None of the fixes listed in the similar bug 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/2017944 Title: Screen Periodicly Flickering Status in linux package in Ubuntu: Incomplete Bug description: This bug happens to me on fresh install of Kubuntu 22.10. I am running AMD not Intel and have the same issue. I have yet to find a solution that works, but I am testing different configs as I type. Here are my specs: OS: Kubuntu 22.10 Kernel: Ubuntu 5.19.0-41.42-generic 5.19.17 CPU: Virtual KVM 16-Core with Host Profile Applied (Ryzen 9 3950X) RAM: 64GB GPU: PCIE-Passthru NVIDIA RTX 3080 KVM BIOS: OVMF-UEFI (Q35) Monitors: Two, one is configured to run at 75MHz Similar to this bug (except I do not have an Intel CPU/GPU in the mix): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 ^ None of the fixes listed in the similar bug worked ^ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017944/+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 1998643] Re: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices
apt install ./linux-headers-5.15.0-72_5.15.0-72.79_all.deb apt install ./linux-image-unsigned-5.15.0-72-generic_5.15.0-72.79_amd64.deb ./linux-modules-5.15.0-72-generic_5.15.0-72.79_amd64.deb # This has smartpqi apt install ./linux-modules-extra-5.15.0-72-generic_5.15.0-72.79_amd64.deb reboot modinfo smartpqi filename: /lib/modules/5.15.0-72-generic/kernel/drivers/scsi/smartpqi/smartpqi.ko license:GPL version:2.1.20-035 description:Driver for Microchip Smart Family Controller version 2.1.20-035 author: Microchip The version is correct. Ran some I/O tests and it looks good. -- 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/1998643 Title: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: [Impact] These patches provide bug fixes and add support for the latest generation of OEM PCI devices to ensure customers are able to use Jammy on the recent generations of server hardware. This will bring us in line with the other major linux distros. [Fix] There are some outstanding patches already in Linus's tree that can be applied to 22.04. git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git The following patches apply to https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045 e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year 6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter 2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints 6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition 69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests 85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures 2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers 44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i 331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang 904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices 297bdc540f0e scsi: smartpqi: Close write read holes dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers 1d393227fc76 scsi: smartpqi: Add controller fw version to console log 4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal 8946ea283808 scsi: smartpqi: Fix typo in comment c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer 31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang 62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035 291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses c66e078ad89e scsi: smartpqi: Fix hibernate and suspend 5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init 00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives 5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads 27655e9db479 scsi: smartpqi: Update volume size after expansion b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend 42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value 9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io() b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code 94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer 70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot 2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs c57ee4ccb358 scsi: smartpqi: Add PCI IDs c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace 64fc9015fbeb scsi: smartpqi: Switch to attribute groups 0ca190805784 scsi: smartpqi: Call scsi_done() directly I added the above SHA1 IDs to a file called: backport_linus_6.1_into_22.04 git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04 git am -s /tmp/patches/*.diff All patches applied without any conflicts. [Test Plan] The upstream driver has undergone extensive testing by Microchip's test team before submitting those patches to the upstream kernel. All patches are tested and accepted in the upstream kernel at this time. One should be able to load the smartpqi driver and verify the version is at 2.1.18-045 [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/smartpqi_2204_3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998643/+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 2017937] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2017937 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => 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/2017937 Title: linux-headers-6.2.0-20-generic kann nicht installiert werden Status in linux package in Ubuntu: Incomplete Bug description: how to solve this problem? wie kann ich das Problem loesen? pbs@pbs-Vostro-5568:~$ sudo dpkg --configure -a [sudo] Passwort für pbs: linux-image-6.2.0-20-generic (6.2.0-20.20) wird eingerichtet ... linux-headers-6.2.0-20-generic (6.2.0-20.20) wird eingerichtet ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic all INCLUDEDIR=/lib/modules/6.2.0-20-generic/build/include KVERSION=6.2.0-20-generic DKMS_BUILD=1...(bad exit status: 2) ERROR (dkms apport): binary package for evdi: 1.12.0 not found Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/evdi/1.12.0/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: Fehler beim Bearbeiten des Paketes linux-headers-6.2.0-20-generic (--configure): »installiertes post-installation-Skript des Paketes linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1 zurück dpkg: Abhängigkeitsprobleme verhindern Konfiguration von linux-headers-generic: linux-headers-generic hängt ab von linux-headers-6.2.0-20-generic; aber: Paket linux-headers-6.2.0-20-generic ist noch nicht konfiguriert. dpkg: Fehler beim Bearbeiten des Paketes linux-headers-generic (--configure): Abhängigkeitsprobleme - verbleibt unkonfiguriert dpkg: Abhängigkeitsprobleme verhindern Konfiguration von linux-generic: linux-generic hängt ab von linux-headers-generic (= 6.2.0.20.20); aber: Paket linux-headers-generic ist noch nicht konfiguriert. dpkg: Fehler beim Bearbeiten des Paketes linux-generic (--configure): Abhängigkeitsprobleme - verbleibt unkonfiguriert Trigger für linux-image-6.2.0-20-generic (6.2.0-20.20) werden verarbeitet ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic all INCLUDEDIR=/lib/modules/6.2.0-20-generic/build/include KVERSION=6.2.0-20-generic DKMS_BUILD=1...(bad exit status: 2) ERROR (dkms apport): binary package for evdi: 1.12.0 not found Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/evdi/1.12.0/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: Fehler beim Bearbeiten des Paketes linux-image-6.2.0-20-generic (--configure): »installiertes post-installation-Skript des Paketes linux-image-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1 zurück Fehler traten auf beim Bearbeiten von: linux-headers-6.2.0-20-generic linux-headers-generic linux-generic linux-image-6.2.0-20-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017937/+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 2017937] [NEW] linux-headers-6.2.0-20-generic kann nicht installiert werden
Public bug reported: how to solve this problem? wie kann ich das Problem loesen? pbs@pbs-Vostro-5568:~$ sudo dpkg --configure -a [sudo] Passwort für pbs: linux-image-6.2.0-20-generic (6.2.0-20.20) wird eingerichtet ... linux-headers-6.2.0-20-generic (6.2.0-20.20) wird eingerichtet ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic all INCLUDEDIR=/lib/modules/6.2.0-20-generic/build/include KVERSION=6.2.0-20-generic DKMS_BUILD=1...(bad exit status: 2) ERROR (dkms apport): binary package for evdi: 1.12.0 not found Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/evdi/1.12.0/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: Fehler beim Bearbeiten des Paketes linux-headers-6.2.0-20-generic (--configure): »installiertes post-installation-Skript des Paketes linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1 zurück dpkg: Abhängigkeitsprobleme verhindern Konfiguration von linux-headers-generic: linux-headers-generic hängt ab von linux-headers-6.2.0-20-generic; aber: Paket linux-headers-6.2.0-20-generic ist noch nicht konfiguriert. dpkg: Fehler beim Bearbeiten des Paketes linux-headers-generic (--configure): Abhängigkeitsprobleme - verbleibt unkonfiguriert dpkg: Abhängigkeitsprobleme verhindern Konfiguration von linux-generic: linux-generic hängt ab von linux-headers-generic (= 6.2.0.20.20); aber: Paket linux-headers-generic ist noch nicht konfiguriert. dpkg: Fehler beim Bearbeiten des Paketes linux-generic (--configure): Abhängigkeitsprobleme - verbleibt unkonfiguriert Trigger für linux-image-6.2.0-20-generic (6.2.0-20.20) werden verarbeitet ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic all INCLUDEDIR=/lib/modules/6.2.0-20-generic/build/include KVERSION=6.2.0-20-generic DKMS_BUILD=1...(bad exit status: 2) ERROR (dkms apport): binary package for evdi: 1.12.0 not found Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/evdi/1.12.0/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: Fehler beim Bearbeiten des Paketes linux-image-6.2.0-20-generic (--configure): »installiertes post-installation-Skript des Paketes linux-image-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1 zurück Fehler traten auf beim Bearbeiten von: linux-headers-6.2.0-20-generic linux-headers-generic linux-generic linux-image-6.2.0-20-generic ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/2017937 Title: linux-headers-6.2.0-20-generic kann nicht installiert werden Status in linux package in Ubuntu: Incomplete Bug description: how to solve this problem? wie kann ich das Problem loesen? pbs@pbs-Vostro-5568:~$ sudo dpkg --configure -a [sudo] Passwort für pbs: linux-image-6.2.0-20-generic (6.2.0-20.20) wird eingerichtet ... linux-headers-6.2.0-20-generic (6.2.0-20.20) wird eingerichtet ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic all INCLUDEDIR=/lib/modules/6.2.0-20-generic/build/include KVERSION=6.2.0-20-generic DKMS_BUILD=1...(bad exit status: 2) ERROR (dkms apport): binary package for evdi: 1.12.0 not found Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/evdi/1.12.0/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: Fehler beim Bearbeiten des Paketes linux-headers-6.2.0-20-generic (--configure): »installiertes
[Kernel-packages] [Bug 2017577] Re: ASUSTeK BCM4366 [14e4:43c3] stopped working
The issue appears to be with the brcmfmac driver, which isn't working for me either. The last kernel version where the driver worked properly was 5.19.0-38 (Ubuntu 22.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/2017577 Title: ASUSTeK BCM4366 [14e4:43c3] stopped working Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 22.04, after recent update WiFi card stopped working. However, when using an Ubuntu install disk the WiFi card is properly detected, but when installation completes (with updates) WiFi is inaccessible again. After an update to Ubuntu 22.10 the issue persists: lspci -vvnn | grep -A 9 Network 04:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries Device [14e4:43c3] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:86fb] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- sudo lshw -c network *-network UNCLAIMED description: Network controller product: Broadcom Inc. and subsidiaries vendor: Broadcom Inc. and subsidiaries physical id: 0 bus info: pci@:04:00.0 version: 04 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress cap_list configuration: latency=0 resources: memory:fc00-fc007fff memory:fb80-fbff memory:e240-e27f lspci -nnk 04:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries Device [14e4:43c3] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:86fb] Kernel modules: brcmfmac ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-40-generic 5.19.0-40.41 ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: zukas 2538 F wireplumber /dev/snd/controlC1: zukas 2538 F wireplumber /dev/snd/controlC0: zukas 2538 F wireplumber /dev/snd/seq:zukas 2535 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Apr 24 16:32:11 2023 InstallationDate: Installed on 2023-04-24 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) IwConfig: lono wireless extensions. enp5s0no wireless extensions. enx6263363990e4 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic root=UUID=cdbd41b6-c857-4dc6-9c20-d8fd8a6ae69e 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-5.19.0-40-generic N/A linux-backports-modules-5.19.0-40-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2023-04-24 (0 days ago) dmi.bios.date: 03/05/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3602 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X570-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3602:bd03/05/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX570-FGAMING:rvrRevX.0x: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: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017577/+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 2017934] [NEW] [IoTG] Integrated TSN controller (stmmac) driver commits tracker
Public bug reported: Based on LP https://bugs.launchpad.net/bugs/2006706 List of cherry-picks required: Adding the actual list of commits to make it easier to reference... The following are the latest updates from our v5.15 kernel https://github.com/intel/linux-intel- quilt/tree/lts-v5.15.71-linux-221214T134252Z 0004-fixup-net-phy-marvell10g-Add-WAKE_PHY-support-to-WOL-.conn 0002-stmmac-intel-Add-ADL-N-PCI-ID.conn --> 30c5601fbf353a40115564e1304a1870978fda29 (v5.18-rc1) 0001-taprio-Add-bitmask-checking-based-on-the-traffic-clas.conn 0053-net-phy-dp83867-Fix-SGMII-FIFO-depth-for-non-OF-devic.conn --> e2a54350dc9642e7dfc07335ca355581caa9dbfe (v6.1-rc6) 0052-net-stmmac-check-supported-linkmode-request-for-set-e.conn 0006-net-stmmac-Add-check-for-supported-EEE-advertisement.conn 0002-net-stmmac-update-EEE-status-when-mac-link-goes-down.conn 0003-net-stmmac-Check-and-exit-when-coalesce-rx-usecs-is-e.conn 0033-Revert-net-sched-taprio-make-qdisc_leaf-see-the-per-n.conn --> af7b29b1deaac6da3bb7637f0e263dfab7bfc7a3 (v6.1-rc1) 0005-taprio-Fix-no-error-return-when-entering-invalid-gate.conn 0005-ethtool-Add-support-for-Frame-Preemption-verification.conn 0008-ethtool-Add-support-for-configuring-frame-preemption-.conn 0020-net-networkproxy-add-MIB-passing-via-shared-memory-me.conn 0042-net-phy-add-wrapper-function-for-setup-master-slave-s.conn 0027-net-phy-reconfigure-PHY-WOL-in-resume-if-WOL-option-s.conn 0025-net-stmmac-Disable-MAC-EEE-when-Network-Proxy-is-enab.conn 0035-net-phy-dp83867-add-TI-PHY-loopback.conn --> 13bd85580b85768238cf726dec0ddd89c06a230a (v6.2-rc1) 0003-net-stmmac-add-FPE-preempt-setting-for-TxQ-preemptibl.conn 0013-net-phy-marvell10g-Add-WAKE_PHY-support-to-WOL-event.conn 0043-net-phy-marvell-add-link-status-check-before-enabling.conn 0040-net-stmmac-add-check-for-supported-mode-before-speed-.conn 0044-net-stmmac-Adjust-mac_capabilities-for-Intel-mGbE-2.5.conn 0022-net-stmmac-enable-network-proxy-MSI-interrupt-support.conn 0007-net-stmmac-restructure-Rx-Tx-hardware-timestamping-fu.conn 0045-net-stmmac-check-CBS-input-values-before-configuratio.conn 0008-net-stmmac-introduce-AF_XDP-ZC-RX-HW-timestamps.conn 0024-net-stmmac-Move-phy-state-machine-handling-into-commo.conn 0048-stmmac-intel-Separate-ADL-N-device-ID-from-TGL.conn 0033-net-phy-update-in-band-AN-mode-when-changing-interfac.conn 0047-net-stmmac-Add-check-for-taprio-basetime-configuratio.conn --> 6d534ee057b62ca9332b988619323ee99c7847c1 (v6.2-rc1) 0039-net-stmmac-Set-MAC-s-flow-control-register-to-reflect.conn --> cc3d2b5fc0d6f8ad8a52da5ea679e5c2ec2adbd4 (v6.1-rc8) 0036-net-stmmac-fix-deadlock-caused-by-taking-RTNL-in-RPM-.conn 0037-net-phy-dp83867-perform-phy-reset-after-modifying-aut.conn 0028-Revert-net-stmmac-trigger-PCS-EEE-to-turn-off-on-link.conn 0014-net-stmmac-Fix-Unbalanced-pm_runtime_enable-warning.conn --> d90d0c175cf2982789d336dda928c0f69d3e8a9d (v5.17-rc1) 0038-net-stmmac-Ensure-tx-function-is-not-running-in-stmma.conn --> 77711683a50477de39757d67ab1a3638220d6860 (v6.1-rc6) 0026-net-phy-skip-disabling-interrupt-when-WOL-is-enabled-.conn 0009-REVERTME-net-stmmac-introduce-AF_XDP-ZC-TX-HW-timesta.conn 0010-net-pcs-xpcs-enable-xpcs-reset-skipping.conn 0018-net-networkproxy-add-network-proxy-heci-client.conn net-stmmac-add-network-proxy-support.conn 0019-net-networkproxy-add-configfs.conn 0015-net-stmmac-skip-runtime-handling-in-mdio-read-write.conn 0012-REVERTME-net-stmmac-Add-support-for-HW-accelerated-VL.conn net: stmmac: only enable DMA interrupts when ready --> 087a7b944c5db409f7c1a68bf4896c56ba54eaff (v5.17-rc7) 0006-net-stmmac-Add-per-packet-time-based-scheduling-for-X.conn 0017-net-networkproxy-introduce-network-proxy-framework.conn 0032-net-pcs-xpcs-combine-C37-SGMII-AN-and-2500BASEX-for-I.conn 0041-net-stmmac-add-check-for-advertising-linkmode-request.conn 0014-net-stmmac-Prevent-double-release-for-suspended-port-.conn 0004-net-stmmac-support-recalculating-of-CBS-idle-slope-un.conn 0046-taprio-Add-boundary-check-for-sched-entry-values.conn 0029-net-stmmac-add-fsleep-in-HW-Rx-timestamp-checking-loo.conn 0011-net-stmmac-Resolve-poor-line-rate-after-switching-fro.conn 0016-net-stmmac-selftest-replace-skb_unshare-with-skb_shar.conn 0021-net-stmmac-move-TX-RX-MAC-state-machine-enablement-to.conn 0005-REVERTME-net-stmmac-Add-module-param-to-del-keep-est-.conn 0001-net-stmmac-Bugfix-on-stmmac_interrupt-for-WOL.conn 0030-platform-x86-intel_pmc_core-Add-IPC-mailbox-accessor-.conn 0031-platform-x86-intel_pmc_core-Add-SoC-register-access.conn 0002-stmmac-intel-PCH-MSI-arbitration-WA-for-HW-bug.conn 0015-net-stmmac-optimize-locking-around-PTP-clock-reads.conn --> 642436a1ad34a28c45bbc2bdc131640a73782356 (v5.18-rc1) 0034-net-stmmac-enable-Intel-mGbE-1G-2.5G-auto-negotiation.conn stmmac: intel: Enable 2.5Gbps for Intel AlderLake-S --> 23d743301198f7903d732d5abb4f2b44f22f5df0 (v5.18-rc1) net: stmmac: switch to use interrupt for hw crosstimestamping --> 76c16d3e19446deea98b7883f261758b96b8781a (v5.19-rc8) net: stmmac:
[Kernel-packages] [Bug 2017929] 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/2017929 Title: Kernel 5.15.0-71 fails to boot on Ubuntu 22.04 (possibly specific to Ryzen APUs) Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 5.15.0-71 a couple of days ago, my PC sporadically fails to boot. I see the following error messages: "error: cannot allocate kernel buffer error: you need to load the kernel first. Press any key to continue..._ " I am then returned to the GRUB boot menu. This has also been experienced by two other AskUbuntu users: https://askubuntu.com/questions/1465460/after-kernel-update-error- cannot-allocate-kernel-buffer-you-need-to-load-kern . The common theme appears to be Ryzen APUs; two of us have 3400Gs and one has a 7600. In my case, the issue appears to be more likely to occur when I have to force-reboot because the system is frozen (due to a separate bug which I will link when I can find it again). But I have not yet reproduced it. Also the log files attached to this report may not contain relevant information as the last couple of boots worked correctly. I will try to capture a relevant kernel log now that I know this is a kernel issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-71-generic 5.15.0-71.78 ProcVersionSignature: Ubuntu 5.15.0-71.78-generic 5.15.92 Uname: Linux 5.15.0-71-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matthew1288 F pulseaudio /dev/snd/controlC0: matthew1288 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 27 17:49:11 2023 InstallationDate: Installed on 2022-01-14 (467 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Micro-Star International Co., Ltd. MS-7B89 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-71-generic root=UUID=7348d288-7351-45cd-8da2-592c59a4f7dd ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.15.0-71-generic N/A linux-backports-modules-5.15.0-71-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-05-26 (336 days ago) dmi.bios.date: 09/28/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.E3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.E3:bd09/28/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 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/2017929/+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 2017929] [NEW] Kernel 5.15.0-71 fails to boot on Ubuntu 22.04 (possibly specific to Ryzen APUs)
Public bug reported: Since upgrading to 5.15.0-71 a couple of days ago, my PC sporadically fails to boot. I see the following error messages: "error: cannot allocate kernel buffer error: you need to load the kernel first. Press any key to continue..._ " I am then returned to the GRUB boot menu. This has also been experienced by two other AskUbuntu users: https://askubuntu.com/questions/1465460/after-kernel-update-error- cannot-allocate-kernel-buffer-you-need-to-load-kern . The common theme appears to be Ryzen APUs; two of us have 3400Gs and one has a 7600. In my case, the issue appears to be more likely to occur when I have to force-reboot because the system is frozen (due to a separate bug which I will link when I can find it again). But I have not yet reproduced it. Also the log files attached to this report may not contain relevant information as the last couple of boots worked correctly. I will try to capture a relevant kernel log now that I know this is a kernel issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-71-generic 5.15.0-71.78 ProcVersionSignature: Ubuntu 5.15.0-71.78-generic 5.15.92 Uname: Linux 5.15.0-71-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matthew1288 F pulseaudio /dev/snd/controlC0: matthew1288 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 27 17:49:11 2023 InstallationDate: Installed on 2022-01-14 (467 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Micro-Star International Co., Ltd. MS-7B89 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-71-generic root=UUID=7348d288-7351-45cd-8da2-592c59a4f7dd ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.15.0-71-generic N/A linux-backports-modules-5.15.0-71-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-05-26 (336 days ago) dmi.bios.date: 09/28/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.E3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.E3:bd09/28/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy -- 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/2017929 Title: Kernel 5.15.0-71 fails to boot on Ubuntu 22.04 (possibly specific to Ryzen APUs) Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 5.15.0-71 a couple of days ago, my PC sporadically fails to boot. I see the following error messages: "error: cannot allocate kernel buffer error: you need to load the kernel first. Press any key to continue..._ " I am then returned to the GRUB boot menu. This has also been experienced by two other AskUbuntu users: https://askubuntu.com/questions/1465460/after-kernel-update-error- cannot-allocate-kernel-buffer-you-need-to-load-kern . The common theme appears to be Ryzen APUs; two of us have 3400Gs and one has a 7600. In my case, the issue appears to be more likely to occur when I have to force-reboot because the system is frozen (due to a separate bug which I will link when I can find it again). But I have not yet reproduced it. Also the log files attached to this report may not contain relevant information as the last couple of boots worked correctly. I will try to capture a relevant kernel log now that I know this is a kernel issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-71-generic 5.15.0-71.78 ProcVersionSignature: Ubuntu 5.15.0-71.78-generic 5.15.92 Uname: Linux 5.15.0-71-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matthew1288 F pulseaudio /dev/snd/controlC0: matthew1288 F pulseaudio CasperMD5CheckResult: pass
[Kernel-packages] [Bug 2012755] Re: [IOTG][RPL] Enable Time Coordinated Compute interface driver
** Description changed: Description Time Coordinated Compute (TCC) Pseudo SRAM interface support on top of Cache Allocation Technology Hardware: Tiger Lake & Elkhart Lake & Alder Lake & Ice Lake & Raptor Lake Target Release: 22.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.19-linux-221019T120731Z - Based on LP bug https://bugs.launchpad.net/intel/+bug/1929903, there are + Based on LP bug https://bugs.launchpad.net/intel/+bug/1996675, there are some more updates for this driver as following. 0017-Support-RPL-in-measurement-function.tcc 0018-Assume-default-hardware-prefetch-bitmask-in-measuremen.tcc 0019-tcc-fix-patch-style-problem.tcc 0020-tcc-Map-and-show-crl-version-number-in-proc.tcc 0022-tcc-Update-hardware-prefetcher-disable-bits-for-ADL-an.tcc 0023-tcc-Choose-different-L3-cache-miss-perf-event-for-ADL-.tcc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2012755 Title: [IOTG][RPL] Enable Time Coordinated Compute interface driver Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg source package in Jammy: In Progress Bug description: Description Time Coordinated Compute (TCC) Pseudo SRAM interface support on top of Cache Allocation Technology Hardware: Tiger Lake & Elkhart Lake & Alder Lake & Ice Lake & Raptor Lake Target Release: 22.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.19-linux-221019T120731Z Based on LP bug https://bugs.launchpad.net/intel/+bug/1996675, there are some more updates for this driver as following. 0017-Support-RPL-in-measurement-function.tcc 0018-Assume-default-hardware-prefetch-bitmask-in-measuremen.tcc 0019-tcc-fix-patch-style-problem.tcc 0020-tcc-Map-and-show-crl-version-number-in-proc.tcc 0022-tcc-Update-hardware-prefetcher-disable-bits-for-ADL-an.tcc 0023-tcc-Choose-different-L3-cache-miss-perf-event-for-ADL-.tcc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2012755/+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 2017928] 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/2017928 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: installed linux-image-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paresh 1806 F wireplumber /dev/snd/seq:paresh 1803 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Apr 27 19:02:59 2023 ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-07-27 (274 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 80TL ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=UUID=b70468ef-06b9-44bb-b285-666410c68fa2 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.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-04-27 (0 days ago) dmi.bios.date: 06/03/2020 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: 1KCN51WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V110-15ISK dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvr1KCN51WW:bd06/03/2020:br1.51:efr1.21:svnLENOVO:pn80TL:pvrLenovoV110-15ISK:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV110-15ISK:skuLENOVO_MT_80TL_BU_idea_FM_V110-15ISK: dmi.product.family: V110-15ISK dmi.product.name: 80TL dmi.product.sku: LENOVO_MT_80TL_BU_idea_FM_V110-15ISK dmi.product.version: Lenovo V110-15ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017928/+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 2017928] Re: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess r
** Tags removed: need-duplicate-check -- 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/2017928 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: New Bug description: installed linux-image-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paresh 1806 F wireplumber /dev/snd/seq:paresh 1803 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Apr 27 19:02:59 2023 ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-07-27 (274 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 80TL ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=UUID=b70468ef-06b9-44bb-b285-666410c68fa2 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.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-04-27 (0 days ago) dmi.bios.date: 06/03/2020 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: 1KCN51WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V110-15ISK dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvr1KCN51WW:bd06/03/2020:br1.51:efr1.21:svnLENOVO:pn80TL:pvrLenovoV110-15ISK:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV110-15ISK:skuLENOVO_MT_80TL_BU_idea_FM_V110-15ISK: dmi.product.family: V110-15ISK dmi.product.name: 80TL dmi.product.sku: LENOVO_MT_80TL_BU_idea_FM_V110-15ISK dmi.product.version: Lenovo V110-15ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017928/+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 2017928] [NEW] package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess
Public bug reported: installed linux-image-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paresh 1806 F wireplumber /dev/snd/seq:paresh 1803 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Apr 27 19:02:59 2023 ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-07-27 (274 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 80TL ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=UUID=b70468ef-06b9-44bb-b285-666410c68fa2 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.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-04-27 (0 days ago) dmi.bios.date: 06/03/2020 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: 1KCN51WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V110-15ISK dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvr1KCN51WW:bd06/03/2020:br1.51:efr1.21:svnLENOVO:pn80TL:pvrLenovoV110-15ISK:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV110-15ISK:skuLENOVO_MT_80TL_BU_idea_FM_V110-15ISK: dmi.product.family: V110-15ISK dmi.product.name: 80TL dmi.product.sku: LENOVO_MT_80TL_BU_idea_FM_V110-15ISK dmi.product.version: Lenovo V110-15ISK dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar -- 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/2017928 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: New Bug description: installed linux-image-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paresh 1806 F wireplumber /dev/snd/seq:paresh 1803 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Apr 27 19:02:59 2023 ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-07-27 (274 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 80TL ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=UUID=b70468ef-06b9-44bb-b285-666410c68fa2 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.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-04-27 (0 days ago) dmi.bios.date: 06/03/2020 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: 1KCN51WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10
[Kernel-packages] [Bug 2017571] Re: SIGNEDv4: add Azure CVM support to the linux-generate ancillary package
** Description changed: Combine azure & azure-fde packages We can generate signed vmlinuz and kernel.efi from the same build. Thus use the same build for both. == Plan of action == * Extend linux-signed & linux-generate to produce CVM specific package builds. * Apply that everywhere. - * Extend package.config inside azure cvm builds + * Extend package.config inside linux-signed-azure* to add cvm builds + * Add linux-meta changes for the above * Drop linux-azure-fde* source kernels -- 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/2017571 Title: SIGNEDv4: add Azure CVM support to the linux-generate ancillary package Status in linux package in Ubuntu: Triaged Bug description: Combine azure & azure-fde packages We can generate signed vmlinuz and kernel.efi from the same build. Thus use the same build for both. == Plan of action == * Extend linux-signed & linux-generate to produce CVM specific package builds. * Apply that everywhere. * Extend package.config inside linux-signed-azure* to add cvm builds * Add linux-meta changes for the above * Drop linux-azure-fde* source kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017571/+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 2017790] Re: Intel Wi-Fi 6 AX201 failing in 23.04
Remove the iwlwifi backports then -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/2017790 Title: Intel Wi-Fi 6 AX201 failing in 23.04 Status in linux-lowlatency package in Ubuntu: Confirmed Bug description: After upgrading from 22.04 to 23.04 the intel wifi driver is not loading, I am seeing the following in dmesg: [ 215.024382] Loading of unsigned module is rejected [ 262.051998] [ cut here ] [ 262.052001] WARNING: CPU: 2 PID: 6946 at net/netlink/genetlink.c:570 genl_validate_ops+0x1cc/0x270 [ 262.052007] Modules linked in: cfg80211(O+) rfcomm xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat nf_tables libcrc32c nfnetlink br_netfilter bridge stp llc vmw_vsock_vmci_transport vsock vmw_vmci snd_seq_dummy snd_hrtimer overlay cmac algif_hash algif_skcipher af_alg bnep dell_rbu typec_displayport snd_hda_codec_hdmi snd_ctl_led binfmt_misc snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel hid_logitech_hidpp soundwire_generic_allocation nls_iso8859_1 soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_compress ac97_bus x86_pkg_temp_thermal r8153_ecm snd_pcm_dmaengine intel_powerclamp cdc_ether coretemp snd_hda_intel usbnet snd_usb_audio kvm_intel snd_intel_dspcfg r8152 snd_intel_ sdw_acpi [ 262.052038] mii hid_plantronics hid_logitech_dj snd_usbmidi_lib snd_hda_codec kvm snd_hda_core snd_hwdep irqbypass mei_hdcp mei_pxp intel_rapl_msr dell_laptop snd_pcm crct10dif_pclmul i915 polyval_clmulni snd_seq_midi polyval_generic snd_seq_midi_event ghash_clmulni_intel sha512_ssse3 snd_rawmidi uvcvideo btusb videobuf2_vmalloc hid_sensor_custom_intel_hinge aesni_intel hid_sensor_gyro_3d hid_sensor_accel_3d dell_wmi videobuf2_memops snd_seq crypto_simd hid_sensor_trigger btrtl drm_buddy snd_seq_device btbcm videobuf2_v4l2 btintel processor_thermal_device_pci_legacy cryptd cmdlinepart industrialio_triggered_buffer dell_smbios rapl dcdbas snd_timer ttm dell_wmi_sysman btmtk videodev kfifo_buf spi_nor processor_thermal_device hid_sensor_iio_common processor_thermal_rfim intel_cstate firmware_attributes_class ledtrig_audio drm_display_helper dell_wmi_descriptor wmi_bmof industrialio mei_me mtd bluetooth snd videobuf2_common mc cec processor_thermal_mbox soundcore rc_core mei ecdh_ generic [ 262.052068] processor_thermal_rapl iwlwifi_compat(O) drm_kms_helper ecc ucsi_acpi joydev i2c_algo_bit intel_rapl_common typec_ucsi syscopyarea intel_soc_dts_iosf sysfillrect typec sysimgblt igen6_edac int3403_thermal soc_button_array int340x_thermal_zone int3400_thermal intel_hid acpi_thermal_rel acpi_pad acpi_tad sparse_keymap hid_multitouch input_leds mac_hid serio_raw msr parport_pc ppdev drm lp parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 usbhid hid_sensor_custom hid_sensor_hub intel_ishtp_hid hid_generic nvme nvme_core intel_ish_ipc i2c_hid_acpi spi_intel_pci rtsx_pci_sdmmc crc32_pclmul video i2c_i801 i2c_hid intel_lpss_pci xhci_pci spi_intel intel_ishtp nvme_common thunderbolt psmouse i2c_smbus intel_lpss rtsx_pci idma64 xhci_pci_renesas hid wmi pinctrl_tigerlake [ 262.052097] CPU: 2 PID: 6946 Comm: modprobe Tainted: GW O 6.2.0-1003-lowlatency #3-Ubuntu [ 262.052098] Hardware name: Dell Inc. Latitude 7420/07MHG4, BIOS 1.24.2 02/24/2023 [ 262.052099] RIP: 0010:genl_validate_ops+0x1cc/0x270 [ 262.052102] Code: 81 c4 d8 00 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d 31 d2 31 c9 31 ff c3 cc cc cc cc 49 83 7d 50 00 0f 85 b9 fe ff ff 0f 0b eb bd <0f> 0b eb b9 0f 0b eb b5 0f 0b eb b1 45 84 ff 75 04 31 c0 eb ad 4d [ 262.052103] RSP: 0018:a91bc7103a88 EFLAGS: 00010206 [ 262.052105] RAX: 0003 RBX: a91bc7103af0 RCX: [ 262.052106] RDX: RSI: RDI: [ 262.052106] RBP: a91bc7103b88 R08: R09: [ 262.052107] R10: R11: R12: 0001 [ 262.052107] R13: c1824780 R14: a91bc7103a88 R15: [ 262.052108] FS: 7fd67c380040() GS:8fcc7f68() knlGS: [ 262.052109] CS: 0010 DS: ES: CR0: 80050033 [ 262.052110] CR2: 7fff38c0e848 CR3: 00010a938006 CR4: 00770ee0 [ 262.052111] PKRU: 5554 [ 262.052112] Call Trace: [ 262.052113] [ 262.052115] ? __pfx_nl80211_pre_doit+0x10/0x10 [cfg80211] [ 262.052146] ? __pfx_nl80211_get_wiphy+0x10/0x10 [cfg80211] [ 262.052171] ? __pfx_nl80211_post_doit+0x10/0x10 [cfg80211] [
[Kernel-packages] [Bug 2017903] Re: LSM stacking and AppArmor for 6.2: additional fixes
Specially crafted tests that can reliably trigger this issue will be added to the test suite. -- 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/2017903 Title: LSM stacking and AppArmor for 6.2: additional fixes Status in linux package in Ubuntu: Triaged Status in linux source package in Lunar: Triaged Bug description: [Impact] We maintain custom LSM stacking and AppArmor SAUCE patches in our kernel to provide additional features that are not available in the upstream AppArmor. We have experienced occasional bugs in the lunar kernel (specifically with the environ.sh test) that can lead to system crashes / failures (such as potential NULL pointer dereference). [Test case] Run AppArmor autopkgtest / qa-regression-testing. [Fix] Apply the following additional fixes provided by AppArmor upstream maintainer: UBUNTU: SAUCE: apparmor: fix policy_compat perms remap for file dfa UBUNTU: SAUCE: apparmor: fix profile verification and enable it UBUNTU: SAUCE: apparmor: fix: add missing failure check in compute_xmatch_perms UBUNTU: SAUCE: apparmor: fix: kzalloc perms tables for shared dfas [Regression potential] Additional fixes are touching only AppArmor specific code, so we may experience regressions (bugs / behavior change) only in apparmor by applying them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017903/+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 2007579] Re: Raptor Lake Thermald ITMT version 2 support
@koba, thanks for your kinetic testing. The [test plan] however also has this bit: """ The thermald log should indicate version 2 is being used with the message: "ignore dummy_str: ds d1 d2 d3 " where ds = a string, d1 .. d3 are uint64 values that are parsed and ignored. """ Did you observe that message in the thermald log? I confess I don't know what in that message would indicate that "version 2 is being used", and I would have asked clarification on that before accepting the package. -- 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/2007579 Title: Raptor Lake Thermald ITMT version 2 support Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Bionic: Won't Fix Status in thermald source package in Focal: Won't Fix Status in thermald source package in Jammy: In Progress Status in thermald source package in Kinetic: Fix Committed Status in thermald source package in Lunar: Fix Released Bug description: == SRU Justification Kinetic == Raptor Lake system uses ITMT v2 instead of V1 for thermal configuration via GDDV. This was observed on Dell XPS 9320 system. Because thermald can't parse V2 table, it is not getting correct thermal threshold temperature and power limits. == The Fix == This is fixed in upstream thermald by the patch: https://github.com/intel/thermal_daemon/commit/90d56bc06cdcf78e7398ea7da389401516591774 This fix is part of Thermald 2.5.2 release. The fix applies cleanly and this is already in Ubuntu Lunar in thermald 2.5.2. The fix checks for illegal ITMT version and handles version 2 as a specific exceptional case. == Regression Risks == For systems that do not used ITMT, no change in behaviour will occur. Systems with versions > 2 (currently not valid) will not have ITMT parsed anymore; this will avoid misinterpreting unsupported ITMT data. Finally, version 2 of ITMT will be now parsed differently and additional fields will be parsed and these will be ignored as intended. == Test Plan == Test against a Dell XPS 9320 system. See if it handles the ITMT correctly. The thermald log should indicate version 2 is being used with the message: "ignore dummy_str: ds d1 d2 d3 " where ds = a string, d1 .. d3 are uint64 values that are parsed and ignored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2007579/+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 1990156] Re: Ubuntu 20.04 HWE Kernel refuses to boot Intel E810-XXV NIC
I can confirm the issue. Ubuntu 20.04.6 LTS on DELL PowerEdge R650 - 5.4.0-147-generic -> working 5.15.0-71-generic -> hangs at boot at "Starting Network Name Resolution..." -- 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/1990156 Title: Ubuntu 20.04 HWE Kernel refuses to boot Intel E810-XXV NIC Status in linux package in Ubuntu: Confirmed Bug description: Hi! We are using Ubuntu 20.04.5 LTS on 20 Dell PowerEdge R650 systems. The systems are equipped with "Intel(R) Ethernet 25G 2P E810-XXV Adapter" network cards. When using the 5.4 kernel (specifically we tested kernel 5.4.0-125-generic) the network card is working without issues. When using the HWE kernel (specifically we tested kernel 5.15.0-47-generic) the system will only boot when the NIC has not been configured using netplan. After configuring (and therefore enabling) the NIC in netplan, the system will hang at "Wait for network to be configured". After waiting for some time other error messages also are being shown: "INFO: task kworker xyz blocked for more than 120 seconds. Not tainted 5.15.0-46-generic" Same for task systemd-network and systemd-udevd. The NIC is using "ice" kernel driver: root@metal020:/home/philippalbrecht# dmesg | grep -i ethernet [5.085905] ice: Intel(R) Ethernet Connection E800 Series Linux Driver - version 0.8.1-k I suspect there have been changes performed in that particular driver between 5.4 and 5.15 release. If additional information is required I am happy to provide. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990156/+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 2017903] Re: LSM stacking and AppArmor for 6.2: additional fixes
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Triaged -- 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/2017903 Title: LSM stacking and AppArmor for 6.2: additional fixes Status in linux package in Ubuntu: Triaged Status in linux source package in Lunar: Triaged Bug description: [Impact] We maintain custom LSM stacking and AppArmor SAUCE patches in our kernel to provide additional features that are not available in the upstream AppArmor. We have experienced occasional bugs in the lunar kernel (specifically with the environ.sh test) that can lead to system crashes / failures (such as potential NULL pointer dereference). [Test case] Run AppArmor autopkgtest / qa-regression-testing. [Fix] Apply the following additional fixes provided by AppArmor upstream maintainer: UBUNTU: SAUCE: apparmor: fix policy_compat perms remap for file dfa UBUNTU: SAUCE: apparmor: fix profile verification and enable it UBUNTU: SAUCE: apparmor: fix: add missing failure check in compute_xmatch_perms UBUNTU: SAUCE: apparmor: fix: kzalloc perms tables for shared dfas [Regression potential] Additional fixes are touching only AppArmor specific code, so we may experience regressions (bugs / behavior change) only in apparmor by applying them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017903/+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 1990156] Re: Ubuntu 20.04 HWE Kernel refuses to boot Intel E810-XXV NIC
** Changed in: linux (Ubuntu) Status: Expired => 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/1990156 Title: Ubuntu 20.04 HWE Kernel refuses to boot Intel E810-XXV NIC Status in linux package in Ubuntu: Confirmed Bug description: Hi! We are using Ubuntu 20.04.5 LTS on 20 Dell PowerEdge R650 systems. The systems are equipped with "Intel(R) Ethernet 25G 2P E810-XXV Adapter" network cards. When using the 5.4 kernel (specifically we tested kernel 5.4.0-125-generic) the network card is working without issues. When using the HWE kernel (specifically we tested kernel 5.15.0-47-generic) the system will only boot when the NIC has not been configured using netplan. After configuring (and therefore enabling) the NIC in netplan, the system will hang at "Wait for network to be configured". After waiting for some time other error messages also are being shown: "INFO: task kworker xyz blocked for more than 120 seconds. Not tainted 5.15.0-46-generic" Same for task systemd-network and systemd-udevd. The NIC is using "ice" kernel driver: root@metal020:/home/philippalbrecht# dmesg | grep -i ethernet [5.085905] ice: Intel(R) Ethernet Connection E800 Series Linux Driver - version 0.8.1-k I suspect there have been changes performed in that particular driver between 5.4 and 5.15 release. If additional information is required I am happy to provide. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990156/+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 2016398] Re: stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?)
OK, so I am trying https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/lunar It seems it's 6.1 instead of 6.2, so maybe I am building the wrong one for 23.04, but if I build master I can replicate the issue with the built kernel. However if I revert 4f140b79ec36db30c9ba2118d966d875bef2a59b "UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files" and rebuild, I can no longer replicate the issue. The issue seems to be in 4f140b79ec36db30c9ba2118d966d875bef2a59b I have narrowed it down to a commit, however, I don't know how to fix it from here, but I hope narrowing it down to a commit helps -- 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/2016398 Title: stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?) Status in linux package in Ubuntu: Confirmed Bug description: Hi BACKGROUND: --- I have a set of scripts that debootstraps and builds vanilla Debian installs, where the only modifications are what packages are installed. Then that becomes the lower directory of an overlayfs mount, a tmpfs becomes the upperdir, and then that becomes the chroot where config changes are made with more scripts. This overlayfs is mounted in its own mount namespace as the script is unshare'd Within these scripts, I make packages with a fork of checkinstall I made which uses the / as the lowerdir, as overlayfs allows that, a tmpfs as the upperdir, the install command is run with chroot, and then the contents are copied. THE ISSUE: -- I noticed that it appears that my ramdisks are remaining in memory, I have isolated it out to the overlayfs mounts with the overlayfs as the lowerdir where chroot is being called on it. I tried entering the namespace myself and umounting it, and notice I get the error "Target is busy" With the "Target Is Busy" issue, I tried to `lsof` and `fuser` and `lsfd` as much as I could, but every user mode tool shows absolutely NO files open at all I was using Kubuntu 18.04, it was an old install and 32 bit, so I had no upgrade path to be using more recent versions. Now I am on 23.04, but I also think this is happening on a 22.10 laptop DIAGNOSIS: -- I am able to isolate it out, and get this to replicate in the smallest script that I could that is now attached. the chroot is important. I am able to unmount the second overlayfs if chroot is never called. Nothing ever has to run IN the chroot, trying to call a binary that does not exist, and then trying to unmount it results in "target is busy" with no open files reportable by user mode tools FURTHER TESTING: Trying to find out the version of Linux this was introduced, I made a script that builds a very minimal ext4 file for a VM with a small debootstrapped system, builds a kernel, and runs the kernel with QEMU.. but when I started, after all that, I can't replicate it at all with a vanilla 6.2.0 kernel. I used the same config out of my /boot to the .config, only tweaking a few options like SYSTEM_TRUSTED_KEYS. Trying to unmount the second filesystem actually results in success I then built a Kubuntu Lunar VM, and was able to replicate it on not just my system. When I built and install the vanilla kernel with bindeb-pkg, and then I boot the vanilla kernel, I can't replicate it, the second filesystem unmounts. When I reboot the VM, and start the default distribution kernel, I am able to replicate the issue, the second filesystem being unable to unmount, with "target is busy" with no files open according to standard usermode tools, when chroot is called on it I tried to look at patches in git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/lunar and git log --oneline --grep="sauce" but none of them really look relevant. I could be VERY wrong in this matter though SUMMARY: Long story short, (I am VERY sorry about the length:) I make an overlayfs, I make a second overlayfs with the first overlayfs as the second one's lowerdir, I chroot into the second overlayfs, and then later I can't unmount the second one as it says "Target is busy", but the user mode tools don't show any files open at all. If I mount the second overlayfs, and then unmount it without ever chroot-ing into it I AM able to unmount it The attached script should replicate the issue This doesn't seem to happen on the vanilla Linux kernel, with the same as close as possible config that Ubuntu uses Thanks ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER
[Kernel-packages] [Bug 2017903] Re: LSM stacking and AppArmor for 6.2: additional fixes
** Changed in: linux (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Lunar) Status: New => Triaged -- 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/2017903 Title: LSM stacking and AppArmor for 6.2: additional fixes Status in linux package in Ubuntu: Triaged Status in linux source package in Lunar: Triaged Bug description: [Impact] We maintain custom LSM stacking and AppArmor SAUCE patches in our kernel to provide additional features that are not available in the upstream AppArmor. We have experienced occasional bugs in the lunar kernel (specifically with the environ.sh test) that can lead to system crashes / failures (such as potential NULL pointer dereference). [Test case] Run AppArmor autopkgtest / qa-regression-testing. [Fix] Apply the following additional fixes provided by AppArmor upstream maintainer: UBUNTU: SAUCE: apparmor: fix policy_compat perms remap for file dfa UBUNTU: SAUCE: apparmor: fix profile verification and enable it UBUNTU: SAUCE: apparmor: fix: add missing failure check in compute_xmatch_perms UBUNTU: SAUCE: apparmor: fix: kzalloc perms tables for shared dfas [Regression potential] Additional fixes are touching only AppArmor specific code, so we may experience regressions (bugs / behavior change) only in apparmor by applying them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017903/+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 2017903] [NEW] LSM stacking and AppArmor for 6.2: additional fixes
Public bug reported: [Impact] We maintain custom LSM stacking and AppArmor SAUCE patches in our kernel to provide additional features that are not available in the upstream AppArmor. We have experienced occasional bugs in the lunar kernel (specifically with the environ.sh test) that can lead to system crashes / failures (such as potential NULL pointer dereference). [Test case] Run AppArmor autopkgtest / qa-regression-testing. [Fix] Apply the following additional fixes provided by AppArmor upstream maintainer: UBUNTU: SAUCE: apparmor: fix policy_compat perms remap for file dfa UBUNTU: SAUCE: apparmor: fix profile verification and enable it UBUNTU: SAUCE: apparmor: fix: add missing failure check in compute_xmatch_perms UBUNTU: SAUCE: apparmor: fix: kzalloc perms tables for shared dfas [Regression potential] Additional fixes are touching only AppArmor specific code, so we may experience regressions (bugs / behavior change) only in apparmor by applying them. ** Affects: linux (Ubuntu) Importance: Medium Status: Triaged ** Affects: linux (Ubuntu Lunar) Importance: Medium Status: Triaged ** Also affects: linux (Ubuntu Lunar) 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/2017903 Title: LSM stacking and AppArmor for 6.2: additional fixes Status in linux package in Ubuntu: Triaged Status in linux source package in Lunar: Triaged Bug description: [Impact] We maintain custom LSM stacking and AppArmor SAUCE patches in our kernel to provide additional features that are not available in the upstream AppArmor. We have experienced occasional bugs in the lunar kernel (specifically with the environ.sh test) that can lead to system crashes / failures (such as potential NULL pointer dereference). [Test case] Run AppArmor autopkgtest / qa-regression-testing. [Fix] Apply the following additional fixes provided by AppArmor upstream maintainer: UBUNTU: SAUCE: apparmor: fix policy_compat perms remap for file dfa UBUNTU: SAUCE: apparmor: fix profile verification and enable it UBUNTU: SAUCE: apparmor: fix: add missing failure check in compute_xmatch_perms UBUNTU: SAUCE: apparmor: fix: kzalloc perms tables for shared dfas [Regression potential] Additional fixes are touching only AppArmor specific code, so we may experience regressions (bugs / behavior change) only in apparmor by applying them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017903/+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 2012468] Re: Add Intel QAT Gen4 firmware
** Tags added: verification-needed-focal verification-needed-jammy verification-needed-kinetic -- 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/2012468 Title: Add Intel QAT Gen4 firmware Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Kinetic: Fix Committed Status in linux-firmware source package in Lunar: Fix Released Bug description: [Impact] The two Intel QAT Gen4 firmware files are already upstreamed: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/qat_4xxx.bin https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/qat_4xxx_mmp.bin Please consider to include them. Please also nominate to Focal and Jammy since they are LTS. [Fix] Cherry pick commit 24c9df9b942518717dd53966712df69ac35c8b90. [Where Problems Could Occur] This is new firmware which will get loaded if the relevant HW is present so could result in all sorts of (kernel) problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2012468/+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 2017846] Re: System kept waking up after pressing power button
Can you please attach logs from systemd-logind? $ journalctl -u systemd-logind.service -b 0 > systemd-logind-log.txt ** Changed in: systemd (Ubuntu) Status: New => 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/2017846 Title: System kept waking up after pressing power button Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Bug description: Tried it 3 times in the last 15min, each time it keeps waking back up. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yamiyuki 42974 F wireplumber /dev/snd/controlC3: yamiyuki 42974 F wireplumber /dev/snd/controlC0: yamiyuki 42974 F wireplumber /dev/snd/seq:yamiyuki 42972 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 27 00:45:37 2023 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic 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.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570S AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620 --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER Package: systemd 252.5-2ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: lunar Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Kernel-packages] [Bug 2009283] Re: linux: CONFIG_SERIAL_8250_MID=y
linux-image-unsigned-5.19.0-1010-nvidia/jammy-proposed,now 5.19.0-1010.10 amd64 [installed] linux-modules-5.19.0-1010-nvidia/jammy-proposed,now 5.19.0-1010.10 amd64 [installed,automatic] CONFIG_SERIAL_8250_MID=y ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- 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/2009283 Title: linux: CONFIG_SERIAL_8250_MID=y Status in linux package in Ubuntu: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: [Impact] CONFIG_SERIAL_8250_MID=y is required to properly use the serial console on some platforms that are using the "mid" serial driver (such as some Intel SoC platforms). The generic kernel should build this driver statically to make sure we properly support these platforms. [Test case] Boot the Ubuntu generic kernel on a system that is using the "mid" serial driver (e.g, no PCI serial). [Fix] Enable CONFIG_SERIAL_8250_MID=y. [Regression potential] Kernel footprint is increased a bit with this change (around +9K), so we may see little performance regressions at boot time in really small platforms (additional memory usage is probably negligible), but it is worth it, otherwise we won't be able to properly support these platforms. NOTE: we may want to disable this option in the could kernels and derivatives and keep it only for the generic. [Original bug report] Starting from 5.19 HWE kernel, this option became as dedicated module instead of being compiled into the kernel. 5.19 hwe-next also has CONFIG_SERIAL_8250_MID=m On 5.15 it was OK ~$ uname -r 5.19.0-32-generic $ cat /boot/config-5.19.0-32-generic | grep 8250_MID CONFIG_SERIAL_8250_MID=m Please make it CONFIG_SERIAL_8250_MID=y for all the future kernels. Previous ticket: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967338 Some discussion: https://lists.ubuntu.com/archives/kernel-team/2022-March/128690.html Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009283/+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 1981087] Proposed package upload rejected
An upload of thermald to jammy-proposed has been rejected from the upload queue for the following reason: "refers to private bugs". -- 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/1981087 Title: thermald prematurely throttling GPU Status in thermald package in Ubuntu: New Status in thermald source package in Jammy: Incomplete Bug description: [Impact] * thermald prematurely throttling GPU [Test Plan] Test1, * Run game on the target machine. * the FPS must not be significantly reduced. Test2, * Run on others platform, ADL/TGL/CML/CFL/KBL. * Use monitoring tool(e.g. s-tui) and stress-ng to verify if the machine runs normally. [Where problems could occur] * better support for Passive Policy. currently passive policy 1 is supported and it should have a bug if the machine only enable pssive policy 2. ~~~ I got a new game and started playing it It would run at over 100 FPS solidly some of the time and then cyclically dip down to below 20 FPS for a few minutes I determined that it was thermald trying to keep my GPU below 70°C to determine this I sudo systemctl stop thermald The game ran solidly and consistently with the GPU at 75°C This is well below the specs set by the manufacturer and perhaps unreasonably low for a laptop But more importantly I was given no indication this was happening. I had to sleuth it out myself. Perhaps it is impossible to determine good defaults for all hardware, I don't know. However without an indication that this is happening there will be a lot of people with a mysteriously broken experience. This was extremely difficult for me to find and I had several friend who are experts on linux gaming and video drivers trying to track this down. I discovered it by luck and perseverance. This absolutely needs some sort of indication and hopefully a way to remedy it from the GUI. ideally it would set thermal limits that are more in line with what the device is designed for and not a conservative default if at all possible. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thermald 2.4.9-1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Fri Jul 8 16:08:55 2022 InstallationDate: Installed on 2020-10-19 (626 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: thermald UpgradeStatus: Upgraded to jammy on 2022-06-17 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1981087/+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 2007579] Re: Raptor Lake Thermald ITMT version 2 support
** Tags removed: verification-needed-kinetic ** Tags added: verification-done-kinetic ** Tags removed: verification-needed ** Tags added: verification-done -- 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/2007579 Title: Raptor Lake Thermald ITMT version 2 support Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Bionic: Won't Fix Status in thermald source package in Focal: Won't Fix Status in thermald source package in Jammy: In Progress Status in thermald source package in Kinetic: Fix Committed Status in thermald source package in Lunar: Fix Released Bug description: == SRU Justification Kinetic == Raptor Lake system uses ITMT v2 instead of V1 for thermal configuration via GDDV. This was observed on Dell XPS 9320 system. Because thermald can't parse V2 table, it is not getting correct thermal threshold temperature and power limits. == The Fix == This is fixed in upstream thermald by the patch: https://github.com/intel/thermal_daemon/commit/90d56bc06cdcf78e7398ea7da389401516591774 This fix is part of Thermald 2.5.2 release. The fix applies cleanly and this is already in Ubuntu Lunar in thermald 2.5.2. The fix checks for illegal ITMT version and handles version 2 as a specific exceptional case. == Regression Risks == For systems that do not used ITMT, no change in behaviour will occur. Systems with versions > 2 (currently not valid) will not have ITMT parsed anymore; this will avoid misinterpreting unsupported ITMT data. Finally, version 2 of ITMT will be now parsed differently and additional fields will be parsed and these will be ignored as intended. == Test Plan == Test against a Dell XPS 9320 system. See if it handles the ITMT correctly. The thermald log should indicate version 2 is being used with the message: "ignore dummy_str: ds d1 d2 d3 " where ds = a string, d1 .. d3 are uint64 values that are parsed and ignored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2007579/+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 2007579] Proposed package upload rejected
An upload of thermald to jammy-proposed has been rejected from the upload queue for the following reason: "refers to private bugs". -- 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/2007579 Title: Raptor Lake Thermald ITMT version 2 support Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Bionic: Won't Fix Status in thermald source package in Focal: Won't Fix Status in thermald source package in Jammy: In Progress Status in thermald source package in Kinetic: Fix Committed Status in thermald source package in Lunar: Fix Released Bug description: == SRU Justification Kinetic == Raptor Lake system uses ITMT v2 instead of V1 for thermal configuration via GDDV. This was observed on Dell XPS 9320 system. Because thermald can't parse V2 table, it is not getting correct thermal threshold temperature and power limits. == The Fix == This is fixed in upstream thermald by the patch: https://github.com/intel/thermal_daemon/commit/90d56bc06cdcf78e7398ea7da389401516591774 This fix is part of Thermald 2.5.2 release. The fix applies cleanly and this is already in Ubuntu Lunar in thermald 2.5.2. The fix checks for illegal ITMT version and handles version 2 as a specific exceptional case. == Regression Risks == For systems that do not used ITMT, no change in behaviour will occur. Systems with versions > 2 (currently not valid) will not have ITMT parsed anymore; this will avoid misinterpreting unsupported ITMT data. Finally, version 2 of ITMT will be now parsed differently and additional fields will be parsed and these will be ignored as intended. == Test Plan == Test against a Dell XPS 9320 system. See if it handles the ITMT correctly. The thermald log should indicate version 2 is being used with the message: "ignore dummy_str: ds d1 d2 d3 " where ds = a string, d1 .. d3 are uint64 values that are parsed and ignored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2007579/+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 2012260] Re: Add support for Alder Lake N
An upload of thermald to jammy-proposed has been rejected from the upload queue for the following reason: "refers to private bugs". ** Also affects: thermald (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: thermald (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: thermald (Ubuntu) Status: In Progress => Fix Released -- 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/2012260 Title: Add support for Alder Lake N Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: New Status in thermald source package in Kinetic: New Bug description: [Impact] * Support thermald on Alder Lake N CPU. [Test Plan] * Use a machine with a Alder Lake N cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Alder Lake N in thermald, which won't impact other hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2012260/+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 2017877] [NEW] Intel Wireless 7260 - bluetooth drops from USB bus almost immediately after connecting a device on the lastest firmware
Public bug reported: The bluetooth in my Intel Wireless 7260 on my Thinkpad W541 resets almost immediately after a device connects. This is seen in dmesg as the device disconnecting and reconnecting to the USB bus with no other error messages, like this: [603851.305788] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 1 week 45 2013 [603851.305827] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq [603851.443776] Bluetooth: hci0: unexpected event for opcode 0xfc2f [603851.460922] Bluetooth: hci0: Intel BT fw patch 0x2a completed & activated [603871.948430] usb 3-11: USB disconnect, device number 36 [603872.273696] usb 3-11: new full-speed USB device number 37 using xhci_hcd [603872.422912] usb 3-11: New USB device found, idVendor=8087, idProduct=07dc, bcdDevice= 0.01 [603872.422916] usb 3-11: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [603872.437854] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 1 week 45 2013 [603872.437873] Bluetooth: hci0: Intel device is already patched. patch num: 2a [603894.932755] input: JBL TUNE700BT (AVRCP) as /devices/virtual/input/input113 [603898.742664] usb 3-11: USB disconnect, device number 37 [603899.057916] usb 3-11: new full-speed USB device number 38 using xhci_hcd [603899.211235] usb 3-11: New USB device found, idVendor=8087, idProduct=07dc, bcdDevice= 0.01 [603899.211241] usb 3-11: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [603899.226972] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 1 week 45 2013 [603899.226988] Bluetooth: hci0: Intel device is already patched. patch num: 2a [603909.785396] input: JBL TUNE700BT (AVRCP) as /devices/virtual/input/input114 [603914.565733] usb 3-11: USB disconnect, device number 38 [603916.905954] usb 3-11: new full-speed USB device number 39 using xhci_hcd [603917.055128] usb 3-11: New USB device found, idVendor=8087, idProduct=07dc, bcdDevice= 0.01 [603917.055147] usb 3-11: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [603917.071869] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 1 week 45 2013 [603917.071877] Bluetooth: hci0: Intel device is already patched. patch num: 2a This has been a problem ever since I got this laptop, but recently I managed to fix it by downgrading the ibt firmware. I downgraded the /lib/firmware/intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq file to this version https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/intel/ibt- hw-37.7.10-fw-1.80.1.2d.d.bseq?id=fb328183532ffc7a1a54e84fb53467e275a95b79 and after that all problems stopped. System info: $ lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 $ apt-cache policy linux-firmware linux-firmware: Installed: 20220329.git681281e4-0ubuntu3.12 Candidate: 20220329.git681281e4-0ubuntu3.12 Version table: *** 20220329.git681281e4-0ubuntu3.12 500 500 http://pl.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 100 /var/lib/dpkg/status 20220329.git681281e4-0ubuntu1 500 500 http://pl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu jammy/main i386 Packages $ lspci - (see attachment) $ lsusb -v (see attachment) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Attachment added: "system-info.txt" https://bugs.launchpad.net/bugs/2017877/+attachment/5669152/+files/system-info.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2017877 Title: Intel Wireless 7260 - bluetooth drops from USB bus almost immediately after connecting a device on the lastest firmware Status in linux-firmware package in Ubuntu: New Bug description: The bluetooth in my Intel Wireless 7260 on my Thinkpad W541 resets almost immediately after a device connects. This is seen in dmesg as the device disconnecting and reconnecting to the USB bus with no other error messages, like this: [603851.305788] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 1 week 45 2013 [603851.305827] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq [603851.443776] Bluetooth: hci0: unexpected event for opcode 0xfc2f [603851.460922] Bluetooth: hci0: Intel BT fw patch 0x2a completed & activated [603871.948430] usb 3-11: USB disconnect, device number 36 [603872.273696] usb 3-11: new full-speed USB device number 37 using xhci_hcd [603872.422912] usb 3-11: New USB device found, idVendor=8087, idProduct=07dc, bcdDevice= 0.01 [603872.422916] usb 3-11: New USB device strings: Mfr=0,
[Kernel-packages] [Bug 2017267] Re: Release upgrade to lunar lobster linux-headers-6.2.0-20 post-installation error
Short: I think downloading the new headers worked for me: https://packages.ubuntu.com/lunar/kernel/ Long: Before installing the new headers I tried to remove the new headers to run on the old kernel. Running on the old kernel is possible by just picking it from GRUB, so this was probably unnecessary in the first place anyway. When doing it I ran into the problem of beeing unable to create metapackages (which I removed to beeing able to remove the new kernel headers). I was unable to install metapackages with the old version (for kinetic). So, I decided to go back to the newest setup and downloaded and installed the new headers (again). When I finally had all dependencies in my list the install went through without a problem. So, I suspect this is just a problem of compiling the new kernel, right? I did no final reboot of the system yet... -- 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/2017267 Title: Release upgrade to lunar lobster linux-headers-6.2.0-20 post- installation error Status in linux package in Ubuntu: Confirmed Bug description: Ended with a dialog box: Could not install 'linux-headers-6.2.0-20-generic' The upgrade will continue but the 'linux-headers-6.2.0-20-generic' package may not be in a working state. Please consider submitting a bug report about it. installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-release-upgrader-core 1:23.04.6 ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 600:0:125:674842:2023-04-21 08:04:24.525593724 -0500:2023-04-21 08:04:24.613596272 -0500:/var/crash/linux-headers-6.2.0-20-generic.0.crash 644:0:125:1078246:2023-04-21 08:04:24.461591872 -0500:2023-04-21 08:04:24.869603682 -0500:/var/crash/nvidia-dkms-520.0.crash CurrentDesktop: ubuntu:GNOME Date: Fri Apr 21 08:09:44 2023 InstallationDate: Installed on 2021-01-04 (836 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-kitty XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago) VarLogDistupgradeTermlog: modified.conffile..etc.apport.report-ignore.README.denylist: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017267/+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 2004262] Re: Intel E810 NICs driver in causing hangs when booting and bonds configured
5.19.0-1010.10 works OK
root@m3-small-x86-01:~# uname -a
Linux m3-small-x86-01 5.19.0-1010-nvidia #10-Ubuntu SMP PREEMPT_DYNAMIC Tue Apr
25 23:39:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
root@m3-small-x86-01:~# lspci|grep E810
01:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for
SFP (rev 02)
01:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for
SFP (rev 02)
root@m3-small-x86-01:~# ping 8.8.8.8 -c 4
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=119 time=0.706 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=119 time=0.774 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=119 time=0.729 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=119 time=0.703 ms
--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3076ms
rtt min/avg/max/mdev = 0.703/0.728/0.774/0.028 ms
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
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/2004262
Title:
Intel E810 NICs driver in causing hangs when booting and bonds
configured
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Committed
Status in linux source package in Lunar:
Confirmed
Bug description:
[Impact]
* Intel E810-family NICs cause system hangs when booting with bonding
enabled
* This happens due to the driver unplugging auxiliary devices
* The unplug event happens under RTNL lock context, which causes a deadlock
where the RDMA driver waits for the RNL lock to complete removal
[Test Plan]
* Users have reported that after setting up bonding on switch and server
side, the system will hang when starting network services
[Fix]
* The upstream patch defers unplugging/re-plugging of the auxiliary device,
so that it's not performed under the RTNL lock context.
* Fix was introduced by commit:
248401cb2c46 ice: avoid bonding causing auxiliary plug/unplug under
RTNL lock
[Regression Potential]
* Regressions would manifest in devices that support RDMA functionality and
have been added to a bond
* We should look out for auxiliary devices that haven't been properly
unplugged, or that cause further issues with
ice_plug_aux_dev()/ice_unplug_aux_dev()
[Original Description]
jammy 22.04.1
linux-image-generic 5.15.0-58-generic
Intel E810-XXV Dual Port NICs in Dell PowerEdge 650
- 5.15 in jammy -> reproducible
- 5.19 in hwe-edge -> reproducible
- 6.2.rc6 in the mainline build -> works
- Intel's ice driver 1.10.1.2.2 -> works
After beonding is enabled on switch and server side, the system will
hang at initialing ubuntu. The kernel loads but around starting the
Network Services the system can hang for sometimes 5 minutes, and in
other cases, indefinitely.
The message of:
echo 0 > /proc/sys/kernel/hung_task_timeout_sec” systemd-resolve
blocked for more than 120 seconds
appears, and eventually the Network services just attempts to start
and never does. This is with or without DHCP enabled.
Tried this same setup with the hwe-22.04, hwe-20.04, hwe-22.04-ege and
linux-oem kernels and all exhibit the same failure.
To work around this. installing the Intel 'ice' driver of version
1.10.1.2.2 works. The system doesn't even remotely hang at startup
and all networking functions remain working (ping, DNS, general
accessibility).
The driver can be found at
https://downloadmirror.intel.com/763930/ice-1.10.1.2.2.tar.gz
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Jan 31 13:08 seq
crw-rw 1 root audio 116, 33 Jan 31 13:08 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5json:
{
"result": "skip"
}DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-01-27 (3 days ago)InstallationMedia:
Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Dell Inc. PowerEdge R650
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 mgag200drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic
root=UUID=668aab7c-abe9-434b-a810-acc6eab76cbc ro fsck.mode=skip
ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
RelatedPackageVersions:
linux-restricted-modules-5.15.0-58-generic N/A
linux-backports-modules-5.15.0-58-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.9
[Kernel-packages] [Bug 2017774] Re: both dell_backlight and nvidia_0 backlight interface appear, and can't adjust the display brightness
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2017774 Title: both dell_backlight and nvidia_0 backlight interface appear, and can't adjust the display brightness Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: In Progress Bug description: [Impact] When switched to discrete mode in the BIOS, nvidia driver will create its own backlight interface(nvidia_0) to control the backlight, but at the same time dell-laptop creates its own backlight interface(dell_backlight), too. In discrete mode, dell_backlight interface doesn't work, and it leads to gnome chooses the wrong interface(dell_backlight) to control the backlight and then leads to the issue. [Fix] The acpi_video_backlight_use_native() helper function is introduced after v6.1 and nvidia driver will call this function if kernel provides it. This helper tells video_detect module that nvidia controls the backlight, so that dell-laptop won't create another backlight interface when it's loaded Below commits are all from v6.1-rc1 fb1836c91317 ACPI: video: Prefer native over vendor a5df42521f32 ACPI: video: Simplify __acpi_video_get_backlight_type()454d61a56d5e ACPI: video: Make acpi_video_backlight_use_native() always return true b39be9f441f9 ACPI: video: Refactor acpi_video_get_backlight_type() a bit a2fc3c899bb0 ACPI: video: Drop backlight_device_get_by_type() call from acpi_video_get_backlight_type() 2600bfa3df99 ACPI: video: Add acpi_video_backlight_use_native() helper [Test] Verified on the target machine and confirmed dell_backlight interface is not generated. [Where problem could occur] All changes are in __acpi_video_get_backlight_type() function and to make it smarter to decide which type of backlight interface should be created. The final result is pretty similar to the latest mainline version, if it introduce any regression we can add quirk to list those misjudged machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2017774/+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 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
@Wiktor, Richard, i saw the kernel(5.19-42) hsa been in the proposed queue. Would you please enable the proposed and help to verify it? thanks ~~~ $ sudo apt install linux-image-5.19.0- linux-image-5.19.0-37-generic linux-image-5.19.0-30-generic linux-image-5.19.0-42-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/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Committed Bug description: [Impact] For amdgpu/i915, hdmi audio output device has disappeared. [Fix] The latest fix for the non-contiguous memalloc helper changed the allocation method for a non-IOMMU system to use only the fallback allocator. This should have worked, but it caused a problem sometimes when too many non-contiguous pages are allocated that can't be treated by HD-audio controller. As a quirk workaround, go back to the original strategy: use dma_alloc_noncontiguous() at first, and apply the fallback only when it fails, but only for non-IOMMU case [Test Case] 1. boot with kernel applied the patches. 2. check the cards in /proc/asound/cards. Get the hdmi cards. 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xe232 irq 137 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xe226 irq 134 [Where problems could occur] Low, this is just workaround and may have a better solution in the future. [Misc] All patches has been landed on OEM-6.1 and lunar. ~~ CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. Currently known affected cards: * HD 7700 (comment 8) * R9 290 (comment 21) * RX 550 (LP: #2012141, and comment 27) * RX 570 (mine) * RX 580 (LP: #2009276, and comment 28) * WX 3200 (comment 29) * RX 6600 (LP: #2009542) * RX 6700 (LP: #2009275) [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 for Jammy (22.04)
** Changed in: thermald (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) -- 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 for Jammy (22.04) Status in OEM Priority Project: New Status in thermald package in Ubuntu: New 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 these 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, there may have some cases that don't check the minimum of PL1 then make PL1 to smaller and smaller and throttle the CPU. this may cause machines run like the old behavior that doesn't have PL1 min/max. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+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 2017774] Re: both dell_backlight and nvidia_0 backlight interface appear, and can't adjust the display brightness
** Description changed: [Impact] + When switched to discrete mode in the BIOS, nvidia driver will create its own backlight interface(nvidia_0) to control the backlight, but at the same time dell-laptop creates its own backlight interface(dell_backlight), too. In discrete mode, dell_backlight interface doesn't work, and it leads to gnome chooses the wrong interface(dell_backlight) to control the backlight and then leads to the issue. + [Fix] + The acpi_video_backlight_use_native() helper function is introduced after v6.1 and nvidia driver will call this function if kernel provides it. This helper tells video_detect module that nvidia controls the backlight, so that dell-laptop won't create another backlight interface when it's loaded + + Below commits are all from v6.1-rc1 + fb1836c91317 ACPI: video: Prefer native over vendor + a5df42521f32 ACPI: video: Simplify __acpi_video_get_backlight_type()454d61a56d5e ACPI: video: Make acpi_video_backlight_use_native() always return true + b39be9f441f9 ACPI: video: Refactor acpi_video_get_backlight_type() a bit + a2fc3c899bb0 ACPI: video: Drop backlight_device_get_by_type() call from acpi_video_get_backlight_type() + 2600bfa3df99 ACPI: video: Add acpi_video_backlight_use_native() helper + [Test] + Verified on the target machine and confirmed dell_backlight interface is not generated. [Where problem could occur] + All changes are in __acpi_video_get_backlight_type() function and to make it smarter to decide which type of backlight interface should be created. The final result is pretty similar to the latest mainline version, if it introduce any regression we can add quirk to list those misjudged machines. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2017774 Title: both dell_backlight and nvidia_0 backlight interface appear, and can't adjust the display brightness Status in HWE Next: New Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.0 source package in Jammy: In Progress Bug description: [Impact] When switched to discrete mode in the BIOS, nvidia driver will create its own backlight interface(nvidia_0) to control the backlight, but at the same time dell-laptop creates its own backlight interface(dell_backlight), too. In discrete mode, dell_backlight interface doesn't work, and it leads to gnome chooses the wrong interface(dell_backlight) to control the backlight and then leads to the issue. [Fix] The acpi_video_backlight_use_native() helper function is introduced after v6.1 and nvidia driver will call this function if kernel provides it. This helper tells video_detect module that nvidia controls the backlight, so that dell-laptop won't create another backlight interface when it's loaded Below commits are all from v6.1-rc1 fb1836c91317 ACPI: video: Prefer native over vendor a5df42521f32 ACPI: video: Simplify __acpi_video_get_backlight_type()454d61a56d5e ACPI: video: Make acpi_video_backlight_use_native() always return true b39be9f441f9 ACPI: video: Refactor acpi_video_get_backlight_type() a bit a2fc3c899bb0 ACPI: video: Drop backlight_device_get_by_type() call from acpi_video_get_backlight_type() 2600bfa3df99 ACPI: video: Add acpi_video_backlight_use_native() helper [Test] Verified on the target machine and confirmed dell_backlight interface is not generated. [Where problem could occur] All changes are in __acpi_video_get_backlight_type() function and to make it smarter to decide which type of backlight interface should be created. The final result is pretty similar to the latest mainline version, if it introduce any regression we can add quirk to list those misjudged machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2017774/+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 1786013] Autopkgtest regression report (linux-meta-nvidia-5.19/5.19.0.1010.11)
All autopkgtests for the newly accepted linux-meta-nvidia-5.19 (5.19.0.1010.11) for jammy have finished running. The following regressions have been reported in tests triggered by the package: lttng-modules/2.13.8-1~ubuntu22.04.0 (arm64) snapd/2.58+22.04 (amd64) systemd/249.11-0ubuntu3.9 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-nvidia-5.19 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 2013088] Re: kernel: fix __clear_user() inline assembly constraints
This bug does not affect nvidia-5.19, hence set jammy to done again to unblock. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- 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/2013088 Title: kernel: fix __clear_user() inline assembly constraints Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Fix Released Bug description: SRU Justification: == [ Impact ] * In case clear_user() crosses two pages and faults on the second page the kernel may write lowcore contents to the first page, instead of clearing it. * The __clear_user() inline assembly misses earlyclobber constraint modifiers. Depending on compiler and compiler options this may lead to incorrect code which copies kernel lowcore contents to user space instead of clearing memory, in case clear_user() faults. [Fix] * For Kinetic and Jammy cherrypick of 89aba4c26fae 89aba4c26fae4e459f755a18912845c348ee48f3 "s390/uaccess: add missing earlyclobber annotations to __clear_user()" * For Focal and Bionic a backport of the above commit is needed: https://launchpadlibrarian.net/659551648/s390-uaccess.patch [ Test Plan ] * A test program in C is needed and used for testing. * The test will be done by IBM. [ Where problems could occur ] * The modification is limited to function 'long __clear_user'. * And there, just to one inline assembly constraints line. * This is usually difficult to trace. * A erroneous modification may lead to a wrong behavior in 'long __clear_user', * and maybe returning a wrong size (in uaccess.c). [ Other Info ] * This affects all Ubuntu releases in service, down to 18.04. * Since we are close to 23.04 kernel freeze, I submit a patch request for 23.04 separately, and submit the SRU request for the all other Ubuntu releases later. __ Description: kernel: fix __clear_user() inline assembly constraints Symptom: In case clear_user() crosses two pages and faults on the second page the kernel may write lowcore contents to the first page, instead of clearing it. Problem: The __clear_user() inline assembly misses earlyclobber constraint modifiers. Depending on compiler and compiler options this may lead to incorrect code which copies kernel lowcore contents to user space instead of clearing memory, in case clear_user() faults. Solution: Add missing earlyclobber constraint modifiers. Preventive:yes Upstream-ID: 89aba4c26fae4e459f755a18912845c348ee48f3 Affected Releases: 18.04 20.04 22.04 22.10 23.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2013088/+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
