date:20240411

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

Title:
  Remote filesystems mounted as CIFS not working after update to Kernel
  "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi
  #17-Ubuntu" (aarch64).

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-6.5 package in Ubuntu:
  Confirmed
Status in linux-raspi package in Ubuntu:
  Confirmed

Bug description:
  Remote filesystems mounted as CIFS are not working after update to
  Kernel "6.5.0-27-generic #28-Ubuntu" for x86_64 (and also after
  updating to Kernel "6.5.0-1014-raspi #17-Ubuntu" in aarch64).

  The remote filesystem is correctly mounted and seems to work but
  trying to write data to the filesystem ends in a kernel error
  exception. After that error the CIFS filesystem just became unusable.

  Previous Kernel version works correctly.

  =
  Example for Kernel "6.5.0-27-generic #28-Ubuntu" (x86_64)
  =
  # lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10

  # uname -a
  Linux fpgmsi 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar  7 
18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  # cat /proc/version_signature
  Ubuntu 6.5.0-27.28-generic 6.5.13

  
  How to reproduce the problem
  
  For instance, I'm using KeePassXC 
(https://launchpad.net/ubuntu/+source/keepassxc) to update a database located 
at CIFS filesystem. Any change done to that database causes this Kernel error 
exception:

  abr 11 09:34:59 fpgmsi kernel: BUG: unable to handle page fault for address: 
fffe
  abr 11 09:34:59 fpgmsi kernel: #PF: supervisor read access in kernel mode
  abr 11 09:34:59 fpgmsi kernel: #PF: error_code(0x) - not-present page
  abr 11 09:34:59 fpgmsi kernel: PGD f45a3f067 P4D f45a3f067 PUD f45a41067 PMD 
0 
  abr 11 09:34:59 fpgmsi kernel: Oops:  [#1] PREEMPT SMP NOPTI
  abr 11 09:34:59 fpgmsi kernel: CPU: 0 PID: 28103 Comm: Thread (pooled) 
Tainted: P   OE  6.5.0-27-generic #28-Ubuntu
  abr 11 09:34:59 fpgmsi kernel: Hardware name: Micro-Star International Co., 
Ltd. MAG Z690 Codex X5 (MS-B930)/PRO Z690-A WIFI (MS-7D25), BIOS D.50 04/26/2022
  abr 11 09:34:59 fpgmsi kernel: RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs]
  abr 11 09:34:59 fpgmsi kernel: Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 
0c 53 48 83 ec 08 48 8b 7f 30 44 89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 
db 74 77 <48> 8b 13 b8 00 10 00 00 f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3
  abr 11 09:34:59 fpgmsi kernel: RSP: 0018:aab6865ffbf8 EFLAGS: 00010282
  abr 11 09:34:59 fpgmsi kernel: RAX:  RBX: fffe 
RCX: 
  abr 11 09:34:59 fpgmsi kernel: RDX:  RSI:  
RDI: 
  abr 11 09:34:59 fpgmsi kernel: RBP: aab6865ffc28 R08: 0001 
R09: 
  abr 11 09:34:59 fpgmsi kernel: R10: 00023854 R11:  
R12: 
  abr 11 09:34:59 fpgmsi kernel: R13: aab6865ffc78 R14: 906675d8aed0 
R15: aab6865ffc70
  abr 11 09:34:59 fpgmsi kernel: FS:  7bd4d594b6c0() 
GS:90753f80() knlGS:
  abr 11 09:34:59 fpgmsi kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  abr 11 09:34:59 fpgmsi kernel: CR2: fffe CR3: 00017022a000 
CR4: 00750ef0
  abr 11 09:34:59 fpgmsi kernel: PKRU: 5554
  abr 11 09:34:59 fpgmsi kernel: Call Trace:
  abr 11 09:34:59 fpgmsi kernel:  
  abr 11 09:34:59 fpgmsi kernel:  ? show_regs+0x6d/0x80
  abr 11 09:34:59 fpgmsi kernel:  ? __die+0x24/0x80
  abr 11 09:34:59 fpgmsi kernel:  ? page_fault_oops+0x99/0x1b0
  abr 11 09:34:59 fpgmsi kernel:  ? kernelmode_fixup_or_oops+0xb2/0x140
  abr 11 09:34:59 fpgmsi kernel:  ? __bad_area_nosemaphore+0x1a5/0x2c0
  abr 11 09:34:59 fpgmsi kernel:  ? bad_area_nosemaphore+0x16/0x30
  abr 11 09:34:59 fpgmsi kernel:  ? do_kern_addr_fault+0x7b/0xa0
  abr 11 09:34:59 fpgmsi kernel:  ? exc_page_fault+0x1a4/0x1b0
  abr 11 09:34:59 fpgmsi kernel:  ? asm_exc_page_fault+0x27/0x30
  abr 11 09:34:59 fpgmsi kernel:  ? cifs_flush_folio+0x41/0xf0 [cifs]
  abr 11 09:34:59 fpgmsi kernel:  ? cifs_flush_folio+0x37/0xf0 [cifs]
  abr 11 09:34:59 fpgmsi kernel:  cifs_remap_file_range+0x172/0x660 [cifs]
  abr 11 09:34:59 fpgmsi kernel:  do_clone_file_range+0x101/0x2d0
  abr 11 09:34:59 fpgmsi kernel:  vfs_clone_file_range+0x3f/0x150
  abr 11 09:34:59 fpgmsi kernel:  ioctl_file_clone+0x52/0xc0
  abr 11 09:34:59 fpgmsi kernel:  do_vfs_ioctl+0x68f/0x910
  abr 11 09:34:59 fpgmsi kernel:  ?

[Kernel-packages] [Bug 2061049] Re: Fix random HuC/GuC initialization failure of Intel i915 driver

2024-04-11 Thread Chris Chiu

** Tags added: oem-priority originate-from-2051627 stella

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

Title:
  Fix random HuC/GuC initialization failure of Intel i915 driver

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

Bug description:
  [Impact]
  i915 error can sometimes be found in kernel message when booting the machine 
w/ power unplugged
  kernel: i915 :00:02.0: [drm] *ERROR* GT1: GuC initialization failed -EIO
  kernel: i915 :00:02.0: [drm] *ERROR* GT1: Enabling uc failed (-5)
  kernel: i915 :00:02.0: [drm] *ERROR* GT1: Failed to initialize GPU, 
declaring it wedged!
  The GPU won't work with this failure

  [Fix]
  Backport the upatream fix for allowing slow HuC loading. 

  [Test]
  1. Unplug the power of the laptop and make sure it's charged by battery
  2. Cold boot or Warm boot the machine and check the GuC init fail message.
  3. Go to settings - > about --> graphics to make sure the GPU information is 
correct every boot.

  [Where problems could occur]
  Simply increase the loading time of HuC still get a working system. Should be 
low risk of regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2061049/+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 2061049] [NEW] Fix random HuC/GuC initialization failure of Intel i915 driver

2024-04-11 Thread Chris Chiu

Public bug reported:

[Impact]
i915 error can sometimes be found in kernel message when booting the machine w/ 
power unplugged
kernel: i915 :00:02.0: [drm] *ERROR* GT1: GuC initialization failed -EIO
kernel: i915 :00:02.0: [drm] *ERROR* GT1: Enabling uc failed (-5)
kernel: i915 :00:02.0: [drm] *ERROR* GT1: Failed to initialize GPU, 
declaring it wedged!
The GPU won't work with this failure

[Fix]
Backport the upatream fix for allowing slow HuC loading. 

[Test]
1. Unplug the power of the laptop and make sure it's charged by battery
2. Cold boot or Warm boot the machine and check the GuC init fail message.
3. Go to settings - > about --> graphics to make sure the GPU information is 
correct every boot.

[Where problems could occur]
Simply increase the loading time of HuC still get a working system. Should be 
low risk of regression.

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

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

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

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

** Affects: linux (Ubuntu Jammy)
 Importance: Undecided
 Status: New

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

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

** Affects: linux (Ubuntu Noble)
 Importance: Undecided
 Status: New

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

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


** Tags: oem-priority originate-from-2051627 stella

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

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

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

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

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

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

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

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

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

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

Title:
  Fix random HuC/GuC initialization failure of Intel i915 driver

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

Bug description:
  [Impact]
  i915 error can sometimes be found in kernel message when booting the machine 
w/ power unplugged
  kernel: i915 :00:02.0: [drm] *ERROR* GT1: GuC initialization failed -EIO
  kernel: i915 :00:02.0: [drm] *ERROR* GT1: Enabling uc failed (-5)
  kernel: i915 :00:02.0: [drm] *ERROR* GT1: Failed to initialize GPU, 
declaring it wedged!
  The GPU won't work with this failure

  [Fix]
  Backport the upatream fix for allowing slow HuC loading. 

  [Test]
  1. Unplug the power of the laptop and make sure it's charged by battery
  2. Cold boot or Warm boot the machine and check the GuC init fail message.
  3. Go to settings - > about --> graphics to make sure the GPU information is 
correct every boot.

  [Where problems could occur]
  Simply increase the loading time of HuC still get a working system. Should be 
low risk of regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2061049/+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 1990592] Re: [nouveau] Xorg desktop environment fails to start with QEMU GPU passthrough to NVIDIA

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)

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

Title:
  [nouveau] Xorg desktop environment fails to start with QEMU GPU
  passthrough to NVIDIA

Status in linux package in Ubuntu:
  New
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  A fresh installation of the Kinetic daily image dated 20220920 fails
  to start the graphical environment when using the nouveau drivers and
  I'm only able to log in on the console. The system under test is using
  QEMU w/ GPU passthrough and an NVIDIA GeForce GTX 650 device.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xserver-xorg-video-nouveau 1:1.0.17-2build1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  Date: Thu Sep 22 16:39:27 2022
  DistUpgraded: Fresh install
  DistroCodename: kinetic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 
[VGA controller])
 Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
   NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GK107 [GeForce GTX 650] [3842:2652]
  InstallationDate: Installed on 2022-09-22 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220920)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-6.2
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-6.2:cvnQEMU:ct1:cvrpc-q35-6.2:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-6.2
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.112-3ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.1.7-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu3
  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/1990592/+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 2060914] Re: kernel NULL pointer dereference in ipu6 driver

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)

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

Title:
  kernel NULL pointer dereference in ipu6 driver

Status in linux package in Ubuntu:
  New

Bug description:
  pr 11 14:43:43 OCBYM2-DVT1-C3 kernel: BUG: kernel NULL pointer dereference, 
address: 
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: #PF: supervisor read access in kernel 
mode
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: #PF: error_code(0x) - not-present 
page
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: PGD 0 P4D 0 
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: Oops:  [#1] PREEMPT SMP NOPTI
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: CPU: 16 PID: 568 Comm: (udev-worker) 
Tainted: G   O   6.8.0-22-generic #22-Ubuntu
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: Hardware name: Dell Inc. Precision 
5490/, BIOS 1.1.0 02/07/2024
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RIP: 0010:__wake_up_common+0x2f/0xb0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: Code: 55 48 89 e5 41 57 41 56 41 55 41 
54 53 48 89 fb 48 83 c3 08 48 83 ec 08 48 8b 47 08 89 75 d4 89 55 d0 48 39 c3 
74 51 4d 89 c7 <4c> 8b 00 41 89 ce 48 8d 78 e8 4d 8d 68 e8 eb 25 74 0c 41 83 e4 
01
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RSP: 0018:b5ebc3063768 EFLAGS: 
00010086
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RAX:  RBX: 
8fb79e181d50 RCX: 
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RDX:  RSI: 
0003 RDI: 8fb79e181d48
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RBP: b5ebc3063798 R08: 
 R09: 
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: R10:  R11: 
 R12: 8fb79e181d48
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: R13: 0003 R14: 
0246 R15: 
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: FS:  77cceb6148c0() 
GS:8fc6cf60() knlGS:
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: CR2:  CR3: 
0001068ae003 CR4: 00f70ef0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: DR0:  DR1: 
 DR2: 
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: DR3:  DR6: 
07f0 DR7: 0400
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: PKRU: 5554
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: Call Trace:
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? show_regs+0x6d/0x80
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? __die+0x24/0x80
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? page_fault_oops+0x99/0x1b0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? do_user_addr_fault+0x2ee/0x6b0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? exc_page_fault+0x83/0x1b0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? asm_exc_page_fault+0x27/0x30
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? __wake_up_common+0x2f/0xb0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  __wake_up+0x37/0x70
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  __vb2_queue_cancel+0xcd/0x300 
[videobuf2_common]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  vb2_core_queue_release+0x23/0x70 
[videobuf2_common]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  vb2_queue_release+0xe/0x20 
[videobuf2_v4l2]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ipu_isys_queue_cleanup+0x12/0x20 
[intel_ipu6_isys]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ipu_isys_video_cleanup+0x2e/0x40 
[intel_ipu6_isys]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  
ipu_isys_csi2_be_soc_cleanup+0x37/0x50 [intel_ipu6_isys]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  isys_unregister_subdevices+0x40/0xa0 
[intel_ipu6_isys]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  isys_probe+0x5c5/0xb80 
[intel_ipu6_isys]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? kernfs_create_link+0x66/0xe0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ipu_bus_probe+0x72/0x130 [intel_ipu6]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  really_probe+0x1c4/0x410
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  __driver_probe_device+0x8c/0x180
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  driver_probe_device+0x24/0xd0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  __driver_attach+0x10b/0x210
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? __pfx___driver_attach+0x10/0x10
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  bus_for_each_dev+0x8a/0xf0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  driver_attach+0x1e/0x30
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  bus_add_driver+0x156/0x260
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  driver_register+0x5e/0x130
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? __pfx_isys_driver_init+0x10/0x10 
[intel_ipu6_isys]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ipu_bus_register_driver+0x16/0x20 
[intel_ipu6]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  isys_driver_init+0x15/0xff0

[Kernel-packages] [Bug 2060918] Re: [24.04]: mpt3sas: Feature and critical Bug fix

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)

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

Title:
  [24.04]: mpt3sas: Feature and critical Bug fix

Status in linux package in Ubuntu:
  New

Bug description:
  Below are the upstream commit IDs:

  c0767560b012 : scsi: mpt3sas: Reload SBR without rebooting HBA
  ee0017c3ed8a : scsi: mpt3sas: Prevent sending diag_reset when the controller 
is ready
  a34fc8c7361c : scsi: mpt3sas: Update driver version to 48.100.00.00

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060918/+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 2060924] Re: [Lenovo Ubuntu 24.04 Bug] Can not detect iscsi disk storage and kernel show " detected conn error (1020)"

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)

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

Title:
  [Lenovo Ubuntu 24.04 Bug] Can not detect iscsi disk storage and kernel
  show " detected conn error (1020)"

Status in linux package in Ubuntu:
  New

Bug description:
  Description:
  When installing Ubuntu 24.04 in remote iscsi storage disk, the installer can 
not detect the remote iscsi storage. After install Ubuntu 24.04 to a local disk 
and boot up to OS, the OS can not detect the remote iscsi disk either. 

  Reproduce Steps:
1. Install Ubunut 24.04 
2. Boot into OS
3. perform command lsblk check remote disk, there isn't one appeared.
   
  Configuration:
  System: Lenovo SR655V3
  OS:noble-live-server-amd64-0401.iso
  BMC Version ：2.30 (Build ID: KAX321V)
  UEFI Version:3.10 (Build ID: KAE115K)
  CPU:Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz*2 M321R2GA3BB6-CQKMG*8
  NIC adapter: Mellanox ConnectX-6 Lx 10/25GbE SFP28 2-port PCIe Ethernet 
Adapte 
  storage：Lenovo D7000 or Lenovo V7000

   Expected results:
   OS can recognize the remote iscsi disk

   Actual results:
   OS cannot recognize the remote iscsi disk.

  Additional info:
1. Ubuntu 22.04 also have this issue, But RHEL9.4 hasn't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060924/+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 2060977] Re: gnome crashes when waking from lock

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)

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

Title:
  gnome crashes when waking from lock

Status in linux package in Ubuntu:
  New

Bug description:
  When trying to log in from locked / sleeping desktop, gnome crashed.

  I have three monitors connected via displayport to this card.

  dmesg snip:

  [Thu Apr 11 08:12:57 2024] audit: type=1107 audit(1712844779.171:174815): 
pid=1799 uid=103 auid=4294967295 ses=4294967295 subj=unconfined 
msg='apparmor="DENIED" operation="dbus_signal"  bus="system" 
path="/org/freedesktop/login1" interface="org.freedesktop.DBus.Properties" 
member="PropertiesChanged" name=":1.12" mask="receive" pid=10350 
label="snap.firefox.firefox" peer_pid=1790 peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? 
addr=? terminal=?'
  [Thu Apr 11 08:12:57 2024] rfkill: input handler enabled
  [Thu Apr 11 08:12:58 2024] audit: type=1107 audit(1712844779.588:174816): 
pid=1799 uid=103 auid=4294967295 ses=4294967295 subj=unconfined 
msg='apparmor="DENIED" operation="dbus_signal"  bus="system" 
path="/org/freedesktop/login1" interface="org.freedesktop.login1.Manager" 
member="SessionRemoved" name=":1.12" mask="receive" pid=10350 
label="snap.firefox.firefox" peer_pid=1790 peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? 
addr=? terminal=?'
  [Thu Apr 11 08:12:58 2024] audit: type=1107 audit(1712844779.698:174817): 
pid=1799 uid=103 auid=4294967295 ses=4294967295 subj=unconfined 
msg='apparmor="DENIED" operation="dbus_signal"  bus="system" 
path="/org/freedesktop/login1" interface="org.freedesktop.login1.Manager" 
member="UserNew" name=":1.12" mask="receive" pid=10350 
label="snap.firefox.firefox" peer_pid=1790 peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? 
addr=? terminal=?'
  [Thu Apr 11 08:12:58 2024] audit: type=1400 audit(1712844779.700:174818): 
apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" 
name="/proc/10350/environ" pid=553296 comm="firefox" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=1000
  [Thu Apr 11 08:12:58 2024] audit: type=1107 audit(1712844779.710:174819): 
pid=1799 uid=103 auid=4294967295 ses=4294967295 subj=unconfined 
msg='apparmor="DENIED" operation="dbus_signal"  bus="system" 
path="/org/freedesktop/login1" interface="org.freedesktop.login1.Manager" 
member="SessionNew" name=":1.12" mask="receive" pid=10350 
label="snap.firefox.firefox" peer_pid=1790 peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? 
addr=? terminal=?'
  [Thu Apr 11 08:12:59 2024] overlayfs: fs on 
'/var/lib/gdm3/.local/share/containers/storage/overlay/compat1995007933/lower1' 
does not support file handles, falling back to xino=off.
  [Thu Apr 11 08:12:59 2024] overlayfs: fs on 
'/var/lib/gdm3/.local/share/containers/storage/overlay/metacopy-check1285164697/l1'
 does not support file handles, falling back to xino=off.
  [Thu Apr 11 08:12:59 2024] overlayfs: fs on 
'/var/lib/gdm3/.local/share/containers/storage/overlay/opaque-bug-check3491611924/l2'
 does not support file handles, falling back to xino=off.
  [Thu Apr 11 08:12:59 2024] snd_hda_codec_hdmi hdaudioC0D0: HDMI: Unknown ELD 
version 0
  [Thu Apr 11 08:13:01 2024] rfkill: input handler disabled
  [Thu Apr 11 08:13:02 2024] [drm:retrieve_link_cap [amdgpu]] *ERROR* 
retrieve_link_cap: Read receiver caps dpcd data failed.
  [Thu Apr 11 08:13:07 2024] rfkill: input handler enabled
  [Thu Apr 11 08:13:08 2024] rfkill: input handler disabled
  [Thu Apr 11 08:13:10 2024] audit: type=1107 audit(1712844791.998:174820): 
pid=1799 uid=103 auid=4294967295 ses=4294967295 subj=unconfined 
msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" 
path="/org/freedesktop/PolicyKit1/Authority" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name=":1.14" pid=555445 label="snap.snap-store.snap-store" peer_pid=1820 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? 
addr=? terminal=?'
  [Thu Apr 11 08:13:10 2024] audit: type=1107 audit(1712844791.999:174821): 
pid=1799 uid=103 auid=4294967295 ses=4294967295 subj=unconfined 
msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" 
path="/org/freedesktop/PolicyKit1/Authority" 
interface="org.freedesktop.PolicyKit1.Authority" member="CheckAuthorization" 
mask="send" name=":1.14" pid=555445 label="snap.snap-store.snap-store" 
peer_pid=1820 peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? 
addr=? terminal=?'

  
  journalctl -u gdm

  -- Boot f2ce6f5ac44d413f8e6a1ba80a0bee53 --
  Apr 08 09:11:10 arc

[Kernel-packages] [Bug 2060981] Re: ACPI BIOS errors

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Anthony Wong (anthonywong)

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

Title:
  ACPI BIOS errors

Status in linux package in Ubuntu:
  New

Bug description:
  dmesg show the below ACPI errors, is this normal?

  
  # dmesg | grep -i acpi
  [0.00] BIOS-e820: [mem 0x59cf8000-0x59dc3fff] ACPI 
data
  [0.00] BIOS-e820: [mem 0x59dc4000-0x59eb] ACPI NVS
  [0.00] reserve setup_data: [mem 
0x59cf8000-0x59dc3fff] ACPI data
  [0.00] reserve setup_data: [mem 
0x59dc4000-0x59eb] ACPI NVS
  [0.00] efi: ACPI=0x59dc3000 ACPI 2.0=0x59dc3014 
TPMFinalLog=0x59e4a000 SMBIOS=0x5a609000 SMBIOS 3.0=0x5a608000 
MEMATTR=0x528f6018 ESRT=0x53983818 MOKvar=0x5a5e4000 INITRD=0x4fde3f98 
RNG=0x59d28018 TPMEventLog=0x4fdc7018 
  [0.020042] ACPI: Early table checksum verification disabled
  [0.020046] ACPI: RSDP 0x59DC3014 24 (v02 _ASUS_)
  [0.020052] ACPI: XSDT 0x59DC2728 00011C (v01 _ASUS_ Notebook 
01072009 AMI  0113)
  [0.020060] ACPI: FACP 0x59DBD000 000114 (v06 _ASUS_ Notebook 
01072009 AMI  00010013)
  [0.020066] ACPI: DSDT 0x59D6 05C524 (v02 _ASUS_ Notebook 
01072009 INTL 20191018)
  [0.020070] ACPI: FACS 0x59EBC000 40
  [0.020074] ACPI: MCFG 0x59DC1000 3C (v01 _ASUS_ Notebook 
01072009 MSFT 0097)
  [0.020077] ACPI: SSDT 0x59DBE000 00255D (v02 CpuRef CpuSsdt  
3000 INTL 20191018)
  [0.020081] ACPI: FIDT 0x59D5F000 9C (v01 _ASUS_ Notebook 
01072009 AMI  00010013)
  [0.020084] ACPI: ECDT 0x59D5E000 C1 (v01 _ASUS_ Notebook 
01072009 AMI. 0005)
  [0.020088] ACPI: MSDM 0x59D5D000 55 (v03 _ASUS_ Notebook 
01072009 ASUS 0001)
  [0.020092] ACPI: SSDT 0x59D58000 004F42 (v02 DptfTa DptfTabl 
1000 INTL 20191018)
  [0.020095] ACPI: SSDT 0x59D56000 0017B5 (v02 SaSsdt SaSsdt   
3000 INTL 20191018)
  [0.020099] ACPI: SSDT 0x59D52000 003350 (v02 INTEL  IgfxSsdt 
3000 INTL 20191018)
  [0.020103] ACPI: SSDT 0x59D46000 00B1B2 (v02 INTEL  TcssSsdt 
1000 INTL 20191018)
  [0.020106] ACPI: HPET 0x59D45000 38 (v01 _ASUS_ Notebook 
01072009 AMI  0113)
  [0.020110] ACPI: APIC 0x59D44000 00012C (v04 _ASUS_ Notebook 
01072009 AMI  0113)
  [0.020114] ACPI: SSDT 0x59D43000 0002A7 (v02 _ASUS_ TcssSsdt 
 INTL 20191018)
  [0.020118] ACPI: SSDT 0x59D3B000 007504 (v02 _ASUS_ TglU_Rvp 
1000 INTL 20191018)
  [0.020122] ACPI: NHLT 0x59D39000 001B54 (v00 _ASUS_ Notebook 
01072009 AMI  0113)
  [0.020126] ACPI: LPIT 0x59D38000 CC (v01 _ASUS_ Notebook 
01072009 AMI  0113)
  [0.020129] ACPI: SSDT 0x59D36000 00012A (v02 _ASUS_ TbtTypeC 
 INTL 20191018)
  [0.020133] ACPI: DBGP 0x59D35000 34 (v01 _ASUS_ Notebook 
01072009 AMI  0113)
  [0.020137] ACPI: DBG2 0x59D34000 54 (v00 _ASUS_ Notebook 
01072009 AMI  0113)
  [0.020141] ACPI: SSDT 0x59D33000 000D8A (v02 _ASUS_ UsbCTabl 
1000 INTL 20191018)
  [0.020145] ACPI: DMAR 0x59D32000 B8 (v02 INTEL  EDK2 
0002  0113)
  [0.020148] ACPI: SSDT 0x59D31000 0004B8 (v02 HgRef  HgRpSsdt 
1000 INTL 20191018)
  [0.020152] ACPI: SSDT 0x59D3 000144 (v02 Intel  ADebTabl 
1000 INTL 20191018)
  [0.020155] ACPI: BGRT 0x59D2F000 38 (v01 _ASUS_ Notebook 
01072009 AMI  00010013)
  [0.020159] ACPI: UEFI 0x59E28000 00063A (v01 INTEL  RstVmdE  
 ??   )
  [0.020163] ACPI: UEFI 0x59E27000 5C (v01 INTEL  RstVmdV  
 ??   )
  [0.020166] ACPI: TPM2 0x59D2E000 4C (v04 _ASUS_ Notebook 
0001 AMI  )
  [0.020170] ACPI: SSDT 0x59D2B000 002495 (v01 OptRf1 Opt1Tabl 
1000 INTL 20191018)
  [0.020173] ACPI: PTDT 0x59D2A000 000D44 (v00 _ASUS_ Notebook 
0005 MSFT 010D)
  [0.020177] ACPI: WSMT 0x59D37000 28 (v01 _ASUS_ Notebook 
01072009 AMI  00010013)
  [0.020181] ACPI: FPDT 0x59D29000 44 (v01 _ASUS_ A M I
01072009 AMI  0113)
  [0.020184] ACPI: Reserving FACP table memory at [mem 
0x59dbd000-0x59dbd113]
  [0.020186] ACPI: Reserving DSDT table memory at [mem 
0x59d6-0x59dbc523]
  [0.020187] ACPI: Reserving FACS table memory at [mem 
0x59ebc000-0x59ebc03f]
  [0.020187] ACPI: Reserving MCFG table memory at [mem 
0x59dc1000-0x59dc103b]
  [0.020188] ACPI: Reserving SSDT table memory at [mem 
0x59dbe000-0x59dc055c]
  [0.020189] ACPI: Reserving FIDT table memory at [mem 
0x59d5f000-0x59d5f09b]
  [

[Kernel-packages] [Bug 2060989] Re: package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to install/upgrade: installed linux-headers-6.5.0-27-generic package post-installation script subprocess r

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Anthony Wong (anthonywong)

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

Title:
  package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to
  install/upgrade: installed linux-headers-6.5.0-27-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  -

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: linux-headers-6.5.0-27-generic 6.5.0-27.28
  ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nela   2694 F wireplumber
   /dev/snd/controlC1:  nela   2694 F wireplumber
   /dev/snd/seq:nela   2674 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Thu Apr 11 10:13:36 2024
  ErrorMessage: installed linux-headers-6.5.0-27-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2024-03-30 (12 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic 
root=UUID=e960f11c-d239-429e-97af-9073de7f3b3a ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to 
install/upgrade: installed linux-headers-6.5.0-27-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: HACN27WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion S7 15ACH6
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrHACN27WW:bd08/02/2021:br1.27:efr1.27:svnLENOVO:pn82K8:pvrLegionS715ACH6:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegionS715ACH6:skuLENOVO_MT_82K8_BU_idea_FM_LegionS715ACH6:
  dmi.product.family: Legion S7 15ACH6
  dmi.product.name: 82K8
  dmi.product.sku: LENOVO_MT_82K8_BU_idea_FM_Legion S7 15ACH6
  dmi.product.version: Legion S7 15ACH6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060989/+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 2060770] Re: NVMe drive fails at high write workload after kernel upgrades

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Anthony Wong (anthonywong)

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

Title:
  NVMe drive fails at high write workload after kernel upgrades

Status in linux package in Ubuntu:
  New

Bug description:
  My problem is similarly described in this old thread:
  https://unix.stackexchange.com/questions/742360/

  journalctl message: one of the many related logs
  Apr 09 15:37:40.096850 ** kernel: Linux version 6.5.0-26-lowlatency 
(buildd@lcy02-amd64-109) (x86_64-linux-gnu-gcc-12 (Ubunntu 
12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) 
#26.1~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Mar 13 10:41:42 UTC (Ubuntu 
6.5.0-26.26.1~22.04.1-lowlatency 6.5.13)
  
  Apr 09 15:43:46.238697 ** kernel: nvme nvme0: controller is down; will 
reset: CSTS=0x, PCI_STATUS=0x10
  Apr 09 15:43:46.239162 ** kernel: nvme nvme0: Does your device have a 
faulty power saving mode enabled?
  Apr 09 15:43:46.239266 ** kernel: nvme nvme0: Try 
"nvme_core.default_ps_max_latency_us=0 pcie_aspm=off" and report a bug
  Apr 09 15:43:46.690200 ** kernel: nvme :06:00.0: enabling device 
( -> 0002)
  Apr 09 15:43:46.690409 ** kernel: nvme nvme0: Disabling device after 
reset failure: -19
  Apr 09 15:43:46.698188 ** kernel: I/O error, dev nvme0n1, sector 1216896 
op 0x1:(WRITE) flags 0xc800 phys_seg 1 prio clas>

  I was using 22.04.4 with hwe kernel, as shown above (kernel 6.5)
  upgrade to 24.04 dev hoping the problem would be resolved, but no it still 
exists (kernel 6.8)

  The problem happens after some kernel upgrades that I'd done after
  2024-03-01, but I cannot pinpoint when; the nvme_core kernel param as
  shown in the message above does not help.

  The problem does NOT exist with 22.04 regular kernel:
  Currently I'd created a VM to perform my heavy write workload using pci 
passthrough of the NVMe drive, and it works okay.  Cannot downgrade host to 
older kernel because of ZFS pool being upgraded

  VM info (where my NVMe drive works okay)

  uname -r
  5.15.0-78-lowlatency

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 22.04.4 LTS
  Release:22.04
  Codename:   jammy

  (maybe) related hardware spec
  CPU: AMD Ryzen 5750G (x8x4x4)
  Chipset: AMD B450
  NVMe: Samsung MZ1LB960HBJR-000FB (PM983a, f/w EDW73F2Q)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060770/+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 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Jose Ogando Justo (joseogando)

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

Title:
  Remote filesystems mounted as CIFS not working after update to Kernel
  "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi
  #17-Ubuntu" (aarch64).

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in linux-raspi package in Ubuntu:
  Confirmed

Bug description:
  Remote filesystems mounted as CIFS are not working after update to
  Kernel "6.5.0-27-generic #28-Ubuntu" for x86_64 (and also after
  updating to Kernel "6.5.0-1014-raspi #17-Ubuntu" in aarch64).

  The remote filesystem is correctly mounted and seems to work but
  trying to write data to the filesystem ends in a kernel error
  exception. After that error the CIFS filesystem just became unusable.

  Previous Kernel version works correctly.

  =
  Example for Kernel "6.5.0-27-generic #28-Ubuntu" (x86_64)
  =
  # lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10

  # uname -a
  Linux fpgmsi 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar  7 
18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  # cat /proc/version_signature
  Ubuntu 6.5.0-27.28-generic 6.5.13

  
  How to reproduce the problem
  
  For instance, I'm using KeePassXC 
(https://launchpad.net/ubuntu/+source/keepassxc) to update a database located 
at CIFS filesystem. Any change done to that database causes this Kernel error 
exception:

  abr 11 09:34:59 fpgmsi kernel: BUG: unable to handle page fault for address: 
fffe
  abr 11 09:34:59 fpgmsi kernel: #PF: supervisor read access in kernel mode
  abr 11 09:34:59 fpgmsi kernel: #PF: error_code(0x) - not-present page
  abr 11 09:34:59 fpgmsi kernel: PGD f45a3f067 P4D f45a3f067 PUD f45a41067 PMD 
0 
  abr 11 09:34:59 fpgmsi kernel: Oops:  [#1] PREEMPT SMP NOPTI
  abr 11 09:34:59 fpgmsi kernel: CPU: 0 PID: 28103 Comm: Thread (pooled) 
Tainted: P   OE  6.5.0-27-generic #28-Ubuntu
  abr 11 09:34:59 fpgmsi kernel: Hardware name: Micro-Star International Co., 
Ltd. MAG Z690 Codex X5 (MS-B930)/PRO Z690-A WIFI (MS-7D25), BIOS D.50 04/26/2022
  abr 11 09:34:59 fpgmsi kernel: RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs]
  abr 11 09:34:59 fpgmsi kernel: Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 
0c 53 48 83 ec 08 48 8b 7f 30 44 89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 
db 74 77 <48> 8b 13 b8 00 10 00 00 f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3
  abr 11 09:34:59 fpgmsi kernel: RSP: 0018:aab6865ffbf8 EFLAGS: 00010282
  abr 11 09:34:59 fpgmsi kernel: RAX:  RBX: fffe 
RCX: 
  abr 11 09:34:59 fpgmsi kernel: RDX:  RSI:  
RDI: 
  abr 11 09:34:59 fpgmsi kernel: RBP: aab6865ffc28 R08: 0001 
R09: 
  abr 11 09:34:59 fpgmsi kernel: R10: 00023854 R11:  
R12: 
  abr 11 09:34:59 fpgmsi kernel: R13: aab6865ffc78 R14: 906675d8aed0 
R15: aab6865ffc70
  abr 11 09:34:59 fpgmsi kernel: FS:  7bd4d594b6c0() 
GS:90753f80() knlGS:
  abr 11 09:34:59 fpgmsi kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  abr 11 09:34:59 fpgmsi kernel: CR2: fffe CR3: 00017022a000 
CR4: 00750ef0
  abr 11 09:34:59 fpgmsi kernel: PKRU: 5554
  abr 11 09:34:59 fpgmsi kernel: Call Trace:
  abr 11 09:34:59 fpgmsi kernel:  
  abr 11 09:34:59 fpgmsi kernel:  ? show_regs+0x6d/0x80
  abr 11 09:34:59 fpgmsi kernel:  ? __die+0x24/0x80
  abr 11 09:34:59 fpgmsi kernel:  ? page_fault_oops+0x99/0x1b0
  abr 11 09:34:59 fpgmsi kernel:  ? kernelmode_fixup_or_oops+0xb2/0x140
  abr 11 09:34:59 fpgmsi kernel:  ? __bad_area_nosemaphore+0x1a5/0x2c0
  abr 11 09:34:59 fpgmsi kernel:  ? bad_area_nosemaphore+0x16/0x30
  abr 11 09:34:59 fpgmsi kernel:  ? do_kern_addr_fault+0x7b/0xa0
  abr 11 09:34:59 fpgmsi kernel:  ? exc_page_fault+0x1a4/0x1b0
  abr 11 09:34:59 fpgmsi kernel:  ? asm_exc_page_fault+0x27/0x30
  abr 11 09:34:59 fpgmsi kernel:  ? cifs_flush_folio+0x41/0xf0 [cifs]
  abr 11 09:34:59 fpgmsi kernel:  ? cifs_flush_folio+0x37/0xf0 [cifs]
  abr 11 09:34:59 fpgmsi kernel:  cifs_remap_file_range+0x172/0x660 [cifs]
  abr 11 09:34:59 fpgmsi kernel:  do_clone_file_range+0x101/0x2d0
  abr 11 09:34:59 fpgmsi kernel:  vfs_clone_file_range+0x3f/0x150
  abr 11 09:34:59 fpgmsi kernel:  ioctl_file_clone+0x52/0xc0
  abr 11 09:34:59 fpgmsi kernel:  do_vfs_ioctl+0x68f/0x910
  abr 11 09:34:59 fpgmsi kernel:  ? __fget_light+0xa5/0x120
  abr 11 09:34:59 fpgmsi kernel:

[Kernel-packages] [Bug 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

** Changed in: linux (Ubuntu Noble)
 Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)

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

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Noble:
  Confirmed

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060904] Re: Fix the RTL8852CE BT FW Crash based on SER false alarm

2024-04-11 Thread Hui Wang

** Changed in: linux-firmware (Ubuntu Jammy)
   Importance: Undecided => Medium

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

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

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

** Changed in: linux-firmware (Ubuntu Noble)
   Importance: Undecided => Medium

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

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

Title:
  Fix the RTL8852CE BT FW Crash based on SER false alarm

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

Bug description:
  This SRU template is for linux-firmware:

  BugLink: https://bugs.launchpad.net/bugs/2060904

  [Impact]

  On a Dell laptop, let it connect to a WiFi router, connect a BT
  device, then disconnect it, connect the bt device again, we expect
  the device could be connected successfully, but it couldn't and
  the BT firmeware crashed.

  [Fix]

  Need to upgrade the firmware for RTL8852CE and cherry-pick 2 kernel
  patches, here we send the MR for firmware first. And it is backward
  compatible, the upgraded firmware could work with kernel without
  those 2 patches as well as before.

  [Test Case]

  With the upgraded firmware + kernel without the 2 kernel patches,
  the wifi and bt could work as well / bad as before.

  With the upgraded firmware + kernel with the 2 kernel patches, bt
  firmware will not crash anymore and bt could connect / disconnect
  many many bt devices.

  [Where problems could occur]

  This MR comes from upstream commit, it has low possibility to
  introduce regression. If the bt or wifi on this laptop couldn't
  work as well as before, it is possible that this MR introduces
  regression. According to our test, the wifi and bt could work well
  with upgraded firmware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2060904/+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 2058740] Re: New upstream relase 535.161.08

