[Kernel-packages] [Bug 2021933] Re: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: il sottoprocesso installato pacchetto linux-headers-6.2.0-20-generic script post-insta
*** This bug is a duplicate of bug 2017227 *** https://bugs.launchpad.net/bugs/2017227 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! ** This bug has been marked a duplicate of bug 2017227 package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: »installiertes post-installation-Skript des Paketes linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1 zurück -- 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/2021933 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: il sottoprocesso installato pacchetto linux- headers-6.2.0-20-generic script post-installation ha restituito lo stato di errore 1 Status in linux package in Ubuntu: Confirmed Bug description: the kernel don't work properly and can't be unintalled or repared ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-42.43-generic 5.19.17 Uname: Linux 5.19.0-42-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 AptOrdering: libkpathsea6:amd64: Install libsynctex2:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: corof 1821 F wireplumber /dev/snd/controlC0: corof 1821 F wireplumber /dev/snd/controlC1: corof 1821 F wireplumber /dev/snd/seq:corof 1818 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Wed May 31 06:40:52 2023 ErrorMessage: il sottoprocesso installato pacchetto linux-headers-6.2.0-20-generic script post-installation ha restituito lo stato di errore 1 InstallationDate: Installed on 2023-02-20 (99 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. enx0050b61f72cc no wireless extensions. MachineType: Dell Inc. Inspiron 560 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=7aa5bd90-70e2-4f81-aae9-f1d3a7582b96 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 RelatedPackageVersions: grub-pc 2.06-2ubuntu16 RfKill: SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: il sottoprocesso installato pacchetto linux-headers-6.2.0-20-generic script post-installation ha restituito lo stato di errore 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/10/2010 dmi.bios.release: 0.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 018D1Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA05:bd11/10/2010:br0.5:svnDellInc.:pnInspiron560:pvr00:rvnDellInc.:rn018D1Y:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0: dmi.product.family: 0 dmi.product.name: Inspiron 560 dmi.product.sku: 0 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021933/+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 2022036] [NEW] package linux-image-5.19.0-43-generic 5.19.0-43.44~22.04.1 failed to install/upgrade: installed linux-image-5.19.0-43-generic package post-installation script sub
Public bug reported: Very slow startup ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-43-generic 5.19.0-43.44~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jun 1 09:49:26 2023 ErrorMessage: installed linux-image-5.19.0-43-generic package post-installation script subprocess returned error exit status 135 InstallationDate: Installed on 2023-03-19 (73 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: linux-signed-hwe-5.19 Title: package linux-image-5.19.0-43-generic 5.19.0-43.44~22.04.1 failed to install/upgrade: installed linux-image-5.19.0-43-generic package post-installation script subprocess returned error exit status 135 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- 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/2022036 Title: package linux-image-5.19.0-43-generic 5.19.0-43.44~22.04.1 failed to install/upgrade: installed linux-image-5.19.0-43-generic package post- installation script subprocess returned error exit status 135 Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: Very slow startup ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-43-generic 5.19.0-43.44~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jun 1 09:49:26 2023 ErrorMessage: installed linux-image-5.19.0-43-generic package post-installation script subprocess returned error exit status 135 InstallationDate: Installed on 2023-03-19 (73 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: linux-signed-hwe-5.19 Title: package linux-image-5.19.0-43-generic 5.19.0-43.44~22.04.1 failed to install/upgrade: installed linux-image-5.19.0-43-generic package post-installation script subprocess returned error exit status 135 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/2022036/+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 1950627] Re: ubuntu_kernel_selftests:net:udpgro_fwd.sh: udpgso_bench_tx: sendmsg: Connection refused
** Merge proposal linked: https://code.launchpad.net/~canonical-kernel-team/+git/rt-hints/+merge/443928 -- 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/1950627 Title: ubuntu_kernel_selftests:net:udpgro_fwd.sh: udpgso_bench_tx: sendmsg: Connection refused Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Confirmed Status in linux source package in Kinetic: Confirmed Bug description: This is from ADT testing (amd64) but I believe I occasionally saw this before. It feels like sometimes the receiver does not get ready before the transmission starts. IIRC this goes away when re-trying. 02:52:31 DEBUG| [stdout] # selftests: net: udpgro_fwd.sh 02:52:31 DEBUG| [stdout] # IPv4 02:52:31 DEBUG| [stdout] # No GRO ok 02:52:32 DEBUG| [stdout] # GRO frag listok 02:52:32 DEBUG| [stdout] # GRO fwd ok 02:52:33 DEBUG| [stdout] # UDP fwd perfudp rx: 333 MB/s 271894 calls/s 02:52:33 DEBUG| [stdout] # udp tx:378 MB/s 6422 calls/s 6422 msg/s 02:52:34 DEBUG| [stdout] # udp rx:383 MB/s 312480 calls/s 02:52:34 DEBUG| [stdout] # udp tx:383 MB/s 6506 calls/s 6506 msg/s 02:52:35 DEBUG| [stdout] # udp rx:381 MB/s 310202 calls/s 02:52:35 DEBUG| [stdout] # udp tx:380 MB/s 6458 calls/s 6458 msg/s 02:52:36 DEBUG| [stdout] # UDP GRO fwd perfudp rx: 344 MB/s 280814 calls/s 02:52:36 DEBUG| [stdout] # udp tx:389 MB/s 6612 calls/s 6612 msg/s 02:52:37 DEBUG| [stdout] # udp rx:364 MB/s 297088 calls/s 02:52:37 DEBUG| [stdout] # udp tx:383 MB/s 6512 calls/s 6512 msg/s 02:52:38 DEBUG| [stdout] # udp rx:448 MB/s 365435 calls/s 02:52:38 DEBUG| [stdout] # udp tx:453 MB/s 7686 calls/s 7686 msg/s 02:52:39 DEBUG| [stdout] # GRO frag list over UDP tunnelok 02:52:39 DEBUG| [stdout] # GRO fwd over UDP tunnel ok 02:52:39 DEBUG| [stdout] # UDP tunnel fwd perf ./udpgso_bench_tx: sendmsg: Connection refused 02:52:39 DEBUG| [stdout] # fail client exit code 1, server 0 02:52:40 DEBUG| [stdout] # UDP tunnel GRO fwd perf udp rx: 236 MB/s 192389 calls/s 02:52:41 DEBUG| [stdout] # udp tx:284 MB/s 4826 calls/s 4826 msg/s 02:52:41 DEBUG| [stdout] # udp rx:295 MB/s 240586 calls/s 02:52:42 DEBUG| [stdout] # udp tx:306 MB/s 5206 calls/s 5206 msg/s 02:52:42 DEBUG| [stdout] # udp rx:306 MB/s 249784 calls/s 02:52:43 DEBUG| [stdout] # udp tx:310 MB/s 5263 calls/s 5263 msg/s 02:52:43 DEBUG| [stdout] # IPv6 02:52:43 DEBUG| [stdout] # No GRO ok 02:52:43 DEBUG| [stdout] # GRO frag listok 02:52:43 DEBUG| [stdout] # GRO fwd ok 02:52:44 DEBUG| [stdout] # UDP fwd perfudp rx: 82 MB/s66844 calls/s 02:52:45 DEBUG| [stdout] # udp tx:334 MB/s 5668 calls/s 5668 msg/s 02:52:45 DEBUG| [stdout] # udp rx:374 MB/s 305206 calls/s 02:52:46 DEBUG| [stdout] # udp tx:375 MB/s 6377 calls/s 6377 msg/s 02:52:46 DEBUG| [stdout] # udp rx:373 MB/s 303948 calls/s 02:52:47 DEBUG| [stdout] # udp tx:371 MB/s 6299 calls/s 6299 msg/s 02:52:48 DEBUG| [stdout] # UDP GRO fwd perfudp rx: 340 MB/s 277046 calls/s 02:52:48 DEBUG| [stdout] # udp tx:389 MB/s 6601 calls/s 6601 msg/s 02:52:49 DEBUG| [stdout] # udp rx:390 MB/s 318311 calls/s 02:52:49 DEBUG| [stdout] # udp tx:391 MB/s 6639 calls/s 6639 msg/s 02:52:50 DEBUG| [stdout] # udp rx:396 MB/s 322528 calls/s 02:52:50 DEBUG| [stdout] # udp tx:406 MB/s 6891 calls/s 6891 msg/s 02:52:50 DEBUG| [stdout] # GRO frag list over UDP tunnelok 02:52:50 DEBUG| [stdout] # GRO fwd over UDP tunnel ok 02:52:52 DEBUG| [stdout] # UDP tunnel fwd perf udp rx: 93 MB/s76354 calls/s 02:52:52 DEBUG| [stdout] # udp tx:257 MB/s 4360 calls/s 4360 msg/s 02:52:53 DEBUG| [stdout] # udp rx:297 MB/s 241883 calls/s 02:52:53 DEBUG| [stdout] # udp tx:315 MB/s 5352 calls/s 5352 msg/s 02:52:54 DEBUG| [stdout] # udp rx:286 MB/s 233207 calls/s 02:52:54 DEBUG| [stdout] # udp tx:304 MB/s 5172 calls/s 5172 msg/s 02:52:55 DEBUG| [stdout] # UDP tunnel GRO fwd perf udp rx: 267 MB/s 217607 calls/s 02:52:55 DEBUG| [stdout] # udp tx:297 MB/s 5039 calls/s 5039 msg/s 02:52:56 DEBUG| [stdout] # udp rx:300 MB/s 244255 calls/s 02:52:56 DEBUG| [stdout] # udp tx:304 MB/s 5164
[Kernel-packages] [Bug 2021949] Re: Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle
** Tags added: oem-priority originate-from-2016873 somerville ** Tags added: originate-from-2000668 -- 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/2021949 Title: Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: New Status in linux-oem-6.1 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-6.0 source package in Kinetic: New Status in linux-oem-6.1 source package in Kinetic: New Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: New Status in linux-oem-6.1 source package in Lunar: New Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: New Status in linux-oem-6.1 source package in Mantic: New Bug description: [Impact] Enabling CL1 (Controller Low Power) states during discovery of existing tunnels established by the system firmware can interfere with the operation of those tunnels. The DisplayPort tunnel establishment timeout of 1.5 seconds can be insufficient for some docking stations, leading to blank displays. [Fix] CL1 states are now not enabled during discovery of existing tunnels. The TMU settings also remain unchanged. The timeout is increased to 3 seconds to allow more time for the DisplayPort connection manager handshake, fixing the issue of displays remaining blank. [Test Cases] 1. plug docking station on the host 2. bring up the host and get into desktop. 3. flip docking station's cable. 4. check if the external monitor works well [Where problems could occur] Low, If the handshake actually requires even more than 3 seconds in some cases, the timeout may still need to be increased further. [Misc] Jammy needs more patches to enable the thunderbolt CLx and the SRU will be a huge, so skip Jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2021949/+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 2021949] Re: Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle
** Description changed: [Impact] + Enabling CL1 (Controller Low Power) states during discovery of existing tunnels established by the system firmware can interfere with the operation of those tunnels. + The DisplayPort tunnel establishment timeout of 1.5 seconds can be insufficient for some docking stations, leading to blank displays. [Fix] + CL1 states are now not enabled during discovery of existing tunnels. The TMU settings also remain unchanged. + The timeout is increased to 3 seconds to allow more time for the DisplayPort connection manager handshake, fixing the issue of displays remaining blank. [Test Cases] + 1. plug docking station on the host + 2. bring up the host and get into desktop. + 3. flip docking station's cable. + 4. check if the external monitor works well [Where problems could occur] + Low, If the handshake actually requires even more than 3 seconds in some cases, the timeout may still need to be increased further. ** Description changed: [Impact] Enabling CL1 (Controller Low Power) states during discovery of existing tunnels established by the system firmware can interfere with the operation of those tunnels. - The DisplayPort tunnel establishment timeout of 1.5 seconds can be insufficient for some docking stations, leading to blank displays. + The DisplayPort tunnel establishment timeout of 1.5 seconds can be insufficient for some docking stations, leading to blank displays. [Fix] - CL1 states are now not enabled during discovery of existing tunnels. The TMU settings also remain unchanged. + CL1 states are now not enabled during discovery of existing tunnels. The TMU settings also remain unchanged. The timeout is increased to 3 seconds to allow more time for the DisplayPort connection manager handshake, fixing the issue of displays remaining blank. [Test Cases] 1. plug docking station on the host 2. bring up the host and get into desktop. 3. flip docking station's cable. 4. check if the external monitor works well [Where problems could occur] Low, If the handshake actually requires even more than 3 seconds in some cases, the timeout may still need to be increased further. + + [Misc] + Jammy needs more patches to enable the thunderbolt CLx and the SRU will be a huge, + so skip 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/2021949 Title: Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: New Status in linux-oem-6.1 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-6.0 source package in Kinetic: New Status in linux-oem-6.1 source package in Kinetic: New Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: New Status in linux-oem-6.1 source package in Lunar: New Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: New Status in linux-oem-6.1 source package in Mantic: New Bug description: [Impact] Enabling CL1 (Controller Low Power) states during discovery of existing tunnels established by the system firmware can interfere with the operation of those tunnels. The DisplayPort tunnel establishment timeout of 1.5 seconds can be insufficient for some docking stations, leading to blank displays. [Fix] CL1 states are now not enabled during discovery of existing tunnels. The TMU settings also remain unchanged. The timeout is increased to 3 seconds to allow more time for the DisplayPort connection manager handshake, fixing the issue of displays remaining blank. [Test Cases] 1. plug docking station on the host 2. bring up the host and get into desktop. 3. flip docking station's cable. 4. check if the external monitor works well [Where problems could occur] Low, If the handshake actually requires even more than 3 seconds in some cases, the timeout may still need to be increased further. [Misc] Jammy needs more patches to enable the thunderbolt CLx and the SRU will be a huge, so skip Jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2021949/+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 1801540]
Created attachment 304349 patch_realtek_alc1220_record.diff Hi all: Basically, ASUS CROSSHAIR VI HERO only provides Windows version, not Linux version. You can try it, after entering the LINUX OS (ALC1220, 0x10ec1022, subsytem ID: 10438735) "sudo su root" type root password "hda-verb /dev/snd/hwC1D0 0x20 SET_COEF_INDEX 0x15" "hda-verb /dev/snd/hwC1D0 0x20 SET_PROC_COEF 0x06e0" "hda-verb /dev/snd/hwC1D0 0x20 SET_COEF_INDEX 0x6f" "hda-verb /dev/snd/hwC1D0 0x20 SET_PROC_COEF 0xc03b" Try recording, will it still break? If possible, please install the PATCH file in the LINUX Kernel source and try it out. Best regards pshou -Original Message- From: bugzilla-dae...@kernel.org Sent: Thursday, May 25, 2023 8:13 PM To: Pshou Subject: [Bug 195303] AMD HD-audio controller: Sound capture is crackled / distorted External mail. https://bugzilla.kernel.org/show_bug.cgi?id=195303 --- Comment #306 from har...@gmx.de --- Created attachment 304321 --> https://bugzilla.kernel.org/attachment.cgi?id=304321=edit script to adapt alc3234 codec coefs -- You may reply to this email to add a comment. You are receiving this mail because: You are on the CC list for the bug. --Please consider the environment before printing this e-mail. -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+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 2009243] Re: kernel 5.19.0-35 clobbers Creative S/B AE-7 Sound Card
Hmm, while the Sound Blaster can now be seen for me in PulseAudio with kernels 5.19.0-42 and 5.19.0-43, it's still not fully functioning properly. It will not appear as a sink if the profile on the card is set to anything but stereo output or duplex. I need my card to output 5.1 surround sound audio, so the card is still not working. The kernel log will output the following when the card fails to appear as a sink: May 31 16:24:49 HX kernel: [ 578.234426] snd_hda_intel :02:00.0: Too many BDL entries: buffer=4194048, period=2097024 May 31 16:24:49 HX kernel: [ 578.237600] snd_hda_intel :02:00.0: Too many BDL entries: buffer=1058304, period=529152 May 31 16:24:49 HX kernel: [ 578.240558] snd_hda_intel :02:00.0: Too many BDL entries: buffer=2116608, period=1058304 May 31 16:24:49 HX kernel: [ 578.242650] snd_hda_intel :02:00.0: Too many BDL entries: buffer=1058304, period=40704 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009243 Title: kernel 5.19.0-35 clobbers Creative S/B AE-7 Sound Card Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: 2023-03-03 Attempted install of kernel 5.19.0-35 using the Linux Mint package installer LM 21.1 Vera, release 21.1). Clobbered my Sound Blaster AE-7. Could not even locate the device using Sound manager utility on Linux Mint Panel (the enumerated device showed up as the embedded sound chip on the mobo which I had previously disabled in the UEFI setup). Uninstalled kernel and reverted back to 5.19.0-32 using Timeshift restore feature which worked fine before the update to 5.19.0-35. Tried again to install 5.19.0-35 the same way, just to be sure. The SB AE-7 got clobbered again. So restored back to 5.19.0-32 generic one more time, using Timeshift. SB AE-7 works fine now with this lower version kernel. Current hardware config: Asus Prime Z790-P wifi mobo. Intel Core i3-13100 processor (with Intel UHD 730 graphics). Corsair Vengeance DDR5 32gb (2x16) ram, 5200Mhz. 3 x Nvme SSD. Boot drive is Western Digital Black SN770 500gb. Asus Nvidia RTX-3050 PCIe graphics card. Creative Labs Sound Blaster AE-7 audio card (PCIe). On-board audio chip (Realtek 7.1 Surround Sound High Definition Audio) is disabled in UEFI. UEFI is AMI/BIOS, revision 0812. Linux Mint 21.1 is running on barebones hardware, no VM involved. No other O/S's are installed on the machine. - Running sudo lspci -vnvn > lspci-vnvn.log gave the following error message... pcilib: sysfs_read_vpd: read failed: No such device --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mikey 4106 F wireplumber /dev/snd/controlC0: mikey 4106 F wireplumber /dev/snd/seq:mikey 4105 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-31 (32 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: ASUS System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=854c280c-7c5c-494d-a304-db66cf592baf ro quiet splash ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 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-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: vera Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/24/2023 dmi.bios.release: 8.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0812 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z790-P WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0812:bd02/24/2023:br8.12:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ790-PWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS
[Kernel-packages] [Bug 2022001] Re: Kernel 5.19.0-42 onward crashes with VMSVGA + 3D acceleration
>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'. Cannot open application windows, as already stated in the bug description, the window or the whole desktop crashes. ** Description changed: KDE Neon 5.27 (Ubuntu 22.04 Jammy) Kernel: linux-image-5.19.0-43-generic Steps to reproduce: 0. Install KDE Neon into Virtualbox 1. Install kernel version 5.19.0-42 or -43 (-generic) 2. Boot the system 3. Log in to KDE desktop 4. Try and open a window or right-click on the desktop Expected outcome: A window opens, or a desktop context menu opens Actual outcome: - Desktop crashes, after that system freezes + - opening a window: X server crashes. Logging in again and opening a window: system crash + - opening a desktop context menu: desktop crashes, after that system freezes Additional info: - dmesg shows a kernel crash trace - kernel 5.19.0-38-generic works OK. ** 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/2022001 Title: Kernel 5.19.0-42 onward crashes with VMSVGA + 3D acceleration Status in linux package in Ubuntu: Confirmed Bug description: KDE Neon 5.27 (Ubuntu 22.04 Jammy) Kernel: linux-image-5.19.0-43-generic Steps to reproduce: 0. Install KDE Neon into Virtualbox 1. Install kernel version 5.19.0-42 or -43 (-generic) 2. Boot the system 3. Log in to KDE desktop 4. Try and open a window or right-click on the desktop Expected outcome: A window opens, or a desktop context menu opens Actual outcome: - opening a window: X server crashes. Logging in again and opening a window: system crash - opening a desktop context menu: desktop crashes, after that system freezes Additional info: - dmesg shows a kernel crash trace - kernel 5.19.0-38-generic works OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022001/+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 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts
This bug was fixed in the package clamav - 0.103.8+dfsg-0ubuntu2
---
clamav (0.103.8+dfsg-0ubuntu2) mantic; urgency=medium
* Extend ifupdown script to support networkd-dispatcher.
- d/clamav-freshclam-ifupdown: Modernize some parts of
the script. Implement support for networkd-dispatcher.
- d/clamav-freshclam.links: Install the
clamav-freshclam-ifupdown script inside the proper
/usr/lib/networkd-dispatcher/{off,routable}.d/
directories.
(LP: #1718227)
-- Sergio Durigan Junior Fri, 12 May
2023 15:58:29 -0400
** Changed in: clamav (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1718227
Title:
replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
Status in aiccu package in Ubuntu:
Invalid
Status in aoetools package in Ubuntu:
New
Status in avahi package in Ubuntu:
New
Status in bind9 package in Ubuntu:
Invalid
Status in chrony package in Ubuntu:
Fix Released
Status in clamav package in Ubuntu:
Fix Released
Status in controlaula package in Ubuntu:
Invalid
Status in ethtool package in Ubuntu:
Triaged
Status in guidedog package in Ubuntu:
New
Status in htpdate package in Ubuntu:
New
Status in ifenslave package in Ubuntu:
Won't Fix
Status in ifmetric package in Ubuntu:
Won't Fix
Status in ifupdown-multi package in Ubuntu:
New
Status in ifupdown-scripts-zg2 package in Ubuntu:
Invalid
Status in isatapd package in Ubuntu:
New
Status in lprng package in Ubuntu:
New
Status in miredo package in Ubuntu:
New
Status in mythtv package in Ubuntu:
New
Status in netplan.io package in Ubuntu:
New
Status in nplan package in Ubuntu:
Invalid
Status in nss-pam-ldapd package in Ubuntu:
Fix Released
Status in ntp package in Ubuntu:
Won't Fix
Status in openntpd package in Ubuntu:
New
Status in openresolv package in Ubuntu:
Won't Fix
Status in openssh package in Ubuntu:
Fix Released
Status in openvpn package in Ubuntu:
Confirmed
Status in openvswitch package in Ubuntu:
Triaged
Status in postfix package in Ubuntu:
Fix Released
Status in quicktun package in Ubuntu:
New
Status in resolvconf package in Ubuntu:
New
Status in sendmail package in Ubuntu:
New
Status in shorewall-init package in Ubuntu:
New
Status in sidedoor package in Ubuntu:
New
Status in slrn package in Ubuntu:
New
Status in tinc package in Ubuntu:
New
Status in ubuntu-fan package in Ubuntu:
Fix Released
Status in ucarp package in Ubuntu:
New
Status in uml-utilities package in Ubuntu:
New
Status in uruk package in Ubuntu:
New
Status in vlan package in Ubuntu:
Won't Fix
Status in vzctl package in Ubuntu:
Triaged
Status in wide-dhcpv6 package in Ubuntu:
New
Status in wpa package in Ubuntu:
New
Bug description:
when network is configured with ifupdown, scripts in
/etc/network/ifup.d/ were called on network being brought up and
/etc/network/ifdown.d were called on network being brought down.
Any packages that shipped these hooks need to be verified to have the
same functionality under a netplan configured system.
# binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
# for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u
aiccu
aoetools
avahi
bind9
chrony
clamav
controlaula
epoptes
ethtool
guidedog
htpdate
ifenslave
ifmetric
ifupdown-extra
ifupdown-multi
ifupdown-scripts-zg2
isatapd
lprng
miredo
mythtv-backend
nss-pam-ldapd
ntp
openntpd
openresolv
openssh
openvpn
postfix
quicktun
resolvconf
sendmail
shorewall-init
sidedoor
slrn
tinc
ubuntu-fan
ucarp
uml-utilities
uruk
vlan
vzctl
wide-dhcpv6
wpa
Related bugs:
* bug 1718227: replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
* bug 1713803: replacement of resolvconf with systemd needs integration
* bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for
dhclient needs integration
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Sep 19 10:53:08 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (789 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: plan
UpgradeStatus: No upgrade log present (probably fresh
[Kernel-packages] [Bug 2022001] 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 2022001 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/2022001 Title: Kernel 5.19.0-42 onward crashes with VMSVGA + 3D acceleration Status in linux package in Ubuntu: Incomplete Bug description: KDE Neon 5.27 (Ubuntu 22.04 Jammy) Kernel: linux-image-5.19.0-43-generic Steps to reproduce: 0. Install KDE Neon into Virtualbox 1. Install kernel version 5.19.0-42 or -43 (-generic) 2. Boot the system 3. Log in to KDE desktop 4. Try and open a window or right-click on the desktop Expected outcome: A window opens, or a desktop context menu opens Actual outcome: Desktop crashes, after that system freezes Additional info: - dmesg shows a kernel crash trace - kernel 5.19.0-38-generic works OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022001/+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 2013390] Re: CPU Lockup related to xhci/DMA
Hello? Has anyone worked on this bug? It's a simple patch: https://bugzilla.kernel.org/show_bug.cgi?id=217242 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/2013390 Title: CPU Lockup related to xhci/DMA Status in linux-signed-hwe-5.13 package in Ubuntu: New Status in linux-signed-hwe-5.15 package in Ubuntu: Confirmed Status in linux-signed-hwe-5.19 package in Ubuntu: New Status in linux-signed-lowlatency package in Ubuntu: New Status in linux-signed-lowlatency-hwe-5.15 package in Ubuntu: New Bug description: CPU lockup problems have been encountered on a number of computers running kernel 5.15 or later, but this problem could've been introduced in an earlier version. Three of these systems are running a light weight version of Ubuntu. The kernels that have been tested are 4.19, 5.15, 5.18, 5.19, 6.0, and 6.1. The basic setup that's running and causing problems is a program that starts several (4+) distinct processes and communicates with different ACM/USB concurrently. This problem can be encountered a few minutes after starting this program up to about a week later, but it generally happens after ~1-3 days. When the lock up occurs, if there are the same number or fewer CPU cores than the running number of running processes doing ACM/USB device communication, nothing else will execute due to all of the CPU cores being locked up until the watchdog frees things up. The longest lockup that has been encountered was over 20 minutes! The computers that this problem has been tested and verified to be present on are the NUC7i5BNK, the ASRock NUC BOX-1260P, and the LattePanda Delta 3. Although, this problem appears to be system agnostic; if kernel version ~5.15 or later is being used, it'll likely happen if this program is setup and run on any system when enough known ACM/USB devices are connected to it and communicated with concurrently from different processes. The main reason "this program" is being stated in a broad sense is because multiple different setups fitting that description have been tested trying to get around encountered problems in various clever ways and this problem has persisted regardless of what's been done. Here's a short snippet from the LattePanda Delta 3's syslog: Mar 21 15:35:59 LattePanda kernel: [437064.977491] NMI watchdog: Watchdog detected hard LOCKUP on cpu 1 Mar 21 15:35:59 LattePanda kernel: [437064.977496] Modules linked in: tls binfmt_misc snd_sof_pci_intel_icl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence intel_rapl_msr snd_sof_intel_hda mei_hdcp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi intel_rapl_common soundwire_bus x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic coretemp ledtrig_audio snd_soc_core nls_iso8859_1 snd_compress ac97_bus kvm_intel snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg kvm snd_intel_sdw_acpi intel_cstate snd_hda_codec snd_hda_core btusb rtsx_usb_ms btrtl btbcm snd_hwdep btintel bluetooth memstick iwlmvm snd_pcm ecdh_generic snd_timer ecc wmi_bmof mac80211 snd libarc4 soundcore 8250_dw mei_me mei iwlwifi ftdi_sio pl2303 cp210x cdc_acm usbserial cfg80211 goodix acpi_tad mac_hid acpi_pad dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua sch_fq_cod el ramoops efi_pstore reed_solomon Mar 21 15:35:59 LattePanda kernel: [437064.977544] pstore_blk pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c rtsx_usb_sdmmc rtsx_usb mmc_block i915 ttm drm_kms_helper syscopyarea sysfillrect igb sysimgblt fb_sys_fops spi_pxa2xx_platform cec dca crct10dif_pclmul rc_core dw_dmac i2c_i801 crc32_pclmul dw_dmac_core ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_smbus i2c_algo_bit sdhci_pci ahci cqhci drm libahci intel_lpss_pci sdhci intel_lpss xhci_pci idma64 xhci_pci_renesas wmi video pinctrl_jasperlake Mar 21 15:35:59 LattePanda kernel: [437064.977572] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G L 5.15.0-67-lowlatency #74-Ubuntu Mar 21 15:35:59 LattePanda kernel: [437064.977575] Hardware name: LattePanda LattePanda 3 Delta/LattePanda 3 Delta, BIOS LP-BS-7-S70JR120-CN51G-D 08/15/2022 Mar 21 15:35:59 LattePanda kernel: [437064.977576] RIP: 0010:native_queued_spin_lock_slowpath.part.0+0x4f/0x200 Mar 21 15:35:59 LattePanda kernel: [437064.977584] Code: 0f ba 2b 08 0f 92 c2 8b 03 0f b6 d2 c1 e2 08 30 e4 09 d0 a9 00 01 ff ff 0f 85 2a 01 00 00 85 c0 74 0e 8b 03 84 c0 74 08 f3 90 <8b> 03 84 c0 75 f8 b8 01 00 00 00 66 89 03 5b 41 5c 41 5d 41 5e 41 Mar 21 15:35:59 LattePanda kernel: [437064.977586] RSP: 0018:b42d4007ce80 EFLAGS: 0002 Mar 21 15:35:59 LattePanda kernel: [437064.977587] RAX: 000c0101 RBX: 9737c026c2ac
[Kernel-packages] [Bug 2022001] Re: Kernel 5.19.0-42 onward crashes with VMSVGA + 3D acceleration
** Tags added: jammy ** Package changed: ubuntu => linux (Ubuntu) -- 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/2022001 Title: Kernel 5.19.0-42 onward crashes with VMSVGA + 3D acceleration Status in linux package in Ubuntu: New Bug description: KDE Neon 5.27 (Ubuntu 22.04 Jammy) Kernel: linux-image-5.19.0-43-generic Steps to reproduce: 0. Install KDE Neon into Virtualbox 1. Install kernel version 5.19.0-42 or -43 (-generic) 2. Boot the system 3. Log in to KDE desktop 4. Try and open a window or right-click on the desktop Expected outcome: A window opens, or a desktop context menu opens Actual outcome: Desktop crashes, after that system freezes Additional info: - dmesg shows a kernel crash trace - kernel 5.19.0-38-generic works OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022001/+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-oem-6.0/6.0.0.1018.18)
All autopkgtests for the newly accepted linux-meta-oem-6.0 (6.0.0.1018.18) for jammy have finished running. The following regressions have been reported in tests triggered by the package: backport-iwlwifi-dkms/9858-0ubuntu3.2 (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-oem-6.0 [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 2021997] 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/2021997 Title: Regression. kernel 5.19.0.43.39 does not boot wirth errors: cannot allocate kernel buffer. you need to load the kernel first. Status in linux package in Ubuntu: Confirmed Bug description: Newly installed kernel linux-image-5.19.0-43-generic 5.19.0.43.39 does not boot with the following diagnostics: - error: cannot allocate kernel buffer. error: you need to load the kernel first. Press any key to continue... Failed to boot both default and fallback entries. Press any key to continue... - And after a short while gets back to grub selection menu. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-43-generic 5.19.0-43.44 ProcVersionSignature: Ubuntu 5.19.0-42.43-generic 5.19.17 Uname: Linux 5.19.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexei 2618 F wireplumber /dev/snd/controlC0: alexei 2618 F wireplumber /dev/snd/seq:alexei 2616 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed May 31 20:31:01 2023 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (2701 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp8s0no wireless extensions. lxcbr0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro 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-42-generic N/A linux-backports-modules-5.19.0-42-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.6 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-01 (241 days ago) dmi.bios.date: 05/10/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.00 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.00:bd05/10/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021997/+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 2021997] [NEW] Regression. kernel 5.19.0.43.39 does not boot wirth errors: cannot allocate kernel buffer. you need to load the kernel first.
Public bug reported: Newly installed kernel linux-image-5.19.0-43-generic 5.19.0.43.39 does not boot with the following diagnostics: - error: cannot allocate kernel buffer. error: you need to load the kernel first. Press any key to continue... Failed to boot both default and fallback entries. Press any key to continue... - And after a short while gets back to grub selection menu. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-43-generic 5.19.0-43.44 ProcVersionSignature: Ubuntu 5.19.0-42.43-generic 5.19.17 Uname: Linux 5.19.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexei 2618 F wireplumber /dev/snd/controlC0: alexei 2618 F wireplumber /dev/snd/seq:alexei 2616 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed May 31 20:31:01 2023 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (2701 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp8s0no wireless extensions. lxcbr0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro 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-42-generic N/A linux-backports-modules-5.19.0-42-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.6 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-01 (241 days ago) dmi.bios.date: 05/10/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.00 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.00:bd05/10/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- 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/2021997 Title: Regression. kernel 5.19.0.43.39 does not boot wirth errors: cannot allocate kernel buffer. you need to load the kernel first. Status in linux package in Ubuntu: New Bug description: Newly installed kernel linux-image-5.19.0-43-generic 5.19.0.43.39 does not boot with the following diagnostics: - error: cannot allocate kernel buffer. error: you need to load the kernel first. Press any key to continue... Failed to boot both default and fallback entries. Press any key to continue... - And after a short while gets back to grub selection menu. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-43-generic 5.19.0-43.44 ProcVersionSignature: Ubuntu 5.19.0-42.43-generic 5.19.17 Uname: Linux 5.19.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexei 2618 F wireplumber /dev/snd/controlC0: alexei 2618 F wireplumber /dev/snd/seq:alexei 2616 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed May 31 20:31:01 2023 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (2701 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp8s0no wireless extensions. lxcbr0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions:
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-bluefield/5.4.0.1065.60)
All autopkgtests for the newly accepted linux-meta-bluefield (5.4.0.1065.60) for focal have finished running. The following regressions have been reported in tests triggered by the package: acpi-call/unknown (arm64) adv-17v35x/unknown (arm64) bbswitch/unknown (arm64) ddcci-driver-linux/unknown (arm64) dm-writeboost/unknown (arm64) dpdk/unknown (arm64) fwts/unknown (arm64) glibc/unknown (arm64) gost-crypto/unknown (arm64) iptables-netflow/unknown (arm64) jool/unknown (arm64) langford/unknown (arm64) lime-forensics/unknown (arm64) linux-bluefield/unknown (arm64) lttng-modules/unknown (arm64) lxc/unknown (arm64) mali-midgard/unknown (arm64) nat-rtsp/unknown (arm64) openafs/unknown (arm64) openrazer/unknown (arm64) r8168/unknown (arm64) snapd/unknown (arm64) west-chamber/unknown (arm64) wireguard-linux-compat/unknown (arm64) xtables-addons/unknown (arm64) zfs-linux/unknown (arm64) 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/focal/update_excuses.html#linux-meta-bluefield [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 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
Updated to 5.19.0-43, still no sound. Reverting to -38 works, -40, -41, -42 and -43 all have no sound through HDMI. Also, from my end: - HDMI device is showing in GUI sound settings for both -38 and -43. - "lspci" prints the same result. - "cat /proc/asound/cards" prints the same for both -38 and -43 (no HDMI devices, but for -38 sound works) - "pacmd list-cards" prints the same thing for both -38 and -43 - Connecting to an LG TV and using 4K 120Hz if that helps (tried to lower the resolution and refresh rate, same result, -38 has sound but -43 doesn't) -- 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 Released 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 2020062] Re: No HDMI/DP audio output on dock(Nvidia GPU)
This bug is awaiting verification that the linux-oem-6.0/6.0.0-1018.18
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.
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.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-oem-6.0 verification-needed-jammy
--
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/2020062
Title:
No HDMI/DP audio output on dock(Nvidia GPU)
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-oem-6.0 source package in Jammy:
Fix Committed
Status in linux-oem-6.1 source package in Jammy:
Fix Committed
Status in linux source package in Lunar:
In Progress
Status in linux-oem-6.0 source package in Lunar:
Invalid
Status in linux-oem-6.1 source package in Lunar:
Invalid
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.0 source package in Mantic:
Invalid
Status in linux-oem-6.1 source package in Mantic:
Invalid
Bug description:
[Impact]
When the machine is docked with an external monitor, it is able to output
display, but the HDMI/DP audio output option is lost in DGFF Hybrid
Discrete/Discrete mode(Nvidia GPU).
[Fix]
Nvidia provides a patch to fix it
https://patchwork.kernel.org/project/alsa-devel/patch/20230517090736.15088-1-nmah...@nvidia.com/
[Test]
Verified on the target machine.
{Where problems could occur]
The patch just adds IDs, and won't lead to any regression.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2020062/+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 2020279] Re: Kernel warning after upgrade to 4.15.0.211.194
For me this was a bare metal bionic install on a home personal, multi- purpose, intranet server (rsyslog, apache, bind9, etc). The message was triggered 480 times in ~6 hours and 15 minutes before I downgraded. I didn't notice other issues. I looked at the logs and couldn't see a pattern of 'cut here' entries and other log entries. -- 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/2020279 Title: Kernel warning after upgrade to 4.15.0.211.194 Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Confirmed Bug description: After rebooting into 4.15.0.211.194 on Ubuntu 18.04.6 the kernel started to produce the below warning. It did not seem to cause any major issue. Revering to 4.15.0.210 stopped the warning. The server is a Droplet at DigitalOcean with their monitoring/management agent installed. May 21 19:09:59 esolr kernel: [ 18.787737] [ cut here ] May 21 19:09:59 esolr kernel: [ 18.787803] WARNING: CPU: 0 PID: 1027 at /build/linux-RlFMDZ/linux-4.15.0/net/core/stream.c:212 sk_stream_kill_queues+0xed/0x110 May 21 19:09:59 esolr kernel: [ 18.787804] Modules linked in: isofs xt_set nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter xt_conntrack nf_conntrack ip_set_hash_net ip_set nfnetlink nls_iso8859_1 kvm_intel kvm binfmt_misc irqbypass input_leds joydev serio_raw sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd psmouse virtio_blk virtio_scsi virtio_net May 21 19:09:59 esolr kernel: [ 18.787835] CPU: 0 PID: 1027 Comm: unattended-upgr Not tainted 4.15.0-211-generic #222-Ubuntu May 21 19:09:59 esolr kernel: [ 18.787836] Hardware name: DigitalOcean Droplet/Droplet, BIOS 20171212 12/12/2017 May 21 19:09:59 esolr kernel: [ 18.787839] RIP: 0010:sk_stream_kill_queues+0xed/0x110 May 21 19:09:59 esolr kernel: [ 18.787840] RSP: :94bf7fc038c0 EFLAGS: 00010282 May 21 19:09:59 esolr kernel: [ 18.787841] RAX: 0024 RBX: 94bf79565500 RCX: 0006 May 21 19:09:59 esolr kernel: [ 18.787842] RDX: RSI: 94bf7fc1b4d8 RDI: 94bf7fc1b4d0 May 21 19:09:59 esolr kernel: [ 18.787842] RBP: 94bf7fc038d0 R08: 0222 R09: 0004 May 21 19:09:59 esolr kernel: [ 18.787843] R10: 94bf7fc03860 R11: 0001 R12: 94bf795655c8 May 21 19:09:59 esolr kernel: [ 18.787844] R13: 0006 R14: 003b R15: May 21 19:09:59 esolr kernel: [ 18.787845] FS: 7f04071d4740() GS:94bf7fc0() knlGS: May 21 19:09:59 esolr kernel: [ 18.787846] CS: 0010 DS: ES: CR0: 80050033 May 21 19:09:59 esolr kernel: [ 18.787846] CR2: 7f0401995e60 CR3: 67586002 CR4: 001606f0 May 21 19:09:59 esolr kernel: [ 18.787850] DR0: DR1: DR2: May 21 19:09:59 esolr kernel: [ 18.787851] DR3: DR6: fffe0ff0 DR7: 0400 May 21 19:09:59 esolr kernel: [ 18.787851] Call Trace: May 21 19:09:59 esolr kernel: [ 18.787853] May 21 19:09:59 esolr kernel: [ 18.787866] inet_csk_destroy_sock+0x59/0x150 May 21 19:09:59 esolr kernel: [ 18.787868] tcp_done+0x96/0xa0 May 21 19:09:59 esolr kernel: [ 18.787872] tcp_time_wait+0x1be/0x280 May 21 19:09:59 esolr kernel: [ 18.787874] tcp_fin+0x16b/0x180 May 21 19:09:59 esolr kernel: [ 18.787876] tcp_data_queue+0x594/0xc20 May 21 19:09:59 esolr kernel: [ 18.787881] tcp_rcv_state_process+0x5dd/0xe70 May 21 19:09:59 esolr kernel: [ 18.787887] ? __slab_alloc+0x20/0x40 May 21 19:09:59 esolr kernel: [ 18.787889] ? kmem_cache_alloc+0x161/0x1c0 May 21 19:09:59 esolr kernel: [ 18.787891] ? skb_clone+0x56/0xc0 May 21 19:09:59 esolr kernel: [ 18.787897] tcp_v6_do_rcv+0x1ca/0x440 May 21 19:09:59 esolr kernel: [ 18.787898] ? tcp_v6_do_rcv+0x1ca/0x440 May 21 19:09:59 esolr kernel: [ 18.787899] tcp_v6_rcv+0x9b6/0xa60 May 21 19:09:59 esolr kernel: [ 18.787907] ? update_load_avg+0x5f9/0x780 May 21 19:09:59 esolr kernel: [ 18.787909] ip6_input_finish+0xcc/0x470 May 21 19:09:59 esolr kernel: [ 18.787911] ip6_input+0x3f/0xb0 May 21 19:09:59 esolr kernel: [ 18.787914] ? ip6_dst_check+0xb1/0xf0 May 21 19:09:59 esolr kernel: [ 18.787915] ip6_rcv_finish+0xd8/0x120 May 21 19:09:59 esolr kernel: [ 18.787916] ipv6_rcv+0x347/0x510 May 21 19:09:59 esolr kernel: [ 18.787917] ?
[Kernel-packages] [Bug 2021986] Re: package linux-headers-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: unable to securely remove '/usr/src/linux-headers-5.19.0-41-generic/virt': N
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2021986 Title: package linux-headers-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: unable to securely remove '/usr/src/linux- headers-5.19.0-41-generic/virt': Not a directory Status in linux-hwe-5.19 package in Ubuntu: New Bug description: Ubuntu launch the Software Updater and I installed all the updates and this error occurred ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-headers-5.19.0-41-generic 5.19.0-41.42~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed May 31 11:05:24 2023 DpkgTerminalLog: Removing linux-headers-5.19.0-41-generic (5.19.0-41.42~22.04.1) ... dpkg: error processing package linux-headers-5.19.0-41-generic (--remove): unable to securely remove '/usr/src/linux-headers-5.19.0-41-generic/virt': Not a directory dpkg: too many errors, stopping DuplicateSignature: package:linux-headers-5.19.0-41-generic:5.19.0-41.42~22.04.1 Removing linux-headers-5.19.0-41-generic (5.19.0-41.42~22.04.1) ... dpkg: error processing package linux-headers-5.19.0-41-generic (--remove): unable to securely remove '/usr/src/linux-headers-5.19.0-41-generic/virt': Not a directory ErrorMessage: unable to securely remove '/usr/src/linux-headers-5.19.0-41-generic/virt': Not a directory InstallationDate: Installed on 2023-05-11 (19 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: linux-hwe-5.19 Title: package linux-headers-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: unable to securely remove '/usr/src/linux-headers-5.19.0-41-generic/virt': Not a directory UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2021986/+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 2021986] [NEW] package linux-headers-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: unable to securely remove '/usr/src/linux-headers-5.19.0-41-generic/virt':
Public bug reported: Ubuntu launch the Software Updater and I installed all the updates and this error occurred ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-headers-5.19.0-41-generic 5.19.0-41.42~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed May 31 11:05:24 2023 DpkgTerminalLog: Removing linux-headers-5.19.0-41-generic (5.19.0-41.42~22.04.1) ... dpkg: error processing package linux-headers-5.19.0-41-generic (--remove): unable to securely remove '/usr/src/linux-headers-5.19.0-41-generic/virt': Not a directory dpkg: too many errors, stopping DuplicateSignature: package:linux-headers-5.19.0-41-generic:5.19.0-41.42~22.04.1 Removing linux-headers-5.19.0-41-generic (5.19.0-41.42~22.04.1) ... dpkg: error processing package linux-headers-5.19.0-41-generic (--remove): unable to securely remove '/usr/src/linux-headers-5.19.0-41-generic/virt': Not a directory ErrorMessage: unable to securely remove '/usr/src/linux-headers-5.19.0-41-generic/virt': Not a directory InstallationDate: Installed on 2023-05-11 (19 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: linux-hwe-5.19 Title: package linux-headers-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: unable to securely remove '/usr/src/linux-headers-5.19.0-41-generic/virt': Not a directory UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2021986 Title: package linux-headers-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: unable to securely remove '/usr/src/linux- headers-5.19.0-41-generic/virt': Not a directory Status in linux-hwe-5.19 package in Ubuntu: New Bug description: Ubuntu launch the Software Updater and I installed all the updates and this error occurred ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-headers-5.19.0-41-generic 5.19.0-41.42~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed May 31 11:05:24 2023 DpkgTerminalLog: Removing linux-headers-5.19.0-41-generic (5.19.0-41.42~22.04.1) ... dpkg: error processing package linux-headers-5.19.0-41-generic (--remove): unable to securely remove '/usr/src/linux-headers-5.19.0-41-generic/virt': Not a directory dpkg: too many errors, stopping DuplicateSignature: package:linux-headers-5.19.0-41-generic:5.19.0-41.42~22.04.1 Removing linux-headers-5.19.0-41-generic (5.19.0-41.42~22.04.1) ... dpkg: error processing package linux-headers-5.19.0-41-generic (--remove): unable to securely remove '/usr/src/linux-headers-5.19.0-41-generic/virt': Not a directory ErrorMessage: unable to securely remove '/usr/src/linux-headers-5.19.0-41-generic/virt': Not a directory InstallationDate: Installed on 2023-05-11 (19 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: linux-hwe-5.19 Title: package linux-headers-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: unable to securely remove '/usr/src/linux-headers-5.19.0-41-generic/virt': Not a directory UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2021986/+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 2020279] Re: Kernel warning after upgrade to 4.15.0.211.194
Hi Andrei, I have no idea what triggers it. The Droplet is a webserver, maybe whenever someone requested a page. The warning did not happen frequently, a few times in an hour, though this server is a test server, probably does not see much traffic. Maybe Jamie has a better idea or could give more info about the environment he saw it on. -- 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/2020279 Title: Kernel warning after upgrade to 4.15.0.211.194 Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Confirmed Bug description: After rebooting into 4.15.0.211.194 on Ubuntu 18.04.6 the kernel started to produce the below warning. It did not seem to cause any major issue. Revering to 4.15.0.210 stopped the warning. The server is a Droplet at DigitalOcean with their monitoring/management agent installed. May 21 19:09:59 esolr kernel: [ 18.787737] [ cut here ] May 21 19:09:59 esolr kernel: [ 18.787803] WARNING: CPU: 0 PID: 1027 at /build/linux-RlFMDZ/linux-4.15.0/net/core/stream.c:212 sk_stream_kill_queues+0xed/0x110 May 21 19:09:59 esolr kernel: [ 18.787804] Modules linked in: isofs xt_set nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter xt_conntrack nf_conntrack ip_set_hash_net ip_set nfnetlink nls_iso8859_1 kvm_intel kvm binfmt_misc irqbypass input_leds joydev serio_raw sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd psmouse virtio_blk virtio_scsi virtio_net May 21 19:09:59 esolr kernel: [ 18.787835] CPU: 0 PID: 1027 Comm: unattended-upgr Not tainted 4.15.0-211-generic #222-Ubuntu May 21 19:09:59 esolr kernel: [ 18.787836] Hardware name: DigitalOcean Droplet/Droplet, BIOS 20171212 12/12/2017 May 21 19:09:59 esolr kernel: [ 18.787839] RIP: 0010:sk_stream_kill_queues+0xed/0x110 May 21 19:09:59 esolr kernel: [ 18.787840] RSP: :94bf7fc038c0 EFLAGS: 00010282 May 21 19:09:59 esolr kernel: [ 18.787841] RAX: 0024 RBX: 94bf79565500 RCX: 0006 May 21 19:09:59 esolr kernel: [ 18.787842] RDX: RSI: 94bf7fc1b4d8 RDI: 94bf7fc1b4d0 May 21 19:09:59 esolr kernel: [ 18.787842] RBP: 94bf7fc038d0 R08: 0222 R09: 0004 May 21 19:09:59 esolr kernel: [ 18.787843] R10: 94bf7fc03860 R11: 0001 R12: 94bf795655c8 May 21 19:09:59 esolr kernel: [ 18.787844] R13: 0006 R14: 003b R15: May 21 19:09:59 esolr kernel: [ 18.787845] FS: 7f04071d4740() GS:94bf7fc0() knlGS: May 21 19:09:59 esolr kernel: [ 18.787846] CS: 0010 DS: ES: CR0: 80050033 May 21 19:09:59 esolr kernel: [ 18.787846] CR2: 7f0401995e60 CR3: 67586002 CR4: 001606f0 May 21 19:09:59 esolr kernel: [ 18.787850] DR0: DR1: DR2: May 21 19:09:59 esolr kernel: [ 18.787851] DR3: DR6: fffe0ff0 DR7: 0400 May 21 19:09:59 esolr kernel: [ 18.787851] Call Trace: May 21 19:09:59 esolr kernel: [ 18.787853] May 21 19:09:59 esolr kernel: [ 18.787866] inet_csk_destroy_sock+0x59/0x150 May 21 19:09:59 esolr kernel: [ 18.787868] tcp_done+0x96/0xa0 May 21 19:09:59 esolr kernel: [ 18.787872] tcp_time_wait+0x1be/0x280 May 21 19:09:59 esolr kernel: [ 18.787874] tcp_fin+0x16b/0x180 May 21 19:09:59 esolr kernel: [ 18.787876] tcp_data_queue+0x594/0xc20 May 21 19:09:59 esolr kernel: [ 18.787881] tcp_rcv_state_process+0x5dd/0xe70 May 21 19:09:59 esolr kernel: [ 18.787887] ? __slab_alloc+0x20/0x40 May 21 19:09:59 esolr kernel: [ 18.787889] ? kmem_cache_alloc+0x161/0x1c0 May 21 19:09:59 esolr kernel: [ 18.787891] ? skb_clone+0x56/0xc0 May 21 19:09:59 esolr kernel: [ 18.787897] tcp_v6_do_rcv+0x1ca/0x440 May 21 19:09:59 esolr kernel: [ 18.787898] ? tcp_v6_do_rcv+0x1ca/0x440 May 21 19:09:59 esolr kernel: [ 18.787899] tcp_v6_rcv+0x9b6/0xa60 May 21 19:09:59 esolr kernel: [ 18.787907] ? update_load_avg+0x5f9/0x780 May 21 19:09:59 esolr kernel: [ 18.787909] ip6_input_finish+0xcc/0x470 May 21 19:09:59 esolr kernel: [ 18.787911] ip6_input+0x3f/0xb0 May 21 19:09:59 esolr kernel: [ 18.787914] ? ip6_dst_check+0xb1/0xf0 May 21 19:09:59 esolr kernel: [ 18.787915] ip6_rcv_finish+0xd8/0x120 May 21 19:09:59 esolr kernel: [ 18.787916] ipv6_rcv+0x347/0x510 May 21 19:09:59 esolr kernel: [ 18.787917] ?
[Kernel-packages] [Bug 2020279] Re: Kernel warning after upgrade to 4.15.0.211.194
I see the original report is on a DigitalOcean Droplet, but I think this should also reproduce in a local VM. Is there anything specific I need to do to trigger the bug, Gabor? -- 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/2020279 Title: Kernel warning after upgrade to 4.15.0.211.194 Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Confirmed Bug description: After rebooting into 4.15.0.211.194 on Ubuntu 18.04.6 the kernel started to produce the below warning. It did not seem to cause any major issue. Revering to 4.15.0.210 stopped the warning. The server is a Droplet at DigitalOcean with their monitoring/management agent installed. May 21 19:09:59 esolr kernel: [ 18.787737] [ cut here ] May 21 19:09:59 esolr kernel: [ 18.787803] WARNING: CPU: 0 PID: 1027 at /build/linux-RlFMDZ/linux-4.15.0/net/core/stream.c:212 sk_stream_kill_queues+0xed/0x110 May 21 19:09:59 esolr kernel: [ 18.787804] Modules linked in: isofs xt_set nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter xt_conntrack nf_conntrack ip_set_hash_net ip_set nfnetlink nls_iso8859_1 kvm_intel kvm binfmt_misc irqbypass input_leds joydev serio_raw sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd psmouse virtio_blk virtio_scsi virtio_net May 21 19:09:59 esolr kernel: [ 18.787835] CPU: 0 PID: 1027 Comm: unattended-upgr Not tainted 4.15.0-211-generic #222-Ubuntu May 21 19:09:59 esolr kernel: [ 18.787836] Hardware name: DigitalOcean Droplet/Droplet, BIOS 20171212 12/12/2017 May 21 19:09:59 esolr kernel: [ 18.787839] RIP: 0010:sk_stream_kill_queues+0xed/0x110 May 21 19:09:59 esolr kernel: [ 18.787840] RSP: :94bf7fc038c0 EFLAGS: 00010282 May 21 19:09:59 esolr kernel: [ 18.787841] RAX: 0024 RBX: 94bf79565500 RCX: 0006 May 21 19:09:59 esolr kernel: [ 18.787842] RDX: RSI: 94bf7fc1b4d8 RDI: 94bf7fc1b4d0 May 21 19:09:59 esolr kernel: [ 18.787842] RBP: 94bf7fc038d0 R08: 0222 R09: 0004 May 21 19:09:59 esolr kernel: [ 18.787843] R10: 94bf7fc03860 R11: 0001 R12: 94bf795655c8 May 21 19:09:59 esolr kernel: [ 18.787844] R13: 0006 R14: 003b R15: May 21 19:09:59 esolr kernel: [ 18.787845] FS: 7f04071d4740() GS:94bf7fc0() knlGS: May 21 19:09:59 esolr kernel: [ 18.787846] CS: 0010 DS: ES: CR0: 80050033 May 21 19:09:59 esolr kernel: [ 18.787846] CR2: 7f0401995e60 CR3: 67586002 CR4: 001606f0 May 21 19:09:59 esolr kernel: [ 18.787850] DR0: DR1: DR2: May 21 19:09:59 esolr kernel: [ 18.787851] DR3: DR6: fffe0ff0 DR7: 0400 May 21 19:09:59 esolr kernel: [ 18.787851] Call Trace: May 21 19:09:59 esolr kernel: [ 18.787853] May 21 19:09:59 esolr kernel: [ 18.787866] inet_csk_destroy_sock+0x59/0x150 May 21 19:09:59 esolr kernel: [ 18.787868] tcp_done+0x96/0xa0 May 21 19:09:59 esolr kernel: [ 18.787872] tcp_time_wait+0x1be/0x280 May 21 19:09:59 esolr kernel: [ 18.787874] tcp_fin+0x16b/0x180 May 21 19:09:59 esolr kernel: [ 18.787876] tcp_data_queue+0x594/0xc20 May 21 19:09:59 esolr kernel: [ 18.787881] tcp_rcv_state_process+0x5dd/0xe70 May 21 19:09:59 esolr kernel: [ 18.787887] ? __slab_alloc+0x20/0x40 May 21 19:09:59 esolr kernel: [ 18.787889] ? kmem_cache_alloc+0x161/0x1c0 May 21 19:09:59 esolr kernel: [ 18.787891] ? skb_clone+0x56/0xc0 May 21 19:09:59 esolr kernel: [ 18.787897] tcp_v6_do_rcv+0x1ca/0x440 May 21 19:09:59 esolr kernel: [ 18.787898] ? tcp_v6_do_rcv+0x1ca/0x440 May 21 19:09:59 esolr kernel: [ 18.787899] tcp_v6_rcv+0x9b6/0xa60 May 21 19:09:59 esolr kernel: [ 18.787907] ? update_load_avg+0x5f9/0x780 May 21 19:09:59 esolr kernel: [ 18.787909] ip6_input_finish+0xcc/0x470 May 21 19:09:59 esolr kernel: [ 18.787911] ip6_input+0x3f/0xb0 May 21 19:09:59 esolr kernel: [ 18.787914] ? ip6_dst_check+0xb1/0xf0 May 21 19:09:59 esolr kernel: [ 18.787915] ip6_rcv_finish+0xd8/0x120 May 21 19:09:59 esolr kernel: [ 18.787916] ipv6_rcv+0x347/0x510 May 21 19:09:59 esolr kernel: [ 18.787917] ? __pskb_pull_tail+0x7f/0x4b0 May 21 19:09:59 esolr kernel: [ 18.787918] ? skb_copy_bits+0x141/0x280 May 21 19:09:59 esolr kernel: [ 18.787920] ?
[Kernel-packages] [Bug 2020279] Re: Kernel warning after upgrade to 4.15.0.211.194
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- 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/2020279 Title: Kernel warning after upgrade to 4.15.0.211.194 Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Confirmed Bug description: After rebooting into 4.15.0.211.194 on Ubuntu 18.04.6 the kernel started to produce the below warning. It did not seem to cause any major issue. Revering to 4.15.0.210 stopped the warning. The server is a Droplet at DigitalOcean with their monitoring/management agent installed. May 21 19:09:59 esolr kernel: [ 18.787737] [ cut here ] May 21 19:09:59 esolr kernel: [ 18.787803] WARNING: CPU: 0 PID: 1027 at /build/linux-RlFMDZ/linux-4.15.0/net/core/stream.c:212 sk_stream_kill_queues+0xed/0x110 May 21 19:09:59 esolr kernel: [ 18.787804] Modules linked in: isofs xt_set nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter xt_conntrack nf_conntrack ip_set_hash_net ip_set nfnetlink nls_iso8859_1 kvm_intel kvm binfmt_misc irqbypass input_leds joydev serio_raw sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd psmouse virtio_blk virtio_scsi virtio_net May 21 19:09:59 esolr kernel: [ 18.787835] CPU: 0 PID: 1027 Comm: unattended-upgr Not tainted 4.15.0-211-generic #222-Ubuntu May 21 19:09:59 esolr kernel: [ 18.787836] Hardware name: DigitalOcean Droplet/Droplet, BIOS 20171212 12/12/2017 May 21 19:09:59 esolr kernel: [ 18.787839] RIP: 0010:sk_stream_kill_queues+0xed/0x110 May 21 19:09:59 esolr kernel: [ 18.787840] RSP: :94bf7fc038c0 EFLAGS: 00010282 May 21 19:09:59 esolr kernel: [ 18.787841] RAX: 0024 RBX: 94bf79565500 RCX: 0006 May 21 19:09:59 esolr kernel: [ 18.787842] RDX: RSI: 94bf7fc1b4d8 RDI: 94bf7fc1b4d0 May 21 19:09:59 esolr kernel: [ 18.787842] RBP: 94bf7fc038d0 R08: 0222 R09: 0004 May 21 19:09:59 esolr kernel: [ 18.787843] R10: 94bf7fc03860 R11: 0001 R12: 94bf795655c8 May 21 19:09:59 esolr kernel: [ 18.787844] R13: 0006 R14: 003b R15: May 21 19:09:59 esolr kernel: [ 18.787845] FS: 7f04071d4740() GS:94bf7fc0() knlGS: May 21 19:09:59 esolr kernel: [ 18.787846] CS: 0010 DS: ES: CR0: 80050033 May 21 19:09:59 esolr kernel: [ 18.787846] CR2: 7f0401995e60 CR3: 67586002 CR4: 001606f0 May 21 19:09:59 esolr kernel: [ 18.787850] DR0: DR1: DR2: May 21 19:09:59 esolr kernel: [ 18.787851] DR3: DR6: fffe0ff0 DR7: 0400 May 21 19:09:59 esolr kernel: [ 18.787851] Call Trace: May 21 19:09:59 esolr kernel: [ 18.787853] May 21 19:09:59 esolr kernel: [ 18.787866] inet_csk_destroy_sock+0x59/0x150 May 21 19:09:59 esolr kernel: [ 18.787868] tcp_done+0x96/0xa0 May 21 19:09:59 esolr kernel: [ 18.787872] tcp_time_wait+0x1be/0x280 May 21 19:09:59 esolr kernel: [ 18.787874] tcp_fin+0x16b/0x180 May 21 19:09:59 esolr kernel: [ 18.787876] tcp_data_queue+0x594/0xc20 May 21 19:09:59 esolr kernel: [ 18.787881] tcp_rcv_state_process+0x5dd/0xe70 May 21 19:09:59 esolr kernel: [ 18.787887] ? __slab_alloc+0x20/0x40 May 21 19:09:59 esolr kernel: [ 18.787889] ? kmem_cache_alloc+0x161/0x1c0 May 21 19:09:59 esolr kernel: [ 18.787891] ? skb_clone+0x56/0xc0 May 21 19:09:59 esolr kernel: [ 18.787897] tcp_v6_do_rcv+0x1ca/0x440 May 21 19:09:59 esolr kernel: [ 18.787898] ? tcp_v6_do_rcv+0x1ca/0x440 May 21 19:09:59 esolr kernel: [ 18.787899] tcp_v6_rcv+0x9b6/0xa60 May 21 19:09:59 esolr kernel: [ 18.787907] ? update_load_avg+0x5f9/0x780 May 21 19:09:59 esolr kernel: [ 18.787909] ip6_input_finish+0xcc/0x470 May 21 19:09:59 esolr kernel: [ 18.787911] ip6_input+0x3f/0xb0 May 21 19:09:59 esolr kernel: [ 18.787914] ? ip6_dst_check+0xb1/0xf0 May 21 19:09:59 esolr kernel: [ 18.787915] ip6_rcv_finish+0xd8/0x120 May 21 19:09:59 esolr kernel: [ 18.787916] ipv6_rcv+0x347/0x510 May 21 19:09:59 esolr kernel: [ 18.787917] ? __pskb_pull_tail+0x7f/0x4b0 May 21 19:09:59 esolr kernel: [ 18.787918] ? skb_copy_bits+0x141/0x280 May 21 19:09:59 esolr kernel:
[Kernel-packages] [Bug 2021605] Re: introduce do_lib_rust=true|false to enable/disable linux-lib-rust package
** Changed in: linux-aws (Ubuntu Lunar) Status: New => Fix Committed -- 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/2021605 Title: introduce do_lib_rust=true|false to enable/disable linux-lib-rust package Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux source package in Lunar: Incomplete Status in linux-aws source package in Lunar: Fix Committed Status in linux source package in Mantic: Incomplete Status in linux-aws source package in Mantic: New Bug description: [Impact] Provide a variable do_lib_rust=true|false in the kernel build system to selectively enable the Rust packaging (linux-lib-rust) with specific kernels and specific architectures. Right now Rust should be enabled only in lunar and mantic and only on amd64. [Test case] Build the kernel producing all the debs. [Fix] Introduce a do_lib_rust=true variable that will be defined only in debian.master/rules.d/amd64.mk for now. [Regression potential] Kernels may need to set this variables if they want to enable the Rust support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021605/+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 1997505] Re: Unattended-Upgrade will upgrade 1020-oem kernel without nvidia-driver
I did a test on focal platforms, I found this issue was not fixed yet.
By default user used oem kernel which is set by oem-meta packages, it
will be ok, but if the user select the generic kernel, then it will meet
black screen issue cause of missing nvidia driver.
Start-Date: 2023-05-31 06:04:11
Commandline: /usr/bin/unattended-upgrade -v
Requested-By: u (1001)
Install: linux-hwe-5.15-headers-5.15.0-73:amd64 (5.15.0-73.80~20.04.1,
automatic), linux-headers-generic-hwe-20.04:amd64 (5.15.0.73.80~20.04.34,
automatic), linux-modules-extra-5.15.0-73-generic:amd64 (5.15.0-73.80~20.04.1,
automatic), linux-image-generic-hwe-20.04:amd64 (5.15.0.73.80~20.04.34,
automatic), linux-generic-hwe-20.04:amd64 (5.15.0.73.80~20.04.34, automatic),
linux-modules-5.15.0-73-generic:amd64 (5.15.0-73.80~20.04.1, automatic),
linux-headers-5.15.0-73-generic:amd64 (5.15.0-73.80~20.04.1, automatic),
linux-image-5.15.0-73-generic:amd64 (5.15.0-73.80~20.04.1, automatic)
Upgrade: linux-image-oem-20.04d:amd64 (5.14.0.1032.29, 5.15.0.73.80~20.04.34),
linux-oem-20.04d:amd64 (5.14.0.1032.29, 5.15.0.73.80~20.04.34)
End-Date: 2023-05-31 06:04:45
Start-Date: 2023-05-31 06:18:38
Commandline: /usr/bin/unattended-upgrade -v
Requested-By: u (1001)
Remove: linux-image-oem-20.04d:amd64 (5.15.0.73.80~20.04.34)
End-Date: 2023-05-31 06:18:38
Start-Date: 2023-05-31 06:18:42
Commandline: /usr/bin/unattended-upgrade -v
Requested-By: u (1001)
Remove: linux-headers-oem-20.04d:amd64 (5.15.0.73.80~20.04.34)
End-Date: 2023-05-31 06:18:42
Removing linux-headers-oem-20.04d (5.15.0.73.80~20.04.34) ...
Packages that were successfully auto-removed: linux-headers-oem-20.04d
linux-image-oem-20.04d
Packages that are kept back:
Package libnvidia-cfg1-510 is kept back because a related package is kept back
or due to local apt_preferences(5).
Package libnvidia-compute-510 is kept back because a related package is kept
back or due to local apt_preferences(5).
Package libnvidia-decode-510 is kept back because a related package is kept
back or due to local apt_preferences(5).
Package libnvidia-encode-510 is kept back because a related package is kept
back or due to local apt_preferences(5).
Package libnvidia-extra-510 is kept back because a related package is kept back
or due to local apt_preferences(5).
Package libnvidia-fbc1-510 is kept back because a related package is kept back
or due to local apt_preferences(5).
Package libnvidia-gl-510 is kept back because a related package is kept back or
due to local apt_preferences(5).
Package linux-modules-nvidia-510-oem-20.04d is kept back because a related
package is kept back or due to local apt_preferences(5).
Package nvidia-compute-utils-510 is kept back because a related package is kept
back or due to local apt_preferences(5).
Package nvidia-driver-510 is kept back because a related package is kept back
or due to local apt_preferences(5).
Package nvidia-kernel-common-510 is kept back because a related package is kept
back or due to local apt_preferences(5).
Package nvidia-kernel-source-510 is kept back because a related package is kept
back or due to local apt_preferences(5).
Package nvidia-utils-510 is kept back because a related package is kept back or
due to local apt_preferences(5).
Package xserver-xorg-video-nvidia-510 is kept back because a related package is
kept back or due to local apt_preferences(5).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1997505
Title:
Unattended-Upgrade will upgrade 1020-oem kernel without nvidia-driver
Status in OEM Priority Project:
Confirmed
Status in linux-meta-oem-5.14 package in Ubuntu:
New
Status in linux-meta-oem-5.17 package in Ubuntu:
Fix Released
Bug description:
If the GMed image used earlier kernel than 5.17.0-1020-oem, then you
would like meet this issue.
1020-oem is in security channel. In jammy the unattende-upgrade will
install security fixes by default.
For the I+N platforms, the nvidia driver couldn't be installed for
1020-oem kernel, then user will meet a black screen cause of nvidia
modules couldn't be loaded.
Unattended-Upgrade::Allowed-Origins {
"${distro_id}:${distro_codename}";
"${distro_id}:${distro_codename}-security";
// Extended Security Maintenance; doesn't necessarily exist for
// every release and this system may not have it installed, but if
// available, the policy for updates is such that unattended-upgrades
// should also install from here by default.
"${distro_id}ESMApps:${distro_codename}-apps-security";
"${distro_id}ESM:${distro_codename}-infra-security";
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1997505/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe
[Kernel-packages] [Bug 2021962] [NEW] F/xilinx and J/xilinx uses different keyword in /proc/device-tree/compatible
Public bug reported: While testing J/xilinx, I noticed that the keyword we use to grep from /proc/device-tree/compatible has to be changed into kv26 instead of k26 that we used for F/xilinx J/xilinx: $ cat /proc/device-tree/compatible xlnx,zynqmp-sk-kv260-rev1xlnx,zynqmp-sk-kv260-revBxlnx,zynqmp-sk-kv260xlnx,zynqmp F/xilinx: $ cat /proc/device-tree/compatible xlnx,zynqmp-smk-k26-rev1xlnx,zynqmp-smk-k26-revBxlnx,zynqmp-smk-k26-revAxlnx,zynqmp-smk-k26xlnx,zynqmp >From what I can found on the Internet, KV260 is "a vision application development platform for Kria K26 SOMs (system-on-module)". But it's better to let the kernel maintainer (Portia) to answer that if this difference is expected. Related change for tests: https://code.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests/+merge/443543 ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-xilinx-zynqmp (Ubuntu) Importance: Undecided Assignee: Portia Stephens (portias) Status: New ** Tags: 5.15 5.4 focal jammy xilinx ** Also affects: linux-xilinx-zynqmp (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-xilinx-zynqmp (Ubuntu) Assignee: (unassigned) => Portia Stephens (portias) ** Tags added: 5.15 5.4 focal jammy xilinx -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2021962 Title: F/xilinx and J/xilinx uses different keyword in /proc/device- tree/compatible Status in ubuntu-kernel-tests: New Status in linux-xilinx-zynqmp package in Ubuntu: New Bug description: While testing J/xilinx, I noticed that the keyword we use to grep from /proc/device-tree/compatible has to be changed into kv26 instead of k26 that we used for F/xilinx J/xilinx: $ cat /proc/device-tree/compatible xlnx,zynqmp-sk-kv260-rev1xlnx,zynqmp-sk-kv260-revBxlnx,zynqmp-sk-kv260xlnx,zynqmp F/xilinx: $ cat /proc/device-tree/compatible xlnx,zynqmp-smk-k26-rev1xlnx,zynqmp-smk-k26-revBxlnx,zynqmp-smk-k26-revAxlnx,zynqmp-smk-k26xlnx,zynqmp From what I can found on the Internet, KV260 is "a vision application development platform for Kria K26 SOMs (system-on-module)". But it's better to let the kernel maintainer (Portia) to answer that if this difference is expected. Related change for tests: https://code.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests/+merge/443543 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2021962/+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 1998194] Re: Please add support for Qualcomm IPC Router in 5.4 focal kernel
** Also affects: linux-intel-iotg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998194 Title: Please add support for Qualcomm IPC Router in 5.4 focal kernel Status in linux package in Ubuntu: Confirmed Status in linux-intel-iotg package in Ubuntu: New Bug description: The modemmanager debian package in focal was recently upgraded to 1.18 (the jammy version was backported - see LP: #1965901). This version has broken some Qualcomm modems as it start to require the Qualcomm IPC Router for them, which drivers are not enabled in Ubuntu kernel 5.4. To fix this we need these options enabled in the focal kernel: CONFIG_QRTR=m CONFIG_QRTR_SMD=m CONFIG_QRTR_TUN=m CONFIG_QRTR_MHI=m The options are already enabled in more modern Ubuntu kernel, i.e. 5.17. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998194/+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 2006102] Re: Mic Mute LED doesn't work on Soundwire laptops
** Changed in: oem-priority Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2006102 Title: Mic Mute LED doesn't work on Soundwire laptops Status in OEM Priority Project: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: Fix Released Status in alsa-ucm-conf source package in Kinetic: Fix Released Status in alsa-ucm-conf source package in Lunar: Fix Released Bug description: Pull request: https://github.com/alsa-project/alsa-ucm-conf/pull/261 [Impact] Mic mute LED doesn't work on Intel-based Dell laptops. [Fix] Due to recent change on how kernel creates sound LEDs, there are two captures are registered, one from SoF and one from HDA. The SoF one is the "real" capture system uses. Since physical LED only gets light up when _all_ captures are muted, detach the HDA one so micmute LED only need to consider SoF capture's mute status. [Test] The mic mute LED works again on Soundwire laptops. The legacy HDA/DMIC systems are unaffected. [Where problems could occur] Theoretically the system may have more than two internal captures registered, then disabling one will not be enough. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2006102/+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 2021949] [NEW] Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle
Public bug reported: [Impact] [Fix] [Test Cases] [Where problems could occur] ** Affects: linux (Ubuntu) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-6.0 (Ubuntu Kinetic) Importance: Undecided Status: New ** Affects: linux-oem-6.1 (Ubuntu Kinetic) Importance: Undecided Status: New ** Affects: linux (Ubuntu Lunar) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-6.0 (Ubuntu Lunar) Importance: Undecided Status: New ** Affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: New ** Affects: linux (Ubuntu Mantic) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-6.0 (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: linux-oem-6.1 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => koba (kobako) ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) -- 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/2021949 Title: Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: New Status in linux-oem-6.1 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-6.0 source package in Kinetic: New Status in linux-oem-6.1 source package in Kinetic: New Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: New Status in linux-oem-6.1 source package in Lunar: New Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: New Status in linux-oem-6.1 source package in Mantic: New Bug description: [Impact] [Fix] [Test Cases] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021949/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 2012755] Re: [IOTG][RPL] Enable Time Coordinated Compute interface driver
This bug was fixed in the package linux-intel-iotg - 5.15.0-1030.35 --- linux-intel-iotg (5.15.0-1030.35) jammy; urgency=medium * jammy/linux-intel-iotg: 5.15.0-1030.35 -proposed tracker (LP: #2019028) * net:veth.sh in ubuntu_kernel_selftests hang with J-intel-iotg (BUG: unable to handle page fault) (LP: #2008085) - Revert "rtnetlink: Add return value check" - Revert "rtnetlink: Fix unchecked return value of dev_xdp_query_md_btf()" - Revert "igc: Enable HW RX Timestamp for AF_XDP ZC" - Revert "igc: Add BTF based metadata for XDP" - Revert "net/core: XDP metadata BTF netlink API" linux-intel-iotg (5.15.0-1029.34) jammy; urgency=medium * jammy/linux-intel-iotg: 5.15.0-1029.34 -proposed tracker (LP: #2016534) * CVE-2023-1829 - [Config]: Make sure CONFIG_NET_CLS_TCINDEX is not available * [IOTG][RPL] Enable Time Coordinated Compute interface driver (LP: #2012755) - tcc: driver should exit if no psram entry found in PTCT. - tcc: tcc drvier should not exit even if no psram entry. - Add new IOCTL to read error log buffer. - Display errlog buffer raw data in kernel log as requested once this driver is loaded. - Fix issue found in acrn uos when convert cacheid to apicid. - tcc: rounding possible non page-aligned ssram address - Support RPL in measurement function. - Assume default hardware prefetch bitmask in measurement function. - tcc: fix patch style problem - tcc: Map and show crl version number in /proc. - tcc: Update hardware prefetcher disable bits for ADL and RPL in cache hit/miss measurement. - tcc: Choose different L3 cache miss perf event for ADL-N. * [IoTG] Integrated TSN controller (stmmac) driver commits tracker (LP: #2017934) - fixup! net: phy: marvell10g: Add WAKE_PHY support to WOL event - taprio: Add bitmask checking based on the traffic class - net: stmmac: Add check for supported EEE advertisement - net: stmmac: update EEE status when mac link goes down - net: stmmac: Check and exit when coalesce rx-usecs is equal to 0 - net: phy: add wrapper function for setup master slave setup - net: phy: dp83867: add TI PHY loopback - net: stmmac: add check for supported mode before speed/advertising change - net: stmmac: Adjust mac_capabilities for Intel mGbE 2.5G mode - net: stmmac: check CBS input values before configuration - stmmac: intel: Separate ADL-N device ID from TGL - net: stmmac: Add check for taprio basetime configuration - net: stmmac: fix deadlock caused by taking RTNL in RPM resume path - net: phy: dp83867: perform phy reset after modifying auto-neg setting - Revert "net: stmmac: trigger PCS EEE to turn off on link down" - net: stmmac: add check for advertising linkmode request for set-eee - taprio: Add boundary check for sched-entry values - taprio: Fix no error return when entering invalid gatemask value - stmmac: intel: PCH MSI arbitration WA for HW bug - igc: Add BTF based metadata for XDP - net: stmmac: Fix 'no previous prototype' build warning - igc: Enable HW RX Timestamp for AF_XDP ZC - net/core: XDP metadata BTF netlink API - rtnetlink: Fix unchecked return value of dev_xdp_query_md_btf() - rtnetlink: Add return value check - Revert "igc: Add support for enabling frame preemption via ethtool" - Revert "igc: Add support for Frame Preemption verification" - Revert "ethtool: Add support for configuring frame preemption" - Revert "ethtool: Add support for configuring and verifying frame preemption" - Revert "ethtool: Add support for configuring frame preemption via ioctl" - Revert "net: tc: Add index of FPE QMASK" - ptp: Fixed read issue on PHC with zero n_pins - net: phy: dp83867: perform restart AN after modifying AN setting - ethtool: Add support for configuring frame preemption - ethtool: Add support for Frame Preemption verification - igc: Add support for enabling frame preemption via ethtool - igc: Add support for Frame Preemption verification [ Ubuntu: 5.15.0-72.79 ] * jammy/linux: 5.15.0-72.79 -proposed tracker (LP: #2016548) * Add split lock detection for EMR (LP: #2015855) - x86/split_lock: Enumerate architectural split lock disable bit * selftest: fib_tests: Always cleanup before exit (LP: #2015956) - selftest: fib_tests: Always cleanup before exit * Add support for intel EMR cpu (LP: #2015372) - platform/x86: intel-uncore-freq: add Emerald Rapids support - perf/x86/intel/cstate: Add Emerald Rapids - perf/x86/rapl: Add support for Intel Emerald Rapids - intel_idle: add Emerald Rapids Xeon support - tools/power/x86/intel-speed-select: Add Emerald Rapid quirk - tools/power turbostat: Introduce support for EMR - powercap: intel_rapl: add support for Emerald Rapids - EDAC/i10nm: Add Intel Emerald Rapids server support * Kernel livepatch ftrace graph fix
[Kernel-packages] [Bug 2017934] Re: [IoTG] Integrated TSN controller (stmmac) driver commits tracker
This bug was fixed in the package linux-intel-iotg - 5.15.0-1030.35 --- linux-intel-iotg (5.15.0-1030.35) jammy; urgency=medium * jammy/linux-intel-iotg: 5.15.0-1030.35 -proposed tracker (LP: #2019028) * net:veth.sh in ubuntu_kernel_selftests hang with J-intel-iotg (BUG: unable to handle page fault) (LP: #2008085) - Revert "rtnetlink: Add return value check" - Revert "rtnetlink: Fix unchecked return value of dev_xdp_query_md_btf()" - Revert "igc: Enable HW RX Timestamp for AF_XDP ZC" - Revert "igc: Add BTF based metadata for XDP" - Revert "net/core: XDP metadata BTF netlink API" linux-intel-iotg (5.15.0-1029.34) jammy; urgency=medium * jammy/linux-intel-iotg: 5.15.0-1029.34 -proposed tracker (LP: #2016534) * CVE-2023-1829 - [Config]: Make sure CONFIG_NET_CLS_TCINDEX is not available * [IOTG][RPL] Enable Time Coordinated Compute interface driver (LP: #2012755) - tcc: driver should exit if no psram entry found in PTCT. - tcc: tcc drvier should not exit even if no psram entry. - Add new IOCTL to read error log buffer. - Display errlog buffer raw data in kernel log as requested once this driver is loaded. - Fix issue found in acrn uos when convert cacheid to apicid. - tcc: rounding possible non page-aligned ssram address - Support RPL in measurement function. - Assume default hardware prefetch bitmask in measurement function. - tcc: fix patch style problem - tcc: Map and show crl version number in /proc. - tcc: Update hardware prefetcher disable bits for ADL and RPL in cache hit/miss measurement. - tcc: Choose different L3 cache miss perf event for ADL-N. * [IoTG] Integrated TSN controller (stmmac) driver commits tracker (LP: #2017934) - fixup! net: phy: marvell10g: Add WAKE_PHY support to WOL event - taprio: Add bitmask checking based on the traffic class - net: stmmac: Add check for supported EEE advertisement - net: stmmac: update EEE status when mac link goes down - net: stmmac: Check and exit when coalesce rx-usecs is equal to 0 - net: phy: add wrapper function for setup master slave setup - net: phy: dp83867: add TI PHY loopback - net: stmmac: add check for supported mode before speed/advertising change - net: stmmac: Adjust mac_capabilities for Intel mGbE 2.5G mode - net: stmmac: check CBS input values before configuration - stmmac: intel: Separate ADL-N device ID from TGL - net: stmmac: Add check for taprio basetime configuration - net: stmmac: fix deadlock caused by taking RTNL in RPM resume path - net: phy: dp83867: perform phy reset after modifying auto-neg setting - Revert "net: stmmac: trigger PCS EEE to turn off on link down" - net: stmmac: add check for advertising linkmode request for set-eee - taprio: Add boundary check for sched-entry values - taprio: Fix no error return when entering invalid gatemask value - stmmac: intel: PCH MSI arbitration WA for HW bug - igc: Add BTF based metadata for XDP - net: stmmac: Fix 'no previous prototype' build warning - igc: Enable HW RX Timestamp for AF_XDP ZC - net/core: XDP metadata BTF netlink API - rtnetlink: Fix unchecked return value of dev_xdp_query_md_btf() - rtnetlink: Add return value check - Revert "igc: Add support for enabling frame preemption via ethtool" - Revert "igc: Add support for Frame Preemption verification" - Revert "ethtool: Add support for configuring frame preemption" - Revert "ethtool: Add support for configuring and verifying frame preemption" - Revert "ethtool: Add support for configuring frame preemption via ioctl" - Revert "net: tc: Add index of FPE QMASK" - ptp: Fixed read issue on PHC with zero n_pins - net: phy: dp83867: perform restart AN after modifying AN setting - ethtool: Add support for configuring frame preemption - ethtool: Add support for Frame Preemption verification - igc: Add support for enabling frame preemption via ethtool - igc: Add support for Frame Preemption verification [ Ubuntu: 5.15.0-72.79 ] * jammy/linux: 5.15.0-72.79 -proposed tracker (LP: #2016548) * Add split lock detection for EMR (LP: #2015855) - x86/split_lock: Enumerate architectural split lock disable bit * selftest: fib_tests: Always cleanup before exit (LP: #2015956) - selftest: fib_tests: Always cleanup before exit * Add support for intel EMR cpu (LP: #2015372) - platform/x86: intel-uncore-freq: add Emerald Rapids support - perf/x86/intel/cstate: Add Emerald Rapids - perf/x86/rapl: Add support for Intel Emerald Rapids - intel_idle: add Emerald Rapids Xeon support - tools/power/x86/intel-speed-select: Add Emerald Rapid quirk - tools/power turbostat: Introduce support for EMR - powercap: intel_rapl: add support for Emerald Rapids - EDAC/i10nm: Add Intel Emerald Rapids server support * Kernel livepatch ftrace graph fix
[Kernel-packages] [Bug 2016829] Re: Completely support vxlan and erspan for flower
This bug was fixed in the package linux-bluefield - 5.4.0-1064.70 --- linux-bluefield (5.4.0-1064.70) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1064.70 -proposed tracker (LP: #2019657) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts [ Ubuntu: 5.4.0-150.167 ] * focal/linux: 5.4.0-150.167 -proposed tracker (LP: #2019682) * CVE-2023-32233 - netfilter: nf_tables: deactivate anonymous set from preparation phase * CVE-2023-2612 - SAUCE: shiftfs: prevent lock unbalance in shiftfs_create_object() * CVE-2023-31436 - net: sched: sch_qfq: prevent slab-out-of-bounds in qfq_activate_agg * CVE-2023-1380 - wifi: brcmfmac: slab-out-of-bounds read in brcmf_get_assoc_ies() * CVE-2023-30456 - KVM: nVMX: add missing consistency checks for CR0 and CR4 * Packaging resync (LP: #1786013) - [Packaging] update helper scripts -- Bartlomiej Zolnierkiewicz Fri, 19 May 2023 16:35:04 +0200 ** Changed in: linux-bluefield (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-1380 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-2612 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-30456 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-31436 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-32233 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2016829 Title: Completely support vxlan and erspan for flower Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Released Bug description: * Explain the bug(s) vxlan and erspan are already supported for flower to allow flower to match vxlan and erspan options. It needs to support vxlan and erspan to act_tunnel_key and related bug fixes for the sake of completeness and to avoid bug in the future. * Brief explanation of fixes Cherry-pick. No adaptation. Add vxlan/erspan support for act_tunnel_key and bug fixes. c96adff95619 cls_flower: call nla_ok() before nla_next() 8e1b3ac47866 net: sched: initialize with 0 before setting erspan md->u e20d4ff2acd7 net: sched: add erspan option support to act_tunnel_key fca3f91cc38a net: sched: add vxlan option support to act_tunnel_key * How to test For vxlan support: It is to allow setting vxlan options using the act_tunnel_key action. Different from geneve options, only one option can be set. And also, geneve options and vxlan options can't be set at the same time. gbp is the only param for vxlan options: # ip link add name vxlan0 type vxlan dstport 0 external # tc qdisc add dev eth0 ingress # tc filter add dev eth0 protocol ip parent : \ flower indev eth0 \ ip_proto udp \ action tunnel_key \ set src_ip 10.0.99.192 \ dst_ip 10.0.99.193 \ dst_port 6081 \ id 11 \ vxlan_opts 01020304 \ action mirred egress redirect dev vxlan0 For erspan support: It is to allow setting erspan options using the act_tunnel_key action. Different from geneve options, only one option can be set. And also, geneve options, vxlan options or erspan options can't be set at the same time. Options are expressed as ver:index:dir:hwid, when ver is set to 1, index will be applied while dir and hwid will be ignored, and when ver is set to 2, dir and hwid will be used while index will be ignored. # ip link add name erspan1 type erspan external # tc qdisc add dev eth0 ingress # tc filter add dev eth0 protocol ip parent : \ flower indev eth0 \ ip_proto udp \ action tunnel_key \ set src_ip 10.0.99.192 \ dst_ip 10.0.99.193 \ dst_port 6081 \ id 11 \ erspan_opts 1:2:0:0 \ action mirred egress redirect dev erspan1 * What it could break. Nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2016829/+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 2021945] [NEW] Jammy update: v6.1.31 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.31 upstream stable release from git://git.kernel.org/ Linux 6.1.31 net: phy: mscc: add VSC8502 to MODULE_DEVICE_TABLE 3c589_cs: Fix an error handling path in tc589_probe() net/smc: Reset connection when trying to use SMCRv2 fails. regulator: mt6359: add read check for PMIC MT6359 firmware: arm_ffa: Set reserved/MBZ fields to zero in the memory descriptors arm64: dts: imx8mn-var-som: fix PHY detection bug by adding deassert delay net/mlx5: Devcom, serialize devcom registration net/mlx5: Devcom, fix error flow in mlx5_devcom_register_device net/mlx5: Collect command failures data only for known commands net/mlx5: Fix error message when failing to allocate device memory net/mlx5: DR, Check force-loopback RC QP capability independently from RoCE net/mlx5: Handle pairing of E-switch via uplink un/load APIs net/mlx5: DR, Fix crc32 calculation to work on big-endian (BE) CPUs net/mlx5e: do as little as possible in napi poll when budget is 0 net/mlx5e: Use correct encap attribute during invalidation net/mlx5e: Fix deadlock in tc route query code net/mlx5e: Fix SQ wake logic in ptp napi_poll context platform/mellanox: mlxbf-pmc: fix sscanf() error checking forcedeth: Fix an error handling path in nv_probe() sctp: fix an issue that plpmtu can never go to complete state cxl: Wait Memory_Info_Valid before access memory related info ASoC: Intel: avs: Access path components under lock ASoC: Intel: avs: Fix declaration of enum avs_channel_config ASoC: Intel: Skylake: Fix declaration of enum skl_ch_cfg x86/show_trace_log_lvl: Ensure stack pointer is aligned, again xen/pvcalls-back: fix double frees with pvcalls_new_active_socket() x86/pci/xen: populate MSI sysfs entries ARM: dts: imx6qdl-mba6: Add missing pvcie-supply regulator coresight: Fix signedness bug in tmc_etr_buf_insert_barrier_packet() platform/x86: ISST: Remove 8 socket limit regulator: pca9450: Fix BUCK2 enable_mask fs: fix undefined behavior in bit shift for SB_NOUSER firmware: arm_ffa: Fix FFA device names for logical partitions firmware: arm_ffa: Check if ffa_driver remove is present before executing optee: fix uninited async notif value power: supply: sbs-charger: Fix INHIBITED bit for Status reg power: supply: bq24190: Call power_supply_changed() after updating input current power: supply: bq25890: Call power_supply_changed() after updating input current or voltage power: supply: bq27xxx: After charger plug in/out wait 0.5s for things to stabilize power: supply: bq27xxx: Ensure power_supply_changed() is called on current sign changes power: supply: bq27xxx: Move bq27xxx_battery_update() down power: supply: bq27xxx: Add cache parameter to bq27xxx_battery_current_and_status() power: supply: bq27xxx: Fix poll_interval handling and races on remove power: supply: bq27xxx: Fix I2C IRQ race on remove power: supply: bq27xxx: Fix bq27xxx_battery_update() race condition power: supply: mt6360: add a check of devm_work_autocancel in mt6360_charger_probe power: supply: leds: Fix blink to LED on transition cifs: mapchars mount option ignored ipv6: Fix out-of-bounds access in ipv6_find_tlv() lan966x: Fix unloading/loading of the driver bpf: fix a memory leak in the LRU and LRU_PERCPU hash maps bpf: Fix mask generation for 32-bit narrow loads of 64-bit fields octeontx2-pf: Fix TSOv6 offload selftests: fib_tests: mute cleanup error message drm: fix drmm_mutex_init() net: fix skb leak in __skb_tstamp_tx() ASoC: lpass: Fix for KASAN use_after_free out of bounds media: radio-shark: Add endpoint checks USB: sisusbvga: Add endpoint checks USB: core: Add routines for endpoint checks in old drivers udplite: Fix NULL pointer dereference in __sk_mem_raise_allocated(). net: fix stack overflow when LRO is disabled for virtual interfaces fbdev: udlfb: Fix endpoint check debugobjects: Don't wake up kswapd from fill_pool() irqchip/mips-gic: Use raw spinlock for gic_lock irqchip/mips-gic: Don't touch vl_map if a local interrupt is not routable x86/topology: Fix erroneous smp_num_siblings on Intel Hybrid platforms perf/x86/uncore: Correct the number of CHAs on SPR drm/amd/amdgpu: limit one queue per gang selftests/memfd: Fix unknown type name build failure binder: fix UAF of alloc->vma in race with munmap() binder: fix UAF caused by faulty buffer cleanup binder: add lockless binder_alloc_(set|get)_vma() Revert "android: binder: stop saving a pointer to the VMA" Revert "binder_alloc: add missing mmap_lock calls when using the VMA" drm/amd/pm: Fix output of pp_od_clk_voltage drm/amd/pm:
[Kernel-packages] [Bug 1939127] Re: ubuntu_kernel_selftests:powerpc:subpage_prot_anon: Failed with 3072 errors on Bionic 4.15 P9
Since it's end of May 2023, bionic reached it's end of base support. So can this bug be closed now as 'Won't Fix' or does it need to stay open (for ESM/Pro matters)? -- 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/1939127 Title: ubuntu_kernel_selftests:powerpc:subpage_prot_anon: Failed with 3072 errors on Bionic 4.15 P9 Status in ubuntu-kernel-tests: New Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: On host baltar with bionic:linux 4.15 for 2021.07.19 (but already same in prev cycle): ... [stdout] Failed at 0x72353a232000 (p=1023,sp=2,w=0), want=fault, got=pass ! [stdout] Failed at 0x72353a232000 (p=1023,sp=2,w=1), want=fault, got=pass ! [stdout] 3072 errors detected [stdout] failure: subpage_prot_anon [stdout] not ok 1..2 selftests: subpage_prot [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1939127/+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 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei (Oops: Exception in kernel mode, sig: 4 [#1])
** Tags removed: bugnameltc-194783 severity-medium ** Tags added: bugnameltc-192677 severity-high -- 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/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei (Oops: Exception in kernel mode, sig: 4 [#1]) Status in ubuntu-kernel-tests: New Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Status in linux source package in Hirsute: Won't Fix Status in linux source package in Impish: Won't Fix Bug description: It looks like our P8 node "entei" tend to fail with the IPv6 TCP test from reuseport_bpf_cpu in ubuntu_kernel_selftests/net on 5.8 kernels: # send cpu 119, receive socket 119 # send cpu 121, receive socket 121 # send cpu 123, receive socket 123 # send cpu 125, receive socket 125 # send cpu 127, receive socket 127 # IPv6 TCP publish-job-status: using request.json It failed silently here, this can be 100% reproduced with Groovy 5.8 and Focal 5.8. This will cause the ubuntu_kernel_selftests being interrupted, the test result for other tests cannot be processed to our result page. Please find attachment for the complete "net" test result on this node with Groovy 5.8.0-52.59 Add the kqa-blocker tag as this might needs to be manually verified. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+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
