[Kernel-packages] [Bug 2044592] Re: installed system + new install refuse to show GUI (Lubuntu, Xubuntu & Ubuntu Desktop noble)
I now believe this is a SUPPORT issue, something got corrupted in the
power outage, and problem exists in my $HOME which was re-used in all
partitions.
I've updated Lubuntu noble thumb-drive, and did a QA-test install of it on this
box, using the REPLACE PARTITION option of the installer which means the
existing /home was not be used.
https://iso.qa.ubuntu.com/qatracker/milestones/450/builds/290626/testcases/1701/results/
After reboot; I was offered at grub the new Lubuntu noble system, plus a
Ubuntu 22.04.3 (prior install; whatever I tried last) as expected. On
login all looks as it should; so NO ISSUE today.
I now believe I have a corruption issue in my /home which thus impacted
Lubuntu, Xubuntu & Ubuntu Desktop... also why I had a failure yesterday
when I tried a 22.04.3 install (it had same issue! where I believe it
should not have!)
** 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/2044592
Title:
installed system + new install refuse to show GUI (Lubuntu, Xubuntu &
Ubuntu Desktop noble)
Status in linux package in Ubuntu:
Incomplete
Bug description:
Please read comment #3, this issue maybe switched to INCOMPLETE
A couple of days ago I suffered a brownout, causing my noble install to
shutdown (uncleanly) on this box
- hp prodesk 600 g3 sff (i5-7500, 8gb, nvidia geforce gt710 (gk208b) + intel
graphics 630)
On power restore, the system would not allow GUI login, I noted an
Xorg crash in the /var/crash/ directory; but I was unable to ubuntu-
bug file it (out of date packages; though I `apt update; apt full-
upgrade` and nothing changed).
I've attempted a re-install today, and after install the system boots,
I get to see the plymouth screen (xubuntu) then blank screen and
cursor top left.
If I switch to text terminal; I can login and see screen for a few
seconds; before the flashing cursor returns (ie. I'm taken away from
ctrl+alt+f4 terminal and to lightdm trying to restart I suspect).
This is the same behavior I had before this install; ie. I believe the
issue is related to a recent package upgrade (this box is only
rebooted about fornightly; so the power outage was the first reboot in
maybe ten days).
My original install was Lubuntu noble (actually a mantic ISO; as noble
ISOs hadn't started then, but using an updated calamares for noble
installed that tsimonq2 requested I test, that upgraded calamares
caused the installed system to use noble sources & become noble not
mantic)
I'm convinced this is a regression due to upgrade; but it also occurs
on recent ISOs too; I also suspect it maybe related to graphic gpus
(intel & nvidia)
FYI: There is a Xorg crash file in /var/crash/ on this box too, it
likewise won't let me `ubuntu-bug` install it, again reporting out of
date packages (libsepol2)
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: guiverc1015 F wireplumber
/dev/snd/controlC1: guiverc1015 F wireplumber
/dev/snd/seq:guiverc1012 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Sat Nov 25 18:05:14 2023
InstallationDate: Installed on 2023-11-25 (0 days ago)
InstallationMedia: Xubuntu 24.04 "Noble Numbat" - Daily amd64 (20231125)
IwConfig:
lono wireless extensions.
eno1 no wireless extensions.
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0e8f:0020 GreenAsia Inc. USB to PS/2 Adapter
Bus 001 Device 003: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_AU.UTF-8
LANGUAGE=en_AU:en
PATH=(custom, no user)
SHELL=/bin/bash
TERM=linux
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=1aef793d-b806-4b39-9b05-baea27c51b5e ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.2
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/30/2018
dmi.bios.release: 2.15
dmi.bios.vendor: HP
dmi.bios.version: P07 Ver. 02.15
dmi.board.name: 82B4
dmi.board.vendor: HP
[Kernel-packages] [Bug 2044592] Re: installed system + new install refuse to show GUI (Lubuntu, Xubuntu & Ubuntu Desktop noble)
** Description changed:
+ Please read comment #3, this issue maybe switched to INCOMPLETE
+
A couple of days ago I suffered a brownout, causing my noble install to
shutdown (uncleanly) on this box
- hp prodesk 600 g3 sff (i5-7500, 8gb, nvidia geforce gt710 (gk208b) + intel
graphics 630)
On power restore, the system would not allow GUI login, I noted an Xorg
crash in the /var/crash/ directory; but I was unable to ubuntu-bug file
it (out of date packages; though I `apt update; apt full-upgrade` and
nothing changed).
I've attempted a re-install today, and after install the system boots, I
get to see the plymouth screen (xubuntu) then blank screen and cursor
top left.
If I switch to text terminal; I can login and see screen for a few
seconds; before the flashing cursor returns (ie. I'm taken away from
ctrl+alt+f4 terminal and to lightdm trying to restart I suspect).
This is the same behavior I had before this install; ie. I believe the
issue is related to a recent package upgrade (this box is only rebooted
about fornightly; so the power outage was the first reboot in maybe ten
days).
My original install was Lubuntu noble (actually a mantic ISO; as noble
ISOs hadn't started then, but using an updated calamares for noble
installed that tsimonq2 requested I test, that upgraded calamares caused
the installed system to use noble sources & become noble not mantic)
I'm convinced this is a regression due to upgrade; but it also occurs on
recent ISOs too; I also suspect it maybe related to graphic gpus (intel
& nvidia)
FYI: There is a Xorg crash file in /var/crash/ on this box too, it
likewise won't let me `ubuntu-bug` install it, again reporting out of
date packages (libsepol2)
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC0: guiverc1015 F wireplumber
- /dev/snd/controlC1: guiverc1015 F wireplumber
- /dev/snd/seq:guiverc1012 F pipewire
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: guiverc1015 F wireplumber
+ /dev/snd/controlC1: guiverc1015 F wireplumber
+ /dev/snd/seq:guiverc1012 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Sat Nov 25 18:05:14 2023
InstallationDate: Installed on 2023-11-25 (0 days ago)
InstallationMedia: Xubuntu 24.04 "Noble Numbat" - Daily amd64 (20231125)
IwConfig:
- lono wireless extensions.
-
- eno1 no wireless extensions.
+ lono wireless extensions.
+
+ eno1 no wireless extensions.
Lsusb:
- Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
- Bus 001 Device 002: ID 0e8f:0020 GreenAsia Inc. USB to PS/2 Adapter
- Bus 001 Device 003: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
- Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+ Bus 001 Device 002: ID 0e8f:0020 GreenAsia Inc. USB to PS/2 Adapter
+ Bus 001 Device 003: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
+ Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
- LANG=en_AU.UTF-8
- LANGUAGE=en_AU:en
- PATH=(custom, no user)
- SHELL=/bin/bash
- TERM=linux
+ LANG=en_AU.UTF-8
+ LANGUAGE=en_AU:en
+ PATH=(custom, no user)
+ SHELL=/bin/bash
+ TERM=linux
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=1aef793d-b806-4b39-9b05-baea27c51b5e ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
- linux-restricted-modules-6.5.0-9-generic N/A
- linux-backports-modules-6.5.0-9-generic N/A
- linux-firmware 20230919.git3672ccab-0ubuntu2.2
+ linux-restricted-modules-6.5.0-9-generic N/A
+ linux-backports-modules-6.5.0-9-generic N/A
+ linux-firmware 20230919.git3672ccab-0ubuntu2.2
RfKill:
-
+
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/30/2018
dmi.bios.release: 2.15
dmi.bios.vendor: HP
dmi.bios.version: P07 Ver. 02.15
dmi.board.name: 82B4
dmi.board.vendor: HP
dmi.board.version: KBC Version 06.21
dmi.chassis.asset.tag: AUD8130DCW
dmi.chassis.type: 3
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 6.33
dmi.modalias:
dmi:bvnHP:bvrP07Ver.02.15:bd01/30/2018:br2.15:efr6.33:svnHP:pnHPProDesk600G3SFF:pvr:rvnHP:rn82B4:rvrKBCVersion06.21:cvnHP:ct3:cvr:sku1MF39PA#ABG:
dmi.product.family: 103C_53307F HP ProDesk
dmi.product.name: HP
[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform
Verified ivsc-driver/mantic-proposed version 0~git202212210258.94ecb88b-0ubuntu0.23.10.3. ** Tags removed: verification-needed verification-needed-mantic ** Tags added: verification-done verification-done-mantic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2031412 Title: Support mipi camera on Intel Meteor Lake platform Status in HWE Next: New Status in ipu6-drivers package in Ubuntu: Fix Released Status in ivsc-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in ipu6-drivers source package in Jammy: Won't Fix Status in ivsc-driver source package in Jammy: Won't Fix Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in ipu6-drivers source package in Mantic: In Progress Status in ivsc-driver source package in Mantic: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Status in ipu6-drivers source package in Noble: Fix Released Status in ivsc-driver source package in Noble: Fix Released Status in linux source package in Noble: Triaged Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [SRU Justification] == ipu6-driver == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. [Fix] Based on upstream tag https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019, and an additional patch to enable/fix compilation of additional sensor modules. [Test Case] This is verified on MTL Lattice and VSC platforms, as well as previous generations e.g. TGL and ADL. To actually verify the camera framework: ``` # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14 # reboot into the 6.5.0-14.14 kernel $ sudo apt install intel-ipu6-dkms intel-vsc-dkms $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u $ sudo apt install gstreamer1.0-icamera v4l2-relayd ``` In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, and their dependencies, are fetched from the oem-solutions-group PPA. Everything else must come from the mantic archive. And then browse https://webcamtests.com/ for testing. [Where problems could occur] This is a new platform. We've been verifying its functions and features, and are still polishing it. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic and on, and yet the lastest stable driver was verified after Mantic was released, it's being proposed to Noble instead. == ivsc-driver == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. Need both firmware and driver change to probe the hardware correctly. [Fix] 4 commits from the latest trunk branch on upstream repository https://github.com/intel/ivsc-driver. [Test Case] With all other changes in position, Intel VSC driver modules are to be loaded as a soft dependency of some selected camera sensor modules. LJCA modules should be loaded automatically on MTL platforms as well. To actually verify the camera framework: ``` # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14 # reboot into the 6.5.0-14.14 kernel $ sudo apt install intel-ipu6-dkms intel-vsc-dkms $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u $ sudo apt install gstreamer1.0-icamera v4l2-relayd ``` In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, and their dependencies, are fetched from the oem-solutions-group PPA. Everything else must come from the mantic archive. And then browse https://webcamtests.com/ for testing. [Where problems could occur] While it changes how LJCA modules match from ACPI ID, it's also tested and verified on previous generations using IVSC, e.g. TGL, ADL. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic and on, and yet the lastest stable driver was verified after Mantic was released, it's being proposed to Noble instead. == linux/linux-oem-6.5 == [Impact] Need kernel driver fixes for int3472/iommu for Intel IPU6 platform on MTL. [Fix] Two fixes in need. One, we need IOMMU passthrough for MTL platform. The other, fix is for handshake pin support for Lattice MIPI aggregator. The Intel IPU6 camera drivers are not yet all upstreamed yet. So far Intel VSC, LJCA (the previous
[Kernel-packages] [Bug 2044330] Re: Update soundwire topology files for Intel RPL platforms
https://code.launchpad.net/~mschiu77/ubuntu/+source/firmware- sof/+git/firmware-sof/+merge/456405 created for Mantic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to firmware-sof in Ubuntu. https://bugs.launchpad.net/bugs/2044330 Title: Update soundwire topology files for Intel RPL platforms Status in firmware-sof package in Ubuntu: New Status in firmware-sof source package in Jammy: New Status in firmware-sof source package in Mantic: New Bug description: [Impact] Old RPL soundwire topology files are found to be muted when doing audio capture on left channel. [Fix] The commit from https://github.com/thesofproject/sof-bin/ is required. * https://github.com/thesofproject/sof-bin/commit/0abfe1a0aebec57bde94c5cfb9b21d6726bd804d (Update v2.2.8 topology files for Intel RPL platforms) [Test Case] Test audio functions on Dell MayaBay RTL platforms. [Where problems could occur] Most topology files for Intel RPL are updated. Need more confirmation on Intel RPL platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/2044330/+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 2021930] Re: kdump cannot generate coredump file on bluefield with 5.4 kernel
adding "-d" to kexec which shows debugging info. I did not see any error... [ 441.468322] kdump-tools[7548]: arch_process_options:178: command_line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1031-bluefield root=1 [ 441.468586] kdump-tools[7548]: arch_process_options:180: initrd: /var/lib/kdump/initrd.img [ 441.468726] kdump-tools[7548]: arch_process_options:182: dtb: (null) [ 441.468827] kdump-tools[7548]: arch_process_options:185: console: (null) [ 441.468936] kdump-tools[7548]: Try gzip decompression. [ 441.734545] kdump-tools[7548]: kernel: 0xa6946010 kernel_size: 0x2c9c198 [ 441.734767] kdump-tools[7548]: set_phys_offset: phys_offset : 8000 (method : vmcoreinfo pt_note) [ 441.734967] kdump-tools[7548]: get_memory_ranges:+[0] 8200 - 87ff [ 441.735103] kdump-tools[7548]: get_memory_ranges:+[1] 88002000 - fffd [ 441.735209] kdump-tools[7548]: get_memory_ranges:- b900 - bcff [ 441.735308] kdump-tools[7548]: get_memory_ranges:- fd00 - feff [ 441.735391] kdump-tools[7548]: get_memory_ranges:+[4] 0001 - 00085a0b [ 441.735467] kdump-tools[7548]: get_memory_ranges:- 0001001ea000 - 0001001eafff [ 441.735568] kdump-tools[7548]: get_memory_ranges:- 00010022 - 00010022 [ 441.735655] kdump-tools[7548]: get_memory_ranges:- 00010023 - 00010023 [ 441.735737] kdump-tools[7548]: get_memory_ranges:- 00010024 - 00010024 [ 441.735813] kdump-tools[7548]: get_memory_ranges:- 00010025 - 00010025 [ 441.735885] kdump-tools[7548]: get_memory_ranges:- 00010026 - 00010026 [ 441.735968] kdump-tools[7548]: get_memory_ranges:- 00010027 - 00010027 [ 441.736117] kdump-tools[7548]: get_memory_ranges:- 00010028 - 00010028 [ 441.736224] kdump-tools[7548]: get_memory_ranges:- 00010029 - 00010029 [ 441.736306] kdump-tools[7548]: get_memory_ranges:- 0001002a - 0001002a [ 441.736380] kdump-tools[7548]: get_memory_ranges:- 0001002b - 0001002b [ 441.736481] kdump-tools[7548]: get_memory_ranges:- 0001002c - 0001002c [ 441.736570] kdump-tools[7548]: get_memory_ranges:- 0001002d - 0001002d [ 441.736650] kdump-tools[7548]: get_memory_ranges:- 0001002e - 0001002e [ 441.736737] kdump-tools[7548]: get_memory_ranges:- 0001002f - 0001002f [ 441.736815] kdump-tools[7548]: get_memory_ranges:- 00010030 - 00010030 [ 441.736887] kdump-tools[7548]: get_memory_ranges:- 00010031 - 00010031 [ 441.736957] kdump-tools[7548]: get_memory_ranges:- 00010032 - 00010032 [ 441.737028] kdump-tools[7548]: get_memory_ranges:- 000276d5 - 0002776a [ 441.737096] kdump-tools[7548]: get_memory_ranges:- 00082f40 - 00084ebf [ 441.737240] kdump-tools[7548]: get_memory_ranges:- 00084ed5 - 00084ed50fff [ 441.737392] kdump-tools[7548]: get_memory_ranges:- 000851d3 - 000851d3 [ 441.737504] kdump-tools[7548]: get_memory_ranges:- 00085214b000 - 000854ee6fff [ 441.737588] kdump-tools[7548]: get_memory_ranges:- 0008570c - 00085a0b [ 441.737665] kdump-tools[7548]: get_memory_ranges:+[12] 00085a0d - 00085a1a [ 441.737740] kdump-tools[7548]: get_memory_ranges:+[13] 00085a2a - 00085a49afff [ 441.737828] kdump-tools[7548]: get_memory_ranges:- 00085a2ac000 - 00085a2acfff [ 441.737912] kdump-tools[7548]: get_memory_ranges:+[15] 00085a4f7000 - 00085a4f [ 441.738007] kdump-tools[7548]: get_memory_ranges:+[16] 00085a64 - 00085a79 [ 441.738099] kdump-tools[7548]: get_memory_ranges:+[17] 00085a7c - 00085a7c [ 441.738180] kdump-tools[7548]: get_memory_ranges:+[18] 00085a91 - 00085a92 [ 441.738253] kdump-tools[7548]: get_memory_ranges:+[19] 00085a9d - 00085aa0 [ 441.738328] kdump-tools[7548]: get_memory_ranges:- 00085a9d - 00085a9d0fff [ 441.738399] kdump-tools[7548]: get_memory_ranges:+[20] 00085acc - 00085ad9 [ 441.738486] kdump-tools[7548]: get_memory_ranges:- 00085ad9 - 00085ad9 [ 441.738567] kdump-tools[7548]: get_memory_ranges:+[21] 00085af8 - 00085ff9 [ 441.738642] kdump-tools[7548]: get_memory_ranges:- 00085bde4000 - 00085c083fff [ 441.738736] kdump-tools[7548]: get_memory_ranges:- 00085c086000 - 00085c087fff [ 441.738822] kdump-tools[7548]: get_memory_ranges:- 00085c088000 - 00085c088fff [ 441.738895] kdump-tools[7548]: get_memory_ranges:- 00085c089000 -
[Kernel-packages] [Bug 2021930] Re: kdump cannot generate coredump file on bluefield with 5.4 kernel
I also tested it on 5.15.0-1031-bluefield and it also fails. Configurations: root@bu-oob:~# kdump-config show DUMP_MODE: kdump USE_KDUMP: 1 KDUMP_COREDIR: /var/crash crashkernel addr: 0xbd00 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.15.0-1031-bluefield kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.15.0-1031-bluefield current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-1031-bluefield root=UUID=8e8b38a6-7d3d-4a29-b7a0-99761624f941 ro console=hvc0 console=ttyAMA0 earlycon=pl011,0x1301 fixrtc net.ifnames=0 biosdevname=0 iommu.passthrough=1 console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@bu-lab60v3-oob:~# ### root@bu-oob:~# dmesg |grep -i crash [0.00] crashkernel reserved: 0xbd00 - 0xfd00 (1024 MB) [0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1031-bluefield root=UUID=8e8b38a6-7d3d-4a29-b7a0-99761624f941 ro console=hvc0 console=ttyAMA0 earlycon=pl011,0x1301 fixrtc net.ifnames=0 biosdevname=0 iommu.passthrough=1 console=tty1 console=ttyS0 crashkernel=2G-4G:320M,4G-32G:1024M,32G-64G:1536M,64G-128G:2048M,128G-:4096M [5.230439] pstore: Using crash dump compression: deflate root@bu-oob:~# root@bu-oob:~# cat /etc/default/grub.d/kdump-tools.cfg GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=2G-4G:320M,4G-32G:1024M,32G-64G:1536M,64G-128G:2048M,128G-:4096M" root@bu-lab60v3-oob:~# grep -e "CRASH" -e "KEXEC" /boot/config-5.15.0-1031-bluefield CONFIG_KEXEC=y CONFIG_KEXEC_FILE=y CONFIG_KEXEC_SIG=y CONFIG_KEXEC_IMAGE_VERIFY_SIG=y CONFIG_CRASH_DUMP=y CONFIG_CRASH_CORE=y CONFIG_KEXEC_CORE=y CONFIG_HAVE_IMA_KEXEC=y CONFIG_IMA_KEXEC=y *** How to reproduce *** When manually triggers the crash "echo c > /proc/sysrq-trigger" the system just hangs without showing any message/log. -- 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/2021930 Title: kdump cannot generate coredump file on bluefield with 5.4 and 5.15 kernel Status in linux-bluefield package in Ubuntu: New Bug description: kdump cannot generate coredump file on bluefield with 5.4 kernel Bug description: Following the instruction in https://ubuntu.com/server/docs/kernel-crash-dump, the coredump file cannot be generated. Bluefield is running 5.4 kernel bf2:~$ uname -a Linux sw-mtx-008-bf2 5.4.0-1060-bluefield #66-Ubuntu SMP PREEMPT Mon Mar 27 15:52:50 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux crashkernel parameter is configured bf2:~$ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-5.4.0-1060-bluefield root=UUID=52ddbe2c-ee4f-48d4-b7d4-ab76e264e438 ro console=hvc0 console=ttyAMA0 earlycon=pl011,0x0100 fixrtc net.ifnames=0 biosdevname=0 iommu.passthrough=1 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M bf2:~$ dmesg | grep -i crash [0.00] crashkernel reserved: 0xcfe0 - 0xefe0 (512 MB) [0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1060-bluefield root=UUID=52ddbe2c-ee4f-48d4-b7d4-ab76e264e438 ro console=hvc0 console=ttyAMA0 earlycon=pl011,0x0100 fixrtc net.ifnames=0 biosdevname=0 iommu.passthrough=1 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M [8.070921] pstore: Using crash dump compression: deflate kdump-config is as below: bf2:~$ kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.4.0-1060-bluefield kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.4.0-1060-bluefield current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.4.0-1060-bluefield root=UUID=52ddbe2c-ee4f-48d4-b7d4-ab76e264e438 ro console=hvc0 console=ttyAMA0 earlycon=pl011,0x0100 fixrtc net.ifnames=0 biosdevname=0 iommu.passthrough=1 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz sysrq: bf2:/# cat /proc/sys/kernel/sysrq 176 After trigged the crash manually with "echo c > /proc/sysrq-trigger", the system could not come up because of OOM. And after change the crashkernel with 1024M memory it still hangs. With default 512M, it hangs at "Killed process 674"
[Kernel-packages] [Bug 2028065] Re: Support for Intel Discrete Gale Peak2/BE200
** Tags added: originate-from-2044233
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2028065
Title:
Support for Intel Discrete Gale Peak2/BE200
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-firmware source package in Jammy:
Incomplete
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in linux source package in Mantic:
Fix Released
Status in linux-firmware source package in Mantic:
Incomplete
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
== linux-firmware ==
[Impact]
Missing firmware for Intel BE200 on Intel Meteor Lake platform.
[Fix]
2 upstream commits needed, and the iwlwifi firmware one is in the pull request
for bug 2037390 (Add firmware for Intel CNVi AX211 on Intel Meteor Lake
platform). Rebased the second one onto PR for bug 2037390.
[Test Case]
Boot with firmware blobs installed, and iwlwifi and btintel should probe
successfully without error.
[Where problems could occur]
While this introduces support for new hardware on new platforms, expect every
possible problem.
[Other Info]
We're to support oem-6.5/jammy, and mantic for best effort. While there is no
Noble branch yet, Noble is not nominated.
While this is rebased onto PR for bug 2037390, it makes that PR a prerequisite
to this one.
== kernel ==
[Impact]
Missing Intel Gale Peak WiFi/Bluetooth support.
[Fix]
WIFI:
a. kernel driver :
- commit 12a89f0177092 ("wifi: iwlwifi: remove 'use_tfh' config to fix
crash") [v6.5-rc2]
b. firmware (to be released):
- ES
- iwlwifi-gl-b0-fm-b0-83.ucode
- iwlwifi-gl-b0-fm-b0.pnvm
- QS
- iwlwifi-gl-c0-fm-c0-83.ucode
- iwlwifi-gl-c0-fm-c0.pnvm
Bluetooth:
a. kernel driver:
- commit 8fd791afddca ("Bluetooth: btintel: Add support for Gale Peak")
- commit 24921786074b ("Bluetooth: Add support for Gale Peak (8087:0036)")
b. firmware (to be released):
- ES
- intel/ibt-0191-0191.sfi
- intel/ibt-0191-0191.ddc
- QS
- intel/ibt-0291-0291.sfi
- intel/ibt-0291-0291.ddc
[Test Case]
To boot with patched kernel and prereleased firmware blob and check basic
WiFi/Bluetooth functions.
[Where problems could occur]
New device. Expect incomplete functions and bugs.
[Other Info]
Targets 6.5 kernels, so only nominated for Mantic and oem-6.5.
= original bug report ==
WIFI:
a. kernel driver :
- commit 12a89f0177092 ("wifi: iwlwifi: remove 'use_tfh' config to fix
crash") [v6.5-rc2]
b. firmware (to be released):
- iwlwifi-gl-b0-fm-b0-83.ucode
- iwlwifi-gl-b0-fm-b0.pnvm
Bluetooth:
a. kernel driver:
- commit 8fd791afddca ("Bluetooth: btintel: Add support for Gale Peak")
- commit 24921786074b ("Bluetooth: Add support for Gale Peak (8087:0036)")
b. firmware (to be released):
- intel/ibt-0191-0191.sfi
- intel/ibt-0191-0191.ddc
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2028065/+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 2040354] Re: Add K24 device tree
** Tags removed: verification-needed-jammy-linux-xilinx-zynqmp ** Tags added: verification-done-jammy -- 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/2040354 Title: Add K24 device tree Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux-xilinx-zynqmp source package in Jammy: Fix Committed Bug description: [ Impact ] * This ports the K24 device trees from the Xilinx 6.1 kernel (xlnx_rebase_v6.1_LTS_2023.1_update) * This will allow the same image.its file and thus flash-kernel package to be used for the K24 development images and the stable release. [ Test Plan ] * The k24 platform does not need to be tested since it is not a certified platform. The normal regression testing on K26 and ZCU platforms is sufficient. [ Where problems could occur ] * A bug in the device tree could cause a build error in the kernel. The device tree is not used by any certified images. [ Other Info ] The change squashes together the following changes from Xilinx xlnx_rebase_v6.1_LTS_2023.1_update branch. Patches that modified device tree other than: arch/arm64/boot/dts/xilinx/zynqmp-sck-kd-g-revA.dts arch/arm64/boot/dts/xilinx/zynqmp-sm-k24-revA.dts arch/arm64/boot/dts/xilinx/zynqmp-smk-k24-revA.dts were modified to remove the other changes. a89bdb9e6f1f arm64: zynqmp: Add/Update/Sync DTs for xilinx platforms f1fe53d988d8 arm64: zynqmp: Update ADI PHY properties for KD240 f660fc7bba89 arm64: zynqmp: Use MIO 77 for ADI PHY reset on KD240 41a6b53e0691 arm64: zynqmp: Fill model name for SOM CCs 958f20d8445e arm64: zynqmp: Fix memory size on k24 c3cc27055c19 arm64: zynqmp: Wire can0 on kd240-revA 9da2d3e73b17 arm64: zynqmp: Configure gem1 rx pins on kd240 board 646a2dfaaaf8 arm64: zynqmp: Cover K24/KD240 revB/1 boards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2040354/+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 2042388] Re: context test in ubuntu_stress_smoke_test failed with M-6.5 riscv / starfive instances
** Also affects: linux-starfive (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-starfive (Ubuntu) Status: New => Invalid ** Changed in: linux-starfive (Ubuntu Mantic) Status: New => Fix Committed ** Also affects: linux-riscv (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-riscv (Ubuntu) Status: New => Invalid ** Changed in: linux-riscv (Ubuntu Mantic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive in Ubuntu. https://bugs.launchpad.net/bugs/2042388 Title: context test in ubuntu_stress_smoke_test failed with M-6.5 riscv / starfive instances Status in ubuntu-kernel-tests: New Status in glibc package in Ubuntu: Invalid Status in linux-riscv package in Ubuntu: Invalid Status in linux-starfive package in Ubuntu: Invalid Status in glibc source package in Mantic: Invalid Status in linux-riscv source package in Mantic: Fix Committed Status in linux-starfive source package in Mantic: Fix Committed Bug description: This issue can be found from the very beginning of these two kernels * mantic/linux-starfive/6.5.0-1001.2 * mantic/linux-riscv/6.5.0-7.7.2 Test failed with: context STARTING context RETURNED 2 context FAILED stress-ng: debug: [12644] invoked with './stress-ng -v -t 5 --context 4 --context-ops 3000 --ignite-cpu --syslog --verbose --verify --oomable' by user 0 'root' stress-ng: debug: [12644] stress-ng 0.16.05 gaea6f3306f46 stress-ng: debug: [12644] system: Linux mantic-starfive-riscv64 6.5.0-1001-starfive #2-Ubuntu SMP Fri Oct 6 12:08:59 UTC 2023 riscv64, gcc 13.2.0, glibc 2.38 stress-ng: debug: [12644] RAM total: 7.7G, RAM free: 6.6G, swap free: 1024.0M stress-ng: debug: [12644] temporary file path: '/home/ubuntu/autotest/client/tmp/ubuntu_stress_smoke_test/src/stress-ng', filesystem type: ext2 (4617314 blocks available) stress-ng: debug: [12644] 8 processors online, 8 processors configured stress-ng: info: [12644] setting to a 5 secs run per stressor stress-ng: debug: [12644] cache allocate: using defaults, cannot determine cache level details stress-ng: debug: [12644] cache allocate: shared cache buffer size: 2048K stress-ng: info: [12644] dispatching hogs: 4 context stress-ng: debug: [12644] starting stressors stress-ng: debug: [12644] 4 stressors started stress-ng: debug: [12645] context: [12645] started (instance 0 on CPU 2) stress-ng: debug: [12647] context: [12647] started (instance 2 on CPU 5) stress-ng: debug: [12648] context: [12648] started (instance 3 on CPU 7) stress-ng: debug: [12646] context: [12646] started (instance 1 on CPU 4) stress-ng: debug: [12644] context: [12645] terminated on signal: 11 (Segmentation fault) stress-ng: debug: [12644] context: [12645] terminated (success) stress-ng: debug: [12644] context: [12646] terminated on signal: 11 (Segmentation fault) stress-ng: debug: [12644] context: [12646] terminated (success) stress-ng: debug: [12644] context: [12647] terminated on signal: 11 (Segmentation fault) stress-ng: debug: [12644] context: [12647] terminated (success) stress-ng: debug: [12644] context: [12648] terminated on signal: 11 (Segmentation fault) stress-ng: debug: [12644] context: [12648] terminated (success) stress-ng: warn: [12644] metrics-check: all bogo-op counters are zero, data may be incorrect stress-ng: debug: [12644] metrics-check: all stressor metrics validated and sane stress-ng: info: [12644] skipped: 0 stress-ng: info: [12644] passed: 4: context (4) stress-ng: info: [12644] failed: 0 stress-ng: info: [12644] metrics untrustworthy: 0 stress-ng: info: [12644] unsuccessful run completed in 9.98 secs Looks like the tests have passed. But marked as failed with a non-zero return code. Tested with stress-ng V0.16.05 and V0.17.00, they all failed with the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2042388/+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 1988023] Re: Could not switch uppercase/lowercase by using keyboard of laptop
Hi Jeff, Any progress for this issue? -- 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/1988023 Title: Could not switch uppercase/lowercase by using keyboard of laptop Status in linux package in Ubuntu: Confirmed Bug description: 1. Fresh install ubuntu server 22.04.1 on Lenovo server. 2. Install console-data package 3. Get locale status: # localectl status System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: us X11 Model: pc105 4. Fail to ist and set keymap with command "localectl", but the kmap file can be found in the /usr/share./keymaps/ #localectl list-keymaps Failed to read list of keymaps: No such file or directory # localectl set-keymap us Failed to set keymap: Keymap us is not installed. # find /usr/ -name us.kmap.gz /usr/share/keymaps/i386/qwerty/us.kmap.gz 5. It need type "CapsLock" twice when want to switch uppercase/lowercase by using keyboard of laptop, not once, the other keyboard has no issue about it. # dumpkeys | grep -E "keymaps|58" keymaps 0-127 keycode 58 = CtrlL_Lock 6. It can switch uppercase/lowercase normally after run command "loadkeys us". Please help check why need type twice "CapsLock" for switching uppercase/lowercase and how to fix it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-29 (0 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) MachineType: Lenovo ThinkSystem SR630 V2 Package: systemd 249.11-0ubuntu3.4 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: jammy uec-images Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Lenovo dmi.bios.version: AFE118I-1.30 dmi.board.asset.tag: none dmi.board.name: 7Z70CTO1WW dmi.board.vendor: Lenovo dmi.board.version: 05 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnLenovo:bvrAFE118I-1.30:bd04/21/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR630V2:pvr05:rvnLenovo:rn7Z70CTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7Z70CTO1WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR630 V2 dmi.product.sku: 7Z70CTO1WW dmi.product.version: 05 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988023/+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 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build
Seems to also affect Mantic, if it was installed as jammy, the upgraded to Mantic. But doesn't seem to affect Mantic system if they were installed fresh as Mantic. All Tests, so far, show it does not affect Noble at all (either upgraded from Mantic or installed fresh). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2044630 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+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 2044810] Re: VF cannot creation with large CPU core systems when RDMA enabled with intel ice driver
** Package changed: ubuntu => linux-hwe-5.15 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2044810 Title: VF cannot creation with large CPU core systems when RDMA enabled with intel ice driver Status in linux-hwe-5.15 package in Ubuntu: New Bug description: Issue Environment: == root@npx:~# cat /etc/os-release PRETTY_NAME="Ubuntu 22.04.3 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.3 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=jammy root@npx:~# uname -r 5.15.0-88-generic root@npx:~# lscpu | head -n 5 Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Address sizes: 52 bits physical, 57 bits virtual Byte Order: Little Endian CPU(s): 256 root@npx:~# ethtool -i ens2f0 driver: ice version: 5.15.0-88-generic firmware-version: 4.40 0x8001c7d5 1.3534.0 expansion-rom-version: bus-info: :16:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes root@npx:~# lspci -s 16:00.0 -vvv 16:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-C for SFP (rev 02) Subsystem: Intel Corporation Ethernet Network Adapter E810-XXV-4 Physical Slot: 2 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [210 v1] Physical Layer 16.0 GT/s Capabilities: [250 v1] Lane Margining at the Receiver Kernel driver in use: ice Kernel modules: ice Issue Description: == # echo 1 > /sys/class/net/ens2f0/device/sriov_numvfs [ 5734.469217] ice :16:00.0: Enabling 1 VFs [ 5734.574945] pci :16:01.0: [8086:1889] type 00 class 0x02 [ 5734.574970] pci :16:01.0: enabling Extended Tags [ 5734.575471] pci :16:01.0: Adding to iommu group 443 [ 5734.575718] ice :16:00.0: Only 0 MSI-X interrupts available for SR-IOV. Not enough to support minimum of 2 MSI-X interrupts per VF for 1 VFs [ 5734.575815] ice :16:00.0: Not enough resources for 1 VFs, try with fewer number of VFs [ 5734.576861] pci :16:01.0: Removing from iommu group 443 [ 5734.623292] iavf: Intel(R) Ethernet Adaptive Virtual Function Network Driver [ 5734.623297] Copyright (c) 2013 - 2018 Intel Corporation. [ 5735.598871] ice :16:00.0: Failed to enable SR-IOV: -28 Issue Found: 1> After disable RDMA, the VF creation works fine; from kernel code, the MSIx are preserved by LAN and RDMA based on CPU cores, this will exhauste all available MSIx for larger core systems (some PF port will only have 512 MSIx in total), this doesn't make sense as the default value (at least make sure a few number VFs can be created successfully if NIC support it) 2> When do the MSIx resource reallocation manually, still raise below error, this is some what a strange behavior, it's better to allow such actions by default from kernel: root@npx:~# devlink resource show pci/:16:00.0 kernel answers: Operation not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2044810/+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 2044810] [NEW] VF cannot creation with large CPU core systems when RDMA enabled with intel ice driver
You have been subscribed to a public bug: Issue Environment: == root@npx:~# cat /etc/os-release PRETTY_NAME="Ubuntu 22.04.3 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.3 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=jammy root@npx:~# uname -r 5.15.0-88-generic root@npx:~# lscpu | head -n 5 Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Address sizes: 52 bits physical, 57 bits virtual Byte Order: Little Endian CPU(s): 256 root@npx:~# ethtool -i ens2f0 driver: ice version: 5.15.0-88-generic firmware-version: 4.40 0x8001c7d5 1.3534.0 expansion-rom-version: bus-info: :16:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes root@npx:~# lspci -s 16:00.0 -vvv 16:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-C for SFP (rev 02) Subsystem: Intel Corporation Ethernet Network Adapter E810-XXV-4 Physical Slot: 2 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [210 v1] Physical Layer 16.0 GT/s Capabilities: [250 v1] Lane Margining at the Receiver Kernel driver in use: ice Kernel modules: ice Issue Description: == # echo 1 > /sys/class/net/ens2f0/device/sriov_numvfs [ 5734.469217] ice :16:00.0: Enabling 1 VFs [ 5734.574945] pci :16:01.0: [8086:1889] type 00 class 0x02 [ 5734.574970] pci :16:01.0: enabling Extended Tags [ 5734.575471] pci :16:01.0: Adding to iommu group 443 [ 5734.575718] ice :16:00.0: Only 0 MSI-X interrupts available for SR-IOV. Not enough to support minimum of 2 MSI-X interrupts per VF for 1 VFs [ 5734.575815] ice :16:00.0: Not enough resources for 1 VFs, try with fewer number of VFs [ 5734.576861] pci :16:01.0: Removing from iommu group 443 [ 5734.623292] iavf: Intel(R) Ethernet Adaptive Virtual Function Network Driver [ 5734.623297] Copyright (c) 2013 - 2018 Intel Corporation. [ 5735.598871] ice :16:00.0: Failed to enable SR-IOV: -28 Issue Found: 1> After disable RDMA, the VF creation works fine; from kernel code, the MSIx are preserved by LAN and RDMA based on CPU cores, this will exhauste all available MSIx for larger core systems (some PF port will only have 512 MSIx in total), this doesn't make sense as the default value (at least make sure a few number VFs can be created successfully if NIC support it) 2> When do the MSIx resource reallocation manually, still raise below error, this is some what a strange behavior, it's better to allow such actions by default from kernel: root@npx:~# devlink resource show pci/:16:00.0 kernel answers: Operation not supported ** Affects: linux-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- VF cannot creation with large CPU core systems when RDMA enabled with intel ice driver https://bugs.launchpad.net/bugs/2044810 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043962] Re: [Mediatek] mt8195-demo: enable CONFIG_COMMON_CLK_MT8188 and CONFIG_MTK_PMIC_WRAP
** Changed in: linux (Ubuntu Noble) 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/2043962 Title: [Mediatek] mt8195-demo: enable CONFIG_COMMON_CLK_MT8188 and CONFIG_MTK_PMIC_WRAP Status in linux package in Ubuntu: Incomplete Status in linux source package in Noble: Incomplete Bug description: [SRU Justification] [Impact] emmc storage is not usable after booting. [Fix] CONFIG_COMMON_CLK_MT8188 and CONFIG_MTK_PMIC_WRAP need to be built-in to supply clock and power as early as possible, in order to have the emmc storage for further installation. both of the modules were in initramfs already but still not be able to bring up the emmc. according to mediatek, these two drivers should be built-in for further peripherals usage. [Test Case] 1. build test. 2. testing on the target device, mediatek g1200 evk board, and check the emmc storage could be recognize and mountable after booting. [Where problems could occur] the risk would be low because both drivers are only used on mediatek platform. [Other info] the purpose of this is to make ubuntu as an arm systemready ir distribution for mediatek platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043962/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1222440] Re: iwlwifi 0000:01:00.0: Microcode SW error detected. Restarting 0x2000000.
Launchpad has imported 19 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=60981. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2013-09-08T15:47:15+00:00 caravena wrote: Open bug in launchpad.net: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222440 01:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N 6235 [8086:088e] (rev 24) Subsystem: Intel Corporation Centrino Advanced-N 6235 AGN [8086:4060] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi [ 231.692719] iwlwifi :01:00.0: Microcode SW error detected. Restarting 0x200. [ 231.692732] iwlwifi :01:00.0: CSR values: [ 231.692738] iwlwifi :01:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG) [ 231.692747] iwlwifi :01:00.0:CSR_HW_IF_CONFIG_REG: 0X00484b00 [ 231.692756] iwlwifi :01:00.0: CSR_INT_COALESCING: 0Xff40 [ 231.692764] iwlwifi :01:00.0: CSR_INT: 0X [ 231.692773] iwlwifi :01:00.0:CSR_INT_MASK: 0X [ 231.692781] iwlwifi :01:00.0: CSR_FH_INT_STATUS: 0X [ 231.692789] iwlwifi :01:00.0: CSR_GPIO_IN: 0X0038 [ 231.692797] iwlwifi :01:00.0: CSR_RESET: 0X [ 231.692806] iwlwifi :01:00.0:CSR_GP_CNTRL: 0X080403c5 [ 231.692814] iwlwifi :01:00.0: CSR_HW_REV: 0X00b0 [ 231.692822] iwlwifi :01:00.0: CSR_EEPROM_REG: 0Xc4540ffd [ 231.692830] iwlwifi :01:00.0: CSR_EEPROM_GP: 0X9801 [ 231.692838] iwlwifi :01:00.0: CSR_OTP_GP_REG: 0X00030001 [ 231.692845] iwlwifi :01:00.0: CSR_GIO_REG: 0X00080044 [ 231.692854] iwlwifi :01:00.0:CSR_GP_UCODE_REG: 0Xd0ed [ 231.692862] iwlwifi :01:00.0: CSR_GP_DRIVER_REG: 0X [ 231.692870] iwlwifi :01:00.0: CSR_UCODE_DRV_GP1: 0X [ 231.692877] iwlwifi :01:00.0: CSR_UCODE_DRV_GP2: 0X [ 231.692885] iwlwifi :01:00.0: CSR_LED_REG: 0X0040 [ 231.692893] iwlwifi :01:00.0:CSR_DRAM_INT_TBL_REG: 0X881187ae [ 231.692901] iwlwifi :01:00.0:CSR_GIO_CHICKEN_BITS: 0X27800200 [ 231.692909] iwlwifi :01:00.0: CSR_ANA_PLL_CFG: 0X [ 231.692917] iwlwifi :01:00.0: CSR_HW_REV_WA_REG: 0X0001001a [ 231.692925] iwlwifi :01:00.0:CSR_DBG_HPET_MEM_REG: 0X [ 231.692930] iwlwifi :01:00.0: FH register values: [ 231.692948] iwlwifi :01:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X116b8500 [ 231.692966] iwlwifi :01:00.0:FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X01158430 [ 231.692983] iwlwifi :01:00.0: FH_RSCSR_CHNL0_WPTR: 0X00f0 [ 231.693000] iwlwifi :01:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X80801114 [ 231.693018] iwlwifi :01:00.0: FH_MEM_RSSR_SHARED_CTRL_REG: 0X00fc [ 231.693035] iwlwifi :01:00.0:FH_MEM_RSSR_RX_STATUS_REG: 0X0703 [ 231.693053] iwlwifi :01:00.0:FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X [ 231.693070] iwlwifi :01:00.0:FH_TSSR_TX_STATUS_REG: 0X07ff0001 [ 231.693088] iwlwifi :01:00.0: FH_TSSR_TX_ERROR_REG: 0X [ 231.693099] iwlwifi :01:00.0: Loaded firmware version: 18.168.6.1 [ 231.693109] iwlwifi :01:00.0: FW error in SYNC CMD REPLY_TX_LINK_QUALITY_CMD [ 231.693126] CPU: 0 PID: 158 Comm: kworker/u16:7 Tainted: GF O 3.11.0-5-generic #11-Ubuntu [ 231.693130] Hardware name: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C/SAMSUNG_NP1234567890, BIOS P14AAJ 04/15/2013 [ 231.693163] Workqueue: iwlwifi iwl_bg_scan_completed [iwldvm] [ 231.693172] 01f4 880115307af0 816f23a1 880116c0 [ 231.693181] 880115307b58 a02cf1ef [ 231.693189] 88011530aee0 810854e0 880115307b20 880115307b20 [ 231.693197] Call Trace: [ 231.693210] [] dump_stack+0x45/0x56 [ 231.693234] [] iwl_trans_pcie_send_hcmd+0x53f/0x5d0 [iwlwifi] [ 231.693237] iwlwifi :01:00.0: Start IWL Error Log Dump: [ 231.693244] iwlwifi :01:00.0: Status: 0x004C, count: 6 [ 231.693250] iwlwifi :01:00.0: 0x2075 | ADVANCED_SYSASSERT [ 231.693255] iwlwifi :01:00.0: 0x9BF4 | uPc [ 231.693261] iwlwifi :01:00.0: 0x9BCE | branchlink1 [ 231.693266] iwlwifi :01:00.0:
[Kernel-packages] [Bug 1374760] Re: iwlwifi 0000:01:00.0: Microcode SW error detected. Restarting 0x2000000.
Launchpad has imported 6 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=90171. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2014-12-21T05:12:39+00:00 caravena wrote: [ 2961.582067] iwlwifi :01:00.0: Microcode SW error detected. Restarting 0x200. [ 2961.582079] iwlwifi :01:00.0: CSR values: [ 2961.582084] iwlwifi :01:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG) [ 2961.582092] iwlwifi :01:00.0:CSR_HW_IF_CONFIG_REG: 0X00484b00 [ 2961.582100] iwlwifi :01:00.0: CSR_INT_COALESCING: 0Xff40 [ 2961.582107] iwlwifi :01:00.0: CSR_INT: 0X [ 2961.582114] iwlwifi :01:00.0:CSR_INT_MASK: 0X [ 2961.582122] iwlwifi :01:00.0: CSR_FH_INT_STATUS: 0X [ 2961.582129] iwlwifi :01:00.0: CSR_GPIO_IN: 0X0038 [ 2961.582136] iwlwifi :01:00.0: CSR_RESET: 0X [ 2961.582143] iwlwifi :01:00.0:CSR_GP_CNTRL: 0X080403c5 [ 2961.582151] iwlwifi :01:00.0: CSR_HW_REV: 0X00b0 [ 2961.582158] iwlwifi :01:00.0: CSR_EEPROM_REG: 0Xcc540ffd [ 2961.582166] iwlwifi :01:00.0: CSR_EEPROM_GP: 0X9801 [ 2961.582173] iwlwifi :01:00.0: CSR_OTP_GP_REG: 0X00030001 [ 2961.582180] iwlwifi :01:00.0: CSR_GIO_REG: 0X00080044 [ 2961.582187] iwlwifi :01:00.0:CSR_GP_UCODE_REG: 0X22d0 [ 2961.582194] iwlwifi :01:00.0: CSR_GP_DRIVER_REG: 0X [ 2961.582201] iwlwifi :01:00.0: CSR_UCODE_DRV_GP1: 0X [ 2961.582209] iwlwifi :01:00.0: CSR_UCODE_DRV_GP2: 0X [ 2961.582216] iwlwifi :01:00.0: CSR_LED_REG: 0X0040 [ 2961.582224] iwlwifi :01:00.0:CSR_DRAM_INT_TBL_REG: 0X880cdd12 [ 2961.582231] iwlwifi :01:00.0:CSR_GIO_CHICKEN_BITS: 0X27800200 [ 2961.582238] iwlwifi :01:00.0: CSR_ANA_PLL_CFG: 0X [ 2961.582246] iwlwifi :01:00.0: CSR_MONITOR_STATUS_REG: 0X43f7f757 [ 2961.582253] iwlwifi :01:00.0: CSR_HW_REV_WA_REG: 0X0001001a [ 2961.582260] iwlwifi :01:00.0:CSR_DBG_HPET_MEM_REG: 0X [ 2961.582265] iwlwifi :01:00.0: FH register values: [ 2961.582282] iwlwifi :01:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X1193c500 [ 2961.582299] iwlwifi :01:00.0:FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X01190060 [ 2961.582315] iwlwifi :01:00.0: FH_RSCSR_CHNL0_WPTR: 0X00d8 [ 2961.582331] iwlwifi :01:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X80801114 [ 2961.582348] iwlwifi :01:00.0: FH_MEM_RSSR_SHARED_CTRL_REG: 0X00fc [ 2961.582364] iwlwifi :01:00.0:FH_MEM_RSSR_RX_STATUS_REG: 0X0703 [ 2961.582380] iwlwifi :01:00.0:FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X [ 2961.582397] iwlwifi :01:00.0:FH_TSSR_TX_STATUS_REG: 0X07ff0001 [ 2961.582414] iwlwifi :01:00.0: FH_TSSR_TX_ERROR_REG: 0X [ 2961.582419] iwlwifi :01:00.0: Loaded firmware version: 18.168.6.1 [ 2961.582543] iwlwifi :01:00.0: Start IWL Error Log Dump: [ 2961.582549] iwlwifi :01:00.0: Status: 0x02CC, count: 6 [ 2961.582554] iwlwifi :01:00.0: 0x28AA | ADVANCED_SYSASSERT [ 2961.582558] iwlwifi :01:00.0: 0x00015984 | uPc [ 2961.582562] iwlwifi :01:00.0: 0x00015974 | branchlink1 [ 2961.582566] iwlwifi :01:00.0: 0x00015974 | branchlink2 [ 2961.582570] iwlwifi :01:00.0: 0xDBEA | interruptlink1 [ 2961.582574] iwlwifi :01:00.0: 0x | interruptlink2 [ 2961.582578] iwlwifi :01:00.0: 0x0729 | data1 [ 2961.582582] iwlwifi :01:00.0: 0x0023 | data2 [ 2961.582586] iwlwifi :01:00.0: 0x01F3 | line [ 2961.582590] iwlwifi :01:00.0: 0x1F00D2F0 | beacon time [ 2961.582594] iwlwifi :01:00.0: 0xBD8A8D10 | tsf low [ 2961.582598] iwlwifi :01:00.0: 0x0033 | tsf hi [ 2961.582601] iwlwifi :01:00.0: 0x | time gp1 [ 2961.582605] iwlwifi :01:00.0: 0xB029F31F | time gp2 [ 2961.582609] iwlwifi :01:00.0: 0x | time gp3 [ 2961.582613] iwlwifi :01:00.0: 0x754312A8 | uCode version [ 2961.582617] iwlwifi :01:00.0: 0x00B0 | hw version [ 2961.582621] iwlwifi :01:00.0: 0x00484B00 | board version [ 2961.582625] iwlwifi :01:00.0: 0x001C | hcmd [ 2961.582629] iwlwifi :01:00.0: 0xAF863000 | isr0 [ 2961.582633] iwlwifi :01:00.0: 0x1189F800 | isr1 [ 2961.582637] iwlwifi :01:00.0: 0x0E1A | isr2 [ 2961.582641] iwlwifi :01:00.0: 0x0543FCC2 | isr3 [ 2961.582645] iwlwifi :01:00.0: 0x |
[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform
Hello You-Sheng, or anyone else affected, Accepted ivsc-driver into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ivsc- driver/0~git202212210258.94ecb88b-0ubuntu0.23.10.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ivsc-driver (Ubuntu Mantic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-mantic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2031412 Title: Support mipi camera on Intel Meteor Lake platform Status in HWE Next: New Status in ipu6-drivers package in Ubuntu: Fix Released Status in ivsc-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in ipu6-drivers source package in Jammy: Won't Fix Status in ivsc-driver source package in Jammy: Won't Fix Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in ipu6-drivers source package in Mantic: In Progress Status in ivsc-driver source package in Mantic: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Status in ipu6-drivers source package in Noble: Fix Released Status in ivsc-driver source package in Noble: Fix Released Status in linux source package in Noble: Triaged Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [SRU Justification] == ipu6-driver == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. [Fix] Based on upstream tag https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019, and an additional patch to enable/fix compilation of additional sensor modules. [Test Case] This is verified on MTL Lattice and VSC platforms, as well as previous generations e.g. TGL and ADL. To actually verify the camera framework: ``` # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14 # reboot into the 6.5.0-14.14 kernel $ sudo apt install intel-ipu6-dkms intel-vsc-dkms $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u $ sudo apt install gstreamer1.0-icamera v4l2-relayd ``` In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, and their dependencies, are fetched from the oem-solutions-group PPA. Everything else must come from the mantic archive. And then browse https://webcamtests.com/ for testing. [Where problems could occur] This is a new platform. We've been verifying its functions and features, and are still polishing it. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic and on, and yet the lastest stable driver was verified after Mantic was released, it's being proposed to Noble instead. == ivsc-driver == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. Need both firmware and driver change to probe the hardware correctly. [Fix] 4 commits from the latest trunk branch on upstream repository https://github.com/intel/ivsc-driver. [Test Case] With all other changes in position, Intel VSC driver modules are to be loaded as a soft dependency of some selected camera sensor modules. LJCA modules should be loaded automatically on MTL platforms as well. To actually verify the camera framework: ``` # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14 # reboot into the 6.5.0-14.14
[Kernel-packages] [Bug 2039009] Re: do not ship ZSTD compressed modules in jammy/hwe-6.5 kernels
This bug is awaiting verification that the linux- gcp-6.5/6.5.0-1010.10~22.04.3 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-linux- gcp-6.5' to 'verification-done-jammy-linux-gcp-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-gcp-6.5' to 'verification-failed-jammy-linux-gcp-6.5'. 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 added: kernel-spammed-jammy-linux-gcp-6.5-v2 verification-needed-jammy-linux-gcp-6.5 -- 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/2039009 Title: do not ship ZSTD compressed modules in jammy/hwe-6.5 kernels Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: Providing zstd compressed modules may break user-space scripts/tools/binaries that are relying on the .ko naming schema. The kernel can still support ZSTD compressed modules (via CONFIG_MODULE_COMPRESS_ZSTD), but our shipped kernel modules will be just regular .ko files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039009/+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 2039010] Re: revert support for arbitrary symbol length in modversion in hwe kernels
This bug is awaiting verification that the linux- gcp-6.5/6.5.0-1010.10~22.04.3 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-linux- gcp-6.5' to 'verification-done-jammy-linux-gcp-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-gcp-6.5' to 'verification-failed-jammy-linux-gcp-6.5'. 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 added: kernel-spammed-jammy-linux-gcp-6.5-v2 verification-needed-jammy-linux-gcp-6.5 -- 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/2039010 Title: revert support for arbitrary symbol length in modversion in hwe kernels Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: The following patch may break user-space, providing an actual ABI change: UBUNTU: SAUCE: modpost: support arbitrary symbol length in modversion This is not critical for new releases (also considering that the potential breakage is unlikely to happen, unless some tools/scripts/apps are inspecting modules' internals - likely only kmod tools, that are ok with this change), but for LTS releases it is just safer to prevent adding this change. Keep in mind that this patch is required to enable Rust support in the generic kernel, but it is not required for hwe kernels, because we do not enable Rust support for them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039010/+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 2042546] Re: Include cifs.ko in linux-modules package
removed modules-extra, rebooted, and installed the new kernel for Azure; then rebooted again. modprobe cifs works, and modules-extra is not installed. Marking verification done for Azure. ** Tags removed: verification-needed-jammy-linux-hwe-6.2 ** Tags added: verification-done-jammy-linux-hwe-6.2 -- 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/2042546 Title: Include cifs.ko in linux-modules package Status in linux package in Ubuntu: Invalid Status in linux source package in Lunar: Fix Committed Bug description: SRU Justification: [Impact] Commit: "smb: move client and server files to common directory fs/smb" introduced in 2023.09.04 moved the fs/cifs directory to fs/sb/client. The inclusion list for linux-modules was not updated, it still contains the old path. This means that the cifs.ko module cannot be loaded if only linux-modules package is installed, now being part of linux-modules-extra. For lunar:main this is not a problem because linux-modules-extra is always installed, but for derivatives like aws, azure etc, this module cannot be loaded without explicitly installing linux-modules-extra. [How to reproduce it]: 1. Install the latest azure kernel 6.2.0-1016.16 2. Load cifs module $ modprobe cifs modprobe: FATAL: Module cifs not found in directory /lib/modules/6.2.0-1016-azure If modules-extra is installed, this works. [Fix] Replace fs/cifs/* with fs/smb/client/* in debian./control.d/.inclusiojn-list This is going to be done in s2023.10.02 cycle for derivatives. [Test Plan] 1. Apply the fix to one of the derivative (azure), build a new kernel and install it 2. Load cifs module $ modprobe cifs It should work without installing modules-extra. [Regression potential] Very low, it's a straightforward fix. [Other Info] Sending a patch for every derivative takes time and each derivative will be fixed once this proposal is acked. There is also the possibility to do it via cranky fix, but owners may omit it during security updates and it's hard to enforce it. Plus, it is a one-time change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042546/+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 2042092] Re: CIFS module is not included in 6.2.0-1016
*** This bug is a duplicate of bug 2042546 *** https://bugs.launchpad.net/bugs/2042546 ** This bug has been marked a duplicate of bug 2042546 Include cifs.ko in linux-modules package -- 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/2042092 Title: CIFS module is not included in 6.2.0-1016 Status in linux-azure package in Ubuntu: Confirmed Bug description: Between 6.2.0-1015 and 6.2.0-1016, the CIFS module was moved from fs/cifs/* to fs/smb/client/*, fs/smb/common/* and fs/smb/server/*. The inclusion list (root/debian.azure-6.2/control.d/azure.inclusion-list) was not updated for this change, so the module is not included in the linux-modules-6.2.0-1026-azure package. WORKAROUND: cifs.ko is provided in the linux-modules-extra-azure (as noted in comment #7); a 'sudo apt install linux-modules-extra-azure' will add it in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2042092/+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 2042772] Re: [amdgpu] Display corrupted/freeze
After all updates with kernel 5.15.0-89 generic at logon screen same problem occurs after clicking user name. Following boot in recovery mode System Monitor shows Xorg running instead of Xwayland. -- 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/2042772 Title: [amdgpu] Display corrupted/freeze Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: After latest updates login display is fine but after entering password display changes to black with random full width 1 pixel high white lines that move randomly vertically. Must power off to recover. Boot in recovery mode works OK. Send email if you need more information. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 5 07:09:04 2023 DistUpgraded: 2022-12-21 11:25:42,433 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Dell Wani [Radeon R5/R6/R7 Graphics] [1028:0769] Subsystem: Dell Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 530/535 / 620/625 Mobile] [1028:0769] InstallationDate: Installed on 2018-08-11 (1912 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 5565 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-88-generic root=UUID=54c49f2a-71f4-4c7f-b611-4f0af1922365 ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to jammy on 2022-12-21 (318 days ago) dmi.bios.date: 10/18/2016 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.5 dmi.board.name: 0021CT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.0.5 dmi.modalias: dmi:bvnDellInc.:bvr1.0.5:bd10/18/2016:br5.3:svnDellInc.:pnInspiron5565:pvr1.0.5:rvnDellInc.:rn0021CT:rvrA00:cvnDellInc.:ct10:cvr1.0.5:sku0769: dmi.product.family: Inspiron dmi.product.name: Inspiron 5565 dmi.product.sku: 0769 dmi.product.version: 1.0.5 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042772/+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-raspi/5.4.0.1100.130)
All autopkgtests for the newly accepted linux-meta-raspi (5.4.0.1100.130) for focal have finished running. The following regressions have been reported in tests triggered by the package: adv-17v35x/unknown (armhf) jool/unknown (arm64) mali-midgard/16.0+pristine-4 (armhf) nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (armhf) r8168/unknown (arm64) wireguard-linux-compat/unknown (arm64) xtables-addons/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-raspi [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 1786013] Autopkgtest regression report (linux-meta-gcp-5.15/5.15.0.1048.56~20.04.1)
All autopkgtests for the newly accepted linux-meta-gcp-5.15 (5.15.0.1048.56~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: systemd/245.4-4ubuntu3.22 (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/focal/update_excuses.html#linux-meta-gcp-5.15 [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 1284397] Re: iwlwifi 0000:01:00.0: Microcode SW error detected. Restarting 0x2000000.
Launchpad has imported 4 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=71121. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2014-02-25T01:38:55+00:00 caravena wrote: Open bug in launchpad.net "[ 4497.019702] iwlwifi :01:00.0: Microcode SW error detected. Restarting 0x200. [ 4497.019714] iwlwifi :01:00.0: CSR values: [ 4497.019719] iwlwifi :01:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG) [ 4497.019729] iwlwifi :01:00.0: CSR_HW_IF_CONFIG_REG: 0X00484b00 [ 4497.019738] iwlwifi :01:00.0: CSR_INT_COALESCING: 0Xff40 [ 4497.019746] iwlwifi :01:00.0: CSR_INT: 0X [ 4497.019754] iwlwifi :01:00.0: CSR_INT_MASK: 0X [ 4497.019763] iwlwifi :01:00.0: CSR_FH_INT_STATUS: 0X [ 4497.019771] iwlwifi :01:00.0: CSR_GPIO_IN: 0X003c [ 4497.019778] iwlwifi :01:00.0: CSR_RESET: 0X [ 4497.019787] iwlwifi :01:00.0: CSR_GP_CNTRL: 0X080403c5 [ 4497.019795] iwlwifi :01:00.0: CSR_HW_REV: 0X00b0 [ 4497.019803] iwlwifi :01:00.0: CSR_EEPROM_REG: 0Xcc140ffd [ 4497.019810] iwlwifi :01:00.0: CSR_EEPROM_GP: 0X9801 [ 4497.019818] iwlwifi :01:00.0: CSR_OTP_GP_REG: 0X00030001 [ 4497.019827] iwlwifi :01:00.0: CSR_GIO_REG: 0X00080044 [ 4497.019835] iwlwifi :01:00.0: CSR_GP_UCODE_REG: 0X7027 [ 4497.019842] iwlwifi :01:00.0: CSR_GP_DRIVER_REG: 0X [ 4497.019850] iwlwifi :01:00.0: CSR_UCODE_DRV_GP1: 0X [ 4497.019858] iwlwifi :01:00.0: CSR_UCODE_DRV_GP2: 0X [ 4497.019866] iwlwifi :01:00.0: CSR_LED_REG: 0X0040 [ 4497.019874] iwlwifi :01:00.0: CSR_DRAM_INT_TBL_REG: 0X880c2d84 [ 4497.019882] iwlwifi :01:00.0: CSR_GIO_CHICKEN_BITS: 0X27800200 [ 4497.019889] iwlwifi :01:00.0: CSR_ANA_PLL_CFG: 0X [ 4497.019897] iwlwifi :01:00.0: CSR_HW_REV_WA_REG: 0X0001001a [ 4497.019905] iwlwifi :01:00.0: CSR_DBG_HPET_MEM_REG: 0X [ 4497.019910] iwlwifi :01:00.0: FH register values: [ 4497.019929] iwlwifi :01:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X0bba9700 [ 4497.019946] iwlwifi :01:00.0: FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X00bb9290 [ 4497.019964] iwlwifi :01:00.0: FH_RSCSR_CHNL0_WPTR: 0X0050 [ 4497.019981] iwlwifi :01:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X80801114 [ 4497.01] iwlwifi :01:00.0: FH_MEM_RSSR_SHARED_CTRL_REG: 0X00fc [ 4497.020030] iwlwifi :01:00.0: FH_MEM_RSSR_RX_STATUS_REG: 0X0703 [ 4497.020048] iwlwifi :01:00.0: FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X [ 4497.020066] iwlwifi :01:00.0: FH_TSSR_TX_STATUS_REG: 0X07ff0001 [ 4497.020084] iwlwifi :01:00.0: FH_TSSR_TX_ERROR_REG: 0X [ 4497.020091] iwlwifi :01:00.0: Loaded firmware version: 18.168.6.1 [ 4497.020218] iwlwifi :01:00.0: Start IWL Error Log Dump: [ 4497.020226] iwlwifi :01:00.0: Status: 0x02CC, count: 6 [ 4497.020235] iwlwifi :01:00.0: 0x198A | ADVANCED_SYSASSERT [ 4497.020243] iwlwifi :01:00.0: 0x00015920 | uPc [ 4497.020250] iwlwifi :01:00.0: 0x00015910 | branchlink1 [ 4497.020257] iwlwifi :01:00.0: 0x00015910 | branchlink2 [ 4497.020264] iwlwifi :01:00.0: 0xDBEA | interruptlink1 [ 4497.020277] iwlwifi :01:00.0: 0x | interruptlink2 [ 4497.020281] iwlwifi :01:00.0: 0x0A0D | data1 [ 4497.020284] iwlwifi :01:00.0: 0x0008 | data2 [ 4497.020288] iwlwifi :01:00.0: 0x01DC | line [ 4497.020292] iwlwifi :01:00.0: 0xA00157F5 | beacon time [ 4497.020296] iwlwifi :01:00.0: 0x823E480B | tsf low [ 4497.020299] iwlwifi :01:00.0: 0x0002 | tsf hi [ 4497.020302] iwlwifi :01:00.0: 0x | time gp1 [ 4497.020306] iwlwifi :01:00.0: 0x0B64FC55 | time gp2 [ 4497.020309] iwlwifi :01:00.0: 0x | time gp3 [ 4497.020313] iwlwifi :01:00.0: 0x754312A8 | uCode version [ 4497.020316] iwlwifi :01:00.0: 0x00B0 | hw version [ 4497.020320] iwlwifi :01:00.0: 0x00484B00 | board version [ 4497.020323] iwlwifi :01:00.0: 0x001C | hcmd [ 4497.020327] iwlwifi :01:00.0: 0xAFA63840 | isr0 [ 4497.020331] iwlwifi :01:00.0: 0x1189F800 | isr1 [ 4497.020335] iwlwifi :01:00.0: 0x0E1F | isr2 [ 4497.020339] iwlwifi :01:00.0: 0x0147FCC2 | isr3 [ 4497.020343] iwlwifi :01:00.0: 0x | isr4 [ 4497.020347] iwlwifi :01:00.0: 0x1112 | isr_pref [ 4497.020351] iwlwifi :01:00.0: 0x000260A4 | wait_event [ 4497.020355] iwlwifi :01:00.0: 0x61F6 | l2p_control [ 4497.020359] iwlwifi :01:00.0: 0xA735 | l2p_duration [ 4497.020363] iwlwifi :01:00.0: 0x0003 | l2p_mhvalid [ 4497.020367] iwlwifi :01:00.0: 0x00101040 | l2p_addr_match [ 4497.020372] iwlwifi :01:00.0: 0x0005 | lmpm_pmg_sel [
[Kernel-packages] [Bug 2043841] Re: kernel BUG: io_uring openat triggers audit reference count underflow
** Package changed: linux-azure-6.2 (Ubuntu) => linux (Ubuntu)
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** Changed in: linux (Ubuntu Lunar)
Status: New => In Progress
** Changed in: linux (Ubuntu Lunar)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux (Ubuntu Lunar)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Mantic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Mantic)
Status: New => In Progress
** Changed in: linux (Ubuntu Mantic)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
--
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/2043841
Title:
kernel BUG: io_uring openat triggers audit reference count underflow
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Lunar:
In Progress
Status in linux source package in Mantic:
In Progress
Bug description:
I first encountered a bug in 6.2.0-1012-azure #12~22.04.1-Ubuntu that
occurs during io_uring openat audit processing. I have a kernel patch
that was accepted into the upstream kernel as well as the v6.6,
v6.5.9, and v6.1.60 releases. The bug was first introduced in the
upstream v5.16 kernel.
I do not see the change yet in:
* The Ubuntu-azure-6.2-6.2.0-1017.17_22.04.1 tag in the jammy kernel
repository.
* The Ubuntu-azure-6.5.0-1009.9 tag in the mantic kernel repository.
Can this upstream commit be cherry picked?
The upstream commit is:
03adc61edad49e1bbecfb53f7ea5d78f398fe368
The upstream patch thread is:
https://lore.kernel.org/audit/20231012215518.ga4...@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net/T/#u
The maintainer pull request thread is:
https://lore.kernel.org/lkml/20231019-kampfsport-
metapher-e5211d7be247@brauner
The pre-patch discussion thread is:
https://lore.kernel.org/io-
uring/mw2pr2101mb1033fff044a258f84aeaa584f1...@mw2pr2101mb1033.namprd21.prod.outlook.com/T/#u
The commit log message is:
commit 03adc61edad49e1bbecfb53f7ea5d78f398fe368
Author: Dan Clash
Date: Thu Oct 12 14:55:18 2023 -0700
audit,io_uring: io_uring openat triggers audit reference count
underflow
An io_uring openat operation can update an audit reference count
from multiple threads resulting in the call trace below.
A call to io_uring_submit() with a single openat op with a flag of
IOSQE_ASYNC results in the following reference count updates.
These first part of the system call performs two increments that
do not race.
do_syscall_64()
__do_sys_io_uring_enter()
io_submit_sqes()
io_openat_prep()
__io_openat_prep()
getname()
getname_flags() /* update 1 (increment) */
__audit_getname() /* update 2 (increment) */
The openat op is queued to an io_uring worker thread which starts the
opportunity for a race. The system call exit performs one decrement.
do_syscall_64()
syscall_exit_to_user_mode()
syscall_exit_to_user_mode_prepare()
__audit_syscall_exit()
audit_reset_context()
putname() /* update 3 (decrement) */
The io_uring worker thread performs one increment and two decrements.
These updates can race with the system call decrement.
io_wqe_worker()
io_worker_handle_work()
io_wq_submit_work()
io_issue_sqe()
io_openat()
io_openat2()
do_filp_open()
path_openat()
__audit_inode() /* update 4 (increment) */
putname() /* update 5 (decrement) */
__audit_uring_exit()
audit_reset_context()
putname() /* update 6 (decrement) */
The fix is to change the refcnt member of struct audit_names
from int to atomic_t.
kernel BUG at fs/namei.c:262!
Call Trace:
...
? putname+0x68/0x70
audit_reset_context.part.0.constprop.0+0xe1/0x300
__audit_uring_exit+0xda/0x1c0
io_issue_sqe+0x1f3/0x450
? lock_timer_base+0x3b/0xd0
io_wq_submit_work+0x8d/0x2b0
? __try_to_del_timer_sync+0x67/0xa0
io_worker_handle_work+0x17c/0x2b0
io_wqe_worker+0x10a/0x350
Cc: sta...@vger.kernel.org
Link:
https://lore.kernel.org/lkml/mw2pr2101mb1033fff044a258f84aeaa584f1...@mw2pr2101mb1033.namprd21.prod.outlook.com/
Fixes: 5bd2182d58e9 ("audit,io_uring,io-wq: add some basic audit support
to io_uring")
Signed-off-by: Dan Clash
Link:
[Kernel-packages] [Bug 1848831]
I also have AX200 card with errors as mentioned above, and no wifi interface at startup. I tried solution from @invalidhandle and it worked: I left alone iwlwifi-cc-a0-50.ucode.zst (I don't have version 48) in /lib/firmware and rebooted. Then wifi was ok and I could connect to internet. I tried also with iwlwifi-cc-a0-77.ucode.zst without success (no interface showing up). I'm using kernel 6.6.2-arch1-1. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1848831 Title: Intel WiFi AX200 [8086:08b1] subsystem [8086:4070] firmware loading error resulting in no wifi Status in Gaming Edition: In Progress Status in linux-firmware package in Ubuntu: Confirmed Bug description: Ubuntu 19.10 - stock kernel - Intel AX200 PCI card in a desktop PC uname -a Linux nahuatl 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux The card is detected OK as dmesg shows, however the card's firmware fails immediately after loading (see dmesg output below) and wifi doesn't work at all. Big disappointment since the AX200 chip was supposed to be supported on 19.10. Ubuntu includes two ax200 firmware versions, version 48 loads by default in my system (and fails). I tried version 46 (by renaming the version 48 file) and it failed in the exact same manner $ ls /lib/firmware/iwlwifi-cc-* /lib/firmware/iwlwifi-cc-a0-46.ucode /lib/firmware/iwlwifi-cc-a0-48.ucode The card's Bluetooth functionality is also detected and it works fine. It's just the wifi FW loading what seems broken in ubuntu's 5.3 kernel. $ rfkill list 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no ~$ dmesg | grep iwl [ 12.312443] iwlwifi :01:00.0: enabling device ( -> 0002) [ 12.321098] iwlwifi :01:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17 [ 12.321101] iwlwifi :01:00.0: Found debug destination: EXTERNAL_DRAM [ 12.321102] iwlwifi :01:00.0: Found debug configuration: 0 [ 12.321309] iwlwifi :01:00.0: loaded firmware version 48.4fa0041f.0 op_mode iwlmvm [ 12.390389] iwlwifi :01:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 [ 12.400654] iwlwifi :01:00.0: Applying debug destination EXTERNAL_DRAM [ 12.400893] iwlwifi :01:00.0: Allocated 0x0040 bytes for firmware monitor. [ 13.414781] iwlwifi :01:00.0: Collecting data: trigger 15 fired. [ 13.414908] iwlwifi :01:00.0: Start IWL Error Log Dump: [ 13.414910] iwlwifi :01:00.0: Status: 0x, count: 6 [ 13.414911] iwlwifi :01:00.0: Loaded firmware version: 48.4fa0041f.0 [ 13.414912] iwlwifi :01:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL [ 13.414913] iwlwifi :01:00.0: 0x002022F0 | trm_hw_status0 [ 13.414913] iwlwifi :01:00.0: 0x | trm_hw_status1 [ 13.414914] iwlwifi :01:00.0: 0x004F8E3C | branchlink2 [ 13.414915] iwlwifi :01:00.0: 0x004E4FF4 | interruptlink1 [ 13.414915] iwlwifi :01:00.0: 0x004E4FF4 | interruptlink2 [ 13.414916] iwlwifi :01:00.0: 0x004F3DB0 | data1 [ 13.414917] iwlwifi :01:00.0: 0x1000 | data2 [ 13.414917] iwlwifi :01:00.0: 0xF000 | data3 [ 13.414918] iwlwifi :01:00.0: 0x | beacon time [ 13.414919] iwlwifi :01:00.0: 0x795F | tsf low [ 13.414919] iwlwifi :01:00.0: 0x | tsf hi [ 13.414920] iwlwifi :01:00.0: 0x | time gp1 [ 13.414921] iwlwifi :01:00.0: 0xDFD5 | time gp2 [ 13.414921] iwlwifi :01:00.0: 0x0001 | uCode revision type [ 13.414922] iwlwifi :01:00.0: 0x0030 | uCode version major [ 13.414923] iwlwifi :01:00.0: 0x4FA0041F | uCode version minor [ 13.414923] iwlwifi :01:00.0: 0x0340 | hw version [ 13.414924] iwlwifi :01:00.0: 0x18C89000 | board version [ 13.414925] iwlwifi :01:00.0: 0x8002FF03 | hcmd [ 13.414925] iwlwifi :01:00.0: 0x0002 | isr0 [ 13.414926] iwlwifi :01:00.0: 0x | isr1 [ 13.414926] iwlwifi :01:00.0: 0x08F2 | isr2 [ 13.414927] iwlwifi :01:00.0: 0x00CC | isr3 [ 13.414928] iwlwifi :01:00.0: 0x | isr4 [ 13.414928] iwlwifi :01:00.0: 0x | last cmd Id [ 13.414929] iwlwifi :01:00.0: 0x004F3DB0 | wait_event [ 13.414930] iwlwifi :01:00.0: 0x | l2p_control [ 13.414930] iwlwifi :01:00.0: 0x0020 | l2p_duration [ 13.414931] iwlwifi :01:00.0: 0x | l2p_mhvalid [ 13.414932] iwlwifi :01:00.0: 0x | l2p_addr_match [ 13.414932] iwlwifi :01:00.0: 0x0009 | lmpm_pmg_sel [ 13.414933] iwlwifi :01:00.0: 0x | timestamp [ 13.414934] iwlwifi :01:00.0: 0xF81C | flow_handler [ 13.414974] iwlwifi :01:00.0: Start IWL Error Log Dump: [ 13.414975]
[Kernel-packages] [Bug 2043905]
FWIW, it's a known issue that most likely still happens with mailine; for details see this msg and the two replies to it: https://lore.kernel.org/all/20231108051638.GA194133@workstation.local/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2043905 Title: VT6307 IEEE1394 card causes reboot loop Status in Linux: In Progress Status in linux package in Ubuntu: New Bug description: used the live USB for Kubuntu and UbuntuStudio 23.10 as well as upgraded to Mantic 6.5.0-10-generic from a Lunar 6.2.0-36 that works... all of the 6.5.0 64 bit kernel versions do a reboot loop prior to the splash screen display. Processor is an AMD Ryzen 5600X, MSI MPG B550 GAMING PLUS Motherboard with 64 gig 3200 ddr4 ram. AMD Radeon RX6600 graphics... latest BIOS firmware is installed, "fwupdmrg refresh --force && fwupdmrg update" in root terminal reports no available updates. in the advanced options of grub I can boot into mantic with the lunar 6.2.0-36 kernel. Cell phone video capture of the bad boot included... Further testing found that a Mantic beta July 3rd build will boot (6.3 kernel) booting to the current live Kubuntu USB with the 6.5.0-9 kernel and removing hardware 1 piece at a time then replacing if the loop occurred found that as soon as a VT6307 PCIe card is removed the 6.5.0-9 and 6.5.0-10 kernels will boot properly. as soon as the card is reinstalled the panic reboot loop starts up again... If there was a log generated from the loop I have been unable to find one in the /var/log directory... I have been unable to get kdump to work... To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2043905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040300] Re: Azure: Improve SQL DB latency
** Tags removed: verification-needed-jammy-linux-azure verification-needed-lunar-linux-azure verification-needed-mantic-linux-azure ** Tags added: verification-done-jammy-linux-azure verification-done-lunar-linux-azure verification-done-mantic-linux-azure -- 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/2040300 Title: Azure: Improve SQL DB latency Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Lunar: Fix Committed Status in linux-azure source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] TCP pingpong threshold is 1 by default. But some applications, like SQL DB may prefer a higher pingpong threshold to activate delayed acks in quick ack mode for better performance. There is no single value that fits all applications. Add net.ipv4.tcp_pingpong_thresh sysctl tunable, so it can be tuned for optimal performance based on the application needs. [Test Case] Microsoft tested [Regression Potential] Should be zero since default behavior is unchanged. [Other Info] SF: #00357415 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2040300/+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 2008583] Re: VMware nested under KVM stopped working on 5.19 kernel on Ryzen: Invalid VMCB.
Can confirm, bug occurs with my setup too: Host: Centos 9 Stream (5.14.0-352.el9.x86_64) Hypervisor: KVM (Openstack) VM: ESXi 7.0u3 Patching the commit @lindt found, and recompiling a custom kernel allowed me to start a VM in an ESXi VM nested in Openstack. Be aware I needed to delete the previously crashing VM in ESXI and create a new one. Failing to do so resulted in ESXi crashing completely and restarting. Can provide additional logs or data if needed. -- 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/2008583 Title: VMware nested under KVM stopped working on 5.19 kernel on Ryzen: Invalid VMCB. Status in linux package in Ubuntu: Confirmed Bug description: My setup: Host: Ubuntu Linux 22.04.1, kernel 5.15, Ryzen 5900x Hypervisor: KVM Windows VM with VMware Workstation 16 Running nested VMs in VMware works ok. It fails if Linux host kernel is updated to 5.19 (22.04.2) with MONITOR PANIC: Invalid VMCB. VMware Workstation unrecoverable error: (vcpu-0) vcpu-0:Invalid VMCB. If I update to Workstation 17 it fails with 2023-02-24T15:21:35.112Z In(05) vmx The following features are required for SVM support in VMware Workstation; however, these features are not available on this host: 2023-02-24T15:21:35.112Z In(05) vmxFlush by ASID. This host supports AMD-V, but the AMD-V implementation is incompatible with VMware Workstation. VMware Workstation does not support the user level monitor on this host. Module 'MonitorMode' power on failed. The same VM works ok on 5.19 kernel on my Intel PC. So it has to do with updated Linux kernel and AMD virtualization and VMware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008583/+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 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build
This bug prevents successful installation of any other package, so I think its importance should be upgraded. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2044630 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+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 2044657] Re: zfs block cloning file system corruption
FreeBSD has released an official advisory for the issue today: https://lists.freebsd.org/archives/freebsd- stable/2023-November/001726.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2044657 Title: zfs block cloning file system corruption Status in zfs-linux package in Ubuntu: Confirmed Bug description: OpenZFS 2.2 reportedly has a bug where block cloning might lead to file system corruption and data loss. This was fixed in OpenZFS 2.2.1. Original bug report: https://github.com/openzfs/zfs/issues/15526 and 2.2.1 release notes: https://github.com/openzfs/zfs/releases/tag/zfs-2.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+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 2042999] Re: BT/WiFi coex stability issue on RTL8851BE/RTL8852BE
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-firmware (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2042999
Title:
BT/WiFi coex stability issue on RTL8851BE/RTL8852BE
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Confirmed
Status in linux-firmware source package in Jammy:
Fix Released
Status in linux-firmware source package in Lunar:
Fix Released
Status in linux-firmware source package in Mantic:
Fix Released
Bug description:
[SRU Justifcation]
[Impact]
On platforms with RTL8851BE/RTL8852BE, bluetooth mouse/keyboard may not work
smoothly with WiFi connection activated.
[Fix]
Proposed firmware upstreamed as:
* 2afd1423e476 ("rtw89: 8852b: update fw to v0.29.29.5")
* 7a916315fb28 ("rtw89: 8852b: update fw to v0.29.29.4")
* 02df6e4f03c0 ("rtw89: 8851b: update fw to v0.29.41.3")
[Test Case]
1. Install Ubuntu 22.04 on SUT with RTL8851BE / 8852BE Wlan card
2. Connected BT KB/MS, and then connected WIFI, select an AP to connect
3. Check BT mouse/keyboard, mouse movement, keyboard key pressing not respond
smoothly.
[Where problems could occur]
This updates opaque firmware blobs, so anything could happen. With
verifications
from multiparties, it improves the stability and no other problem found so
far.
[Other Info]
On Lunar, we don't have RTL8851BE enabled, so the related commits are omitted.
On Mantic and oem-6.5/jammy, we have both.
== original bug report ==
1.Install Ubuntu 22.04 on SUT with RTL8851BE / 8852BE Wlan card
2.Connected BT KB/MS,and then connected WIFI, select an AP to connect
3.Check BT mouse/keyboard, mouse movement, keyboard key pressing not respond
smoothly.
Proposed firmware upstreamed as:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2afd1423e4765eb691711ea5e78a19853cb2f6eb
("rtw89: 8852b: update fw to v0.29.29.5")
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=7a916315fb2889aa4b89a71b4eb0b18e5d6153a9
("rtw89: 8852b: update fw to v0.29.29.4")
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=02df6e4f03c08fe95c8967a69b86d2c1165400d6
("rtw89: 8851b: update fw to v0.29.41.3")
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042999/+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 2044589] Re: [Ubuntu 24.04 LTS] mpi3mr: Add support for SAS5116 controller and include critical fixes
** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Noble) 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/2044589 Title: [Ubuntu 24.04 LTS] mpi3mr: Add support for SAS5116 controller and include critical fixes Status in linux package in Ubuntu: Confirmed Status in linux source package in Noble: Confirmed Bug description: This request is to add support for SAS5116 controller and few critical bug-fixes in Ubuntu 24.04 LTS. Below is the list of upstream commits that adds support for SAS5116: b4d94164ff32 scsi: mpi3mr: driver version upgrade to 8.5.0.0.50 1193a89d2b6d scsi: mpi3mr: Add support for status reply descriptor cb5b60894602 scsi: mpi3mr: Increase maximum number of PHYs to 64 from 32 c9260ff28ee5 scsi: mpi3mr: Add PCI checks where SAS5116 diverges from SAS4116 6fa21eab82be scsi: mpi3mr: Add support for SAS5116 PCI IDs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044589/+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-raspi/5.4.0.1099.129)
All autopkgtests for the newly accepted linux-meta-raspi (5.4.0.1099.129) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (armhf) openafs/unknown (arm64) openrazer/unknown (arm64) systemd/unknown (arm64) west-chamber/unknown (arm64) wireguard/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-raspi [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 2042677] Re: [UBUNTU 23.04] PKCS#11 Applications fail to find libopencryptoki.so library due to missing /etc/ld.so.conf.d entry.
Well, if I'm not mistaken this was discussed in LP#2022088, comment #4: https://bugs.launchpad.net/ubuntu/+source/opencryptoki/+bug/2022088/comments/4 And based on this, the quilt patch debian/patches/03-dlopen-soname.patch got expanded. How does your 'ec_tests -slot 0' output look like? My attempt: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 23.04 Release:23.04 Codename: lunar $ apt-cache policy opencryptoki libopencryptoki0 libopencryptoki-dev opencryptoki: Installed: 3.20.0+dfsg-0ubuntu1.1 Candidate: 3.20.0+dfsg-0ubuntu1.1 Version table: *** 3.20.0+dfsg-0ubuntu1.1 500 500 http://ports.ubuntu.com/ubuntu-ports lunar-updates/universe s390x Packages 100 /var/lib/dpkg/status 3.20.0+dfsg-0ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/universe s390x Packages libopencryptoki0: Installed: 3.20.0+dfsg-0ubuntu1.1 Candidate: 3.20.0+dfsg-0ubuntu1.1 Version table: *** 3.20.0+dfsg-0ubuntu1.1 500 500 http://ports.ubuntu.com/ubuntu-ports lunar-updates/universe s390x Packages 100 /var/lib/dpkg/status 3.20.0+dfsg-0ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/universe s390x Packages libopencryptoki-dev: Installed: 3.20.0+dfsg-0ubuntu1.1 Candidate: 3.20.0+dfsg-0ubuntu1.1 Version table: *** 3.20.0+dfsg-0ubuntu1.1 500 500 http://ports.ubuntu.com/ubuntu-ports lunar-updates/universe s390x Packages 100 /var/lib/dpkg/status 3.20.0+dfsg-0ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/universe s390x Packages # sudo vi /etc/apt/sources.list # enable deb-src for universe and universe-updates $ sudo apt update && sudo apt full-upgrade $ sudo apt-get --yes build-dep opencryptoki $ sudo apt --yes install automake libtool m4 autoconf flex bison libcap-dev expect # libudev-dev $ git clone https://github.com/opencryptoki/opencryptoki $ cd opencryptoki $ sudo -i $ ./bootstrap.sh $ ./configure --enable-testcases $ make $ sudo ./testcases/crypto/ec_tests -slot 0 Using slot #0... With option: no_init: 0 -- * TESTCASE run_GenerateECCKeyPairSignVerify BEGIN Starting ECC generate key pair with pkey=0 ... * TESTCASE run_GenerateECCKeyPairSignVerify ERROR (testcases/crypto/ec_func.c:1538)) C_OpenSession() rc = CKR_TOKEN_NOT_PRESENT -- * TESTCASE run_ImportECCKeyPairSignVerify BEGIN Starting ECC import key pair with pkey=0 ... * TESTCASE run_ImportECCKeyPairSignVerify ERROR (testcases/crypto/ec_func.c:1684)) C_OpenSession() rc = CKR_TOKEN_NOT_PRESENT -- * TESTCASE run_TransferECCKeyPairSignVerify BEGIN Starting ECC transfer key pair with pkey=0 ... * TESTCASE run_TransferECCKeyPairSignVerify ERROR (testcases/crypto/ec_func.c:1854)) C_OpenSession() rc = CKR_TOKEN_NOT_PRESENT -- * TESTCASE run_DeriveECDHKey BEGIN starting run_DeriveECDHKey with pkey=0 ... * TESTCASE run_DeriveECDHKey ERROR (testcases/crypto/ec_func.c:391)) C_OpenSession() rc = CKR_TOKEN_NOT_PRESENT -- * TESTCASE run_DeriveECDHKeyKAT BEGIN starting run_DeriveECDHKeyKAT with pkey=0 ... * TESTCASE run_DeriveECDHKeyKAT ERROR (testcases/crypto/ec_func.c:925)) C_OpenSession() rc = CKR_TOKEN_NOT_PRESENT -- * TESTSUITE run_DeriveBTC BEGIN starting run_DeriveBTC with pkey=0 ... * TESTCASE run_DeriveBTC ERROR (testcases/crypto/ec_func.c:2492)) C_OpenSession() rc = CKR_TOKEN_NOT_PRESENT Total=0, Ran=0, Passed=0, Failed=0, Skipped=0, Errors=6 (total elapsed time 0s 196us) Well, errors, but no obvious crash. syslog shows: 2023-11-27T15:03:07.490186+00:00 hwe0002 ec_tests: usr/lib/cca_stdll/cca_specific.c token_specific_init: Error loading library: 'libcsulcca.so' [libcsulcca.so: cannot open shared object file: No such file or directory] 2023-11-27T15:03:08.046466+00:00 hwe0002 ec_tests: usr/lib/ep11_stdll/ep11_specific.c ep11_load_host_lib: Error loading shared library 'libep11.so[.4][.3|.2|.1]' [libep11.so: cannot open shared object file: No such file or directory] But that is because I have no libcsulcca.so, nor libep11 installed ... Installing csulcca gets me along the first msg. But right now I don't have a new enough libep11 - the latest I have still wants libssl1.0.0 or libssl1.1. What is the exact output that you get? Where do you see the error - in the terminal where you call ec_tests or in the logs? (Btw. same output for mantic and jammy). ** Package changed: linux (Ubuntu) => opencryptoki (Ubuntu) ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) -- 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/2042677 Title: [UBUNTU 23.04] PKCS#11 Applications fail to find libopencryptoki.so library due to missing /etc/ld.so.conf.d entry. Status in Ubuntu on IBM z Systems: New Status in
[Kernel-packages] [Bug 1993566] Re: dbus-daemon: Unknown group "power" in message bus configuration file
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: thermald (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1993566 Title: dbus-daemon: Unknown group "power" in message bus configuration file Status in thermald package in Ubuntu: Confirmed Bug description: Hi, I see the following error message in the logs: # journalctl | grep 'Unknown group "power"' Oct 19 18:41:35 jophur dbus-daemon[630]: dbus[630]: Unknown group "power" in message bus configuration file Oct 19 18:46:35 jophur dbus-daemon[630]: Unknown group "power" in message bus configuration file Oct 19 18:46:36 jophur dbus-daemon[630]: Unknown group "power" in message bus configuration file The problem comes from this file: # grep -r power /etc/dbus-1/ /etc/dbus-1/system.d/org.freedesktop.thermald.conf:
[Kernel-packages] [Bug 2032628] Re: Kernel 6.2.0-26 does not boot
The newest update to kernel 6.2.0-37 solved the issue. ** 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/2032628 Title: Kernel 6.2.0-26 does not boot Status in linux package in Ubuntu: Fix Released Bug description: My Ubuntu 22.04.3 LTS auto updated from kernel 5.19.0-46-generic to 6.2.0-26-generic. The new kernel does not boot. It stops right after the following warnings: /dev/nvme0n1p7: clean etc. dell_smbios: Unable to run on non-Dell system usb 1-7: 3:3: cannot set freq 24000 to ep 0x82 The PC is a Dell Alienware Aurora R13. If I let it start in recovery mode and then resume boot, it works, but among other it does not recognize two screens. This "ubuntu-bug" was done after booting in this way. The old kernel boots fine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Aug 22 11:17:48 2023 InstallationDate: Installed on 2023-04-04 (139 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032628/+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 1989983] Re: kinetic: apply new apparmor and LSM stacking patch set
This bug is awaiting verification that the linux-lowlatency- hwe-6.5/6.5.0-14.14.1~22.04.1 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-linux- lowlatency-hwe-6.5' to 'verification-done-jammy-linux-lowlatency- hwe-6.5'. If the problem still exists, change the tag 'verification- needed-jammy-linux-lowlatency-hwe-6.5' to 'verification-failed-jammy- linux-lowlatency-hwe-6.5'. 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 added: kernel-spammed-jammy-linux-lowlatency-hwe-6.5-v2 verification-needed-jammy-linux-lowlatency-hwe-6.5 -- 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/1989983 Title: kinetic: apply new apparmor and LSM stacking patch set Status in linux package in Ubuntu: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: [Impact] Align with the latest apparmor and LSM stacking versions. To do so we need to: - revert sauce to get back to upstream apparmor, and drop old LSM stacking - pull in needed patches from upstream 6.0 - pull in needed patches from apparmor-next 6.1 This is required to properly support apparmor in Ubuntu. [Test case] We test apparmor in our RT suite. [Regression potential] We may see breakage in the apparmor tests after applying this patch set. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017903] Re: LSM stacking and AppArmor for 6.2: additional fixes
This bug is awaiting verification that the linux-lowlatency- hwe-6.5/6.5.0-14.14.1~22.04.1 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-linux- lowlatency-hwe-6.5' to 'verification-done-jammy-linux-lowlatency- hwe-6.5'. If the problem still exists, change the tag 'verification- needed-jammy-linux-lowlatency-hwe-6.5' to 'verification-failed-jammy- linux-lowlatency-hwe-6.5'. 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 added: kernel-spammed-jammy-linux-lowlatency-hwe-6.5-v2 verification-needed-jammy-linux-lowlatency-hwe-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2017903 Title: LSM stacking and AppArmor for 6.2: additional fixes Status in linux package in Ubuntu: Fix Released Status in linux source package in Lunar: Fix Released Bug description: [Impact] We maintain custom LSM stacking and AppArmor SAUCE patches in our kernel to provide additional features that are not available in the upstream AppArmor. We have experienced occasional bugs in the lunar kernel (specifically with the environ.sh test) that can lead to system crashes / failures (such as potential NULL pointer dereference). [Test case] Run AppArmor autopkgtest / qa-regression-testing. [Fix] Apply the following additional fixes provided by AppArmor upstream maintainer: UBUNTU: SAUCE: apparmor: fix policy_compat perms remap for file dfa UBUNTU: SAUCE: apparmor: fix profile verification and enable it UBUNTU: SAUCE: apparmor: fix: add missing failure check in compute_xmatch_perms UBUNTU: SAUCE: apparmor: fix: kzalloc perms tables for shared dfas [Regression potential] Additional fixes are touching only AppArmor specific code, so we may experience regressions (bugs / behavior change) only in apparmor by applying them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017903/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)
This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.1~22.04.1 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-linux-
lowlatency-hwe-6.5' to 'verification-done-jammy-linux-lowlatency-
hwe-6.5'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-lowlatency-hwe-6.5' to 'verification-failed-jammy-
linux-lowlatency-hwe-6.5'.
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 added: kernel-spammed-jammy-linux-lowlatency-hwe-6.5-v2
verification-needed-jammy-linux-lowlatency-hwe-6.5
--
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/2016908
Title:
udev fails to make prctl() syscall with apparmor=0 (as used by maas by
default)
Status in AppArmor:
Fix Released
Status in MAAS:
Fix Released
Status in maas-images:
Invalid
Status in apparmor package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Invalid
Status in apparmor source package in Lunar:
Invalid
Status in linux source package in Lunar:
Fix Released
Status in systemd source package in Lunar:
Invalid
Bug description:
I'm assuming the image being used for these deploys is 20230417 or
20230417.1 based on the fact that I saw a 6.2 kernel being used which
I don't believe was part of the 20230319 serial. I don't have access
to the maas server, so I can't directly check any log files.
MAAS Version: 3.3.2
Here's where the serial log indicates it can't download the squashfs. The
full log is attached as scobee-lunar-no-squashfs.log (there are some other
console message intermixed):
no search or nameservers found in /run/net-BOOTIF.conf /run/net-*.conf
/run/net6
-*.conf
::
root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.04/lunar/candi
date/squa[ 206.804704] Btrfs loaded, crc32c=crc32c-generic, zoned=yes,
fsverity
=yes
shfs
:: mount_squash downloading
http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.0
4/lunar/candidate/squashfs to /root.tmp.img
Connecting to 10.229.32.21:5248 (10.229.32.21:5248)
wget: can't connect to remote host (10.229.32.21): Network is unreachable
:: mount -t squashfs -o loop '/root.tmp.img' '/root.tmp'
mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory
done.
Still gathering logs and info and will update as I go.
Kernel Bug / Apparmor
reproducer
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-kernel
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-initrd
$ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd
./boot-initrd -append 'console=ttyS0 break=modules apparmor=0'
#start the VM
Starting systemd-udevd version 252.5-2ubuntu3
Spawning shell within the initramfs
BusyBox v1.35.0 (Ubuntu 1:1.35.0-4ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) udevadm info --export-db
Failed to set death signal: Invalid argument
Observe that udevadm fails to setup death signal, with in systemd code
is this
https://github.com/systemd/systemd/blob/08c2f9c626e0f0052d505b1b7e52f335c0fbfa1d/src/basic/process-
util.c#L1252
if (flags & (FORK_DEATHSIG|FORK_DEATHSIG_SIGINT))
if (prctl(PR_SET_PDEATHSIG, (flags & FORK_DEATHSIG_SIGINT) ?
SIGINT : SIGTERM) < 0) {
log_full_errno(prio, errno, "Failed to set death
signal: %m");
_exit(EXIT_FAILURE);
}
workaround set kernel commandline to `apparmor=1`
MAAS bug
Why is maas setting `apparmor=0` ? Ubuntu shouldn't be used without apparmor.
Even for deployment and commisioning.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/2016908/+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 2028253] Re: update apparmor and LSM stacking patch set
This bug is awaiting verification that the linux-lowlatency- hwe-6.5/6.5.0-14.14.1~22.04.1 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-linux- lowlatency-hwe-6.5' to 'verification-done-jammy-linux-lowlatency- hwe-6.5'. If the problem still exists, change the tag 'verification- needed-jammy-linux-lowlatency-hwe-6.5' to 'verification-failed-jammy- linux-lowlatency-hwe-6.5'. 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 added: kernel-spammed-jammy-linux-lowlatency-hwe-6.5-v2 verification-needed-jammy-linux-lowlatency-hwe-6.5 -- 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/2028253 Title: update apparmor and LSM stacking patch set Status in linux package in Ubuntu: Fix Released Status in linux source package in Mantic: Fix Released Bug description: [Impact] Provide an updated patch set for apparmor / LSM stacking with all the custom features that we need in the Ubuntu kernel. This patch set is required to provide the proper confinement with snaps and other Ubuntu-specific security features. [Fix] Apply the latest updated patch set from: https://gitlab.com/jjohansen/apparmor-kernel [Test case] Run the apparmor test case suite. [Regression potential] This patch set introduces significant non-upstream changes to the security layer, so we may expect generic regressions in the kernel, especially running applications that are stressing the security layer (such as systemd, snapd, lxd, etc.). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028253/+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 2038567] Re: Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature
This bug is awaiting verification that the linux-lowlatency- hwe-6.5/6.5.0-14.14.1~22.04.1 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-linux- lowlatency-hwe-6.5' to 'verification-done-jammy-linux-lowlatency- hwe-6.5'. If the problem still exists, change the tag 'verification- needed-jammy-linux-lowlatency-hwe-6.5' to 'verification-failed-jammy- linux-lowlatency-hwe-6.5'. 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 added: kernel-spammed-jammy-linux-lowlatency-hwe-6.5-v2 verification-needed-jammy-linux-lowlatency-hwe-6.5 -- 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/2038567 Title: Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature Status in Release Notes for Ubuntu: New Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Triaged Status in snapd package in Ubuntu: Confirmed Bug description: Following upgrade to 6.5.0-7 kernel in mantic cloud images we are seeing a regression in our cloud image tests. The test runs the following: ``` lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait ``` The `lxc exec mantic -- cloud-init status --wait` times out after 240s and will fail our test as a result. I have been able to replicate in a local VM ``` wget http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img wget --output-document=launch-qcow2-image-qemu.sh https://gist.githubusercontent.com/philroche/14c241c086a5730481e24178b654268f/raw/7af95cd4dfc8e1d0600e6118803d2c866765714e/gistfile1.txt chmod +x launch-qcow2-image-qemu.sh ./launch-qcow2-image-qemu.sh --password passw0rd --image ./mantic-server-cloudimg-amd64.img cat < "./reproducer.sh" #!/bin/bash -eux lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait EOF chmod +x ./reproducer.sh sshpass -p passw0rd scp -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -P ./reproducer.sh ubuntu@127.0.0.1:~/ sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get update sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get upgrade --assume-yes sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 ./reproducer.sh ``` The issue is not present with the 6.5.0-5 kernel and the issue is present regardless of the container launched. I tried the jammy container to test this. From my test VM ``` ubuntu@cloudimg:~$ uname --all Linux cloudimg 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 29 09:14:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@cloudimg:~$ uname --kernel-release 6.5.0-7-generic ``` This is a regression in our test that will block 23.10 cloud image release next week. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038567/+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 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."
Hello Kellen, or anyone else affected,
Accepted makedumpfile into focal-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.7-1ubuntu2.5 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: makedumpfile (Ubuntu Focal)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1970672
Title:
makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid
pmd_pte."
Status in makedumpfile package in Ubuntu:
Fix Released
Status in makedumpfile source package in Focal:
Fix Committed
Bug description:
[Impact]
* On Focal with an HWE (>=5.12) kernel, makedumpfile can sometimes fail with
"__vtop4_x86_64: Can't get a valid pmd_pte."
* makedumpfile falls back to cp for the dump, resulting in extremely
large vmcores. This can impact both collection and analysis due to
lack of space for the resulting vmcore.
* This is fixed in upstream commit present in versions 1.7.0 and 1.7.1:
https://github.com/makedumpfile/makedumpfile/commit/646456862df8926ba10dd7330abf3bf0f887e1b6
commit 646456862df8926ba10dd7330abf3bf0f887e1b6
Author: Kazuhito Hagio
Date: Wed May 26 14:31:26 2021 +0900
[PATCH] Increase SECTION_MAP_LAST_BIT to 5
* Required for kernel 5.12
Kernel commit 1f90a3477df3 ("mm: teach pfn_to_online_page() about
ZONE_DEVICE section collisions") added a section flag
(SECTION_TAINT_ZONE_DEVICE) and causes makedumpfile an error on
some machines like this:
__vtop4_x86_64: Can't get a valid pmd_pte.
readmem: Can't convert a virtual address(e2bdc200) to physical
address.
readmem: type_addr: 0, addr:e2bdc200, size:32768
__exclude_unnecessary_pages: Can't read the buffer of struct page.
create_2nd_bitmap: Can't exclude unnecessary pages.
Increase SECTION_MAP_LAST_BIT to 5 to fix this. The bit had not
been used until the change, so we can just increase the value.
Signed-off-by: Kazuhito Hagio
[Test Plan]
* Confirm that makedumpfile works as expected by triggering a kdump.
* Confirm that the patched makedumpfile works as expected on a system
known to experience the issue.
* Confirm that the patched makedumpfile is able to work with a cp-
generated known affected vmcore to compress it. The unpatched version
fails.
[Where problems could occur]
* This change could adversely affect the collection/compression of
vmcores during a kdump situation resulting in fallback to cp.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1970672/+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 2044722] Re: Enabling fips-preview on Jammy AWS fails with: Depends: linux-aws-fips (>= 5.15.0.1042.43) but it is not installable
** Tags removed: need-amd64-retrace
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2044722
Title:
Enabling fips-preview on Jammy AWS fails with: Depends: linux-aws-fips
(>= 5.15.0.1042.43) but it is not installable
Status in linux-aws package in Ubuntu:
New
Bug description:
I'm testing the fips-review packages on AWS for Jammy. That fails
with:
Unexpected APT error.
Failed running command 'apt-get install --assume-yes --allow-downgrades -o
Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold"
ubuntu-aws-fips' [exit(100)]. Message: E: Unable to correct problems, you have
held broken packages.
Steps to reproduce:
1) aws ec2 run-instances --image-id
resolve:ssm:/aws/service/canonical/ubuntu/server/22.04/stable/current/amd64/hvm/ebs-gp2/ami-id
--instance-type m6a.large --key-name toabctl
2) ssh into the instance
3) ua attach $MY_UA_TOKEN
4) ua enable fips-preview # (answer with yes)
The result is:
# ua enable fips-preview
One moment, checking your subscription first
FIPS Preview cannot be enabled with Livepatch.
Disable Livepatch and proceed to enable FIPS Preview? (y/N) y
Disabling incompatible service: Livepatch
This will install crypto packages that have been submitted to NIST for review
but do not have FIPS certification yet. Use this for early access to the FIPS
modules.
Please note that the Livepatch service will be unavailable after
this operation.
Warning: This action can take some time and cannot be undone.
Are you sure? (y/N) y
Updating FIPS Preview package lists
Installing FIPS Preview packages
Updating standard Ubuntu package lists
Could not enable FIPS Preview.
Updating package lists
Unexpected APT error.
Failed running command 'apt-get install --assume-yes --allow-downgrades -o
Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold"
ubuntu-aws-fips' [exit(100)]. Message: E: Unable to correct problems, you have
held broken packages.
See /var/log/ubuntu-advantage.log
From that log:
["2023-11-27T09:58:33.581", "DEBUG", "ubuntupro.system", "subp", 714, "Failed
running command 'apt-get install --assume-yes --allow-downgrades -o
Dpkg::Options::=\"--force-confdef\" -o Dpkg::Options::=\"--force-confold\"
ubuntu-aws-fips' [exit(100)]. Mes
sage: E: Unable to correct problems, you have held broken packages.\n", {}]
["2023-11-27T09:58:33.581", "WARNING", "ubuntupro.system", "subp", 715,
"Stderr: E: Unable to correct problems, you have held broken
packages.\n\nStdout: Reading package lists...\nBuilding dependency
tree...\nReading state information...\nSome packages c
ould not be installed. This may mean that you have\nrequested an impossible
situation or if you are using the unstable\ndistribution that some required
packages have not yet been created\nor been moved out of Incoming.\nThe
following information may help
to resolve the situation:\n\nThe following packages have unmet
dependencies:\n ubuntu-aws-fips : Depends: linux-aws-fips (>= 5.15.0.1042.43)
but it is not installable\n", {}]
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-advantage-tools 30~22.04
ProcVersionSignature: Ubuntu 6.2.0-1016.16~22.04.1-aws 6.2.16
Uname: Linux 6.2.0-1016-aws x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudID: aws
CloudName: aws
CloudPlatform: ec2
CloudRegion: eu-central-1
CloudSubPlatform: metadata (http://169.254.169.254)
Date: Mon Nov 27 09:59:57 2023
Ec2AMI: ami-097610d2a71255e7d
Ec2AMIManifest: (unknown)
Ec2Architecture: x86_64
Ec2AvailabilityZone: eu-central-1a
Ec2Imageid: ami-097610d2a71255e7d
Ec2InstanceType: m6a.large
Ec2Instancetype: m6a.large
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
Ec2Region: eu-central-1
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-advantage-tools
UpgradeStatus: No upgrade log present (probably fresh install)
cloud-id.txt: aws
livepatch-status.txt-error:
Failed running command '/snap/bin/canonical-livepatch status' [exit(1)].
Message: Machine is not enabled. Please run 'sudo canonical-livepatch enable'
with the
token obtained from https://ubuntu.com/livepatch.
pro-journal.txt:
Nov 27 09:57:07.273351 ip-172-31-20-161 systemd[1]: Condition check resulted
in Ubuntu Pro reboot cmds being skipped.
Nov 27 09:57:13.549831 ip-172-31-20-161 systemd[1]: Condition check resulted
in Ubuntu Pro Background Auto Attach being skipped.
uaclient.conf:
contract_url: https://contracts.canonical.com
log_level: debug
Note: there is no hold package:
# apt-mark showhold
root@ip-172-31-20-161:~#
To manage notifications about this bug go to:
[Kernel-packages] [Bug 1215411] Re: libcpupower.so is not installed from linux-tools
I'm looking at this on +1, and there don't seem to be an obvious forward. Debian has their own SONAME versioning for when the kernel package breaks libcpupower's ABI, but we only have per-kernel-versioned packages. * Do we want to provide an unversioned linux-tools-dev with a similar ABI-breakage SONAME versioning? * Do we want to patch these packages (if possible) to not depend on libcpupower? * Or if no one seems to mind (as it seems from the age of this), how about blocklisting the packages depending on libcpupower-dev from 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/1215411 Title: libcpupower.so is not installed from linux-tools Status in cpufreqd package in Ubuntu: Confirmed Status in gkrellm2-cpufreq package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in opa-ff package in Ubuntu: New Bug description: The patch for bug 1158668 installs cpupower_$(abi_version) command- line tool as well as libcpupower.so.$(abi_version). This isn't particularly suitable for projects that previously used libcpufreq and intend to migrate to libcpupower, because the libcpupower.so symlink is no longer installed. The command-line tools can also have symlinks (e.g. cpupower -> cpupower_$(abi_version)). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpufreqd/+bug/1215411/+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 2038522] Re: disable shiftfs
** Merge proposal linked: https://code.launchpad.net/~canonical-kernel-team/+git/overlay-shiftfs-tests/+merge/454842 -- 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/2038522 Title: disable shiftfs Status in linux package in Ubuntu: Triaged Status in linux source package in Mantic: Fix Committed Bug description: [Impact] Now that all the filesystems that we officially support have the idmapped mounts capability we can get rid of shiftfs. The benefit of this change is that we don't have to maintain an out- of-tree filesystem anymore and we can completely rely on upstream features. [Test case] lxd was the main user of shiftfs to compensate the lack of idmapped mounts capability of certain filesystems, such as zfs / ceph, but now in mantic also these two filesystem received the support for idmapped mounts (support for zfs was introduced in 2.2.0~rc3 and for ceph see LP: #2032959). The lxd team provided a positive feedback, testing the latest 6.5 Mantic kernel across all the supported filesystems with shiftfs disabled. [Fix] Disable shiftfs in the kernel config and enable unsafe idmapped mounts by default (default=on). [Regression potential] The support for idmapped mounts for the ceph filesystem is not applied upstream yet, so we may experience regressions in systems that are using this filesystem. Moreover disabling shiftfs may trigger failures in our testing (testing shiftfs capabilities will obviously fail) or break any other user-space application that is relying on shiftfs (however to our knowledge lxd was the only "official" user or shiftfs; for this reason we may also see potential regressions in lxd). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038522/+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 2038522] Re: disable shiftfs
** Merge proposal unlinked: https://code.launchpad.net/~canonical-kernel-team/+git/overlay-shiftfs-tests/+merge/454842 -- 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/2038522 Title: disable shiftfs Status in linux package in Ubuntu: Triaged Status in linux source package in Mantic: Fix Committed Bug description: [Impact] Now that all the filesystems that we officially support have the idmapped mounts capability we can get rid of shiftfs. The benefit of this change is that we don't have to maintain an out- of-tree filesystem anymore and we can completely rely on upstream features. [Test case] lxd was the main user of shiftfs to compensate the lack of idmapped mounts capability of certain filesystems, such as zfs / ceph, but now in mantic also these two filesystem received the support for idmapped mounts (support for zfs was introduced in 2.2.0~rc3 and for ceph see LP: #2032959). The lxd team provided a positive feedback, testing the latest 6.5 Mantic kernel across all the supported filesystems with shiftfs disabled. [Fix] Disable shiftfs in the kernel config and enable unsafe idmapped mounts by default (default=on). [Regression potential] The support for idmapped mounts for the ceph filesystem is not applied upstream yet, so we may experience regressions in systems that are using this filesystem. Moreover disabling shiftfs may trigger failures in our testing (testing shiftfs capabilities will obviously fail) or break any other user-space application that is relying on shiftfs (however to our knowledge lxd was the only "official" user or shiftfs; for this reason we may also see potential regressions in lxd). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038522/+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 2044722] Re: Enabling fips-preview on Jammy AWS fails with: Unexpected APT error
** Package changed: ubuntu-advantage-tools (Ubuntu) => linux-aws
(Ubuntu)
** Summary changed:
- Enabling fips-preview on Jammy AWS fails with: Unexpected APT error
+ Enabling fips-preview on Jammy AWS fails with: Depends: linux-aws-fips (>=
5.15.0.1042.43) but it is not installable
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2044722
Title:
Enabling fips-preview on Jammy AWS fails with: Depends: linux-aws-fips
(>= 5.15.0.1042.43) but it is not installable
Status in linux-aws package in Ubuntu:
New
Bug description:
I'm testing the fips-review packages on AWS for Jammy. That fails
with:
Unexpected APT error.
Failed running command 'apt-get install --assume-yes --allow-downgrades -o
Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold"
ubuntu-aws-fips' [exit(100)]. Message: E: Unable to correct problems, you have
held broken packages.
Steps to reproduce:
1) aws ec2 run-instances --image-id
resolve:ssm:/aws/service/canonical/ubuntu/server/22.04/stable/current/amd64/hvm/ebs-gp2/ami-id
--instance-type m6a.large --key-name toabctl
2) ssh into the instance
3) ua attach $MY_UA_TOKEN
4) ua enable fips-preview # (answer with yes)
The result is:
# ua enable fips-preview
One moment, checking your subscription first
FIPS Preview cannot be enabled with Livepatch.
Disable Livepatch and proceed to enable FIPS Preview? (y/N) y
Disabling incompatible service: Livepatch
This will install crypto packages that have been submitted to NIST for review
but do not have FIPS certification yet. Use this for early access to the FIPS
modules.
Please note that the Livepatch service will be unavailable after
this operation.
Warning: This action can take some time and cannot be undone.
Are you sure? (y/N) y
Updating FIPS Preview package lists
Installing FIPS Preview packages
Updating standard Ubuntu package lists
Could not enable FIPS Preview.
Updating package lists
Unexpected APT error.
Failed running command 'apt-get install --assume-yes --allow-downgrades -o
Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold"
ubuntu-aws-fips' [exit(100)]. Message: E: Unable to correct problems, you have
held broken packages.
See /var/log/ubuntu-advantage.log
From that log:
["2023-11-27T09:58:33.581", "DEBUG", "ubuntupro.system", "subp", 714, "Failed
running command 'apt-get install --assume-yes --allow-downgrades -o
Dpkg::Options::=\"--force-confdef\" -o Dpkg::Options::=\"--force-confold\"
ubuntu-aws-fips' [exit(100)]. Mes
sage: E: Unable to correct problems, you have held broken packages.\n", {}]
["2023-11-27T09:58:33.581", "WARNING", "ubuntupro.system", "subp", 715,
"Stderr: E: Unable to correct problems, you have held broken
packages.\n\nStdout: Reading package lists...\nBuilding dependency
tree...\nReading state information...\nSome packages c
ould not be installed. This may mean that you have\nrequested an impossible
situation or if you are using the unstable\ndistribution that some required
packages have not yet been created\nor been moved out of Incoming.\nThe
following information may help
to resolve the situation:\n\nThe following packages have unmet
dependencies:\n ubuntu-aws-fips : Depends: linux-aws-fips (>= 5.15.0.1042.43)
but it is not installable\n", {}]
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-advantage-tools 30~22.04
ProcVersionSignature: Ubuntu 6.2.0-1016.16~22.04.1-aws 6.2.16
Uname: Linux 6.2.0-1016-aws x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudID: aws
CloudName: aws
CloudPlatform: ec2
CloudRegion: eu-central-1
CloudSubPlatform: metadata (http://169.254.169.254)
Date: Mon Nov 27 09:59:57 2023
Ec2AMI: ami-097610d2a71255e7d
Ec2AMIManifest: (unknown)
Ec2Architecture: x86_64
Ec2AvailabilityZone: eu-central-1a
Ec2Imageid: ami-097610d2a71255e7d
Ec2InstanceType: m6a.large
Ec2Instancetype: m6a.large
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
Ec2Region: eu-central-1
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-advantage-tools
UpgradeStatus: No upgrade log present (probably fresh install)
cloud-id.txt: aws
livepatch-status.txt-error:
Failed running command '/snap/bin/canonical-livepatch status' [exit(1)].
Message: Machine is not enabled. Please run 'sudo canonical-livepatch enable'
with the
token obtained from https://ubuntu.com/livepatch.
pro-journal.txt:
Nov 27 09:57:07.273351 ip-172-31-20-161 systemd[1]: Condition check resulted
in Ubuntu Pro reboot cmds being skipped.
Nov 27 09:57:13.549831 ip-172-31-20-161 systemd[1]: Condition check resulted
in Ubuntu Pro Background Auto Attach being skipped.
uaclient.conf:
contract_url:
[Kernel-packages] [Bug 2044722] Re: Enabling fips-preview on Jammy AWS fails with: Depends: linux-aws-fips (>= 5.15.0.1042.43) but it is not installable
Hello, Thomas
this seems to be something wrong with the metapackage itself. I believe
u-a-t is doing what it should, but the dependency chain for ubuntu-aws-
fips is broken, based on the logs:
> The following packages have unmet dependencies:\n ubuntu-aws-fips :
Depends: linux-aws-fips (>= 5.15.0.1042.43) but it is not installable\n
FIPS people may know better how to deal with this.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2044722
Title:
Enabling fips-preview on Jammy AWS fails with: Depends: linux-aws-fips
(>= 5.15.0.1042.43) but it is not installable
Status in linux-aws package in Ubuntu:
New
Bug description:
I'm testing the fips-review packages on AWS for Jammy. That fails
with:
Unexpected APT error.
Failed running command 'apt-get install --assume-yes --allow-downgrades -o
Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold"
ubuntu-aws-fips' [exit(100)]. Message: E: Unable to correct problems, you have
held broken packages.
Steps to reproduce:
1) aws ec2 run-instances --image-id
resolve:ssm:/aws/service/canonical/ubuntu/server/22.04/stable/current/amd64/hvm/ebs-gp2/ami-id
--instance-type m6a.large --key-name toabctl
2) ssh into the instance
3) ua attach $MY_UA_TOKEN
4) ua enable fips-preview # (answer with yes)
The result is:
# ua enable fips-preview
One moment, checking your subscription first
FIPS Preview cannot be enabled with Livepatch.
Disable Livepatch and proceed to enable FIPS Preview? (y/N) y
Disabling incompatible service: Livepatch
This will install crypto packages that have been submitted to NIST for review
but do not have FIPS certification yet. Use this for early access to the FIPS
modules.
Please note that the Livepatch service will be unavailable after
this operation.
Warning: This action can take some time and cannot be undone.
Are you sure? (y/N) y
Updating FIPS Preview package lists
Installing FIPS Preview packages
Updating standard Ubuntu package lists
Could not enable FIPS Preview.
Updating package lists
Unexpected APT error.
Failed running command 'apt-get install --assume-yes --allow-downgrades -o
Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold"
ubuntu-aws-fips' [exit(100)]. Message: E: Unable to correct problems, you have
held broken packages.
See /var/log/ubuntu-advantage.log
From that log:
["2023-11-27T09:58:33.581", "DEBUG", "ubuntupro.system", "subp", 714, "Failed
running command 'apt-get install --assume-yes --allow-downgrades -o
Dpkg::Options::=\"--force-confdef\" -o Dpkg::Options::=\"--force-confold\"
ubuntu-aws-fips' [exit(100)]. Mes
sage: E: Unable to correct problems, you have held broken packages.\n", {}]
["2023-11-27T09:58:33.581", "WARNING", "ubuntupro.system", "subp", 715,
"Stderr: E: Unable to correct problems, you have held broken
packages.\n\nStdout: Reading package lists...\nBuilding dependency
tree...\nReading state information...\nSome packages c
ould not be installed. This may mean that you have\nrequested an impossible
situation or if you are using the unstable\ndistribution that some required
packages have not yet been created\nor been moved out of Incoming.\nThe
following information may help
to resolve the situation:\n\nThe following packages have unmet
dependencies:\n ubuntu-aws-fips : Depends: linux-aws-fips (>= 5.15.0.1042.43)
but it is not installable\n", {}]
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-advantage-tools 30~22.04
ProcVersionSignature: Ubuntu 6.2.0-1016.16~22.04.1-aws 6.2.16
Uname: Linux 6.2.0-1016-aws x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudID: aws
CloudName: aws
CloudPlatform: ec2
CloudRegion: eu-central-1
CloudSubPlatform: metadata (http://169.254.169.254)
Date: Mon Nov 27 09:59:57 2023
Ec2AMI: ami-097610d2a71255e7d
Ec2AMIManifest: (unknown)
Ec2Architecture: x86_64
Ec2AvailabilityZone: eu-central-1a
Ec2Imageid: ami-097610d2a71255e7d
Ec2InstanceType: m6a.large
Ec2Instancetype: m6a.large
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
Ec2Region: eu-central-1
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-advantage-tools
UpgradeStatus: No upgrade log present (probably fresh install)
cloud-id.txt: aws
livepatch-status.txt-error:
Failed running command '/snap/bin/canonical-livepatch status' [exit(1)].
Message: Machine is not enabled. Please run 'sudo canonical-livepatch enable'
with the
token obtained from https://ubuntu.com/livepatch.
pro-journal.txt:
Nov 27 09:57:07.273351 ip-172-31-20-161 systemd[1]: Condition check resulted
in Ubuntu Pro reboot cmds being skipped.
Nov 27 09:57:13.549831 ip-172-31-20-161 systemd[1]: Condition
[Kernel-packages] [Bug 2044722] [NEW] Enabling fips-preview on Jammy AWS fails with: Unexpected APT error
You have been subscribed to a public bug:
I'm testing the fips-review packages on AWS for Jammy. That fails with:
Unexpected APT error.
Failed running command 'apt-get install --assume-yes --allow-downgrades -o
Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold"
ubuntu-aws-fips' [exit(100)]. Message: E: Unable to correct problems, you have
held broken packages.
Steps to reproduce:
1) aws ec2 run-instances --image-id
resolve:ssm:/aws/service/canonical/ubuntu/server/22.04/stable/current/amd64/hvm/ebs-gp2/ami-id
--instance-type m6a.large --key-name toabctl
2) ssh into the instance
3) ua attach $MY_UA_TOKEN
4) ua enable fips-preview # (answer with yes)
The result is:
# ua enable fips-preview
One moment, checking your subscription first
FIPS Preview cannot be enabled with Livepatch.
Disable Livepatch and proceed to enable FIPS Preview? (y/N) y
Disabling incompatible service: Livepatch
This will install crypto packages that have been submitted to NIST for review
but do not have FIPS certification yet. Use this for early access to the FIPS
modules.
Please note that the Livepatch service will be unavailable after
this operation.
Warning: This action can take some time and cannot be undone.
Are you sure? (y/N) y
Updating FIPS Preview package lists
Installing FIPS Preview packages
Updating standard Ubuntu package lists
Could not enable FIPS Preview.
Updating package lists
Unexpected APT error.
Failed running command 'apt-get install --assume-yes --allow-downgrades -o
Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold"
ubuntu-aws-fips' [exit(100)]. Message: E: Unable to correct problems, you have
held broken packages.
See /var/log/ubuntu-advantage.log
From that log:
["2023-11-27T09:58:33.581", "DEBUG", "ubuntupro.system", "subp", 714, "Failed
running command 'apt-get install --assume-yes --allow-downgrades -o
Dpkg::Options::=\"--force-confdef\" -o Dpkg::Options::=\"--force-confold\"
ubuntu-aws-fips' [exit(100)]. Mes
sage: E: Unable to correct problems, you have held broken packages.\n", {}]
["2023-11-27T09:58:33.581", "WARNING", "ubuntupro.system", "subp", 715,
"Stderr: E: Unable to correct problems, you have held broken
packages.\n\nStdout: Reading package lists...\nBuilding dependency
tree...\nReading state information...\nSome packages c
ould not be installed. This may mean that you have\nrequested an impossible
situation or if you are using the unstable\ndistribution that some required
packages have not yet been created\nor been moved out of Incoming.\nThe
following information may help
to resolve the situation:\n\nThe following packages have unmet dependencies:\n
ubuntu-aws-fips : Depends: linux-aws-fips (>= 5.15.0.1042.43) but it is not
installable\n", {}]
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-advantage-tools 30~22.04
ProcVersionSignature: Ubuntu 6.2.0-1016.16~22.04.1-aws 6.2.16
Uname: Linux 6.2.0-1016-aws x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudID: aws
CloudName: aws
CloudPlatform: ec2
CloudRegion: eu-central-1
CloudSubPlatform: metadata (http://169.254.169.254)
Date: Mon Nov 27 09:59:57 2023
Ec2AMI: ami-097610d2a71255e7d
Ec2AMIManifest: (unknown)
Ec2Architecture: x86_64
Ec2AvailabilityZone: eu-central-1a
Ec2Imageid: ami-097610d2a71255e7d
Ec2InstanceType: m6a.large
Ec2Instancetype: m6a.large
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
Ec2Region: eu-central-1
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-advantage-tools
UpgradeStatus: No upgrade log present (probably fresh install)
cloud-id.txt: aws
livepatch-status.txt-error:
Failed running command '/snap/bin/canonical-livepatch status' [exit(1)].
Message: Machine is not enabled. Please run 'sudo canonical-livepatch enable'
with the
token obtained from https://ubuntu.com/livepatch.
pro-journal.txt:
Nov 27 09:57:07.273351 ip-172-31-20-161 systemd[1]: Condition check resulted
in Ubuntu Pro reboot cmds being skipped.
Nov 27 09:57:13.549831 ip-172-31-20-161 systemd[1]: Condition check resulted
in Ubuntu Pro Background Auto Attach being skipped.
uaclient.conf:
contract_url: https://contracts.canonical.com
log_level: debug
Note: there is no hold package:
# apt-mark showhold
root@ip-172-31-20-161:~#
** Affects: linux-aws (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug ec2-images jammy need-amd64-retrace
--
Enabling fips-preview on Jammy AWS fails with: Unexpected APT error
https://bugs.launchpad.net/bugs/2044722
You received this bug notification because you are a member of Kernel Packages,
which is subscribed to linux-aws in Ubuntu.
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta/6.5.0.14.16)
All autopkgtests for the newly accepted linux-meta (6.5.0.14.16) for mantic have finished running. The following regressions have been reported in tests triggered by the package: systemd/253.5-1ubuntu6.1 (armhf) 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/mantic/update_excuses.html#linux-meta [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 2032247] Comment bridged from LTC Bugzilla
--- Comment From s...@de.ibm.com 2023-11-27 04:25 EDT--- I've just upgraded to mantic (23.10) and I still see that linking static PIE programs leads to a segfaults at runtime. As mentioned in the bug-report, if both libc6-dev and libc6-dev-s390x-cross packages are installed, the crt-object files from the cross package are prefered and as the cross package still lacks rcrt1.o (needed for static PIE), it just uses it from the non-cross package. Due to the mixture of crt-files, it ends up in the segfault at runtime. Here is the list of my installed libc6-packages: # apt list --installed "libc6*" Listing... Done libc6-dbg/mantic,now 2.38-1ubuntu6 s390x [installed] libc6-dev-s390/mantic,now 2.38-1ubuntu6 s390x [installed] libc6-dev-s390x-cross/mantic,now 2.38-1ubuntu4cross1 all [installed] libc6-dev/mantic,now 2.38-1ubuntu6 s390x [installed] libc6-s390/mantic,now 2.38-1ubuntu6 s390x [installed] libc6-s390x-cross/mantic,now 2.38-1ubuntu4cross1 all [installed,automatic] libc6/mantic,now 2.38-1ubuntu6 s390x [installed] -- 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/2032247 Title: [UBUNTU 23.04] S390: static-PIE programs segfaults if libc6-dev-s390x-cross package is installed Status in Ubuntu on IBM z Systems: New Status in gcc-12-cross package in Ubuntu: New Status in gcc-13-cross package in Ubuntu: New Status in glibc package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: == by Stefan == A simple helloworld program build and linked as static-PIE segfaults while startup in __libc_setup_tls: $ gcc -c -fPIE -static-pie -o hello.o hello.c $ gcc -o hello hello.o -static-pie Note: If only libc6-dev package is installed, all is fine. If both libc6-dev and libc6-dev-s390x-cross packages are installed, you will see the mentioned segfault. Linking with "-Wl,-v" dumps the used linker command and it shows the used startup-files: /usr/lib/s390x-linux-gnu/rcrt1.o => from libc6-dev /usr/s390x-linux-gnu/lib/crti.o => from libc6-dev-s390x-cross /usr/lib/gcc/s390x-linux-gnu/12/crtbeginS.o /usr/lib/gcc/s390x-linux-gnu/12/crtendS.o /usr/s390x-linux-gnu/lib/crtn.o => from libc6-dev-s390x-cross Linking as static-PIE requires the rcrt1.o file, which is not available in libc6-dev-s390x-cross package, but in libc6-dev. Due to this mixing of the startup-files, you get the segfault. This issue can be fixed by enabling static-PIE also in the libc6-dev-s390x-cross package, then all startup-files belong to the same package. For s390x static-PIE was introduced in glibc 2.36: commit "S390: Enable static PIE" (in glibc 2.36) https://sourceware.org/git/?p=glibc.git;a=commit;h=728894dba4a19578bd803906de184a8dd51ed13c There is a configure check which do a link-test to ensure that a suitable binutils(ld) version is used. Afterwards static-PIE is automatically enabled. The required binutils-patches are first included in binutils 2.39. According to the build log of package cross-toolchain-base (see https://launchpad.net/ubuntu/+source/cross-toolchain-base/66ubuntu3/+build/25689036), the libc6-dev-s390x-cross package is cross-build on x86_64 and the mentioned configure check fails: running configure fragment for sysdeps/s390/s390-64 checking for s390-specific static PIE requirements... no In this cross build, glibc is configured in order to first build the crt-startup-files, which are needed to complete the cross-gcc build. At this time, the sysroot does not contain the crt-files or libc.so itself. Thus the "linking" configure check is failing. After building the cross-gcc, glibc is build without re-configuring. Thus static-PIE is not enabled. In glibc-upstream, this configure check is now adjusted and it allows checking binutils by version number: commit "s390x: Fix static PIE condition for toolchain bootstrapping." (will be in glibc 2.39) https://sourceware.org/git/?p=glibc.git;a=commit;h=f5f96b784beb3480e0e8d10e250ca7e6063ab881 Perhaps you also have to pick the following commits by Sam James which adjusted the tests in between (both are in glibc 2.36): - commit "s390: use $READELF" https://sourceware.org/git/?p=glibc.git;a=commit;h=c376ff3287b9b0f78a4f8951313c6dae60cbdfea - commit "s390: use LC_ALL=C for readelf call" https://sourceware.org/git/?p=glibc.git;a=commit;h=2249ec60a987f9a7aa585890de2bd365b3656d28 In addition to the static-PIE configure-checks, there are those other s390-specific configure-checks to determine which IFUNC-optimizations can be build and used as default. Those also fail for libc6-dev-s390x-cross as linking is also involved: running configure fragment for sysdeps/s390 checking for __builtin_tbegin... yes checking for S390 vector instruction support... no configure: WARNING: Use binutils with vector-support in order to use optimized
[Kernel-packages] [Bug 2044718] [NEW] mantic on raspberry5: x and/or lightdm problems
Public bug reported: running mantic on raspberry5, graphical sessions doesn't start unless on gdm3; while performing installation, Ubuntu Budgie graphical session goes on without problems but at reboot DE doesn't start. See attached logs collection ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Attachment added: "error logs collection" https://bugs.launchpad.net/bugs/2044718/+attachment/5723791/+files/various_logs.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2044718 Title: mantic on raspberry5: x and/or lightdm problems Status in linux-raspi package in Ubuntu: New Bug description: running mantic on raspberry5, graphical sessions doesn't start unless on gdm3; while performing installation, Ubuntu Budgie graphical session goes on without problems but at reboot DE doesn't start. See attached logs collection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2044718/+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 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
** Changed in: ideapad-laptop Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in ideapad-laptop: Invalid Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Confirmed Status in linux source package in Mantic: Confirmed Status in linux source package in Noble: Confirmed Status in Fedora: New Bug description: [Impact] Keyboard and touchpad doesn't work on some recent systems, and also s2idle is broken. [Fix] Two upstream commits. 128b0c9781c9f26 x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility 3bde7ec13c97144 platform/x86: Add s2idle quirk for more Lenovo laptops [Test case] boot a fixed kernel and test that input and s2idle works. [Where problems could occur] A buggy bios could maybe advertise a system being PCAT compatible when it's not, though in such a case it might have been already caught before. -- Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+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 2038263] Re: Add SoF topology support on Intel RaptorLake DELL SKU 0C11
** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2038263 Title: Add SoF topology support on Intel RaptorLake DELL SKU 0C11 Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Committed Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in firmware-sof source package in Lunar: Won't Fix Status in linux source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in firmware-sof source package in Mantic: Fix Released Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: SRU Jusitification for firmware-sof [Impact] To support audio functions on RPL Dell SKU 0C11, it requires the topology file from sof-tplg-v2.2.7 [Fix] Pull the sof-rpl-rt711-l0-rt1316-l12.tplg from https://github.com/thesofproject/sof-bin/releases/tag/v2023.09 [Test Case] Install the fixes on the target platform(RPL Dell SKU 0C11) and verify the audio function. 1. Install the firmware-sof on platform(RPL) Dell SKU 0C11 2. Make sure the audio output/input devices are not dummy in audio settings. [Where problems could occur] New firmware is only for the RPL platforms which requires the specific topology file. [Misc] https://github.com/thesofproject/sof-bin/releases/tag/v2023.09 [Impact] Audio play/capture are not functional on specific Dell machines of Intel RPL platforms [Fix] Backport the fix from Intel in https://github.com/thesofproject/linux [Test Case] 1. Power on the machine and open the audio settings 2. Verify it's not `Dummy` shown on the Audio output/input option [Where problems could occur] Only affect specific Intel RPL platforms. The risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2038263/+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