This bug was fixed in the package libnvidia-nscq-535 -
535.161.08-0ubuntu3.20.04.1

---
libnvidia-nscq-535 (535.161.08-0ubuntu3.20.04.1) focal; urgency=medium

  * New Upstream release (LP: #2058740)

 -- Kuba Pawlak   Tue, 26 Mar 2024 11:41:41
+0100

** Changed in: libnvidia-nscq-535 (Ubuntu Focal)
   Status: New => Fix Released

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

Title:
  New upstream relase 535.161.08

Status in fabric-manager-535 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-535 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:
  Fix Released
Status in fabric-manager-535 source package in Bionic:
  New
Status in libnvidia-nscq-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535-server source package in Bionic:
  New
Status in fabric-manager-535 source package in Focal:
  Fix Released
Status in libnvidia-nscq-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Focal:
  New
Status in nvidia-graphics-drivers-535-server source package in Focal:
  Fix Released
Status in fabric-manager-535 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Jammy:
  New
Status in nvidia-graphics-drivers-535-server source package in Jammy:
  Fix Released
Status in fabric-manager-535 source package in Mantic:
  Fix Released
Status in libnvidia-nscq-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Mantic:
  New
Status in nvidia-graphics-drivers-535-server source package in Mantic:
  Fix Released
Status in fabric-manager-535 source package in Noble:
  Fix Released
Status in libnvidia-nscq-535 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Noble:
  New
Status in nvidia-graphics-drivers-535-server source package in Noble:
  Fix Released

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2058740/+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 2061040] [NEW] I2C HID device sometimes fails to initialize causing touchpad to not work

2024-04-11 Thread Haw Loeung

Public bug reported:

Hi,

Touchpad on my new Lenovo X1 Carbon (Gen12) with the Sensel haptic pad
doesn't work on boot. I see this:

