[Kernel-packages] [Bug 2043786] Re: RTL8111EPP: Fix the network lost after resume with DASH

[Stefan Bader]

** Changed in: linux (Ubuntu Lunar)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Mantic)
   Importance: Undecided => Medium

-- 
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/2043786

Title:
  RTL8111EPP: Fix the network lost after resume with DASH

Status in HWE Next:
  In Progress
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 linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  In Progress
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
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:
  [Impact]
  On the system installed RTL8111EPP with DASH, unable to get the network back 
upon system resume

  [Fix]
  handle DASH during system suspend and resume.

  [Test]
  Vendor tested on hardware, the ethernet is OK after resume.

  [Where problems could occur]
  It may break r8169 driver.

  No SRU for Jammy 5.15 kernel due to too many commits are needed to
  backport to support DASH.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2043786/+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 2038259] Re: Include QCA WWAN 4G Qualcomm SDX12 CAT12/DW5825e support

[You-Sheng Yang]

** Description changed:

- Required fix: https://lore.kernel.org/linux-
- usb/20230901093610.67438-1-puliang...@fibocom.com
+ BugLink: https://bugs.launchpad.net/bugs/2038259
+ 
+ [Impact]
+ 
+ Missing usb serial interface for FM101R-GL.
+ 
+ [Fix]
+ 
+ * commit 52480e1f1a25 ("USB: serial: option: add Fibocom to DELL custom modem 
FM101R-GL"): in v6.6-rc7
+ * commit a1092619dd28 ("USB: serial: option: fix FM101R-GL defines"): in 
v6.7-rc3
+ 
+ [Test Case]
+ 
+ 1. check lsusb & dmesg output
+ ```
+ $ lsusb
+ Bus 004 Device 002: ID 413c:8215 Dell Computer Corp. Fibocom FM101-GL Module
+ ...
+ $ sudo dmesg
+ [8.460678] usbcore: registered new interface driver usbserial_generic
+ [8.460690] usbserial: USB Serial support registered for generic
+ [8.549734] usbcore: registered new interface driver option
+ [8.550108] usbserial: USB Serial support registered for GSM modem (1-port)
+ [8.550266] option 4-4:1.2: GSM modem (1-port) converter detected
+ [8.553584] usb 4-4: GSM modem (1-port) converter now attached to ttyUSB0
+ [8.556445] usbcore: registered new interface driver cdc_ncm
+ [8.601187] usbcore: registered new interface driver cdc_wdm
+ [9.059744] cdc_mbim 4-4:1.0: setting rx_max = 16384
+ [9.060079] cdc_mbim 4-4:1.0: cdc-wdm0: USB WDM device
+ [9.060338] wwan wwan0: port wwan0mbim0 attached
+ ```
+ 
+ 2. make sure ModemManager has probed it:
+ ```
+ $ mmcli -L
+ /org/freedesktop/ModemManager1/Modem/0 [Fibocom Wireless Inc.] Fibocom 
FM101-GL Module
+ ```
+ 
+ [Where problems could occur]
+ 
+ New hardware, still under development. Maybe we'll have to enable/patch
+ for its vendor specific interface or so.
+ 
+ [Other Info]
+ 
+ The first patch is available for v6.6, and the second for v6.7. While
+ we're enabling it on linux-oem-6.5/jammy, nominate for linux/noble,
+ which is currently on v6.6, and linux-oem-6.5.

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: Confirmed => In Progress

** Changed in: linux (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: linux (Ubuntu Mantic)
   Status: Confirmed => Won't Fix

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Importance: Undecided => High

** Changed in: linux-oem-6.5 (Ubuntu Mantic)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Description changed:

- BugLink: https://bugs.launchpad.net/bugs/2038259
+ [SRU Justification]
  
  [Impact]
  
  Missing usb serial interface for FM101R-GL.
  
  [Fix]
  
  * commit 52480e1f1a25 ("USB: serial: option: add Fibocom to DELL custom modem 
FM101R-GL"): in v6.6-rc7
  * commit a1092619dd28 ("USB: serial: option: fix FM101R-GL defines"): in 
v6.7-rc3
  
  [Test Case]
  
  1. check lsusb & dmesg output
  ```
  $ lsusb
  Bus 004 Device 002: ID 413c:8215 Dell Computer Corp. Fibocom FM101-GL Module
  ...
  $ sudo dmesg
  [8.460678] usbcore: registered new interface driver usbserial_generic
  [8.460690] usbserial: USB Serial support registered for generic
  [8.549734] usbcore: registered new interface driver option
  [8.550108] usbserial: USB Serial support registered for GSM modem (1-port)
  [8.550266] option 4-4:1.2: GSM modem (1-port) converter detected
  [8.553584] usb 4-4: GSM modem (1-port) converter now attached to ttyUSB0
  [8.556445] usbcore: registered new interface driver cdc_ncm
  [8.601187] usbcore: registered new interface driver cdc_wdm
  [9.059744] cdc_mbim 4-4:1.0: setting rx_max = 16384
  [9.060079] cdc_mbim 4-4:1.0: cdc-wdm0: USB WDM device
  [9.060338] wwan wwan0: port wwan0mbim0 attached
  ```
  
  2. make sure ModemManager has probed it:
  ```
  $ mmcli -L
- /org/freedesktop/ModemManager1/Modem/0 [Fibocom Wireless Inc.] Fibocom 
FM101-GL Module
+ /org/freedesktop/ModemManager1/Modem/0 [Fibocom Wireless Inc.] Fibocom 
FM101-GL Module
  ```
  
  [Where problems could occur]
  
  New hardware, still under development. Maybe we'll have to enable/patch
  for its vendor specific interface or so.
  
  [Other Info]
  
  The first patch is available for v6.6, and the second for v6.7. While
  we're enabling it on linux-oem-6.5/jammy, nominate for linux/noble,
  which is currently on v6.6, and linux-oem-6.5.

-- 
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/2038259

Title:
  Include QCA WWAN 4G Qualcomm SDX12 CAT12/DW5825e support

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.5 source package in Jammy:
  In Progress
Status in linux source package in Mantic:
  Won't Fix
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [SRU 

[Kernel-packages] [Bug 2044657] Re: zfs block cloning file system corruption

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux-hwe-6.2 (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2044657

Title:
  zfs block cloning file system corruption

Status in linux-hwe-6.2 package in Ubuntu:
  Confirmed
Status in linux-hwe-6.5 package in Ubuntu:
  Confirmed
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/linux-hwe-6.2/+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 2044657] Re: zfs block cloning file system corruption

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux-hwe-6.5 (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2044657

Title:
  zfs block cloning file system corruption

Status in linux-hwe-6.2 package in Ubuntu:
  Confirmed
Status in linux-hwe-6.5 package in Ubuntu:
  Confirmed
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/linux-hwe-6.2/+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 2045220] [NEW] Focal update: v5.4.258 upstream stable release

[Portia Stephens]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   upstream stable patchset 2023-11-30
   from git://git.kernel.org/

NFS/pNFS: Report EINVAL errors from connect() to the server
SUNRPC: Mark the cred for revalidation if the server rejects it
tracing: Increase trace array ref count on enable and filter files
ata: libahci: clear pending interrupt status
ext4: remove the 'group' parameter of ext4_trim_extent
ext4: add new helper interface ext4_try_to_trim_range()
ext4: scope ret locally in ext4_try_to_trim_range()
ext4: change s_last_trim_minblks type to unsigned long
ext4: mark group as trimmed only if it was fully scanned
ext4: replace the traditional ternary conditional operator with with max()/min()
ext4: move setting of trimmed bit into ext4_try_to_trim_range()
ext4: do not let fstrim block system suspend
ASoC: meson: spdifin: start hw on dai probe
netfilter: nf_tables: disallow element removal on anonymous sets
bpf: Avoid deadlock when using queue and stack maps from NMI
selftests/tls: Add {} to avoid static checker warning
selftests: tls: swap the TX and RX sockets in some tests
ASoC: imx-audmix: Fix return error with devm_clk_get()
i40e: Fix for persistent lldp support
i40e: Remove scheduling while atomic possibility
i40e: Fix warning message and call stack during rmmod i40e driver
i40e: Fix VF VLAN offloading when port VLAN is configured
powerpc/perf/hv-24x7: Update domain value check
dccp: fix dccp_v4_err()/dccp_v6_err() again
net: hns3: add 5ms delay before clear firmware reset irq source
net: bridge: use DEV_STATS_INC()
team: fix null-ptr-deref when team device type is changed
net: rds: Fix possible NULL-pointer dereference
gpio: tb10x: Fix an error handling path in tb10x_gpio_probe()
i2c: mux: demux-pinctrl: check the return value of devm_kstrdup()
Input: i8042 - add quirk for TUXEDO Gemini 17 Gen1/Clevo PD70PN
scsi: qla2xxx: Fix update_fcport for current_topology
scsi: qla2xxx: Fix deletion race condition
drm/amd/display: Reinstate LFC optimization
drm/amd/display: Fix LFC multiplier changing erratically
drm/amd/display: prevent potential division by zero errors
ata: libata: disallow dev-initiated LPM transitions to unsupported states
MIPS: Alchemy: only build mmc support helpers if au1xmmc is enabled
clk: tegra: fix error return case for recalc_rate
ARM: dts: ti: omap: motorola-mapphone: Fix abe_clkctrl warning on boot
bus: ti-sysc: Fix SYSC_QUIRK_SWSUP_SIDLE_ACT handling for uart wake-up
xtensa: add default definition for XCHAL_HAVE_DIV32
xtensa: iss/network: make functions static
xtensa: boot: don't add include-dirs
xtensa: boot/lib: fix function prototypes
gpio: pmic-eic-sprd: Add can_sleep flag for PMIC EIC chip
parisc: sba: Fix compile warning wrt list of SBA devices
parisc: iosapic.c: Fix sparse warnings
parisc: drivers: Fix sparse warning
parisc: irq: Make irq_stack_union static to avoid sparse warning
selftests/ftrace: Correctly enable event in instance-event.tc
ring-buffer: Avoid softlockup in ring_buffer_resize()
ata: libata-eh: do not clear ATA_PFLAG_EH_PENDING in ata_eh_reset()
spi: nxp-fspi: reset the FLSHxCR1 registers
bpf: Clarify error expectations from bpf_clone_redirect
powerpc/watchpoints: Annotate atomic context in more places
fbdev/sh7760fb: Depend on FB=y
nvme-pci: do not set the NUMA node of device if it has none
watchdog: iTCO_wdt: No need to stop the timer in probe
watchdog: iTCO_wdt: Set NO_REBOOT if the watchdog is not already running
i40e: improve locking of mac_filter_hash
i40e: always propagate error value in i40e_set_vsi_promisc()
i40e: fix return of uninitialized aq_ret in i40e_set_vsi_promisc
smack: Record transmuting in smk_transmuted
smack: Retrieve transmuting information in smack_inode_getsecurity()
Smack:- Use overlay inode label in smack_inode_copy_up()
serial: 8250_port: Check IRQ data before use
nilfs2: fix potential use after free in nilfs_gccache_submit_read_data()
ALSA: hda: Disable power save for solving pop issue on Lenovo ThinkCentre M70q
ata: libata-scsi: ignore reserved bits for REPORT SUPPORTED OPERATION CODES
i2c: i801: unregister tco_pdev in i801_probe() error path
ring-buffer: Update "shortest_full" in polling
btrfs: properly report 0 avail for very full file systems
net: thunderbolt: Fix TCPv6 GSO checksum calculation
ata: libata-core: Fix ata_port_request_pm() locking
ata: libata-core: Fix port and device removal
ata: libata-core: Do not register PM operations for SAS ports
ata: libata-sata: increase PMP SRST timeout to 10s
fs: binfmt_elf_efpic: fix personality for ELF-FDPIC
rbd: move rbd_dev_refresh() definition
rbd: 

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure/5.4.0.1121.114)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-azure (5.4.0.1121.114) for 
focal have finished running.
The following regressions have been reported in tests triggered by the package:

dahdi-linux/1:2.11.1~dfsg-1ubuntu6.3 (amd64)
v4l2loopback/0.12.3-1ubuntu0.4 (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-azure

[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 2044061] Re: [amdgpu] Green vertical and horizontal lines appearing since update

[Daniel van Vugt]

The amdgpu kernel driver here doesn't seem to be from Ubuntu so we can't
track its bugs here.

Please consider uninstalling the drivers that are presumably from AMD,
then reboot and report new bugs to Ubuntu for any issues you find.


** Changed in: linux-hwe-6.2 (Ubuntu)
   Status: New => Invalid

** Changed in: mesa (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2044061

Title:
  [amdgpu] Green vertical and horizontal lines appearing since update

Status in linux-hwe-6.2 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid

Bug description:
  Did sudo apt update && upgrade, now getting vertical and horizontal
  visual artifacts

  -Tried installing amd drivers
  -Tried using an older kernel

  Still no luck; definitely 100% not a hardware issue, machine is dual
  boot and they do not appear on the windows side. It's related to the
  update. It occurs particularly frequently if I'm writing code or
  moving windows around. Attaching a picture to try and show it (it's
  hard to catch on pictures and I don't think it shows up in a screen
  shot). It's very annoying.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 20 21:30:01 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   amdgpu/6.2.4-1683306.22.04, 6.2.0-36-generic, x86_64: installed
   amdgpu/6.2.4-1683306.22.04, 6.2.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Radeon RX 580 Armor 4G 
OC [1462:3418]
  InstallationDate: Installed on 2023-10-30 (21 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: Micro-Star International Co., Ltd MS-7B86
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic 
root=UUID=6628c08f-0884-4517-a532-a5ba1ff5653e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/17/2020
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: M.70
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450-A PRO MAX (MS-7B86)
  dmi.board.vendor: Micro-Star International Co., Ltd
  dmi.board.version: 4.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd
  dmi.chassis.version: 4.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrM.70:bd06/17/2020:br5.14:svnMicro-StarInternationalCo.,Ltd:pnMS-7B86:pvr4.0:rvnMicro-StarInternationalCo.,Ltd:rnB450-APROMAX(MS-7B86):rvr4.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr4.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B86
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 4.0
  dmi.sys.vendor: Micro-Star International Co., Ltd
  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 N/A
  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-hwe-6.2/+bug/2044061/+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-azure-fde-5.15/5.15.0.1053.61~20.04.1.31)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-azure-fde-5.15 
(5.15.0.1053.61~20.04.1.31) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

dahdi-linux/1:2.11.1~dfsg-1ubuntu6.3 (amd64)
nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 (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-azure-fde-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 2038514] Re: NVIDIA CVE-2023-{31018|31022}

[Alex Murray]

Since these CVEs are now public, marking this bug as public too.

** Information type changed from Private Security to Public Security

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/2038514

Title:
  NVIDIA CVE-2023-{31018|31022}

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Mantic:
  Fix Released

Bug description:
  NVIDIA CVE-2023-31018, NVIDIA CVE-2023-31022

  https://nvidia.custhelp.com/app/answers/detail/a_id/5491

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2038514/+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 2036143] Re: out-of-bounds error

[Alex Murray]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

-- 
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/2036143

Title:
  out-of-bounds error

Status in linux package in Ubuntu:
  New

Bug description:
  kernel boots OK, but there are these errors at log (dmesg). I am not
  sure this may be a security hole or not, that`s why i mark this bug as
  if it is:

  elhoir@elhoir-sobremesa:~$ sudo dmesg | grep bounds
  [sudo] contraseña para elhoir: 
  [   13.059453] UBSAN: array-index-out-of-bounds in 
/build/linux-IPoq5q/linux-6.5.0/sound/pci/ctxfi/ctamixer.c:346:48
  [   13.059520]  __ubsan_handle_out_of_bounds+0xc6/0x110
  [   17.146799] UBSAN: array-index-out-of-bounds in 
/build/linux-IPoq5q/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3669:4
  [   17.146828]  __ubsan_handle_out_of_bounds+0xc6/0x110
  [   17.149755] UBSAN: array-index-out-of-bounds in 
/build/linux-IPoq5q/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3676:4
  [   17.149775]  __ubsan_handle_out_of_bounds+0xc6/0x110
  elhoir@elhoir-sobremesa:~$
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2022-12-03 (333 days ago)
  InstallationMedia: Xubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
  IwConfig:
   lono wireless extensions.
   
   enp34s0   no wireless extensions.
   
   virbr0no wireless extensions.
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=7601c1d1-2a20-422f-9131-05f4a4b73984 ro quiet splash 
amd_pstate=active vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-10-generic N/A
   linux-backports-modules-6.5.0-10-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.1
  RfKill:
   
  Tags: mantic
  Uname: Linux 6.5.0-10-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-07-23 (101 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/03/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 1.D0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A520M PRO (MS-7D14)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.D0:bd03/03/2023:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D14:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnA520MPRO(MS-7D14):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7D14
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036143/+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 2041751] Re: RM: Remove dangerously insecure MPPE PPTP from Ubuntu

[Alex Murray]

Subscribing ~ubuntu-archive to look at this request.

-- 
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/2041751

Title:
  RM: Remove dangerously insecure MPPE PPTP from Ubuntu

Status in linux package in Ubuntu:
  New
Status in network-manager-pptp package in Ubuntu:
  New
Status in pptp-linux package in Ubuntu:
  New
Status in pptpd package in Ubuntu:
  New

Bug description:
  Remove dangerously insecure MPPE PPTP from Ubuntu

  https://pptpclient.sourceforge.net/protocol-security.phtml

  It has been dead for over 20 years now.

  IPSec OpenVPN Strongswan are much better alternatives.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041751/+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 2045205] [NEW] "spi-nor spi0.1:Software reset failed:-524" in shutdown screen

[AceLan Kao]

Public bug reported:

[Impact]
There is a spi error message on the screen when shutting down the machine.
It won't hurt anything and all device work well in the next boot up.
Intel SPI controller doesn't support reset command, but our customer feel bad 
about this message.

[Fix]
Distinguish the error code -EOPNOTSUPP from -ENOTSUPP, and not showing the 
warnning when it's op not supported.
https://lkml.org/lkml/2023/11/29/62

[Test case]
1. boot up the system with intel SPI controller on it
2. power off the system and check if there are spi software reset failed errors 
on the screen.

[Where problems could occur]
There is a minor risk of breaking user-space applications
that rely on specific return codes for unsupported operations. However,
this risk is considered low, as such use-cases are unlikely to be common
or critical.

** Affects: hwe-next
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: AceLan Kao (acelankao)
 Status: In Progress

** Affects: linux-oem-6.5 (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux (Ubuntu Jammy)
 Importance: Undecided
 Assignee: AceLan Kao (acelankao)
 Status: In Progress

** Affects: linux-oem-6.5 (Ubuntu Jammy)
 Importance: Undecided
 Assignee: AceLan Kao (acelankao)
 Status: In Progress

** Affects: linux (Ubuntu Mantic)
 Importance: Undecided
 Assignee: AceLan Kao (acelankao)
 Status: In Progress

** Affects: linux-oem-6.5 (Ubuntu Mantic)
 Importance: Undecided
 Status: Invalid

** Affects: linux (Ubuntu Noble)
 Importance: Undecided
 Assignee: AceLan Kao (acelankao)
 Status: In Progress

** Affects: linux-oem-6.5 (Ubuntu Noble)
 Importance: Undecided
 Status: Invalid


** Tags: oem-priority originate-from-2036480 somerville

** Also affects: linux (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-6.5 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux (Ubuntu Mantic)
   Status: New => In Progress

** Changed in: linux (Ubuntu Noble)
   Status: New => In Progress

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux-oem-6.5 (Ubuntu Mantic)
   Status: New => Invalid

** Changed in: linux-oem-6.5 (Ubuntu Noble)
   Status: New => Invalid

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => AceLan Kao (acelankao)

** Changed in: linux (Ubuntu Mantic)
 Assignee: (unassigned) => AceLan Kao (acelankao)

** Changed in: linux (Ubuntu Noble)
 Assignee: (unassigned) => AceLan Kao (acelankao)

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
 Assignee: (unassigned) => AceLan Kao (acelankao)

** Tags added: oem-priority originate-from-2036480 somerville

-- 
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/2045205

Title:
  "spi-nor spi0.1:Software reset failed:-524" in shutdown screen

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-6.5 source package in Jammy:
  In Progress
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  There is a spi error message on the screen when shutting down the machine.
  It won't hurt anything and all device work well in the next boot up.
  Intel SPI controller doesn't support reset command, but our customer feel bad 
about this message.

  [Fix]
  Distinguish the error code -EOPNOTSUPP from -ENOTSUPP, and not showing the 
warnning when it's op not supported.
  https://lkml.org/lkml/2023/11/29/62

  [Test case]
  1. boot up the system with intel SPI controller on it
  2. power off the system and check if there are spi software reset failed 
errors on the screen.

  [Where problems could occur]
  There is a minor risk of breaking user-space applications
  that rely on specific return codes for unsupported operations. However,
  this risk is considered low, as such use-cases are unlikely to be common
  or critical.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2045205/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : 

[Kernel-packages] [Bug 2042902] Re: ucm2: soundwire: add rt713 SDCA device

[Artur Pak]

for Mantic

** Patch removed: "alsa-ucm-conf_1.2.9-1ubuntu3.1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2042902/+attachment/5724131/+files/alsa-ucm-conf_1.2.9-1ubuntu3.1.debdiff

** Patch added: "alsa-ucm-conf_1.2.9-1ubuntu4.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2042902/+attachment/5724992/+files/alsa-ucm-conf_1.2.9-1ubuntu4.debdiff

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/2042902

Title:
  ucm2: soundwire: add rt713 SDCA device

Status in OEM Priority Project:
  In Progress
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Jammy:
  New
Status in alsa-ucm-conf source package in Lunar:
  New
Status in alsa-ucm-conf source package in Mantic:
  New
Status in alsa-ucm-conf source package in Noble:
  Fix Released

Bug description:
  [ Impact ]
  Affects devices with SoundWire-Audio Codec-ALC713 and SoundWire-Jack 
Codec-ALC713.
  Without correct configurations in userspace above codecs cannot be used. Thus 
in Settings > Sound > Output test doesn't produce sounds and Input device is 
greyed out.

  [ Fix ]
  Adding rt713 config files in ucm2 will allow to utilize those codecs.
  Upstream commit added support: 
https://github.com/alsa-project/alsa-ucm-conf/pull/363

  [ Test Plan ]
  Device with the soundwire card

  $ cat /proc/asound/cards
   0 [sofsoundwire   ]: sof-soundwire - sof-soundwire
    Intel Soundwire SOF

  Before fix:

  1. $ alsactl init
  alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration 
file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf
  alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file 
/usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2
  alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use 
case configuration -2
  Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" 
"HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 
mic:rt713-dmic" "" ""
  Hardware is initialized using a generic method

  2. $ amixer contents
  ...
  numid=24,iface=MIXER,name='Headphone Switch'
    ; type=BOOLEAN,access=rw--,values=1
    : values=off
  ...
  numid=33,iface=MIXER,name='IEC958 Playback Switch'
    ; type=BOOLEAN,access=rw--,values=1
    : values=off

  After fix: after adding patch files

  1. $ alsactl init
  alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf 
/var/lib/alsa/card0.conf.d' failed (exit code 1)

  (note: assuming that failed to remove the empty directory is not a
  critical problem)

  2. $ amixer contents
  ...
  numid=24,iface=MIXER,name='Headphone Switch'
    ; type=BOOLEAN,access=rw--,values=1
    : values=on
  ...
  numid=33,iface=MIXER,name='IEC958 Playback Switch'
    ; type=BOOLEAN,access=rw--,values=1
    : values=on

  [Where problems could occur]

   * This change adds new hardware support.

   * The change only adds new hardware support,
     it will not affect other codec device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2042902/+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 1975444] Re: mt7921e wifi fails to resume after suspend

[Doki]

It happens from time to time with my Dell Inspiron as well (I happen to
have 5425, 7425 and 5625 models)

The mt7921e module reload seems to fix the issue.

I've created a root owned executable file at /usr/lib/systemd/system-
sleep/mt-wifi for it as

#!/bin/sh
PATH=/sbin:/usr/sbin:/bin:/usr/bin

if [ "$1" = "post" ]; then
modprobe mt7921e
elif [ "$1" = "pre" ]; then
modprobe -r mt7921e
fi
exit 0

-- 
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/1975444

Title:
  mt7921e wifi fails to resume after suspend

Status in linux package in Ubuntu:
  Expired

Bug description:
  After resuming my suspended PC, the wifi becomes unresponsive. The
  only way to get it working again is to do a full reboot. I'm using
  Ubuntu 22.04 LTS Jammy and my wifi card is:

  MEDIATEK Corp. MT7921K (RZ608) Wi-Fi 6E 80MHz using `mt7921e` driver.

  This is what I can see in the logs:

  kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT 
domain=0x000a address=0x0 flags=0x0020]
  kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT 
domain=0x000a address=0x0 flags=0x0020]
  kernel: mt7921e :02:00.0: chip reset
  kernel: mt7921e :02:00.0: Message 004e (seq 7) timeout
  kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT 
domain=0x000a address=0x0 flags=0x0020]
  kernel: mt7921e :02:00.0: chip reset failed
  kernel: mt7921e :02:00.0: Failed to get patch semaphore
  kernel: mt7921e :02:00.0: Message 8010 (seq 4) timeout
  kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT 
  kernel: mt7921e :02:00.0: chip reset failed
  kernel: mt7921e :02:00.0: Failed to get patch semaphore
  kernel: mt7921e :02:00.0: Message 8010 (seq 12) timeout
  kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT 
domain=0x000a address=0x0 flags=0x0020]
  kernel: mt7921e :02:00.0: Failed to get patch semaphore
  kernel: mt7921e :02:00.0: Message 8010 (seq 11) timeout
  kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT 
domain=0x000a address=0x0 flags=0x0020]
  kernel: mt7921e :02:00.0: Failed to get patch semaphore
  kernel: mt7921e :02:00.0: Message 8010 (seq 10) timeout
  kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT 
domain=0x000a address=0x0 flags=0x0020]
  kernel: mt7921e :02:00.0: Failed to get patch semaphore
  kernel: mt7921e :02:00.0: Message 8010 (seq 9) timeout
  kernel:  mt7921_start+0x25/0x70 [mt7921e]
  kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT 
domain=0x000a address=0x0 flags=0x0020]
  kernel: PM: pci_legacy_suspend(): mt7921_pci_suspend+0x0/0x340 [mt7921e] 
returns -110
  kernel: mt7921e :02:00.0: Message 4007 (seq 2) timeout
  kernel:  mt7921_poll_rx+0x4f/0xe0 [mt7921e]
  kernel: mt7921e :02:00.0 wlp2s0: renamed from wlan0
  NetworkManager:   [1653237444.7259] rfkill1: found Wi-Fi radio 
killswitch (at 
/sys/devices/pci:00/:00:02.2/:02:00.0/ieee80211/phy0/rfkill1) 
(driver mt7921e)
  kernel: mt7921e :02:00.0: Firmware init done
  kernel:  mt7921_pci_driver_init+0x23/0x1000 [mt7921e]
  kernel: mt7921e :02:00.0: ASIC revision: 79610010

  I really appreciate someone's help to fix this behaviour.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsoles 1932 F pulseaudio
   /dev/snd/controlC0:  dsoles 1932 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-07 (16 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: AZW SER
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=212b8944-a42a-41d8-add0-95aa98d374fb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/21/2022
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: SER_V1.08_P3C6M43_B_Link
  dmi.board.asset.tag: Default string
  dmi.board.name: SER
  dmi.board.vendor: AZW
  dmi.board.version: V01
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: AZW
  dmi.chassis.version: Default string
  dmi.modalias: 

[Kernel-packages] [Bug 2045072] Re: [Samsung Galaxy Book2 750XED] Screen goes black

[Daniel van Vugt]

Thanks. It sounds like perhaps the laptop lid switch or LCD backlight
are misbehaving.

When the screen goes black, do you notice if:

 * The machine is sleeping (power light has changed); or
 * There is still a picture on screen you can see with a flashlight only.

Either way, please try the kernel parameter:

  acpi_backlight=vendor


** Summary changed:

- Bug on galaky book2 750xed
+ [Samsung Galaxy Book2 750XED] Screen goes black

** Package changed: ubuntu => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2045072

Title:
  [Samsung Galaxy Book2 750XED] Screen goes black

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I had to set nomode parameter to avoid the screen become dark and then
  change the line of the file /etc/default/grub

  from "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

  to "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_dc=0
  intel_idle.max_cstate=2"

  then add to the file /etc/systemd/logind.conf

  the instructions:

  HandleLidSwitch=ignore
  HandleLidSwitchExternalPower=ignore
  HandleLidSwitchDocked=ignore

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 28 22:00:43 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) 
(prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Alder Lake-UP3 GT2 [Iris Xe 
Graphics] [144d:c1c6]
  InstallationDate: Installed on 2023-11-13 (15 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=it_IT.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=681212a7-b32a-4fbf-a9a1-b51bef0216f7 ro quiet splash i915.enable_dc=0 
intel_idle.max_cstate=2 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2023
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P13CFG.039.230726.HQ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP750XED-KC2IT
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SAMSUNG_SW_REVISION_12345+0.0.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP13CFG.039.230726.HQ:bd07/26/2023:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn750XED:pvrP13CFG:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP750XED-KC2IT:rvrSAMSUNG_SW_REVISION_12345+0.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-ADLP-PCFG:
  dmi.product.family: Galaxy Book2
  dmi.product.name: 750XED
  dmi.product.sku: SCAI-A5A5-A5A5-ADLP-PCFG
  dmi.product.version: P13CFG
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045072/+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 2045072] [NEW] [Samsung Galaxy Book2 750XED] Screen goes black

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I had to set nomode parameter to avoid the screen become dark and then
change the line of the file /etc/default/grub

from "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

to "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_dc=0
intel_idle.max_cstate=2"

then add to the file /etc/systemd/logind.conf

the instructions:

HandleLidSwitch=ignore
HandleLidSwitchExternalPower=ignore
HandleLidSwitchDocked=ignore

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 28 22:00:43 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) 
(prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd Alder Lake-UP3 GT2 [Iris Xe Graphics] 
[144d:c1c6]
InstallationDate: Installed on 2023-11-13 (15 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
 LANG=it_IT.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=681212a7-b32a-4fbf-a9a1-b51bef0216f7 ro quiet splash i915.enable_dc=0 
intel_idle.max_cstate=2 vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/26/2023
dmi.bios.release: 5.25
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: P13CFG.039.230726.HQ
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP750XED-KC2IT
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SAMSUNG_SW_REVISION_12345+0.0.
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP13CFG.039.230726.HQ:bd07/26/2023:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn750XED:pvrP13CFG:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP750XED-KC2IT:rvrSAMSUNG_SW_REVISION_12345+0.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-ADLP-PCFG:
dmi.product.family: Galaxy Book2
dmi.product.name: 750XED
dmi.product.sku: SCAI-A5A5-A5A5-ADLP-PCFG
dmi.product.version: P13CFG
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: amd64 apport-bug mantic ubuntu wayland-session
-- 
[Samsung Galaxy Book2 750XED] Screen goes black
https://bugs.launchpad.net/bugs/2045072
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux 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 2036377] Re: Fix RCU warning on AMD laptops

[Kai-Heng Feng]

** Tags removed: verification-needed-mantic-linux
** Tags added: verification-done-mantic-linux

-- 
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/2036377

Title:
  Fix RCU warning on AMD laptops

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
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:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  Scary kernel splat about RCU can be observed everytime laptop resumes
  from suspend.

  [Fix]
  Use non-atomic notifier for power supply change to relax the constraint.

  [Test]
  Once the fix is applied, no more RCU warning can be found after several
  suspend/resume cycle.

  [Where problems could occur]
  Essentially no regression potential. Atomic notifier should be used by
  core kernel, and things like power supply doesn't need to be atomic
  anyway.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2036377/+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 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

[Christian Rohmann]

1) Andre, after I switched to active-backup the issue is gone (so far).
But yeah, we are looking for a reproducer as well. It's hard to narrow
down some random issue - also likely for Intel.

2) But I just received an email from an Intel developer with a suggested
change to the driver to narrow down the issue further. I quote ...

--- cut ---

Could you edit file (from kernel source tree base) 
drivers/net/ethernet/intel/ice/ice_lag.c .
Then find the functions ice_init_lag()and ice_deinit_lag().

Then add this line to the beginning of the functions
 

return 0; and return; respectively.


the patch nomenclature would look something like this:


* Memory will be freed in ice_deinit_lag
*/
int ice_init_lag(struct ice_pf *pf)
{
struct device *dev = ice_pf_to_dev(pf);
struct ice_lag *lag;
struct ice_vsi *vsi;
int err;

+   return 0;
pf->lag = kzalloc(sizeof(*lag), GFP_KERNEL);
if (!pf->lag)
return -ENOMEM;
lag = pf->lag;

………


* This function is meant to only be called on driver remove/shutdown
*/
void ice_deinit_lag(struct ice_pf *pf)
{
struct ice_lag *lag;

+   return;
lag = pf->lag;

Then re-build the driver and try to reproduce the problem?

--- cut ---


So in essence I believe this just skips offloading the bonding / LACP to the HW.
I will set this up on one or two of our machines to test. Would you please also 
try this on your systems?

-- 
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/2036239

Title:
  Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  I'm having issues with an Intel E810-XXV card on a Dell server under Ubuntu 
Jammy.

  Details:

  - hardware --> a1:00.0 Ethernet controller: Intel Corporation Ethernet
  Controller E810-XXV for SFP (rev 02)

  - tested with both GA and HWE kernels (`5.15.0-83-generic #92` and
  `6.2.0-32-generic #32~22.04.1-Ubuntu`) with the same results.

  - using a bond over the two ports of the same card, at 25Gbps to two
  different switches, bond is using LACP with hash layer3+4 and fast
  timeout. But I believe the bug is not directly related to bonding as
  the problem seems to be in the interface.

  - machine installed by maas. No issues during installation, but at
  that time bond is not formed yet, later when linux is booted, the bond
  is formed and works without issues for a while

  - it works for about 2 to 3 hours fine, then the issue starts (may or
  may not be related to network load, but it seems that it is triggered
  by some tests that I run after openstack finishes installing)

  - one of the legs of the bond freezes and everything that would go to
  that lag is discarded, in and out, ping to random external hosts start
  losing every second packet

  - after some time you can see on the kernel log messages about "NETDEV
  WATCHDOG: enp161s0f0 (ice): transmit queue 166 timed out" and a stack
  trace

  - the switch does log that the bond is flapping
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 12 20:05 seq
   crw-rw 1 root audio 116, 33 Sep 12 20:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-22 (24 days ago)
  InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release 
amd64 (20230810)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7515
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 mgag200drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-83-generic 
root=UUID=cfb5f171-77e6-4fcd-947b-52901f51b26a ro
  ProcVersionSignature: Ubuntu 5.15.0-83.92-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-83-generic N/A
   linux-backports-modules-5.15.0-83-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.18
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-83-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 07/27/2023
  dmi.bios.release: 2.12
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.12.4
  dmi.board.name: 0J91V2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell 

[Kernel-packages] [Bug 2044192] Re: Patches needed for AmpereOne (arm64)

[John Cabaj]

** Description changed:

  [Impact]
  
- * Google requested patches for AmpereOne machine t ype
+ * Google requested patches for AmpereOne machine type
  
  [Fix]
  
  * Changes already in Mantic, will be in Jammy 6.5 kernel, targeting Jammy 
5.15 and Focal 5.4 for now
  * Cherry-picks from upstream
  
  0e5d5ae837c8 ("arm64: Add AMPERE1 to the Spectre-BHB affected list")
  db26f8f2da92 ("clocksource/drivers/arch_arm_timer: Move workaround 
synchronisation around")
  c1153d52c414 ("clocksource/drivers/arm_arch_timer: Fix masking for high freq 
counters")
  ec8f7f3342c8 ("clocksource/drivers/arm_arch_timer: Drop unnecessary ISB on 
CVAL programming")
  41f8d02a6a55 ("clocksource/drivers/arm_arch_timer: Remove any trace of the 
TVAL programming interface")
  012f18850452 ("clocksource/drivers/arm_arch_timer: Work around broken CVAL 
implementations")
  30aa08da35e0 ("clocksource/drivers/arm_arch_timer: Advertise 56bit timer to 
the core code")
  8b82c4f883a7 ("clocksource/drivers/arm_arch_timer: Move MMIO timer 
programming over to CVAL")
  72f47a3f0ea4 ("clocksource/drivers/arm_arch_timer: Fix MMIO base address vs 
callback ordering issue")
  ac9ef4f24cb2 ("clocksource/drivers/arm_arch_timer: Move drop _tval from 
erratum function names")
  a38b71b0833e ("clocksource/drivers/arm_arch_timer: Move system register timer 
programming over to CVAL")
  1e8d929231cf ("clocksource/drivers/arm_arch_timer: Extend write side of timer 
register accessors to u64")
  d72689988d67 ("clocksource/drivers/arm_arch_timer: Drop CNT*_TVAL read 
accessors")
  4775bc63f880 ("clocksource/arm_arch_timer: Add build-time guards for 
unhandled register accesses")
  
  [Test Case]
  
  * Compile tested
  * Boot tested
  * To be tested by Google
  
  [Where things could go wrong]
  
  * Low chance of regression. Changes isolated to to timers.
  
  [Other Info]
  
  * SF #00372821

** Description changed:

  [Impact]
  
  * Google requested patches for AmpereOne machine type
  
  [Fix]
  
  * Changes already in Mantic, will be in Jammy 6.5 kernel, targeting Jammy 
5.15 and Focal 5.4 for now
  * Cherry-picks from upstream
  
  0e5d5ae837c8 ("arm64: Add AMPERE1 to the Spectre-BHB affected list")
  db26f8f2da92 ("clocksource/drivers/arch_arm_timer: Move workaround 
synchronisation around")
  c1153d52c414 ("clocksource/drivers/arm_arch_timer: Fix masking for high freq 
counters")
  ec8f7f3342c8 ("clocksource/drivers/arm_arch_timer: Drop unnecessary ISB on 
CVAL programming")
  41f8d02a6a55 ("clocksource/drivers/arm_arch_timer: Remove any trace of the 
TVAL programming interface")
  012f18850452 ("clocksource/drivers/arm_arch_timer: Work around broken CVAL 
implementations")
  30aa08da35e0 ("clocksource/drivers/arm_arch_timer: Advertise 56bit timer to 
the core code")
  8b82c4f883a7 ("clocksource/drivers/arm_arch_timer: Move MMIO timer 
programming over to CVAL")
  72f47a3f0ea4 ("clocksource/drivers/arm_arch_timer: Fix MMIO base address vs 
callback ordering issue")
  ac9ef4f24cb2 ("clocksource/drivers/arm_arch_timer: Move drop _tval from 
erratum function names")
  a38b71b0833e ("clocksource/drivers/arm_arch_timer: Move system register timer 
programming over to CVAL")
  1e8d929231cf ("clocksource/drivers/arm_arch_timer: Extend write side of timer 
register accessors to u64")
  d72689988d67 ("clocksource/drivers/arm_arch_timer: Drop CNT*_TVAL read 
accessors")
  4775bc63f880 ("clocksource/arm_arch_timer: Add build-time guards for 
unhandled register accesses")
  
  [Test Case]
  
  * Compile tested
  * Boot tested
  * To be tested by Google
  
  [Where things could go wrong]
  
- * Low chance of regression. Changes isolated to to timers.
+ * Low chance of regression. Changes isolated to ARM timers.
  
  [Other Info]
  
  * SF #00372821

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/2044192

Title:
  Patches needed for AmpereOne (arm64)

Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Focal:
  New
Status in linux-gcp source package in Jammy:
  New

Bug description:
  [Impact]

  * Google requested patches for AmpereOne machine type

  [Fix]

  * Changes already in Mantic, will be in Jammy 6.5 kernel, targeting Jammy 
5.15 and Focal 5.4 for now
  * Cherry-picks from upstream

  0e5d5ae837c8 ("arm64: Add AMPERE1 to the Spectre-BHB affected list")
  db26f8f2da92 ("clocksource/drivers/arch_arm_timer: Move workaround 
synchronisation around")
  c1153d52c414 ("clocksource/drivers/arm_arch_timer: Fix masking for high freq 
counters")
  ec8f7f3342c8 ("clocksource/drivers/arm_arch_timer: Drop unnecessary ISB on 
CVAL programming")
  41f8d02a6a55 ("clocksource/drivers/arm_arch_timer: Remove any trace of the 
TVAL programming interface")
  012f18850452 ("clocksource/drivers/arm_arch_timer: Work around broken CVAL 
implementations")
  30aa08da35e0 ("clocksource/drivers/arm_arch_timer: Advertise 56bit timer 

[Kernel-packages] [Bug 2030972] Re: No speakers sound on MSI Cyborg 15 A12V (Alder Lake PCH-P High Definition Audio)

[Leo]

Today I saw that there was an update in Ubuntu about the sound on Intel
Meteor Lake hardware . I don't know if it has anything to do with the
problem, but I told my brother to update the laptop and now it works
properly.


https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2029281/comments/16

firmware-sof (2.0-1ubuntu4.4) jammy; urgency=medium

  * Soundwire support for Dell SKU0C87 devices. LP: #2029281
- Add sof-v2.7 for Intel Meteor Lake hardware.
- Add more sof-v2.7.1 Intel MTL binaries

firmware-sof (2.0-1ubuntu4.3) jammy; urgency=medium

  * Add RPL topology updates
- UBUNTU: SAUCE: Add topology updates for Intel RPL Dell 0C11 SKU.
(LP: #2038263)

 -- Dimitri John Ledkov  Fri, 17 Nov 2023 12:13:11
+

-- 
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/2030972

Title:
  No speakers sound on MSI Cyborg 15 A12V (Alder Lake PCH-P High
  Definition Audio)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Recently my brother bought this gaming Laptop (
  https://www.msi.com/Laptop/Cyborg-15-A12VX/Specification ) , and I
  installed on it Ubuntu 23.04 (6.2.0-26-generic) . Everything works
  great, but he can't hear nothing on the laptop speakers. If he plug a
  headphones, or use HDMI don't have this problem. I see a lot of
  similar issues with this audio device, Alder Lake PCH-P High
  Definition Audio, in other distros and seems to be an old kernel
  problem:

  https://askubuntu.com/questions/1454834/no-sound-out-of-laptop-
  speakers-with-alder-lake-audio-controller

  https://bugzilla.kernel.org/show_bug.cgi?id=216311

  I hope it will be fixed soon to avoid having to use headphones.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2023-07-05 (48 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: Micro-Star International Co., Ltd. Cyborg 15 A12VF
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=gl_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-27-generic 
root=UUID=1900688e-0b4b-4a99-839b-91e783371cf8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-27-generic N/A
   linux-backports-modules-6.2.0-27-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.5
  Tags:  lunar
  Uname: Linux 6.2.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True
  dmi.bios.date: 03/27/2023
  dmi.bios.release: 3.9
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: E15K1IMS.309
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-15K1
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15K1IMS.309:bd03/27/2023:br3.9:svnMicro-StarInternationalCo.,Ltd.:pnCyborg15A12VF:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15K1:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku15K1.3:
  dmi.product.family: GF
  dmi.product.name: Cyborg 15 A12VF
  dmi.product.sku: 15K1.3
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2030972/+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 1914881] Re: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245,

[Leo]

Today I saw that there was an update in Ubuntu about the sound on Intel
Meteor Lake hardware . I don't know if it has anything to do with the
problem, but I told my brother to update the laptop and now it works
properly.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2029281/comments/16

firmware-sof (2.0-1ubuntu4.4) jammy; urgency=medium

  * Soundwire support for Dell SKU0C87 devices. LP: #2029281
- Add sof-v2.7 for Intel Meteor Lake hardware.
- Add more sof-v2.7.1 Intel MTL binaries

firmware-sof (2.0-1ubuntu4.3) jammy; urgency=medium

  * Add RPL topology updates
- UBUNTU: SAUCE: Add topology updates for Intel RPL Dell 0C11 SKU.
(LP: #2038263)

 -- Dimitri John Ledkov  Fri, 17 Nov 2023 12:13:11
+

-- 
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/1914881

Title:
  No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx,
  Realtek ALC245,

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  There is no sound output from the laptop internal speakers when
  running Ubuntu 20.10.

  This is a dual-boot system;
   - Booting Windows first and then rebooting to Ubuntu -> sound works fine
   - Booting Ubuntu first and then rebooting to Windows -> Windows identifies 
sound as not enables and runs its troubleshooter to enable it

  The card seems to be recognised OK (system sound settings report
  output device as Speaker - Tiger Lake-LP Smart Sound technology Audio
  Controller. VU meters etc all appear as if sound is playing, but no
  sound.

  Headphone socket works perfectly.

  Similar bug reports for different laptops in the HP x360 series
  suggest this is a pinning problem and that the extract below from the
  boot logs may support this.

  lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  aplay -l

   List of PLAYBACK Hardware Devices 
  card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) []
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) []
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) []
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) []
    Subdevices: 1/1
    Subdevice #0: subdevice #0

  extract from journalctl -b

  kernel: snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC245: line_outs=1 
(0x17/0x0/0x0/0x0/0x0) type:>
  kernel: snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  kernel: snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
  kernel: snd_hda_codec_realtek ehdaudio0D0:mono: mono_out=0x0
  kernel: snd_hda_codec_realtek ehdaudio0D0:inputs:
  kernel: snd_hda_codec_realtek ehdaudio0D0:  Mic=0x19

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  derek  1460 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb  6 20:48:52 2021
  InstallationDate: Installed on 2021-02-04 (2 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  derek  1460 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, Speaker, 
Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/13/2021
  dmi.bios.release: 15.9
  dmi.bios.vendor: AMI
  dmi.bios.version: F.09
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 87F7
  dmi.board.vendor: HP
  dmi.board.version: 40.43
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 40.43
  dmi.modalias: 
dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx
  dmi.product.sku: 2G2C7EA#ABU
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  

[Kernel-packages] [Bug 2036184] Re: Infinite systemd loop when power off the machine with multiple MD RAIDs

[Avi Rosenberg]

any ETA for adding the fix to linux-hwe-22.04 ?

-- 
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/2036184

Title:
  Infinite systemd loop when power off the machine with multiple MD
  RAIDs

Status in HWE Next:
  New
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 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 linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  The system with multiple MD RAIDs sometimes hangs while rebooting, that's 
because of the systemd can't stop and close the MD disk.

  [Fix]
  This commit fixes the issue, and this issue has been introduced by 
12a6caf27324 ("md: only delete entries from all_mddevs when the disk is freed") 
after v6.0

  https://patchwork.kernel.org/project/linux-
  raid/patch/20230914152416.10819-1-mariusz.tkac...@linux.intel.com/

  [Test case]
  1. Reboot the system with multiple MD RAIDs at least 10 times.
  2. Make sure the system can reboot successfully every time.
  3. You should not see error messages like below.

  [ 205.360738] systemd-shutdown[1]: Stopping MD devices.
  [ 205.366384] systemd-shutdown[1]: sd-device-enumerator: Scan all dirs
  [ 205.373327] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/bus
  [ 205.380427] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/class
  [ 205.388257] systemd-shutdown[1]: Stopping MD /dev/md127 (9:127).
  [ 205.394880] systemd-shutdown[1]: Failed to sync MD block device /dev/md127, 
ignoring: Input/output error
  [ 205.404975] md: md127 stopped.
  [ 205.470491] systemd-shutdown[1]: Stopping MD /dev/md126 (9:126).
  [ 205.770179] md: md126: resync interrupted.
  [ 205.776258] md126: detected capacity change from 1900396544 to 0
  [ 205.783349] md: md126 stopped.
  [ 205.862258] systemd-shutdown[1]: Stopping MD /dev/md125 (9:125).
  [ 205.862435] md: md126 stopped.
  [ 205.868376] systemd-shutdown[1]: Failed to sync MD block device /dev/md125, 
ignoring: Input/output error
  [ 205.872845] block device autoloading is deprecated and will be removed.
  [ 205.880955] md: md125 stopped.
  [ 205.934349] systemd-shutdown[1]: Stopping MD /dev/md124p2 (259:7).
  [ 205.947707] systemd-shutdown[1]: Could not stop MD /dev/md124p2: Device or 
resource busy
  [ 205.957004] systemd-shutdown[1]: Stopping MD /dev/md124p1 (259:6).
  [ 205.964177] systemd-shutdown[1]: Could not stop MD /dev/md124p1: Device or 
resource busy
  [ 205.973155] systemd-shutdown[1]: Stopping MD /dev/md124 (9:124).
  [ 205.979789] systemd-shutdown[1]: Could not stop MD /dev/md124: Device or 
resource busy
  [ 205.988475] systemd-shutdown[1]: Not all MD devices stopped, 4 left.

  [Where problems could occur]
  It fixes the data race issue, should not introduce any regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2036184/+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 2043542] Re: Add MT7925 WiFi/BT support

[You-Sheng Yang]

PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-2043542

-- 
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/2043542

Title:
  Add MT7925 WiFi/BT support

Status in HWE Next:
  New
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Incomplete

Bug description:
  * WiFi
- https://lore.kernel.org/all/cover.1690863143.git.deren...@mediatek.com/
  * ebe81e6b8659 wifi: mt76: connac: add more unified event IDs
  * 3c1199134874 wifi: mt76: connac: add more unified command IDs
  * 473f26fb167e wifi: mt76: connac: add data field in struct tlv
  * 975cd4d6d547 wifi: mt76: connac: add eht support for tx power
  * e9eac4eb1bbd wifi: mt76: connac: add eht support for phy mode config
  * d3d7f57e5c1c wifi: mt76: connac: export functions for mt7925
  * 69f94b9fab06 wifi: mt76: mt792x: support mt7925 chip init
  * 525209262f9c wifi: mt76: connac: introduce helper for mt7925 chipset
  * Bluetooth
- 
https://github.com/torvalds/linux/commit/4c92ae75ea7d41b6bafe10ee6f4c12ec12624786

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2043542/+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 2044969] Re: Upstream bug: ZFS feature@block_cloning causes data corruption

[Mike Ferreira]

To install 2.2.1, i had to enable proposed in sources, then explicitly install:
>>>
sudo apt install -y zfsutils-linux=2.2.1-0ubuntu1 
libnvpair3linux=2.2.1-0ubuntu1 libuutil3linux=2.2.1-0ubuntu1 
libzfs4linux=2.2.1-0ubuntu1 libzpool5linux=2.2.1-0ubuntu1 
zfs-dkms=2.2.1-0ubuntu1
>>>
To get all the dependencies. I did tha before the install of Noble, then again 
after the install to reinstall what it rsync'ed from the Snap image to /target, 
so they would be 2.2.1.

But there is still something wrong with that. Debuggin whta is being passed... 
>>>
# Autogenerated by Subiquity: 2023-11-29 04:40:40.713721 UTC
install:
  error_tarfile: /var/log/installer/curtin-errors.tar
...
storage:
  config:
...
  - vdevs:
- partition-3
pool: rpool
mountpoint: /
pool_properties:
  ashift: 12
  autotrim: 'on'
  version: null
fs_properties:
  acltype: posixacl
  atime: null
  canmount: 'off'
  compression: lz4
  devices: 'off'
  dnodesize: auto
  normalization: formD
  relatime: 'on'
  sync: standard
  xattr: sa
default_features: true
id: zpool-1
type: zpool
  - pool: zpool-1
volume: ROOT
properties:
  canmount: 'off'
  mountpoint: none
id: zfs-2
type: zfs
...
>>>
You can see that it says: "default_features: true"

But the zpool property feature@block_cloning is still returning as
"active" <-- Which is strange, because that should say either "enabled"
or "disabled"...

To confirm, with everything as 2.2.1, hwere OpenZFS siad that that
feature is specifically 'disabled', I created another pool, and it was
"enabled" by default. I had to destroy the zpool and explicitly tell it
to be disabled in the creation statement.

-- 
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/2044969

Title:
  Upstream bug: ZFS feature@block_cloning causes data corruption

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  Noble DAILY ISO 2023.11.27 & Current Mantic Installers.

  some copied files are corrupted (chunks replaced by zeros) ISSUE #15526
  RE:https://github.com/openzfs/zfs/issues/15526

  zpool feature@block_cloning came out with version 2.2.0 of zfs-linux,
  this is not the root of that bug, but exacerbates the underlying bug.
  The bug was reported, and version 2.2.1 was released with that feature
  turned off by default, so that would be a problem out of the gate.

  There is a patch out which got approved, merged and built tonight that, after 
testing, seems to correct that:
  dnode_is_dirty: check dnode and its data for dirtiness #15571
  https://github.com/openzfs/zfs/pull/15571

  Unfortunately, Mantic was released with version 2.2.0. Current DEV
  Noble also has 2.2.0. This feature in the default ZFS install scripts
  for both Mantic and Noble, with the current default, In bpool,
  feature@block_cloning is disable, but for rpool, the same feature is
  enabled, so "at risk".

  This feature is set at pool creation time. You cannot set this feature
  to disable without destroying the pool and recreating it fresh. Have
  good backups, via rsync. cp is affected, but not rsync.

  Version 2.2.1 has this feature disabled by default. It was released
  Nov 21, 2023.

  I am proposing that the patched build from tonight get pushed through
  for Mantic when it hits from upstream... And possibly pushing 2.2.1
  through for Noble, where we can thoroughly test it in this current DEV
  Cycle.

  Also, this was filed because of Security as it relates to data integrity 
concerns:
  CVE-2023-49298
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-49298

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: zfsutils-linux 2.2.0-0ubuntu3
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Mon Nov 27 19:58:32 2023
  InstallationDate: Installed on 2023-11-23 (4 days ago)
  InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231123)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044969/+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 2031412] Re: Support mipi camera on Intel Meteor Lake platform

[You-Sheng Yang]

Nothing broken. It's just one more change to load as soon as possible.

-- 
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 MIPI aggregator for ADL/RPL platforms) are
  in v6.6 already, and IPU6 ISYS is under upstream review. More components
  to come according to 

[Kernel-packages] [Bug 2041996] Re: pwr-mlxbf: Several bug fixes for focal

[Bartlomiej Zolnierkiewicz]

** Also affects: linux-bluefield (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: linux-bluefield (Ubuntu)
   Status: New => Invalid

-- 
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/2041996

Title:
  pwr-mlxbf: Several bug fixes for focal

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Focal:
  New

Bug description:
  SRU Justification:

  [Impact]

  There is are several changes that needs to be made to pwr-mlxbf in focal:
  * There is a race condition between gpio-mlxbf2.c driver being loaded and 
pwr-mlxbf.c being loaded
  * When the module is removed, there is a panic due to NULL pointer access
  * soft reset needs to be replaced by graceful reboot

  [Fix]

  * Fix race condition between gpio-mlxbf2.c driver being loaded and 
pwr-mlxbf.c being loaded
  * Fix panic due to access to NULL pointer when driver is removed via rmmod
  * support graceful reboot instead of soft reset 

  [Test Case]

  * all test cases are for BF2:
  * trigger the gpio toggling from the BMC: ipmitool raw 0x32 0xA1 0x02
This should trigger a graceful reboot of the DPU.
  * rmmod/modprobe
  * reboot test and make sure the driver is always loaded

  [Regression Potential]

  * Run the 100 reboot test and make sure that the driver is loaded with
  no issues. That the gpio graceful reboot works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2041996/+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 2019000] Re: Use new annotations model

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-aws-
fips/5.4.0-1116.126+fips1 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-focal-linux-aws-fips' to
'verification-done-focal-linux-aws-fips'. If the problem still exists,
change the tag 'verification-needed-focal-linux-aws-fips' to
'verification-failed-focal-linux-aws-fips'.


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-focal-linux-aws-fips-v2 
verification-needed-focal-linux-aws-fips

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/2019000

Title:
  Use new annotations model

Status in linux package in Ubuntu:
  Invalid
Status in linux-gcp package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Focal:
  Fix Released
Status in linux-gcp source package in Focal:
  Fix Released
Status in linux-kvm source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-gcp source package in Jammy:
  Fix Released
Status in linux-kvm source package in Jammy:
  New
Status in linux source package in Kinetic:
  Confirmed
Status in linux-gcp source package in Kinetic:
  Invalid
Status in linux-kvm source package in Kinetic:
  Invalid

Bug description:
  [Impact]

  Starting with lunar we have introduced a new way to manage kernel
  configs, unifying the duplicated information defined in the
  annotations file + config chunks into an annotations-only model.

  [Test case]

  A kernel build can be considered a valid test case, in particular the
  specific command that is used to update the .config's for all the
  supported architectures and flavours:

   $ fakeroot debian/rules updateconfigs

  [Fix]

  Import the required changes in debian/ from lunar (with the required
  adjustments) to support the annotations-only model also in all the
  previous releases.

  [Regression potential]

  We may experience regressions during the updateconfigs step,
  especially with derivatives. Moreover, derivatives that want to
  transition to the new annotations model require to adjust the header
  in the annotations file as following (make sure to define the
  corresponding architectures and flavours):

  # FORMAT: 4
  # ARCH: amd64 arm64 armhf ppc64el s390x
  # FLAVOUR: amd64-generic amd64-lowlatency arm64-generic arm64-generic-64k 
arm64-lowlatency arm64-lowlatency-64k armhf-generic armhf-generic-lpae 
ppc64el-generic s390x-generic

  After adjusting the header a special command is provided to transition
  to the new annotations-only model:

   $ fakeroot debian/rules migrateconfigs

  This command should automatically import the old configs into the new
  annotations file.

  A kernel with this change applied can still support the old
  annotations+configs model, the transition to the new model is not
  mandatory.

  Basically without using `fakeroot debian/rules migrateconfigs` the
  updateconfigs step will continue to use the old model and the old
  scripts (that is the safest approach to avoid potential unexpected
  .config changes).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019000/+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

[Jake Lepere]

I'm running into this issue as well, though the following lines are
included in my output:

```
Depends: openssl (= 3.0.2-0ubuntu1.10+Fips1) but 3.0.2-0ubuntu1.12 is to be 
installed
Depends: libssl3 (= 3.0.2-0ubuntu1.10+Fips1) but 3.0.2-0ubuntu1.12 is to be 
installed
```

I already have `3.0.2-0ubuntu1.12` installed, though.

```
$ dpkg -s openssl
Package: openssl
Status: install ok installed
Priority: important
Section: utils
Installed-Size: 2053
Maintainer: Ubuntu Developers 
Architecture: amd64
Multi-Arch: foreign
*Version: 3.0.2-0ubuntu1.12*
Depends: libc6 (>= 2.34), libssl3 (>= 3.0.2-0ubuntu1.2)
Suggests: ca-certificates
Conffiles:
 /etc/ssl/openssl.cnf 6b4a72a4ce84bab35d884e536295e14f
Description: Secure Sockets Layer toolkit - cryptographic utility
 This package is part of the OpenSSL project's implementation of the SSL
 and TLS cryptographic protocols for secure communication over the
 Internet.
 .
 It contains the general-purpose command line binary /usr/bin/openssl,
 useful for cryptographic operations such as:
  * creating RSA, DH, and DSA key parameters;
  * creating X.509 certificates, CSRs, and CRLs;
  * calculating message digests;
  * encrypting and decrypting with ciphers;
  * testing SSL/TLS clients and servers;
  * handling S/MIME signed or encrypted mail.
Homepage: https://www.openssl.org/
Original-Maintainer: Debian OpenSSL Team 

```

-- 
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 

[Kernel-packages] [Bug 2042090] Re: Orchid Bay MLK2/Maya Bay MLK soundwire support

[You-Sheng Yang]

** Description changed:

+ == firmware-sof ==
+ 
+ [Impact]
+ 
+ Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.
+ 
+ [Fix]
+ 
+ Kernel driver, ALSA ucm, and firmware fixes are needed. For firmware-
+ sof, it's the upstream commit 99466c05f15f ("Add Intel SOF2.7.2 topology
+ files").
+ 
+ [Test Case]
+ 
+ 1. enable -proposed pocket and install firmware-sof-signed
+ 2. browse youtube, hold backspace on virtual terminal or whatever makes some 
noises
+ 3. expected sound system brought up and reacts accordingly
+ 
+ [Where problems could occur]
+ 
+ While this enables new devices on new platforms, we may bump into burst
+ noises, power consumption problems at corner cases not covered by test
+ program.
+ 
+ [Other Info]
+ 
+ This is to enable sof devices on Intel MTL platform, which is only
+ supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
+ Jammy.
+ 
+ == original bug report ==
+ 
  The kernel patches has been applied in the ASoC tree.
  Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel 
(spinics.net) [spinics.net]
  https://www.spinics.net/lists/alsa-devel/msg167273.html
  We need 3/23, 4/23, 6/23, and 
https://github.com/thesofproject/linux/commit/037809ef79874a610216fd6b6d50f53e069b5176
  
  And the UCM PR is submitted
  ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 · 
alsa-project/alsa-ucm-conf (github.com) [github.com]
  https://github.com/alsa-project/alsa-ucm-conf/pull/363
+ See bug 2042902.
  
  For firmware-sof, need upstream commit 99466c05f15f ("Add Intel SOF2.7.2
  topology files").

** Attachment removed: "firmware-sof_2.2.6-1ubuntu4~ppa.1.noble.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.5/+bug/2042090/+attachment/5722781/+files/firmware-sof_2.2.6-1ubuntu4~ppa.1.noble.debdiff

** Attachment removed: "firmware-sof_2.2.6-1ubuntu1.3~ppa.1.mantic.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.5/+bug/2042090/+attachment/5722782/+files/firmware-sof_2.2.6-1ubuntu1.3~ppa.1.mantic.debdiff

** Attachment removed: "firmware-sof_2.0-1ubuntu4.5~ppa.1.jammy.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.5/+bug/2042090/+attachment/5722783/+files/firmware-sof_2.0-1ubuntu4.5~ppa.1.jammy.debdiff

** Description changed:

+ [SRU Justifications]
+ 
  == firmware-sof ==
  
  [Impact]
  
  Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.
  
  [Fix]
  
  Kernel driver, ALSA ucm, and firmware fixes are needed. For firmware-
  sof, it's the upstream commit 99466c05f15f ("Add Intel SOF2.7.2 topology
  files").
  
  [Test Case]
  
  1. enable -proposed pocket and install firmware-sof-signed
  2. browse youtube, hold backspace on virtual terminal or whatever makes some 
noises
  3. expected sound system brought up and reacts accordingly
  
  [Where problems could occur]
  
  While this enables new devices on new platforms, we may bump into burst
  noises, power consumption problems at corner cases not covered by test
  program.
  
  [Other Info]
  
  This is to enable sof devices on Intel MTL platform, which is only
  supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
  Jammy.
  
  == original bug report ==
  
  The kernel patches has been applied in the ASoC tree.
  Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel 
(spinics.net) [spinics.net]
  https://www.spinics.net/lists/alsa-devel/msg167273.html
  We need 3/23, 4/23, 6/23, and 
https://github.com/thesofproject/linux/commit/037809ef79874a610216fd6b6d50f53e069b5176
  
  And the UCM PR is submitted
  ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 · 
alsa-project/alsa-ucm-conf (github.com) [github.com]
  https://github.com/alsa-project/alsa-ucm-conf/pull/363
  See bug 2042902.
  
  For firmware-sof, need upstream commit 99466c05f15f ("Add Intel SOF2.7.2
  topology files").

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Jammy)
   Status: New => Invalid

** Changed in: linux (Ubuntu Noble)
   Status: New => Triaged

** Changed in: linux (Ubuntu Mantic)
   Status: New => Triaged

-- 
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/2042090

Title:
  Orchid Bay MLK2/Maya Bay MLK soundwire support

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  In Progress
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Triaged
Status in firmware-sof source package in Mantic:
  In Progress
Status in linux source package in Mantic:
  Triaged
Status in linux-oem-6.5 source package in Mantic:

[Kernel-packages] [Bug 2042090] Re: Orchid Bay MLK2/Maya Bay MLK soundwire support

[You-Sheng Yang]

** Description changed:

  The kernel patches has been applied in the ASoC tree.
  Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel 
(spinics.net) [spinics.net]
  https://www.spinics.net/lists/alsa-devel/msg167273.html
- We need 3/23, 4/23, 6/23
+ We need 3/23, 4/23, 6/23, and 
https://github.com/thesofproject/linux/commit/037809ef79874a610216fd6b6d50f53e069b5176
  
  And the UCM PR is submitted
  ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 · 
alsa-project/alsa-ucm-conf (github.com) [github.com]
  https://github.com/alsa-project/alsa-ucm-conf/pull/363
+ 
+ For firmware-sof, need upstream commit 99466c05f15f ("Add Intel SOF2.7.2
+ topology files").

-- 
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/2042090

Title:
  Orchid Bay MLK2/Maya Bay MLK soundwire support

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  In Progress
Status in linux-oem-6.5 source package in Jammy:
  Triaged
Status in firmware-sof source package in Mantic:
  In Progress
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in firmware-sof source package in Noble:
  In Progress
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  The kernel patches has been applied in the ASoC tree.
  Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel 
(spinics.net) [spinics.net]
  https://www.spinics.net/lists/alsa-devel/msg167273.html
  We need 3/23, 4/23, 6/23, and 
https://github.com/thesofproject/linux/commit/037809ef79874a610216fd6b6d50f53e069b5176

  And the UCM PR is submitted
  ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 · 
alsa-project/alsa-ucm-conf (github.com) [github.com]
  https://github.com/alsa-project/alsa-ucm-conf/pull/363

  For firmware-sof, need upstream commit 99466c05f15f ("Add Intel
  SOF2.7.2 topology files").

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042090/+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 2044330] Re: Update soundwire topology files for Intel RPL platforms

[You-Sheng Yang]

This is being SRUed along with bug 2042090. See PPA, debdiff there.

** Changed in: firmware-sof (Ubuntu)
   Status: New => In Progress

** Changed in: firmware-sof (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: firmware-sof (Ubuntu Mantic)
   Status: New => In Progress

** Changed in: firmware-sof (Ubuntu)
   Importance: Undecided => High

** Changed in: firmware-sof (Ubuntu Jammy)
   Importance: Undecided => High

** Changed in: firmware-sof (Ubuntu Mantic)
   Importance: Undecided => High

** Changed in: firmware-sof (Ubuntu)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Changed in: firmware-sof (Ubuntu Jammy)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Changed in: firmware-sof (Ubuntu Mantic)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

-- 
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:
  In Progress
Status in firmware-sof source package in Jammy:
  In Progress
Status in firmware-sof source package in Mantic:
  In Progress

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

Re: [Kernel-packages] [Bug 2042090] Re: Orchid Bay MLK2/Maya Bay MLK soundwire support

[You-Sheng Yang]

Attach proposed debdiff for firmware-sof for Jammy, Mantic and Noble.

V2: include changes for bug 2044330.

Note that it contains binary files that cannot be correctly rendered
by debdiff and a PPA at
https://launchpad.net/~vicamo/+archive/ubuntu/ppa-2042090 is provided
at the same time.

Need sponsor.


** Attachment added: "firmware-sof_2.2.6-1ubuntu1.3~ppa.2.mantic.debdiff"
   
https://bugs.launchpad.net/bugs/2042090/+attachment/5724781/+files/firmware-sof_2.2.6-1ubuntu1.3~ppa.2.mantic.debdiff

** Attachment added: "firmware-sof_2.0-1ubuntu4.5~ppa.2.jammy.debdiff"
   
https://bugs.launchpad.net/bugs/2042090/+attachment/5724782/+files/firmware-sof_2.0-1ubuntu4.5~ppa.2.jammy.debdiff

** Attachment added: "firmware-sof_2.2.6-1ubuntu4~ppa.2.noble.debdiff"
   
https://bugs.launchpad.net/bugs/2042090/+attachment/5724783/+files/firmware-sof_2.2.6-1ubuntu4~ppa.2.noble.debdiff

-- 
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/2042090

Title:
  Orchid Bay MLK2/Maya Bay MLK soundwire support

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  In Progress
Status in linux-oem-6.5 source package in Jammy:
  Triaged
Status in firmware-sof source package in Mantic:
  In Progress
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in firmware-sof source package in Noble:
  In Progress
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  The kernel patches has been applied in the ASoC tree.
  Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel 
(spinics.net) [spinics.net]
  https://www.spinics.net/lists/alsa-devel/msg167273.html
  We need 3/23, 4/23, 6/23, and 
https://github.com/thesofproject/linux/commit/037809ef79874a610216fd6b6d50f53e069b5176

  And the UCM PR is submitted
  ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 · 
alsa-project/alsa-ucm-conf (github.com) [github.com]
  https://github.com/alsa-project/alsa-ucm-conf/pull/363

  For firmware-sof, need upstream commit 99466c05f15f ("Add Intel
  SOF2.7.2 topology files").

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042090/+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

[Andrea Righi]

shiftfs has been correctly disabled in 6.5.0-14:

$ uname -r
6.5.0-14-generic
$ sudo modprobe shiftfs
modprobe: FATAL: Module shiftfs not found in directory 
/lib/modules/6.5.0-14-generic

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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

[Andrea Righi]

** Tags removed: verification-needed-mantic-linux
** Tags added: verification-done-mantic

-- 
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 2045069] Re: Azure: Deprecate Netvsc and implement MANA direct

[Tim Gardner]

** Changed in: linux-azure (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Changed in: linux-azure (Ubuntu Lunar)
   Status: In Progress => Fix Committed

** Changed in: linux-azure (Ubuntu Mantic)
   Status: In Progress => Fix Committed

-- 
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/2045069

Title:
  Azure: Deprecate Netvsc and implement MANA direct

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]

  Microsoft has asked for the inclusion of 3 patches that deprecate the
  use of netvsc in favor of MANA direct.

  hv_netvsc: Mark VF as slave before exposing it to user-mode:
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=c807d6cd089d2f4951baa838081ec5ae3e2360f8

  hv_netvsc: Fix race of register_netdevice_notifier and VF register:
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=85520856466ed6bc3b1ccb013cddac70ceb437db

  hv_netvsc: fix race of netvsc and VF register_netdevice:
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=d30fb712e52964f2cf9a9c14cf67078394044837

  [Test Plan]

  Microsoft tested

  [Regression potential]

  User space that relies on netvsc will likely fail

  [Other Info]

  SF: #00374570

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2045069/+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 2038611] Re: drop all references to is_rust_module.sh in kernels >= 6.5

[Andrea Righi]

This is still failing in mantic, "something" in our kernel cranking
process re-added the chmod command in debian.master/reconstruct for
is_rust_module.sh, this needs further investigation.

** Tags removed: verification-needed-mantic-linux
** Tags added: verification-failed-mantic

-- 
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/2038611

Title:
  drop all references to is_rust_module.sh in kernels >= 6.5

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  [Impact]

  The script tools/is_rust_module.sh has been dropped by this commit:

079c66bbe2f8 ("UBUNTU: SAUCE: btf, scripts: rust: drop
  is_rust_module.sh")

  And upstream as well (in 6.6):

41bdc6decda0 ("btf, scripts: rust: drop is_rust_module.sh")

  But we still have a reference of it in debian.master/reconstruct and
  that generates the following warning during the build:

chmod: cannot access 'scripts/is_rust_module.sh': No such file or
  directory

  [Fix]

  Drop the reference to is_rust_module.sh from reconstruct to prevent
  unnecessary warnings during the build.

  [Test case]

  The following command ran from the kernel source directory is enough
  to trigger the warning:

   $ fakeroot debian/rules clean

  [Regression potential]

  This change is affecting only our packaging. The change is trivial but
  it might affect our kernel build process in case of regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038611/+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 2019040] Re: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images

[Tim Gardner]

** Tags removed: verification-needed-jammy-linux-xilinx-zynqmp
** Tags added: verification-done-jammy-linux-xilinx-zynqmp

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/2019040

Title:
  linux-*: please enable dm-verity kconfigs to allow MoK/db verified
  root images

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-meta-azure package in Ubuntu:
  Invalid
Status in linux-meta-kvm package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-kvm source package in Jammy:
  Fix Released
Status in linux-meta-azure source package in Jammy:
  Invalid
Status in linux-meta-kvm source package in Jammy:
  New
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-kvm source package in Kinetic:
  In Progress
Status in linux-meta-azure source package in Kinetic:
  Invalid
Status in linux-meta-kvm source package in Kinetic:
  New
Status in linux source package in Lunar:
  Fix Released
Status in linux-kvm source package in Lunar:
  Fix Released
Status in linux-meta-azure source package in Lunar:
  New
Status in linux-meta-kvm source package in Lunar:
  New
Status in linux source package in Mantic:
  Fix Committed
Status in linux-kvm source package in Mantic:
  Invalid
Status in linux-meta-azure source package in Mantic:
  Invalid
Status in linux-meta-kvm source package in Mantic:
  Invalid

Bug description:
  SRU Justification

  [Impact]

  The kvm flavours currently do not enable dm-verity. This stops us from
  using integrity protected and verified images in VMs using this kernel
  flavour.

  [Fix]

  Please consider enabling the following kconfigs:

  CONFIG_DM_VERITY
  CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG
  CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING
  CONFIG_INTEGRITY_MACHINE_KEYRING
  CONFIG_IMA_ARCH_POLICY (this might not be necessary if the machine keyring 
implementation is patched to skip the check enabled by this kconfig)

  (The latter two are needed to ensure that MoK keys can be used to
  verify dm-verity images too, via the machine keyring linked to the
  secondary keyring)

  These are already enabled in the 'main' kernel config, and in other
  distros.

  As a specific and explicit use case, in the systemd project we want to
  test functionality provided by systemd that needs these kconfigs on
  Ubuntu machines running the kvm flavour kernel.

  To verify whether this works, add a certificate to MOK, boot and check
  the content of the secondary keyring. The machine keyring should show
  up under it, and it should show the certificates loaded in MOK. E.g.:

  $ sudo keyctl show %:.secondary_trusted_keys
  Keyring
   159454604 ---lswrv  0 0  keyring: .secondary_trusted_keys
    88754641 ---lswrv  0 0   \_ keyring: .builtin_trusted_keys
   889010778 ---lswrv  0 0   |   \_ asymmetric: Debian Secure Boot CA: 
6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1
   799434660 ---lswrv  0 0   |   \_ asymmetric: Debian Secure Boot 
Signer 2022 - linux: 14011249c2675ea8e5148542202005810584b25f
   541326986 ---lswrv  0 0   \_ keyring: .machine
   188508854 ---lswrv  0 0   \_ asymmetric: Debian Secure Boot CA: 
6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1
   475039424 ---lswrv  0 0   \_ asymmetric: sb-bluca: Secure Boot 
Signing: 9a61c52d07d78a76935e67bdbe3f5e6968d62479

  [Regression Potential]

  MOK keys may not be correctly read.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019040/+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 2042850] Re: Boot log print hang on screen, no login prompt on Aspeed 2600 rev 52 BMC

[Philip Cox]

I've verified it, and marked it as such

** Tags removed: verification-needed-mantic-linux
** Tags added: verification-done-mantic

-- 
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/2042850

Title:
  Boot log print hang on screen, no login prompt on Aspeed 2600 rev 52
  BMC

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  This is a public version of https://bugs.launchpad.net/bugs/2042423
  

  Subject: [mantic:linux]  drm/ast: Add BMC virtual connector


  SRU Justification:

  [Impact]
  On systems with Aspeed 2600 revision 52 GPUs, the display fails to progress 
to the login prompt.  With the commit (added in 6.5.0-6.6)

 commit: 916ae609a033cbb55661905d310ba2358b7621ea
 Author:  Jocelyn Falempe 
 Date:Thu Jul 13 15:41:31 2023 +0200
 Subject: drm/ast: report connection status on Display Port.

   the Aspeed 2600 rev 52 GPUs have issues.

  They need the commit:

  This change was dependant on the upstream change
  commit e329cb53b45da475966c4b2e49f6a4a430f307fa
  Author: Jocelyn Falempe 
  Date: Thu Jul 13 15:41:30 2023 +0200
  Subject: drm/ast: Add BMC virtual connector

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e329cb53b45da475966c4b2e49f6a4a430f307fa

  
  in order to have the display work correctly on the rev52 GPUs.  


  [Fix]
  With cherry-picking this change, the functionality of BMCs using Aspeed 2600 
rev52 GPUs work as expected, as they did prior to the regression in 6.5.0-6.6. 

  [Test Plan]
  I have tested this on multiple versions of Aspeed 2600 GPU enabled BMCs, and 
the revision 52 systems that required the nomodeset option to boot to the 
prompt, now boot fine and display the login prompt, and there is no regression 
on the other systems.  I have tested this on different Aspeed GPUs, and have 
not seen any regressions, or unexpected behaviour. 

  
  [Where problems could occur]
  As this fixes a regression of  functionality for the mantic kernel's Aspeed 
GPU driver on a very specific version of some BMCs to the state it was was in 
the mantic 6.5.0-5.5 kernel, I think there is little room for regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042850/+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 2019040] Re: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images

[Tim Gardner]

** Tags removed: verification-needed-mantic-linux
** Tags added: verification-done-mantic-linux

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/2019040

Title:
  linux-*: please enable dm-verity kconfigs to allow MoK/db verified
  root images

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-meta-azure package in Ubuntu:
  Invalid
Status in linux-meta-kvm package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-kvm source package in Jammy:
  Fix Released
Status in linux-meta-azure source package in Jammy:
  Invalid
Status in linux-meta-kvm source package in Jammy:
  New
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-kvm source package in Kinetic:
  In Progress
Status in linux-meta-azure source package in Kinetic:
  Invalid
Status in linux-meta-kvm source package in Kinetic:
  New
Status in linux source package in Lunar:
  Fix Released
Status in linux-kvm source package in Lunar:
  Fix Released
Status in linux-meta-azure source package in Lunar:
  New
Status in linux-meta-kvm source package in Lunar:
  New
Status in linux source package in Mantic:
  Fix Committed
Status in linux-kvm source package in Mantic:
  Invalid
Status in linux-meta-azure source package in Mantic:
  Invalid
Status in linux-meta-kvm source package in Mantic:
  Invalid

Bug description:
  SRU Justification

  [Impact]

  The kvm flavours currently do not enable dm-verity. This stops us from
  using integrity protected and verified images in VMs using this kernel
  flavour.

  [Fix]

  Please consider enabling the following kconfigs:

  CONFIG_DM_VERITY
  CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG
  CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING
  CONFIG_INTEGRITY_MACHINE_KEYRING
  CONFIG_IMA_ARCH_POLICY (this might not be necessary if the machine keyring 
implementation is patched to skip the check enabled by this kconfig)

  (The latter two are needed to ensure that MoK keys can be used to
  verify dm-verity images too, via the machine keyring linked to the
  secondary keyring)

  These are already enabled in the 'main' kernel config, and in other
  distros.

  As a specific and explicit use case, in the systemd project we want to
  test functionality provided by systemd that needs these kconfigs on
  Ubuntu machines running the kvm flavour kernel.

  To verify whether this works, add a certificate to MOK, boot and check
  the content of the secondary keyring. The machine keyring should show
  up under it, and it should show the certificates loaded in MOK. E.g.:

  $ sudo keyctl show %:.secondary_trusted_keys
  Keyring
   159454604 ---lswrv  0 0  keyring: .secondary_trusted_keys
    88754641 ---lswrv  0 0   \_ keyring: .builtin_trusted_keys
   889010778 ---lswrv  0 0   |   \_ asymmetric: Debian Secure Boot CA: 
6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1
   799434660 ---lswrv  0 0   |   \_ asymmetric: Debian Secure Boot 
Signer 2022 - linux: 14011249c2675ea8e5148542202005810584b25f
   541326986 ---lswrv  0 0   \_ keyring: .machine
   188508854 ---lswrv  0 0   \_ asymmetric: Debian Secure Boot CA: 
6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1
   475039424 ---lswrv  0 0   \_ asymmetric: sb-bluca: Secure Boot 
Signing: 9a61c52d07d78a76935e67bdbe3f5e6968d62479

  [Regression Potential]

  MOK keys may not be correctly read.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019040/+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 2042573] Re: arm64 atomic issues cause disk corruption

[Roxana Nicolescu]

Boot tested on an arm64 vm

** Tags removed: verification-needed-mantic-linux
** Tags added: verification-done-mantic-linux

-- 
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/2042573

Title:
  arm64 atomic issues cause disk corruption

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Mantic:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]
  The mantic kernel introduced a regression in atomic operations on arm64
  which causes all kinds of problems including file system corruptions,
  since commit "locking/atomic: scripts: restructure fallback
  ifdeffery".

  An example report of people encountering this in UTM with a arm64
  generic kernel: https://github.com/utmapp/UTM/issues/4840

  [Fix]
  Cherry-pick commit "locking/atomic: scripts: fix fallback ifdeffery"
  from linux-stable v6.5.6

  [Test Plan]

  Boot test on an arm64 vm.

  [Where problems could occur]
  Since this is touching atomic operations, this has a wide impact on the
  kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042573/+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 1827961] Re: Lenovo dock MAC Address pass through doesn't work in Ubuntu

[madjax]

Is there a similar bug report for Dells hardware? I can't get
passthrough to work between Dell Latitude and any Dell dock/adapter

-- 
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/1827961

Title:
  Lenovo dock MAC Address pass through doesn't work in Ubuntu

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Lenovo dock doesn't support MAC passthrough.

  [Fix]
  Add support to Lenovo Dock MAC passthrough.

  [Test]
  MAC passthrough works once the patch is applied.

  [Regression Potential]
  Low. Apart from adding support to Lenovo Dock, this patch only did minor
  refactoring to existing behavior, no functional change to current code.

  === Original Bug Report ===
  Similar to bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579984 
the MAC address pass through does not work with a Lenovo Thunderbolt 3 
Workstation Dock.

  The dock's network port is recognized and working but it has its own
  MAC address even though MAC Address pass through is enabled in the
  BIOS.

  This is the dock in question:

  https://www.lenovo.com/us/en/accessories-and-monitors/top-
  tech/Thunderbolt-WS-230W-dock-US/p/40AN0230US

  and the laptop is a Lenovo P1. Debug files attached.

  Please let me know if further info is required.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  rauer  2107 F pulseaudio
   /dev/snd/controlC1:  rauer  2107 F pulseaudio
   /dev/snd/controlC0:  rauer  2107 F pulseaudio
  CurrentDesktop: i3
  Date: Mon May  6 19:34:26 2019
  InstallationDate: Installed on 2019-04-09 (27 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  MachineType: LENOVO 20MES1WH00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=9c2b3401-a2e2-41ae-bc22-d1de22149ee0 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET39W (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MES1WH00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q40104 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET39W(1.21):bd04/15/2019:svnLENOVO:pn20MES1WH00:pvrThinkPadP1:rvnLENOVO:rn20MES1WH00:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P1
  dmi.product.name: 20MES1WH00
  dmi.product.sku: LENOVO_MT_20ME_BU_Think_FM_ThinkPad P1
  dmi.product.version: ThinkPad P1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827961/+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 2039732] Re: No graphic desktop environment on Google GCP instances

[Launchpad Bug Tracker]

This bug was fixed in the package linux-gcp - 6.2.0-1019.21

---
linux-gcp (6.2.0-1019.21) lunar; urgency=medium

  * lunar/linux-gcp: 6.2.0-1019.21 -proposed tracker (LP: #2041886)

  * Include cifs.ko in linux-modules package (LP: #2042546)
- [Packaging] Replace fs/cifs with fs/smb/client in inclusion list

  * No graphic desktop environment on Google GCP instances (LP: #2039732)
- [Config] gcp: Inherit CONFIG_SYSFB_SIMPLEFB from master

  * Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization
(LP: #2039191)
- x86/boot: Move x86_cache_alignment initialization to correct spot

  [ Ubuntu: 6.2.0-37.38 ]

  * lunar/linux: 6.2.0-37.38 -proposed tracker (LP: #2041899)
  * CVE-2023-31085
- ubi: Refuse attaching if mtd's erasesize is 0
  * CVE-2023-25775
- RDMA/irdma: Prevent zero-length STAG registration
  * CVE-2023-45871
- igb: set max size RX buffer when store bad packet is enabled
  * CVE-2023-5345
- fs/smb/client: Reset password pointer to NULL
  * CVE-2023-5090
- x86: KVM: SVM: always update the x2avic msr interception
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts

 -- Manuel Diewald   Thu, 02 Nov 2023
21:47:27 +0100

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/2039732

Title:
  No graphic desktop environment on Google GCP instances

Status in linux-gcp package in Ubuntu:
  In Progress
Status in linux-gcp source package in Jammy:
  Fix Released
Status in linux-gcp source package in Lunar:
  Fix Released
Status in linux-gcp source package in Mantic:
  Fix Committed

Bug description:
  [Impact]

  * Google reports not being able to display graphic desktop
  environment.

  [Fix]

  * CONFIG_SYSFB_SIMPLEFB was initially enabled in
  https://git.launchpad.net/~ubuntu-
  kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master-
  next=0bf2a2472f71a3001a8a9a0849b6bed7e7069a7b. It was subsequently
  disabled for amd64 in https://git.launchpad.net/~ubuntu-
  kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master-
  next=40b0ce0833309133453c3dbc19753f62084c0a7a. This was not
  reflected in the GCP kernel config.

  [Test Case]

  * Compile tested
  * Boot tested
  * To be tested by Google

  [Where things could go wrong]

  * Low chance of regression. Simple config change that was not taken
  from generic.

  [Other Info]

  * SF #00366439

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2039732/+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 2039191] Re: Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization

[Launchpad Bug Tracker]

This bug was fixed in the package linux-gcp - 6.2.0-1019.21

---
linux-gcp (6.2.0-1019.21) lunar; urgency=medium

  * lunar/linux-gcp: 6.2.0-1019.21 -proposed tracker (LP: #2041886)

  * Include cifs.ko in linux-modules package (LP: #2042546)
- [Packaging] Replace fs/cifs with fs/smb/client in inclusion list

  * No graphic desktop environment on Google GCP instances (LP: #2039732)
- [Config] gcp: Inherit CONFIG_SYSFB_SIMPLEFB from master

  * Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization
(LP: #2039191)
- x86/boot: Move x86_cache_alignment initialization to correct spot

  [ Ubuntu: 6.2.0-37.38 ]

  * lunar/linux: 6.2.0-37.38 -proposed tracker (LP: #2041899)
  * CVE-2023-31085
- ubi: Refuse attaching if mtd's erasesize is 0
  * CVE-2023-25775
- RDMA/irdma: Prevent zero-length STAG registration
  * CVE-2023-45871
- igb: set max size RX buffer when store bad packet is enabled
  * CVE-2023-5345
- fs/smb/client: Reset password pointer to NULL
  * CVE-2023-5090
- x86: KVM: SVM: always update the x2avic msr interception
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts

 -- Manuel Diewald   Thu, 02 Nov 2023
21:47:27 +0100

** Changed in: linux-gcp (Ubuntu Lunar)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/2039191

Title:
  Kernel oops on 32-0bit kernels due to x86_cache_alignment
  initialization

Status in linux-aws package in Ubuntu:
  In Progress
Status in linux-gcp package in Ubuntu:
  Fix Committed
Status in linux-aws source package in Lunar:
  Fix Released
Status in linux-gcp source package in Lunar:
  Fix Released
Status in linux-aws source package in Mantic:
  In Progress
Status in linux-gcp source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  * Kernel OOPS encountered on 32-bit kernels due to commit cd0e9ab from

git://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/lunar

  [Fix]

  * Clean cherry pick from linux-next, commit 3e3255265291

  [Test Case]

  * Compile tested
  * Boot tested
  * To be tested by Google

  [Where things could go wrong]

  * Low chance of regression, isolated fix slightly modifying when value becomes
available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2039191/+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 2039732] Re: No graphic desktop environment on Google GCP instances

[Launchpad Bug Tracker]

This bug was fixed in the package linux-gcp - 5.15.0-1047.55

---
linux-gcp (5.15.0-1047.55) jammy; urgency=medium

  * jammy/linux-gcp: 5.15.0-1047.55 -proposed tracker (LP: #2041917)

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/s2023.10.02)

  * Incorrect argument from SEV live-migration fix (LP: #2040337)
- SAUCE: (no-up) x86/mm: Fixing notify_range_enc_status_changed incorrect
  argument

  * No graphic desktop environment on Google GCP instances (LP: #2039732)
- [Config] gcp: Inherit CONFIG_SYSFB_SIMPLEFB from master

  [ Ubuntu: 5.15.0-89.99 ]

  * jammy/linux: 5.15.0-89.99 -proposed tracker (LP: #2041949)
  * CVE-2023-31085
- ubi: Refuse attaching if mtd's erasesize is 0
  * CVE-2023-45871
- igb: set max size RX buffer when store bad packet is enabled
  * CVE-2023-25775
- RDMA/irdma: Remove irdma_uk_mw_bind()
- RDMA/irdma: Remove irdma_sc_send_lsmm_nostag()
- RDMA/irdma: Remove irdma_cqp_up_map_cmd()
- RDMA/irdma: Remove irdma_get_hw_addr()
- RDMA/irdma: Make irdma_uk_cq_init() return a void
- RDMA/irdma: optimize rx path by removing unnecessary copy
- RDMA/irdma: Remove enum irdma_status_code
- RDMA/irdma: Remove excess error variables
- RDMA/irdma: Prevent zero-length STAG registration
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts

 -- Stefan Bader   Fri, 03 Nov 2023 15:14:39
+0100

** Changed in: linux-gcp (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-25775

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-31085

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-45871

** Changed in: linux-gcp (Ubuntu Lunar)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5090

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5345

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/2039732

Title:
  No graphic desktop environment on Google GCP instances

Status in linux-gcp package in Ubuntu:
  In Progress
Status in linux-gcp source package in Jammy:
  Fix Released
Status in linux-gcp source package in Lunar:
  Fix Released
Status in linux-gcp source package in Mantic:
  Fix Committed

Bug description:
  [Impact]

  * Google reports not being able to display graphic desktop
  environment.

  [Fix]

  * CONFIG_SYSFB_SIMPLEFB was initially enabled in
  https://git.launchpad.net/~ubuntu-
  kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master-
  next=0bf2a2472f71a3001a8a9a0849b6bed7e7069a7b. It was subsequently
  disabled for amd64 in https://git.launchpad.net/~ubuntu-
  kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master-
  next=40b0ce0833309133453c3dbc19753f62084c0a7a. This was not
  reflected in the GCP kernel config.

  [Test Case]

  * Compile tested
  * Boot tested
  * To be tested by Google

  [Where things could go wrong]

  * Low chance of regression. Simple config change that was not taken
  from generic.

  [Other Info]

  * SF #00366439

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2039732/+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 2039925] Re: Realtek RTS5264 SD 7.0 cardreader support

[You-Sheng Yang]

Verified linux-oem-6.5/jammy-proposed version 6.5.0-1009.10.

** Tags removed: verification-needed-jammy-linux-oem-6.5
** Tags added: verification-done-jammy-linux-oem-6.5

-- 
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/2039925

Title:
  Realtek RTS5264 SD 7.0 cardreader support

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Won't Fix
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  Missing Realtek RTS5264 SD 7.0 cardreader support:
  ```
  $ lspci -nnnk
  :56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 
[10ec:5264] (rev 01)
  Subsystem: Dell Device [1028:0cc8]
  Kernel driver in use: rtsx_pci
  Kernel modules: rtsx_pci
  ```

  [Fix]

  V4 patchset under review:
  
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/

  [Test Case]

  With kernel driver probed and loaded successfully, there should be a line in 
the dmesg:
  ```
  rtsx_pci :56:00.0: enabling device ( -> 0002)
  ```

  [Where problems could occur]

  New hardware, expecting all possible way to go wrong.

  [Other Info]

  Nominated for oem-6.5 and Noble.

  == original bug report ==

  Missing Realtek RTS5264 SD 7.0 cardreader support:
  ```
  $ lspci -nnnk
  :56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 
[10ec:5264] (rev 01)
  Subsystem: Dell Device [1028:0cc8]
  Kernel driver in use: rtsx_pci
  Kernel modules: rtsx_pci
  ```

  V4 patchset: 
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5json:
   {
     "result": "skip"
   }
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-magmar+X114
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-11-15 (5 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
somerville-jammy-amd64-20220504-33
  IwConfig:
   lono wireless extensions.

   enx00e04c691040  no wireless extensions.

   wlp1s0f0  no wireless extensions.
  MachineType: Dell Inc. Precision 5690
  Package: linux-oem-6.5
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9008-oem 
root=UUID=b6f2aa0f-7cf0-4307-a7ff-d6af8316c896 ro automatic-oem-config quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-9008.8+exp.31-oem 6.5.3
  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-9008-oem N/A
   linux-backports-modules-6.5.0-9008-oem  N/A
   linux-firmware  
20220329.git681281e4-0ubuntu3.22+exp.90
  Tags:  jammy
  Uname: Linux 6.5.0-9008-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 10/26/2023
  dmi.bios.release: 0.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.2.12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.2.12:bd10/26/2023:br0.2:efr0.0:svnDellInc.:pnPrecision5690:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0CC8:
  dmi.product.family: Precision
  dmi.product.name: Precision 5690
  dmi.product.sku: 0CC8
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2039925/+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 2040337] Re: Incorrect argument from SEV live-migration fix

[Launchpad Bug Tracker]

This bug was fixed in the package linux-gcp - 5.15.0-1047.55

---
linux-gcp (5.15.0-1047.55) jammy; urgency=medium

  * jammy/linux-gcp: 5.15.0-1047.55 -proposed tracker (LP: #2041917)

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/s2023.10.02)

  * Incorrect argument from SEV live-migration fix (LP: #2040337)
- SAUCE: (no-up) x86/mm: Fixing notify_range_enc_status_changed incorrect
  argument

  * No graphic desktop environment on Google GCP instances (LP: #2039732)
- [Config] gcp: Inherit CONFIG_SYSFB_SIMPLEFB from master

  [ Ubuntu: 5.15.0-89.99 ]

  * jammy/linux: 5.15.0-89.99 -proposed tracker (LP: #2041949)
  * CVE-2023-31085
- ubi: Refuse attaching if mtd's erasesize is 0
  * CVE-2023-45871
- igb: set max size RX buffer when store bad packet is enabled
  * CVE-2023-25775
- RDMA/irdma: Remove irdma_uk_mw_bind()
- RDMA/irdma: Remove irdma_sc_send_lsmm_nostag()
- RDMA/irdma: Remove irdma_cqp_up_map_cmd()
- RDMA/irdma: Remove irdma_get_hw_addr()
- RDMA/irdma: Make irdma_uk_cq_init() return a void
- RDMA/irdma: optimize rx path by removing unnecessary copy
- RDMA/irdma: Remove enum irdma_status_code
- RDMA/irdma: Remove excess error variables
- RDMA/irdma: Prevent zero-length STAG registration
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts

 -- Stefan Bader   Fri, 03 Nov 2023 15:14:39
+0100

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/2040337

Title:
  Incorrect argument from SEV live-migration fix

Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Focal:
  Fix Released
Status in linux-gcp source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  * Google requested fix to notify_range_enc_status_changed() passing
  incorrect argument.

  [Fix]

  * Upstream ac3f9c9f1b37 introduced change to 
notify_range_enc_status_changed() to accept page size instead of number of 
pages, but function was not updated. Updating to send correct argument. 
Upstream implementation changed with TDX
  support, and is unaffected, so no plans to upstream.

  [Test Case]

  * Compile tested
  * Boot tested
  * Tested by Google

  [Where things could go wrong]

  * Low chance of regression. Isolated logic fix.

  [Other Info]

  * SF #00367134

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2040337/+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 2040337] Re: Incorrect argument from SEV live-migration fix

[Launchpad Bug Tracker]

This bug was fixed in the package linux-gcp - 5.4.0-1118.127

---
linux-gcp (5.4.0-1118.127) focal; urgency=medium

  * focal/linux-gcp: 5.4.0-1118.127 -proposed tracker (LP: #2041969)

  * Incorrect argument from SEV live-migration fix (LP: #2040337)
- SAUCE: (no-up) x86/mm: Fixing notify_range_enc_status_changed incorrect
  argument

  [ Ubuntu: 5.4.0-167.184 ]

  * focal/linux: 5.4.0-167.184 -proposed tracker (LP: #2041988)
  * CVE-2023-45871
- igb: set max size RX buffer when store bad packet is enabled
  * CVE-2023-31085
- ubi: Refuse attaching if mtd's erasesize is 0
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts

 -- Stefan Bader   Fri, 03 Nov 2023 15:25:48
+0100

** Changed in: linux-gcp (Ubuntu Focal)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-31085

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-45871

** Changed in: linux-gcp (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-25775

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/2040337

Title:
  Incorrect argument from SEV live-migration fix

Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Focal:
  Fix Released
Status in linux-gcp source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  * Google requested fix to notify_range_enc_status_changed() passing
  incorrect argument.

  [Fix]

  * Upstream ac3f9c9f1b37 introduced change to 
notify_range_enc_status_changed() to accept page size instead of number of 
pages, but function was not updated. Updating to send correct argument. 
Upstream implementation changed with TDX
  support, and is unaffected, so no plans to upstream.

  [Test Case]

  * Compile tested
  * Boot tested
  * Tested by Google

  [Where things could go wrong]

  * Low chance of regression. Isolated logic fix.

  [Other Info]

  * SF #00367134

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2040337/+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

[Roxana Nicolescu]

** Tags removed: verification-needed-jammy-linux-lowlatency-hwe-6.5
** Tags added: verification-done-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

[Roxana Nicolescu]

** Tags removed: verification-needed-jammy-linux-lowlatency-hwe-6.5
** Tags added: verification-done-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)

[Roxana Nicolescu]

** Tags removed: verification-needed-jammy-linux-lowlatency-hwe-6.5
** Tags added: verification-done-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

[Roxana Nicolescu]

** Tags removed: verification-needed-jammy-linux-lowlatency-hwe-6.5
** Tags added: verification-done-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 2031412] Re: Support mipi camera on Intel Meteor Lake platform

[Andreas Hasenack]

Generally, it's your call, unless what you mean is that the current
version in unapproved, without the fix for 2044991, is broken/bad/not-
worth-it. Keep in mind that you would be adding another bug to the sru,
requiring again the full SRU template (impact, test plan, validation),
and all of the listed bugs have to be accepted and pass validation for
the SRU to be released to updates.

-- 
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 

[Kernel-packages] [Bug 2043905] Re: VT6307 IEEE1394 card causes reboot loop

[Beyil]

Had a slightly different outcome with the latest kernel (6.5.0-13),  I
put the card in to transfer some data from the firewire device, went to
use the 6.2 kernel but didn't hit the shift in time to get the advanced
grub menu to select it. I got a "Kernel panic unable to locate UUID="
message, and the machine went into a hardlock state (keyboard was
unresponsive). Used the reset button to reboot into kernel 6.2, located
that the UUID it references is for / . rebooted back into the 6.5 kernel
and its back to the reboot loop.

I have been unable to get it to reproduce the "unable to locate"
message.

As soon as the 1394 card is removed it again works on the 6.5 kernel

No log file found.
My VT6307 card has the ASM1083 chip on it.

-- 
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 2031412] Re: Support mipi camera on Intel Meteor Lake platform

[Viral Wang]

Sorry to cut in at the very last moment.

Considering there's a new release tag from upstream code for
ipu6-drivers to fix the Mayabay MLK issue (lp:2044991), shall we include
the changes for ipu6-drivers at this time? Thank you!

** Tags added: block-proposed-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 

[Kernel-packages] [Bug 2038433] Re: systemd autopkgtest regression on arm64 and s390x on mantic

[Juerg Haefliger]

The first container reboot fails because seeding takes too long (which
is bug 1878225). Then the hack kicks in and a second image build is
attempted with also fails. The hack masks the problematic services

9811s Created symlink /etc/systemd/system/snapd.service → /dev/null.
9817s Created symlink /etc/systemd/system/snapd.seeded.service → /dev/null.

but the subsequent reboot still times out. Huh?

-- 
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/2038433

Title:
  systemd autopkgtest regression on arm64 and s390x on mantic

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in linux source package in Mantic:
  Confirmed
Status in systemd source package in Mantic:
  New

Bug description:
  tests-in-lxd seems to fail to download the lxd image used for the test (or 
something similar), looking at the log:
  ...
  Publishing instance: Image pack: 85% (5.51MB/s)

  Instance published with fingerprint: 
83b511be44395f2afc7d4d1ee0708cb18834c8b15cb208c9d218964ed8479114
  6845s autopkgtest [09:11:14]: starting date and time: 2023-10-03 09:11:14+
  6845s autopkgtest [09:11:14]: version 5.28ubuntu1
  6845s autopkgtest [09:11:14]: host autopkgtest; command line: 
/usr/bin/autopkgtest -U -B . --test-name=unit-tests -- lxd 
autopkgtest/ubuntu/mantic/arm64
  7063s : failure: (down) ['mktemp', '--directory', '--tmpdir', 
'autopkgtest.XX'] failed (exit status 1, stderr '')
  7063s autopkgtest [09:14:52]: ERROR: testbed failure: unexpected eof from the 
testbed
  7063s autopkgtest [09:14:52]: test tests-in-lxd: ---]
  7064s autopkgtest [09:14:53]: test tests-in-lxd:  - - - - - - - - - - results 
- - - - - - - - - -
  7064s tests-in-lxd FAIL non-zero exit status 1
  2:40 PM
  ...

  This introduces a regression that is blocking the promotion of new
  kernels in Mantic.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: systemd 253.5-1ubuntu6
  ProcVersionSignature: Ubuntu 6.5.0-5.5.1-lowlatency 6.5.0
  Uname: Linux 6.5.0-5-lowlatency x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  4 14:38:15 2023
  InstallationDate: Installed on 2023-09-25 (9 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-lowlatency 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 2.04
  dmi.board.asset.tag: Default string
  dmi.board.name: G1621-02
  dmi.board.vendor: GPD
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.ec.firmware.release: 2.3
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.04:bd09/01/2022:br5.19:efr2.3:svnGPD:pnG1621-02:pvrDefaultstring:rvnGPD:rnG1621-02:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: G1621-02
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: GPD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038433/+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 2031412] Re: Support mipi camera on Intel Meteor Lake platform

[Andreas Hasenack]

ipu6-drivers in mantic unapproved is addressing more than just this bug:
its changes[1] file lists 2012407 2021740 2026402 2031412.

#2021740 had a question about using a ppa in the test case
#2026402 didn't have a test case, and Timo recently added a comment saying that 
this bug was actually already fixed in mantic

It's not my SRU shift today, but other SRU team members can review these
pending issues and their current status.

1.
https://launchpadlibrarian.net/697874516/ipu6-drivers_0~git202310180730.3f813580-0ubuntu0.23.10.1_source.changes

-- 
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]

  

[Kernel-packages] [Bug 2044657] Re: zfs block cloning file system corruption

[Chad Wagner]

It appears upstream is prepping a 2.1.14 and 2.2.2 release that includes this 
fix to both branches.
https://github.com/openzfs/zfs/pull/15601
https://github.com/openzfs/zfs/pull/15602

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2044657

Title:
  zfs block cloning file system corruption

Status in linux-hwe-6.2 package in Ubuntu:
  New
Status in linux-hwe-6.5 package in Ubuntu:
  New
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/linux-hwe-6.2/+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 2038433] Re: systemd autopkgtest regression on arm64 and s390x on mantic

[Juerg Haefliger]

>From my limited testing, it looks like it was introduced in 6.5.0-10.10.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2038433

Title:
  systemd autopkgtest regression on arm64 and s390x on mantic

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in linux source package in Mantic:
  Confirmed
Status in systemd source package in Mantic:
  New

Bug description:
  tests-in-lxd seems to fail to download the lxd image used for the test (or 
something similar), looking at the log:
  ...
  Publishing instance: Image pack: 85% (5.51MB/s)

  Instance published with fingerprint: 
83b511be44395f2afc7d4d1ee0708cb18834c8b15cb208c9d218964ed8479114
  6845s autopkgtest [09:11:14]: starting date and time: 2023-10-03 09:11:14+
  6845s autopkgtest [09:11:14]: version 5.28ubuntu1
  6845s autopkgtest [09:11:14]: host autopkgtest; command line: 
/usr/bin/autopkgtest -U -B . --test-name=unit-tests -- lxd 
autopkgtest/ubuntu/mantic/arm64
  7063s : failure: (down) ['mktemp', '--directory', '--tmpdir', 
'autopkgtest.XX'] failed (exit status 1, stderr '')
  7063s autopkgtest [09:14:52]: ERROR: testbed failure: unexpected eof from the 
testbed
  7063s autopkgtest [09:14:52]: test tests-in-lxd: ---]
  7064s autopkgtest [09:14:53]: test tests-in-lxd:  - - - - - - - - - - results 
- - - - - - - - - -
  7064s tests-in-lxd FAIL non-zero exit status 1
  2:40 PM
  ...

  This introduces a regression that is blocking the promotion of new
  kernels in Mantic.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: systemd 253.5-1ubuntu6
  ProcVersionSignature: Ubuntu 6.5.0-5.5.1-lowlatency 6.5.0
  Uname: Linux 6.5.0-5-lowlatency x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  4 14:38:15 2023
  InstallationDate: Installed on 2023-09-25 (9 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-lowlatency 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 2.04
  dmi.board.asset.tag: Default string
  dmi.board.name: G1621-02
  dmi.board.vendor: GPD
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.ec.firmware.release: 2.3
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.04:bd09/01/2022:br5.19:efr2.3:svnGPD:pnG1621-02:pvrDefaultstring:rvnGPD:rnG1621-02:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: G1621-02
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: GPD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038433/+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 2038433] Re: systemd autopkgtest regression on arm64 and s390x on mantic

[Juerg Haefliger]

Ok that's not it. It looks like a container reboot takes longer than 1
min with newer kernels resulting in a timeout error and subsequent
failure.

-- 
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/2038433

Title:
  systemd autopkgtest regression on arm64 and s390x on mantic

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in linux source package in Mantic:
  Confirmed
Status in systemd source package in Mantic:
  New

Bug description:
  tests-in-lxd seems to fail to download the lxd image used for the test (or 
something similar), looking at the log:
  ...
  Publishing instance: Image pack: 85% (5.51MB/s)

  Instance published with fingerprint: 
83b511be44395f2afc7d4d1ee0708cb18834c8b15cb208c9d218964ed8479114
  6845s autopkgtest [09:11:14]: starting date and time: 2023-10-03 09:11:14+
  6845s autopkgtest [09:11:14]: version 5.28ubuntu1
  6845s autopkgtest [09:11:14]: host autopkgtest; command line: 
/usr/bin/autopkgtest -U -B . --test-name=unit-tests -- lxd 
autopkgtest/ubuntu/mantic/arm64
  7063s : failure: (down) ['mktemp', '--directory', '--tmpdir', 
'autopkgtest.XX'] failed (exit status 1, stderr '')
  7063s autopkgtest [09:14:52]: ERROR: testbed failure: unexpected eof from the 
testbed
  7063s autopkgtest [09:14:52]: test tests-in-lxd: ---]
  7064s autopkgtest [09:14:53]: test tests-in-lxd:  - - - - - - - - - - results 
- - - - - - - - - -
  7064s tests-in-lxd FAIL non-zero exit status 1
  2:40 PM
  ...

  This introduces a regression that is blocking the promotion of new
  kernels in Mantic.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: systemd 253.5-1ubuntu6
  ProcVersionSignature: Ubuntu 6.5.0-5.5.1-lowlatency 6.5.0
  Uname: Linux 6.5.0-5-lowlatency x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  4 14:38:15 2023
  InstallationDate: Installed on 2023-09-25 (9 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-lowlatency 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 2.04
  dmi.board.asset.tag: Default string
  dmi.board.name: G1621-02
  dmi.board.vendor: GPD
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.ec.firmware.release: 2.3
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.04:bd09/01/2022:br5.19:efr2.3:svnGPD:pnG1621-02:pvrDefaultstring:rvnGPD:rnG1621-02:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: G1621-02
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: GPD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038433/+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 2038433] Re: systemd autopkgtest regression on arm64 and s390x on mantic

[Juerg Haefliger]

2023-11-29T11:00:34.713689+00:00 mantic-test systemd[1]: Reached target 
cloud-init.target - Cloud-init target.
2023-11-29T11:00:34.713731+00:00 mantic-test systemd[1]: Startup finished in 
5.934s.
2023-11-29T11:00:34.766612+00:00 mantic-test systemd[1]: dmesg.service: 
Deactivated successfully.
2023-11-29T11:01:00.318282+00:00 mantic-test systemd[1]: 
systemd-hostnamed.service: Deactivated successfully.
2023-11-29T11:01:03.018207+00:00 mantic-test systemd[1]: 
systemd-timedated.service: Deactivated successfully.
2023-11-29T11:01:51.230419+00:00 mantic-test systemd[1]: Created slice 
user-0.slice - User Slice of UID 0.
2023-11-29T11:01:51.231018+00:00 mantic-test systemd[1]: Starting 
user-runtime-dir@0.service - User Runtime Directory /run/user/0...
2023-11-29T11:01:51.235439+00:00 mantic-test systemd[1]: Finished 
user-runtime-dir@0.service - User Runtime Directory /run/user/0.
2023-11-29T11:01:51.236741+00:00 mantic-test systemd[1]: Starting 
user@0.service - User Manager for UID 0...

-- 
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/2038433

Title:
  systemd autopkgtest regression on arm64 and s390x on mantic

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in linux source package in Mantic:
  Confirmed
Status in systemd source package in Mantic:
  New

Bug description:
  tests-in-lxd seems to fail to download the lxd image used for the test (or 
something similar), looking at the log:
  ...
  Publishing instance: Image pack: 85% (5.51MB/s)

  Instance published with fingerprint: 
83b511be44395f2afc7d4d1ee0708cb18834c8b15cb208c9d218964ed8479114
  6845s autopkgtest [09:11:14]: starting date and time: 2023-10-03 09:11:14+
  6845s autopkgtest [09:11:14]: version 5.28ubuntu1
  6845s autopkgtest [09:11:14]: host autopkgtest; command line: 
/usr/bin/autopkgtest -U -B . --test-name=unit-tests -- lxd 
autopkgtest/ubuntu/mantic/arm64
  7063s : failure: (down) ['mktemp', '--directory', '--tmpdir', 
'autopkgtest.XX'] failed (exit status 1, stderr '')
  7063s autopkgtest [09:14:52]: ERROR: testbed failure: unexpected eof from the 
testbed
  7063s autopkgtest [09:14:52]: test tests-in-lxd: ---]
  7064s autopkgtest [09:14:53]: test tests-in-lxd:  - - - - - - - - - - results 
- - - - - - - - - -
  7064s tests-in-lxd FAIL non-zero exit status 1
  2:40 PM
  ...

  This introduces a regression that is blocking the promotion of new
  kernels in Mantic.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: systemd 253.5-1ubuntu6
  ProcVersionSignature: Ubuntu 6.5.0-5.5.1-lowlatency 6.5.0
  Uname: Linux 6.5.0-5-lowlatency x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  4 14:38:15 2023
  InstallationDate: Installed on 2023-09-25 (9 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-lowlatency 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 2.04
  dmi.board.asset.tag: Default string
  dmi.board.name: G1621-02
  dmi.board.vendor: GPD
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.ec.firmware.release: 2.3
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.04:bd09/01/2022:br5.19:efr2.3:svnGPD:pnG1621-02:pvrDefaultstring:rvnGPD:rnG1621-02:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: G1621-02
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: GPD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038433/+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 2043183] Re: kernel NULL pointer dereference with qBittorrent under heavy

[Petr Tichy]

Found the same running heavy workload with https://questdb.io/

-- 
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/2043183

Title:
  kernel NULL pointer dereference with qBittorrent under heavy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When qBittorrent is running heavy mmap-based I/O workload on XFS, a
  "kernel NULL pointer dereference" pops up in a few hours, making the
  process in D state and I have to reboot the whole system. Stack trace
  is supplied as an attachment.

  Tested affected kernels (all hwe-22.04):

  - linux-image-5.19.0-41-generic
  - linux-image-5.19.0-42-generic
  - linux-image-5.19.0-43-generic
  - linux-image-6.2.0-34-generic
  - linux-image-6.2.0-36-generic

  Tested unaffected (all "stock", non-hwe):

  - linux-image-5.15.0-76-generic
  - (basically every 5.15 is unaffected)
  - linux-image-5.15.0-86-generic
  - linux-image-5.15.0-88-generic

  Based on information gathered online, I believe I am running into the
  exact same problem as
  , also
  

  I believe adding upstream cbc02854331edc6dc22d8b77b6e22e38ebc7dd51
  (first seen in 6.6-rc1, backported to 6.5.3 and 6.1.53) should solve
  this problem. Is this going to happen soon to hwe-22.04?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043183/+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 2043183] Re: kernel NULL pointer dereference with qBittorrent under heavy

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2043183

Title:
  kernel NULL pointer dereference with qBittorrent under heavy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When qBittorrent is running heavy mmap-based I/O workload on XFS, a
  "kernel NULL pointer dereference" pops up in a few hours, making the
  process in D state and I have to reboot the whole system. Stack trace
  is supplied as an attachment.

  Tested affected kernels (all hwe-22.04):

  - linux-image-5.19.0-41-generic
  - linux-image-5.19.0-42-generic
  - linux-image-5.19.0-43-generic
  - linux-image-6.2.0-34-generic
  - linux-image-6.2.0-36-generic

  Tested unaffected (all "stock", non-hwe):

  - linux-image-5.15.0-76-generic
  - (basically every 5.15 is unaffected)
  - linux-image-5.15.0-86-generic
  - linux-image-5.15.0-88-generic

  Based on information gathered online, I believe I am running into the
  exact same problem as
  , also
  

  I believe adding upstream cbc02854331edc6dc22d8b77b6e22e38ebc7dd51
  (first seen in 6.6-rc1, backported to 6.5.3 and 6.1.53) should solve
  this problem. Is this going to happen soon to hwe-22.04?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043183/+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 2045129] [NEW] package libnvidia-extra-535 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/aarch64-linux-gnu/gbm/nvidia-drm_gbm.so', which is also in pa

[mikeshi]

Public bug reported:

just upgrade nvidia driver to 535

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libnvidia-extra-535 (not installed)
Uname: Linux 5.10.104-tegra aarch64
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: arm64
CasperMD5CheckResult: skip
Date: Wed Nov 29 18:06:40 2023
ErrorMessage: trying to overwrite 
'/usr/lib/aarch64-linux-gnu/gbm/nvidia-drm_gbm.so', which is also in package 
nvidia-l4t-gbm 35.2.1-20230124153320
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.10
SourcePackage: nvidia-graphics-drivers-535
Title: package libnvidia-extra-535 (not installed) failed to install/upgrade: 
trying to overwrite '/usr/lib/aarch64-linux-gnu/gbm/nvidia-drm_gbm.so', which 
is also in package nvidia-l4t-gbm 35.2.1-20230124153320
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-535 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package arm64 focal

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu.
https://bugs.launchpad.net/bugs/2045129

Title:
  package libnvidia-extra-535 (not installed) failed to install/upgrade:
  trying to overwrite '/usr/lib/aarch64-linux-gnu/gbm/nvidia-
  drm_gbm.so', which is also in package nvidia-l4t-gbm
  35.2.1-20230124153320

Status in nvidia-graphics-drivers-535 package in Ubuntu:
  New

Bug description:
  just upgrade nvidia driver to 535

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libnvidia-extra-535 (not installed)
  Uname: Linux 5.10.104-tegra aarch64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: arm64
  CasperMD5CheckResult: skip
  Date: Wed Nov 29 18:06:40 2023
  ErrorMessage: trying to overwrite 
'/usr/lib/aarch64-linux-gnu/gbm/nvidia-drm_gbm.so', which is also in package 
nvidia-l4t-gbm 35.2.1-20230124153320
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.10
  SourcePackage: nvidia-graphics-drivers-535
  Title: package libnvidia-extra-535 (not installed) failed to install/upgrade: 
trying to overwrite '/usr/lib/aarch64-linux-gnu/gbm/nvidia-drm_gbm.so', which 
is also in package nvidia-l4t-gbm 35.2.1-20230124153320
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2045129/+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 2038433] Re: systemd autopkgtest regression on arm64 and s390x on mantic

[Juerg Haefliger]

So the workaround for the above in systemd/debian/tests/tests-in-lxd is
problematic?

-- 
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/2038433

Title:
  systemd autopkgtest regression on arm64 and s390x on mantic

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in linux source package in Mantic:
  Confirmed
Status in systemd source package in Mantic:
  New

Bug description:
  tests-in-lxd seems to fail to download the lxd image used for the test (or 
something similar), looking at the log:
  ...
  Publishing instance: Image pack: 85% (5.51MB/s)

  Instance published with fingerprint: 
83b511be44395f2afc7d4d1ee0708cb18834c8b15cb208c9d218964ed8479114
  6845s autopkgtest [09:11:14]: starting date and time: 2023-10-03 09:11:14+
  6845s autopkgtest [09:11:14]: version 5.28ubuntu1
  6845s autopkgtest [09:11:14]: host autopkgtest; command line: 
/usr/bin/autopkgtest -U -B . --test-name=unit-tests -- lxd 
autopkgtest/ubuntu/mantic/arm64
  7063s : failure: (down) ['mktemp', '--directory', '--tmpdir', 
'autopkgtest.XX'] failed (exit status 1, stderr '')
  7063s autopkgtest [09:14:52]: ERROR: testbed failure: unexpected eof from the 
testbed
  7063s autopkgtest [09:14:52]: test tests-in-lxd: ---]
  7064s autopkgtest [09:14:53]: test tests-in-lxd:  - - - - - - - - - - results 
- - - - - - - - - -
  7064s tests-in-lxd FAIL non-zero exit status 1
  2:40 PM
  ...

  This introduces a regression that is blocking the promotion of new
  kernels in Mantic.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: systemd 253.5-1ubuntu6
  ProcVersionSignature: Ubuntu 6.5.0-5.5.1-lowlatency 6.5.0
  Uname: Linux 6.5.0-5-lowlatency x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  4 14:38:15 2023
  InstallationDate: Installed on 2023-09-25 (9 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-lowlatency 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 2.04
  dmi.board.asset.tag: Default string
  dmi.board.name: G1621-02
  dmi.board.vendor: GPD
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.ec.firmware.release: 2.3
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.04:bd09/01/2022:br5.19:efr2.3:svnGPD:pnG1621-02:pvrDefaultstring:rvnGPD:rnG1621-02:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: G1621-02
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: GPD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038433/+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 2038433] Re: systemd autopkgtest regression on arm64 and s390x on mantic

[Juerg Haefliger]

Oh -> bug 1878225

-- 
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/2038433

Title:
  systemd autopkgtest regression on arm64 and s390x on mantic

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in linux source package in Mantic:
  Confirmed
Status in systemd source package in Mantic:
  New

Bug description:
  tests-in-lxd seems to fail to download the lxd image used for the test (or 
something similar), looking at the log:
  ...
  Publishing instance: Image pack: 85% (5.51MB/s)

  Instance published with fingerprint: 
83b511be44395f2afc7d4d1ee0708cb18834c8b15cb208c9d218964ed8479114
  6845s autopkgtest [09:11:14]: starting date and time: 2023-10-03 09:11:14+
  6845s autopkgtest [09:11:14]: version 5.28ubuntu1
  6845s autopkgtest [09:11:14]: host autopkgtest; command line: 
/usr/bin/autopkgtest -U -B . --test-name=unit-tests -- lxd 
autopkgtest/ubuntu/mantic/arm64
  7063s : failure: (down) ['mktemp', '--directory', '--tmpdir', 
'autopkgtest.XX'] failed (exit status 1, stderr '')
  7063s autopkgtest [09:14:52]: ERROR: testbed failure: unexpected eof from the 
testbed
  7063s autopkgtest [09:14:52]: test tests-in-lxd: ---]
  7064s autopkgtest [09:14:53]: test tests-in-lxd:  - - - - - - - - - - results 
- - - - - - - - - -
  7064s tests-in-lxd FAIL non-zero exit status 1
  2:40 PM
  ...

  This introduces a regression that is blocking the promotion of new
  kernels in Mantic.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: systemd 253.5-1ubuntu6
  ProcVersionSignature: Ubuntu 6.5.0-5.5.1-lowlatency 6.5.0
  Uname: Linux 6.5.0-5-lowlatency x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  4 14:38:15 2023
  InstallationDate: Installed on 2023-09-25 (9 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-lowlatency 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 2.04
  dmi.board.asset.tag: Default string
  dmi.board.name: G1621-02
  dmi.board.vendor: GPD
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.ec.firmware.release: 2.3
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.04:bd09/01/2022:br5.19:efr2.3:svnGPD:pnG1621-02:pvrDefaultstring:rvnGPD:rnG1621-02:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: G1621-02
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: GPD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038433/+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 2045079] Re: Lunar update: upstream stable patchset 2023-11-28

[Stefan Bader]

** Changed in: linux (Ubuntu Lunar)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2045079

Title:
  Lunar update: upstream stable patchset 2023-11-28

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Lunar:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2023-11-28

  Ported from the following upstream stable releases:
  v6.1.54, v6.5.4

     from git://git.kernel.org/

  net/ipv6: SKB symmetric hash should incorporate transport ports
  mm: multi-gen LRU: rename lrugen->lists[] to lrugen->folios[]
  Multi-gen LRU: fix per-zone reclaim
  io_uring/net: don't overflow multishot accept
  io_uring: break out of iowq iopoll on teardown
  io_uring/sqpoll: fix io-wq affinity when IORING_SETUP_SQPOLL is used
  io_uring: Don't set affinity on a dying sqpoll thread
  drm/virtio: Conditionally allocate virtio_gpu_fence
  scsi: qla2xxx: Adjust IOCB resource on qpair create
  scsi: qla2xxx: Limit TMF to 8 per function
  scsi: qla2xxx: Fix deletion race condition
  scsi: qla2xxx: fix inconsistent TMF timeout
  scsi: qla2xxx: Fix command flush during TMF
  scsi: qla2xxx: Fix erroneous link up failure
  scsi: qla2xxx: Turn off noisy message log
  scsi: qla2xxx: Fix session hang in gnl
  scsi: qla2xxx: Fix TMF leak through
  scsi: qla2xxx: Remove unsupported ql2xenabledif option
  scsi: qla2xxx: Flush mailbox commands on chip reset
  scsi: qla2xxx: Fix smatch warn for qla_init_iocb_limit()
  scsi: qla2xxx: Error code did not return to upper layer
  scsi: qla2xxx: Fix firmware resource tracking
  null_blk: fix poll request timeout handling
  fbdev/ep93xx-fb: Do not assign to struct fb_info.dev
  clk: qcom: camcc-sc7180: fix async resume during probe
  drm/ast: Fix DRAM init on AST2200
  ASoC: tegra: Fix SFC conversion for few rates
  clk: qcom: turingcc-qcs404: fix missing resume during probe
  arm64: dts: renesas: rzg2l: Fix txdv-skew-psec typos
  send channel sequence number in SMB3 requests after reconnects
  mm: hugetlb_vmemmap: fix a race between vmemmap pmd split
  lib/test_meminit: allocate pages up to order MAX_ORDER
  parisc: led: Fix LAN receive and transmit LEDs
  parisc: led: Reduce CPU overhead for disk & lan LED computation
  cifs: update desired access while requesting for directory lease
  pinctrl: cherryview: fix address_space_handler() argument
  dt-bindings: clock: xlnx,versal-clk: drop select:false
  clk: imx: pll14xx: dynamically configure PLL for 393216000/361267200Hz
  clk: imx: pll14xx: align pdiv with reference manual
  clk: qcom: gcc-mdm9615: use proper parent for pll0_vote clock
  soc: qcom: qmi_encdec: Restrict string length in decode
  clk: qcom: dispcc-sm8450: fix runtime PM imbalance on probe errors
  clk: qcom: lpasscc-sc7280: fix missing resume during probe
  clk: qcom: q6sstop-qcs404: fix missing resume during probe
  clk: qcom: mss-sc7180: fix missing resume during probe
  NFS: Fix a potential data corruption
  NFSv4/pnfs: minor fix for cleanup path in nfs4_get_device_info
  bus: mhi: host: Skip MHI reset if device is in RDDM
  kbuild: rpm-pkg: define _arch conditionally
  kbuild: do not run depmod for 'make modules_sign'
  tpm_crb: Fix an error handling path in crb_acpi_add()
  gfs2: Switch to wait_event in gfs2_logd
  gfs2: low-memory forced flush fixes
  mailbox: qcom-ipcc: fix incorrect num_chans counting
  kconfig: fix possible buffer overflow
  Input: iqs7222 - configure power mode before triggering ATI
  perf trace: Use zfree() to reduce chances of use after free
  perf trace: Really free the evsel->priv area
  pwm: atmel-tcb: Convert to platform remove callback returning void
  pwm: atmel-tcb: Harmonize resource allocation order
  pwm: atmel-tcb: Fix resource freeing in error path and remove
  backlight: gpio_backlight: Drop output GPIO direction check for initial power 
state
  Input: tca6416-keypad - always expect proper IRQ number in i2c client
  Input: tca6416-keypad - fix interrupt enable disbalance
  perf annotate bpf: Don't enclose non-debug code with an assert()
  x86/virt: Drop unnecessary check on extended CPUID level in cpu_has_svm()
  perf vendor events: Update the JSON/events descriptions for power10 platform
  perf vendor events: Drop some of the JSON/events for power10 platform
  perf vendor events: Drop STORES_PER_INST metric event for power10 platform
  perf top: 

[Kernel-packages] [Bug 2038433] Re: systemd autopkgtest regression on arm64 and s390x on mantic

[Juerg Haefliger]

Is seems the container fails to boot. From a bad run:

9109s autopkgtest [10:39:17]: test tests-in-lxd: [---
9145s 2023-11-28T10:39:50Z INFO Waiting for automatic snapd restart...
9259s lxd 5.19-8635f82 from Canonical** installed
9288s Creating autopkgtest-prepare-jhI
9475s Retrieving image: metadata: 100% (323.81MB/s)
  Retrieving image: rootfs: 1% (3.53MB/s)
  
  Retrieving image: rootfs: 100% (8.38MB/s)
  Retrieving image: Unpack: 100% (226.67MB/s)
  Starting autopkgtest-prepare-jhI
9486s Created symlink /etc/systemd/system/serial-getty@getty.service → 
/dev/null.
9490s Failed to connect to bus: No such file or directory
9632s Timed out waiting for container to boot

-- 
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/2038433

Title:
  systemd autopkgtest regression on arm64 and s390x on mantic

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in linux source package in Mantic:
  Confirmed
Status in systemd source package in Mantic:
  New

Bug description:
  tests-in-lxd seems to fail to download the lxd image used for the test (or 
something similar), looking at the log:
  ...
  Publishing instance: Image pack: 85% (5.51MB/s)

  Instance published with fingerprint: 
83b511be44395f2afc7d4d1ee0708cb18834c8b15cb208c9d218964ed8479114
  6845s autopkgtest [09:11:14]: starting date and time: 2023-10-03 09:11:14+
  6845s autopkgtest [09:11:14]: version 5.28ubuntu1
  6845s autopkgtest [09:11:14]: host autopkgtest; command line: 
/usr/bin/autopkgtest -U -B . --test-name=unit-tests -- lxd 
autopkgtest/ubuntu/mantic/arm64
  7063s : failure: (down) ['mktemp', '--directory', '--tmpdir', 
'autopkgtest.XX'] failed (exit status 1, stderr '')
  7063s autopkgtest [09:14:52]: ERROR: testbed failure: unexpected eof from the 
testbed
  7063s autopkgtest [09:14:52]: test tests-in-lxd: ---]
  7064s autopkgtest [09:14:53]: test tests-in-lxd:  - - - - - - - - - - results 
- - - - - - - - - -
  7064s tests-in-lxd FAIL non-zero exit status 1
  2:40 PM
  ...

  This introduces a regression that is blocking the promotion of new
  kernels in Mantic.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: systemd 253.5-1ubuntu6
  ProcVersionSignature: Ubuntu 6.5.0-5.5.1-lowlatency 6.5.0
  Uname: Linux 6.5.0-5-lowlatency x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  4 14:38:15 2023
  InstallationDate: Installed on 2023-09-25 (9 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-lowlatency 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 2.04
  dmi.board.asset.tag: Default string
  dmi.board.name: G1621-02
  dmi.board.vendor: GPD
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.ec.firmware.release: 2.3
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.04:bd09/01/2022:br5.19:efr2.3:svnGPD:pnG1621-02:pvrDefaultstring:rvnGPD:rnG1621-02:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: G1621-02
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: GPD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038433/+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