| [Thu Apr 11 13:57:26 2024] i2c_hid_acpi i2c-SNSL0028:00: device did not ack 
reset within 1000 ms
| [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item 
tag 0x0
| [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item 
tag 0x0
| [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item 
tag 0x0
| [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item 
tag 0x0
| [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item 
tag 0x0
| [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item 
tag 0x0
| [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item 
tag 0x0
| [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item 
tag 0x0
| [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item 
tag 0x0
| [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item 
tag 0x0
| [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main item 
tag 0x0
| ...
| [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unbalanced 
collection at end of report description
| [Thu Apr 11 13:57:26 2024] hid-generic: probe of 0018:2C2F:0028.0001 failed 
with error -22

Per the Arch Linux wiki page[1], removing and reloading the
`i2c_hid_acpi` seems to fix it:

| [Thu Apr 11 13:58:02 2024] i2c_hid_acpi i2c-SNSL0028:00: device did not ack 
reset within 1000 ms
| [Thu Apr 11 13:58:02 2024] input: SNSL0028:00 2C2F:0028 Mouse as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-15/i2c-SNSL0028:00/0018:2C2F:0028.0002/input/input15
| [Thu Apr 11 13:58:02 2024] input: SNSL0028:00 2C2F:0028 Touchpad as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-15/i2c-SNSL0028:00/0018:2C2F:0028.0002/input/input16
| [Thu Apr 11 13:58:02 2024] hid-multitouch 0018:2C2F:0028.0002: input,hidraw0: 
I2C HID v1.00 Mouse [SNSL0028:00 2C2F:0028] on i2c-SNSL0028:00
| [Thu Apr 11 13:58:03 2024] psmouse serio1: trackpoint: Synaptics TrackPoint 
firmware: 0x08, buttons: 3/3
| [Thu Apr 11 13:58:03 2024] input: TPPS/2 Synaptics TrackPoint as 
/devices/platform/i8042/serio1/input/input18

>From that Arch Linux wiki page, it seems to be a bug upstream[2] with
the commit fixing this:

|
https://github.com/torvalds/linux/commit/af93a167eda90192563bce64c4bb989836afac1f

Or

| https://lore.kernel.org/linux-
input/20240331182440.14477-1...@kl.wtf/T/#u

Can we get fix this backported?

| [hloeung@dharkan tmp]$ apt-cache policy linux-image-generic-hwe-24.04
| linux-image-generic-hwe-24.04:
|   Installed: 6.8.0-22.22
|   Candidate: 6.8.0-22.22
|   Version table:
|  *** 6.8.0-22.22 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
| 100 /var/lib/dpkg/status
| [hloeung@dharkan tmp]$ uname -a
| Linux dharkan.local 6.8.0-22-generic #22-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr  
4 22:30:32 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
| [hloeung@dharkan tmp]$

Thanks,

Haw

[1]: https://wiki.archlinux.org/title/Lenovo_ThinkPad_Z16_Gen_2
[2]: https://bugzilla.redhat.com/show_bug.cgi?id=2271136

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

** Affects: linux (Ubuntu Noble)
 Importance: Undecided
 Status: New


** Tags: noble

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

** Tags added: noble

** Description changed:

  Hi,
  
  Touchpad on my new Lenovo X1 Carbon (Gen12) with the Sensel haptic pad
  doesn't work on boot. I see this:
  
  | [Thu Apr 11 13:57:26 2024] i2c_hid_acpi i2c-SNSL0028:00: device did not ack 
reset within 1000 ms
  | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main 
item tag 0x0
  | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main 
item tag 0x0
  | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main 
item tag 0x0
  | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main 
item tag 0x0
  | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main 
item tag 0x0
  | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main 
item tag 0x0
  | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main 
item tag 0x0
  | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main 
item tag 0x0
  | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main 
item tag 0x0
  | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main 
item tag 0x0
  | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main 
item tag 0x0
  | ...
  | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unbalanced 
collection at end of report description
  | [Thu Apr 11 13:57:26 2024] hid-generic: probe of

[Kernel-packages] [Bug 2060748] Re: iwlwifi error popping up every few minutes in Kubuntu 23.10 using Intel AX210 card

2024-04-11 Thread Jess Ferments

If it is helpful, I have output from "trace-cmd record -e iwlwifi -e
mac80211 -e cfg80211 -e iwlwifi_msg" from when the error is occuring. If
there are any other things that would help debugging this, I am happy to
provide more info.

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

Title:
  iwlwifi error popping up every few minutes in Kubuntu 23.10 using
  Intel AX210 card

Status in linux package in Ubuntu:
  New

Bug description:
  I just installed Kubuntu 23.10 (using latest default kernel) on a new
  desktop PC I built, which uses an AX210NGW DTK M.2 wifi/bluetooth
  card. Here is output from lspci -v:

  e4:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 
160MHz (rev 1a)
Subsystem: Intel Corporation Wi-Fi 6 AX210 160MHz
Flags: bus master, fast devsel, latency 0, IRQ 381, IOMMU group 15
Memory at ba30 (64-bit, non-prefetchable) [size=16K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [40] Express Endpoint, MSI 00
Capabilities: [80] MSI-X: Enable+ Count=16 Masked-
Capabilities: [100] Advanced Error Reporting
Capabilities: [14c] Latency Tolerance Reporting
Capabilities: [154] L1 PM Substates
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

  

  Wifi error popping up every few minutes in Kubuntu
  I just installed Kubuntu 23.10 on a new desktop PC I built, which uses an 
AX210NGW DTK M.2 wifi card:

  Code:

  e4:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 
160MHz (rev 1a)
Subsystem: Intel Corporation Wi-Fi 6 AX210 160MHz
Flags: bus master, fast devsel, latency 0, IRQ 381, IOMMU group 15
Memory at ba30 (64-bit, non-prefetchable) [size=16K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [40] Express Endpoint, MSI 00
Capabilities: [80] MSI-X: Enable+ Count=16 Masked-
Capabilities: [100] Advanced Error Reporting
Capabilities: [14c] Latency Tolerance Reporting
Capabilities: [154] L1 PM Substates
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

  The internet seems to be somewhat working, but at least once a minute
  I have two "Network Management" error notifications that pop up in KDE
  that say "Connection Wired Connection 3 deactivated" and "Wired
  Interface e2x52e8ae7d39d1: IP configuration was unavailable".

  I checked the logs in /var/log/dmesg and saw that there were a ton of
  iwlwifi error messages in there that look like this:

  [   44.926474] kernel: Intel(R) Wireless WiFi driver for Linux
  [   44.926508] kernel: iwlwifi :e4:00.0: enabling device ( -> 0002)
  [   44.927758] kernel: iwlwifi :e4:00.0: Detected crf-id 0x400410, cnv-id 
0x400410 wfpm id 0x8000
  [   44.927763] kernel: iwlwifi :e4:00.0: PCI dev 2725/0024, rev=0x420, 
rfid=0x10d000
  [   44.931064] kernel: iwlwifi :e4:00.0: api flags index 2 larger than 
supported by driver
  [   44.931076] kernel: iwlwifi :e4:00.0: TLV_FW_FSEQ_VERSION: FSEQ 
Version: 0.0.2.41
  [   44.931318] kernel: iwlwifi :e4:00.0: loaded firmware version 
83.e8f84e98.0 ty-a0-gf-a0-83.ucode op_mode iwlmvm
  [   44.955070] kernel: Bluetooth: Core ver 2.22
  [   44.955089] kernel: NET: Registered PF_BLUETOOTH protocol family
  [   44.955090] kernel: Bluetooth: HCI device and connection manager 
initialized
  [   44.955095] kernel: Bluetooth: HCI socket layer initialized
  [   44.955097] kernel: Bluetooth: L2CAP socket layer initialized
  [   44.955101] kernel: Bluetooth: SCO socket layer initialized
  [   45.275827] kernel: Bluetooth: hci0: Device revision is 0
  [   45.275833] kernel: Bluetooth: hci0: Secure boot is enabled
  [   45.275836] kernel: Bluetooth: hci0: OTP lock is enabled
  [   45.275838] kernel: Bluetooth: hci0: API lock is enabled
  [   45.275840] kernel: Bluetooth: hci0: Debug lock is disabled
  [   45.275842] kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [   45.275845] kernel: Bluetooth: hci0: Bootloader timestamp 2019.40 
buildtype 1 build 38
  [   45.276888] kernel: nvidia :c1:00.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=none:owns=none
  [   45.278400] kernel: Bluetooth: hci0: Found device firmware: 
intel/ibt-0041-0041.sfi
  [   45.278415] kernel: Bluetooth: hci0: Boot Address: 0x100800
  [   45.278416] kernel: Bluetooth: hci0: Firmware Version: 254-28.23
  [   47.405919] kernel: iwlwifi :e4:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20
  [   47.405936] kernel: iwlwifi :e4:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
  [   47.405945] kernel: iwlwifi :e4:00.0: WFPM_AUTH_KEY_0: 0x90
  [   47.405955] kernel: iwlwifi :e4:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0

[Kernel-packages] [Bug 2058740] Re: New upstream relase 535.161.08

This bug was fixed in the package fabric-manager-535 -
535.161.08-0ubuntu3.23.10.1

---
fabric-manager-535 (535.161.08-0ubuntu3.23.10.1) mantic; urgency=medium

  * New Upstream release (LP: #2058740)

 -- Kuba Pawlak   Tue, 26 Mar 2024 12:04:44
+0100

** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Mantic)
   Status: New => Fix Released

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

Title:
  New upstream relase 535.161.08

Status in fabric-manager-535 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-535 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:
  Fix Released
Status in fabric-manager-535 source package in Bionic:
  New
Status in libnvidia-nscq-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535-server source package in Bionic:
  New
Status in fabric-manager-535 source package in Focal:
  Fix Released
Status in libnvidia-nscq-535 source package in Focal:
  New
Status in nvidia-graphics-drivers-535 source package in Focal:
  New
Status in nvidia-graphics-drivers-535-server source package in Focal:
  Fix Released
Status in fabric-manager-535 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Jammy:
  New
Status in nvidia-graphics-drivers-535-server source package in Jammy:
  Fix Released
Status in fabric-manager-535 source package in Mantic:
  Fix Released
Status in libnvidia-nscq-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Mantic:
  New
Status in nvidia-graphics-drivers-535-server source package in Mantic:
  Fix Released
Status in fabric-manager-535 source package in Noble:
  Fix Released
Status in libnvidia-nscq-535 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Noble:
  New
Status in nvidia-graphics-drivers-535-server source package in Noble:
  Fix Released

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2058740/+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 2058740] Re: New upstream relase 535.161.08

This bug was fixed in the package libnvidia-nscq-535 -
535.161.08-0ubuntu3.23.10.1

---
libnvidia-nscq-535 (535.161.08-0ubuntu3.23.10.1) mantic; urgency=medium

  * New Upstream release (LP: #2058740)

 -- Kuba Pawlak   Tue, 26 Mar 2024 11:32:13
+0100

** Changed in: fabric-manager-535 (Ubuntu Mantic)
   Status: New => Fix Released

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

Title:
  New upstream relase 535.161.08

Status in fabric-manager-535 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-535 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:
  Fix Released
Status in fabric-manager-535 source package in Bionic:
  New
Status in libnvidia-nscq-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535-server source package in Bionic:
  New
Status in fabric-manager-535 source package in Focal:
  Fix Released
Status in libnvidia-nscq-535 source package in Focal:
  New
Status in nvidia-graphics-drivers-535 source package in Focal:
  New
Status in nvidia-graphics-drivers-535-server source package in Focal:
  Fix Released
Status in fabric-manager-535 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Jammy:
  New
Status in nvidia-graphics-drivers-535-server source package in Jammy:
  Fix Released
Status in fabric-manager-535 source package in Mantic:
  Fix Released
Status in libnvidia-nscq-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Mantic:
  New
Status in nvidia-graphics-drivers-535-server source package in Mantic:
  Fix Released
Status in fabric-manager-535 source package in Noble:
  Fix Released
Status in libnvidia-nscq-535 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Noble:
  New
Status in nvidia-graphics-drivers-535-server source package in Noble:
  Fix Released

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2058740/+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 2058740] Re: New upstream relase 535.161.08

This bug was fixed in the package fabric-manager-535 -
535.161.08-0ubuntu3.20.04.1

---
fabric-manager-535 (535.161.08-0ubuntu3.20.04.1) focal; urgency=medium

  * New Upstream release (LP: #2058740)

 -- Kuba Pawlak   Tue, 26 Mar 2024 12:13:02
+0100

** Changed in: fabric-manager-535 (Ubuntu Focal)
   Status: New => Fix Released

** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Focal)
   Status: New => Fix Released

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

Title:
  New upstream relase 535.161.08

Status in fabric-manager-535 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-535 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:
  Fix Released
Status in fabric-manager-535 source package in Bionic:
  New
Status in libnvidia-nscq-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535-server source package in Bionic:
  New
Status in fabric-manager-535 source package in Focal:
  Fix Released
Status in libnvidia-nscq-535 source package in Focal:
  New
Status in nvidia-graphics-drivers-535 source package in Focal:
  New
Status in nvidia-graphics-drivers-535-server source package in Focal:
  Fix Released
Status in fabric-manager-535 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Jammy:
  New
Status in nvidia-graphics-drivers-535-server source package in Jammy:
  Fix Released
Status in fabric-manager-535 source package in Mantic:
  Fix Released
Status in libnvidia-nscq-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Mantic:
  New
Status in nvidia-graphics-drivers-535-server source package in Mantic:
  Fix Released
Status in fabric-manager-535 source package in Noble:
  Fix Released
Status in libnvidia-nscq-535 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Noble:
  New
Status in nvidia-graphics-drivers-535-server source package in Noble:
  Fix Released

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2058740/+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 2058740] Re: New upstream relase 535.161.08

This bug was fixed in the package fabric-manager-535 -
535.161.08-0ubuntu3.22.04.1

---
fabric-manager-535 (535.161.08-0ubuntu3.22.04.1) jammy; urgency=medium

  * New Upstream release (LP: #2058740)

 -- Kuba Pawlak   Tue, 26 Mar 2024 12:06:45
+0100

** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Jammy)
   Status: New => Fix Released

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

Title:
  New upstream relase 535.161.08

Status in fabric-manager-535 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-535 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:
  Fix Released
Status in fabric-manager-535 source package in Bionic:
  New
Status in libnvidia-nscq-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535-server source package in Bionic:
  New
Status in fabric-manager-535 source package in Focal:
  Fix Released
Status in libnvidia-nscq-535 source package in Focal:
  New
Status in nvidia-graphics-drivers-535 source package in Focal:
  New
Status in nvidia-graphics-drivers-535-server source package in Focal:
  Fix Released
Status in fabric-manager-535 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Jammy:
  New
Status in nvidia-graphics-drivers-535-server source package in Jammy:
  Fix Released
Status in fabric-manager-535 source package in Mantic:
  Fix Released
Status in libnvidia-nscq-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Mantic:
  New
Status in nvidia-graphics-drivers-535-server source package in Mantic:
  Fix Released
Status in fabric-manager-535 source package in Noble:
  Fix Released
Status in libnvidia-nscq-535 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Noble:
  New
Status in nvidia-graphics-drivers-535-server source package in Noble:
  Fix Released

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2058740/+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 2059147] Re: New upstream relase 535.171.04

This bug was fixed in the package nvidia-graphics-drivers-535 -
535.171.04-0ubuntu0.22.04.1

---
nvidia-graphics-drivers-535 (535.171.04-0ubuntu0.22.04.1) jammy; urgency=medium

  * New upstream release (LP: #2059147)

 -- Bartlomiej Zolnierkiewicz 
Tue, 26 Mar 2024 19:24:18 +0100

** Changed in: nvidia-graphics-drivers-535 (Ubuntu Jammy)
   Status: New => Fix Released

** Changed in: nvidia-graphics-drivers-535 (Ubuntu Mantic)
   Status: New => Fix Released

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

Title:
  New upstream relase 535.171.04

Status in nvidia-graphics-drivers-535 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Noble:
  New

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2059147/+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 2058740] Re: New upstream relase 535.161.08

This bug was fixed in the package nvidia-graphics-drivers-535-server -
535.161.08-0ubuntu2.22.04.1

---
nvidia-graphics-drivers-535-server (535.161.08-0ubuntu2.22.04.1) jammy; 
urgency=medium

  * New Upstream release (LP: #2058740)

 -- Kuba Pawlak   Tue, 26 Mar 2024 15:25:16
+0100

** Changed in: libnvidia-nscq-535 (Ubuntu Mantic)
   Status: New => Fix Released

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

Title:
  New upstream relase 535.161.08

Status in fabric-manager-535 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-535 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:
  Fix Released
Status in fabric-manager-535 source package in Bionic:
  New
Status in libnvidia-nscq-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535-server source package in Bionic:
  New
Status in fabric-manager-535 source package in Focal:
  Fix Released
Status in libnvidia-nscq-535 source package in Focal:
  New
Status in nvidia-graphics-drivers-535 source package in Focal:
  New
Status in nvidia-graphics-drivers-535-server source package in Focal:
  Fix Released
Status in fabric-manager-535 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Jammy:
  New
Status in nvidia-graphics-drivers-535-server source package in Jammy:
  Fix Released
Status in fabric-manager-535 source package in Mantic:
  Fix Released
Status in libnvidia-nscq-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Mantic:
  New
Status in nvidia-graphics-drivers-535-server source package in Mantic:
  Fix Released
Status in fabric-manager-535 source package in Noble:
  Fix Released
Status in libnvidia-nscq-535 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Noble:
  New
Status in nvidia-graphics-drivers-535-server source package in Noble:
  Fix Released

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2058740/+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 2058740] Re: New upstream relase 535.161.08

This bug was fixed in the package nvidia-graphics-drivers-535-server -
535.161.08-0ubuntu2.20.04.1

---
nvidia-graphics-drivers-535-server (535.161.08-0ubuntu2.20.04.1) focal; 
urgency=medium

  * New Upstream release (LP: #2058740)

 -- Kuba Pawlak   Tue, 26 Mar 2024 15:34:20
+0100

** Changed in: libnvidia-nscq-535 (Ubuntu Jammy)
   Status: New => Fix Released

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

Title:
  New upstream relase 535.161.08

Status in fabric-manager-535 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-535 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:
  Fix Released
Status in fabric-manager-535 source package in Bionic:
  New
Status in libnvidia-nscq-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535-server source package in Bionic:
  New
Status in fabric-manager-535 source package in Focal:
  Fix Released
Status in libnvidia-nscq-535 source package in Focal:
  New
Status in nvidia-graphics-drivers-535 source package in Focal:
  New
Status in nvidia-graphics-drivers-535-server source package in Focal:
  Fix Released
Status in fabric-manager-535 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Jammy:
  New
Status in nvidia-graphics-drivers-535-server source package in Jammy:
  Fix Released
Status in fabric-manager-535 source package in Mantic:
  Fix Released
Status in libnvidia-nscq-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Mantic:
  New
Status in nvidia-graphics-drivers-535-server source package in Mantic:
  Fix Released
Status in fabric-manager-535 source package in Noble:
  Fix Released
Status in libnvidia-nscq-535 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Noble:
  New
Status in nvidia-graphics-drivers-535-server source package in Noble:
  Fix Released

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2058740/+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 2058740] Re: New upstream relase 535.161.08

This bug was fixed in the package libnvidia-nscq-535 -
535.161.08-0ubuntu3.22.04.1

---
libnvidia-nscq-535 (535.161.08-0ubuntu3.22.04.1) jammy; urgency=medium

  * New Upstream release (LP: #2058740)

 -- Kuba Pawlak   Tue, 26 Mar 2024 11:38:50
+0100

** Changed in: fabric-manager-535 (Ubuntu Jammy)
   Status: New => Fix Released

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

Title:
  New upstream relase 535.161.08

Status in fabric-manager-535 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-535 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:
  Fix Released
Status in fabric-manager-535 source package in Bionic:
  New
Status in libnvidia-nscq-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535-server source package in Bionic:
  New
Status in fabric-manager-535 source package in Focal:
  Fix Released
Status in libnvidia-nscq-535 source package in Focal:
  New
Status in nvidia-graphics-drivers-535 source package in Focal:
  New
Status in nvidia-graphics-drivers-535-server source package in Focal:
  Fix Released
Status in fabric-manager-535 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Jammy:
  New
Status in nvidia-graphics-drivers-535-server source package in Jammy:
  Fix Released
Status in fabric-manager-535 source package in Mantic:
  Fix Released
Status in libnvidia-nscq-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Mantic:
  New
Status in nvidia-graphics-drivers-535-server source package in Mantic:
  Fix Released
Status in fabric-manager-535 source package in Noble:
  Fix Released
Status in libnvidia-nscq-535 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Noble:
  New
Status in nvidia-graphics-drivers-535-server source package in Noble:
  Fix Released

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2058740/+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 2059147] Re: New upstream relase 535.171.04

This bug was fixed in the package nvidia-graphics-drivers-535 -
535.171.04-0ubuntu0.20.04.1

---
nvidia-graphics-drivers-535 (535.171.04-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream release (LP: #2059147)

 -- Bartlomiej Zolnierkiewicz 
Tue, 26 Mar 2024 20:18:27 +0100

** Changed in: nvidia-graphics-drivers-535 (Ubuntu Focal)
   Status: New => Fix Released

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

Title:
  New upstream relase 535.171.04

Status in nvidia-graphics-drivers-535 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Noble:
  New

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2059147/+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 1929791] Re: Bluetooth does not start if system boots from USB

2024-04-11 Thread Dave Jones

I haven't managed to reproduce this on several systems (pi4 booting from
USB, pi5 booting from NVMe, etc). Setting to incomplete until anyone can
come up with a firm reproduction case.

** Changed in: pi-bluetooth (Ubuntu)
   Status: New => Incomplete

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

Title:
  Bluetooth does not start if system boots from USB

Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in pi-bluetooth package in Ubuntu:
  Incomplete

Bug description:
  Hello! I have a strange bug with Bluetooth on Raspberry Pi 4 8Gb and Ubuntu 
21.04 (also had it on Ubuntu 20.10). It's internal Bluetooth adapder does not 
initialize, if I boot system from USB, wherein does not matter what I am using: 
16 Gb USB Flash Drive, 2 Tb External USB HDD or 1 Tb External SSD. After system 
boot up, it shows me "no Bluetooth adapters found", hcidev also shows nothing. 
I'm getting hciuart.service error:
  ===
  taras@taras-rpi:~$ systemctl status hciuart.service
  ● hciuart.service - Configure Bluetooth Modems connected by UART
   Loaded: loaded (/lib/systemd/system/hciuart.service; enabled; vendor 
prese>
   Active: failed (Result: exit-code) since Thu 2021-05-27 08:22:57 EEST; 
3mi>
  Process: 599 ExecStart=/usr/bin/btuart (code=exited, status=1/FAILURE)

  тра 27 08:22:46 taras-rpi systemd[1]: Starting Configure Bluetooth Modems 
conne>
  тра 27 08:22:57 taras-rpi btuart[631]: Initialization timed out.
  тра 27 08:22:57 taras-rpi btuart[631]: bcm43xx_init
  тра 27 08:22:57 taras-rpi btuart[631]: Flash firmware 
/lib/firmware/brcm/BCM434>
  тра 27 08:22:57 taras-rpi btuart[631]: Set Controller UART speed to 300 
bit>
  тра 27 08:22:57 taras-rpi systemd[1]: hciuart.service: Control process 
exited, >
  тра 27 08:22:57 taras-rpi systemd[1]: hciuart.service: Failed with result 
'exit>
  тра 27 08:22:57 taras-rpi systemd[1]: Failed to start Configure Bluetooth 
Modem>
  ===
  But if I continue reboot system, it may appear in 1-2 cases from 10. It'v 
very strange.
  If I disable this service manually via:
  ===
  sudo systemctl disable hciuart.service
  ===
  restart the system and run:
  ===
  sudo systemctl start hciuart.service
  ===
  Bluetooth adapter will appear in 100% cases. And if I boot Ubuntu from 
microSD card, everything works properly, Bluetooth starts all times. I thought, 
mb here is not enougth power for USB devices. I've bought USB hub with external 
power, but it does not help.
  Must say, that I don't have this problem on Raspberry Pi OS, I have it on USB 
HDD too and it works without any problems.
  Any suggestions?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1929791/+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 2060217] Re: NFSv4 fails to mount in noble/s390x

2024-04-11 Thread Andreas Hasenack

Adding a release notes task to put a note under "known issues".

** Also affects: ubuntu-release-notes
   Importance: Undecided
   Status: New

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

Title:
  NFSv4 fails to mount in noble/s390x

Status in Release Notes for Ubuntu:
  New
Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New
Status in nfs-utils package in Ubuntu:
  Invalid

Bug description:
  https://autopkgtest.ubuntu.com/packages/n/nfs-utils/noble/s390x

  Looks like it has been failing for a long time already.

  Log: https://autopkgtest.ubuntu.com/results/autopkgtest-
  noble/noble/s390x/n/nfs-utils/20240404_145924_ef255@/log.gz

  339s autopkgtest [14:41:04]: test local-server-client: 
[---
  340s Killed
  340s autopkgtest [14:41:05]: test process requested reboot with marker boot1
  364s autopkgtest-virt-ssh: WARNING: ssh connection failed. Retrying in 3 
seconds...
  372s FAIL: nfs_home not mounted
  373s autopkgtest [14:41:38]: test local-server-client: 
---]
  373s local-server-client  FAIL non-zero exit status 1

  and

  934s autopkgtest [14:50:59]: test kerberos-mount: [---
  935s Initializing database '/var/lib/krb5kdc/principal' for realm 'DEP8',
  935s master key name 'K/M@DEP8'
  935s Authenticating as principal root/admin@DEP8 with password.
  935s Principal "nfs/nfs-server.dep8@DEP8" created.
  935s Authenticating as principal root/admin@DEP8 with password.
  935s Entry for principal nfs/nfs-server.dep8 with kvno 2, encryption type 
aes256-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab.
  935s Entry for principal nfs/nfs-server.dep8 with kvno 2, encryption type 
aes128-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab.
  935s Authenticating as principal root/admin@DEP8 with password.
  935s Principal "host/nfs-server.dep8@DEP8" created.
  935s Authenticating as principal root/admin@DEP8 with password.
  935s Entry for principal host/nfs-server.dep8 with kvno 2, encryption type 
aes256-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab.
  935s Entry for principal host/nfs-server.dep8 with kvno 2, encryption type 
aes128-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab.
  936s exporting *:/storage
  938s mount.nfs: mount system call failed for /mnt
  938s umount: /mnt: not mounted.
  938s autopkgtest [14:51:02]: test kerberos-mount: ---]
  939s kerberos-mount   FAIL non-zero exit status 32

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2060217/+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 2056757] Re: The booting process blocked in 6.5.0-25 during systemd-resolve start phase

2024-04-11 Thread François Bobot

It was not fixed in 6.5.0-26 but it seems solved in 6.5.0-27.

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

Title:
  The booting process blocked in 6.5.0-25 during systemd-resolve start
  phase

Status in linux package in Ubuntu:
  New

Bug description:
  Since booting in 6.5.0-25-generic some kworker thread were stuck. This
  problem with iwlwifi was new. Booting back in 6.5.0-21-generic solved
  the problem.

  This was a suspicious new error:

  ```
  kernel: iwlwifi :3b:00.0: Error sending MCC_UPDATE_CMD: time out after 
2000ms.
  kernel: iwlwifi :3b:00.0: Current CMD queue read_ptr 16 write_ptr 17
  kernel: iwlwifi :3b:00.0: DEVICE_ENABLED bit is not set. Aborting dump.
  kernel: iwlwifi :3b:00.0: Queue 0 is active on fifo 7 and stuck for 2500 
ms. SW [16, 17] HW [17, 17] FH TRB=0x0700010
  ```

  example of blocked kworkers:

  ```
  kernel: INFO: task kworker/0:1:9 blocked for more than 120 seconds.
  kernel:   Not tainted 6.5.0-25-generic #25-Ubuntu
  kernel: task:kworker/0:1 state:D stack:0 pid:9 ppid:2  
flags:0x4000
  kernel: Workqueue: events cfg80211_rfkill_block_work [cfg80211]
  ```

  ```
  kernel: INFO: task irq/173-iwlwifi:945 blocked for more than 120 seconds.
  kernel: task:irq/173-iwlwifi state:D stack:0 pid:945   ppid:2  
flags:0x4000
  ```

  ```
  kernel: INFO: task modprobe:947 blocked for more than 120 seconds.
  kernel:   Not tainted 6.5.0-25-generic #25-Ubuntu
  kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
  kernel: task:modprobestate:D stack:0 pid:947   ppid:583
flags:0x4002

  ```

  
  ```
  kernel: INFO: task kworker/u32:10:1016 blocked for more than 120 seconds.
  kernel: task:kworker/u32:10  state:D stack:0 pid:1016  ppid:2  
flags:0x4000
  kernel: Workqueue: events_power_efficient reg_check_chans_work [cfg80211]
  ```

  ```
  kernel: INFO: task systemd-resolve:1093 blocked for more than 120 seconds.
  kernel: task:systemd-resolve state:D stack:0 pid:1093  ppid:1  
flags:0x0006
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-modules-extra-6.5.0-25-generic 6.5.0-25.25
  ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
  Uname: Linux 6.5.0-21-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 11 11:41:51 2024
  Dependencies:
   linux-modules-6.5.0-25-generic 6.5.0-25.25
   wireless-regdb 2022.06.06-0ubuntu2
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-10-21 (1237 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/zsh
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-21-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-21-generic N/A
   linux-backports-modules-6.5.0-21-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-11-13 (119 days ago)
  dmi.bios.date: 10/11/2021
  dmi.bios.release: 1.14
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.1
  dmi.board.name: 024X86
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.1:bd10/11/2021:br1.14:svnDellInc.:pnPrecision5540:pvr:rvnDellInc.:rn024X86:rvrA04:cvnDellInc.:ct10:cvr:sku0906:
  dmi.product.family: Precision
  dmi.product.name: Precision 5540
  dmi.product.sku: 0906
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056757/+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 2061006] [NEW] aws: KVM and guest support for the PSCI SYSTEM_OFF2 (hibernate) call

2024-04-11 Thread Philip Cox

Public bug reported:

SRU Justification:

[Impact]
PSCI v1.3 adds support for SYSTEM_OFF2 which is analogous to ACPI S4 state.

This will allow hosting environments to determine that a guest is
hibernated rather than just powered off, and ensure that they preserve
the virtual environment appropriately to allow the guest to resume
safely (or bump the hardware_signature in the FACS to trigger a clean
reboot instead).

[Fix]
This adds support for it to KVM, and to the guest hibernate code.

https://lore.kernel.org/lkml/20240312135958.727765-1-dw...@infradead.org

[Test Plan]
AWS tested.

[Where problems could occur]
If the final spec of the PSCI v1.3 changes, there may be changes required to 
this patch series.

[Other Info]

SF# 00383181

** Affects: linux-aws (Ubuntu)
 Importance: Undecided
 Assignee: Philip Cox (philcox)
 Status: New

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

Title:
  aws: KVM and guest support for the PSCI SYSTEM_OFF2 (hibernate) call

Status in linux-aws package in Ubuntu:
  New

Bug description:
  SRU Justification:

  [Impact]
  PSCI v1.3 adds support for SYSTEM_OFF2 which is analogous to ACPI S4 state.

  This will allow hosting environments to determine that a guest is
  hibernated rather than just powered off, and ensure that they preserve
  the virtual environment appropriately to allow the guest to resume
  safely (or bump the hardware_signature in the FACS to trigger a clean
  reboot instead).

  [Fix]
  This adds support for it to KVM, and to the guest hibernate code.

  https://lore.kernel.org/lkml/20240312135958.727765-1-dw...@infradead.org

  [Test Plan]
  AWS tested.

  [Where problems could occur]
  If the final spec of the PSCI v1.3 changes, there may be changes required to 
this patch series.

  [Other Info]

  SF# 00383181

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2061006/+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 2060992] Re: aws: Guest kernel support for clean boot on demand

2024-04-11 Thread Philip Cox

** Description changed:

SRU Justification:

[Impact]
The FACS field in the ACPI table is optional, but can be used communicate the
hardware_signature field. If this field changes on resuming from a hibernation
a clean reboot should happen rather than the resume from hibernation.

On hardware reduced platforms[0] this field may exist but it is not
exposed currently.

[Fix]
Expose this field even on hardware reduced platforms.

https://lore.kernel.org/lkml/20240312134148.727454-1-dw...@infradead.org

[Test Plan]
AWS test.

[Where problems could occur]
- If on hardware reduced platforms that incorrectly support/advertise the FACS
field, hibernation may break if it returns a hardware signature that changes.
+ If on hardware reduced platforms that incorrectly support/advertise the FACS
field, hibernation may break if it returns a hardware signature that changes.

+ [Other info]
+ SF# 00383181

[0]: See Section 4.1 of the ACPI spec for info on hardware-reduced platforms.

https://uefi.org/htmlspecs/ACPI_Spec_6_4_html/04_ACPI_Hardware_Specification/ACPI_Hardware_Specification.html

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

Title:
aws: Guest kernel support for clean boot on demand

Status in linux-aws package in Ubuntu:
New

Bug description:
SRU Justification:

On hardware reduced platforms[0] this field may exist but it is not
exposed currently.

[Fix]
Expose this field even on hardware reduced platforms.

https://lore.kernel.org/lkml/20240312134148.727454-1-dw...@infradead.org

[Test Plan]
AWS test.

[Where problems could occur]
If on hardware reduced platforms that incorrectly support/advertise the FACS
field, hibernation may break if it returns a hardware signature that changes.

[Other info]
SF# 00383181

[0]: See Section 4.1 of the ACPI spec for info on hardware-reduced platforms.

https://uefi.org/htmlspecs/ACPI_Spec_6_4_html/04_ACPI_Hardware_Specification/ACPI_Hardware_Specification.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2060992/+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 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)

2024-04-11 Thread Matthieu Baerts

Hi Dann,

Thank you for doing that!

Is there something I can do to help?

Note that I published the modifications I did [1] in a dedicated PPA
[2]. This was a merge with Debian.

If it is no longer needed to support Ubuntu FAN -- see my comment in #3
-- all Ubuntu-specific patches can be removed, and a simple "sync" with
Debian can be done instead.

[1] 
https://code.launchpad.net/~matttbe/ubuntu/+source/iproute2/+git/iproute2/+ref/merge-lp2051672-noble
[2] https://launchpad.net/~matttbe/+archive/ubuntu/iproute2-lp2051672

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

Title:
  [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from
  testing/unstable (main)

Status in iproute2 package in Ubuntu:
  Confirmed

Bug description:
  A few versions have been released and Ubuntu Noble still has the 6.1
  version (6.1.0-1ubuntu2) from one year ago. Could it be possible to
  import the latest version from Debian unstable fixing a bunch of
  issues and supporting features from more recent kernels?

  Please note that Ubuntu Noble 24.04 will probably be shipped with the
  v6.8 kernel [1]. IPRoute v6.1 supports features added up to the v6.1
  kernel, so missing the ones added to earlier versions. Switching to
  the v6.7 now should ease the upgrade to the v6.8 later.

  [1] https://discourse.ubuntu.com/t/introducing-kernel-6-8-for-
  the-24-04-noble-numbat-release/41958

  Upstream ChangeLog:

  - 6.2: https://lore.kernel.org/netdev/20230220105811.674bd304@hermes.local/
  - 6.3: https://lore.kernel.org/netdev/20230427090253.7a92616b@hermes.local/
  - 6.4: https://lore.kernel.org/netdev/20230626093137.2f302acc@hermes.local/
  - 6.5: https://lore.kernel.org/netdev/20230906093918.394a1b1d@hermes.local/
  - 6.6: https://lore.kernel.org/netdev/20231106090325.07092c87@hermes.local/
  - 6.7: https://lore.kernel.org/netdev/20240108094709.050e22bc@hermes.local/
  - 6.8: https://lore.kernel.org/netdev/20240311094432.16bf9516@hermes.local/

  (Previous changelog:
  
https://lore.kernel.org/netdev/?q=s%3A%22%5BANNOUNCE%5D+iproute2%22+AND+NOT+s%3A%22Re%3A%22
  )

  ChangeLog from Debian:

  iproute2 (6.8.0-1) unstable; urgency=medium

[ Ceppo ]
* Update Italian po-debconf translation (Closes: #1063002)

[ Luca Boccassi ]
* Add build dependency on libnsl-dev (Closes: #1065214)
* Switch to pkgconf
* Update upstream source from tag 'upstream/6.8.0'
* Drop 0002-ss-show-extra-info-when-processes-is-not-used.patch, merged
  upstream
* Drop iproute2-doc package
* Drop tc/m_xt.so and tc/m_ipt.so, removed upstream

   -- Luca Boccassi <>  Tue, 12 Mar 2024 14:02:38 +

  iproute2 (6.7.0-2) unstable; urgency=medium

    * Backport fix for 'ss' output

   -- Luca Boccassi <>  Mon, 22 Jan 2024 12:24:29 +

  iproute2 (6.7.0-1) unstable; urgency=medium

    * Add Italian debconf translation (Closes: #1056582)
    * Update upstream source from tag 'upstream/6.7.0'
    * Bump copyright year ranges in d/copyright
    * Drop 0002-Revert-Makefile-ensure-CONF_USR_DIR-honours-the-libd.patch,
  merged upstream
    * Default config files moved from /usr/lib to /usr/share

   -- Luca Boccassi <>  Fri, 12 Jan 2024 21:47:59 +

  iproute2 (6.6.0-1) unstable; urgency=medium

    * Update upstream source from tag 'upstream/6.6.0'
    * Backport patch to fix configuration installation
    * Remove handling of qt_atm.so, dropped upstream

   -- Luca Boccassi <>  Sun, 05 Nov 2023 22:46:20 +

  iproute2 (6.5.0-5) unstable; urgency=medium

    * Use dh-sequence-movetousr

   -- Luca Boccassi <>  Tue, 24 Oct 2023 15:24:01 +0100

  iproute2 (6.5.0-4) unstable; urgency=medium

    * postinst: handle legacy config files only when upgrading from previous
  versions that shipped them
    * postinst: ensure that locally modified legacy config files are
  preserved as overrides on upgrade (Closes: #1051577)
    * Note configuration files location changes in NEWS

   -- Luca Boccassi <>  Sat, 16 Sep 2023 18:58:51 +0100

  iproute2 (6.5.0-3) unstable; urgency=medium

    * Remove further leftovers as part of upstream's move of config to /usr
  (Closes: #1051577)

   -- Luca Boccassi <>  Mon, 11 Sep 2023 09:42:12 +0100

  iproute2 (6.5.0-2) unstable; urgency=medium

    * Add maintscript to remove conffiles that upstream has moved to /usr
  (Closes: #1051577)

   -- Luca Boccassi <>  Sun, 10 Sep 2023 21:28:28 +0100

  iproute2 (6.5.0-1) unstable; urgency=medium

    [ Luca Boccassi ]
    * Use wildcard for Lintian overrides

    [ Peter Kvillegård ]
    * Add Swedish translation of debconf messages (Closes: #1050442)

    [ Luca Boccassi ]
    * Update upstream source from tag 'upstream/6.5.0'
    * Use cap_bpf instead of cap_sys_admin for ip vrf-exec
    * Package-provided config files are now shipped in /usr/iproute2 instead
  of

[Kernel-packages] [Bug 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

2024-04-11 Thread Aaron Honeycutt

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

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

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Noble:
  Confirmed

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

2024-04-11 Thread Ubuntu QA Website

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/2060868

** Tags added: iso-testing

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

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

Status in linux package in Ubuntu:
  New
Status in linux source package in Noble:
  New

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2056227] Re: KVM: arm64: softlockups in stage2_apply_range

2024-04-11 Thread Krister Johansen

I've tested linux/5.15.0-104.114 and it passes my tests.  Marking
verification-done-jammy-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/2056227

Title:
  KVM: arm64: softlockups in stage2_apply_range

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

Bug description:
  [Impact]

  Tearing down kvm VMs on arm64 can cause softlockups to appear on console.  
When
  terminating VMs with > 100Gb of memory and 4k pages, the memory unmap times
  often exceed 20 seconds, which can trigger the softlockup detector.  Portions 
of
  the unmap path also have interrupts disabled while tlb invalidation 
instructions
  run, which can further contribute to latency problems.  My team has observed
  networking latency problems if the cpu where the teardown is occurring is also
  mapped to handle a NIC interrupt.

  Fortunately, a solution has been in place since Linux 6.1.  A small pair of
  patches modify stage2_apply_range to operate on smaller memory ranges before
  performing a cond_resched.  With these patches applied, softlockups are no
  longer observed when tearing down VMs with large amounts of memory. 

  Although I also submitted the patches to 5.15 LTS (link to LTS submission in
  "Backport" section), I'd appreciate it if Ubuntu were willing to take this
  submission in parallel since the impact has left us unable to utilize arm64 
for
  kvm until we can either migrate our hypervisors to hugepages, pick up this 
fix,
  or some combination of the two.

  [Backport]

  Backport the following fixes from linux 6.1: 

  3b5c082bbf KVM: arm64: Work out supported block level at compile time
  5994bc9e05 KVM: arm64: Limit stage2_apply_range() batch size to largest block

  The fix is in 5994bc9e05 and 3b5c082bbf is a dependency that was submitted as
  part of the series.  The original submission is here:

  https://lore.kernel.org/all/20221007234151.461779-1-oliver.up...@linux.dev/

  I've also submitted the patches to 5.15 LTS here:

  https://lore.kernel.org/stable/cover.1709665227.git.k...@templeofstupid.com/

  Both fixes cherry picked cleanly and there were no conflicts.

  [Test]
 
  Executed the test from 5994bc9e05 as well as my own run of kvm_page_table_test
  on a VM with 4k pages and a memory size > 100Gb.  Without the patches,
  softlockups were observed in both tests.  With the patches applied, the tests
  ran without incident.

  This was tested against both LTS 5.15.150 and linux-aws-5.15.0-1055.
   
  [Potential Regression]
 
  Regression potential is low.  These patches have been present in Linux since 
6.1
  and appear to have needed no further maintenance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056227/+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 2056227] Re: KVM: arm64: softlockups in stage2_apply_range

2024-04-11 Thread Krister Johansen

For posterity, LTS 5.15 picked up this fix in 5.15.154

** Tags removed: verification-needed-jammy-linux
** Tags added: verification-done-jammy-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/2056227

Title:
  KVM: arm64: softlockups in stage2_apply_range

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

Bug description:
  [Impact]

  Tearing down kvm VMs on arm64 can cause softlockups to appear on console.  
When
  terminating VMs with > 100Gb of memory and 4k pages, the memory unmap times
  often exceed 20 seconds, which can trigger the softlockup detector.  Portions 
of
  the unmap path also have interrupts disabled while tlb invalidation 
instructions
  run, which can further contribute to latency problems.  My team has observed
  networking latency problems if the cpu where the teardown is occurring is also
  mapped to handle a NIC interrupt.

  Fortunately, a solution has been in place since Linux 6.1.  A small pair of
  patches modify stage2_apply_range to operate on smaller memory ranges before
  performing a cond_resched.  With these patches applied, softlockups are no
  longer observed when tearing down VMs with large amounts of memory. 

  Although I also submitted the patches to 5.15 LTS (link to LTS submission in
  "Backport" section), I'd appreciate it if Ubuntu were willing to take this
  submission in parallel since the impact has left us unable to utilize arm64 
for
  kvm until we can either migrate our hypervisors to hugepages, pick up this 
fix,
  or some combination of the two.

  [Backport]

  Backport the following fixes from linux 6.1: 

  3b5c082bbf KVM: arm64: Work out supported block level at compile time
  5994bc9e05 KVM: arm64: Limit stage2_apply_range() batch size to largest block

  The fix is in 5994bc9e05 and 3b5c082bbf is a dependency that was submitted as
  part of the series.  The original submission is here:

  https://lore.kernel.org/all/20221007234151.461779-1-oliver.up...@linux.dev/

  I've also submitted the patches to 5.15 LTS here:

  https://lore.kernel.org/stable/cover.1709665227.git.k...@templeofstupid.com/

  Both fixes cherry picked cleanly and there were no conflicts.

  [Test]
 
  Executed the test from 5994bc9e05 as well as my own run of kvm_page_table_test
  on a VM with 4k pages and a memory size > 100Gb.  Without the patches,
  softlockups were observed in both tests.  With the patches applied, the tests
  ran without incident.

  This was tested against both LTS 5.15.150 and linux-aws-5.15.0-1055.
   
  [Potential Regression]
 
  Regression potential is low.  These patches have been present in Linux since 
6.1
  and appear to have needed no further maintenance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056227/+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 2060217] Re: NFSv4 fails to mount in noble/s390x

2024-04-11 Thread Andreas Hasenack

Marking the userspace component (src:nfs-utils) task as invalid, since
it's a bug in the kernel.

** Changed in: nfs-utils (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  NFSv4 fails to mount in noble/s390x

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New
Status in nfs-utils package in Ubuntu:
  Invalid

Bug description:
  https://autopkgtest.ubuntu.com/packages/n/nfs-utils/noble/s390x

  Looks like it has been failing for a long time already.

  Log: https://autopkgtest.ubuntu.com/results/autopkgtest-
  noble/noble/s390x/n/nfs-utils/20240404_145924_ef255@/log.gz

  339s autopkgtest [14:41:04]: test local-server-client: 
[---
  340s Killed
  340s autopkgtest [14:41:05]: test process requested reboot with marker boot1
  364s autopkgtest-virt-ssh: WARNING: ssh connection failed. Retrying in 3 
seconds...
  372s FAIL: nfs_home not mounted
  373s autopkgtest [14:41:38]: test local-server-client: 
---]
  373s local-server-client  FAIL non-zero exit status 1

  and

  934s autopkgtest [14:50:59]: test kerberos-mount: [---
  935s Initializing database '/var/lib/krb5kdc/principal' for realm 'DEP8',
  935s master key name 'K/M@DEP8'
  935s Authenticating as principal root/admin@DEP8 with password.
  935s Principal "nfs/nfs-server.dep8@DEP8" created.
  935s Authenticating as principal root/admin@DEP8 with password.
  935s Entry for principal nfs/nfs-server.dep8 with kvno 2, encryption type 
aes256-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab.
  935s Entry for principal nfs/nfs-server.dep8 with kvno 2, encryption type 
aes128-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab.
  935s Authenticating as principal root/admin@DEP8 with password.
  935s Principal "host/nfs-server.dep8@DEP8" created.
  935s Authenticating as principal root/admin@DEP8 with password.
  935s Entry for principal host/nfs-server.dep8 with kvno 2, encryption type 
aes256-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab.
  935s Entry for principal host/nfs-server.dep8 with kvno 2, encryption type 
aes128-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab.
  936s exporting *:/storage
  938s mount.nfs: mount system call failed for /mnt
  938s umount: /mnt: not mounted.
  938s autopkgtest [14:51:02]: test kerberos-mount: ---]
  939s kerberos-mount   FAIL non-zero exit status 32

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2060217/+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 2060992] [NEW] aws: Guest kernel support for clean boot on demand

2024-04-11 Thread Philip Cox

Public bug reported:

SRU Justification:

On hardware reduced platforms[0] this field may exist but it is not
exposed currently.

[Fix]
Expose this field even on hardware reduced platforms.

https://lore.kernel.org/lkml/20240312134148.727454-1-dw...@infradead.org

[Test Plan]
AWS test.

[Where problems could occur]
If on hardware reduced platforms that incorrectly support/advertise the FACS
field, hibernation may break if it returns a hardware signature that changes.

[0]: See Section 4.1 of the ACPI spec for info on hardware-reduced platforms.
https://uefi.org/htmlspecs/ACPI_Spec_6_4_html/04_ACPI_Hardware_Specification/ACPI_Hardware_Specification.html

** Affects: linux-aws (Ubuntu)
Importance: Undecided
Assignee: Philip Cox (philcox)
Status: New

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

Title:
aws: Guest kernel support for clean boot on demand

Status in linux-aws package in Ubuntu:
New

Bug description:
SRU Justification:

On hardware reduced platforms[0] this field may exist but it is not
exposed currently.

[Fix]
Expose this field even on hardware reduced platforms.

https://lore.kernel.org/lkml/20240312134148.727454-1-dw...@infradead.org

[Test Plan]
AWS test.

[Where problems could occur]
If on hardware reduced platforms that incorrectly support/advertise the FACS
field, hibernation may break if it returns a hardware signature that changes.

[0]: See Section 4.1 of the ACPI spec for info on hardware-reduced platforms.

https://uefi.org/htmlspecs/ACPI_Spec_6_4_html/04_ACPI_Hardware_Specification/ACPI_Hardware_Specification.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2060992/+subscriptions

[Kernel-packages] [Bug 2060984] Re: FFe: New firmware release

build available at

https://launchpad.net/~tjaalton/+archive/ubuntu/firmware

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

Title:
  FFe: New firmware release

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  A new upstream release of linux-firmware was tagged on 2024.04.10,
  this would sync us with that. Changes:

   - imx: sdma: update firmware to v3.6/v4.6
   - linux-firmware: mediatek: Update MT8173 VPU firmware to v1.1.8
   - amdgpu: DMCUB updates for various AMDGPU ASICs
   - Intel Bluetooth: Update firmware file for Intel Bluetooth 9260
   - Intel Bluetooth: Update firmware file for Intel Bluetooth 9560
   - Intel Bluetooth: Update firmware file for Intel Bluetooth AX201
   - Intel Bluetooth: Update firmware file for Intel Bluetooth AX200
   - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX210
   - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX211
   - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX211
   - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX203
   - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX203
   - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX101
   - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX101
   - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX211
   - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203
   - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX101
   - Intel Bluetooth: Update firmware file for Intel Bluetooth BE200
   - WHENCE: Link the Raspberry Pi CM4 and 5B to the 4B
   - Montage: update firmware for Mont-TSSE
   - linux-firmware: Add firmware for Cirrus CS35L56 for Dell laptops
   - rtw88: Add RTL8703B firmware v11.0.0
   - rtw89: 8922a: add firmware v0.35.18.0
   - rtw89: 8852c: update fw to v0.27.56.14
   - mekdiatek: Update mt8186 SOF firmware to v2.0.1
   - linux-firmware: update firmware for en8811h 2.5G ethernet phy
   - amdgpu: DMCUB updates for various AMDGPU ASICs
   - i915: Add DG2 HuC 7.10.15
   - ath10k: WCN3990: hw1.0: move firmware back from qcom/ location
   - ath10k: WCN3990: hw1.0: add qcm2290 firmware API file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2060984/+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 2060984] Re: FFe: New firmware release

would also fix https://bugs.launchpad.net/ubuntu/+source/linux-
firmware/+bug/2060904

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

Title:
  FFe: New firmware release

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  A new upstream release of linux-firmware was tagged on 2024.04.10,
  this would sync us with that. Changes:

   - imx: sdma: update firmware to v3.6/v4.6
   - linux-firmware: mediatek: Update MT8173 VPU firmware to v1.1.8
   - amdgpu: DMCUB updates for various AMDGPU ASICs
   - Intel Bluetooth: Update firmware file for Intel Bluetooth 9260
   - Intel Bluetooth: Update firmware file for Intel Bluetooth 9560
   - Intel Bluetooth: Update firmware file for Intel Bluetooth AX201
   - Intel Bluetooth: Update firmware file for Intel Bluetooth AX200
   - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX210
   - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX211
   - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX211
   - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX203
   - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX203
   - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX101
   - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX101
   - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX211
   - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203
   - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX101
   - Intel Bluetooth: Update firmware file for Intel Bluetooth BE200
   - WHENCE: Link the Raspberry Pi CM4 and 5B to the 4B
   - Montage: update firmware for Mont-TSSE
   - linux-firmware: Add firmware for Cirrus CS35L56 for Dell laptops
   - rtw88: Add RTL8703B firmware v11.0.0
   - rtw89: 8922a: add firmware v0.35.18.0
   - rtw89: 8852c: update fw to v0.27.56.14
   - mekdiatek: Update mt8186 SOF firmware to v2.0.1
   - linux-firmware: update firmware for en8811h 2.5G ethernet phy
   - amdgpu: DMCUB updates for various AMDGPU ASICs
   - i915: Add DG2 HuC 7.10.15
   - ath10k: WCN3990: hw1.0: move firmware back from qcom/ location
   - ath10k: WCN3990: hw1.0: add qcm2290 firmware API file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2060984/+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 2060989] [NEW] package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to install/upgrade: installed linux-headers-6.5.0-27-generic package post-installation script subprocess

2024-04-11 Thread Nela Petrželková

Public bug reported:

-

ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-27-generic 6.5.0-27.28
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  nela   2694 F wireplumber
 /dev/snd/controlC1:  nela   2694 F wireplumber
 /dev/snd/seq:nela   2674 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Thu Apr 11 10:13:36 2024
ErrorMessage: installed linux-headers-6.5.0-27-generic package 
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2024-03-30 (12 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic 
root=UUID=e960f11c-d239-429e-97af-9073de7f3b3a ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to 
install/upgrade: installed linux-headers-6.5.0-27-generic package 
post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/02/2021
dmi.bios.release: 1.27
dmi.bios.vendor: LENOVO
dmi.bios.version: HACN27WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion S7 15ACH6
dmi.ec.firmware.release: 1.27
dmi.modalias: 
dmi:bvnLENOVO:bvrHACN27WW:bd08/02/2021:br1.27:efr1.27:svnLENOVO:pn82K8:pvrLegionS715ACH6:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegionS715ACH6:skuLENOVO_MT_82K8_BU_idea_FM_LegionS715ACH6:
dmi.product.family: Legion S7 15ACH6
dmi.product.name: 82K8
dmi.product.sku: LENOVO_MT_82K8_BU_idea_FM_Legion S7 15ACH6
dmi.product.version: Legion S7 15ACH6
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-package mantic need-duplicate-check

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

Title:
  package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to
  install/upgrade: installed linux-headers-6.5.0-27-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  -

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: linux-headers-6.5.0-27-generic 6.5.0-27.28
  ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nela   2694 F wireplumber
   /dev/snd/controlC1:  nela   2694 F wireplumber
   /dev/snd/seq:nela   2674 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Thu Apr 11 10:13:36 2024
  ErrorMessage: installed linux-headers-6.5.0-27-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2024-03-30 (12 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic 
root=UUID=e960f11c-d239-429e-97af-9073de7f3b3a ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to 
install/upgrade: installed linux-headers-6.5.0-27-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: HACN27WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion S7 15ACH6
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrHACN27WW:bd08/02/2021:br1.27:efr1.27:svnLENOVO:pn82K8:pvrLegionS715ACH6:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegionS715ACH6:skuLENOVO_MT_82K8_BU_idea_FM_LegionS715ACH6:

[Kernel-packages] [Bug 2060984] [NEW] FFe: New firmware release

Public bug reported:

A new upstream release of linux-firmware was tagged on 2024.04.10, this
would sync us with that. Changes:

 - imx: sdma: update firmware to v3.6/v4.6
 - linux-firmware: mediatek: Update MT8173 VPU firmware to v1.1.8
 - amdgpu: DMCUB updates for various AMDGPU ASICs
 - Intel Bluetooth: Update firmware file for Intel Bluetooth 9260
 - Intel Bluetooth: Update firmware file for Intel Bluetooth 9560
 - Intel Bluetooth: Update firmware file for Intel Bluetooth AX201
 - Intel Bluetooth: Update firmware file for Intel Bluetooth AX200
 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX210
 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX211
 - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX211
 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX203
 - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX203
 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX101
 - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX101
 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX211
 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203
 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX101
 - Intel Bluetooth: Update firmware file for Intel Bluetooth BE200
 - WHENCE: Link the Raspberry Pi CM4 and 5B to the 4B
 - Montage: update firmware for Mont-TSSE
 - linux-firmware: Add firmware for Cirrus CS35L56 for Dell laptops
 - rtw88: Add RTL8703B firmware v11.0.0
 - rtw89: 8922a: add firmware v0.35.18.0
 - rtw89: 8852c: update fw to v0.27.56.14
 - mekdiatek: Update mt8186 SOF firmware to v2.0.1
 - linux-firmware: update firmware for en8811h 2.5G ethernet phy
 - amdgpu: DMCUB updates for various AMDGPU ASICs
 - i915: Add DG2 HuC 7.10.15
 - ath10k: WCN3990: hw1.0: move firmware back from qcom/ location
 - ath10k: WCN3990: hw1.0: add qcm2290 firmware API file

** Affects: linux-firmware (Ubuntu)
 Importance: Undecided
 Status: New

** Summary changed:

- New firmware release
+ FFe: New firmware release

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

Title:
  FFe: New firmware release

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  A new upstream release of linux-firmware was tagged on 2024.04.10,
  this would sync us with that. Changes:

   - imx: sdma: update firmware to v3.6/v4.6
   - linux-firmware: mediatek: Update MT8173 VPU firmware to v1.1.8
   - amdgpu: DMCUB updates for various AMDGPU ASICs
   - Intel Bluetooth: Update firmware file for Intel Bluetooth 9260
   - Intel Bluetooth: Update firmware file for Intel Bluetooth 9560
   - Intel Bluetooth: Update firmware file for Intel Bluetooth AX201
   - Intel Bluetooth: Update firmware file for Intel Bluetooth AX200
   - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX210
   - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX211
   - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX211
   - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX203
   - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX203
   - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX101
   - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX101
   - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX211
   - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203
   - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX101
   - Intel Bluetooth: Update firmware file for Intel Bluetooth BE200
   - WHENCE: Link the Raspberry Pi CM4 and 5B to the 4B
   - Montage: update firmware for Mont-TSSE
   - linux-firmware: Add firmware for Cirrus CS35L56 for Dell laptops
   - rtw88: Add RTL8703B firmware v11.0.0
   - rtw89: 8922a: add firmware v0.35.18.0
   - rtw89: 8852c: update fw to v0.27.56.14
   - mekdiatek: Update mt8186 SOF firmware to v2.0.1
   - linux-firmware: update firmware for en8811h 2.5G ethernet phy
   - amdgpu: DMCUB updates for various AMDGPU ASICs
   - i915: Add DG2 HuC 7.10.15
   - ath10k: WCN3990: hw1.0: move firmware back from qcom/ location
   - ath10k: WCN3990: hw1.0: add qcm2290 firmware API file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2060984/+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 2060727] Re: The keyboard does not work after latest kernel update

2024-04-11 Thread Aussems J.a.c.

My history log give the entry below when the problem occurs:

Start-Date: 2024-04-08  14:38:34
Commandline: aptdaemon role='role-commit-packages' sender=':1.79'
Install: linux-image-6.5.0-1019-oem:amd64 (6.5.0-1019.20, automatic), 
linux-modules-6.5.0-1019-oem:amd64 (6.5.0-1019.20, automatic), 
linux-image-oem-22.04d:amd64 (6.5.0.1019.21, automatic), linux-oem-22.04d:amd64 
(6.5.0.1019.21, automatic), linux-headers-oem-22.04d:amd64 (6.5.0.1019.21, 
automatic), linux-headers-6.5.0-1019-oem:amd64 (6.5.0-1019.20, automatic), 
linux-oem-6.5-headers-6.5.0-1019:amd64 (6.5.0-1019.20, automatic)
Upgrade: linux-headers-oem-22.04:amd64 (6.5.0.1018.20, 6.5.0.1019.21), 
linux-image-oem-22.04c:amd64 (6.1.0.1036.37, 6.5.0.1019.21), 
linux-oem-22.04c:amd64 (6.1.0.1036.37, 6.5.0.1019.21), linux-oem-22.04:amd64 
(6.5.0.1018.20, 6.5.0.1019.21), linux-headers-oem-22.04c:amd64 (6.1.0.1036.37, 
6.5.0.1019.21), linux-image-oem-22.04:amd64 (6.5.0.1018.20, 6.5.0.1019.21), 
linux-libc-dev:amd64 (5.15.0-101.111, 5.15.0-102.112)
End-Date: 2024-04-08  14:38:57

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

Title:
  The keyboard does not work after latest kernel update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The computer is a ThinkPad L15 Gen 4, its integrated keyboard does not
  work after the latest kernel update and its subsequent reboot of the
  laptop. Nothing else is connected to the laptop.

  --

  In /var/log/apt/history.log , the latest we can see is:

  Start-Date: 2024-04-09  12:37:28
  Commandline: apt full-upgrade
  Install: linux-modules-extra-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-headers-6.5.0-27:amd64 (6.5.0-27.28, automatic), 
linux-modules-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-image-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-headers-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic)
  Upgrade: linux-headers-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), 
linux-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-image-generic:amd64 
(6.5.0.26.26, 6.5.0.27.27), linux-libc-dev:amd64 (6.5.0-26.26, 6.5.0-27.28)
  End-Date: 2024-04-09  12:37:51

  --

  $ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 23.10
  Release:23.10

  $ # Note: It's Kubuntu 23.10

  --

  $ uname -a
  Linux tp 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar  7 18:21:00 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060727/+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 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

2024-04-11 Thread Aaron Honeycutt

I'm able to recreate this issue as well. I also want to note that the
24.04 LTS Beta also does not boot with the "Try or Install" option in
GRUB but it does boot the ISO.

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

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

Status in linux package in Ubuntu:
  New
Status in linux source package in Noble:
  New

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060727] Re: The keyboard does not work after latest kernel update

2024-04-11 Thread Aussems J.a.c.




I changed in file '/etc/default/grub' the lines:

GRUB_TIMEOUT_STYLE=menu
GRUB_TIMEOUT=-1

I used the command 'sudo update-grub' and Reboot the computer.
The grub menu is now shown and I can still use the internal keyboard.

I can choose between kernel version:

- Linux 6.5.0.-1019-oem
- Linux 6.5.0.-1018-oem

When I choose the kernel, 1019, the keyboard does not functions after booting
When I choose the kernel, 1018, the keyboard workes after booting.

So this shows that the problem is caused by the 1019 kernel.

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

Title:
  The keyboard does not work after latest kernel update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The computer is a ThinkPad L15 Gen 4, its integrated keyboard does not
  work after the latest kernel update and its subsequent reboot of the
  laptop. Nothing else is connected to the laptop.

  --

  In /var/log/apt/history.log , the latest we can see is:

  Start-Date: 2024-04-09  12:37:28
  Commandline: apt full-upgrade
  Install: linux-modules-extra-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-headers-6.5.0-27:amd64 (6.5.0-27.28, automatic), 
linux-modules-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-image-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-headers-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic)
  Upgrade: linux-headers-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), 
linux-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-image-generic:amd64 
(6.5.0.26.26, 6.5.0.27.27), linux-libc-dev:amd64 (6.5.0-26.26, 6.5.0-27.28)
  End-Date: 2024-04-09  12:37:51

  --

  $ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 23.10
  Release:23.10

  $ # Note: It's Kubuntu 23.10

  --

  $ uname -a
  Linux tp 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar  7 18:21:00 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060727/+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 2060981] [NEW] ACPI BIOS errors

2024-04-11 Thread Islam

Public bug reported:

dmesg show the below ACPI errors, is this normal?


# dmesg | grep -i acpi
[0.00] BIOS-e820: [mem 0x59cf8000-0x59dc3fff] ACPI data
[0.00] BIOS-e820: [mem 0x59dc4000-0x59eb] ACPI NVS
[0.00] reserve setup_data: [mem 0x59cf8000-0x59dc3fff] 
ACPI data
[0.00] reserve setup_data: [mem 0x59dc4000-0x59eb] 
ACPI NVS
[0.00] efi: ACPI=0x59dc3000 ACPI 2.0=0x59dc3014 TPMFinalLog=0x59e4a000 
SMBIOS=0x5a609000 SMBIOS 3.0=0x5a608000 MEMATTR=0x528f6018 ESRT=0x53983818 
MOKvar=0x5a5e4000 INITRD=0x4fde3f98 RNG=0x59d28018 TPMEventLog=0x4fdc7018 
[0.020042] ACPI: Early table checksum verification disabled
[0.020046] ACPI: RSDP 0x59DC3014 24 (v02 _ASUS_)
[0.020052] ACPI: XSDT 0x59DC2728 00011C (v01 _ASUS_ Notebook 
01072009 AMI  0113)
[0.020060] ACPI: FACP 0x59DBD000 000114 (v06 _ASUS_ Notebook 
01072009 AMI  00010013)
[0.020066] ACPI: DSDT 0x59D6 05C524 (v02 _ASUS_ Notebook 
01072009 INTL 20191018)
[0.020070] ACPI: FACS 0x59EBC000 40
[0.020074] ACPI: MCFG 0x59DC1000 3C (v01 _ASUS_ Notebook 
01072009 MSFT 0097)
[0.020077] ACPI: SSDT 0x59DBE000 00255D (v02 CpuRef CpuSsdt  
3000 INTL 20191018)
[0.020081] ACPI: FIDT 0x59D5F000 9C (v01 _ASUS_ Notebook 
01072009 AMI  00010013)
[0.020084] ACPI: ECDT 0x59D5E000 C1 (v01 _ASUS_ Notebook 
01072009 AMI. 0005)
[0.020088] ACPI: MSDM 0x59D5D000 55 (v03 _ASUS_ Notebook 
01072009 ASUS 0001)
[0.020092] ACPI: SSDT 0x59D58000 004F42 (v02 DptfTa DptfTabl 
1000 INTL 20191018)
[0.020095] ACPI: SSDT 0x59D56000 0017B5 (v02 SaSsdt SaSsdt   
3000 INTL 20191018)
[0.020099] ACPI: SSDT 0x59D52000 003350 (v02 INTEL  IgfxSsdt 
3000 INTL 20191018)
[0.020103] ACPI: SSDT 0x59D46000 00B1B2 (v02 INTEL  TcssSsdt 
1000 INTL 20191018)
[0.020106] ACPI: HPET 0x59D45000 38 (v01 _ASUS_ Notebook 
01072009 AMI  0113)
[0.020110] ACPI: APIC 0x59D44000 00012C (v04 _ASUS_ Notebook 
01072009 AMI  0113)
[0.020114] ACPI: SSDT 0x59D43000 0002A7 (v02 _ASUS_ TcssSsdt 
 INTL 20191018)
[0.020118] ACPI: SSDT 0x59D3B000 007504 (v02 _ASUS_ TglU_Rvp 
1000 INTL 20191018)
[0.020122] ACPI: NHLT 0x59D39000 001B54 (v00 _ASUS_ Notebook 
01072009 AMI  0113)
[0.020126] ACPI: LPIT 0x59D38000 CC (v01 _ASUS_ Notebook 
01072009 AMI  0113)
[0.020129] ACPI: SSDT 0x59D36000 00012A (v02 _ASUS_ TbtTypeC 
 INTL 20191018)
[0.020133] ACPI: DBGP 0x59D35000 34 (v01 _ASUS_ Notebook 
01072009 AMI  0113)
[0.020137] ACPI: DBG2 0x59D34000 54 (v00 _ASUS_ Notebook 
01072009 AMI  0113)
[0.020141] ACPI: SSDT 0x59D33000 000D8A (v02 _ASUS_ UsbCTabl 
1000 INTL 20191018)
[0.020145] ACPI: DMAR 0x59D32000 B8 (v02 INTEL  EDK2 
0002  0113)
[0.020148] ACPI: SSDT 0x59D31000 0004B8 (v02 HgRef  HgRpSsdt 
1000 INTL 20191018)
[0.020152] ACPI: SSDT 0x59D3 000144 (v02 Intel  ADebTabl 
1000 INTL 20191018)
[0.020155] ACPI: BGRT 0x59D2F000 38 (v01 _ASUS_ Notebook 
01072009 AMI  00010013)
[0.020159] ACPI: UEFI 0x59E28000 00063A (v01 INTEL  RstVmdE  
 ??   )
[0.020163] ACPI: UEFI 0x59E27000 5C (v01 INTEL  RstVmdV  
 ??   )
[0.020166] ACPI: TPM2 0x59D2E000 4C (v04 _ASUS_ Notebook 
0001 AMI  )
[0.020170] ACPI: SSDT 0x59D2B000 002495 (v01 OptRf1 Opt1Tabl 
1000 INTL 20191018)
[0.020173] ACPI: PTDT 0x59D2A000 000D44 (v00 _ASUS_ Notebook 
0005 MSFT 010D)
[0.020177] ACPI: WSMT 0x59D37000 28 (v01 _ASUS_ Notebook 
01072009 AMI  00010013)
[0.020181] ACPI: FPDT 0x59D29000 44 (v01 _ASUS_ A M I
01072009 AMI  0113)
[0.020184] ACPI: Reserving FACP table memory at [mem 0x59dbd000-0x59dbd113]
[0.020186] ACPI: Reserving DSDT table memory at [mem 0x59d6-0x59dbc523]
[0.020187] ACPI: Reserving FACS table memory at [mem 0x59ebc000-0x59ebc03f]
[0.020187] ACPI: Reserving MCFG table memory at [mem 0x59dc1000-0x59dc103b]
[0.020188] ACPI: Reserving SSDT table memory at [mem 0x59dbe000-0x59dc055c]
[0.020189] ACPI: Reserving FIDT table memory at [mem 0x59d5f000-0x59d5f09b]
[0.020190] ACPI: Reserving ECDT table memory at [mem 0x59d5e000-0x59d5e0c0]
[0.020191] ACPI: Reserving MSDM table memory at [mem 0x59d5d000-0x59d5d054]
[0.020191] ACPI: Reserving SSDT table memory at [mem 0x59d58000-0x59d5cf41]
[0.020192] ACPI: Reserving SSDT table memory at [mem 0x59d56000-0x59d577b4]
[0.020193] ACPI: Reserving SSDT table memory at [mem 0x59d52000-0x59d5534f]
[0.020196] ACPI: Reserving SSDT

[Kernel-packages] [Bug 2060977] [NEW] gnome crashes when waking from lock

2024-04-11 Thread Brett Holman

Public bug reported:

When trying to log in from locked / sleeping desktop, gnome crashed.

I have three monitors connected via displayport to this card.

dmesg snip:

[Thu Apr 11 08:12:57 2024] audit: type=1107 audit(1712844779.171:174815): 
pid=1799 uid=103 auid=4294967295 ses=4294967295 subj=unconfined 
msg='apparmor="DENIED" operation="dbus_signal"  bus="system" 
path="/org/freedesktop/login1" interface="org.freedesktop.DBus.Properties" 
member="PropertiesChanged" name=":1.12" mask="receive" pid=10350 
label="snap.firefox.firefox" peer_pid=1790 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=103 hostname=? 
addr=? terminal=?'
[Thu Apr 11 08:12:57 2024] rfkill: input handler enabled
[Thu Apr 11 08:12:58 2024] audit: type=1107 audit(1712844779.588:174816): 
pid=1799 uid=103 auid=4294967295 ses=4294967295 subj=unconfined 
msg='apparmor="DENIED" operation="dbus_signal"  bus="system" 
path="/org/freedesktop/login1" interface="org.freedesktop.login1.Manager" 
member="SessionRemoved" name=":1.12" mask="receive" pid=10350 
label="snap.firefox.firefox" peer_pid=1790 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=103 hostname=? 
addr=? terminal=?'
[Thu Apr 11 08:12:58 2024] audit: type=1107 audit(1712844779.698:174817): 
pid=1799 uid=103 auid=4294967295 ses=4294967295 subj=unconfined 
msg='apparmor="DENIED" operation="dbus_signal"  bus="system" 
path="/org/freedesktop/login1" interface="org.freedesktop.login1.Manager" 
member="UserNew" name=":1.12" mask="receive" pid=10350 
label="snap.firefox.firefox" peer_pid=1790 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=103 hostname=? 
addr=? terminal=?'
[Thu Apr 11 08:12:58 2024] audit: type=1400 audit(1712844779.700:174818): 
apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" 
name="/proc/10350/environ" pid=553296 comm="firefox" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=1000
[Thu Apr 11 08:12:58 2024] audit: type=1107 audit(1712844779.710:174819): 
pid=1799 uid=103 auid=4294967295 ses=4294967295 subj=unconfined 
msg='apparmor="DENIED" operation="dbus_signal"  bus="system" 
path="/org/freedesktop/login1" interface="org.freedesktop.login1.Manager" 
member="SessionNew" name=":1.12" mask="receive" pid=10350 
label="snap.firefox.firefox" peer_pid=1790 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=103 hostname=? 
addr=? terminal=?'
[Thu Apr 11 08:12:59 2024] overlayfs: fs on 
'/var/lib/gdm3/.local/share/containers/storage/overlay/compat1995007933/lower1' 
does not support file handles, falling back to xino=off.
[Thu Apr 11 08:12:59 2024] overlayfs: fs on 
'/var/lib/gdm3/.local/share/containers/storage/overlay/metacopy-check1285164697/l1'
 does not support file handles, falling back to xino=off.
[Thu Apr 11 08:12:59 2024] overlayfs: fs on 
'/var/lib/gdm3/.local/share/containers/storage/overlay/opaque-bug-check3491611924/l2'
 does not support file handles, falling back to xino=off.
[Thu Apr 11 08:12:59 2024] snd_hda_codec_hdmi hdaudioC0D0: HDMI: Unknown ELD 
version 0
[Thu Apr 11 08:13:01 2024] rfkill: input handler disabled
[Thu Apr 11 08:13:02 2024] [drm:retrieve_link_cap [amdgpu]] *ERROR* 
retrieve_link_cap: Read receiver caps dpcd data failed.
[Thu Apr 11 08:13:07 2024] rfkill: input handler enabled
[Thu Apr 11 08:13:08 2024] rfkill: input handler disabled
[Thu Apr 11 08:13:10 2024] audit: type=1107 audit(1712844791.998:174820): 
pid=1799 uid=103 auid=4294967295 ses=4294967295 subj=unconfined 
msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" 
path="/org/freedesktop/PolicyKit1/Authority" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name=":1.14" pid=555445 label="snap.snap-store.snap-store" peer_pid=1820 
peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=103 hostname=? 
addr=? terminal=?'
[Thu Apr 11 08:13:10 2024] audit: type=1107 audit(1712844791.999:174821): 
pid=1799 uid=103 auid=4294967295 ses=4294967295 subj=unconfined 
msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" 
path="/org/freedesktop/PolicyKit1/Authority" 
interface="org.freedesktop.PolicyKit1.Authority" member="CheckAuthorization" 
mask="send" name=":1.14" pid=555445 label="snap.snap-store.snap-store" 
peer_pid=1820 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=103 hostname=? 
addr=? terminal=?'


journalctl -u gdm

-- Boot f2ce6f5ac44d413f8e6a1ba80a0bee53 --
Apr 08 09:11:10 arc systemd[1]: Starting gdm.service - GNOME Display Manager...
Apr 08 09:11:10 arc systemd[1]: Started gdm.service - GNOME Display Manager.
Apr 08 09:11:10 arc gdm-launch-environment][7305]: 
pam_env(gdm-launch-environment:session): deprecated reading of user environment 
enabled
Apr 08 09:11:10 arc gdm-launch-environment][7305]: 
pam_unix(gdm-launch-environment:session): session opened for user gdm(uid=126) 
by

[Kernel-packages] [Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)

** Attachment added: "Upstream 6.7 changelog"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+attachment/5763789/+files/6.7-changes.txt

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

Title:
  [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from
  testing/unstable (main)

Status in iproute2 package in Ubuntu:
  Confirmed

Bug description:
  A few versions have been released and Ubuntu Noble still has the 6.1
  version (6.1.0-1ubuntu2) from one year ago. Could it be possible to
  import the latest version from Debian unstable fixing a bunch of
  issues and supporting features from more recent kernels?

  Please note that Ubuntu Noble 24.04 will probably be shipped with the
  v6.8 kernel [1]. IPRoute v6.1 supports features added up to the v6.1
  kernel, so missing the ones added to earlier versions. Switching to
  the v6.7 now should ease the upgrade to the v6.8 later.

  [1] https://discourse.ubuntu.com/t/introducing-kernel-6-8-for-
  the-24-04-noble-numbat-release/41958

  Upstream ChangeLog:

  - 6.2: https://lore.kernel.org/netdev/20230220105811.674bd304@hermes.local/
  - 6.3: https://lore.kernel.org/netdev/20230427090253.7a92616b@hermes.local/
  - 6.4: https://lore.kernel.org/netdev/20230626093137.2f302acc@hermes.local/
  - 6.5: https://lore.kernel.org/netdev/20230906093918.394a1b1d@hermes.local/
  - 6.6: https://lore.kernel.org/netdev/20231106090325.07092c87@hermes.local/
  - 6.7: https://lore.kernel.org/netdev/20240108094709.050e22bc@hermes.local/
  - 6.8: https://lore.kernel.org/netdev/20240311094432.16bf9516@hermes.local/

  (Previous changelog:
  
https://lore.kernel.org/netdev/?q=s%3A%22%5BANNOUNCE%5D+iproute2%22+AND+NOT+s%3A%22Re%3A%22
  )

  ChangeLog from Debian:

  iproute2 (6.8.0-1) unstable; urgency=medium

[ Ceppo ]
* Update Italian po-debconf translation (Closes: #1063002)

[ Luca Boccassi ]
* Add build dependency on libnsl-dev (Closes: #1065214)
* Switch to pkgconf
* Update upstream source from tag 'upstream/6.8.0'
* Drop 0002-ss-show-extra-info-when-processes-is-not-used.patch, merged
  upstream
* Drop iproute2-doc package
* Drop tc/m_xt.so and tc/m_ipt.so, removed upstream

   -- Luca Boccassi <>  Tue, 12 Mar 2024 14:02:38 +

  iproute2 (6.7.0-2) unstable; urgency=medium

    * Backport fix for 'ss' output

   -- Luca Boccassi <>  Mon, 22 Jan 2024 12:24:29 +

  iproute2 (6.7.0-1) unstable; urgency=medium

    * Add Italian debconf translation (Closes: #1056582)
    * Update upstream source from tag 'upstream/6.7.0'
    * Bump copyright year ranges in d/copyright
    * Drop 0002-Revert-Makefile-ensure-CONF_USR_DIR-honours-the-libd.patch,
  merged upstream
    * Default config files moved from /usr/lib to /usr/share

   -- Luca Boccassi <>  Fri, 12 Jan 2024 21:47:59 +

  iproute2 (6.6.0-1) unstable; urgency=medium

    * Update upstream source from tag 'upstream/6.6.0'
    * Backport patch to fix configuration installation
    * Remove handling of qt_atm.so, dropped upstream

   -- Luca Boccassi <>  Sun, 05 Nov 2023 22:46:20 +

  iproute2 (6.5.0-5) unstable; urgency=medium

    * Use dh-sequence-movetousr

   -- Luca Boccassi <>  Tue, 24 Oct 2023 15:24:01 +0100

  iproute2 (6.5.0-4) unstable; urgency=medium

    * postinst: handle legacy config files only when upgrading from previous
  versions that shipped them
    * postinst: ensure that locally modified legacy config files are
  preserved as overrides on upgrade (Closes: #1051577)
    * Note configuration files location changes in NEWS

   -- Luca Boccassi <>  Sat, 16 Sep 2023 18:58:51 +0100

  iproute2 (6.5.0-3) unstable; urgency=medium

    * Remove further leftovers as part of upstream's move of config to /usr
  (Closes: #1051577)

   -- Luca Boccassi <>  Mon, 11 Sep 2023 09:42:12 +0100

  iproute2 (6.5.0-2) unstable; urgency=medium

    * Add maintscript to remove conffiles that upstream has moved to /usr
  (Closes: #1051577)

   -- Luca Boccassi <>  Sun, 10 Sep 2023 21:28:28 +0100

  iproute2 (6.5.0-1) unstable; urgency=medium

    [ Luca Boccassi ]
    * Use wildcard for Lintian overrides

    [ Peter Kvillegård ]
    * Add Swedish translation of debconf messages (Closes: #1050442)

    [ Luca Boccassi ]
    * Update upstream source from tag 'upstream/6.5.0'
    * Use cap_bpf instead of cap_sys_admin for ip vrf-exec
    * Package-provided config files are now shipped in /usr/iproute2 instead
  of /etc/iproute2

   -- Luca Boccassi <>  Sat, 09 Sep 2023 16:32:54 +0100

  iproute2 (6.4.0-1) unstable; urgency=medium

    * Fix patch header Forwarded field
    * Enable ELF metadata stamping
    * Update upstream source from tag 'upstream/6.4.0'
    * Update Lintian overrides

   -- Luca Boccassi <>  Fri, 30 Jun 2023 12:16:40 +0100

  iproute2 (6.3.0-1) unstable;

[Kernel-packages] [Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)

** Attachment added: "Upstream 6.8 changelog"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+attachment/5763790/+files/6.8-changes.txt

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

Title:
  [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from
  testing/unstable (main)

Status in iproute2 package in Ubuntu:
  Confirmed

Bug description:
  A few versions have been released and Ubuntu Noble still has the 6.1
  version (6.1.0-1ubuntu2) from one year ago. Could it be possible to
  import the latest version from Debian unstable fixing a bunch of
  issues and supporting features from more recent kernels?

  Please note that Ubuntu Noble 24.04 will probably be shipped with the
  v6.8 kernel [1]. IPRoute v6.1 supports features added up to the v6.1
  kernel, so missing the ones added to earlier versions. Switching to
  the v6.7 now should ease the upgrade to the v6.8 later.

  [1] https://discourse.ubuntu.com/t/introducing-kernel-6-8-for-
  the-24-04-noble-numbat-release/41958

  Upstream ChangeLog:

  - 6.2: https://lore.kernel.org/netdev/20230220105811.674bd304@hermes.local/
  - 6.3: https://lore.kernel.org/netdev/20230427090253.7a92616b@hermes.local/
  - 6.4: https://lore.kernel.org/netdev/20230626093137.2f302acc@hermes.local/
  - 6.5: https://lore.kernel.org/netdev/20230906093918.394a1b1d@hermes.local/
  - 6.6: https://lore.kernel.org/netdev/20231106090325.07092c87@hermes.local/
  - 6.7: https://lore.kernel.org/netdev/20240108094709.050e22bc@hermes.local/
  - 6.8: https://lore.kernel.org/netdev/20240311094432.16bf9516@hermes.local/

  (Previous changelog:
  
https://lore.kernel.org/netdev/?q=s%3A%22%5BANNOUNCE%5D+iproute2%22+AND+NOT+s%3A%22Re%3A%22
  )

  ChangeLog from Debian:

  iproute2 (6.8.0-1) unstable; urgency=medium

[ Ceppo ]
* Update Italian po-debconf translation (Closes: #1063002)

[ Luca Boccassi ]
* Add build dependency on libnsl-dev (Closes: #1065214)
* Switch to pkgconf
* Update upstream source from tag 'upstream/6.8.0'
* Drop 0002-ss-show-extra-info-when-processes-is-not-used.patch, merged
  upstream
* Drop iproute2-doc package
* Drop tc/m_xt.so and tc/m_ipt.so, removed upstream

   -- Luca Boccassi <>  Tue, 12 Mar 2024 14:02:38 +

  iproute2 (6.7.0-2) unstable; urgency=medium

    * Backport fix for 'ss' output

   -- Luca Boccassi <>  Mon, 22 Jan 2024 12:24:29 +

  iproute2 (6.7.0-1) unstable; urgency=medium

    * Add Italian debconf translation (Closes: #1056582)
    * Update upstream source from tag 'upstream/6.7.0'
    * Bump copyright year ranges in d/copyright
    * Drop 0002-Revert-Makefile-ensure-CONF_USR_DIR-honours-the-libd.patch,
  merged upstream
    * Default config files moved from /usr/lib to /usr/share

   -- Luca Boccassi <>  Fri, 12 Jan 2024 21:47:59 +

  iproute2 (6.6.0-1) unstable; urgency=medium

    * Update upstream source from tag 'upstream/6.6.0'
    * Backport patch to fix configuration installation
    * Remove handling of qt_atm.so, dropped upstream

   -- Luca Boccassi <>  Sun, 05 Nov 2023 22:46:20 +

  iproute2 (6.5.0-5) unstable; urgency=medium

    * Use dh-sequence-movetousr

   -- Luca Boccassi <>  Tue, 24 Oct 2023 15:24:01 +0100

  iproute2 (6.5.0-4) unstable; urgency=medium

    * postinst: handle legacy config files only when upgrading from previous
  versions that shipped them
    * postinst: ensure that locally modified legacy config files are
  preserved as overrides on upgrade (Closes: #1051577)
    * Note configuration files location changes in NEWS

   -- Luca Boccassi <>  Sat, 16 Sep 2023 18:58:51 +0100

  iproute2 (6.5.0-3) unstable; urgency=medium

    * Remove further leftovers as part of upstream's move of config to /usr
  (Closes: #1051577)

   -- Luca Boccassi <>  Mon, 11 Sep 2023 09:42:12 +0100

  iproute2 (6.5.0-2) unstable; urgency=medium

    * Add maintscript to remove conffiles that upstream has moved to /usr
  (Closes: #1051577)

   -- Luca Boccassi <>  Sun, 10 Sep 2023 21:28:28 +0100

  iproute2 (6.5.0-1) unstable; urgency=medium

    [ Luca Boccassi ]
    * Use wildcard for Lintian overrides

    [ Peter Kvillegård ]
    * Add Swedish translation of debconf messages (Closes: #1050442)

    [ Luca Boccassi ]
    * Update upstream source from tag 'upstream/6.5.0'
    * Use cap_bpf instead of cap_sys_admin for ip vrf-exec
    * Package-provided config files are now shipped in /usr/iproute2 instead
  of /etc/iproute2

   -- Luca Boccassi <>  Sat, 09 Sep 2023 16:32:54 +0100

  iproute2 (6.4.0-1) unstable; urgency=medium

    * Fix patch header Forwarded field
    * Enable ELF metadata stamping
    * Update upstream source from tag 'upstream/6.4.0'
    * Update Lintian overrides

   -- Luca Boccassi <>  Fri, 30 Jun 2023 12:16:40 +0100

  iproute2 (6.3.0-1) unstable;

[Kernel-packages] [Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)

** Attachment added: "Upstream 6.6 changelog"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+attachment/5763788/+files/6.6-changes.txt

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

Title:
  [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from
  testing/unstable (main)

Status in iproute2 package in Ubuntu:
  Confirmed

Bug description:
  A few versions have been released and Ubuntu Noble still has the 6.1
  version (6.1.0-1ubuntu2) from one year ago. Could it be possible to
  import the latest version from Debian unstable fixing a bunch of
  issues and supporting features from more recent kernels?

  Please note that Ubuntu Noble 24.04 will probably be shipped with the
  v6.8 kernel [1]. IPRoute v6.1 supports features added up to the v6.1
  kernel, so missing the ones added to earlier versions. Switching to
  the v6.7 now should ease the upgrade to the v6.8 later.

  [1] https://discourse.ubuntu.com/t/introducing-kernel-6-8-for-
  the-24-04-noble-numbat-release/41958

  Upstream ChangeLog:

  - 6.2: https://lore.kernel.org/netdev/20230220105811.674bd304@hermes.local/
  - 6.3: https://lore.kernel.org/netdev/20230427090253.7a92616b@hermes.local/
  - 6.4: https://lore.kernel.org/netdev/20230626093137.2f302acc@hermes.local/
  - 6.5: https://lore.kernel.org/netdev/20230906093918.394a1b1d@hermes.local/
  - 6.6: https://lore.kernel.org/netdev/20231106090325.07092c87@hermes.local/
  - 6.7: https://lore.kernel.org/netdev/20240108094709.050e22bc@hermes.local/
  - 6.8: https://lore.kernel.org/netdev/20240311094432.16bf9516@hermes.local/

  (Previous changelog:
  
https://lore.kernel.org/netdev/?q=s%3A%22%5BANNOUNCE%5D+iproute2%22+AND+NOT+s%3A%22Re%3A%22
  )

  ChangeLog from Debian:

  iproute2 (6.8.0-1) unstable; urgency=medium

[ Ceppo ]
* Update Italian po-debconf translation (Closes: #1063002)

[ Luca Boccassi ]
* Add build dependency on libnsl-dev (Closes: #1065214)
* Switch to pkgconf
* Update upstream source from tag 'upstream/6.8.0'
* Drop 0002-ss-show-extra-info-when-processes-is-not-used.patch, merged
  upstream
* Drop iproute2-doc package
* Drop tc/m_xt.so and tc/m_ipt.so, removed upstream

   -- Luca Boccassi <>  Tue, 12 Mar 2024 14:02:38 +

  iproute2 (6.7.0-2) unstable; urgency=medium

    * Backport fix for 'ss' output

   -- Luca Boccassi <>  Mon, 22 Jan 2024 12:24:29 +

  iproute2 (6.7.0-1) unstable; urgency=medium

    * Add Italian debconf translation (Closes: #1056582)
    * Update upstream source from tag 'upstream/6.7.0'
    * Bump copyright year ranges in d/copyright
    * Drop 0002-Revert-Makefile-ensure-CONF_USR_DIR-honours-the-libd.patch,
  merged upstream
    * Default config files moved from /usr/lib to /usr/share

   -- Luca Boccassi <>  Fri, 12 Jan 2024 21:47:59 +

  iproute2 (6.6.0-1) unstable; urgency=medium

    * Update upstream source from tag 'upstream/6.6.0'
    * Backport patch to fix configuration installation
    * Remove handling of qt_atm.so, dropped upstream

   -- Luca Boccassi <>  Sun, 05 Nov 2023 22:46:20 +

  iproute2 (6.5.0-5) unstable; urgency=medium

    * Use dh-sequence-movetousr

   -- Luca Boccassi <>  Tue, 24 Oct 2023 15:24:01 +0100

  iproute2 (6.5.0-4) unstable; urgency=medium

    * postinst: handle legacy config files only when upgrading from previous
  versions that shipped them
    * postinst: ensure that locally modified legacy config files are
  preserved as overrides on upgrade (Closes: #1051577)
    * Note configuration files location changes in NEWS

   -- Luca Boccassi <>  Sat, 16 Sep 2023 18:58:51 +0100

  iproute2 (6.5.0-3) unstable; urgency=medium

    * Remove further leftovers as part of upstream's move of config to /usr
  (Closes: #1051577)

   -- Luca Boccassi <>  Mon, 11 Sep 2023 09:42:12 +0100

  iproute2 (6.5.0-2) unstable; urgency=medium

    * Add maintscript to remove conffiles that upstream has moved to /usr
  (Closes: #1051577)

   -- Luca Boccassi <>  Sun, 10 Sep 2023 21:28:28 +0100

  iproute2 (6.5.0-1) unstable; urgency=medium

    [ Luca Boccassi ]
    * Use wildcard for Lintian overrides

    [ Peter Kvillegård ]
    * Add Swedish translation of debconf messages (Closes: #1050442)

    [ Luca Boccassi ]
    * Update upstream source from tag 'upstream/6.5.0'
    * Use cap_bpf instead of cap_sys_admin for ip vrf-exec
    * Package-provided config files are now shipped in /usr/iproute2 instead
  of /etc/iproute2

   -- Luca Boccassi <>  Sat, 09 Sep 2023 16:32:54 +0100

  iproute2 (6.4.0-1) unstable; urgency=medium

    * Fix patch header Forwarded field
    * Enable ELF metadata stamping
    * Update upstream source from tag 'upstream/6.4.0'
    * Update Lintian overrides

   -- Luca Boccassi <>  Fri, 30 Jun 2023 12:16:40 +0100

  iproute2 (6.3.0-1) unstable;

[Kernel-packages] [Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)

** Attachment added: "Upstream 6.5 changelog"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+attachment/5763787/+files/6.5-changes.txt

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

Title:
  [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from
  testing/unstable (main)

Status in iproute2 package in Ubuntu:
  Confirmed

Bug description:
  A few versions have been released and Ubuntu Noble still has the 6.1
  version (6.1.0-1ubuntu2) from one year ago. Could it be possible to
  import the latest version from Debian unstable fixing a bunch of
  issues and supporting features from more recent kernels?

  Please note that Ubuntu Noble 24.04 will probably be shipped with the
  v6.8 kernel [1]. IPRoute v6.1 supports features added up to the v6.1
  kernel, so missing the ones added to earlier versions. Switching to
  the v6.7 now should ease the upgrade to the v6.8 later.

  [1] https://discourse.ubuntu.com/t/introducing-kernel-6-8-for-
  the-24-04-noble-numbat-release/41958

  Upstream ChangeLog:

  - 6.2: https://lore.kernel.org/netdev/20230220105811.674bd304@hermes.local/
  - 6.3: https://lore.kernel.org/netdev/20230427090253.7a92616b@hermes.local/
  - 6.4: https://lore.kernel.org/netdev/20230626093137.2f302acc@hermes.local/
  - 6.5: https://lore.kernel.org/netdev/20230906093918.394a1b1d@hermes.local/
  - 6.6: https://lore.kernel.org/netdev/20231106090325.07092c87@hermes.local/
  - 6.7: https://lore.kernel.org/netdev/20240108094709.050e22bc@hermes.local/
  - 6.8: https://lore.kernel.org/netdev/20240311094432.16bf9516@hermes.local/

  (Previous changelog:
  
https://lore.kernel.org/netdev/?q=s%3A%22%5BANNOUNCE%5D+iproute2%22+AND+NOT+s%3A%22Re%3A%22
  )

  ChangeLog from Debian:

  iproute2 (6.8.0-1) unstable; urgency=medium

[ Ceppo ]
* Update Italian po-debconf translation (Closes: #1063002)

[ Luca Boccassi ]
* Add build dependency on libnsl-dev (Closes: #1065214)
* Switch to pkgconf
* Update upstream source from tag 'upstream/6.8.0'
* Drop 0002-ss-show-extra-info-when-processes-is-not-used.patch, merged
  upstream
* Drop iproute2-doc package
* Drop tc/m_xt.so and tc/m_ipt.so, removed upstream

   -- Luca Boccassi <>  Tue, 12 Mar 2024 14:02:38 +

  iproute2 (6.7.0-2) unstable; urgency=medium

    * Backport fix for 'ss' output

   -- Luca Boccassi <>  Mon, 22 Jan 2024 12:24:29 +

  iproute2 (6.7.0-1) unstable; urgency=medium

    * Add Italian debconf translation (Closes: #1056582)
    * Update upstream source from tag 'upstream/6.7.0'
    * Bump copyright year ranges in d/copyright
    * Drop 0002-Revert-Makefile-ensure-CONF_USR_DIR-honours-the-libd.patch,
  merged upstream
    * Default config files moved from /usr/lib to /usr/share

   -- Luca Boccassi <>  Fri, 12 Jan 2024 21:47:59 +

  iproute2 (6.6.0-1) unstable; urgency=medium

    * Update upstream source from tag 'upstream/6.6.0'
    * Backport patch to fix configuration installation
    * Remove handling of qt_atm.so, dropped upstream

   -- Luca Boccassi <>  Sun, 05 Nov 2023 22:46:20 +

  iproute2 (6.5.0-5) unstable; urgency=medium

    * Use dh-sequence-movetousr

   -- Luca Boccassi <>  Tue, 24 Oct 2023 15:24:01 +0100

  iproute2 (6.5.0-4) unstable; urgency=medium

    * postinst: handle legacy config files only when upgrading from previous
  versions that shipped them
    * postinst: ensure that locally modified legacy config files are
  preserved as overrides on upgrade (Closes: #1051577)
    * Note configuration files location changes in NEWS

   -- Luca Boccassi <>  Sat, 16 Sep 2023 18:58:51 +0100

  iproute2 (6.5.0-3) unstable; urgency=medium

    * Remove further leftovers as part of upstream's move of config to /usr
  (Closes: #1051577)

   -- Luca Boccassi <>  Mon, 11 Sep 2023 09:42:12 +0100

  iproute2 (6.5.0-2) unstable; urgency=medium

    * Add maintscript to remove conffiles that upstream has moved to /usr
  (Closes: #1051577)

   -- Luca Boccassi <>  Sun, 10 Sep 2023 21:28:28 +0100

  iproute2 (6.5.0-1) unstable; urgency=medium

    [ Luca Boccassi ]
    * Use wildcard for Lintian overrides

    [ Peter Kvillegård ]
    * Add Swedish translation of debconf messages (Closes: #1050442)

    [ Luca Boccassi ]
    * Update upstream source from tag 'upstream/6.5.0'
    * Use cap_bpf instead of cap_sys_admin for ip vrf-exec
    * Package-provided config files are now shipped in /usr/iproute2 instead
  of /etc/iproute2

   -- Luca Boccassi <>  Sat, 09 Sep 2023 16:32:54 +0100

  iproute2 (6.4.0-1) unstable; urgency=medium

    * Fix patch header Forwarded field
    * Enable ELF metadata stamping
    * Update upstream source from tag 'upstream/6.4.0'
    * Update Lintian overrides

   -- Luca Boccassi <>  Fri, 30 Jun 2023 12:16:40 +0100

  iproute2 (6.3.0-1) unstable;

[Kernel-packages] [Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)

** Attachment added: "Upstream 6.4 changelog"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+attachment/5763786/+files/6.4-changes.txt

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

Title:
  [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from
  testing/unstable (main)

Status in iproute2 package in Ubuntu:
  Confirmed

Bug description:
  A few versions have been released and Ubuntu Noble still has the 6.1
  version (6.1.0-1ubuntu2) from one year ago. Could it be possible to
  import the latest version from Debian unstable fixing a bunch of
  issues and supporting features from more recent kernels?

  Please note that Ubuntu Noble 24.04 will probably be shipped with the
  v6.8 kernel [1]. IPRoute v6.1 supports features added up to the v6.1
  kernel, so missing the ones added to earlier versions. Switching to
  the v6.7 now should ease the upgrade to the v6.8 later.

  [1] https://discourse.ubuntu.com/t/introducing-kernel-6-8-for-
  the-24-04-noble-numbat-release/41958

  Upstream ChangeLog:

  - 6.2: https://lore.kernel.org/netdev/20230220105811.674bd304@hermes.local/
  - 6.3: https://lore.kernel.org/netdev/20230427090253.7a92616b@hermes.local/
  - 6.4: https://lore.kernel.org/netdev/20230626093137.2f302acc@hermes.local/
  - 6.5: https://lore.kernel.org/netdev/20230906093918.394a1b1d@hermes.local/
  - 6.6: https://lore.kernel.org/netdev/20231106090325.07092c87@hermes.local/
  - 6.7: https://lore.kernel.org/netdev/20240108094709.050e22bc@hermes.local/
  - 6.8: https://lore.kernel.org/netdev/20240311094432.16bf9516@hermes.local/

  (Previous changelog:
  
https://lore.kernel.org/netdev/?q=s%3A%22%5BANNOUNCE%5D+iproute2%22+AND+NOT+s%3A%22Re%3A%22
  )

  ChangeLog from Debian:

  iproute2 (6.8.0-1) unstable; urgency=medium

[ Ceppo ]
* Update Italian po-debconf translation (Closes: #1063002)

[ Luca Boccassi ]
* Add build dependency on libnsl-dev (Closes: #1065214)
* Switch to pkgconf
* Update upstream source from tag 'upstream/6.8.0'
* Drop 0002-ss-show-extra-info-when-processes-is-not-used.patch, merged
  upstream
* Drop iproute2-doc package
* Drop tc/m_xt.so and tc/m_ipt.so, removed upstream

   -- Luca Boccassi <>  Tue, 12 Mar 2024 14:02:38 +

  iproute2 (6.7.0-2) unstable; urgency=medium

    * Backport fix for 'ss' output

   -- Luca Boccassi <>  Mon, 22 Jan 2024 12:24:29 +

  iproute2 (6.7.0-1) unstable; urgency=medium

    * Add Italian debconf translation (Closes: #1056582)
    * Update upstream source from tag 'upstream/6.7.0'
    * Bump copyright year ranges in d/copyright
    * Drop 0002-Revert-Makefile-ensure-CONF_USR_DIR-honours-the-libd.patch,
  merged upstream
    * Default config files moved from /usr/lib to /usr/share

   -- Luca Boccassi <>  Fri, 12 Jan 2024 21:47:59 +

  iproute2 (6.6.0-1) unstable; urgency=medium

    * Update upstream source from tag 'upstream/6.6.0'
    * Backport patch to fix configuration installation
    * Remove handling of qt_atm.so, dropped upstream

   -- Luca Boccassi <>  Sun, 05 Nov 2023 22:46:20 +

  iproute2 (6.5.0-5) unstable; urgency=medium

    * Use dh-sequence-movetousr

   -- Luca Boccassi <>  Tue, 24 Oct 2023 15:24:01 +0100

  iproute2 (6.5.0-4) unstable; urgency=medium

    * postinst: handle legacy config files only when upgrading from previous
  versions that shipped them
    * postinst: ensure that locally modified legacy config files are
  preserved as overrides on upgrade (Closes: #1051577)
    * Note configuration files location changes in NEWS

   -- Luca Boccassi <>  Sat, 16 Sep 2023 18:58:51 +0100

  iproute2 (6.5.0-3) unstable; urgency=medium

    * Remove further leftovers as part of upstream's move of config to /usr
  (Closes: #1051577)

   -- Luca Boccassi <>  Mon, 11 Sep 2023 09:42:12 +0100

  iproute2 (6.5.0-2) unstable; urgency=medium

    * Add maintscript to remove conffiles that upstream has moved to /usr
  (Closes: #1051577)

   -- Luca Boccassi <>  Sun, 10 Sep 2023 21:28:28 +0100

  iproute2 (6.5.0-1) unstable; urgency=medium

    [ Luca Boccassi ]
    * Use wildcard for Lintian overrides

    [ Peter Kvillegård ]
    * Add Swedish translation of debconf messages (Closes: #1050442)

    [ Luca Boccassi ]
    * Update upstream source from tag 'upstream/6.5.0'
    * Use cap_bpf instead of cap_sys_admin for ip vrf-exec
    * Package-provided config files are now shipped in /usr/iproute2 instead
  of /etc/iproute2

   -- Luca Boccassi <>  Sat, 09 Sep 2023 16:32:54 +0100

  iproute2 (6.4.0-1) unstable; urgency=medium

    * Fix patch header Forwarded field
    * Enable ELF metadata stamping
    * Update upstream source from tag 'upstream/6.4.0'
    * Update Lintian overrides

   -- Luca Boccassi <>  Fri, 30 Jun 2023 12:16:40 +0100

  iproute2 (6.3.0-1) unstable;

[Kernel-packages] [Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)

It seems like this bug should now be a FFe (see
https://wiki.ubuntu.com/FreezeExceptionProcess) - so converting...

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

Title:
  [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from
  testing/unstable (main)

Status in iproute2 package in Ubuntu:
  Confirmed

Bug description:
  A few versions have been released and Ubuntu Noble still has the 6.1
  version (6.1.0-1ubuntu2) from one year ago. Could it be possible to
  import the latest version from Debian unstable fixing a bunch of
  issues and supporting features from more recent kernels?

  Please note that Ubuntu Noble 24.04 will probably be shipped with the
  v6.8 kernel [1]. IPRoute v6.1 supports features added up to the v6.1
  kernel, so missing the ones added to earlier versions. Switching to
  the v6.7 now should ease the upgrade to the v6.8 later.

  [1] https://discourse.ubuntu.com/t/introducing-kernel-6-8-for-
  the-24-04-noble-numbat-release/41958

  Upstream ChangeLog:

  - 6.2: https://lore.kernel.org/netdev/20230220105811.674bd304@hermes.local/
  - 6.3: https://lore.kernel.org/netdev/20230427090253.7a92616b@hermes.local/
  - 6.4: https://lore.kernel.org/netdev/20230626093137.2f302acc@hermes.local/
  - 6.5: https://lore.kernel.org/netdev/20230906093918.394a1b1d@hermes.local/
  - 6.6: https://lore.kernel.org/netdev/20231106090325.07092c87@hermes.local/
  - 6.7: https://lore.kernel.org/netdev/20240108094709.050e22bc@hermes.local/
  - 6.8: https://lore.kernel.org/netdev/20240311094432.16bf9516@hermes.local/

  (Previous changelog:
  
https://lore.kernel.org/netdev/?q=s%3A%22%5BANNOUNCE%5D+iproute2%22+AND+NOT+s%3A%22Re%3A%22
  )

  ChangeLog from Debian:

  iproute2 (6.8.0-1) unstable; urgency=medium

[ Ceppo ]
* Update Italian po-debconf translation (Closes: #1063002)

[ Luca Boccassi ]
* Add build dependency on libnsl-dev (Closes: #1065214)
* Switch to pkgconf
* Update upstream source from tag 'upstream/6.8.0'
* Drop 0002-ss-show-extra-info-when-processes-is-not-used.patch, merged
  upstream
* Drop iproute2-doc package
* Drop tc/m_xt.so and tc/m_ipt.so, removed upstream

   -- Luca Boccassi <>  Tue, 12 Mar 2024 14:02:38 +

  iproute2 (6.7.0-2) unstable; urgency=medium

    * Backport fix for 'ss' output

   -- Luca Boccassi <>  Mon, 22 Jan 2024 12:24:29 +

  iproute2 (6.7.0-1) unstable; urgency=medium

    * Add Italian debconf translation (Closes: #1056582)
    * Update upstream source from tag 'upstream/6.7.0'
    * Bump copyright year ranges in d/copyright
    * Drop 0002-Revert-Makefile-ensure-CONF_USR_DIR-honours-the-libd.patch,
  merged upstream
    * Default config files moved from /usr/lib to /usr/share

   -- Luca Boccassi <>  Fri, 12 Jan 2024 21:47:59 +

  iproute2 (6.6.0-1) unstable; urgency=medium

    * Update upstream source from tag 'upstream/6.6.0'
    * Backport patch to fix configuration installation
    * Remove handling of qt_atm.so, dropped upstream

   -- Luca Boccassi <>  Sun, 05 Nov 2023 22:46:20 +

  iproute2 (6.5.0-5) unstable; urgency=medium

    * Use dh-sequence-movetousr

   -- Luca Boccassi <>  Tue, 24 Oct 2023 15:24:01 +0100

  iproute2 (6.5.0-4) unstable; urgency=medium

    * postinst: handle legacy config files only when upgrading from previous
  versions that shipped them
    * postinst: ensure that locally modified legacy config files are
  preserved as overrides on upgrade (Closes: #1051577)
    * Note configuration files location changes in NEWS

   -- Luca Boccassi <>  Sat, 16 Sep 2023 18:58:51 +0100

  iproute2 (6.5.0-3) unstable; urgency=medium

    * Remove further leftovers as part of upstream's move of config to /usr
  (Closes: #1051577)

   -- Luca Boccassi <>  Mon, 11 Sep 2023 09:42:12 +0100

  iproute2 (6.5.0-2) unstable; urgency=medium

    * Add maintscript to remove conffiles that upstream has moved to /usr
  (Closes: #1051577)

   -- Luca Boccassi <>  Sun, 10 Sep 2023 21:28:28 +0100

  iproute2 (6.5.0-1) unstable; urgency=medium

    [ Luca Boccassi ]
    * Use wildcard for Lintian overrides

    [ Peter Kvillegård ]
    * Add Swedish translation of debconf messages (Closes: #1050442)

    [ Luca Boccassi ]
    * Update upstream source from tag 'upstream/6.5.0'
    * Use cap_bpf instead of cap_sys_admin for ip vrf-exec
    * Package-provided config files are now shipped in /usr/iproute2 instead
  of /etc/iproute2

   -- Luca Boccassi <>  Sat, 09 Sep 2023 16:32:54 +0100

  iproute2 (6.4.0-1) unstable; urgency=medium

    * Fix patch header Forwarded field
    * Enable ELF metadata stamping
    * Update upstream source from tag 'upstream/6.4.0'
    * Update Lintian overrides

   -- Luca Boccassi <>  Fri, 30 Jun 2023 12:16:40 +0100

  iproute2 (6.3.0-1) unstable; urgency=medium

    * Drop obsolete

[Kernel-packages] [Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)

** Attachment added: "Upstream 6.2 changelog"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+attachment/5763784/+files/6.2-changes.txt

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

Title:
  [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from
  testing/unstable (main)

Status in iproute2 package in Ubuntu:
  Confirmed

Bug description:
  A few versions have been released and Ubuntu Noble still has the 6.1
  version (6.1.0-1ubuntu2) from one year ago. Could it be possible to
  import the latest version from Debian unstable fixing a bunch of
  issues and supporting features from more recent kernels?

  Please note that Ubuntu Noble 24.04 will probably be shipped with the
  v6.8 kernel [1]. IPRoute v6.1 supports features added up to the v6.1
  kernel, so missing the ones added to earlier versions. Switching to
  the v6.7 now should ease the upgrade to the v6.8 later.

  [1] https://discourse.ubuntu.com/t/introducing-kernel-6-8-for-
  the-24-04-noble-numbat-release/41958

  Upstream ChangeLog:

  - 6.2: https://lore.kernel.org/netdev/20230220105811.674bd304@hermes.local/
  - 6.3: https://lore.kernel.org/netdev/20230427090253.7a92616b@hermes.local/
  - 6.4: https://lore.kernel.org/netdev/20230626093137.2f302acc@hermes.local/
  - 6.5: https://lore.kernel.org/netdev/20230906093918.394a1b1d@hermes.local/
  - 6.6: https://lore.kernel.org/netdev/20231106090325.07092c87@hermes.local/
  - 6.7: https://lore.kernel.org/netdev/20240108094709.050e22bc@hermes.local/
  - 6.8: https://lore.kernel.org/netdev/20240311094432.16bf9516@hermes.local/

  (Previous changelog:
  
https://lore.kernel.org/netdev/?q=s%3A%22%5BANNOUNCE%5D+iproute2%22+AND+NOT+s%3A%22Re%3A%22
  )

  ChangeLog from Debian:

  iproute2 (6.8.0-1) unstable; urgency=medium

[ Ceppo ]
* Update Italian po-debconf translation (Closes: #1063002)

[ Luca Boccassi ]
* Add build dependency on libnsl-dev (Closes: #1065214)
* Switch to pkgconf
* Update upstream source from tag 'upstream/6.8.0'
* Drop 0002-ss-show-extra-info-when-processes-is-not-used.patch, merged
  upstream
* Drop iproute2-doc package
* Drop tc/m_xt.so and tc/m_ipt.so, removed upstream

   -- Luca Boccassi <>  Tue, 12 Mar 2024 14:02:38 +

  iproute2 (6.7.0-2) unstable; urgency=medium

    * Backport fix for 'ss' output

   -- Luca Boccassi <>  Mon, 22 Jan 2024 12:24:29 +

  iproute2 (6.7.0-1) unstable; urgency=medium

    * Add Italian debconf translation (Closes: #1056582)
    * Update upstream source from tag 'upstream/6.7.0'
    * Bump copyright year ranges in d/copyright
    * Drop 0002-Revert-Makefile-ensure-CONF_USR_DIR-honours-the-libd.patch,
  merged upstream
    * Default config files moved from /usr/lib to /usr/share

   -- Luca Boccassi <>  Fri, 12 Jan 2024 21:47:59 +

  iproute2 (6.6.0-1) unstable; urgency=medium

    * Update upstream source from tag 'upstream/6.6.0'
    * Backport patch to fix configuration installation
    * Remove handling of qt_atm.so, dropped upstream

   -- Luca Boccassi <>  Sun, 05 Nov 2023 22:46:20 +

  iproute2 (6.5.0-5) unstable; urgency=medium

    * Use dh-sequence-movetousr

   -- Luca Boccassi <>  Tue, 24 Oct 2023 15:24:01 +0100

  iproute2 (6.5.0-4) unstable; urgency=medium

    * postinst: handle legacy config files only when upgrading from previous
  versions that shipped them
    * postinst: ensure that locally modified legacy config files are
  preserved as overrides on upgrade (Closes: #1051577)
    * Note configuration files location changes in NEWS

   -- Luca Boccassi <>  Sat, 16 Sep 2023 18:58:51 +0100

  iproute2 (6.5.0-3) unstable; urgency=medium

    * Remove further leftovers as part of upstream's move of config to /usr
  (Closes: #1051577)

   -- Luca Boccassi <>  Mon, 11 Sep 2023 09:42:12 +0100

  iproute2 (6.5.0-2) unstable; urgency=medium

    * Add maintscript to remove conffiles that upstream has moved to /usr
  (Closes: #1051577)

   -- Luca Boccassi <>  Sun, 10 Sep 2023 21:28:28 +0100

  iproute2 (6.5.0-1) unstable; urgency=medium

    [ Luca Boccassi ]
    * Use wildcard for Lintian overrides

    [ Peter Kvillegård ]
    * Add Swedish translation of debconf messages (Closes: #1050442)

    [ Luca Boccassi ]
    * Update upstream source from tag 'upstream/6.5.0'
    * Use cap_bpf instead of cap_sys_admin for ip vrf-exec
    * Package-provided config files are now shipped in /usr/iproute2 instead
  of /etc/iproute2

   -- Luca Boccassi <>  Sat, 09 Sep 2023 16:32:54 +0100

  iproute2 (6.4.0-1) unstable; urgency=medium

    * Fix patch header Forwarded field
    * Enable ELF metadata stamping
    * Update upstream source from tag 'upstream/6.4.0'
    * Update Lintian overrides

   -- Luca Boccassi <>  Fri, 30 Jun 2023 12:16:40 +0100

  iproute2 (6.3.0-1) unstable;

[Kernel-packages] [Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)

** Attachment added: "Upstream 6.3 changelog"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+attachment/5763785/+files/6.3-changes.txt

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

Title:
  [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from
  testing/unstable (main)

Status in iproute2 package in Ubuntu:
  Confirmed

Bug description:
  A few versions have been released and Ubuntu Noble still has the 6.1
  version (6.1.0-1ubuntu2) from one year ago. Could it be possible to
  import the latest version from Debian unstable fixing a bunch of
  issues and supporting features from more recent kernels?

  Please note that Ubuntu Noble 24.04 will probably be shipped with the
  v6.8 kernel [1]. IPRoute v6.1 supports features added up to the v6.1
  kernel, so missing the ones added to earlier versions. Switching to
  the v6.7 now should ease the upgrade to the v6.8 later.

  [1] https://discourse.ubuntu.com/t/introducing-kernel-6-8-for-
  the-24-04-noble-numbat-release/41958

  Upstream ChangeLog:

  - 6.2: https://lore.kernel.org/netdev/20230220105811.674bd304@hermes.local/
  - 6.3: https://lore.kernel.org/netdev/20230427090253.7a92616b@hermes.local/
  - 6.4: https://lore.kernel.org/netdev/20230626093137.2f302acc@hermes.local/
  - 6.5: https://lore.kernel.org/netdev/20230906093918.394a1b1d@hermes.local/
  - 6.6: https://lore.kernel.org/netdev/20231106090325.07092c87@hermes.local/
  - 6.7: https://lore.kernel.org/netdev/20240108094709.050e22bc@hermes.local/
  - 6.8: https://lore.kernel.org/netdev/20240311094432.16bf9516@hermes.local/

  (Previous changelog:
  
https://lore.kernel.org/netdev/?q=s%3A%22%5BANNOUNCE%5D+iproute2%22+AND+NOT+s%3A%22Re%3A%22
  )

  ChangeLog from Debian:

  iproute2 (6.8.0-1) unstable; urgency=medium

[ Ceppo ]
* Update Italian po-debconf translation (Closes: #1063002)

[ Luca Boccassi ]
* Add build dependency on libnsl-dev (Closes: #1065214)
* Switch to pkgconf
* Update upstream source from tag 'upstream/6.8.0'
* Drop 0002-ss-show-extra-info-when-processes-is-not-used.patch, merged
  upstream
* Drop iproute2-doc package
* Drop tc/m_xt.so and tc/m_ipt.so, removed upstream

   -- Luca Boccassi <>  Tue, 12 Mar 2024 14:02:38 +

  iproute2 (6.7.0-2) unstable; urgency=medium

    * Backport fix for 'ss' output

   -- Luca Boccassi <>  Mon, 22 Jan 2024 12:24:29 +

  iproute2 (6.7.0-1) unstable; urgency=medium

    * Add Italian debconf translation (Closes: #1056582)
    * Update upstream source from tag 'upstream/6.7.0'
    * Bump copyright year ranges in d/copyright
    * Drop 0002-Revert-Makefile-ensure-CONF_USR_DIR-honours-the-libd.patch,
  merged upstream
    * Default config files moved from /usr/lib to /usr/share

   -- Luca Boccassi <>  Fri, 12 Jan 2024 21:47:59 +

  iproute2 (6.6.0-1) unstable; urgency=medium

    * Update upstream source from tag 'upstream/6.6.0'
    * Backport patch to fix configuration installation
    * Remove handling of qt_atm.so, dropped upstream

   -- Luca Boccassi <>  Sun, 05 Nov 2023 22:46:20 +

  iproute2 (6.5.0-5) unstable; urgency=medium

    * Use dh-sequence-movetousr

   -- Luca Boccassi <>  Tue, 24 Oct 2023 15:24:01 +0100

  iproute2 (6.5.0-4) unstable; urgency=medium

    * postinst: handle legacy config files only when upgrading from previous
  versions that shipped them
    * postinst: ensure that locally modified legacy config files are
  preserved as overrides on upgrade (Closes: #1051577)
    * Note configuration files location changes in NEWS

   -- Luca Boccassi <>  Sat, 16 Sep 2023 18:58:51 +0100

  iproute2 (6.5.0-3) unstable; urgency=medium

    * Remove further leftovers as part of upstream's move of config to /usr
  (Closes: #1051577)

   -- Luca Boccassi <>  Mon, 11 Sep 2023 09:42:12 +0100

  iproute2 (6.5.0-2) unstable; urgency=medium

    * Add maintscript to remove conffiles that upstream has moved to /usr
  (Closes: #1051577)

   -- Luca Boccassi <>  Sun, 10 Sep 2023 21:28:28 +0100

  iproute2 (6.5.0-1) unstable; urgency=medium

    [ Luca Boccassi ]
    * Use wildcard for Lintian overrides

    [ Peter Kvillegård ]
    * Add Swedish translation of debconf messages (Closes: #1050442)

    [ Luca Boccassi ]
    * Update upstream source from tag 'upstream/6.5.0'
    * Use cap_bpf instead of cap_sys_admin for ip vrf-exec
    * Package-provided config files are now shipped in /usr/iproute2 instead
  of /etc/iproute2

   -- Luca Boccassi <>  Sat, 09 Sep 2023 16:32:54 +0100

  iproute2 (6.4.0-1) unstable; urgency=medium

    * Fix patch header Forwarded field
    * Enable ELF metadata stamping
    * Update upstream source from tag 'upstream/6.4.0'
    * Update Lintian overrides

   -- Luca Boccassi <>  Fri, 30 Jun 2023 12:16:40 +0100

  iproute2 (6.3.0-1) unstable;

[Kernel-packages] [Bug 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).

2024-04-11 Thread Chrescht

No issue in kernel  6.5.0-26-generic.

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

Title:
  Remote filesystems mounted as CIFS not working after update to Kernel
  "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi
  #17-Ubuntu" (aarch64).

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in linux-raspi package in Ubuntu:
  Confirmed

Bug description:
  Remote filesystems mounted as CIFS are not working after update to
  Kernel "6.5.0-27-generic #28-Ubuntu" for x86_64 (and also after
  updating to Kernel "6.5.0-1014-raspi #17-Ubuntu" in aarch64).

  The remote filesystem is correctly mounted and seems to work but
  trying to write data to the filesystem ends in a kernel error
  exception. After that error the CIFS filesystem just became unusable.

  Previous Kernel version works correctly.

  =
  Example for Kernel "6.5.0-27-generic #28-Ubuntu" (x86_64)
  =
  # lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10

  # uname -a
  Linux fpgmsi 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar  7 
18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  # cat /proc/version_signature
  Ubuntu 6.5.0-27.28-generic 6.5.13

  
  How to reproduce the problem
  
  For instance, I'm using KeePassXC 
(https://launchpad.net/ubuntu/+source/keepassxc) to update a database located 
at CIFS filesystem. Any change done to that database causes this Kernel error 
exception:

  abr 11 09:34:59 fpgmsi kernel: BUG: unable to handle page fault for address: 
fffe
  abr 11 09:34:59 fpgmsi kernel: #PF: supervisor read access in kernel mode
  abr 11 09:34:59 fpgmsi kernel: #PF: error_code(0x) - not-present page
  abr 11 09:34:59 fpgmsi kernel: PGD f45a3f067 P4D f45a3f067 PUD f45a41067 PMD 
0 
  abr 11 09:34:59 fpgmsi kernel: Oops:  [#1] PREEMPT SMP NOPTI
  abr 11 09:34:59 fpgmsi kernel: CPU: 0 PID: 28103 Comm: Thread (pooled) 
Tainted: P   OE  6.5.0-27-generic #28-Ubuntu
  abr 11 09:34:59 fpgmsi kernel: Hardware name: Micro-Star International Co., 
Ltd. MAG Z690 Codex X5 (MS-B930)/PRO Z690-A WIFI (MS-7D25), BIOS D.50 04/26/2022
  abr 11 09:34:59 fpgmsi kernel: RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs]
  abr 11 09:34:59 fpgmsi kernel: Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 
0c 53 48 83 ec 08 48 8b 7f 30 44 89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 
db 74 77 <48> 8b 13 b8 00 10 00 00 f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3
  abr 11 09:34:59 fpgmsi kernel: RSP: 0018:aab6865ffbf8 EFLAGS: 00010282
  abr 11 09:34:59 fpgmsi kernel: RAX:  RBX: fffe 
RCX: 
  abr 11 09:34:59 fpgmsi kernel: RDX:  RSI:  
RDI: 
  abr 11 09:34:59 fpgmsi kernel: RBP: aab6865ffc28 R08: 0001 
R09: 
  abr 11 09:34:59 fpgmsi kernel: R10: 00023854 R11:  
R12: 
  abr 11 09:34:59 fpgmsi kernel: R13: aab6865ffc78 R14: 906675d8aed0 
R15: aab6865ffc70
  abr 11 09:34:59 fpgmsi kernel: FS:  7bd4d594b6c0() 
GS:90753f80() knlGS:
  abr 11 09:34:59 fpgmsi kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  abr 11 09:34:59 fpgmsi kernel: CR2: fffe CR3: 00017022a000 
CR4: 00750ef0
  abr 11 09:34:59 fpgmsi kernel: PKRU: 5554
  abr 11 09:34:59 fpgmsi kernel: Call Trace:
  abr 11 09:34:59 fpgmsi kernel:  
  abr 11 09:34:59 fpgmsi kernel:  ? show_regs+0x6d/0x80
  abr 11 09:34:59 fpgmsi kernel:  ? __die+0x24/0x80
  abr 11 09:34:59 fpgmsi kernel:  ? page_fault_oops+0x99/0x1b0
  abr 11 09:34:59 fpgmsi kernel:  ? kernelmode_fixup_or_oops+0xb2/0x140
  abr 11 09:34:59 fpgmsi kernel:  ? __bad_area_nosemaphore+0x1a5/0x2c0
  abr 11 09:34:59 fpgmsi kernel:  ? bad_area_nosemaphore+0x16/0x30
  abr 11 09:34:59 fpgmsi kernel:  ? do_kern_addr_fault+0x7b/0xa0
  abr 11 09:34:59 fpgmsi kernel:  ? exc_page_fault+0x1a4/0x1b0
  abr 11 09:34:59 fpgmsi kernel:  ? asm_exc_page_fault+0x27/0x30
  abr 11 09:34:59 fpgmsi kernel:  ? cifs_flush_folio+0x41/0xf0 [cifs]
  abr 11 09:34:59 fpgmsi kernel:  ? cifs_flush_folio+0x37/0xf0 [cifs]
  abr 11 09:34:59 fpgmsi kernel:  cifs_remap_file_range+0x172/0x660 [cifs]
  abr 11 09:34:59 fpgmsi kernel:  do_clone_file_range+0x101/0x2d0
  abr 11 09:34:59 fpgmsi kernel:  vfs_clone_file_range+0x3f/0x150
  abr 11 09:34:59 fpgmsi kernel:  ioctl_file_clone+0x52/0xc0
  abr 11 09:34:59 fpgmsi kernel:  do_vfs_ioctl+0x68f/0x910
  abr 11 09:34:59 fpgmsi kernel:  ? __fget_light+0xa5/0x120
  abr 11 09:34:59 fpgmsi kernel:  __x64_sys_ioctl+0x7d/0xf0
  abr 11 09:34:59 fpgmsi kernel:

[Kernel-packages] [Bug 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).

2024-04-11 Thread Pgenest

Same issue when I copy files from a Synology smb share to another directory on 
the same smb share
Issue occured after system update.


$ lsb_release -rd
No LSB modules are available.
Description:Ubuntu 23.10
Release:23.10


$ uname -a
Linux Panoramix 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar  7 
18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux


$ cat /proc/version_signature
Ubuntu 6.5.0-27.28-generic 6.5.13



/var/log/syslog

2024-04-11T15:20:25.107768+02:00 Panoramix kernel: [ 5748.234124] BUG: unable 
to handle page fault for address: fffe
2024-04-11T15:20:25.107782+02:00 Panoramix kernel: [ 5748.234132] #PF: 
supervisor read access in kernel mode
2024-04-11T15:20:25.107784+02:00 Panoramix kernel: [ 5748.234136] #PF: 
error_code(0x) - not-present page
2024-04-11T15:20:25.107786+02:00 Panoramix kernel: [ 5748.234138] PGD 44d43f067 
P4D 44d43f067 PUD 44d441067 PMD 0 
2024-04-11T15:20:25.107788+02:00 Panoramix kernel: [ 5748.234146] Oops:  
[#1] PREEMPT SMP NOPTI
2024-04-11T15:20:25.107790+02:00 Panoramix kernel: [ 5748.234150] CPU: 10 PID: 
326370 Comm: pool-nemo Tainted: G   OE  6.5.0-27-generic #28-Ubuntu
2024-04-11T15:20:25.107792+02:00 Panoramix kernel: [ 5748.234155] Hardware 
name: Micro-Star International Co., Ltd. MS-7C56/MPG B550 GAMING PLUS 
(MS-7C56), BIOS 1.90 03/17/2022
2024-04-11T15:20:25.107794+02:00 Panoramix kernel: [ 5748.234158] RIP: 
0010:cifs_flush_folio+0x41/0xf0 [cifs]
2024-04-11T15:20:25.107809+02:00 Panoramix kernel: [ 5748.234214] Code: 49 89 
cd 31 c9 41 54 49 89 f4 48 c1 ee 0c 53 48 83 ec 08 48 8b 7f 30 44 89 45 d4 e8 
79 23 f5 e0 48 89 c3 31 c0 48 85 db 74 77 <48> 8b 13 b8 00 10 00 00 f7 c2 00 00 
01 00 74 10 0f b6 4b 51 48 d3
2024-04-11T15:20:25.107811+02:00 Panoramix kernel: [ 5748.234217] RSP: 
0018:acb394a9fc30 EFLAGS: 00010282
2024-04-11T15:20:25.107813+02:00 Panoramix kernel: [ 5748.234221] RAX: 
 RBX: fffe RCX: 
2024-04-11T15:20:25.107815+02:00 Panoramix kernel: [ 5748.234223] RDX: 
 RSI:  RDI: 
2024-04-11T15:20:25.107817+02:00 Panoramix kernel: [ 5748.234226] RBP: 
acb394a9fc60 R08: 0001 R09: 
2024-04-11T15:20:25.107819+02:00 Panoramix kernel: [ 5748.234228] R10: 
3950 R11:  R12: 
2024-04-11T15:20:25.107821+02:00 Panoramix kernel: [ 5748.234230] R13: 
acb394a9fcb0 R14: 97b687327508 R15: acb394a9fca8
2024-04-11T15:20:25.107823+02:00 Panoramix kernel: [ 5748.234233] FS:  
79a0b57f26c0() GS:97bd0dc8() knlGS:
2024-04-11T15:20:25.107825+02:00 Panoramix kernel: [ 5748.234236] CS:  0010 DS: 
 ES:  CR0: 80050033
2024-04-11T15:20:25.107826+02:00 Panoramix kernel: [ 5748.234239] CR2: 
fffe CR3: 00018f466000 CR4: 00750ee0
2024-04-11T15:20:25.107828+02:00 Panoramix kernel: [ 5748.234242] PKRU: 5554
2024-04-11T15:20:25.107830+02:00 Panoramix kernel: [ 5748.234244] Call Trace:
2024-04-11T15:20:25.107831+02:00 Panoramix kernel: [ 5748.234247]  
2024-04-11T15:20:25.107833+02:00 Panoramix kernel: [ 5748.234251]  ? 
show_regs+0x6d/0x80
2024-04-11T15:20:25.107835+02:00 Panoramix kernel: [ 5748.234258]  ? 
__die+0x24/0x80
2024-04-11T15:20:25.107837+02:00 Panoramix kernel: [ 5748.234263]  ? 
page_fault_oops+0x99/0x1b0
2024-04-11T15:20:25.107839+02:00 Panoramix kernel: [ 5748.234270]  ? 
kernelmode_fixup_or_oops+0xb2/0x140
2024-04-11T15:20:25.107841+02:00 Panoramix kernel: [ 5748.234274]  ? 
__bad_area_nosemaphore+0x1a5/0x2c0
2024-04-11T15:20:25.107843+02:00 Panoramix kernel: [ 5748.234279]  ? 
bad_area_nosemaphore+0x16/0x30
2024-04-11T15:20:25.107845+02:00 Panoramix kernel: [ 5748.234283]  ? 
do_kern_addr_fault+0x7b/0xa0
2024-04-11T15:20:25.107847+02:00 Panoramix kernel: [ 5748.234287]  ? 
exc_page_fault+0x1a4/0x1b0
2024-04-11T15:20:25.107848+02:00 Panoramix kernel: [ 5748.234293]  ? 
asm_exc_page_fault+0x27/0x30
2024-04-11T15:20:25.107850+02:00 Panoramix kernel: [ 5748.234302]  ? 
cifs_flush_folio+0x41/0xf0 [cifs]
2024-04-11T15:20:25.107851+02:00 Panoramix kernel: [ 5748.234340]  
cifs_remap_file_range+0x172/0x660 [cifs]
2024-04-11T15:20:25.107852+02:00 Panoramix kernel: [ 5748.234378]  
do_clone_file_range+0x104/0x2d0
2024-04-11T15:20:25.107854+02:00 Panoramix kernel: [ 5748.234388]  
vfs_clone_file_range+0x3f/0x150
2024-04-11T15:20:25.107864+02:00 Panoramix kernel: [ 5748.234393]  
ioctl_file_clone+0x52/0xc0
2024-04-11T15:20:25.107865+02:00 Panoramix kernel: [ 5748.234399]  
do_vfs_ioctl+0x68f/0x910
2024-04-11T15:20:25.107867+02:00 Panoramix kernel: [ 5748.234404]  ? 
srso_alias_return_thunk+0x5/0x7f
2024-04-11T15:20:25.107869+02:00 Panoramix kernel: [ 5748.234409]  ? 
__fget_light+0xa5/0x120
2024-04-11T15:20:25.107870+02:00 Panoramix kernel: [ 5748.234415]  
__x64_sys_ioctl+0x7d/0xf0
2024-04-11T15:20:25.107872+02:00 Panoramix

[Kernel-packages] [Bug 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).

2024-04-11 Thread fprietog

> Same issue on kernel 6.5.0-27-generic #28~22.04.1-Ubuntu

That kernel is from the "linux-hwe-6.5" package. I'll try to link this
bug to that package to avoid duplication.

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

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

Title:
  Remote filesystems mounted as CIFS not working after update to Kernel
  "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi
  #17-Ubuntu" (aarch64).

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in linux-raspi package in Ubuntu:
  Confirmed

Bug description:
  Remote filesystems mounted as CIFS are not working after update to
  Kernel "6.5.0-27-generic #28-Ubuntu" for x86_64 (and also after
  updating to Kernel "6.5.0-1014-raspi #17-Ubuntu" in aarch64).

  The remote filesystem is correctly mounted and seems to work but
  trying to write data to the filesystem ends in a kernel error
  exception. After that error the CIFS filesystem just became unusable.

  Previous Kernel version works correctly.

  =
  Example for Kernel "6.5.0-27-generic #28-Ubuntu" (x86_64)
  =
  # lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10

  # uname -a
  Linux fpgmsi 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar  7 
18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  # cat /proc/version_signature
  Ubuntu 6.5.0-27.28-generic 6.5.13

  
  How to reproduce the problem
  
  For instance, I'm using KeePassXC 
(https://launchpad.net/ubuntu/+source/keepassxc) to update a database located 
at CIFS filesystem. Any change done to that database causes this Kernel error 
exception:

  abr 11 09:34:59 fpgmsi kernel: BUG: unable to handle page fault for address: 
fffe
  abr 11 09:34:59 fpgmsi kernel: #PF: supervisor read access in kernel mode
  abr 11 09:34:59 fpgmsi kernel: #PF: error_code(0x) - not-present page
  abr 11 09:34:59 fpgmsi kernel: PGD f45a3f067 P4D f45a3f067 PUD f45a41067 PMD 
0 
  abr 11 09:34:59 fpgmsi kernel: Oops:  [#1] PREEMPT SMP NOPTI
  abr 11 09:34:59 fpgmsi kernel: CPU: 0 PID: 28103 Comm: Thread (pooled) 
Tainted: P   OE  6.5.0-27-generic #28-Ubuntu
  abr 11 09:34:59 fpgmsi kernel: Hardware name: Micro-Star International Co., 
Ltd. MAG Z690 Codex X5 (MS-B930)/PRO Z690-A WIFI (MS-7D25), BIOS D.50 04/26/2022
  abr 11 09:34:59 fpgmsi kernel: RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs]
  abr 11 09:34:59 fpgmsi kernel: Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 
0c 53 48 83 ec 08 48 8b 7f 30 44 89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 
db 74 77 <48> 8b 13 b8 00 10 00 00 f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3
  abr 11 09:34:59 fpgmsi kernel: RSP: 0018:aab6865ffbf8 EFLAGS: 00010282
  abr 11 09:34:59 fpgmsi kernel: RAX:  RBX: fffe 
RCX: 
  abr 11 09:34:59 fpgmsi kernel: RDX:  RSI:  
RDI: 
  abr 11 09:34:59 fpgmsi kernel: RBP: aab6865ffc28 R08: 0001 
R09: 
  abr 11 09:34:59 fpgmsi kernel: R10: 00023854 R11:  
R12: 
  abr 11 09:34:59 fpgmsi kernel: R13: aab6865ffc78 R14: 906675d8aed0 
R15: aab6865ffc70
  abr 11 09:34:59 fpgmsi kernel: FS:  7bd4d594b6c0() 
GS:90753f80() knlGS:
  abr 11 09:34:59 fpgmsi kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  abr 11 09:34:59 fpgmsi kernel: CR2: fffe CR3: 00017022a000 
CR4: 00750ef0
  abr 11 09:34:59 fpgmsi kernel: PKRU: 5554
  abr 11 09:34:59 fpgmsi kernel: Call Trace:
  abr 11 09:34:59 fpgmsi kernel:  
  abr 11 09:34:59 fpgmsi kernel:  ? show_regs+0x6d/0x80
  abr 11 09:34:59 fpgmsi kernel:  ? __die+0x24/0x80
  abr 11 09:34:59 fpgmsi kernel:  ? page_fault_oops+0x99/0x1b0
  abr 11 09:34:59 fpgmsi kernel:  ? kernelmode_fixup_or_oops+0xb2/0x140
  abr 11 09:34:59 fpgmsi kernel:  ? __bad_area_nosemaphore+0x1a5/0x2c0
  abr 11 09:34:59 fpgmsi kernel:  ? bad_area_nosemaphore+0x16/0x30
  abr 11 09:34:59 fpgmsi kernel:  ? do_kern_addr_fault+0x7b/0xa0
  abr 11 09:34:59 fpgmsi kernel:  ? exc_page_fault+0x1a4/0x1b0
  abr 11 09:34:59 fpgmsi kernel:  ? asm_exc_page_fault+0x27/0x30
  abr 11 09:34:59 fpgmsi kernel:  ? cifs_flush_folio+0x41/0xf0 [cifs]
  abr 11 09:34:59 fpgmsi kernel:  ? cifs_flush_folio+0x37/0xf0 [cifs]
  abr 11 09:34:59 fpgmsi kernel:  cifs_remap_file_range+0x172/0x660 [cifs]
  abr 11 09:34:59 fpgmsi kernel:  do_clone_file_range+0x101/0x2d0
  abr 11 09:34:59 fpgmsi kernel:  vfs_clone_file_range+0x3f/0x150
  abr 11 09:34:59 fpgmsi kernel:  ioctl_file_clone+0x52/0xc0

[Kernel-packages] [Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)

** Summary changed:

- Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable 
(main)
+ [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from 
testing/unstable (main)

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

Title:
  [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from
  testing/unstable (main)

Status in iproute2 package in Ubuntu:
  Confirmed

Bug description:
  A few versions have been released and Ubuntu Noble still has the 6.1
  version (6.1.0-1ubuntu2) from one year ago. Could it be possible to
  import the latest version from Debian unstable fixing a bunch of
  issues and supporting features from more recent kernels?

  Please note that Ubuntu Noble 24.04 will probably be shipped with the
  v6.8 kernel [1]. IPRoute v6.1 supports features added up to the v6.1
  kernel, so missing the ones added to earlier versions. Switching to
  the v6.7 now should ease the upgrade to the v6.8 later.

  [1] https://discourse.ubuntu.com/t/introducing-kernel-6-8-for-
  the-24-04-noble-numbat-release/41958

  Upstream ChangeLog:

  - 6.2: https://lore.kernel.org/netdev/20230220105811.674bd304@hermes.local/
  - 6.3: https://lore.kernel.org/netdev/20230427090253.7a92616b@hermes.local/
  - 6.4: https://lore.kernel.org/netdev/20230626093137.2f302acc@hermes.local/
  - 6.5: https://lore.kernel.org/netdev/20230906093918.394a1b1d@hermes.local/
  - 6.6: https://lore.kernel.org/netdev/20231106090325.07092c87@hermes.local/
  - 6.7: https://lore.kernel.org/netdev/20240108094709.050e22bc@hermes.local/
  - 6.8: https://lore.kernel.org/netdev/20240311094432.16bf9516@hermes.local/

  (Previous changelog:
  
https://lore.kernel.org/netdev/?q=s%3A%22%5BANNOUNCE%5D+iproute2%22+AND+NOT+s%3A%22Re%3A%22
  )

  ChangeLog from Debian:

  iproute2 (6.8.0-1) unstable; urgency=medium

[ Ceppo ]
* Update Italian po-debconf translation (Closes: #1063002)

[ Luca Boccassi ]
* Add build dependency on libnsl-dev (Closes: #1065214)
* Switch to pkgconf
* Update upstream source from tag 'upstream/6.8.0'
* Drop 0002-ss-show-extra-info-when-processes-is-not-used.patch, merged
  upstream
* Drop iproute2-doc package
* Drop tc/m_xt.so and tc/m_ipt.so, removed upstream

   -- Luca Boccassi <>  Tue, 12 Mar 2024 14:02:38 +

  iproute2 (6.7.0-2) unstable; urgency=medium

    * Backport fix for 'ss' output

   -- Luca Boccassi <>  Mon, 22 Jan 2024 12:24:29 +

  iproute2 (6.7.0-1) unstable; urgency=medium

    * Add Italian debconf translation (Closes: #1056582)
    * Update upstream source from tag 'upstream/6.7.0'
    * Bump copyright year ranges in d/copyright
    * Drop 0002-Revert-Makefile-ensure-CONF_USR_DIR-honours-the-libd.patch,
  merged upstream
    * Default config files moved from /usr/lib to /usr/share

   -- Luca Boccassi <>  Fri, 12 Jan 2024 21:47:59 +

  iproute2 (6.6.0-1) unstable; urgency=medium

    * Update upstream source from tag 'upstream/6.6.0'
    * Backport patch to fix configuration installation
    * Remove handling of qt_atm.so, dropped upstream

   -- Luca Boccassi <>  Sun, 05 Nov 2023 22:46:20 +

  iproute2 (6.5.0-5) unstable; urgency=medium

    * Use dh-sequence-movetousr

   -- Luca Boccassi <>  Tue, 24 Oct 2023 15:24:01 +0100

  iproute2 (6.5.0-4) unstable; urgency=medium

    * postinst: handle legacy config files only when upgrading from previous
  versions that shipped them
    * postinst: ensure that locally modified legacy config files are
  preserved as overrides on upgrade (Closes: #1051577)
    * Note configuration files location changes in NEWS

   -- Luca Boccassi <>  Sat, 16 Sep 2023 18:58:51 +0100

  iproute2 (6.5.0-3) unstable; urgency=medium

    * Remove further leftovers as part of upstream's move of config to /usr
  (Closes: #1051577)

   -- Luca Boccassi <>  Mon, 11 Sep 2023 09:42:12 +0100

  iproute2 (6.5.0-2) unstable; urgency=medium

    * Add maintscript to remove conffiles that upstream has moved to /usr
  (Closes: #1051577)

   -- Luca Boccassi <>  Sun, 10 Sep 2023 21:28:28 +0100

  iproute2 (6.5.0-1) unstable; urgency=medium

    [ Luca Boccassi ]
    * Use wildcard for Lintian overrides

    [ Peter Kvillegård ]
    * Add Swedish translation of debconf messages (Closes: #1050442)

    [ Luca Boccassi ]
    * Update upstream source from tag 'upstream/6.5.0'
    * Use cap_bpf instead of cap_sys_admin for ip vrf-exec
    * Package-provided config files are now shipped in /usr/iproute2 instead
  of /etc/iproute2

   -- Luca Boccassi <>  Sat, 09 Sep 2023 16:32:54 +0100

  iproute2 (6.4.0-1) unstable; urgency=medium

    * Fix patch header Forwarded field
    * Enable ELF metadata stamping
    * Update upstream source from tag 'upstream/6.4.0'
    * Update Lintian overrides

   -- Luca Boccassi <>  Fri, 30 Jun 2023 12:16:40

[Kernel-packages] [Bug 2060969] Re: UB 24.04: update uproute2 package

*** This bug is a duplicate of bug 2051672 ***
https://bugs.launchpad.net/bugs/2051672

** This bug has been marked a duplicate of bug 2051672
   Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable 
(main)

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

Title:
  UB 24.04: update uproute2 package

Status in linux package in Ubuntu:
  New

Bug description:
  This ticket is an FR to update iproute2 package from 6.1.0 to latest
  upstream version.

  This updated is needed to support latest mlx5 driver features.

  Missing support examples
  1) related feature: ipsec packet offload (iproute v6.7):
  https://lore.kernel.org/netdev/20231003180557.GC51282@unreal/T/
  994e80e9 devlink: Support setting port function ipsec_packet cap
  27fd1bfa devlink: Support setting port function ipsec_crypto cap
  kernel
  https://www.spinics.net/lists/netdev/msg932050.html

  2) related feature: live migration (iproute2 v6.2.0)
  https://lore.kernel.org/netdev/2022125849.510284-5-sh...@nvidia.com/T/
  e036c36 devlink: Add documentation for roce and migratable port function 
attributes
  32168d8a devlink: Support setting port function migratable cap
  bb2eea91 devlink: Support setting port function roce cap

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060969/+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 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).

2024-04-11 Thread Chrescht

Same issue on kernel  6.5.0-27-generic #28~22.04.1-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/2060919

Title:
  Remote filesystems mounted as CIFS not working after update to Kernel
  "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi
  #17-Ubuntu" (aarch64).

Status in linux package in Ubuntu:
  Confirmed
Status in linux-raspi package in Ubuntu:
  Confirmed

Bug description:
  Remote filesystems mounted as CIFS are not working after update to
  Kernel "6.5.0-27-generic #28-Ubuntu" for x86_64 (and also after
  updating to Kernel "6.5.0-1014-raspi #17-Ubuntu" in aarch64).

  The remote filesystem is correctly mounted and seems to work but
  trying to write data to the filesystem ends in a kernel error
  exception. After that error the CIFS filesystem just became unusable.

  Previous Kernel version works correctly.

  =
  Example for Kernel "6.5.0-27-generic #28-Ubuntu" (x86_64)
  =
  # lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10

  # uname -a
  Linux fpgmsi 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar  7 
18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  # cat /proc/version_signature
  Ubuntu 6.5.0-27.28-generic 6.5.13

  
  How to reproduce the problem
  
  For instance, I'm using KeePassXC 
(https://launchpad.net/ubuntu/+source/keepassxc) to update a database located 
at CIFS filesystem. Any change done to that database causes this Kernel error 
exception:

  abr 11 09:34:59 fpgmsi kernel: BUG: unable to handle page fault for address: 
fffe
  abr 11 09:34:59 fpgmsi kernel: #PF: supervisor read access in kernel mode
  abr 11 09:34:59 fpgmsi kernel: #PF: error_code(0x) - not-present page
  abr 11 09:34:59 fpgmsi kernel: PGD f45a3f067 P4D f45a3f067 PUD f45a41067 PMD 
0 
  abr 11 09:34:59 fpgmsi kernel: Oops:  [#1] PREEMPT SMP NOPTI
  abr 11 09:34:59 fpgmsi kernel: CPU: 0 PID: 28103 Comm: Thread (pooled) 
Tainted: P   OE  6.5.0-27-generic #28-Ubuntu
  abr 11 09:34:59 fpgmsi kernel: Hardware name: Micro-Star International Co., 
Ltd. MAG Z690 Codex X5 (MS-B930)/PRO Z690-A WIFI (MS-7D25), BIOS D.50 04/26/2022
  abr 11 09:34:59 fpgmsi kernel: RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs]
  abr 11 09:34:59 fpgmsi kernel: Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 
0c 53 48 83 ec 08 48 8b 7f 30 44 89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 
db 74 77 <48> 8b 13 b8 00 10 00 00 f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3
  abr 11 09:34:59 fpgmsi kernel: RSP: 0018:aab6865ffbf8 EFLAGS: 00010282
  abr 11 09:34:59 fpgmsi kernel: RAX:  RBX: fffe 
RCX: 
  abr 11 09:34:59 fpgmsi kernel: RDX:  RSI:  
RDI: 
  abr 11 09:34:59 fpgmsi kernel: RBP: aab6865ffc28 R08: 0001 
R09: 
  abr 11 09:34:59 fpgmsi kernel: R10: 00023854 R11:  
R12: 
  abr 11 09:34:59 fpgmsi kernel: R13: aab6865ffc78 R14: 906675d8aed0 
R15: aab6865ffc70
  abr 11 09:34:59 fpgmsi kernel: FS:  7bd4d594b6c0() 
GS:90753f80() knlGS:
  abr 11 09:34:59 fpgmsi kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  abr 11 09:34:59 fpgmsi kernel: CR2: fffe CR3: 00017022a000 
CR4: 00750ef0
  abr 11 09:34:59 fpgmsi kernel: PKRU: 5554
  abr 11 09:34:59 fpgmsi kernel: Call Trace:
  abr 11 09:34:59 fpgmsi kernel:  
  abr 11 09:34:59 fpgmsi kernel:  ? show_regs+0x6d/0x80
  abr 11 09:34:59 fpgmsi kernel:  ? __die+0x24/0x80
  abr 11 09:34:59 fpgmsi kernel:  ? page_fault_oops+0x99/0x1b0
  abr 11 09:34:59 fpgmsi kernel:  ? kernelmode_fixup_or_oops+0xb2/0x140
  abr 11 09:34:59 fpgmsi kernel:  ? __bad_area_nosemaphore+0x1a5/0x2c0
  abr 11 09:34:59 fpgmsi kernel:  ? bad_area_nosemaphore+0x16/0x30
  abr 11 09:34:59 fpgmsi kernel:  ? do_kern_addr_fault+0x7b/0xa0
  abr 11 09:34:59 fpgmsi kernel:  ? exc_page_fault+0x1a4/0x1b0
  abr 11 09:34:59 fpgmsi kernel:  ? asm_exc_page_fault+0x27/0x30
  abr 11 09:34:59 fpgmsi kernel:  ? cifs_flush_folio+0x41/0xf0 [cifs]
  abr 11 09:34:59 fpgmsi kernel:  ? cifs_flush_folio+0x37/0xf0 [cifs]
  abr 11 09:34:59 fpgmsi kernel:  cifs_remap_file_range+0x172/0x660 [cifs]
  abr 11 09:34:59 fpgmsi kernel:  do_clone_file_range+0x101/0x2d0
  abr 11 09:34:59 fpgmsi kernel:  vfs_clone_file_range+0x3f/0x150
  abr 11 09:34:59 fpgmsi kernel:  ioctl_file_clone+0x52/0xc0
  abr 11 09:34:59 fpgmsi kernel:  do_vfs_ioctl+0x68f/0x910
  abr 11 09:34:59 fpgmsi kernel:  ? __fget_light+0xa5/0x120
  abr 11 09:34:59 fpgmsi kernel:  __x64_sys_ioctl+0x7d/0xf0
  abr 11 09:34:59 fpgmsi kernel:  do_syscall_64+0x59/0x90
  abr 11 09:34:59

[Kernel-packages] [Bug 2060969] Re: UB 24.04: update uproute2 package

2024-04-11 Thread Amir Tzin

** Description changed:

  This ticket is an FR to update iproute2 package from 6.1.0 to latest
  upstream version.
  
  This updated is needed to support latest mlx5 driver features.
  
- Missing support examples (iproute v6.7):
- 1)
- ipsec
+ Missing support examples
+ 1) related feature: ipsec packet offload (iproute v6.7):
  https://lore.kernel.org/netdev/20231003180557.GC51282@unreal/T/
  994e80e9 devlink: Support setting port function ipsec_packet cap
  27fd1bfa devlink: Support setting port function ipsec_crypto cap
  kernel
  https://www.spinics.net/lists/netdev/msg932050.html
  
- 2)
+ 2) related feature: live migration (iproute2 v6.2.0)
+ https://lore.kernel.org/netdev/2022125849.510284-5-sh...@nvidia.com/T/
+ e036c36 devlink: Add documentation for roce and migratable port function 
attributes
+ 32168d8a devlink: Support setting port function migratable cap
+ bb2eea91 devlink: Support setting port function roce cap

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

Title:
  UB 24.04: update uproute2 package

Status in linux package in Ubuntu:
  New

Bug description:
  This ticket is an FR to update iproute2 package from 6.1.0 to latest
  upstream version.

  This updated is needed to support latest mlx5 driver features.

  Missing support examples
  1) related feature: ipsec packet offload (iproute v6.7):
  https://lore.kernel.org/netdev/20231003180557.GC51282@unreal/T/
  994e80e9 devlink: Support setting port function ipsec_packet cap
  27fd1bfa devlink: Support setting port function ipsec_crypto cap
  kernel
  https://www.spinics.net/lists/netdev/msg932050.html

  2) related feature: live migration (iproute2 v6.2.0)
  https://lore.kernel.org/netdev/2022125849.510284-5-sh...@nvidia.com/T/
  e036c36 devlink: Add documentation for roce and migratable port function 
attributes
  32168d8a devlink: Support setting port function migratable cap
  bb2eea91 devlink: Support setting port function roce cap

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060969/+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 2057424] Re: No variable refresh rate (VRR) on the Framework 16

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

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

Title:
  No variable refresh rate (VRR) on the Framework 16

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.8 package in Ubuntu:
  New
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.8 source package in Noble:
  New

Bug description:
  Quoted from AMD proposed fix in https://lore.kernel.org/amd-
  
gfx/46657fa4-630e-47a5-a339-242ecd5ba...@amd.com/T/#m94e3b7d292e359f3d656babe3ccdbf7fc6daab6f

  > The monitor shipped with the Framework 16 supports VRR [1], but it's not
  > being advertised.
  >
  > This is because the detailed timing block doesn't contain
  > `EDID_DETAIL_MONITOR_RANGE` which amdgpu looks for to find min and max
  > frequencies.  This check however is superfluous for this case because
  > update_display_info() calls drm_get_monitor_range() to get these ranges
  > already.
  >
  > So if the `DRM_EDID_FEATURE_CONTINUOUS_FREQ` EDID feature is found then
  > turn on freesync without extra checks.

  See: 
https://www.reddit.com/r/framework/comments/1b4y2i5/no_variable_refresh_rate_on_the_framework_16_on/
  See: 
https://www.reddit.com/r/framework/comments/1b6vzcy/framework_16_variable_refresh_rate/
  See: 
https://community.frame.work/t/resolved-no-vrr-freesync-with-amd-version/42338
  Link: https://gist.github.com/superm1/e8fbacfa4d0f53150231d3a3e0a13faf

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2057424/+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 2060969] [NEW] UB 24.04: update uproute2 package

2024-04-11 Thread Amir Tzin

Public bug reported:

This ticket is an FR to update iproute2 package from 6.1.0 to latest
upstream version.

This updated is needed to support latest mlx5 driver features.

Missing support examples (iproute v6.7):
1)
ipsec
https://lore.kernel.org/netdev/20231003180557.GC51282@unreal/T/
994e80e9 devlink: Support setting port function ipsec_packet cap
27fd1bfa devlink: Support setting port function ipsec_crypto cap
kernel
https://www.spinics.net/lists/netdev/msg932050.html

2)

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

** Description changed:

  This ticket is an FR to update iproute2 package from 6.1.0 to latest
  upstream version.
  
  This updated is needed to support latest mlx5 driver features.
  
- Missing support examples:
- 1) 
- ipsec 
+ Missing support examples (iproute v6.7):
+ 1)
+ ipsec
  https://lore.kernel.org/netdev/20231003180557.GC51282@unreal/T/
  994e80e9 devlink: Support setting port function ipsec_packet cap
  27fd1bfa devlink: Support setting port function ipsec_crypto cap
  kernel
  https://www.spinics.net/lists/netdev/msg932050.html
  
  2)

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

Title:
  UB 24.04: update uproute2 package

Status in linux package in Ubuntu:
  New

Bug description:
  This ticket is an FR to update iproute2 package from 6.1.0 to latest
  upstream version.

  This updated is needed to support latest mlx5 driver features.

  Missing support examples (iproute v6.7):
  1)
  ipsec
  https://lore.kernel.org/netdev/20231003180557.GC51282@unreal/T/
  994e80e9 devlink: Support setting port function ipsec_packet cap
  27fd1bfa devlink: Support setting port function ipsec_crypto cap
  kernel
  https://www.spinics.net/lists/netdev/msg932050.html

  2)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060969/+subscriptions


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

[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)

2024-04-11 Thread Terin Stock

Adding the kernel parameters to the grub configuration greatly reduces
the flicker on my Dell Precision 5480 running Ubuntu 22.04. However, it
returns every few seconds after the external display has gone to
standby, despite /sys/module/i915/parameters/enable_dc and
/sys/module/intel_idle/parameters/max_cstate still reporting their
updated values.

:00:02.0 VGA compatible controller: Intel Corporation Device a7a0 (rev 04) 
(prog-if 00 [VGA controller])
Subsystem: Dell Device 0c40
Flags: bus master, fast devsel, latency 0, IRQ 213, IOMMU group 1
Memory at 607f00 (64-bit, non-prefetchable) [size=16M]
Memory at 40 (64-bit, prefetchable) [size=256M]
I/O ports at 3000 [size=64]
Expansion ROM at 000c [virtual] [disabled] [size=128K]
Capabilities: [40] Vendor Specific Information: Len=0c 
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable+ 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [100] Process Address Space ID (PASID)
Capabilities: [200] Address Translation Service (ATS)
Capabilities: [300] Page Request Interface (PRI)
Capabilities: [320] Single Root I/O Virtualization (SR-IOV)
Kernel driver in use: i915
Kernel modules: i915

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

Title:
  [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0
  intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)

Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.19 package in Ubuntu:
  Fix Released
Status in linux-hwe-6.2 package in Ubuntu:
  Confirmed
Status in linux source package in Lunar:
  Won't Fix
Status in linux-hwe-5.19 source package in Lunar:
  Invalid
Status in linux-hwe-6.2 source package in Lunar:
  Invalid

Bug description:
  Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @
  18/1/2022

  Booting into desktop gets heavy screen flickering and disforming (unusable)
  both booting on xorg and wayland

  on kernel 5.13 it did not occur so heavy (only little glitches once in
  a while see bug 1948778)

  adding the kernel parameter i915.enable_dc=0 intel_idle.max_cstate=2
  fixed this

  i had these same bugs on this machine before:

  https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644

  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lotuspsychje   1201 F pipewire-media-
    lotuspsychje   1207 F pulseaudio
   /dev/snd/seq:lotuspsychje   1193 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 04:22:00 2022
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth 
Adapter
   Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 
Camera
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook N7x0WU
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic 
root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash 
intel_idle.max_cstate=4 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-17-generic N/A
   linux-backports-modules-5.15.0-17-generic  N/A
   linux-firmware 1.204
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2019
  dmi.bios.release: 7.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 7.13
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N7x0WU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.14
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: N7x0WU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+subscriptions


-- 
Mailing list:

[Kernel-packages] [Bug 2060217] Re: NFSv4 fails to mount in noble/s390x

2024-04-11 Thread GuoqingJiang

Thanks Vasily. After it is merged by upstream maintainer, maybe you can
send it to ubuntu kernel list as well, or wait until noble update to
future upstream stable release since the patch has been cced to
sta...@vger.kernel.org and also has fixes tag.

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

Title:
  NFSv4 fails to mount in noble/s390x

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New
Status in nfs-utils package in Ubuntu:
  Triaged

Bug description:
  https://autopkgtest.ubuntu.com/packages/n/nfs-utils/noble/s390x

  Looks like it has been failing for a long time already.

  Log: https://autopkgtest.ubuntu.com/results/autopkgtest-
  noble/noble/s390x/n/nfs-utils/20240404_145924_ef255@/log.gz

  339s autopkgtest [14:41:04]: test local-server-client: 
[---
  340s Killed
  340s autopkgtest [14:41:05]: test process requested reboot with marker boot1
  364s autopkgtest-virt-ssh: WARNING: ssh connection failed. Retrying in 3 
seconds...
  372s FAIL: nfs_home not mounted
  373s autopkgtest [14:41:38]: test local-server-client: 
---]
  373s local-server-client  FAIL non-zero exit status 1

  and

  934s autopkgtest [14:50:59]: test kerberos-mount: [---
  935s Initializing database '/var/lib/krb5kdc/principal' for realm 'DEP8',
  935s master key name 'K/M@DEP8'
  935s Authenticating as principal root/admin@DEP8 with password.
  935s Principal "nfs/nfs-server.dep8@DEP8" created.
  935s Authenticating as principal root/admin@DEP8 with password.
  935s Entry for principal nfs/nfs-server.dep8 with kvno 2, encryption type 
aes256-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab.
  935s Entry for principal nfs/nfs-server.dep8 with kvno 2, encryption type 
aes128-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab.
  935s Authenticating as principal root/admin@DEP8 with password.
  935s Principal "host/nfs-server.dep8@DEP8" created.
  935s Authenticating as principal root/admin@DEP8 with password.
  935s Entry for principal host/nfs-server.dep8 with kvno 2, encryption type 
aes256-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab.
  935s Entry for principal host/nfs-server.dep8 with kvno 2, encryption type 
aes128-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab.
  936s exporting *:/storage
  938s mount.nfs: mount system call failed for /mnt
  938s umount: /mnt: not mounted.
  938s autopkgtest [14:51:02]: test kerberos-mount: ---]
  939s kerberos-mount   FAIL non-zero exit status 32

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2060217/+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 2060866] Re: No keybord after kernel upgrade

2024-04-11 Thread Aussems J.a.c.

*** This bug is a duplicate of bug 2060727 ***
https://bugs.launchpad.net/bugs/2060727

-
I changed in file '/etc/default/grub' the lines:

GRUB_TIMEOUT_STYLE=menu
GRUB_TIMEOUT=-1

I used the command 'sudo update-grub' and Reboot the computer.
The grub menu is now shown and I can still use the internal keyboard.

I can choose between kernel version:

- Linux 6.5.0.-1019-oem
- Linux 6.5.0.-1018-oem

When I choose the kernel, 1019, the keyboard does not functions after booting
When I choose the kernel, 1018, the keyboard workes after booting.

So this shows that the problem is caused by the 1019 kernel.

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

Title:
  No keybord after kernel upgrade

Status in linux package in Ubuntu:
  New

Bug description:
  Hi, I am using a Lenovo Thinkpas L15 laptop, X86 X64, with Xubuntu 22.04.04 
LTS installed.
  The version I am using is:

  Linux t-l15 6.5.0-1019-oem #20-Ubuntu SMP PREEMPT_DYNAMIC Mon Mar 18
  17:38:55 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  Yesterday, 2024-04-08, the system had a kernel upgrade and sind than I can't 
use the buildin keyboard of the laptop.
  The mouse pad is still working and when I goto the BIOS the keyboard is also 
working.
  At the moment I use a USB keyboard.

  When I give the command, cat /sys/class/dmi/id/chassis_type, the
  system replys with '10'

  Who can/will help to solve the problem?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pi 1884 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2024-01-24 (77 days ago)
  InstallationMedia: Xubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
  MachineType: LENOVO 21H3002SMH
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1019-oem 
root=UUID=55d807e5-860a-4445-bf3d-3f39e30424f2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1019.20-oem 6.5.13
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1019-oem N/A
   linux-backports-modules-6.5.0-1019-oem  N/A
   linux-firmware  20220329.git681281e4-0ubuntu3.29
  Tags:  jammy
  Uname: Linux 6.5.0-1019-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2024
  dmi.bios.release: 1.21
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R24ET38W (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21H3002SMH
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.13
  dmi.modalias: 
dmi:bvnLENOVO:bvrR24ET38W(1.21):bd03/01/2024:br1.21:efr1.13:svnLENOVO:pn21H3002SMH:pvrThinkPadL15Gen4:rvnLENOVO:rn21H3002SMH:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21H3_BU_Think_FM_ThinkPadL15Gen4:
  dmi.product.family: ThinkPad L15 Gen 4
  dmi.product.name: 21H3002SMH
  dmi.product.sku: LENOVO_MT_21H3_BU_Think_FM_ThinkPad L15 Gen 4
  dmi.product.version: ThinkPad L15 Gen 4
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060866/+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 2056373] Re: Problems with HVCS and hotplugging

2024-04-11 Thread Ubuntu Kernel Bot

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


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

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

Title:
  Problems with HVCS and hotplugging

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Invalid
Status in linux source package in Noble:
  Invalid

Bug description:
  SRU Justification:
  ==

  [Impact]

   * HVCS (Hypervisor Virtual Console Server) is broken because the
 virtual terminal mkvterm fails, caused by pvmutil failing.

   * When mkvterm is ran, it ultimately fails because it calls pvmutil
 which fails.
 pvmutil calls drmgr, and drmgr is adding a slot correctly.
 However, when drmgr writes the slot information to ?/add_slot,
 the return is -ENODEV.

   * This leads to HVCS never having probe() called.

   * In addition, HVCS is missing patches/fixes, and is broken without
  them.

  [Fix]

   * Fix one and two is required for focal only, all other for focal and
  jammy:

   * 57409d4fb12c 57409d4fb12c185b2c0689e0496878c8f6bb5b58
 "powerpc/pseries: Fix bad drc_index_start value parsing of drc-info entry"

   * c5e76fa05b2d c5e76fa05b2df519b9f08571cc57e623c1569faa
 "powerpc/pseries: Fix of_read_drc_info_cell() to point at next record"

   * 6a9a733edd46 6a9a733edd46732e906d976dc21a42dd361e53cc
 "hvcs: Fix hvcs port reference counting"

   * 760aa5e81f33 760aa5e81f33e0da82512c4288489739a6d1c556
 "hvcs: Use dev_groups to manage hvcs device attributes"

   * 503a90dd619d 503a90dd619d52dcac2cc68bd742aa914c7cd47a
 "hvcs: Use driver groups to manage driver attributes"

   * 3a8d3b366ce4 3a8d3b366ce47024bf274eac783f8af5df2780f5
 "hvcs: Get reference to tty in remove"

   * d432228bc7b1 d432228bc7b1b3f0ed06510278ff5a77b3749fe6
 "hvcs: Use vhangup in hotplug remove"

   * 28d49f8cbe9c 28d49f8cbe9c7966f91ee1b5ec2f997f6e55bf9f
 "hvcs: Synchronize hotplug remove with port free"

  [Test Plan]

   * The high level test plan is to run mkvterm with an id.
   
   * mkvterm will fail because /dev/hvcs* device nodes are missing.

   * Details see https://bugs.launchpad.net/bugs/2023243 for more information.
 Especially the script provided by IBM
 (see original bug description: `---Steps to Reproduce---`).

   * IBM will (stress) test the updated kernel(s) provided in -proposed.

  [Where problems could occur]

   * The first two commits affect arch/powerpc/platforms/pseries/of_helpers.c
 and are needed to fix the hotplugging issue seen when drmgr goes to write
 the slot information to /sys/bus/pci/slots/control/add_slot.
 In case of issues here hotplugging with drmgr might break.

   * The issue lies in rpadlpar_io and rpaphp calling an of helper function
 of_read_drc_info_cell(). Without these commits, the value stored
 drc_index_start is incorrect.
 This ultimately results in the entire SLOT string being incorrect,
 and rpaphp never finding the newly added slot by drmgr.
 rpadlpar then returns -ENODEV.
 Therefore, HVCS is never probed, and the device nodes are never created.

   * HVCS, rpadlpar_io, and rpaphp should ideally not even need to be loaded
 prior to drmgr adding a vio slot.
 If rpadlpar_io and rpaphp are not loaded, drmgr will load them.
 In addition, if rpadlpar_io and rpaphp register the new slot correctly,
 rpadlpar_io will call dlpar_add_vio_slot(),
 which calls vio_register_device_node() with the device node.
 This is what tells the driver core to init and probe HVCS
 (which is needed to create the device nodes).

   * The remaning 6 commits are needed for HVCS, that is essentially
 broken without them.
 Overall, issues they fix are race conditions, hotplug remove issues,
 as well as memory leaks.

   * Please notice that this is entirely ppc64el architecture-specifc.

  [Other Info]

   * All the commits listed above are included in mantic and noble.
 Hence these are set to Invalid.

[Kernel-packages] [Bug 2045560] Re: TCP memory leak, slow network (arm64)

2024-04-11 Thread Jonathan Heathcote

As another "me too" situation, I'm seeing the same phenomenon, though on
Rocky 9 rather than Ubuntu and on older kernels (5.14). Reporting
details here on the off chance this provides some insight.

Hardware: Ampere Altra Max 128 cores (aarch64), ConnectX6-DX NICs (2 x dual 
100G port)
Kernel versions tested: 5.15 (Rocky 9 native kernel) and 6.8 (elrepo kernel), 
both configured with 64 KB pages
OS: Rocky Linux 9
Software: nginx serving ~90k HTTPS clients at ~350 GBit/s (a synthetic load 
test)
Bare-metal (no virtualisation).

In my test environment, ~90k HTTPS connections are opened (and reused
via keepalive) and used to stream ~350 GBit/s of traffic to a cluster of
load generators. In this scenario, TCP memory gradually creeps up until
reaching the memory pressure threshold in /proc/sys/net/ipv4/tcp_mem
(243890 pages, or 15.6 GB in this system). At this point memory usage
growth actually increases slightly (and increased CPU load and response
times are also observed). The system eventually reaches the ultimate
limit (365832 pages, or 23.4 GB) at which point most connections fail
and all requests receive very slow responses.

Closing all connections or restarting nginx does not free up the memory,
only a reboot resolves the situation -- as reported above already.

Leaked memory appears to persist even if all connections are closed
prior to hitting any of the above limits.

Unfortunately I don't yet have any ideas on how to fix this but would be
glad to hear (and will share) any insights about what might be going on
here!

** Attachment added: "TCP memory consumption"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-aws-6.2/+bug/2045560/+attachment/5763728/+files/boom.png

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

Title:
  TCP memory  leak, slow network (arm64)

Status in linux-signed-aws-6.2 package in Ubuntu:
  Confirmed

Bug description:
  Hello! 

  We have Ubuntu OS-based servers running in both AWS and Azure clouds.
  These servers are handling thousands of connections, and we've been
  experiencing issues with TCP memory usage since upgrading to Ubuntu
  22.04.3 from 22.04.2.

  $ cat /proc/net/sockstat
  sockets: used 6642
  TCP: inuse 5962 orphan 0 tw 292 alloc 6008 mem 128989
  UDP: inuse 5 mem 0
  UDPLITE: inuse 0
  RAW: inuse 0
  FRAG: inuse 0 memory 0

  As shown in the output below, even after stopping all possible
  services and closing all open connections, the TCP memory usage
  remains high and only decreases very slowly.

  $ cat /proc/net/sockstat
  sockets: used 138
  TCP: inuse 2 orphan 0 tw 0 alloc 3 mem 128320
  UDP: inuse 3 mem 0
  UDPLITE: inuse 0
  RAW: inuse 0
  FRAG: inuse 0 memory 0

  I have attached a screenshot of linear TCP memory usage growth, which
  we believe may indicate a TCP memory leak

  When net.ipv4.tcp_mem limit is reached, it causes network slowdown

  We've never had these issues before, and the only solution we've found
  so far is to reboot the node. Do you have any suggestions on how to
  troubleshoot further?

  Thank you for any help or guidance you can provide!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-1015-aws 6.2.0-1015.15~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-1015.15~22.04.1-aws 6.2.16
  Uname: Linux 6.2.0-1015-aws aarch64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CloudArchitecture: aarch64
  CloudID: aws
  CloudName: aws
  CloudPlatform: ec2
  CloudRegion: us-west-2
  CloudSubPlatform: metadata (http://169.254.169.254)
  Date: Mon Dec  4 13:13:08 2023
  Ec2AMI: ami-095a68e28e781dfe1
  Ec2AMIManifest: (unknown)
  Ec2Architecture: arm64
  Ec2AvailabilityZone: us-west-2b
  Ec2Imageid: ami-095a68e28e781dfe1
  Ec2InstanceType: m7g.large
  Ec2Instancetype: m7g.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Ec2Region: us-west-2
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: linux-signed-aws-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-aws-6.2/+bug/2045560/+subscriptions


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-nvidia-tegra-igx/5.15.0.1010.10)

2024-04-11 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-meta-nvidia-tegra-igx 
(5.15.0.1010.10) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/249.11-0ubuntu3.12 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta-nvidia-tegra-igx

[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 2059968] Autopkgtest regression report (linux-meta-nvidia-tegra-igx/5.15.0.1010.10)

2024-04-11 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-meta-nvidia-tegra-igx 
(5.15.0.1010.10) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/249.11-0ubuntu3.12 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta-nvidia-tegra-igx

[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-nvidia-tegra-igx in Ubuntu.
https://bugs.launchpad.net/bugs/2059968

Title:
  Produce kernel snaps for linux-nvidia-tegra-igx

Status in linux-meta-nvidia-tegra-igx package in Ubuntu:
  Fix Committed
Status in linux-nvidia-tegra-igx package in Ubuntu:
  Fix Committed
Status in linux-nvidia-tegra-igx-modules-signed package in Ubuntu:
  Fix Committed
Status in linux-signed-nvidia-tegra-igx package in Ubuntu:
  Fix Committed

Bug description:
  We plan on producing Ubuntu Core images with the linux-nvidia-tegra-
  igx kernel. To support this, add support for producing kernel snaps to
  our kernel source packaging.

  This requires changes to linux-meta-nvidia-tegra-igx, 
linux-signed-nvidia-tegra-igx, and linux-nvidia-tegra-igx-modules-signed, which 
include:
  * Adding uc meta packages for the -rt and non-rt kernel flavours.
  * Generating signed kernel.efi images.
  * Adding ubuntu-core-initramfs config to include modules unique to Tegra 
platforms.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-tegra-igx/+bug/2059968/+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 2060942] [NEW] Missing power LED on earlier models

2024-04-11 Thread Dave Jones

Public bug reported:

The Pi Zero 2W, 2B, and 3B all fail to light their power LED once the
kernel starts booting under noble (I hope this is only on noble; I only
just noticed this during ISO testing and it's quite possible I missed it
on earlier revisions...).

Specifically, on the 2W (which only has a combined activity and power
LED), /sys/class/leds/ACT/trigger is [actpwr] on RaspiOS, which makes it
illuminate by default and blink off during mmc0 activity. This trigger
setting appears to be unavailable under the Ubuntu kernel.

On the 2B and 3B, the trigger is set to [none] which results in the LED
initially illuminating while the bootloader is running and then
disappearing. The default under RaspiOS is [input] which makes it
illuminate normally, but switch off on undervolt. This trigger settging
also appears unavailable under the Ubuntu kernel.

** Affects: linux-raspi (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: raspi-image rls-nn-incoming

** Tags added: raspi-image

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

** Tags added: rls-nn-incoming

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

Title:
  Missing power LED on earlier models

Status in linux-raspi package in Ubuntu:
  Confirmed

Bug description:
  The Pi Zero 2W, 2B, and 3B all fail to light their power LED once the
  kernel starts booting under noble (I hope this is only on noble; I
  only just noticed this during ISO testing and it's quite possible I
  missed it on earlier revisions...).

  Specifically, on the 2W (which only has a combined activity and power
  LED), /sys/class/leds/ACT/trigger is [actpwr] on RaspiOS, which makes
  it illuminate by default and blink off during mmc0 activity. This
  trigger setting appears to be unavailable under the Ubuntu kernel.

  On the 2B and 3B, the trigger is set to [none] which results in the
  LED initially illuminating while the bootloader is running and then
  disappearing. The default under RaspiOS is [input] which makes it
  illuminate normally, but switch off on undervolt. This trigger
  settging also appears unavailable under the Ubuntu kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2060942/+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 2060217] Comment bridged from LTC Bugzilla

2024-04-11 Thread bugproxy

--- Comment From vasily.gor...@de.ibm.com 2024-04-11 05:50 EDT---
I've sent a fix proposal to mailing lists
https://lore.kernel.org/all/patch.git-0ff58649313e.your-ad-here.call-01712828617-ext-4049@work.hours/

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

Title:
  NFSv4 fails to mount in noble/s390x

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New
Status in nfs-utils package in Ubuntu:
  Triaged

Bug description:
  https://autopkgtest.ubuntu.com/packages/n/nfs-utils/noble/s390x

  Looks like it has been failing for a long time already.

  Log: https://autopkgtest.ubuntu.com/results/autopkgtest-
  noble/noble/s390x/n/nfs-utils/20240404_145924_ef255@/log.gz

  339s autopkgtest [14:41:04]: test local-server-client: 
[---
  340s Killed
  340s autopkgtest [14:41:05]: test process requested reboot with marker boot1
  364s autopkgtest-virt-ssh: WARNING: ssh connection failed. Retrying in 3 
seconds...
  372s FAIL: nfs_home not mounted
  373s autopkgtest [14:41:38]: test local-server-client: 
---]
  373s local-server-client  FAIL non-zero exit status 1

  and

  934s autopkgtest [14:50:59]: test kerberos-mount: [---
  935s Initializing database '/var/lib/krb5kdc/principal' for realm 'DEP8',
  935s master key name 'K/M@DEP8'
  935s Authenticating as principal root/admin@DEP8 with password.
  935s Principal "nfs/nfs-server.dep8@DEP8" created.
  935s Authenticating as principal root/admin@DEP8 with password.
  935s Entry for principal nfs/nfs-server.dep8 with kvno 2, encryption type 
aes256-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab.
  935s Entry for principal nfs/nfs-server.dep8 with kvno 2, encryption type 
aes128-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab.
  935s Authenticating as principal root/admin@DEP8 with password.
  935s Principal "host/nfs-server.dep8@DEP8" created.
  935s Authenticating as principal root/admin@DEP8 with password.
  935s Entry for principal host/nfs-server.dep8 with kvno 2, encryption type 
aes256-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab.
  935s Entry for principal host/nfs-server.dep8 with kvno 2, encryption type 
aes128-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab.
  936s exporting *:/storage
  938s mount.nfs: mount system call failed for /mnt
  938s umount: /mnt: not mounted.
  938s autopkgtest [14:51:02]: test kerberos-mount: ---]
  939s kerberos-mount   FAIL non-zero exit status 32

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2060217/+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 2060904] Re: Fix the RTL8852CE BT FW Crash based on SER false alarm

2024-04-11 Thread Hui Wang

** Description changed:

- This bug is for tracking purpose
+ This SRU template is for linux-firmware:
+ 
+ BugLink: https://bugs.launchpad.net/bugs/2060904
+ 
+ [Impact]
+ 
+ On a Dell laptop, let it connect to a WiFi router, connect a BT
+ device, then disconnect it, connect the bt device again, we expect
+ the device could be connected successfully, but it couldn't and
+ the BT firmeware crashed.
+ 
+ [Fix]
+ 
+ Need to upgrade the firmware for RTL8852CE and cherry-pick 2 kernel
+ patches, here we send the MR for firmware first. And it is backward
+ compatible, the upgraded firmware could work with kernel without
+ those 2 patches as well as before.
+ 
+ [Test Case]
+ 
+ With the upgraded firmware + kernel without the 2 kernel patches,
+ the wifi and bt could work as well / bad as before.
+ 
+ With the upgraded firmware + kernel with the 2 kernel patches, bt
+ firmware will not crash anymore and bt could connect / disconnect
+ many many bt devices.
+ 
+ [Where problems could occur]
+ 
+ This MR comes from upstream commit, it has low possibility to
+ introduce regression. If the bt or wifi on this laptop couldn't
+ work as well as before, it is possible that this MR introduces
+ regression. According to our test, the wifi and bt could work well
+ with upgraded firmware.

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

Title:
  Fix the RTL8852CE BT FW Crash based on SER false alarm

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

Bug description:
  This SRU template is for linux-firmware:

  BugLink: https://bugs.launchpad.net/bugs/2060904

  [Impact]

  On a Dell laptop, let it connect to a WiFi router, connect a BT
  device, then disconnect it, connect the bt device again, we expect
  the device could be connected successfully, but it couldn't and
  the BT firmeware crashed.

  [Fix]

  Need to upgrade the firmware for RTL8852CE and cherry-pick 2 kernel
  patches, here we send the MR for firmware first. And it is backward
  compatible, the upgraded firmware could work with kernel without
  those 2 patches as well as before.

  [Test Case]

  With the upgraded firmware + kernel without the 2 kernel patches,
  the wifi and bt could work as well / bad as before.

  With the upgraded firmware + kernel with the 2 kernel patches, bt
  firmware will not crash anymore and bt could connect / disconnect
  many many bt devices.

  [Where problems could occur]

  This MR comes from upstream commit, it has low possibility to
  introduce regression. If the bt or wifi on this laptop couldn't
  work as well as before, it is possible that this MR introduces
  regression. According to our test, the wifi and bt could work well
  with upgraded firmware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2060904/+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 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

2024-04-11 Thread Axel Schneck

Hello,

I just tested your suggestion wit 104
It's working here with this kernel
Dont understand why you will still provide a faulty kernel until end of month?
We have a lot of servers here using CIFS mounts and we have to prevent all of 
them now from getting a faulty kernel.
bye
Axel

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

Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  Hi,

  updated some Ubuntu 22.04 systems to lastest available state this
  morning, which caused CIFS mounts (from various fileservers) to stop
  working. Kernel was updated to version 5.15.0-102-generic.

  I can mount the shares without problems (mount -t cifs), but then, df for 
example tells me: df: /mnt: Resource temporarily unavailable.
  I'm able to list and browse all the files, but accessing them (even readonly) 
is very unstable. Sometimes it works and sometimes it just gives me i/o errors. 

  Switching back to  5.15.0-101-generic or 5.15.0-100-generic solves the
  problem and everything works again as expected.

  Seems like some bug has been implemented in 5.15.0-102-generic...

  To reproduce the problem, I started a while loop on one server to
  write to some file on a specific mounted CIFS share and read it from
  another one

  root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; 
sleep 1 ; done
  -bash: /mnt/hallo.txt: Input/output error
  -bash: /mnt/hallo.txt: Input/output error
  ^C

  root@:~$ tail -f /mnt/hallo.txt
  Tue Apr  9 04:10:52 PM CEST 2024 hallo
  Tue Apr  9 04:10:53 PM CEST 2024 hallo
  Tue Apr  9 04:10:54 PM CEST 2024 hallo
  Tue Apr  9 04:10:55 PM CEST 2024 hallo
  Tue Apr  9 04:10:56 PM CEST 2024 hallo
  Tue Apr  9 04:10:57 PM CEST 2024 hallo
  Tue Apr  9 04:10:58 PM CEST 2024 hallo
  Tue Apr  9 04:10:59 PM CEST 2024 hallo
  Tue Apr  9 04:11:00 PM CEST 2024 hallo
  Tue Apr  9 04:11:01 PM CEST 2024 hallo
  tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: 
Resource temporarily unavailable
  Tue Apr  9 04:11:04 PM CEST 2024 hallo
  Tue Apr  9 04:11:05 PM CEST 2024 hallo
  Tue Apr  9 04:11:06 PM CEST 2024 hallo
  Tue Apr  9 04:11:07 PM CEST 2024 hallo
  Tue Apr  9 04:11:08 PM CEST 2024 hallo
  Tue Apr  9 04:11:09 PM CEST 2024 hallo
  Tue Apr  9 04:11:10 PM CEST 2024 hallo

  While doing this, both servers tell me, the resource is unavailable

  root@:~# df -h /mnt
  df: /mnt: Resource temporarily unavailable

  root@:~$ df -h /mnt
  df: /mnt: Resource temporarily unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+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 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

2024-04-11 Thread Benjamin Richner

> Just a note that 5.15.0-104-generic is a part of the 2024.04.01 SRU
cycle, and will likely be released at the end of month, as per
https://kernel.ubuntu.com/, and won't be coming out any sooner.

Do I understand this correctly, do you keep kernel update 5.15.0-102.112
in place and let people update into a kernel that breaks SMB/CIFS for
almost an entire month? Isn't that dangerous? I manage a bunch of Ubuntu
servers and I had to instruct people to hold off on all Ubuntu updates
immediately as not to break all the file shares, which would be very
disruptive to our operations.

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

Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  Hi,

  updated some Ubuntu 22.04 systems to lastest available state this
  morning, which caused CIFS mounts (from various fileservers) to stop
  working. Kernel was updated to version 5.15.0-102-generic.

  I can mount the shares without problems (mount -t cifs), but then, df for 
example tells me: df: /mnt: Resource temporarily unavailable.
  I'm able to list and browse all the files, but accessing them (even readonly) 
is very unstable. Sometimes it works and sometimes it just gives me i/o errors. 

  Switching back to  5.15.0-101-generic or 5.15.0-100-generic solves the
  problem and everything works again as expected.

  Seems like some bug has been implemented in 5.15.0-102-generic...

  To reproduce the problem, I started a while loop on one server to
  write to some file on a specific mounted CIFS share and read it from
  another one

  root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; 
sleep 1 ; done
  -bash: /mnt/hallo.txt: Input/output error
  -bash: /mnt/hallo.txt: Input/output error
  ^C

  root@:~$ tail -f /mnt/hallo.txt
  Tue Apr  9 04:10:52 PM CEST 2024 hallo
  Tue Apr  9 04:10:53 PM CEST 2024 hallo
  Tue Apr  9 04:10:54 PM CEST 2024 hallo
  Tue Apr  9 04:10:55 PM CEST 2024 hallo
  Tue Apr  9 04:10:56 PM CEST 2024 hallo
  Tue Apr  9 04:10:57 PM CEST 2024 hallo
  Tue Apr  9 04:10:58 PM CEST 2024 hallo
  Tue Apr  9 04:10:59 PM CEST 2024 hallo
  Tue Apr  9 04:11:00 PM CEST 2024 hallo
  Tue Apr  9 04:11:01 PM CEST 2024 hallo
  tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: 
Resource temporarily unavailable
  Tue Apr  9 04:11:04 PM CEST 2024 hallo
  Tue Apr  9 04:11:05 PM CEST 2024 hallo
  Tue Apr  9 04:11:06 PM CEST 2024 hallo
  Tue Apr  9 04:11:07 PM CEST 2024 hallo
  Tue Apr  9 04:11:08 PM CEST 2024 hallo
  Tue Apr  9 04:11:09 PM CEST 2024 hallo
  Tue Apr  9 04:11:10 PM CEST 2024 hallo

  While doing this, both servers tell me, the resource is unavailable

  root@:~# df -h /mnt
  df: /mnt: Resource temporarily unavailable

  root@:~$ df -h /mnt
  df: /mnt: Resource temporarily unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+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 2060924] Re: [Lenovo Ubuntu 24.04 Bug] Can not detect iscsi disk storage and kernel show " detected conn error (1020)"

2024-04-11 Thread xiaochun Lee

The  OS will pop out the "detected conn error (1020)" after run
command "systemctl restart iscsid" and command "systemctl restart open-
iscsi" I've open debug mode of module "scsi_tcp, libiscsi,
scsi_transport_iscsi" and have the journal log and sosreport log for
you.

-->>
Apr 10 07:48:27 test kernel: scsi host18: iSCSI Initiator over TCP/IP
Apr 10 07:48:28 test kernel:  connection2:0: detected conn error (1020)
Apr 10 07:48:28 test iscsid[3302]: Could not set session2 priority. 
READ/WRITE throughout and latency could be affected.
Apr 10 07:48:28 test iscsid[3302]: Login failed to authenticate with 
target iqn.1986-03.com.ibm:2145.v7000gen2.node2
Apr 10 07:48:28 test iscsid[3302]: session 2 login rejected: Initiator 
failed authentication with target
Apr 10 07:48:28 test iscsid[3302]: Connection2:0 to [target: 
iqn.1986-03.com.ibm:2145.v7000gen2.node2, portal: 9.0.0.22,3260] through 
[iface: default] is shutdown

Apr 10 07:59:34 test iscsiadm[4267]: iscsiadm: initiator reported error 
(24 - iSCSI login failed due to authorization failure)
Apr 10 07:59:34 test iscsiadm[4267]: iscsiadm: Could not login to 
[iface: default, target: iqn.1986-03.com.ibm:2145.v7000gen2.node2, portal: 
9.0.0.22,3260].
Apr 10 07:59:34 test iscsiadm[4267]: iscsiadm: initiator reported error 
(24 - iSCSI login failed due to authorization failure)
Apr 10 07:59:34 test iscsiadm[4267]: iscsiadm: Could not log into all 
portals
Apr 10 07:59:34 test iscsiadm[4267]: Logging in to [iface: default, 
target: iqn.1986-03.com.ibm:2145.v7000gen2.node2, portal: 
2000:0501::0100::::0666,3260]
Apr 10 07:59:34 test iscsiadm[4267]: Logging in to [iface: default, target: 
iqn.1986-03.com.ibm:2145.v7000gen2.node2, portal: 9.0.0.22,3260]
<<--

** Attachment added: "sosreport file"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060924/+attachment/5763645/+files/sosreport-test-111-2024-04-11-wjglwlp.tar.xz

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

Title:
  [Lenovo Ubuntu 24.04 Bug] Can not detect iscsi disk storage and kernel
  show " detected conn error (1020)"

Status in linux package in Ubuntu:
  New

Bug description:
  Description:
  When installing Ubuntu 24.04 in remote iscsi storage disk, the installer can 
not detect the remote iscsi storage. After install Ubuntu 24.04 to a local disk 
and boot up to OS, the OS can not detect the remote iscsi disk either. 

  Reproduce Steps:
1. Install Ubunut 24.04 
2. Boot into OS
3. perform command lsblk check remote disk, there isn't one appeared.
   
  Configuration:
  System: Lenovo SR655V3
  OS:noble-live-server-amd64-0401.iso
  BMC Version ：2.30 (Build ID: KAX321V)
  UEFI Version:3.10 (Build ID: KAE115K)
  CPU:Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz*2 M321R2GA3BB6-CQKMG*8
  NIC adapter: Mellanox ConnectX-6 Lx 10/25GbE SFP28 2-port PCIe Ethernet 
Adapte 
  storage：Lenovo D7000 or Lenovo V7000

   Expected results:
   OS can recognize the remote iscsi disk

   Actual results:
   OS cannot recognize the remote iscsi disk.

  Additional info:
1. Ubuntu 22.04 also have this issue, But RHEL9.4 hasn't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060924/+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 2060924] [NEW] [Lenovo Ubuntu 24.04 Bug] Can not detect iscsi disk storage and kernel show " detected conn error (1020)"

2024-04-11 Thread xiaochun Lee

Public bug reported:

Description:
When installing Ubuntu 24.04 in remote iscsi storage disk, the installer can 
not detect the remote iscsi storage. After install Ubuntu 24.04 to a local disk 
and boot up to OS, the OS can not detect the remote iscsi disk either. 

Reproduce Steps:
  1. Install Ubunut 24.04 
  2. Boot into OS
  3. perform command lsblk check remote disk, there isn't one appeared.
 
Configuration:
System: Lenovo SR655V3
OS:noble-live-server-amd64-0401.iso
BMC Version ：2.30 (Build ID: KAX321V)
UEFI Version:3.10 (Build ID: KAE115K)
CPU:Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz*2 M321R2GA3BB6-CQKMG*8
NIC adapter: Mellanox ConnectX-6 Lx 10/25GbE SFP28 2-port PCIe Ethernet Adapte 
storage：Lenovo D7000 or Lenovo V7000

 Expected results:
 OS can recognize the remote iscsi disk

 Actual results:
 OS cannot recognize the remote iscsi disk.

Additional info:
  1. Ubuntu 22.04 also have this issue, But RHEL9.4 hasn't.

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

** Summary changed:

- [Lenovo Ubuntu 24.04 Bug] Can not detect iscsi disk storage 
+ [Lenovo Ubuntu 24.04 Bug] Can not detect iscsi disk storage and kernel show " 
detected conn error (1020)"

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

Title:
  [Lenovo Ubuntu 24.04 Bug] Can not detect iscsi disk storage and kernel
  show " detected conn error (1020)"

Status in linux package in Ubuntu:
  New

Bug description:
  Description:
  When installing Ubuntu 24.04 in remote iscsi storage disk, the installer can 
not detect the remote iscsi storage. After install Ubuntu 24.04 to a local disk 
and boot up to OS, the OS can not detect the remote iscsi disk either. 

  Reproduce Steps:
1. Install Ubunut 24.04 
2. Boot into OS
3. perform command lsblk check remote disk, there isn't one appeared.
   
  Configuration:
  System: Lenovo SR655V3
  OS:noble-live-server-amd64-0401.iso
  BMC Version ：2.30 (Build ID: KAX321V)
  UEFI Version:3.10 (Build ID: KAE115K)
  CPU:Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz*2 M321R2GA3BB6-CQKMG*8
  NIC adapter: Mellanox ConnectX-6 Lx 10/25GbE SFP28 2-port PCIe Ethernet 
Adapte 
  storage：Lenovo D7000 or Lenovo V7000

   Expected results:
   OS can recognize the remote iscsi disk

   Actual results:
   OS cannot recognize the remote iscsi disk.

  Additional info:
1. Ubuntu 22.04 also have this issue, But RHEL9.4 hasn't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060924/+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 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu"

2024-04-11 Thread fprietog

==
Example for Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64)
==
# lsb_release -rd
No LSB modules are available.
Description:Ubuntu 23.10
Release:23.10

# uname -a
Linux fpgrpi 6.5.0-1014-raspi #17-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 21 
11:24:03 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

# cat /proc/version_signature
Ubuntu 6.5.0-1014.17-raspi 6.5.13


How to reproduce the problem

For instance, I'm using KeePassXC 
(https://launchpad.net/ubuntu/+source/keepassxc) to update a database located 
at CIFS filesystem. Any change done to that database causes this Kernel error 
exception:

abr 11 09:11:02 fpgrpi kernel: Unable to handle kernel paging request at 
virtual address fffe
abr 11 09:11:02 fpgrpi kernel: Mem abort info:
abr 11 09:11:02 fpgrpi kernel:   ESR = 0x9604
abr 11 09:11:02 fpgrpi kernel:   EC = 0x25: DABT (current EL), IL = 32 bits
abr 11 09:11:02 fpgrpi kernel:   SET = 0, FnV = 0
abr 11 09:11:02 fpgrpi kernel:   EA = 0, S1PTW = 0
abr 11 09:11:02 fpgrpi kernel:   FSC = 0x04: level 0 translation fault
abr 11 09:11:02 fpgrpi kernel: Data abort info:
abr 11 09:11:02 fpgrpi kernel:   ISV = 0, ISS = 0x0004, ISS2 = 0x
abr 11 09:11:02 fpgrpi kernel:   CM = 0, WnR = 0, TnD = 0, TagAccess = 0
abr 11 09:11:02 fpgrpi kernel:   GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
abr 11 09:11:02 fpgrpi kernel: swapper pgtable: 4k pages, 48-bit VAs, 
pgdp=01498000
abr 11 09:11:02 fpgrpi kernel: [fffe] pgd=, 
p4d=
abr 11 09:11:02 fpgrpi kernel: Internal error: Oops: 9604 [#1] 
PREEMPT SMP
abr 11 09:11:02 fpgrpi kernel: Modules linked in: rfcomm snd_seq_dummy 
snd_hrtimer snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device 
nls_utf8 cifs cifs_arc4 cifs_md4 fscache netfs cmac algif_hash algif_skcipher 
af_alg bnep lz4 lz4_compress zram zsmalloc nft_chain_nat nf_nat sunrpc 
xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 binfmt_misc 
nft_compat nf_tables nfnetlink brcmfmac_wcc btsdio brcmfmac vc4 brcmutil 
snd_soc_hdmi_codec hci_uart cfg80211 drm_display_helper btqca btrtl 
raspberrypi_hwmon cec drm_dma_helper btbcm btintel bluetooth 
raspberrypi_gpiomem drm_kms_helper ecdh_generic rfkill ecc snd_soc_core 
bcm2835_v4l2(CE) bcm2835_codec(CE) bcm2835_isp(CE) bcm2835_mmal_vchiq(CE) 
snd_compress ac97_bus snd_pcm_dmaengine rpivid_hevc(CE) vc_sm_cma(CE) 
snd_bcm2835(CE) v4l2_mem2mem videobuf2_vmalloc videobuf2_dma_contig 
videobuf2_memops videobuf2_v4l2 videodev videobuf2_common mc snd_pcm snd_timer 
joydev nvmem_rmem input_leds uio_pdrv_genirq uio tcp_bbr
  sch_fq ecryptfs parport_pc ppdev lp parport fuse
abr 11 09:11:02 fpgrpi kernel:  ip_tables x_tables autofs4 btrfs 
blake2b_generic raid10 hid_generic raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx usbhid xor xor_neon uas usb_storage raid6_pq 
libcrc32c raid1 raid0 multipath linear md_mod dm_mirror dm_region_hash dm_log 
dm_mod dax zstd z3fold spidev dwc2 v3d gpu_sched drm_shmem_helper drm roles 
crct10dif_ce drm_panel_orientation_quirks i2c_brcmstb udc_core i2c_bcm2835 
xhci_pci xhci_pci_renesas spi_bcm2835 snd backlight phy_generic aes_arm64
abr 11 09:11:02 fpgrpi kernel: CPU: 3 PID: 79549 Comm: Thread (pooled) Tainted: 
G C  E  6.5.0-1014-raspi #17-Ubuntu
abr 11 09:11:02 fpgrpi kernel: Hardware name: Raspberry Pi 4 Model B Rev 1.4 
(DT)
abr 11 09:11:02 fpgrpi kernel: pstate: 6045 (nZCv daif +PAN -UAO -TCO -DIT 
-SSBS BTYPE=--)
abr 11 09:11:02 fpgrpi kernel: pc : cifs_flush_folio+0x5c/0x160 [cifs]
abr 11 09:11:02 fpgrpi kernel: lr : cifs_flush_folio+0x50/0x160 [cifs]
abr 11 09:11:02 fpgrpi kernel: sp : 80008d00bb30
abr 11 09:11:02 fpgrpi kernel: x29: 80008d00bb30 x28:  x27: 
6cb892a49000
abr 11 09:11:02 fpgrpi kernel: x26: 6cb88fff9200 x25: 6cb92bd1c350 x24: 

abr 11 09:11:02 fpgrpi kernel: x23: 0001 x22: 80008d00bba8 x21: 
80008d00bbb0
abr 11 09:11:02 fpgrpi kernel: x20:  x19: fffe x18: 

abr 11 09:11:02 fpgrpi kernel: x17:  x16: b6bfe450e050 x15: 

abr 11 09:11:02 fpgrpi kernel: x14:  x13:  x12: 

abr 11 09:11:02 fpgrpi kernel: x11:  x10:  x9 : 
b6bfe450df28
abr 11 09:11:02 fpgrpi kernel: x8 : 80008d00bad8 x7 :  x6 : 
00023854
abr 11 09:11:02 fpgrpi kernel: x5 : 6cb887d82080 x4 : 1000 x3 : 

abr 11 09:11:02 fpgrpi kernel: x2 :  x1 : 0001 x0 : 
fffe
abr 11 09:11:02 fpgrpi kernel: Call trace:
abr 11 09:11:02 fpgrpi kernel:  cifs_flush_folio+0x5c/0x160 [cifs]
abr 11 09:11:02 fpgrpi kernel:

[Kernel-packages] [Bug 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu"

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

** Changed in: linux-raspi (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/2060919

Title:
  Remote filesystems mounted as CIFS not working after update to Kernel
  "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi
  #17-Ubuntu" (aarch64).

Status in linux package in Ubuntu:
  Confirmed
Status in linux-raspi package in Ubuntu:
  Confirmed

Bug description:
  Remote filesystems mounted as CIFS are not working after update to
  Kernel "6.5.0-27-generic #28-Ubuntu" for x86_64 (and also after
  updating to Kernel "6.5.0-1014-raspi #17-Ubuntu" in aarch64).

  The remote filesystem is correctly mounted and seems to work but
  trying to write data to the filesystem ends in a kernel error
  exception. After that error the CIFS filesystem just became unusable.

  Previous Kernel version works correctly.

  =
  Example for Kernel "6.5.0-27-generic #28-Ubuntu" (x86_64)
  =
  # lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10

  # uname -a
  Linux fpgmsi 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar  7 
18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  # cat /proc/version_signature
  Ubuntu 6.5.0-27.28-generic 6.5.13

  
  How to reproduce the problem
  
  For instance, I'm using KeePassXC 
(https://launchpad.net/ubuntu/+source/keepassxc) to update a database located 
at CIFS filesystem. Any change done to that database causes this Kernel error 
exception:

  abr 11 09:34:59 fpgmsi kernel: BUG: unable to handle page fault for address: 
fffe
  abr 11 09:34:59 fpgmsi kernel: #PF: supervisor read access in kernel mode
  abr 11 09:34:59 fpgmsi kernel: #PF: error_code(0x) - not-present page
  abr 11 09:34:59 fpgmsi kernel: PGD f45a3f067 P4D f45a3f067 PUD f45a41067 PMD 
0 
  abr 11 09:34:59 fpgmsi kernel: Oops:  [#1] PREEMPT SMP NOPTI
  abr 11 09:34:59 fpgmsi kernel: CPU: 0 PID: 28103 Comm: Thread (pooled) 
Tainted: P   OE  6.5.0-27-generic #28-Ubuntu
  abr 11 09:34:59 fpgmsi kernel: Hardware name: Micro-Star International Co., 
Ltd. MAG Z690 Codex X5 (MS-B930)/PRO Z690-A WIFI (MS-7D25), BIOS D.50 04/26/2022
  abr 11 09:34:59 fpgmsi kernel: RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs]
  abr 11 09:34:59 fpgmsi kernel: Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 
0c 53 48 83 ec 08 48 8b 7f 30 44 89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 
db 74 77 <48> 8b 13 b8 00 10 00 00 f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3
  abr 11 09:34:59 fpgmsi kernel: RSP: 0018:aab6865ffbf8 EFLAGS: 00010282
  abr 11 09:34:59 fpgmsi kernel: RAX:  RBX: fffe 
RCX: 
  abr 11 09:34:59 fpgmsi kernel: RDX:  RSI:  
RDI: 
  abr 11 09:34:59 fpgmsi kernel: RBP: aab6865ffc28 R08: 0001 
R09: 
  abr 11 09:34:59 fpgmsi kernel: R10: 00023854 R11:  
R12: 
  abr 11 09:34:59 fpgmsi kernel: R13: aab6865ffc78 R14: 906675d8aed0 
R15: aab6865ffc70
  abr 11 09:34:59 fpgmsi kernel: FS:  7bd4d594b6c0() 
GS:90753f80() knlGS:
  abr 11 09:34:59 fpgmsi kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  abr 11 09:34:59 fpgmsi kernel: CR2: fffe CR3: 00017022a000 
CR4: 00750ef0
  abr 11 09:34:59 fpgmsi kernel: PKRU: 5554
  abr 11 09:34:59 fpgmsi kernel: Call Trace:
  abr 11 09:34:59 fpgmsi kernel:  
  abr 11 09:34:59 fpgmsi kernel:  ? show_regs+0x6d/0x80
  abr 11 09:34:59 fpgmsi kernel:  ? __die+0x24/0x80
  abr 11 09:34:59 fpgmsi kernel:  ? page_fault_oops+0x99/0x1b0
  abr 11 09:34:59 fpgmsi kernel:  ? kernelmode_fixup_or_oops+0xb2/0x140
  abr 11 09:34:59 fpgmsi kernel:  ? __bad_area_nosemaphore+0x1a5/0x2c0
  abr 11 09:34:59 fpgmsi kernel:  ? bad_area_nosemaphore+0x16/0x30
  abr 11 09:34:59 fpgmsi kernel:  ? do_kern_addr_fault+0x7b/0xa0
  abr 11 09:34:59 fpgmsi kernel:  ? exc_page_fault+0x1a4/0x1b0
  abr 11 09:34:59 fpgmsi kernel:  ? asm_exc_page_fault+0x27/0x30
  abr 11 09:34:59 fpgmsi kernel:  ? cifs_flush_folio+0x41/0xf0 [cifs]
  abr 11 09:34:59 fpgmsi kernel:  ? cifs_flush_folio+0x37/0xf0 [cifs]
  abr 11 09:34:59 fpgmsi kernel:  cifs_remap_file_range+0x172/0x660 [cifs]
  abr 11 09:34:59 fpgmsi kernel:  do_clone_file_range+0x101/0x2d0
  abr 11 09:34:59 fpgmsi kernel:  vfs_clone_file_range+0x3f/0x150
  abr 11 09:34:59 fpgmsi kernel:  ioctl_file_clone+0x52/0xc0
  abr 11 09:34:59 fpgmsi kernel:  do_vfs_ioctl+0x68f/0x910
  abr 11 09:34:59 fpgmsi kernel:  ? __fget_light+0xa5/0x120
  abr 11 09:34:59 fpgmsi kernel:  __x64_sys_ioctl+0x7d/0xf0

[Kernel-packages] [Bug 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu"