[Kernel-packages] [Bug 2021740] Re: Add modaliases support

[You-Sheng Yang]

SRU:
* http://10.131.201.69/kernel/jammy-linux-oem/pulls/81 (oem-6.5)
* http://10.131.201.69/kernel/jammy-linux-oem/pulls/82 (oem-6.1)

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

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

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

** Changed in: linux-oem-6.1 (Ubuntu Kinetic)
   Status: New => Invalid

** Changed in: linux-oem-6.1 (Ubuntu Lunar)
   Status: New => Invalid

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

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

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

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

** Changed in: linux (Ubuntu Jammy)
   Status: New => Won't Fix

** Changed in: linux (Ubuntu Kinetic)
   Status: New => Won't Fix

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

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

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

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

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

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

** Description changed:

  [SRU Justifications]
+ 
+ == kernel ==
+ 
+ [Impact]
+ 
+ Need modaliases info for ubuntu-drivers integration.
+ 
+ [Fix]
+ 
+ This Ubuntu sauced patch copies modaliases info from source dkms deb packages 
to
+ standalone `linux-modules---` ones if available.
+ 
+ [Test Case]
+ 
+ ```bash
+ $ sudo add-apt-repository ppa:canonical-hwe-team/experimental-unstable
+ $ apt-cache show linux-modules-ivsc-6.6.0-9005-generic | grep Modaliases
+ Modaliases: mei-vsc(acpi*:INTC1009:*, acpi*:INTC1058:*, acpi*:INTC1094:*, 
acpi*:INTC10D0:*)
+ ```
+ 
+ [Where problems could occur]
+ 
+ With **XB-Modaliases** field added to deb control, `ubuntu-drivers` will then
+ give a list of installable `linux-modules---` 
candidates
+ on available platforms. So far based on current `debian/dkms-versions`, the 
only
+ one will be enabled will be ivsc-driver, and ipu6-drivers to be SRUed soon.
+ 
+ [Other Info]
+ 
+ To nominate Unstable/Mantic/Lunar/OEM-6.5/OEM-6.1.
+ 
+ Note that this adds a build-dep to dh-modaliases from universe pocket.
+ 
+ == ipu6-drivers, ivsc-driver ==
  
  [Impact]
  
  Bug 2012407: kernel build fails without a newly learned directive in
  /sbin/dkms in bug 2012612 that helps identify whether a dkms modules is
  supposed to be built at all.
  
  Bug 2021740: To allow dkms driver installation initiated by ubuntu-
  drivers, packages must carry XB-Modaliases in debian/control.
  
  Bug 2026402: ipu6 dkms driver now fails to build against v6.5-rc1 and
  on.
  
  [Fix]
  
  * A BUILD_EXCLUSIVE_CONFIG patch for bug 2012407 was added to ivsc-
  driver/{jammy,lunar} because ivsc-driver/mantic has that already from
  bug 2012410. Also applied to ipu6-drivers/{mantic,lunar,jammy}.
  
  * Modaliases fixes for bug 2021740 was applied to ivsc-
  drivers/{mantic,lunar,jammy}, and ipu6-drivers/{mantic,lunar,jammy}
  
  * Additional fixes from upstream ipu6-drivers repo were added to
  ipu6-drivers/mantic for new hardware platforms.
  
  [Test Case]
  
  Bug 2012407: make sure intel-ipu6-dkms build will be skipped on
  platforms without CONFIG_VIDEO_V4L2_I2C, and intel-vsc-dkms on platforms
  without CONFIG_GPIOLIB_IRQCHIP, such as linux-headers-kvm/jammy.
  
  Bug 2021740: check built binary deb has XB-Modaliases tag in `dpkg-deb
  --info` output.
  
  For rest of the changes, they should be verified on next IPU6 equipped
  platform.
  
  [Where problems could occur]
  
  For changes for bug 2012407 and bug 2021740, they do no side effect to
  runtime system but to reinforce the interaction between other
  components.
  
  For rest of the changes, only in ipu6-drivers/mantic, they're to sync
  with upstream development for new hardware platforms, and expects bug
  fixes, updates in the coming development cycle.
  
  [Other Info]
  
  == original bug report ==
  
  To be discovered by ubuntu-drivers, dkms packages should have modaliases
  tag in debian/control as possible.

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

Title:
  Add modaliases support

Status in ipu6-drivers package in Ubuntu:
  In Progress
Status in ivsc-driver package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Jammy:
  In 

[Kernel-packages] [Bug 2021740] Re: Add modaliases support

[You-Sheng Yang]

SRU:
* https://lists.ubuntu.com/archives/kernel-team/2023-October/146164.html (lunar)
* https://lists.ubuntu.com/archives/kernel-team/2023-October/146166.html 
(unstable, mantic)

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

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

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

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

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

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

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

Title:
  Add modaliases support

Status in ipu6-drivers package in Ubuntu:
  In Progress
Status in ivsc-driver package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Jammy:
  In Progress
Status in ivsc-driver source package in Jammy:
  In Progress
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  In Progress
Status in linux-oem-6.5 source package in Jammy:
  In Progress
Status in ipu6-drivers source package in Kinetic:
  Won't Fix
Status in ivsc-driver source package in Kinetic:
  Won't Fix
Status in linux source package in Kinetic:
  Won't Fix
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux-oem-6.5 source package in Kinetic:
  Invalid
Status in ipu6-drivers source package in Lunar:
  In Progress
Status in ivsc-driver source package in Lunar:
  In Progress
Status in linux source package in Lunar:
  In Progress
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in ipu6-drivers source package in Mantic:
  In Progress
Status in ivsc-driver source package in Mantic:
  Fix Released
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [SRU Justifications]

  == kernel ==

  [Impact]

  Need modaliases info for ubuntu-drivers integration.

  [Fix]

  This Ubuntu sauced patch copies modaliases info from source dkms deb packages 
to
  standalone `linux-modules---` ones if available.

  [Test Case]

  ```bash
  $ sudo add-apt-repository ppa:canonical-hwe-team/experimental-unstable
  $ apt-cache show linux-modules-ivsc-6.6.0-9005-generic | grep Modaliases
  Modaliases: mei-vsc(acpi*:INTC1009:*, acpi*:INTC1058:*, acpi*:INTC1094:*, 
acpi*:INTC10D0:*)
  ```

  [Where problems could occur]

  With **XB-Modaliases** field added to deb control, `ubuntu-drivers` will then
  give a list of installable `linux-modules---` 
candidates
  on available platforms. So far based on current `debian/dkms-versions`, the 
only
  one will be enabled will be ivsc-driver, and ipu6-drivers to be SRUed soon.

  [Other Info]

  To nominate Unstable/Mantic/Lunar/OEM-6.5/OEM-6.1.

  Note that this adds a build-dep to dh-modaliases from universe pocket.

  == ipu6-drivers, ivsc-driver ==

  [Impact]

  Bug 2012407: kernel build fails without a newly learned directive in
  /sbin/dkms in bug 2012612 that helps identify whether a dkms modules
  is supposed to be built at all.

  Bug 2021740: To allow dkms driver installation initiated by ubuntu-
  drivers, packages must carry XB-Modaliases in debian/control.

  Bug 2026402: ipu6 dkms driver now fails to build against v6.5-rc1 and
  on.

  [Fix]

  * A BUILD_EXCLUSIVE_CONFIG patch for bug 2012407 was added to ivsc-
  driver/{jammy,lunar} because ivsc-driver/mantic has that already from
  bug 2012410. Also applied to ipu6-drivers/{mantic,lunar,jammy}.

  * Modaliases fixes for bug 2021740 was applied to ivsc-
  drivers/{mantic,lunar,jammy}, and ipu6-drivers/{mantic,lunar,jammy}

  * Additional fixes from upstream ipu6-drivers repo were added to
  ipu6-drivers/mantic for new hardware platforms.

  [Test Case]

  Bug 2012407: make sure intel-ipu6-dkms build will be skipped on
  platforms without CONFIG_VIDEO_V4L2_I2C, and intel-vsc-dkms on
  platforms without CONFIG_GPIOLIB_IRQCHIP, such as linux-headers-
  kvm/jammy.

  Bug 2021740: check built binary deb has XB-Modaliases tag in `dpkg-deb
  --info` output.

  For rest of the changes, they should be verified on next IPU6 equipped
  platform.

  [Where problems could occur]

  For changes for bug 2012407 and bug 2021740, they do no side effect to
  runtime system but to reinforce the interaction between other
  components.

  For rest of the changes, only in ipu6-drivers/mantic, they're to sync
  with upstream development for new hardware 

[Kernel-packages] [Bug 2038685] Re: Missing BTF file in Ubuntu ESM kernels

[Dimitri John Ledkov]

I think if linux-headers package produces /usr/src/linux-
headers-4.15.0-219-generic/vmlinux file everything will "just" work for
everybody.

Although stuff might be surprised if it is not a full vmlinux but just
btf info.

But this might even fix generating btf info for dkms modules.

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

Title:
  Missing BTF file in Ubuntu ESM kernels

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  New
Status in linux source package in Xenial:
  New
Status in linux source package in Bionic:
  New

Bug description:
  This is a follow-up from: https://discourse.ubuntu.com/t/ask-us-
  anything-about-ubuntu-kernels/27664/142

  Older Ubuntu distributions come with a kernel image that support eBPF
  but are not built with a BTF file published (/sys/kernel/btf/vmlinux).
  This BTF file is crucial when trying to run eBPF programs that were
  built with CO-RE in mind such that a program can be compiled once and
  run in any kernel (with some caveats) because the BPF loaders can use
  the BTF file to relocate addresses of kernel fields at load time for
  the currently running kernel. In the past I've used the debug symbols
  that Ubuntu publishes to create BTF files using `pahole` for these
  older kernels and then re-using that BTF file for any machine running
  that kernel. This is not ideal but I had managed to work around it.

  However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18)
  there isn't a debug symbols repository from where to pull the debug
  symbols packages to build their respective BTF file and no BTF file is
  generated when the kernel is built. This essentially makes these ESM
  kernels incompatible with eBPF programs that run using CO-RE (which is
  more or less the norm nowadays). Based on my conversation on the
  discourse link above it seems like ideally these ESM kernels should be
  published with a BTF file.

  P.S. I wasn't able to submit this through `ubuntu-bug linux` as it
  gave me an error saying `Problem in linux-image-4.15.0-218-generic
  This is not an official Ubuntu package. Please remove any third party
  package and try again`. I am not sure why it says that as this is a
  Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro
  attach` and then updated to the latest ESM kernel.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.29
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2021-05-18 (870 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0e0f:0008 VMware, Inc.
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-218-generic 
root=UUID=c6dbf1d0-3a95-4d98-a0f8-fdea28a5ffc9 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  ProcVersionSignature: Ubuntu 4.15.0-218.229-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-218-generic N/A
   linux-backports-modules-4.15.0-218-generic  N/A
   linux-firmware  1.173.21
  RfKill:

  Tags:  bionic
  Uname: Linux 4.15.0-218-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to 

[Kernel-packages] [Bug 2035028] Re: 6.5 kernel BUG at mm/slub.c:440 when cycling bluetooth

[Gerald Nunn]

I'm having the exact same issue albeit on a Lenovo Z16 running Arch
Linux (kernel 6.5.7). I'm curious if your Thinkpad is using the Qualcomm
Bluetooth stack like the Z16 is?

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

Title:
  6.5 kernel BUG at mm/slub.c:440 when cycling bluetooth

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In 6.5.0-4-generic, tried switching Momentum 4 wireless headphones
  between headset and handsfree profiles and I think also ended up
  cycling it on/off, causing a kernel bug in the memory management.

  Sep 08 15:54:45 jak-t14-g3 kernel: [ cut here ]
  Sep 08 15:54:45 jak-t14-g3 kernel: kernel BUG at mm/slub.c:440!
  Sep 08 15:54:45 jak-t14-g3 kernel: invalid opcode:  [#1] PREEMPT SMP NOPTI
  Sep 08 15:54:45 jak-t14-g3 kernel: CPU: 4 PID: 353971 Comm: kworker/u33:3 Not 
tainted 6.5.0-4-generic #4-Ubuntu
  Sep 08 15:54:45 jak-t14-g3 kernel: Hardware name: LENOVO 
21CF004PGE/21CF004PGE, BIOS R23ET65W (1.35 ) 03/21/2023
  Sep 08 15:54:45 jak-t14-g3 kernel: Workqueue: hci0 hci_devcd_rx [bluetooth] 
  Sep 08 15:54:45 jak-t14-g3 kernel: RIP: 0010:__slab_free+0x156/0x2e0
  Sep 08 15:54:45 jak-t14-g3 kernel: Code: 8b 06 48 89 0c 24 48 c1 e8 36 48 8b 
84 c3 d8 00 00 00 48 89 c7 48 89 44 24 20 e8 65 6c cc 00 48 8b 0c 24 48 89 44 
24 08 eb 83 <0f> 0b f7 43 08 00 0d 21 00 75 ca eb bf f7 43 08 00 0d 21 00 0f 84
  Sep 08 15:54:45 jak-t14-g3 kernel: RSP: 0018:ae30a77fbc80 EFLAGS: 00010246
  Sep 08 15:54:45 jak-t14-g3 kernel: RAX: 9c11644bac00 RBX: 
9c0dc0042c00 RCX: 801f
  Sep 08 15:54:45 jak-t14-g3 kernel: RDX: 9c11644ba800 RSI: 
9c11644ba800 RDI: ae30a77fbcf0
  Sep 08 15:54:45 jak-t14-g3 kernel: RBP: ae30a77fbd20 R08: 
0001 R09: 8bfd9f77 
  Sep 08 15:54:45 jak-t14-g3 kernel: R10:  R11: 
 R12: 9c11644ba800
  Sep 08 15:54:45 jak-t14-g3 kernel: R13: 9c11644ba800 R14: 
ec1352912e00 R15: 
  Sep 08 15:54:45 jak-t14-g3 kernel: FS:  () 
GS:9c14def0() knlGS:
  Sep 08 15:54:45 jak-t14-g3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033 
  Sep 08 15:54:45 jak-t14-g3 kernel: CR2: 55ddb6efdcd8 CR3: 
00068703a000 CR4: 00750ee0
  Sep 08 15:54:45 jak-t14-g3 kernel: PKRU: 5554
  Sep 08 15:54:45 jak-t14-g3 kernel: Call Trace:
  Sep 08 15:54:45 jak-t14-g3 kernel:  
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? show_regs+0x6d/0x80
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? die+0x37/0xa0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? do_trap+0xd4/0xf0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? do_error_trap+0x71/0xb0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? __slab_free+0x156/0x2e0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? exc_invalid_op+0x52/0x80
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? __slab_free+0x156/0x2e0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? asm_exc_invalid_op+0x1b/0x20
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? skb_free_head+0x87/0xd0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? __slab_free+0x156/0x2e0
  Sep 08 15:54:45 jak-t14-g3 kernel:  __kmem_cache_free+0x318/0x360
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? skb_free_head+0x87/0xd0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? srso_alias_return_thunk+0x5/0x7f
  Sep 08 15:54:45 jak-t14-g3 kernel:  kfree+0x78/0x120
  Sep 08 15:54:45 jak-t14-g3 kernel:  skb_free_head+0x87/0xd0
  Sep 08 15:54:45 jak-t14-g3 kernel:  skb_release_data+0x159/0x200
  Sep 08 15:54:45 jak-t14-g3 kernel:  kfree_skb_reason+0x55/0x140
  Sep 08 15:54:45 jak-t14-g3 kernel:  hci_devcd_rx+0x99/0x580 [bluetooth]
  Sep 08 15:54:45 jak-t14-g3 kernel:  process_one_work+0x223/0x440
  Sep 08 15:54:45 jak-t14-g3 kernel:  worker_thread+0x4d/0x3f0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? srso_alias_return_thunk+0x5/0x7f
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? _raw_spin_lock_irqsave+0xe/0x20
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? __pfx_worker_thread+0x10/0x10
  Sep 08 15:54:45 jak-t14-g3 kernel:  kthread+0xf2/0x120
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? __pfx_kthread+0x10/0x10
  Sep 08 15:54:45 jak-t14-g3 kernel:  ret_from_fork+0x47/0x70
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? __pfx_kthread+0x10/0x10
  Sep 08 15:54:45 jak-t14-g3 kernel:  ret_from_fork_asm+0x1b/0x30
  Sep 08 15:54:45 jak-t14-g3 kernel:  
  Sep 08 15:54:45 jak-t14-g3 kernel: Modules linked in: ccm michael_mic 
vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock rfcomm 
snd_seq_dummy snd_hrtimer wireguard curve25519_x86_64 libchacha20poly1305 
chacha_x86_64 poly1305_x86_64 libcurve25519_generic libchacha ip6_udp_tunnel 
udp_tunnel cmac algif_hash algif_skcipher af_alg snd_usb_audio snd_usbmidi_lib 
snd_ump bnep overlay btusb btrtl btbcm btintel btmtk binfmt_misc bluetooth 
ecdh_generic ecc qrtr_mhi uvcvideo videobuf2_vmalloc cdc_mbim uvc cdc_wdm 
videobuf2_memops cdc_ncm videobuf2_v4l2 

[Kernel-packages] [Bug 2034688] Re: installation of kernel headers fail with "Read-only file system" error

[Dimitri John Ledkov]

Can you please try refresh to channel 23.10/beta or --revision 1474 and
let me know if this improves things?

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  installation of kernel headers fail with "Read-only file system" error

Status in ubuntu-desktop-installer:
  Triaged
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Mantic 20230907

  Installation of packages that ship files in /lib/modules or
  /lib/firmware are expected to fail, so their installation must be
  prevented.

  For instance:

  $ apt install linux-headers-generic-6.3.0-7
  Reading package lists...
  Building dependency tree...
  Reading state information...
  linux-headers-6.3.0-7 is already the newest version (6.3.0-7.7).
  The following packages will be upgraded:
linux-headers-6.3.0-7-generic
  1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  51 not fully installed or removed.
  Need to get 0 B/3,667 kB of archives.
  After this operation, 27.9 MB of additional disk space will be used.
  (Reading database ... 132615 files and directories currently installed.)
  Preparing to unpack .../linux-headers-6.3.0-7-generic_6.3.0-7.7_amd64.deb ...
  Unpacking linux-headers-6.3.0-7-generic (6.3.0-7.7) over (6.3.0-7.7) ...
  dpkg: error processing archive 
/var/cache/apt/archives/linux-headers-6.3.0-7-generic_6.3.0-7.7_amd64.deb 
(--unpack):
   error creating symbolic link './lib/modules/6.3.0-7-generic/build': 
Read-only file system
  dpkg: error while cleaning up:
   unable to remove newly-extracted version of 
'/lib/modules/6.3.0-7-generic/build': Read-only file system
  Errors were encountered while processing:
   /var/cache/apt/archives/linux-headers-6.3.0-7-generic_6.3.0-7.7_amd64.deb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2034688/+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 2034688] Re: installation of kernel headers fail with "Read-only file system" error

[Dimitri John Ledkov]

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

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

Title:
  installation of kernel headers fail with "Read-only file system" error

Status in ubuntu-desktop-installer:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Mantic 20230907

  Installation of packages that ship files in /lib/modules or
  /lib/firmware are expected to fail, so their installation must be
  prevented.

  For instance:

  $ apt install linux-headers-generic-6.3.0-7
  Reading package lists...
  Building dependency tree...
  Reading state information...
  linux-headers-6.3.0-7 is already the newest version (6.3.0-7.7).
  The following packages will be upgraded:
linux-headers-6.3.0-7-generic
  1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  51 not fully installed or removed.
  Need to get 0 B/3,667 kB of archives.
  After this operation, 27.9 MB of additional disk space will be used.
  (Reading database ... 132615 files and directories currently installed.)
  Preparing to unpack .../linux-headers-6.3.0-7-generic_6.3.0-7.7_amd64.deb ...
  Unpacking linux-headers-6.3.0-7-generic (6.3.0-7.7) over (6.3.0-7.7) ...
  dpkg: error processing archive 
/var/cache/apt/archives/linux-headers-6.3.0-7-generic_6.3.0-7.7_amd64.deb 
(--unpack):
   error creating symbolic link './lib/modules/6.3.0-7-generic/build': 
Read-only file system
  dpkg: error while cleaning up:
   unable to remove newly-extracted version of 
'/lib/modules/6.3.0-7-generic/build': Read-only file system
  Errors were encountered while processing:
   /var/cache/apt/archives/linux-headers-6.3.0-7-generic_6.3.0-7.7_amd64.deb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2034688/+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 2039231] [NEW] UBSAN: array-index-out-of-bounds in /build/linux-oem-6.5-XiW3QL/linux-oem-6.5-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7655:12

[Robert Ross]

Public bug reported:

Dmesg is full of UBSAN errors to do with the mpt3sas driver when
initializing an mpt2sas device.

[5.012673] UBSAN: array-index-out-of-bounds in 
/build/linux-oem-6.5-XiW3QL/linux-oem-6.5-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12
[5.014521] index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY 
[1]'
[5.015606] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 6.5.0-1004-oem 
#4-Ubuntu
[5.015611] Hardware name: Supermicro C7Q67/C7Q67, BIOS 2.1a 11/10/2015
[5.015613] Call Trace:
[5.015617]  
[5.015621]  dump_stack_lvl+0x48/0x70
[5.015632]  dump_stack+0x10/0x20
[5.015637]  __ubsan_handle_out_of_bounds+0xc6/0x110
[5.015646]  _scsih_check_topo_delete_events+0x2dc/0x350 [mpt3sas]
[5.015698]  mpt3sas_scsih_event_callback+0x21f/0x630 [mpt3sas]
[5.015735]  _base_async_event.isra.0+0x73/0x190 [mpt3sas]
[5.015769]  _base_process_reply_queue+0x3a0/0x720 [mpt3sas]
[5.015799]  _base_interrupt+0x4e/0x70 [mpt3sas]
[5.015829]  __handle_irq_event_percpu+0x4f/0x1c0
[5.015835]  handle_irq_event+0x39/0x80
[5.015839]  handle_edge_irq+0x8c/0x250
[5.015844]  __common_interrupt+0x56/0x110
[5.015850]  common_interrupt+0x9f/0xb0
[5.015854]  
[5.015856]  
[5.015858]  asm_common_interrupt+0x27/0x40
[5.015865] RIP: 0010:cpuidle_enter_state+0xda/0x720
[5.015872] Code: 25 07 ff e8 a8 f5 ff ff 8b 53 04 49 89 c7 0f 1f 44 00 00 
31 ff e8 46 d1 05 ff 80 7d d0 00 0f 85 61 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 
0f 88 f7 01 00 00 4d 63 ee 49 83 fd 09 0f 87 19 05 00 00
[5.015876] RSP: 0018:ac24c00bbe18 EFLAGS: 0246
[5.015881] RAX:  RBX: a0abc03beb00 RCX: 
[5.015884] RDX: 0003 RSI:  RDI: 
[5.015886] RBP: ac24c00bbe68 R08:  R09: 
[5.015888] R10:  R11:  R12: b64d1ac0
[5.015890] R13: 0004 R14: 0004 R15: 00012ab445e7
[5.015895]  ? cpuidle_enter_state+0xca/0x720
[5.015901]  ? tick_nohz_stop_tick+0x90/0x210
[5.015908]  cpuidle_enter+0x2e/0x50
[5.015912]  call_cpuidle+0x23/0x60
[5.015918]  cpuidle_idle_call+0x11d/0x190
[5.015922]  do_idle+0x82/0xf0
[5.015926]  cpu_startup_entry+0x1d/0x20
[5.015930]  start_secondary+0x129/0x160
[5.015936]  secondary_startup_64_no_verify+0x17e/0x18b
[5.015944]  
[5.015946] 

[5.017993] mpt2sas_cm0: hba_port entry: fd3a54f4, port: 255 is 
added to hba_port list
[5.018324] 

[5.019566] UBSAN: array-index-out-of-bounds in 
/build/linux-oem-6.5-XiW3QL/linux-oem-6.5-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:6810:36
[5.021429] index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]'
[5.022478] CPU: 2 PID: 153 Comm: kworker/u8:7 Not tainted 6.5.0-1004-oem 
#4-Ubuntu
[5.022483] Hardware name: Supermicro C7Q67/C7Q67, BIOS 2.1a 11/10/2015
[5.022486] Workqueue: fw_event_mpt2sas0 _firmware_event_work [mpt3sas]
[5.022533] Call Trace:
[5.022536]  
[5.022539]  dump_stack_lvl+0x48/0x70
[5.022547]  dump_stack+0x10/0x20
[5.022551]  __ubsan_handle_out_of_bounds+0xc6/0x110
[5.022559]  _scsih_sas_host_add+0x669/0x700 [mpt3sas]
[5.022597]  _mpt3sas_fw_work+0x753/0xbc0 [mpt3sas]
[5.022633]  ? raw_spin_rq_unlock+0x10/0x40
[5.022637]  ? finish_task_switch.isra.0+0x85/0x2a0
[5.022642]  ? __schedule+0x2d4/0x750
[5.022648]  _firmware_event_work+0x16/0x20 [mpt3sas]
[5.022681]  process_one_work+0x240/0x450
[5.022688]  worker_thread+0x50/0x3f0
[5.022693]  ? __pfx_worker_thread+0x10/0x10
[5.022698]  kthread+0xf2/0x120
[5.022704]  ? __pfx_kthread+0x10/0x10
[5.022710]  ret_from_fork+0x47/0x70
[5.022717]  ? __pfx_kthread+0x10/0x10
[5.022722]  ret_from_fork_asm+0x1b/0x30
[5.022728]  
[5.022729] 

[5.025642] mpt2sas_cm0: host_add: handle(0x0001), 
sas_addr(0x500062b0002d0050), phys(8)
[5.025919] 

[5.027158] UBSAN: array-index-out-of-bounds in 
/build/linux-oem-6.5-XiW3QL/linux-oem-6.5-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:6598:38
[5.029016] index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]'
[5.030064] CPU: 2 PID: 153 Comm: kworker/u8:7 Not tainted 6.5.0-1004-oem 
#4-Ubuntu
[5.030069] Hardware name: Supermicro C7Q67/C7Q67, BIOS 2.1a 11/10/2015
[5.030071] Workqueue: fw_event_mpt2sas0 _firmware_event_work [mpt3sas]
[5.030108] Call Trace:
[5.030110]  
[5.030113]  dump_stack_lvl+0x48/0x70
[5.030119]  dump_stack+0x10/0x20
[5.030123]  __ubsan_handle_out_of_bounds+0xc6/0x110

[Kernel-packages] [Bug 2039227] Re: Jammy update: v5.15.129 upstream stable release

[Kamal Mostafa]

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    v5.15.129 upstream stable release
+    from git://git.kernel.org/
  
-v5.15.129 upstream stable release
-from git://git.kernel.org/
+ NFSv4.2: fix error handling in nfs42_proc_getxattr
+ NFSv4: fix out path in __nfs4_get_acl_uncached
+ xprtrdma: Remap Receive buffers after a reconnect
+ PCI: acpiphp: Reassign resources on bridge if necessary
+ dlm: improve plock logging if interrupted
+ dlm: replace usage of found with dedicated list iterator variable
+ fs: dlm: add pid to debug log
+ fs: dlm: change plock interrupted message to debug again
+ fs: dlm: use dlm_plock_info for do_unlock_close
+ fs: dlm: fix mismatch of plock results from userspace
+ MIPS: cpu-features: Enable octeon_cache by cpu_type
+ MIPS: cpu-features: Use boot_cpu_type for CPU type based features
+ fbdev: Improve performance of sys_imageblit()
+ fbdev: Fix sys_imageblit() for arbitrary image widths
+ fbdev: fix potential OOB read in fast_imageblit()
+ ALSA: pcm: Fix potential data race at PCM memory allocation helpers
+ jbd2: remove t_checkpoint_io_list
+ jbd2: remove journal_clean_one_cp_list()
+ jbd2: fix a race when checking checkpoint buffer busy
+ can: raw: fix receiver memory leak
+ drm/amd/display: do not wait for mpc idle if tg is disabled
+ drm/amd/display: check TG is non-null before checking if enabled
+ can: raw: fix lockdep issue in raw_release()
+ tracing: Fix cpu buffers unavailable due to 'record_disabled' missed
+ tracing: Fix memleak due to race between current_tracer and trace
+ octeontx2-af: SDP: fix receive link config
+ sock: annotate data-races around prot->memory_pressure
+ dccp: annotate data-races in dccp_poll()
+ ipvlan: Fix a reference count leak warning in ipvlan_ns_exit()
+ net: bgmac: Fix return value check for fixed_phy_register()
+ net: bcmgenet: Fix return value check for fixed_phy_register()
+ net: validate veth and vxcan peer ifindexes
+ ice: fix receive buffer size miscalculation
+ igb: Avoid starting unnecessary workqueues
+ igc: Fix the typo in the PTM Control macro
+ net/sched: fix a qdisc modification with ambiguous command request
+ netfilter: nf_tables: flush pending destroy work before netlink notifier
+ netfilter: nf_tables: fix out of memory error handling
+ rtnetlink: return ENODEV when ifname does not exist and group is given
+ rtnetlink: Reject negative ifindexes in RTM_NEWLINK
+ net: remove bond_slave_has_mac_rcu()
+ bonding: fix macvlan over alb bond support
+ net/ncsi: make one oem_gma function for all mfr id
+ net/ncsi: change from ndo_set_mac_address to dev_set_mac_address
+ ibmveth: Use dcbf rather than dcbfl
+ NFSv4: Fix dropped lock for racing OPEN and delegation return
+ clk: Fix slab-out-of-bounds error in devm_clk_release()
+ ALSA: ymfpci: Fix the missing snd_card_free() call at probe error
+ mm: add a call to flush_cache_vmap() in vmap_pfn()
+ NFS: Fix a use after free in nfs_direct_join_group()
+ nfsd: Fix race to FREE_STATEID and cl_revoked
+ selinux: set next pointer before attaching to list
+ batman-adv: Trigger events for auto adjusted MTU
+ batman-adv: Don't increase MTU when set by user
+ batman-adv: Do not get eth header before batadv_check_management_packet
+ batman-adv: Fix TT global entry leak when client roamed back
+ batman-adv: Fix batadv_v_ogm_aggr_send memory leak
+ batman-adv: Hold rtnl lock during MTU update via netlink
+ lib/clz_ctz.c: Fix __clzdi2() and __ctzdi2() for 32-bit kernels
+ radix tree: remove unused variable
+ of: unittest: Fix EXPECT for parse_phandle_with_args_map() test
+ of: dynamic: Refactor action prints to not use "%pOF" inside devtree_lock
+ media: vcodec: Fix potential array out-of-bounds in encoder queue_setup
+ PCI: acpiphp: Use pci_assign_unassigned_bridge_resources() only for non-root 
bus
+ drm/vmwgfx: Fix shader stage validation
+ drm/display/dp: Fix the DP DSC Receiver cap size
+ x86/fpu: Invalidate FPU state correctly on exec()
+ nfs: use vfs setgid helper
+ nfsd: use vfs setgid helper
+ torture: Fix hang during kthread shutdown phase
+ cgroup/cpuset: Rename 

[Kernel-packages] [Bug 2039211] acpidump.txt

[Juan Pedro Paredes]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/2039211/+attachment/5708982/+files/acpidump.txt

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

Title:
  nf_nat and macvlan

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [114596.323853] [ cut here ]
  [114596.323855] WARNING: CPU: 1 PID: 46587 at net/netfilter/nf_nat_core.c:678 
nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323865] Modules linked in: tls xt_nat xt_tcpudp xt_conntrack 
nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat 
nf_tables nfnetlink br_netfilter rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd 
grace fscache netfs overlay macvlan bridge stp llc cfg80211 sunrpc binfmt_misc 
nls_iso8859_1 intel_rapl_msr intel_rapl_common hyperv_fb serio_raw joydev 
mac_hid hv_balloon vmgenid msr parport_pc ppdev lp dm_multipath parport 
efi_pstore dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear hyperv_drm drm_shmem_helper hid_generic 
drm_kms_helper hid_hyperv drm hid hv_storvsc hyperv_keyboard hv_netvsc 
scsi_transport_fc hv_utils crct10dif_pclmul crc32_pclmul polyval_clmulni 
polyval_generic ghash_clmulni_intel aesni_intel crypto_simd cryptd hv_vmbus
  [114596.323907] CPU: 1 PID: 46587 Comm: kworker/u4:3 Tainted: GB   W  
6.5.0-9-generic #9-Ubuntu
  [114596.323909] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
  [114596.323910] Workqueue: events_unbound macvlan_process_broadcast [macvlan]
  [114596.323914] RIP: 0010:nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323919] Code: 8b bb b0 00 00 00 48 83 c8 20 48 89 83 80 00 00 00 48 
85 ff 0f 84 d2 fe ff ff 0f b6 07 84 c0 0f 85 75 fe ff ff e9 bb fe ff ff <0f> 0b 
31 c0 e9 d2 fe ff ff ba 20 08 00 00 be 02 00 00 00 48 89 df
  [114596.323920] RSP: 0018:acc1ebd0 EFLAGS: 00010202
  [114596.323921] RAX: 0080 RBX: 9773847b0200 RCX: 

  [114596.323922] RDX:  RSI: acc1ec8c RDI: 
9773847b0200
  [114596.323923] RBP: acc1ec70 R08: 2d00a8c0 R09: 

  [114596.323924] R10:  R11:  R12: 

  [114596.323925] R13: 9075ec40 R14: acc1ec8c R15: 
9773847b0200
  [114596.323925] FS:  () GS:97737fb0() 
knlGS:
  [114596.323926] CS:  0010 DS:  ES:  CR0: 80050033
  [114596.323927] CR2: 2a8952d9d000 CR3: 44532000 CR4: 
00350ee0
  [114596.323929] Call Trace:
  [114596.323931]  
  [114596.323933]  ? show_regs+0x6d/0x80
  [114596.323936]  ? __warn+0x89/0x160
  [114596.323939]  ? nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323944]  ? report_bug+0x17e/0x1b0
  [114596.323947]  ? handle_bug+0x51/0xa0
  [114596.323950]  ? exc_invalid_op+0x18/0x80
  [114596.323952]  ? asm_exc_invalid_op+0x1b/0x20
  [114596.323955]  ? nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323959]  __nf_nat_alloc_null_binding+0x5e/0x90 [nf_nat]
  [114596.323963]  nf_nat_inet_fn+0x2da/0x350 [nf_nat]
  [114596.323967]  nf_nat_ipv4_local_in+0x59/0x140 [nf_nat]
  [114596.323971]  nf_hook_slow+0x43/0xd0
  [114596.323974]  ip_local_deliver+0xe1/0x120
  [114596.323977]  ? __pfx_ip_local_deliver_finish+0x10/0x10
  [114596.323978]  ip_rcv+0x175/0x190
  [114596.323980]  ? __pfx_ip_rcv_finish+0x10/0x10
  [114596.323982]  __netif_receive_skb_one_core+0x91/0xa0
  [114596.323985]  __netif_receive_skb+0x15/0x60
  [114596.323987]  process_backlog+0x8e/0x150
  [114596.323989]  __napi_poll+0x30/0x1f0
  [114596.323990]  net_rx_action+0x181/0x2e0
  [114596.323993]  __do_softirq+0xd6/0x346
  [114596.323995]  do_softirq.part.0+0x41/0x80
  [114596.323997]  
  [114596.323998]  
  [114596.323999]  __local_bh_enable_ip+0x72/0x80
  [114596.324001]  netif_rx+0xec/0x100
  [114596.324002]  macvlan_broadcast+0x102/0x1d0 [macvlan]
  [114596.324006]  macvlan_multicast_rx+0x66/0x80 [macvlan]
  [114596.324009]  macvlan_process_broadcast+0xe9/0x160 [macvlan]
  [114596.324012]  process_one_work+0x220/0x440
  [114596.324014]  worker_thread+0x4d/0x3f0
  [114596.324016]  ? _raw_spin_unlock_irqrestore+0x11/0x60
  [114596.324017]  ? __pfx_worker_thread+0x10/0x10
  [114596.324018]  kthread+0xef/0x120
  [114596.324021]  ? __pfx_kthread+0x10/0x10
  [114596.324022]  ret_from_fork+0x44/0x70
  [114596.324025]  ? __pfx_kthread+0x10/0x10
  [114596.324027]  ret_from_fork_asm+0x1b/0x30
  [114596.324029]  
  [114596.324029] ---[ end trace  ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  

[Kernel-packages] [Bug 2039211] WifiSyslog.txt

[Juan Pedro Paredes]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/2039211/+attachment/5708981/+files/WifiSyslog.txt

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

Title:
  nf_nat and macvlan

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [114596.323853] [ cut here ]
  [114596.323855] WARNING: CPU: 1 PID: 46587 at net/netfilter/nf_nat_core.c:678 
nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323865] Modules linked in: tls xt_nat xt_tcpudp xt_conntrack 
nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat 
nf_tables nfnetlink br_netfilter rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd 
grace fscache netfs overlay macvlan bridge stp llc cfg80211 sunrpc binfmt_misc 
nls_iso8859_1 intel_rapl_msr intel_rapl_common hyperv_fb serio_raw joydev 
mac_hid hv_balloon vmgenid msr parport_pc ppdev lp dm_multipath parport 
efi_pstore dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear hyperv_drm drm_shmem_helper hid_generic 
drm_kms_helper hid_hyperv drm hid hv_storvsc hyperv_keyboard hv_netvsc 
scsi_transport_fc hv_utils crct10dif_pclmul crc32_pclmul polyval_clmulni 
polyval_generic ghash_clmulni_intel aesni_intel crypto_simd cryptd hv_vmbus
  [114596.323907] CPU: 1 PID: 46587 Comm: kworker/u4:3 Tainted: GB   W  
6.5.0-9-generic #9-Ubuntu
  [114596.323909] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
  [114596.323910] Workqueue: events_unbound macvlan_process_broadcast [macvlan]
  [114596.323914] RIP: 0010:nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323919] Code: 8b bb b0 00 00 00 48 83 c8 20 48 89 83 80 00 00 00 48 
85 ff 0f 84 d2 fe ff ff 0f b6 07 84 c0 0f 85 75 fe ff ff e9 bb fe ff ff <0f> 0b 
31 c0 e9 d2 fe ff ff ba 20 08 00 00 be 02 00 00 00 48 89 df
  [114596.323920] RSP: 0018:acc1ebd0 EFLAGS: 00010202
  [114596.323921] RAX: 0080 RBX: 9773847b0200 RCX: 

  [114596.323922] RDX:  RSI: acc1ec8c RDI: 
9773847b0200
  [114596.323923] RBP: acc1ec70 R08: 2d00a8c0 R09: 

  [114596.323924] R10:  R11:  R12: 

  [114596.323925] R13: 9075ec40 R14: acc1ec8c R15: 
9773847b0200
  [114596.323925] FS:  () GS:97737fb0() 
knlGS:
  [114596.323926] CS:  0010 DS:  ES:  CR0: 80050033
  [114596.323927] CR2: 2a8952d9d000 CR3: 44532000 CR4: 
00350ee0
  [114596.323929] Call Trace:
  [114596.323931]  
  [114596.323933]  ? show_regs+0x6d/0x80
  [114596.323936]  ? __warn+0x89/0x160
  [114596.323939]  ? nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323944]  ? report_bug+0x17e/0x1b0
  [114596.323947]  ? handle_bug+0x51/0xa0
  [114596.323950]  ? exc_invalid_op+0x18/0x80
  [114596.323952]  ? asm_exc_invalid_op+0x1b/0x20
  [114596.323955]  ? nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323959]  __nf_nat_alloc_null_binding+0x5e/0x90 [nf_nat]
  [114596.323963]  nf_nat_inet_fn+0x2da/0x350 [nf_nat]
  [114596.323967]  nf_nat_ipv4_local_in+0x59/0x140 [nf_nat]
  [114596.323971]  nf_hook_slow+0x43/0xd0
  [114596.323974]  ip_local_deliver+0xe1/0x120
  [114596.323977]  ? __pfx_ip_local_deliver_finish+0x10/0x10
  [114596.323978]  ip_rcv+0x175/0x190
  [114596.323980]  ? __pfx_ip_rcv_finish+0x10/0x10
  [114596.323982]  __netif_receive_skb_one_core+0x91/0xa0
  [114596.323985]  __netif_receive_skb+0x15/0x60
  [114596.323987]  process_backlog+0x8e/0x150
  [114596.323989]  __napi_poll+0x30/0x1f0
  [114596.323990]  net_rx_action+0x181/0x2e0
  [114596.323993]  __do_softirq+0xd6/0x346
  [114596.323995]  do_softirq.part.0+0x41/0x80
  [114596.323997]  
  [114596.323998]  
  [114596.323999]  __local_bh_enable_ip+0x72/0x80
  [114596.324001]  netif_rx+0xec/0x100
  [114596.324002]  macvlan_broadcast+0x102/0x1d0 [macvlan]
  [114596.324006]  macvlan_multicast_rx+0x66/0x80 [macvlan]
  [114596.324009]  macvlan_process_broadcast+0xe9/0x160 [macvlan]
  [114596.324012]  process_one_work+0x220/0x440
  [114596.324014]  worker_thread+0x4d/0x3f0
  [114596.324016]  ? _raw_spin_unlock_irqrestore+0x11/0x60
  [114596.324017]  ? __pfx_worker_thread+0x10/0x10
  [114596.324018]  kthread+0xef/0x120
  [114596.324021]  ? __pfx_kthread+0x10/0x10
  [114596.324022]  ret_from_fork+0x44/0x70
  [114596.324025]  ? __pfx_kthread+0x10/0x10
  [114596.324027]  ret_from_fork_asm+0x1b/0x30
  [114596.324029]  
  [114596.324029] ---[ end trace  ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
 

[Kernel-packages] [Bug 2039211] UdevDb.txt

[Juan Pedro Paredes]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/2039211/+attachment/5708980/+files/UdevDb.txt

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

Title:
  nf_nat and macvlan

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [114596.323853] [ cut here ]
  [114596.323855] WARNING: CPU: 1 PID: 46587 at net/netfilter/nf_nat_core.c:678 
nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323865] Modules linked in: tls xt_nat xt_tcpudp xt_conntrack 
nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat 
nf_tables nfnetlink br_netfilter rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd 
grace fscache netfs overlay macvlan bridge stp llc cfg80211 sunrpc binfmt_misc 
nls_iso8859_1 intel_rapl_msr intel_rapl_common hyperv_fb serio_raw joydev 
mac_hid hv_balloon vmgenid msr parport_pc ppdev lp dm_multipath parport 
efi_pstore dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear hyperv_drm drm_shmem_helper hid_generic 
drm_kms_helper hid_hyperv drm hid hv_storvsc hyperv_keyboard hv_netvsc 
scsi_transport_fc hv_utils crct10dif_pclmul crc32_pclmul polyval_clmulni 
polyval_generic ghash_clmulni_intel aesni_intel crypto_simd cryptd hv_vmbus
  [114596.323907] CPU: 1 PID: 46587 Comm: kworker/u4:3 Tainted: GB   W  
6.5.0-9-generic #9-Ubuntu
  [114596.323909] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
  [114596.323910] Workqueue: events_unbound macvlan_process_broadcast [macvlan]
  [114596.323914] RIP: 0010:nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323919] Code: 8b bb b0 00 00 00 48 83 c8 20 48 89 83 80 00 00 00 48 
85 ff 0f 84 d2 fe ff ff 0f b6 07 84 c0 0f 85 75 fe ff ff e9 bb fe ff ff <0f> 0b 
31 c0 e9 d2 fe ff ff ba 20 08 00 00 be 02 00 00 00 48 89 df
  [114596.323920] RSP: 0018:acc1ebd0 EFLAGS: 00010202
  [114596.323921] RAX: 0080 RBX: 9773847b0200 RCX: 

  [114596.323922] RDX:  RSI: acc1ec8c RDI: 
9773847b0200
  [114596.323923] RBP: acc1ec70 R08: 2d00a8c0 R09: 

  [114596.323924] R10:  R11:  R12: 

  [114596.323925] R13: 9075ec40 R14: acc1ec8c R15: 
9773847b0200
  [114596.323925] FS:  () GS:97737fb0() 
knlGS:
  [114596.323926] CS:  0010 DS:  ES:  CR0: 80050033
  [114596.323927] CR2: 2a8952d9d000 CR3: 44532000 CR4: 
00350ee0
  [114596.323929] Call Trace:
  [114596.323931]  
  [114596.323933]  ? show_regs+0x6d/0x80
  [114596.323936]  ? __warn+0x89/0x160
  [114596.323939]  ? nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323944]  ? report_bug+0x17e/0x1b0
  [114596.323947]  ? handle_bug+0x51/0xa0
  [114596.323950]  ? exc_invalid_op+0x18/0x80
  [114596.323952]  ? asm_exc_invalid_op+0x1b/0x20
  [114596.323955]  ? nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323959]  __nf_nat_alloc_null_binding+0x5e/0x90 [nf_nat]
  [114596.323963]  nf_nat_inet_fn+0x2da/0x350 [nf_nat]
  [114596.323967]  nf_nat_ipv4_local_in+0x59/0x140 [nf_nat]
  [114596.323971]  nf_hook_slow+0x43/0xd0
  [114596.323974]  ip_local_deliver+0xe1/0x120
  [114596.323977]  ? __pfx_ip_local_deliver_finish+0x10/0x10
  [114596.323978]  ip_rcv+0x175/0x190
  [114596.323980]  ? __pfx_ip_rcv_finish+0x10/0x10
  [114596.323982]  __netif_receive_skb_one_core+0x91/0xa0
  [114596.323985]  __netif_receive_skb+0x15/0x60
  [114596.323987]  process_backlog+0x8e/0x150
  [114596.323989]  __napi_poll+0x30/0x1f0
  [114596.323990]  net_rx_action+0x181/0x2e0
  [114596.323993]  __do_softirq+0xd6/0x346
  [114596.323995]  do_softirq.part.0+0x41/0x80
  [114596.323997]  
  [114596.323998]  
  [114596.323999]  __local_bh_enable_ip+0x72/0x80
  [114596.324001]  netif_rx+0xec/0x100
  [114596.324002]  macvlan_broadcast+0x102/0x1d0 [macvlan]
  [114596.324006]  macvlan_multicast_rx+0x66/0x80 [macvlan]
  [114596.324009]  macvlan_process_broadcast+0xe9/0x160 [macvlan]
  [114596.324012]  process_one_work+0x220/0x440
  [114596.324014]  worker_thread+0x4d/0x3f0
  [114596.324016]  ? _raw_spin_unlock_irqrestore+0x11/0x60
  [114596.324017]  ? __pfx_worker_thread+0x10/0x10
  [114596.324018]  kthread+0xef/0x120
  [114596.324021]  ? __pfx_kthread+0x10/0x10
  [114596.324022]  ret_from_fork+0x44/0x70
  [114596.324025]  ? __pfx_kthread+0x10/0x10
  [114596.324027]  ret_from_fork_asm+0x1b/0x30
  [114596.324029]  
  [114596.324029] ---[ end trace  ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  

[Kernel-packages] [Bug 2039211] ProcModules.txt

[Juan Pedro Paredes]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/2039211/+attachment/5708979/+files/ProcModules.txt

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

Title:
  nf_nat and macvlan

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [114596.323853] [ cut here ]
  [114596.323855] WARNING: CPU: 1 PID: 46587 at net/netfilter/nf_nat_core.c:678 
nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323865] Modules linked in: tls xt_nat xt_tcpudp xt_conntrack 
nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat 
nf_tables nfnetlink br_netfilter rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd 
grace fscache netfs overlay macvlan bridge stp llc cfg80211 sunrpc binfmt_misc 
nls_iso8859_1 intel_rapl_msr intel_rapl_common hyperv_fb serio_raw joydev 
mac_hid hv_balloon vmgenid msr parport_pc ppdev lp dm_multipath parport 
efi_pstore dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear hyperv_drm drm_shmem_helper hid_generic 
drm_kms_helper hid_hyperv drm hid hv_storvsc hyperv_keyboard hv_netvsc 
scsi_transport_fc hv_utils crct10dif_pclmul crc32_pclmul polyval_clmulni 
polyval_generic ghash_clmulni_intel aesni_intel crypto_simd cryptd hv_vmbus
  [114596.323907] CPU: 1 PID: 46587 Comm: kworker/u4:3 Tainted: GB   W  
6.5.0-9-generic #9-Ubuntu
  [114596.323909] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
  [114596.323910] Workqueue: events_unbound macvlan_process_broadcast [macvlan]
  [114596.323914] RIP: 0010:nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323919] Code: 8b bb b0 00 00 00 48 83 c8 20 48 89 83 80 00 00 00 48 
85 ff 0f 84 d2 fe ff ff 0f b6 07 84 c0 0f 85 75 fe ff ff e9 bb fe ff ff <0f> 0b 
31 c0 e9 d2 fe ff ff ba 20 08 00 00 be 02 00 00 00 48 89 df
  [114596.323920] RSP: 0018:acc1ebd0 EFLAGS: 00010202
  [114596.323921] RAX: 0080 RBX: 9773847b0200 RCX: 

  [114596.323922] RDX:  RSI: acc1ec8c RDI: 
9773847b0200
  [114596.323923] RBP: acc1ec70 R08: 2d00a8c0 R09: 

  [114596.323924] R10:  R11:  R12: 

  [114596.323925] R13: 9075ec40 R14: acc1ec8c R15: 
9773847b0200
  [114596.323925] FS:  () GS:97737fb0() 
knlGS:
  [114596.323926] CS:  0010 DS:  ES:  CR0: 80050033
  [114596.323927] CR2: 2a8952d9d000 CR3: 44532000 CR4: 
00350ee0
  [114596.323929] Call Trace:
  [114596.323931]  
  [114596.323933]  ? show_regs+0x6d/0x80
  [114596.323936]  ? __warn+0x89/0x160
  [114596.323939]  ? nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323944]  ? report_bug+0x17e/0x1b0
  [114596.323947]  ? handle_bug+0x51/0xa0
  [114596.323950]  ? exc_invalid_op+0x18/0x80
  [114596.323952]  ? asm_exc_invalid_op+0x1b/0x20
  [114596.323955]  ? nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323959]  __nf_nat_alloc_null_binding+0x5e/0x90 [nf_nat]
  [114596.323963]  nf_nat_inet_fn+0x2da/0x350 [nf_nat]
  [114596.323967]  nf_nat_ipv4_local_in+0x59/0x140 [nf_nat]
  [114596.323971]  nf_hook_slow+0x43/0xd0
  [114596.323974]  ip_local_deliver+0xe1/0x120
  [114596.323977]  ? __pfx_ip_local_deliver_finish+0x10/0x10
  [114596.323978]  ip_rcv+0x175/0x190
  [114596.323980]  ? __pfx_ip_rcv_finish+0x10/0x10
  [114596.323982]  __netif_receive_skb_one_core+0x91/0xa0
  [114596.323985]  __netif_receive_skb+0x15/0x60
  [114596.323987]  process_backlog+0x8e/0x150
  [114596.323989]  __napi_poll+0x30/0x1f0
  [114596.323990]  net_rx_action+0x181/0x2e0
  [114596.323993]  __do_softirq+0xd6/0x346
  [114596.323995]  do_softirq.part.0+0x41/0x80
  [114596.323997]  
  [114596.323998]  
  [114596.323999]  __local_bh_enable_ip+0x72/0x80
  [114596.324001]  netif_rx+0xec/0x100
  [114596.324002]  macvlan_broadcast+0x102/0x1d0 [macvlan]
  [114596.324006]  macvlan_multicast_rx+0x66/0x80 [macvlan]
  [114596.324009]  macvlan_process_broadcast+0xe9/0x160 [macvlan]
  [114596.324012]  process_one_work+0x220/0x440
  [114596.324014]  worker_thread+0x4d/0x3f0
  [114596.324016]  ? _raw_spin_unlock_irqrestore+0x11/0x60
  [114596.324017]  ? __pfx_worker_thread+0x10/0x10
  [114596.324018]  kthread+0xef/0x120
  [114596.324021]  ? __pfx_kthread+0x10/0x10
  [114596.324022]  ret_from_fork+0x44/0x70
  [114596.324025]  ? __pfx_kthread+0x10/0x10
  [114596.324027]  ret_from_fork_asm+0x1b/0x30
  [114596.324029]  
  [114596.324029] ---[ end trace  ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 

[Kernel-packages] [Bug 2039211] ProcCpuinfoMinimal.txt

[Juan Pedro Paredes]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2039211/+attachment/5708977/+files/ProcCpuinfoMinimal.txt

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

Title:
  nf_nat and macvlan

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [114596.323853] [ cut here ]
  [114596.323855] WARNING: CPU: 1 PID: 46587 at net/netfilter/nf_nat_core.c:678 
nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323865] Modules linked in: tls xt_nat xt_tcpudp xt_conntrack 
nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat 
nf_tables nfnetlink br_netfilter rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd 
grace fscache netfs overlay macvlan bridge stp llc cfg80211 sunrpc binfmt_misc 
nls_iso8859_1 intel_rapl_msr intel_rapl_common hyperv_fb serio_raw joydev 
mac_hid hv_balloon vmgenid msr parport_pc ppdev lp dm_multipath parport 
efi_pstore dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear hyperv_drm drm_shmem_helper hid_generic 
drm_kms_helper hid_hyperv drm hid hv_storvsc hyperv_keyboard hv_netvsc 
scsi_transport_fc hv_utils crct10dif_pclmul crc32_pclmul polyval_clmulni 
polyval_generic ghash_clmulni_intel aesni_intel crypto_simd cryptd hv_vmbus
  [114596.323907] CPU: 1 PID: 46587 Comm: kworker/u4:3 Tainted: GB   W  
6.5.0-9-generic #9-Ubuntu
  [114596.323909] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
  [114596.323910] Workqueue: events_unbound macvlan_process_broadcast [macvlan]
  [114596.323914] RIP: 0010:nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323919] Code: 8b bb b0 00 00 00 48 83 c8 20 48 89 83 80 00 00 00 48 
85 ff 0f 84 d2 fe ff ff 0f b6 07 84 c0 0f 85 75 fe ff ff e9 bb fe ff ff <0f> 0b 
31 c0 e9 d2 fe ff ff ba 20 08 00 00 be 02 00 00 00 48 89 df
  [114596.323920] RSP: 0018:acc1ebd0 EFLAGS: 00010202
  [114596.323921] RAX: 0080 RBX: 9773847b0200 RCX: 

  [114596.323922] RDX:  RSI: acc1ec8c RDI: 
9773847b0200
  [114596.323923] RBP: acc1ec70 R08: 2d00a8c0 R09: 

  [114596.323924] R10:  R11:  R12: 

  [114596.323925] R13: 9075ec40 R14: acc1ec8c R15: 
9773847b0200
  [114596.323925] FS:  () GS:97737fb0() 
knlGS:
  [114596.323926] CS:  0010 DS:  ES:  CR0: 80050033
  [114596.323927] CR2: 2a8952d9d000 CR3: 44532000 CR4: 
00350ee0
  [114596.323929] Call Trace:
  [114596.323931]  
  [114596.323933]  ? show_regs+0x6d/0x80
  [114596.323936]  ? __warn+0x89/0x160
  [114596.323939]  ? nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323944]  ? report_bug+0x17e/0x1b0
  [114596.323947]  ? handle_bug+0x51/0xa0
  [114596.323950]  ? exc_invalid_op+0x18/0x80
  [114596.323952]  ? asm_exc_invalid_op+0x1b/0x20
  [114596.323955]  ? nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323959]  __nf_nat_alloc_null_binding+0x5e/0x90 [nf_nat]
  [114596.323963]  nf_nat_inet_fn+0x2da/0x350 [nf_nat]
  [114596.323967]  nf_nat_ipv4_local_in+0x59/0x140 [nf_nat]
  [114596.323971]  nf_hook_slow+0x43/0xd0
  [114596.323974]  ip_local_deliver+0xe1/0x120
  [114596.323977]  ? __pfx_ip_local_deliver_finish+0x10/0x10
  [114596.323978]  ip_rcv+0x175/0x190
  [114596.323980]  ? __pfx_ip_rcv_finish+0x10/0x10
  [114596.323982]  __netif_receive_skb_one_core+0x91/0xa0
  [114596.323985]  __netif_receive_skb+0x15/0x60
  [114596.323987]  process_backlog+0x8e/0x150
  [114596.323989]  __napi_poll+0x30/0x1f0
  [114596.323990]  net_rx_action+0x181/0x2e0
  [114596.323993]  __do_softirq+0xd6/0x346
  [114596.323995]  do_softirq.part.0+0x41/0x80
  [114596.323997]  
  [114596.323998]  
  [114596.323999]  __local_bh_enable_ip+0x72/0x80
  [114596.324001]  netif_rx+0xec/0x100
  [114596.324002]  macvlan_broadcast+0x102/0x1d0 [macvlan]
  [114596.324006]  macvlan_multicast_rx+0x66/0x80 [macvlan]
  [114596.324009]  macvlan_process_broadcast+0xe9/0x160 [macvlan]
  [114596.324012]  process_one_work+0x220/0x440
  [114596.324014]  worker_thread+0x4d/0x3f0
  [114596.324016]  ? _raw_spin_unlock_irqrestore+0x11/0x60
  [114596.324017]  ? __pfx_worker_thread+0x10/0x10
  [114596.324018]  kthread+0xef/0x120
  [114596.324021]  ? __pfx_kthread+0x10/0x10
  [114596.324022]  ret_from_fork+0x44/0x70
  [114596.324025]  ? __pfx_kthread+0x10/0x10
  [114596.324027]  ret_from_fork_asm+0x1b/0x30
  [114596.324029]  
  [114596.324029] ---[ end trace  ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: 

[Kernel-packages] [Bug 2039211] PaInfo.txt

[Juan Pedro Paredes]

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/2039211/+attachment/5708975/+files/PaInfo.txt

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

Title:
  nf_nat and macvlan

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [114596.323853] [ cut here ]
  [114596.323855] WARNING: CPU: 1 PID: 46587 at net/netfilter/nf_nat_core.c:678 
nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323865] Modules linked in: tls xt_nat xt_tcpudp xt_conntrack 
nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat 
nf_tables nfnetlink br_netfilter rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd 
grace fscache netfs overlay macvlan bridge stp llc cfg80211 sunrpc binfmt_misc 
nls_iso8859_1 intel_rapl_msr intel_rapl_common hyperv_fb serio_raw joydev 
mac_hid hv_balloon vmgenid msr parport_pc ppdev lp dm_multipath parport 
efi_pstore dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear hyperv_drm drm_shmem_helper hid_generic 
drm_kms_helper hid_hyperv drm hid hv_storvsc hyperv_keyboard hv_netvsc 
scsi_transport_fc hv_utils crct10dif_pclmul crc32_pclmul polyval_clmulni 
polyval_generic ghash_clmulni_intel aesni_intel crypto_simd cryptd hv_vmbus
  [114596.323907] CPU: 1 PID: 46587 Comm: kworker/u4:3 Tainted: GB   W  
6.5.0-9-generic #9-Ubuntu
  [114596.323909] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
  [114596.323910] Workqueue: events_unbound macvlan_process_broadcast [macvlan]
  [114596.323914] RIP: 0010:nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323919] Code: 8b bb b0 00 00 00 48 83 c8 20 48 89 83 80 00 00 00 48 
85 ff 0f 84 d2 fe ff ff 0f b6 07 84 c0 0f 85 75 fe ff ff e9 bb fe ff ff <0f> 0b 
31 c0 e9 d2 fe ff ff ba 20 08 00 00 be 02 00 00 00 48 89 df
  [114596.323920] RSP: 0018:acc1ebd0 EFLAGS: 00010202
  [114596.323921] RAX: 0080 RBX: 9773847b0200 RCX: 

  [114596.323922] RDX:  RSI: acc1ec8c RDI: 
9773847b0200
  [114596.323923] RBP: acc1ec70 R08: 2d00a8c0 R09: 

  [114596.323924] R10:  R11:  R12: 

  [114596.323925] R13: 9075ec40 R14: acc1ec8c R15: 
9773847b0200
  [114596.323925] FS:  () GS:97737fb0() 
knlGS:
  [114596.323926] CS:  0010 DS:  ES:  CR0: 80050033
  [114596.323927] CR2: 2a8952d9d000 CR3: 44532000 CR4: 
00350ee0
  [114596.323929] Call Trace:
  [114596.323931]  
  [114596.323933]  ? show_regs+0x6d/0x80
  [114596.323936]  ? __warn+0x89/0x160
  [114596.323939]  ? nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323944]  ? report_bug+0x17e/0x1b0
  [114596.323947]  ? handle_bug+0x51/0xa0
  [114596.323950]  ? exc_invalid_op+0x18/0x80
  [114596.323952]  ? asm_exc_invalid_op+0x1b/0x20
  [114596.323955]  ? nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323959]  __nf_nat_alloc_null_binding+0x5e/0x90 [nf_nat]
  [114596.323963]  nf_nat_inet_fn+0x2da/0x350 [nf_nat]
  [114596.323967]  nf_nat_ipv4_local_in+0x59/0x140 [nf_nat]
  [114596.323971]  nf_hook_slow+0x43/0xd0
  [114596.323974]  ip_local_deliver+0xe1/0x120
  [114596.323977]  ? __pfx_ip_local_deliver_finish+0x10/0x10
  [114596.323978]  ip_rcv+0x175/0x190
  [114596.323980]  ? __pfx_ip_rcv_finish+0x10/0x10
  [114596.323982]  __netif_receive_skb_one_core+0x91/0xa0
  [114596.323985]  __netif_receive_skb+0x15/0x60
  [114596.323987]  process_backlog+0x8e/0x150
  [114596.323989]  __napi_poll+0x30/0x1f0
  [114596.323990]  net_rx_action+0x181/0x2e0
  [114596.323993]  __do_softirq+0xd6/0x346
  [114596.323995]  do_softirq.part.0+0x41/0x80
  [114596.323997]  
  [114596.323998]  
  [114596.323999]  __local_bh_enable_ip+0x72/0x80
  [114596.324001]  netif_rx+0xec/0x100
  [114596.324002]  macvlan_broadcast+0x102/0x1d0 [macvlan]
  [114596.324006]  macvlan_multicast_rx+0x66/0x80 [macvlan]
  [114596.324009]  macvlan_process_broadcast+0xe9/0x160 [macvlan]
  [114596.324012]  process_one_work+0x220/0x440
  [114596.324014]  worker_thread+0x4d/0x3f0
  [114596.324016]  ? _raw_spin_unlock_irqrestore+0x11/0x60
  [114596.324017]  ? __pfx_worker_thread+0x10/0x10
  [114596.324018]  kthread+0xef/0x120
  [114596.324021]  ? __pfx_kthread+0x10/0x10
  [114596.324022]  ret_from_fork+0x44/0x70
  [114596.324025]  ? __pfx_kthread+0x10/0x10
  [114596.324027]  ret_from_fork_asm+0x1b/0x30
  [114596.324029]  
  [114596.324029] ---[ end trace  ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  

[Kernel-packages] [Bug 2039211] ProcInterrupts.txt

[Juan Pedro Paredes]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/2039211/+attachment/5708978/+files/ProcInterrupts.txt

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

Title:
  nf_nat and macvlan

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [114596.323853] [ cut here ]
  [114596.323855] WARNING: CPU: 1 PID: 46587 at net/netfilter/nf_nat_core.c:678 
nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323865] Modules linked in: tls xt_nat xt_tcpudp xt_conntrack 
nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat 
nf_tables nfnetlink br_netfilter rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd 
grace fscache netfs overlay macvlan bridge stp llc cfg80211 sunrpc binfmt_misc 
nls_iso8859_1 intel_rapl_msr intel_rapl_common hyperv_fb serio_raw joydev 
mac_hid hv_balloon vmgenid msr parport_pc ppdev lp dm_multipath parport 
efi_pstore dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear hyperv_drm drm_shmem_helper hid_generic 
drm_kms_helper hid_hyperv drm hid hv_storvsc hyperv_keyboard hv_netvsc 
scsi_transport_fc hv_utils crct10dif_pclmul crc32_pclmul polyval_clmulni 
polyval_generic ghash_clmulni_intel aesni_intel crypto_simd cryptd hv_vmbus
  [114596.323907] CPU: 1 PID: 46587 Comm: kworker/u4:3 Tainted: GB   W  
6.5.0-9-generic #9-Ubuntu
  [114596.323909] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
  [114596.323910] Workqueue: events_unbound macvlan_process_broadcast [macvlan]
  [114596.323914] RIP: 0010:nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323919] Code: 8b bb b0 00 00 00 48 83 c8 20 48 89 83 80 00 00 00 48 
85 ff 0f 84 d2 fe ff ff 0f b6 07 84 c0 0f 85 75 fe ff ff e9 bb fe ff ff <0f> 0b 
31 c0 e9 d2 fe ff ff ba 20 08 00 00 be 02 00 00 00 48 89 df
  [114596.323920] RSP: 0018:acc1ebd0 EFLAGS: 00010202
  [114596.323921] RAX: 0080 RBX: 9773847b0200 RCX: 

  [114596.323922] RDX:  RSI: acc1ec8c RDI: 
9773847b0200
  [114596.323923] RBP: acc1ec70 R08: 2d00a8c0 R09: 

  [114596.323924] R10:  R11:  R12: 

  [114596.323925] R13: 9075ec40 R14: acc1ec8c R15: 
9773847b0200
  [114596.323925] FS:  () GS:97737fb0() 
knlGS:
  [114596.323926] CS:  0010 DS:  ES:  CR0: 80050033
  [114596.323927] CR2: 2a8952d9d000 CR3: 44532000 CR4: 
00350ee0
  [114596.323929] Call Trace:
  [114596.323931]  
  [114596.323933]  ? show_regs+0x6d/0x80
  [114596.323936]  ? __warn+0x89/0x160
  [114596.323939]  ? nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323944]  ? report_bug+0x17e/0x1b0
  [114596.323947]  ? handle_bug+0x51/0xa0
  [114596.323950]  ? exc_invalid_op+0x18/0x80
  [114596.323952]  ? asm_exc_invalid_op+0x1b/0x20
  [114596.323955]  ? nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323959]  __nf_nat_alloc_null_binding+0x5e/0x90 [nf_nat]
  [114596.323963]  nf_nat_inet_fn+0x2da/0x350 [nf_nat]
  [114596.323967]  nf_nat_ipv4_local_in+0x59/0x140 [nf_nat]
  [114596.323971]  nf_hook_slow+0x43/0xd0
  [114596.323974]  ip_local_deliver+0xe1/0x120
  [114596.323977]  ? __pfx_ip_local_deliver_finish+0x10/0x10
  [114596.323978]  ip_rcv+0x175/0x190
  [114596.323980]  ? __pfx_ip_rcv_finish+0x10/0x10
  [114596.323982]  __netif_receive_skb_one_core+0x91/0xa0
  [114596.323985]  __netif_receive_skb+0x15/0x60
  [114596.323987]  process_backlog+0x8e/0x150
  [114596.323989]  __napi_poll+0x30/0x1f0
  [114596.323990]  net_rx_action+0x181/0x2e0
  [114596.323993]  __do_softirq+0xd6/0x346
  [114596.323995]  do_softirq.part.0+0x41/0x80
  [114596.323997]  
  [114596.323998]  
  [114596.323999]  __local_bh_enable_ip+0x72/0x80
  [114596.324001]  netif_rx+0xec/0x100
  [114596.324002]  macvlan_broadcast+0x102/0x1d0 [macvlan]
  [114596.324006]  macvlan_multicast_rx+0x66/0x80 [macvlan]
  [114596.324009]  macvlan_process_broadcast+0xe9/0x160 [macvlan]
  [114596.324012]  process_one_work+0x220/0x440
  [114596.324014]  worker_thread+0x4d/0x3f0
  [114596.324016]  ? _raw_spin_unlock_irqrestore+0x11/0x60
  [114596.324017]  ? __pfx_worker_thread+0x10/0x10
  [114596.324018]  kthread+0xef/0x120
  [114596.324021]  ? __pfx_kthread+0x10/0x10
  [114596.324022]  ret_from_fork+0x44/0x70
  [114596.324025]  ? __pfx_kthread+0x10/0x10
  [114596.324027]  ret_from_fork_asm+0x1b/0x30
  [114596.324029]  
  [114596.324029] ---[ end trace  ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 

[Kernel-packages] [Bug 2039211] ProcCpuinfo.txt

[Juan Pedro Paredes]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/2039211/+attachment/5708976/+files/ProcCpuinfo.txt

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

Title:
  nf_nat and macvlan

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [114596.323853] [ cut here ]
  [114596.323855] WARNING: CPU: 1 PID: 46587 at net/netfilter/nf_nat_core.c:678 
nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323865] Modules linked in: tls xt_nat xt_tcpudp xt_conntrack 
nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat 
nf_tables nfnetlink br_netfilter rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd 
grace fscache netfs overlay macvlan bridge stp llc cfg80211 sunrpc binfmt_misc 
nls_iso8859_1 intel_rapl_msr intel_rapl_common hyperv_fb serio_raw joydev 
mac_hid hv_balloon vmgenid msr parport_pc ppdev lp dm_multipath parport 
efi_pstore dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear hyperv_drm drm_shmem_helper hid_generic 
drm_kms_helper hid_hyperv drm hid hv_storvsc hyperv_keyboard hv_netvsc 
scsi_transport_fc hv_utils crct10dif_pclmul crc32_pclmul polyval_clmulni 
polyval_generic ghash_clmulni_intel aesni_intel crypto_simd cryptd hv_vmbus
  [114596.323907] CPU: 1 PID: 46587 Comm: kworker/u4:3 Tainted: GB   W  
6.5.0-9-generic #9-Ubuntu
  [114596.323909] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
  [114596.323910] Workqueue: events_unbound macvlan_process_broadcast [macvlan]
  [114596.323914] RIP: 0010:nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323919] Code: 8b bb b0 00 00 00 48 83 c8 20 48 89 83 80 00 00 00 48 
85 ff 0f 84 d2 fe ff ff 0f b6 07 84 c0 0f 85 75 fe ff ff e9 bb fe ff ff <0f> 0b 
31 c0 e9 d2 fe ff ff ba 20 08 00 00 be 02 00 00 00 48 89 df
  [114596.323920] RSP: 0018:acc1ebd0 EFLAGS: 00010202
  [114596.323921] RAX: 0080 RBX: 9773847b0200 RCX: 

  [114596.323922] RDX:  RSI: acc1ec8c RDI: 
9773847b0200
  [114596.323923] RBP: acc1ec70 R08: 2d00a8c0 R09: 

  [114596.323924] R10:  R11:  R12: 

  [114596.323925] R13: 9075ec40 R14: acc1ec8c R15: 
9773847b0200
  [114596.323925] FS:  () GS:97737fb0() 
knlGS:
  [114596.323926] CS:  0010 DS:  ES:  CR0: 80050033
  [114596.323927] CR2: 2a8952d9d000 CR3: 44532000 CR4: 
00350ee0
  [114596.323929] Call Trace:
  [114596.323931]  
  [114596.323933]  ? show_regs+0x6d/0x80
  [114596.323936]  ? __warn+0x89/0x160
  [114596.323939]  ? nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323944]  ? report_bug+0x17e/0x1b0
  [114596.323947]  ? handle_bug+0x51/0xa0
  [114596.323950]  ? exc_invalid_op+0x18/0x80
  [114596.323952]  ? asm_exc_invalid_op+0x1b/0x20
  [114596.323955]  ? nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323959]  __nf_nat_alloc_null_binding+0x5e/0x90 [nf_nat]
  [114596.323963]  nf_nat_inet_fn+0x2da/0x350 [nf_nat]
  [114596.323967]  nf_nat_ipv4_local_in+0x59/0x140 [nf_nat]
  [114596.323971]  nf_hook_slow+0x43/0xd0
  [114596.323974]  ip_local_deliver+0xe1/0x120
  [114596.323977]  ? __pfx_ip_local_deliver_finish+0x10/0x10
  [114596.323978]  ip_rcv+0x175/0x190
  [114596.323980]  ? __pfx_ip_rcv_finish+0x10/0x10
  [114596.323982]  __netif_receive_skb_one_core+0x91/0xa0
  [114596.323985]  __netif_receive_skb+0x15/0x60
  [114596.323987]  process_backlog+0x8e/0x150
  [114596.323989]  __napi_poll+0x30/0x1f0
  [114596.323990]  net_rx_action+0x181/0x2e0
  [114596.323993]  __do_softirq+0xd6/0x346
  [114596.323995]  do_softirq.part.0+0x41/0x80
  [114596.323997]  
  [114596.323998]  
  [114596.323999]  __local_bh_enable_ip+0x72/0x80
  [114596.324001]  netif_rx+0xec/0x100
  [114596.324002]  macvlan_broadcast+0x102/0x1d0 [macvlan]
  [114596.324006]  macvlan_multicast_rx+0x66/0x80 [macvlan]
  [114596.324009]  macvlan_process_broadcast+0xe9/0x160 [macvlan]
  [114596.324012]  process_one_work+0x220/0x440
  [114596.324014]  worker_thread+0x4d/0x3f0
  [114596.324016]  ? _raw_spin_unlock_irqrestore+0x11/0x60
  [114596.324017]  ? __pfx_worker_thread+0x10/0x10
  [114596.324018]  kthread+0xef/0x120
  [114596.324021]  ? __pfx_kthread+0x10/0x10
  [114596.324022]  ret_from_fork+0x44/0x70
  [114596.324025]  ? __pfx_kthread+0x10/0x10
  [114596.324027]  ret_from_fork_asm+0x1b/0x30
  [114596.324029]  
  [114596.324029] ---[ end trace  ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 

[Kernel-packages] [Bug 2039227] Re: Jammy update: v5.15.129 upstream stable release

[Kamal Mostafa]

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

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

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

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

Title:
  Jammy update: v5.15.129 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress

Bug description:
  
  SRU Justification

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

 v5.15.129 upstream stable release
 from git://git.kernel.org/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039227/+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 2039211] Re: nf_nat and macvlan

[Juan Pedro Paredes]

apport information

** Tags added: apport-collected

** Description changed:

  [114596.323853] [ cut here ]
  [114596.323855] WARNING: CPU: 1 PID: 46587 at net/netfilter/nf_nat_core.c:678 
nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323865] Modules linked in: tls xt_nat xt_tcpudp xt_conntrack 
nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat 
nf_tables nfnetlink br_netfilter rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd 
grace fscache netfs overlay macvlan bridge stp llc cfg80211 sunrpc binfmt_misc 
nls_iso8859_1 intel_rapl_msr intel_rapl_common hyperv_fb serio_raw joydev 
mac_hid hv_balloon vmgenid msr parport_pc ppdev lp dm_multipath parport 
efi_pstore dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear hyperv_drm drm_shmem_helper hid_generic 
drm_kms_helper hid_hyperv drm hid hv_storvsc hyperv_keyboard hv_netvsc 
scsi_transport_fc hv_utils crct10dif_pclmul crc32_pclmul polyval_clmulni 
polyval_generic ghash_clmulni_intel aesni_intel crypto_simd cryptd hv_vmbus
  [114596.323907] CPU: 1 PID: 46587 Comm: kworker/u4:3 Tainted: GB   W  
6.5.0-9-generic #9-Ubuntu
  [114596.323909] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
  [114596.323910] Workqueue: events_unbound macvlan_process_broadcast [macvlan]
  [114596.323914] RIP: 0010:nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323919] Code: 8b bb b0 00 00 00 48 83 c8 20 48 89 83 80 00 00 00 48 
85 ff 0f 84 d2 fe ff ff 0f b6 07 84 c0 0f 85 75 fe ff ff e9 bb fe ff ff <0f> 0b 
31 c0 e9 d2 fe ff ff ba 20 08 00 00 be 02 00 00 00 48 89 df
  [114596.323920] RSP: 0018:acc1ebd0 EFLAGS: 00010202
  [114596.323921] RAX: 0080 RBX: 9773847b0200 RCX: 

  [114596.323922] RDX:  RSI: acc1ec8c RDI: 
9773847b0200
  [114596.323923] RBP: acc1ec70 R08: 2d00a8c0 R09: 

  [114596.323924] R10:  R11:  R12: 

  [114596.323925] R13: 9075ec40 R14: acc1ec8c R15: 
9773847b0200
  [114596.323925] FS:  () GS:97737fb0() 
knlGS:
  [114596.323926] CS:  0010 DS:  ES:  CR0: 80050033
  [114596.323927] CR2: 2a8952d9d000 CR3: 44532000 CR4: 
00350ee0
  [114596.323929] Call Trace:
  [114596.323931]  
  [114596.323933]  ? show_regs+0x6d/0x80
  [114596.323936]  ? __warn+0x89/0x160
  [114596.323939]  ? nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323944]  ? report_bug+0x17e/0x1b0
  [114596.323947]  ? handle_bug+0x51/0xa0
  [114596.323950]  ? exc_invalid_op+0x18/0x80
  [114596.323952]  ? asm_exc_invalid_op+0x1b/0x20
  [114596.323955]  ? nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323959]  __nf_nat_alloc_null_binding+0x5e/0x90 [nf_nat]
  [114596.323963]  nf_nat_inet_fn+0x2da/0x350 [nf_nat]
  [114596.323967]  nf_nat_ipv4_local_in+0x59/0x140 [nf_nat]
  [114596.323971]  nf_hook_slow+0x43/0xd0
  [114596.323974]  ip_local_deliver+0xe1/0x120
  [114596.323977]  ? __pfx_ip_local_deliver_finish+0x10/0x10
  [114596.323978]  ip_rcv+0x175/0x190
  [114596.323980]  ? __pfx_ip_rcv_finish+0x10/0x10
  [114596.323982]  __netif_receive_skb_one_core+0x91/0xa0
  [114596.323985]  __netif_receive_skb+0x15/0x60
  [114596.323987]  process_backlog+0x8e/0x150
  [114596.323989]  __napi_poll+0x30/0x1f0
  [114596.323990]  net_rx_action+0x181/0x2e0
  [114596.323993]  __do_softirq+0xd6/0x346
  [114596.323995]  do_softirq.part.0+0x41/0x80
  [114596.323997]  
  [114596.323998]  
  [114596.323999]  __local_bh_enable_ip+0x72/0x80
  [114596.324001]  netif_rx+0xec/0x100
  [114596.324002]  macvlan_broadcast+0x102/0x1d0 [macvlan]
  [114596.324006]  macvlan_multicast_rx+0x66/0x80 [macvlan]
  [114596.324009]  macvlan_process_broadcast+0xe9/0x160 [macvlan]
  [114596.324012]  process_one_work+0x220/0x440
  [114596.324014]  worker_thread+0x4d/0x3f0
  [114596.324016]  ? _raw_spin_unlock_irqrestore+0x11/0x60
  [114596.324017]  ? __pfx_worker_thread+0x10/0x10
  [114596.324018]  kthread+0xef/0x120
  [114596.324021]  ? __pfx_kthread+0x10/0x10
  [114596.324022]  ret_from_fork+0x44/0x70
  [114596.324025]  ? __pfx_kthread+0x10/0x10
  [114596.324027]  ret_from_fork_asm+0x1b/0x30
  [114596.324029]  
  [114596.324029] ---[ end trace  ]---
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 oct 11 08:43 seq
   crw-rw 1 root audio 116, 33 oct 11 08:43 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.27.0-0ubuntu5

[Kernel-packages] [Bug 2039227] [NEW] Jammy update: v5.15.129 upstream stable release

[Kamal Mostafa]

Public bug reported:


SRU Justification

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

   v5.15.129 upstream stable release
   from git://git.kernel.org/

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

** Affects: linux (Ubuntu Jammy)
 Importance: Medium
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Jammy)
   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/2039227

Title:
  Jammy update: v5.15.129 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress

Bug description:
  
  SRU Justification

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

 v5.15.129 upstream stable release
 from git://git.kernel.org/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039227/+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 2031537] Re: Ethernet not stable 23.04 (RTL8168/8169)

[ahmed hanafi al-sayed]

Hi garry could you test the kernel in comment #101 please

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

Title:
  Ethernet not stable 23.04 (RTL8168/8169)

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

Bug description:
  [Impact]

  Ethernet is unstable with Realtek RTL8168h/8111h NIC and kernel 6.2
  resulting in frequent transmit queue timeouts. Related to ASPM. See
  'original description' below.

  [Test Case]

  Just regular usage for an extended period of time. No transmit queue
  timeouts with RTL8168h/8111h NICs.

  [Where Problems Could Occur]

  Modification are isolated to the r8169 driver so only machine where
  that driver is loaded are affected. Issues could show up as kernel
  crashes, stack traces, non-fnuctional wired network.

  [Original Description]

  hello,
  it is my first time reporting a pug hope it is the last

  there is thread here
  https://ubuntuforums.org/showthread.php?t=2489146=14151513

  another user experienced similar issue

  my network work fine at startup keep working for hours then disconnect and 
cannot reconnect without a restart
  I tested the cable using another pc and it was working repluged with no 
difference

  I thought it is caused by nvidia driver so changed it and the problem
  persist

  I use systemd-networkd

  uname -a
  Linux ahmed-OptiPlex-3090 6.2.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Wed 
Jul 12 22:39:51 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  lspci:
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 1b)

  dmesg:

  [Mon Aug 7 12:36:47 2023] audit: type=1400 audit(1691401007.881:150): 
apparmor="ALLOWED" operation="file_perm" class="file" 
profile="libreoffice-oosplash" 
name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_74ed987bff2950ad36ea f76d6640d9dc" 
pid=14414 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 
ouid=1000
  [Mon Aug 7 12:39:19 2023] [ cut here ]
  [Mon Aug 7 12:39:19 2023] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 
timed out
  [Mon Aug 7 12:39:19 2023] WARNING: CPU: 4 PID: 0 at 
net/sched/sch_generic.c:525 dev_watchdog+0x23a/0x250
  [Mon Aug 7 12:39:19 2023] Modules linked in: snd_seq_dummy snd_hrtimer 
nvidia_uvm(PO) bridge stp llc cfg80211 binfmt_misc nvidia_drm(PO) nls_iso8859_1 
snd_ctl_led nvidia_modeset(PO) snd_sof_pci_intel_cnl snd_sof_intel_hda_common 
soundwire_intel soundwire_generic_allocation soundwire_cadence 
snd_sof_intel_hda snd_sof_pci snd_hda_codec_realtek snd_sof_xtensa_dsp 
snd_hda_codec_generic snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core 
snd_hda_codec_hdmi snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel 
snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec intel_rapl_msr 
intel_rapl_common snd_hda_core intel_tcc_cooling x86_pkg_temp_thermal snd_hwdep 
intel_powerclamp coretemp nvidia(PO) snd_pcm kvm_intel snd_seq_midi i915 
snd_seq_midi_event mei_hdcp mei_pxp snd_rawmidi kvm drm_buddy snd_seq ttm 
irqbypass drm_display_helper snd_seq_device crct10dif_pclmul cec 
polyval_clmulni snd_timer polyval_generic dell_wmi ghash_clmulni_intel rc_core
  [Mon Aug 7 12:39:19 2023] sha512_ssse3 cmdlinepart aesni_intel drm_kms_helper 
snd mei_me spi_nor crypto_simd i2c_algo_bit dell_smbios cryptd soundcore dcdbas 
syscopyarea sysfillrect ledtrig_audio dell_wmi_sysman sysimgblt mei rapl mtd 
sparse_keymap dell_wmi_descriptor intel_pch_thermal intel_cstate wmi_bmof 
firmware_attributes_class ee1004 input_leds acpi_pad mac_hid msr parport_pc 
ppdev lp drm parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 
hid_generic usbhid hid ahci crc32_pclmul r8169 video intel_lpss_pci 
spi_intel_pci i2c_i801 libahci xhci_pci spi_intel intel_lpss realtek i2c_smbus 
xhci_pci_renesas idma64 wmi pinctrl_cannonlake
  [Mon Aug 7 12:39:19 2023] CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O 
6.2.0-26-generic #26-Ubuntu
  [Mon Aug 7 12:39:19 2023] Hardware name: Dell Inc. OptiPlex 3090/0492YX, BIOS 
2.13.1 05/10/2023
  [Mon Aug 7 12:39:19 2023] RIP: 0010:dev_watchdog+0x23a/0x250
  [Mon Aug 7 12:39:19 2023] Code: 00 e9 2b ff ff ff 48 89 df c6 05 ba a6 d5 01 
01 e8 3b 07 f8 ff 44 89 f1 48 89 de 48 c7 c7 f8 25 67 9d 48 89 c2 e8 06 09 29 
ff <0f> 0b e9 1c ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00
  [Mon Aug 7 12:39:19 2023] RSP: 0018:b40c40254e38 EFLAGS: 00010246
  [Mon Aug 7 12:39:19 2023] RAX:  RBX: 997996868000 RCX: 

  [Mon Aug 7 12:39:19 2023] RDX:  RSI:  RDI: 

  [Mon Aug 7 12:39:19 2023] RBP: b40c40254e68 R08:  R09: 

  [Mon Aug 7 12:39:19 2023] R10:  R11:  R12: 
9979968684c8
  [Mon Aug 7 12:39:19 

[Kernel-packages] [Bug 2031537] Re: Ethernet not stable 23.04 (RTL8168/8169)

[Garry]

6.2.0-34-generic (release)
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash fsck.mode=force fsck.repair=yes 
pcie_aspm=off"


When the driver fails, NetworkManager shows "active (running)" and 
/sys/class/net/enp2s0/speed shows "1000" :-(

kernel: [ cut here ]
kernel: NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out
kernel: WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:525 
dev_watchdog+0x21f/0x230
kernel: Modules linked in: rfcomm tls xt_conntrack nft_chain_nat xt_MASQUERADE 
nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
xfrm_user xfrm_algo xt_addrtype nft_compat nf_tables libc>
kernel:  snd_rawmidi rc_core crct10dif_pclmul btusb snd_seq polyval_generic 
ghash_clmulni_intel drm_kms_helper btrtl btbcm snd_seq_device sha512_ssse3 
i2c_algo_bit btintel snd_timer aesni_intel syscopyarea i>
kernel: CPU: 1 PID: 0 Comm: swapper/1 Not tainted 6.2.0-34-generic 
#34~22.04.1-Ubuntu
kernel: Hardware name: AZW U59/U59, BIOS JTKT001 05/05/2022
kernel: RIP: 0010:dev_watchdog+0x21f/0x230
kernel: Code: 00 e9 31 ff ff ff 4c 89 e7 c6 05 96 6c 78 01 01 e8 26 00 f8 ff 44 
89 f1 4c 89 e6 48 c7 c7 38 5c c4 aa 48 89 c2 e8 01 d6 2b ff <0f> 0b e9 22 ff ff 
ff 66 2e 0f 1f 84 00 00 00 00 00 90 90 90 90 90
kernel: RSP: 0018:b28c4007ce70 EFLAGS: 00010246
kernel: RAX:  RBX: 9b8fd24784c8 RCX: 
kernel: RDX:  RSI:  RDI: 
kernel: RBP: b28c4007ce98 R08:  R09: 
kernel: R10:  R11:  R12: 9b8fd2478000
kernel: R13: 9b8fd247841c R14:  R15: 
kernel: FS:  () GS:9b933008() 
knlGS:
kernel: CS:  0010 DS:  ES:  CR0: 80050033
kernel: CR2: 00c000133010 CR3: 0001d921 CR4: 00350ee0
kernel: Call Trace:
kernel:  
kernel:  ? show_regs+0x72/0x90
kernel:  ? dev_watchdog+0x21f/0x230
kernel:  ? __warn+0x8d/0x160
kernel:  ? dev_watchdog+0x21f/0x230
kernel:  ? report_bug+0x1bb/0x1d0
kernel:  ? irq_work_queue+0x32/0x80
kernel:  ? handle_bug+0x46/0x90
kernel:  ? exc_invalid_op+0x19/0x80
kernel:  ? asm_exc_invalid_op+0x1b/0x20
kernel:  ? dev_watchdog+0x21f/0x230
kernel:  ? __pfx_dev_watchdog+0x10/0x10
kernel:  call_timer_fn+0x29/0x160
kernel:  ? __pfx_dev_watchdog+0x10/0x10
kernel:  __run_timers.part.0+0x1fb/0x2b0
kernel:  ? ktime_get+0x43/0xc0
kernel:  ? __pfx_tick_sched_timer+0x10/0x10
kernel:  ? lapic_next_deadline+0x2c/0x50
kernel:  ? clockevents_program_event+0xb2/0x140
kernel:  run_timer_softirq+0x2a/0x60
kernel:  __do_softirq+0xda/0x330
kernel:  ? hrtimer_interrupt+0x12b/0x250
kernel:  __irq_exit_rcu+0xa2/0xd0
kernel:  irq_exit_rcu+0xe/0x20
kernel:  sysvec_apic_timer_interrupt+0x96/0xb0
kernel:  
kernel:  
kernel:  asm_sysvec_apic_timer_interrupt+0x1b/0x20
kernel: RIP: 0010:cpuidle_enter_state+0xde/0x6f0
kernel: Code: 61 11 56 e8 a4 2b 45 ff 8b 53 04 49 89 c7 0f 1f 44 00 00 31 ff e8 
52 0a 44 ff 80 7d d0 00 0f 85 e8 00 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 0f 
02 00 00 4d 63 ee 49 83 fd 09 0f 87 c4 04 00 00
kernel: RSP: 0018:b28c4012be28 EFLAGS: 0246
kernel: RAX:  RBX: 9b93300bd928 RCX: 
kernel: RDX: 0001 RSI:  RDI: 
kernel: RBP: b28c4012be78 R08:  R09: 
kernel: R10:  R11:  R12: ab6c29a0
kernel: R13: 0003 R14: 0003 R15: 00013895edc48f3b
kernel:  ? cpuidle_enter_state+0xce/0x6f0
kernel:  cpuidle_enter+0x2e/0x50
kernel:  cpuidle_idle_call+0x14f/0x1e0
kernel:  do_idle+0x82/0x110
kernel:  cpu_startup_entry+0x20/0x30
kernel:  start_secondary+0x122/0x160
kernel:  secondary_startup_64_no_verify+0xe5/0xeb
kernel:  
kernel: ---[ end trace  ]---


System:Kernel: 6.2.0-34-generic x86_64 bits: 64 Console: pty pts/1 Distro: 
Ubuntu 22.04.3 LTS (Jammy Jellyfish)
Machine:   Type: Desktop Mobo: AZW model: U59 serial: N/A UEFI: American 
Megatrends LLC. v: JTKT001 date: 05/05/2022
Network:   Device-1: Intel Wireless 3165 driver: iwlwifi
   IF: wlp1s0 state: down mac: 
   Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
driver: r8169
   IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: 
   Device-3: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
driver: r8169
   IF: enp3s0 state: down mac: 
   IF-ID-1: docker0 state: down mac: 

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

Title:
  Ethernet not stable 23.04 (RTL8168/8169)

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

Bug description:
  [Impact]

  Ethernet is unstable with Realtek RTL8168h/8111h NIC and kernel 6.2
  resulting in 

[Kernel-packages] [Bug 2033399] Re: Boot failure on VisionFive2 board with Mantic daily-preinstalled.

[Doc Bacardi]

Thank you for the updated documentation here: 
https://wiki.ubuntu.com/RISC-V/StarFive%20VisionFive%202
Finally a hint how to get this working...

Using the brand new image from here:
https://cdimage.ubuntu.com/releases/23.10/release/ubuntu-23.10-preinstalled-
server-riscv64+visionfive2.img.xz

The image only boots with the patched u-boot from here:
https://launchpad.net/~ubuntu-risc-v-
team/+archive/ubuntu/release/+sourcefiles/u-boot-
starfive/2023.09.22-next-5d2fae79c7d6-0ubuntu1~ppa4/u-boot-
starfive_2023.09.22-next-5d2fae79c7d6.orig.tar.xz

Follow the instructions in the chapter "Updating U-Boot". Do not use the
vendor U-Boot and do not forget to reset the environment to the
defaults.

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

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

Title:
  Boot failure on VisionFive2 board with Mantic daily-preinstalled.

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  The Mantic preinstalled SD card image for the VisionFive2 board does not boot.
  I tested this on one v1.3B board with 4GB RAM.
  Older Mantic images are booting, which was last tested with the 
daily-preinstalled from  20.Jul .

  Attached are the UART logs of the working and the non-working image.
  Both images were tested on the same VisionFive2 board.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033399/+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 2039211] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 2039211

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  nf_nat and macvlan

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [114596.323853] [ cut here ]
  [114596.323855] WARNING: CPU: 1 PID: 46587 at net/netfilter/nf_nat_core.c:678 
nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323865] Modules linked in: tls xt_nat xt_tcpudp xt_conntrack 
nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat 
nf_tables nfnetlink br_netfilter rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd 
grace fscache netfs overlay macvlan bridge stp llc cfg80211 sunrpc binfmt_misc 
nls_iso8859_1 intel_rapl_msr intel_rapl_common hyperv_fb serio_raw joydev 
mac_hid hv_balloon vmgenid msr parport_pc ppdev lp dm_multipath parport 
efi_pstore dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear hyperv_drm drm_shmem_helper hid_generic 
drm_kms_helper hid_hyperv drm hid hv_storvsc hyperv_keyboard hv_netvsc 
scsi_transport_fc hv_utils crct10dif_pclmul crc32_pclmul polyval_clmulni 
polyval_generic ghash_clmulni_intel aesni_intel crypto_simd cryptd hv_vmbus
  [114596.323907] CPU: 1 PID: 46587 Comm: kworker/u4:3 Tainted: GB   W  
6.5.0-9-generic #9-Ubuntu
  [114596.323909] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
  [114596.323910] Workqueue: events_unbound macvlan_process_broadcast [macvlan]
  [114596.323914] RIP: 0010:nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323919] Code: 8b bb b0 00 00 00 48 83 c8 20 48 89 83 80 00 00 00 48 
85 ff 0f 84 d2 fe ff ff 0f b6 07 84 c0 0f 85 75 fe ff ff e9 bb fe ff ff <0f> 0b 
31 c0 e9 d2 fe ff ff ba 20 08 00 00 be 02 00 00 00 48 89 df
  [114596.323920] RSP: 0018:acc1ebd0 EFLAGS: 00010202
  [114596.323921] RAX: 0080 RBX: 9773847b0200 RCX: 

  [114596.323922] RDX:  RSI: acc1ec8c RDI: 
9773847b0200
  [114596.323923] RBP: acc1ec70 R08: 2d00a8c0 R09: 

  [114596.323924] R10:  R11:  R12: 

  [114596.323925] R13: 9075ec40 R14: acc1ec8c R15: 
9773847b0200
  [114596.323925] FS:  () GS:97737fb0() 
knlGS:
  [114596.323926] CS:  0010 DS:  ES:  CR0: 80050033
  [114596.323927] CR2: 2a8952d9d000 CR3: 44532000 CR4: 
00350ee0
  [114596.323929] Call Trace:
  [114596.323931]  
  [114596.323933]  ? show_regs+0x6d/0x80
  [114596.323936]  ? __warn+0x89/0x160
  [114596.323939]  ? nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323944]  ? report_bug+0x17e/0x1b0
  [114596.323947]  ? handle_bug+0x51/0xa0
  [114596.323950]  ? exc_invalid_op+0x18/0x80
  [114596.323952]  ? asm_exc_invalid_op+0x1b/0x20
  [114596.323955]  ? nf_nat_setup_info+0x30e/0x360 [nf_nat]
  [114596.323959]  __nf_nat_alloc_null_binding+0x5e/0x90 [nf_nat]
  [114596.323963]  nf_nat_inet_fn+0x2da/0x350 [nf_nat]
  [114596.323967]  nf_nat_ipv4_local_in+0x59/0x140 [nf_nat]
  [114596.323971]  nf_hook_slow+0x43/0xd0
  [114596.323974]  ip_local_deliver+0xe1/0x120
  [114596.323977]  ? __pfx_ip_local_deliver_finish+0x10/0x10
  [114596.323978]  ip_rcv+0x175/0x190
  [114596.323980]  ? __pfx_ip_rcv_finish+0x10/0x10
  [114596.323982]  __netif_receive_skb_one_core+0x91/0xa0
  [114596.323985]  __netif_receive_skb+0x15/0x60
  [114596.323987]  process_backlog+0x8e/0x150
  [114596.323989]  __napi_poll+0x30/0x1f0
  [114596.323990]  net_rx_action+0x181/0x2e0
  [114596.323993]  __do_softirq+0xd6/0x346
  [114596.323995]  do_softirq.part.0+0x41/0x80
  [114596.323997]  
  [114596.323998]  
  [114596.323999]  __local_bh_enable_ip+0x72/0x80
  [114596.324001]  netif_rx+0xec/0x100
  [114596.324002]  macvlan_broadcast+0x102/0x1d0 [macvlan]
  [114596.324006]  macvlan_multicast_rx+0x66/0x80 [macvlan]
  [114596.324009]  macvlan_process_broadcast+0xe9/0x160 [macvlan]
  [114596.324012]  process_one_work+0x220/0x440
  [114596.324014]  worker_thread+0x4d/0x3f0
  [114596.324016]  ? 

[Kernel-packages] [Bug 2039211] [NEW] nf_nat and macvlan

[Juan Pedro Paredes]

Public bug reported:

[114596.323853] [ cut here ]
[114596.323855] WARNING: CPU: 1 PID: 46587 at net/netfilter/nf_nat_core.c:678 
nf_nat_setup_info+0x30e/0x360 [nf_nat]
[114596.323865] Modules linked in: tls xt_nat xt_tcpudp xt_conntrack 
nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat 
nf_tables nfnetlink br_netfilter rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd 
grace fscache netfs overlay macvlan bridge stp llc cfg80211 sunrpc binfmt_misc 
nls_iso8859_1 intel_rapl_msr intel_rapl_common hyperv_fb serio_raw joydev 
mac_hid hv_balloon vmgenid msr parport_pc ppdev lp dm_multipath parport 
efi_pstore dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear hyperv_drm drm_shmem_helper hid_generic 
drm_kms_helper hid_hyperv drm hid hv_storvsc hyperv_keyboard hv_netvsc 
scsi_transport_fc hv_utils crct10dif_pclmul crc32_pclmul polyval_clmulni 
polyval_generic ghash_clmulni_intel aesni_intel crypto_simd cryptd hv_vmbus
[114596.323907] CPU: 1 PID: 46587 Comm: kworker/u4:3 Tainted: GB   W
  6.5.0-9-generic #9-Ubuntu
[114596.323909] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
[114596.323910] Workqueue: events_unbound macvlan_process_broadcast [macvlan]
[114596.323914] RIP: 0010:nf_nat_setup_info+0x30e/0x360 [nf_nat]
[114596.323919] Code: 8b bb b0 00 00 00 48 83 c8 20 48 89 83 80 00 00 00 48 85 
ff 0f 84 d2 fe ff ff 0f b6 07 84 c0 0f 85 75 fe ff ff e9 bb fe ff ff <0f> 0b 31 
c0 e9 d2 fe ff ff ba 20 08 00 00 be 02 00 00 00 48 89 df
[114596.323920] RSP: 0018:acc1ebd0 EFLAGS: 00010202
[114596.323921] RAX: 0080 RBX: 9773847b0200 RCX: 

[114596.323922] RDX:  RSI: acc1ec8c RDI: 
9773847b0200
[114596.323923] RBP: acc1ec70 R08: 2d00a8c0 R09: 

[114596.323924] R10:  R11:  R12: 

[114596.323925] R13: 9075ec40 R14: acc1ec8c R15: 
9773847b0200
[114596.323925] FS:  () GS:97737fb0() 
knlGS:
[114596.323926] CS:  0010 DS:  ES:  CR0: 80050033
[114596.323927] CR2: 2a8952d9d000 CR3: 44532000 CR4: 
00350ee0
[114596.323929] Call Trace:
[114596.323931]  
[114596.323933]  ? show_regs+0x6d/0x80
[114596.323936]  ? __warn+0x89/0x160
[114596.323939]  ? nf_nat_setup_info+0x30e/0x360 [nf_nat]
[114596.323944]  ? report_bug+0x17e/0x1b0
[114596.323947]  ? handle_bug+0x51/0xa0
[114596.323950]  ? exc_invalid_op+0x18/0x80
[114596.323952]  ? asm_exc_invalid_op+0x1b/0x20
[114596.323955]  ? nf_nat_setup_info+0x30e/0x360 [nf_nat]
[114596.323959]  __nf_nat_alloc_null_binding+0x5e/0x90 [nf_nat]
[114596.323963]  nf_nat_inet_fn+0x2da/0x350 [nf_nat]
[114596.323967]  nf_nat_ipv4_local_in+0x59/0x140 [nf_nat]
[114596.323971]  nf_hook_slow+0x43/0xd0
[114596.323974]  ip_local_deliver+0xe1/0x120
[114596.323977]  ? __pfx_ip_local_deliver_finish+0x10/0x10
[114596.323978]  ip_rcv+0x175/0x190
[114596.323980]  ? __pfx_ip_rcv_finish+0x10/0x10
[114596.323982]  __netif_receive_skb_one_core+0x91/0xa0
[114596.323985]  __netif_receive_skb+0x15/0x60
[114596.323987]  process_backlog+0x8e/0x150
[114596.323989]  __napi_poll+0x30/0x1f0
[114596.323990]  net_rx_action+0x181/0x2e0
[114596.323993]  __do_softirq+0xd6/0x346
[114596.323995]  do_softirq.part.0+0x41/0x80
[114596.323997]  
[114596.323998]  
[114596.323999]  __local_bh_enable_ip+0x72/0x80
[114596.324001]  netif_rx+0xec/0x100
[114596.324002]  macvlan_broadcast+0x102/0x1d0 [macvlan]
[114596.324006]  macvlan_multicast_rx+0x66/0x80 [macvlan]
[114596.324009]  macvlan_process_broadcast+0xe9/0x160 [macvlan]
[114596.324012]  process_one_work+0x220/0x440
[114596.324014]  worker_thread+0x4d/0x3f0
[114596.324016]  ? _raw_spin_unlock_irqrestore+0x11/0x60
[114596.324017]  ? __pfx_worker_thread+0x10/0x10
[114596.324018]  kthread+0xef/0x120
[114596.324021]  ? __pfx_kthread+0x10/0x10
[114596.324022]  ret_from_fork+0x44/0x70
[114596.324025]  ? __pfx_kthread+0x10/0x10
[114596.324027]  ret_from_fork_asm+0x1b/0x30
[114596.324029]  
[114596.324029] ---[ end trace  ]---

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 oct 11 08:43 seq
 crw-rw 1 root audio 116, 33 oct 11 08:43 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:

[Kernel-packages] [Bug 1968040] Re: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

[Sean Morley]

** Attachment added: "journalctl.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5708896/+files/journalctl.txt

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

Title:
  [i915] Blanked screen doesn't wake up after locking
  [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid
  argument]

Status in GNOME Shell:
  New
Status in Mutter:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.19 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  [ Workaround ]

  Add to /etc/environment (in Ubuntu 22.04):

    MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0

  or in Ubuntu 22.10 and later:

    MUTTER_DEBUG_FORCE_KMS_MODE=simple

  and then reboot.

  [ Upstream bugs ]

  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5098
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2268
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2749

  [ Original report ]

  (initially reported as a comment on bug #1965085, and split into a
  separate bug report)

  After I lock my screen and let it blank, moving the mouse or pressing
  any key on the keyboard won't wake it up. The only reliable workaround
  I've found is to press Ctrl+Alt+F1.

  That's on a fully up-to-date jammy, my hardware is an Intel NUC with a
  single Samsung monitor connected with a standard HDMI cable. This is a
  regression that started happening yesterday (2022-04-05) if I can
  remember correctly (I do apply pending updates at least once daily).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  6 15:19:30 2022
  InstallationDate: Installed on 2020-09-16 (566 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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 1968040] Re: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

[Sean Morley]

I am also able to reproduce this bug.  I logged in via ssh and collected
journal logs and drm_info while the screen was blank and unrecoverable.

MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 does in fact solve the issue for me.


** Attachment added: "drm_info.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5708895/+files/drm_info.txt

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

Title:
  [i915] Blanked screen doesn't wake up after locking
  [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid
  argument]

Status in GNOME Shell:
  New
Status in Mutter:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.19 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  [ Workaround ]

  Add to /etc/environment (in Ubuntu 22.04):

    MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0

  or in Ubuntu 22.10 and later:

    MUTTER_DEBUG_FORCE_KMS_MODE=simple

  and then reboot.

  [ Upstream bugs ]

  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5098
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2268
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2749

  [ Original report ]

  (initially reported as a comment on bug #1965085, and split into a
  separate bug report)

  After I lock my screen and let it blank, moving the mouse or pressing
  any key on the keyboard won't wake it up. The only reliable workaround
  I've found is to press Ctrl+Alt+F1.

  That's on a fully up-to-date jammy, my hardware is an Intel NUC with a
  single Samsung monitor connected with a standard HDMI cable. This is a
  regression that started happening yesterday (2022-04-05) if I can
  remember correctly (I do apply pending updates at least once daily).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  6 15:19:30 2022
  InstallationDate: Installed on 2020-09-16 (566 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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 2039208] Re: Azure: mlx5e: Add support for PCI relaxed ordering (RO) for better performance

[Tim Gardner]

https://lists.ubuntu.com/archives/kernel-team/2023-October/146153.html

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

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

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

** Changed in: linux-azure (Ubuntu Jammy)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

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

** Changed in: linux-azure (Ubuntu Lunar)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  Azure: mlx5e: Add support for PCI relaxed ordering (RO) for better
  performance

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Jammy:
  In Progress
Status in linux-azure source package in Lunar:
  In Progress

Bug description:
  SRU Justification

  [Impact]
  On Azure, the VM SKU Standard_NC64as_T4_v3's bandwidth is 30 Gbps, but we can 
only reach 15~20 Gbps with the 5.15.0-1049-azure kernel in Ubuntu 20.04 or the 
6.2.0-1014-azure kernel in Ubuntu 22.04.

  After I pick up the upstream patch(es) to enable PCI relaxed ordering
  (RO) for the Mellanox VF NIC, the throughput goes up to 30.4 Gbps.

  [Fix]

  [1]
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=17347d5430c4e4e1a3c58ffa2732746bd26a9c02

  [2]
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e2351e517068718724f1d3b4010e2a41ec91fa76

  [3]
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=77528e2aed9246cf8017b8a6f1b658a264d6f2b2

  [4]
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ed4b0661cce119870edb1994fd06c9cbc1dc05c3

  [Test Plan]

  Microsoft tested

  [Regression Potential]

  Mellanox connections could be corrupted or run slower.

  [Other Info]

  SF: #00370735

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2039208/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland

[Bug Watch Updater]

** Changed in: mutter
   Status: New => Fix Released

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

Title:
  [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy
  load in Wayland

Status in Linux:
  New
Status in Mutter:
  Fix Released
Status in X.Org X server:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  In Progress
Status in linux source package in Mantic:
  Confirmed
Status in mutter source package in Mantic:
  In Progress

Bug description:
  [ Impact ]

  gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems,
  sometimes when the screen locks, sometimes when launching particular
  apps.

  [ Workaround ]

  Add this to /etc/environment:

    MUTTER_DEBUG_KMS_THREAD_TYPE=user

  and then reboot.

  [ Test Plan ]

  Not all Ryzen systems (including one I just purchased) are able to
  reproduce the bug. We have no choice but to leave final verification
  to the community. Anyone affected should try locking their screen and
  verify they are not instantly returned to the login screen.

  [ Where problems could occur ]

  Anywhere in frame scheduling and particularly for mouse cursor
  movement since that's what the real-time thread exists to optimize.

  [ Original Description ]

  I have this issue on Ubuntu 23.10. Lock screen works only with an external 
monitor connected. Otherwise the session is ended and the user is logged out 
and brought to the gdm screen.
  All works in xorg.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~beta.1-0ubuntu2
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 22:32:22 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2023-09-03 (3 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2034619/+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 2039208] [NEW] Azure: mlx5e: Add support for PCI relaxed ordering (RO) for better performance

[Tim Gardner]

Public bug reported:

SRU Justification

[Impact]
On Azure, the VM SKU Standard_NC64as_T4_v3's bandwidth is 30 Gbps, but we can 
only reach 15~20 Gbps with the 5.15.0-1049-azure kernel in Ubuntu 20.04 or the 
6.2.0-1014-azure kernel in Ubuntu 22.04.

After I pick up the upstream patch(es) to enable PCI relaxed ordering
(RO) for the Mellanox VF NIC, the throughput goes up to 30.4 Gbps.

[Fix]

[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=17347d5430c4e4e1a3c58ffa2732746bd26a9c02

[2]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e2351e517068718724f1d3b4010e2a41ec91fa76

[3]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=77528e2aed9246cf8017b8a6f1b658a264d6f2b2

[4]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ed4b0661cce119870edb1994fd06c9cbc1dc05c3

[Test Plan]

Microsoft tested

[Regression Potential]

Mellanox connections could be corrupted or run slower.

[Other Info]

SF: #00370735

** Affects: linux-azure (Ubuntu)
 Importance: Undecided
 Status: Fix Released

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

** Package changed: linux (Ubuntu) => linux-azure (Ubuntu)

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

** Changed in: linux-azure (Ubuntu)
   Status: New => Fix Released

** Description changed:

  SRU Justification
  
  [Impact]
  On Azure, the VM SKU Standard_NC64as_T4_v3's bandwidth is 30 Gbps, but we can 
only reach 15~20 Gbps with the 5.15.0-1049-azure kernel in Ubuntu 20.04 or the 
6.2.0-1014-azure kernel in Ubuntu 22.04.
  
  After I pick up the upstream patch(es) to enable PCI relaxed ordering
  (RO) for the Mellanox VF NIC, the throughput goes up to 30.4 Gbps.
+ 
+ [Fix]
+ 
+ [1]
+ 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=17347d5430c4e4e1a3c58ffa2732746bd26a9c02
+ 
+ [2]
+ 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e2351e517068718724f1d3b4010e2a41ec91fa76
+ 
+ [3]
+ 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=77528e2aed9246cf8017b8a6f1b658a264d6f2b2
+ 
+ [4]
+ 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ed4b0661cce119870edb1994fd06c9cbc1dc05c3
  
  [Test Plan]
  
  Microsoft tested
  
  [Regression Potential]
  
  Mellanox connections could be corrupted or run slower.
  
  [Other Info]
  
  SF: #00370735

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

Title:
  Azure: mlx5e: Add support for PCI relaxed ordering (RO) for better
  performance

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Lunar:
  New

Bug description:
  SRU Justification

  [Impact]
  On Azure, the VM SKU Standard_NC64as_T4_v3's bandwidth is 30 Gbps, but we can 
only reach 15~20 Gbps with the 5.15.0-1049-azure kernel in Ubuntu 20.04 or the 
6.2.0-1014-azure kernel in Ubuntu 22.04.

  After I pick up the upstream patch(es) to enable PCI relaxed ordering
  (RO) for the Mellanox VF NIC, the throughput goes up to 30.4 Gbps.

  [Fix]

  [1]
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=17347d5430c4e4e1a3c58ffa2732746bd26a9c02

  [2]
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e2351e517068718724f1d3b4010e2a41ec91fa76

  [3]
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=77528e2aed9246cf8017b8a6f1b658a264d6f2b2

  [4]
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ed4b0661cce119870edb1994fd06c9cbc1dc05c3

  [Test Plan]

  Microsoft tested

  [Regression Potential]

  Mellanox connections could be corrupted or run slower.

  [Other Info]

  SF: #00370735

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2039208/+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 2034523] Re: Lenovo Thinkpad P14s Gen3 amd Ryzen 7 PRO 6850U various segfault and system becoming irresponsive

[__JEAN_FRANCOIS__]

Sounds like a good news.

On my side I was also experiencing hw issues (hence many many freezes
and other problems), the motherboard of my laptop has been replaced
recently.

As suggested by someone from lenovo on lenovo forum, I'm now running fedora 38 
which seemed to be stable for him (I'm waiting for Ubuntu 23.10 and a more 
recent kernel).
On fedora I'm running kernel 6.5.5-200.fc38.x86_64.
Gdm is started but I'm using the laptop remotely through ssh (I'm still worried 
about the system stability) so there is not much graphical activity (only 
journalctl -k -f on tty2) it's probably why I haven't faced any issue yet 
(uptime is 6 days).

It seems the issue is solved, but let me know if you want me to try
something on the kernel I'm running.

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

Title:
  Lenovo Thinkpad P14s Gen3 amd Ryzen 7 PRO 6850U various segfault and
  system becoming irresponsive

Status in linux-signed-oem-6.5 package in Ubuntu:
  Confirmed

Bug description:
  Hello

  This bug report is related to:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033756 : the
  hardware is the same.

  I'm still hoping that my laptop does not crash once a day (in average), I'm 
now trying the kernel 6.5. It seems a bit better but:
  - I got screen flickering (screen goes black ~2s then comes back) both on 
external monitor and on internal. It seems to happen once for each screen, not 
at the same time.
  - Various programs are crashing with segfault
  - System become nearly unusable (soft lockup loop), maybe closing the lid 
stop this loop. This last point was triggered by launching a huge compilation.

  Let me know if I can do some tests that could help to solve the
  problem.

  Kind regards

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-1003-oem 6.5.0-1003.3
  ProcVersionSignature: Ubuntu 6.5.0-1003.3-oem 6.5.0
  Uname: Linux 6.5.0-1003-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 09:53:02 2023
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02
  InstallationDate: Installed on 2023-06-02 (95 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20220803-13:42
  ProcEnviron:
   TERM=alacritty
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: linux-signed-oem-6.5
  UpgradeStatus: Upgraded to jammy on 2023-08-12 (24 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-6.5/+bug/2034523/+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 2034523] Re: Lenovo Thinkpad P14s Gen3 amd Ryzen 7 PRO 6850U various segfault and system becoming irresponsive

[Dominik]

This is related to kernel 6.5 and happens for me on Ryzen 5 3500U on
Mantic Minotaur.

It is fixed in kernel 6.5.6, as described here:
https://gitlab.freedesktop.org/drm/amd/-/issues/2830

I first saw this on Fedora with kernel 6.5.5 (it was not present on
kernel 6.4) and can confirm kernel 6.5.6 fixes it.

I really hope Mantic is not released with the kernel it has now.

** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2830
   https://gitlab.freedesktop.org/drm/amd/-/issues/2830

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

Title:
  Lenovo Thinkpad P14s Gen3 amd Ryzen 7 PRO 6850U various segfault and
  system becoming irresponsive

Status in linux-signed-oem-6.5 package in Ubuntu:
  Confirmed

Bug description:
  Hello

  This bug report is related to:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033756 : the
  hardware is the same.

  I'm still hoping that my laptop does not crash once a day (in average), I'm 
now trying the kernel 6.5. It seems a bit better but:
  - I got screen flickering (screen goes black ~2s then comes back) both on 
external monitor and on internal. It seems to happen once for each screen, not 
at the same time.
  - Various programs are crashing with segfault
  - System become nearly unusable (soft lockup loop), maybe closing the lid 
stop this loop. This last point was triggered by launching a huge compilation.

  Let me know if I can do some tests that could help to solve the
  problem.

  Kind regards

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-1003-oem 6.5.0-1003.3
  ProcVersionSignature: Ubuntu 6.5.0-1003.3-oem 6.5.0
  Uname: Linux 6.5.0-1003-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 09:53:02 2023
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02
  InstallationDate: Installed on 2023-06-02 (95 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20220803-13:42
  ProcEnviron:
   TERM=alacritty
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: linux-signed-oem-6.5
  UpgradeStatus: Upgraded to jammy on 2023-08-12 (24 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-6.5/+bug/2034523/+subscriptions


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

[Kernel-packages] [Bug 2039191] [NEW] Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization

[John Cabaj]

Public bug reported:

[Impact]

* Kernel OOPS encountered on 32-bit kernels due to commit cd0e9ab from
  git://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/lunar

[Fix]

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

[Test Case]

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

[Where things could go wrong]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Status in linux-aws package in Ubuntu:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-aws source package in Jammy:
  New
Status in linux-gcp source package in Jammy:
  New
Status in linux-aws source package in Lunar:
  New
Status in linux-gcp source package in Lunar:
  New
Status in linux-aws source package in Mantic:
  New
Status in linux-gcp source package in Mantic:
  New

Bug description:
  [Impact]

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

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

  [Fix]

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

  [Test Case]

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

  [Where things could go wrong]

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

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


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

[Kernel-packages] [Bug 2038782] Re: linux-firmware halts boot before grub screen on clean install-upgrade to Ubuntu 22.04.3

[John Patterson]

Linux-firmware (only) is being added to this build

Oct 11 19:09:07 ziirkaan kernel: Linux version 6.2.0-34-generic 
(buildd@bos03-amd64-059) (x86_64-linux-gnu-gcc-11 (Ubuntu 
11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) 
#34~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep  7 13:12:03 UTC 2 (Ubuntu 
6.2.0-34.34~22.04.1-generic 6.2.16)
Oct 11 19:09:07 ziirkaan kernel: Command line: 
BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic 
root=UUID=2a54f09f-8cc0-4b2c-bdbb-6c794d6e2635 ro quiet splash vt.handoff=7
Oct 11 19:09:07 ziirkaan kernel: KERNEL supported cpus:
Oct 11 19:09:07 ziirkaan kernel:   Intel GenuineIntel
Oct 11 19:09:07 ziirkaan kernel:   AMD AuthenticAMD
Oct 11 19:09:07 ziirkaan kernel:   Hygon HygonGenuine
Oct 11 19:09:07 ziirkaan kernel:   Centaur CentaurHauls
Oct 11 19:09:07 ziirkaan kernel:   zhaoxin   Shanghai

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

Title:
  linux-firmware halts boot before grub screen on clean install-upgrade
  to Ubuntu 22.04.3

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  
  System halts just after filesystem journaling after USB install of LTS Ubuntu 
22.04.2 to Ubuntu 22.04.3, never makes it to grub screen, can't boot system. 

  Another bug report from 2020 says their system gets past grub screen
  and then gets stuck, I don't even make it that far, no other bug
  reports I found seems similar. Since I can't get to grub, I can't
  adjust boot options because it's apparently not going to load the OS.

  I receive no errors. Since the OS isn't loaded, nothing shows up in
  the filesystem logs.

  
  Can CTRL+ALT+DEL reboot, but can't get past journaling and into GRUB.

  
  Since system won't proceed further after journaling completes, apport can't 
start or dump a report.


  
  Steps to Reproduce:
  ---

  * Boot from official USB 22.04.2 USB image made as per Ubuntu instructions 
using Ubuntu bootable disk tool 
  * Accept all installation defaults
  * reboot

  Once rebooted and at 22.04.2 desktop, open terminal and issue:

  * sudo apt update

  (You will be told 340+ packages need to be installed)

  * sudo apt upgrade

  (wait for apt upgrade to complete)

  * reboot

  After rebooting from upgrade, system halts after filesystem journaling
  (which reports filesystem is in a good state on my system), yet system
  will not continue to grub/OS boot options screen despite filesystem
  being OK.

  I left system running at that spot overnight, no change in the AM,
  still stuck at journaling screen.

  Again, journaling reports no errors, computer simply won't boot.


  HOW I VERIFIED:
  ---

  Wiped disk (full overwrite erase)

  Reinstalled as per above

  sudo apt update
  sudo apt-mark hold linux-firmware
  sudo apt upgrade
  reboot

  After above steps, system boots & runs (using same system now to write
  this bug report).

  At this time, the system is as fully patched as I can get it:

  user@myhost:~$ sudo apt list --upgradeable
  [sudo] password for user: 
  Listing... Done
  gjs/jammy-updates 1.72.4-0ubuntu0.22.04.1 amd64 [upgradable from: 
1.72.2-0ubuntu1]
  libgjs0g/jammy-updates 1.72.4-0ubuntu0.22.04.1 amd64 [upgradable from: 
1.72.2-0ubuntu1]
  linux-firmware/jammy-updates,jammy-updates 20220329.git681281e4-0ubuntu3.19 
all [upgradable from: 20220329.git681281e4-0ubuntu3.10]


  
  ADDITIONAL NOTES:
  

  Booting into a stand-alone memory test on the system finds no memory
  faults or errors.

  Video stress-test of all functions (2D, shaders, vector, bump, buffer,
  raytrace etc.) performed on the system prior to running "sudo apt
  upgrade".  No failure, no crash, frame rates on par with public
  benchmarks. Crushed the card at 4K resolution, and also ran it with
  eight 1k instances with no problems. Video card ruled out.

  Replaced hard disk with new disk from different vendor, (even though
  journal finds no errors), problem persisted.

  
  Simply placing a hold on linux-firmware package prevents the problem reliably 
regardless of hardware setup.

  
  System up and stable now across multiple reboots and software installs for 6 
hours and now has full software load, including qemu/kvm.


  
  DIAGNOSTICS
  ---

  user@myhost:~$ sudo lshw -short

  H/W path  Device  Class  Description
  
system System Product Name 
(SKU)
  /0busTUF GAMING B550-PLUS 
WIFI II
  /0/0  memory 64KiB BIOS
  /0/34 memory 64GiB System Memory
  /0/34/0   memory 16GiB DIMM DDR4 
Synchronous Unbuffered (Unregistered) 2400 MHz 

[Kernel-packages] [Bug 2037403] Re: PCI BARs larger than 128GB are disabled

[Feysel Mohammed]

** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy

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

Title:
  PCI BARs larger than 128GB are disabled

Status in linux package in Ubuntu:
  Incomplete
Status in linux-bluefield package in Ubuntu:
  New
Status in linux source package in Jammy:
  Fix Committed
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  [SRU Justification]

  [Impact]

  Current linux-bluefield kernel reports that PCI BARs larger than 128GB
  are disabled.

  Increase the maximum PCI BAR size from 128GB to 8TB for future
  expansion.

  [Test Plan]

  Use updated kernel with PCI device with PCI BARs larger than 128GB.

  [Where problems could occur]

  No potential problems are expected.

  [Other Info]

  Testing has been provided by the customer. This patch is a cherry-pick
  from the upstream 5.18 kernel. It is intended for linux-bluefield
  kernel re-spin but it may be also suitable for the generic kernel
  (separate submission).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037403/+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 2038583] Re: Turning COMPAT_32BIT_TIME off on s390x

[bugproxy]

** Tags added: architecture-s39064 bugnameltc-203848 severity-medium
targetmilestone-inin---

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

Title:
  Turning COMPAT_32BIT_TIME off on s390x

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This will prevent existing s390 binaries to operate correctly, if they
  are still using 32bit time.

  24.04 LTS is likely to be used for 10 years. And if allowed to overrun
  and remain active in the field in 2038 can lead to catastrophic
  failure in the field due to these syscalls enabled and used.

  I would like to request if we can turn off COMPAT_32BIT_TIME on every
  architecture, thus this will be arch by arch bug report, and arch by
  arch decision.

  This needs to be a per-arch decision, potentially taking into
  consideration bi-arch userspace support.

  config COMPAT_32BIT_TIME
   bool "Provide system calls for 32-bit time_t"
   default !64BIT || COMPAT
   help
 This enables 32 bit time_t support in addition to 64 bit time_t support.
 This is relevant on all 32-bit architectures, and 64-bit architectures
 as part of compat syscall handling.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2038583/+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 2038985] Re: AMD W7900 dGFX boots into blank screen

[You-Sheng Yang]

*** This bug is a duplicate of bug 2038981 ***
https://bugs.launchpad.net/bugs/2038981

** This bug has been marked a duplicate of bug 2038981
   No external output when hotplugging to a DP monitor after the monitor went 
to sleep for AMD 6300 GPU

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

Title:
  AMD W7900 dGFX boots into blank screen

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in linux-oem-6.5 source package in Jammy:
  Triaged
Status in linux source package in Lunar:
  Confirmed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Confirmed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  Proposed fix: https://lore.kernel.org/linux-
  usb/20231009184643.129986-1-mario.limoncie...@amd.com/

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2038985/+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 2039173] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  tc goes to 100% CPU and locks up the system on recent 5.15 kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Install a new Ubuntu 22.04 Jammy system and run the following commands
  in a bash shell:

  sudo -i
  apt-get update && apt-get install -y iproute2  # often not necessary
  depmod -a
  modprobe ifb numifbs=1
  ip link add ifb0 type ifb
  ip link set dev ifb0 up
  tc qdisc add dev lo ingress
  tc filter add dev lo parent : protocol ip u32 match u32 0 0 action mirred 
egress redirect dev ifb0
  tc qdisc add dev lo root handle 1: htb 
  tc qdisc add dev ifb0 root handle 1: htb direct_qlen 1000
  echo "next command may lock up"
  tc qdisc add dev ifb0 parent 1:1 handle 10: netem limit 100 delay 100ms 20ms 
distribution normal

  and you will see tc's CPU usage go to 100% and soon after the entire
  system will lock up. tc in this state cannot be killed, even with kill
  -9.

  This happens on the October 10th version 
https://cloud-images.ubuntu.com/jammy/20231010/jammy-server-cloudimg-amd64.ova, 
which has kernel version 5.15.0-86-generic.
  It does not happen on the previous version 
https://cloud-images.ubuntu.com/jammy/20230929/jammy-server-cloudimg-amd64.ova, 
which has kernel version 5.15.0-84-generic.

  On the 5.15.0-84-generic version, the final TC command gives an error
  "Error: Specified class not found.". This is not seen on the
  "5.15.0-86-generic" version.

  Therefore I believe this is a regression between these two kernel
  versions 5.15.0-84 and 5.15.0-86. The tc binary is identical and the
  iproute2 library has the same version on both installations.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-86-generic 5.15.0-86.96
  ProcVersionSignature: Ubuntu 5.15.0-86.96-generic 5.15.122
  Uname: Linux 5.15.0-86-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 11 17:07 seq
   crw-rw 1 root audio 116, 33 Oct 11 17:07 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: ovf
  CloudName: ovf
  CloudPlatform: ovf
  CloudSubPlatform: ovf (iso)
  Date: Wed Oct 11 17:14:39 2023
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  PciMultimedia:
   
  ProcEnviron:
   TERM=vt100
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-86-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-86-generic N/A
   linux-backports-modules-5.15.0-86-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2018
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039173/+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 2039174] [NEW] Jammy update: v6.1.57 upstream stable release

[Timo Aaltonen]

Public bug reported:


SRU Justification

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

   v6.1.57 upstream stable release
   from git://git.kernel.org/


Linux 6.1.57
xen/events: replace evtchn_rwlock with RCU
ipv6: remove one read_lock()/read_unlock() pair in rt6_check_neigh()
btrfs: file_remove_privs needs an exclusive lock in direct io write
netlink: remove the flex array from struct nlmsghdr
btrfs: fix fscrypt name leak after failure to join log transaction
btrfs: fix an error handling path in btrfs_rename()
vrf: Fix lockdep splat in output path
ipv6: remove nexthop_fib6_nh_bh()
parisc: Restore __ldcw_align for PA-RISC 2.0 processors
ksmbd: fix uaf in smb20_oplock_break_ack
ksmbd: fix race condition between session lookup and expire
x86/sev: Use the GHCB protocol when available for SNP CPUID requests
RDMA/mlx5: Fix NULL string error
RDMA/mlx5: Fix mutex unlocking on error flow for steering anchor creation
RDMA/siw: Fix connection failure handling
RDMA/srp: Do not call scsi_done() from srp_abort()
RDMA/uverbs: Fix typo of sizeof argument
RDMA/cma: Fix truncation compilation warning in make_cma_ports
RDMA/cma: Initialize ib_sa_multicast structure to 0 when join
gpio: pxa: disable pinctrl calls for MMP_GPIO
gpio: aspeed: fix the GPIO number passed to pinctrl_gpio_set_config()
IB/mlx4: Fix the size of a buffer in add_port_entries()
of: dynamic: Fix potential memory leak in of_changeset_action()
RDMA/core: Require admin capabilities to set system parameters
dm zoned: free dmz->ddev array in dmz_put_zoned_devices
parisc: Fix crash with nr_cpus=1 option
smb: use kernel_connect() and kernel_bind()
intel_idle: add Emerald Rapids Xeon support
HID: intel-ish-hid: ipc: Disable and reenable ACPI GPE bit
HID: sony: remove duplicate NULL check before calling usb_free_urb()
netlink: annotate data-races around sk->sk_err
netlink: Fix potential skb memleak in netlink_ack
netlink: split up copies in the ack construction
sctp: update hb timer immediately after users change hb_interval
sctp: update transport state when processing a dupcook packet
tcp: fix delayed ACKs for MSS boundary condition
tcp: fix quick-ack counting to count actual ACKs of new data
tipc: fix a potential deadlock on >lock
net: stmmac: dwmac-stm32: fix resume on STM32 MCU
ipv4: Set offload_failed flag in fibmatch results
netfilter: nf_tables: nft_set_rbtree: fix spurious insertion failure
netfilter: nf_tables: Deduplicate nft_register_obj audit logs
selftests: netfilter: Extend nft_audit.sh
selftests: netfilter: Test nf_tables audit logging
netfilter: handle the connecting collision properly in nf_conntrack_proto_sctp
ibmveth: Remove condition to recompute TCP header checksum.
net: ethernet: ti: am65-cpsw: Fix error code in am65_cpsw_nuss_init_tx_chns()
net: nfc: llcp: Add lock when modifying device list
net: usb: smsc75xx: Fix uninit-value access in __smsc75xx_read_reg
ipv6: tcp: add a missing nf_reset_ct() in 3WHS handling
net: dsa: mv88e6xxx: Avoid EEPROM timeout when EEPROM is absent
ptp: ocp: Fix error handling in ptp_ocp_device_init
ipv4, ipv6: Fix handling of transhdrlen in __ip{,6}_append_data()
neighbour: fix data-races around n->output
neighbour: switch to standard rcu, instead of rcu_bh
neighbour: annotate lockless accesses to n->nud_state
bpf: Add BPF_FIB_LOOKUP_SKIP_NEIGH for bpf_fib_lookup
net: fix possible store tearing in neigh_periodic_work()
modpost: add missing else to the "of" check
bpf, sockmap: Reject sk_msg egress redirects to non-TCP sockets
bpf, sockmap: Do not inc copied_seq when PEEK flag set
bpf: tcp_read_skb needs to pop skb regardless of seq
NFSv4: Fix a nfs4_state_manager() race
ima: rework CONFIG_IMA dependency block
scsi: target: core: Fix deadlock due to recursive locking
ima: Finish deprecation of IMA_TRUSTED_KEYRING Kconfig
regulator/core: regulator_register: set device->class earlier
iommu/mediatek: Fix share pgtable for iova over 4GB
perf/x86/amd: Do not WARN() on every IRQ
wifi: mac80211: fix potential key use-after-free
regmap: rbtree: Fix wrong register marked as in-cache when creating new node
perf/x86/amd/core: Fix overflow reset on hotplug
wifi: mt76: mt76x02: fix MT76x0 external LNA gain handling
drivers/net: process the result of hdlc_open() and add call of hdlc_close() in 
uhdlc_close()
Bluetooth: ISO: Fix handling of listen for unicast
Bluetooth: Delete unused hci_req_prepare_suspend() declaration
regulator: mt6358: split ops for buck and linear range LDO regulators
regulator: mt6358: Use linear voltage helpers for single range regulators
regulator: mt6358: Drop *_SSHUB regulators
bpf: Fix tr 

[Kernel-packages] [Bug 2039173] [NEW] tc goes to 100% CPU and locks up the system on recent 5.15 kernels

[Thomas Walton]

Public bug reported:

Install a new Ubuntu 22.04 Jammy system and run the following commands
in a bash shell:

sudo -i
apt-get update && apt-get install -y iproute2  # often not necessary
depmod -a
modprobe ifb numifbs=1
ip link add ifb0 type ifb
ip link set dev ifb0 up
tc qdisc add dev lo ingress
tc filter add dev lo parent : protocol ip u32 match u32 0 0 action mirred 
egress redirect dev ifb0
tc qdisc add dev lo root handle 1: htb 
tc qdisc add dev ifb0 root handle 1: htb direct_qlen 1000
echo "next command may lock up"
tc qdisc add dev ifb0 parent 1:1 handle 10: netem limit 100 delay 100ms 20ms 
distribution normal

and you will see tc's CPU usage go to 100% and soon after the entire
system will lock up. tc in this state cannot be killed, even with kill
-9.

This happens on the October 10th version 
https://cloud-images.ubuntu.com/jammy/20231010/jammy-server-cloudimg-amd64.ova, 
which has kernel version 5.15.0-86-generic.
It does not happen on the previous version 
https://cloud-images.ubuntu.com/jammy/20230929/jammy-server-cloudimg-amd64.ova, 
which has kernel version 5.15.0-84-generic.

On the 5.15.0-84-generic version, the final TC command gives an error
"Error: Specified class not found.". This is not seen on the
"5.15.0-86-generic" version.

Therefore I believe this is a regression between these two kernel
versions 5.15.0-84 and 5.15.0-86. The tc binary is identical and the
iproute2 library has the same version on both installations.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-86-generic 5.15.0-86.96
ProcVersionSignature: Ubuntu 5.15.0-86.96-generic 5.15.122
Uname: Linux 5.15.0-86-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Oct 11 17:07 seq
 crw-rw 1 root audio 116, 33 Oct 11 17:07 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudID: ovf
CloudName: ovf
CloudPlatform: ovf
CloudSubPlatform: ovf (iso)
Date: Wed Oct 11 17:14:39 2023
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:
 
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: VMware, Inc. VMware Virtual Platform
PciMultimedia:
 
ProcEnviron:
 TERM=vt100
 PATH=(custom, no user)
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-86-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-86-generic N/A
 linux-backports-modules-5.15.0-86-generic  N/A
 linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/12/2018
dmi.bios.release: 4.6
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.ec.firmware.release: 0.0
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

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


** Tags: amd64 apport-bug jammy uec-images

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

Title:
  tc goes to 100% CPU and locks up the system on recent 5.15 kernels

Status in linux package in Ubuntu:
  New

Bug description:
  Install a new Ubuntu 22.04 Jammy system and run the following commands
  in a bash shell:

  sudo -i
  apt-get update && apt-get install -y iproute2  # often not necessary
  depmod -a
  modprobe ifb numifbs=1
  ip link add ifb0 type ifb
  ip link set dev ifb0 up
  tc qdisc add dev lo ingress
  tc filter add dev lo parent : protocol ip u32 match u32 0 0 action mirred 
egress redirect dev ifb0
  tc qdisc add dev lo root handle 1: htb 
  tc qdisc add dev ifb0 root handle 1: htb direct_qlen 1000
  echo "next command may lock up"
  tc qdisc add dev ifb0 parent 1:1 handle 10: netem limit 100 delay 100ms 20ms 
distribution normal

  and you will see tc's CPU usage go to 100% and soon after the entire
  system will lock up. tc in this state cannot be killed, even with kill
  -9.

  This happens on the October 10th version 

[Kernel-packages] [Bug 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)

[Dimitri John Ledkov]

** Changed in: apparmor (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: apparmor (Ubuntu Lunar)
   Status: Confirmed => Invalid

** Changed in: maas
   Status: Fix Committed => Fix Released

** Changed in: apparmor
   Status: Fix Committed => Fix Released

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

Title:
  udev fails to make prctl() syscall with apparmor=0 (as used by maas by
  default)

Status in AppArmor:
  Fix Released
Status in MAAS:
  Fix Released
Status in maas-images:
  Invalid
Status in apparmor package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in apparmor source package in Lunar:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in systemd source package in Lunar:
  Invalid

Bug description:
  I'm assuming the image being used for these deploys is 20230417 or
  20230417.1 based on the fact that I saw a 6.2 kernel being used which
  I don't believe was part of the 20230319 serial. I don't have access
  to the maas server, so I can't directly check any log files.

  MAAS Version: 3.3.2

  Here's where the serial log indicates it can't download the squashfs. The 
full log is attached as scobee-lunar-no-squashfs.log (there are some other 
console message intermixed):
  no search or nameservers found in /run/net-BOOTIF.conf /run/net-*.conf 
/run/net6
  -*.conf
  :: 
root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.04/lunar/candi
  date/squa[  206.804704] Btrfs loaded, crc32c=crc32c-generic, zoned=yes, 
fsverity
  =yes
  shfs
  :: mount_squash downloading 
http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.0
  4/lunar/candidate/squashfs to /root.tmp.img
  Connecting to 10.229.32.21:5248 (10.229.32.21:5248)
  wget: can't connect to remote host (10.229.32.21): Network is unreachable
  :: mount -t squashfs -o loop  '/root.tmp.img' '/root.tmp'
  mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory
  done.

  Still gathering logs and info and will update as I go.

  
  Kernel Bug / Apparmor
  reproducer

  $ wget 
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-kernel
  $ wget 
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-initrd
  $ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd 
./boot-initrd -append 'console=ttyS0 break=modules apparmor=0'

  #start the VM
  
  Starting systemd-udevd version 252.5-2ubuntu3
  Spawning shell within the initramfs

  BusyBox v1.35.0 (Ubuntu 1:1.35.0-4ubuntu1) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  (initramfs) udevadm info --export-db
  Failed to set death signal: Invalid argument

  Observe that udevadm fails to setup death signal, with in systemd code
  is this

  
https://github.com/systemd/systemd/blob/08c2f9c626e0f0052d505b1b7e52f335c0fbfa1d/src/basic/process-
  util.c#L1252

  if (flags & (FORK_DEATHSIG|FORK_DEATHSIG_SIGINT))
  if (prctl(PR_SET_PDEATHSIG, (flags & FORK_DEATHSIG_SIGINT) ? 
SIGINT : SIGTERM) < 0) {
  log_full_errno(prio, errno, "Failed to set death 
signal: %m");
  _exit(EXIT_FAILURE);
  }

  
  workaround set kernel commandline to `apparmor=1`
  

  MAAS bug
  Why is maas setting `apparmor=0` ? Ubuntu shouldn't be used without apparmor. 
Even for deployment and commisioning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/2016908/+subscriptions


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

[Kernel-packages] [Bug 2039167] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  I get this message "array-index-out-of-bounds"  every time I turn on
  my laptop since I upgraded from 23.04. to 23.10.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  UBSAN: array-index-out-of-bounds in 
/build/linux-D15vQj/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:929:40
  index 1 is out of range for type 'UCHAR [1]'

  My firmware version is X515DAP.311.
  OS type 64-bit.
  GNOME version 45.0.
  Kernel version Linux 6.5.0-9-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zoran  2329 F wireplumber
   /dev/snd/controlC0:  zoran  2329 F wireplumber
   /dev/snd/seq:zoran  2316 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 12 13:42:16 2023
  InstallationDate: Installed on 2023-09-21 (21 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=9b0c8205-22d2-4c7e-8e53-959a91e2174d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-10-12 (0 days ago)
  dmi.bios.date: 01/06/2023
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X515DAP.311
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X515DAP
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX515DAP.311:bd01/06/2023:br5.14:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX515DAP_M515DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX515DAP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ASUSLaptop
  dmi.product.name: VivoBook_ASUSLaptop X515DAP_M515DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039167/+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 2039167] [NEW] I get this message "array-index-out-of-bounds" every time I turn on my laptop since I upgraded from 23.04. to 23.10.

[Zoran Nikolov]

Public bug reported:

UBSAN: array-index-out-of-bounds in 
/build/linux-D15vQj/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:929:40
index 1 is out of range for type 'UCHAR [1]'

My firmware version is X515DAP.311.
OS type 64-bit.
GNOME version 45.0.
Kernel version Linux 6.5.0-9-generic.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  zoran  2329 F wireplumber
 /dev/snd/controlC0:  zoran  2329 F wireplumber
 /dev/snd/seq:zoran  2316 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 12 13:42:16 2023
InstallationDate: Installed on 2023-09-21 (21 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=9b0c8205-22d2-4c7e-8e53-959a91e2174d ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-6.5.0-9-generic N/A
 linux-backports-modules-6.5.0-9-generic  N/A
 linux-firmware   20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-10-12 (0 days ago)
dmi.bios.date: 01/06/2023
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X515DAP.311
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X515DAP
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX515DAP.311:bd01/06/2023:br5.14:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX515DAP_M515DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX515DAP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: ASUSLaptop
dmi.product.name: VivoBook_ASUSLaptop X515DAP_M515DA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug mantic wayland-session

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

Title:
  I get this message "array-index-out-of-bounds"  every time I turn on
  my laptop since I upgraded from 23.04. to 23.10.

Status in linux package in Ubuntu:
  New

Bug description:
  UBSAN: array-index-out-of-bounds in 
/build/linux-D15vQj/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:929:40
  index 1 is out of range for type 'UCHAR [1]'

  My firmware version is X515DAP.311.
  OS type 64-bit.
  GNOME version 45.0.
  Kernel version Linux 6.5.0-9-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zoran  2329 F wireplumber
   /dev/snd/controlC0:  zoran  2329 F wireplumber
   /dev/snd/seq:zoran  2316 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 12 13:42:16 2023
  InstallationDate: Installed on 2023-09-21 (21 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=9b0c8205-22d2-4c7e-8e53-959a91e2174d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-10-12 (0 days ago)
  dmi.bios.date: 01/06/2023
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X515DAP.311
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X515DAP
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX515DAP.311:bd01/06/2023:br5.14:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX515DAP_M515DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX515DAP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ASUSLaptop
  

[Kernel-packages] [Bug 2037065] Re: Wifi not working on StarFive VisionFive

[Launchpad Bug Tracker]

*** This bug is a duplicate of bug 2038546 ***
https://bugs.launchpad.net/bugs/2038546

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

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

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

Title:
  Wifi not working on StarFive VisionFive

Status in linux-starfive package in Ubuntu:
  Confirmed

Bug description:
  I am currently testing http://cdimage.ubuntu.com/ubuntu-server/daily-
  preinstalled/20230920/mantic-preinstalled-server-
  riscv64+visionfive.img.xz according to
  
http://iso.qa.ubuntu.com/qatracker/milestones/448/builds/287116/testcases/1754/results

  'nmcli dev wifi list' and 'ip a' do not show the WiFi device.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-5.19.0-1014-starfive 5.19.0-1014.16
  ProcVersionSignature: Ubuntu 5.19.0-1014.16-starfive 5.19.17
  Uname: Linux 5.19.0-1014-starfive riscv64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230920
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Fri Sep 22 09:05:10 2023
  ProcCpuinfoMinimal:
   processor: 1
   hart : 0
   isa  : rv64imafdc
   mmu  : sv39
   uarch: sifive,u74-mc
  SourcePackage: linux-starfive
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2038567] Re: Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature

[Launchpad Bug Tracker]

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

** Changed in: apparmor (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/2038567

Title:
  Disable restricting unprivileged change_profile by default, due to LXD
  latest/stable not yet compatible with this new apparmor feature

Status in Release Notes for Ubuntu:
  New
Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Triaged
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  Following upgrade to 6.5.0-7 kernel in mantic cloud images we are
  seeing a regression in our cloud image tests. The test runs the
  following:

  ```
  lxd init --auto --storage-backend dir
  lxc launch ubuntu-daily:mantic mantic
  lxc info mantic
  lxc exec mantic -- cloud-init status --wait
  ```

  The `lxc exec mantic -- cloud-init status --wait` times out after 240s
  and will fail our test as a result.

  I have been able to replicate in a local VM

  ```
  wget 
http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img 
  wget --output-document=launch-qcow2-image-qemu.sh 
https://gist.githubusercontent.com/philroche/14c241c086a5730481e24178b654268f/raw/7af95cd4dfc8e1d0600e6118803d2c866765714e/gistfile1.txt
 
  chmod +x launch-qcow2-image-qemu.sh 

  ./launch-qcow2-image-qemu.sh --password passw0rd --image 
./mantic-server-cloudimg-amd64.img 
  cat < "./reproducer.sh"
  #!/bin/bash -eux
  lxd init --auto --storage-backend dir
  lxc launch ubuntu-daily:mantic mantic
  lxc info mantic
  lxc exec mantic -- cloud-init status --wait
  EOF
  chmod +x ./reproducer.sh
  sshpass -p passw0rd scp -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -P  ./reproducer.sh ubuntu@127.0.0.1:~/
  sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -p  ubuntu@127.0.0.1 sudo apt-get update
  sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -p  ubuntu@127.0.0.1 sudo apt-get upgrade 
--assume-yes
  sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -p  ubuntu@127.0.0.1 ./reproducer.sh
  ```

  The issue is not present with the 6.5.0-5 kernel and the issue is
  present regardless of the container launched. I tried the jammy
  container to test this.

  From my test VM

  ```
  ubuntu@cloudimg:~$ uname --all
  Linux cloudimg 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 29 
09:14:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
  ubuntu@cloudimg:~$ uname --kernel-release
  6.5.0-7-generic
  ```

  This is a regression in our test that will block 23.10 cloud image
  release next week.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038567/+subscriptions


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

[Kernel-packages] [Bug 2038567] Re: Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature

[Launchpad Bug Tracker]

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

** Changed in: snapd (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/2038567

Title:
  Disable restricting unprivileged change_profile by default, due to LXD
  latest/stable not yet compatible with this new apparmor feature

Status in Release Notes for Ubuntu:
  New
Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Triaged
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  Following upgrade to 6.5.0-7 kernel in mantic cloud images we are
  seeing a regression in our cloud image tests. The test runs the
  following:

  ```
  lxd init --auto --storage-backend dir
  lxc launch ubuntu-daily:mantic mantic
  lxc info mantic
  lxc exec mantic -- cloud-init status --wait
  ```

  The `lxc exec mantic -- cloud-init status --wait` times out after 240s
  and will fail our test as a result.

  I have been able to replicate in a local VM

  ```
  wget 
http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img 
  wget --output-document=launch-qcow2-image-qemu.sh 
https://gist.githubusercontent.com/philroche/14c241c086a5730481e24178b654268f/raw/7af95cd4dfc8e1d0600e6118803d2c866765714e/gistfile1.txt
 
  chmod +x launch-qcow2-image-qemu.sh 

  ./launch-qcow2-image-qemu.sh --password passw0rd --image 
./mantic-server-cloudimg-amd64.img 
  cat < "./reproducer.sh"
  #!/bin/bash -eux
  lxd init --auto --storage-backend dir
  lxc launch ubuntu-daily:mantic mantic
  lxc info mantic
  lxc exec mantic -- cloud-init status --wait
  EOF
  chmod +x ./reproducer.sh
  sshpass -p passw0rd scp -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -P  ./reproducer.sh ubuntu@127.0.0.1:~/
  sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -p  ubuntu@127.0.0.1 sudo apt-get update
  sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -p  ubuntu@127.0.0.1 sudo apt-get upgrade 
--assume-yes
  sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -p  ubuntu@127.0.0.1 ./reproducer.sh
  ```

  The issue is not present with the 6.5.0-5 kernel and the issue is
  present regardless of the container launched. I tried the jammy
  container to test this.

  From my test VM

  ```
  ubuntu@cloudimg:~$ uname --all
  Linux cloudimg 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 29 
09:14:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
  ubuntu@cloudimg:~$ uname --kernel-release
  6.5.0-7-generic
  ```

  This is a regression in our test that will block 23.10 cloud image
  release next week.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038567/+subscriptions


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

[Kernel-packages] [Bug 2033441] Re: linux-firmware is outdated

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.21

---
linux-firmware (20220329.git681281e4-0ubuntu3.21) jammy; urgency=medium

  * linux-firmware is outdated (LP: #2033441)
- nvidia: update Tu10x and Tu11x signed firmware to support newer Turing HW
  * NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox) 
driver installed (LP: #2038745)
- amdgpu: update SMU 13.0.0 firmware for amd.5.5 release
- amdgpu: update SMU 13.0.7 firmware for amd.5.5 release

linux-firmware (20220329.git681281e4-0ubuntu3.20) jammy; urgency=medium

  * Multiple RTL8851BE BT stability issues (LP: #2037224)
- rtl_bt: Update RTL8851B BT USB firmware to 0x048A_D230

 -- Juerg Haefliger   Tue, 10 Oct 2023
11:34:40 +0200

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

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

Title:
  linux-firmware is outdated

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-firmware source package in Lunar:
  Fix Released
Status in linux-firmware source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  This is optimus laptop with Intel 11th Gen and Nvidia.
  In recent kernels like 6.2.0 it gives a blank screen after booting and if 
nouveau.modset=1 is set, it completely freeze the system.

  I remember it was working fine in 5.x kernels.
  Now I have to blacklist nouveau and use Nvidia driver instead.

  Using this commit of linux-firmware solved the issue:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/nvidia?id=2e92a49f90f73c8edc44b25c6e669d5e70893c90

  [Fix]

  Upstream commit 2e92a49f90f9 ("nvidia: update Tu10x and Tu11x signed
  firmware to support newer Turing HW")

  [Test Case]

  Boot a machine with relevant GPU.

  [Where Problems Could Occur]

  Updated Nvidia FW so limited to machines with relevant GPUs.

  [Additional Information]

  # journalctl -b -2 | grep nouveau
  Aug 29 21:07:54 ZB kernel: Command line: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic 
root=/dev/mapper/vgubuntu-root ro nouveau.modeset=1 quiet splash
  Aug 29 21:07:54 ZB kernel: Kernel command line: 
BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgubuntu-root ro 
nouveau.modeset=1 quiet splash
  Aug 29 21:07:54 ZB kernel: nouveau: detected PR support, will not use DSM
  Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: enabling device ( -> 
0003)
  Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: NVIDIA TU117 (167000a1)
  Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: bios: version 90.17.61.00.73
  Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: pmu: firmware unavailable
  Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: fb: 2048 MiB GDDR6
  Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: halted
  Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC SCTL 7021 
TIDX 1b1f
  Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 23ac
  Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2055
  Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2305
  Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 201c
  Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2303
  Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2051
  Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 269e
  Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2617
  Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25e8
  Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b2
  Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
  Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
  Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
  Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
  Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
  Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
  Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
  Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
  Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
  Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
  Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
  Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
  Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
  Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
  Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
  

[Kernel-packages] [Bug 2037224] Re: Multiple RTL8851BE BT stability issues

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.21

---
linux-firmware (20220329.git681281e4-0ubuntu3.21) jammy; urgency=medium

  * linux-firmware is outdated (LP: #2033441)
- nvidia: update Tu10x and Tu11x signed firmware to support newer Turing HW
  * NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox) 
driver installed (LP: #2038745)
- amdgpu: update SMU 13.0.0 firmware for amd.5.5 release
- amdgpu: update SMU 13.0.7 firmware for amd.5.5 release

linux-firmware (20220329.git681281e4-0ubuntu3.20) jammy; urgency=medium

  * Multiple RTL8851BE BT stability issues (LP: #2037224)
- rtl_bt: Update RTL8851B BT USB firmware to 0x048A_D230

 -- Juerg Haefliger   Tue, 10 Oct 2023
11:34:40 +0200

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

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

Title:
  Multiple RTL8851BE BT stability issues

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-firmware source package in Mantic:
  Fix Committed

Bug description:
  [SRU Justification]

  [Impact]

  There are multiple stability issues for RTL8851B.

  Issue-1:

  After disabling BT and leaving it idle for a period, manually turning on the
  RTL8851BE will fail.

  Issue-2:

  Failed to probe Bluetooth USB interface after resumed from suspend. There may 
be
  either failure to read device descriptors:

usb 1-14: device descriptor read/64, error -71

  or tx command timeout:

Bluetooth: hci0: Opcode 0x2041 failed: -110
Bluetooth: hci0: command 0x2041 tx timeout

  [Fix]

  Upstream commit addc33924 ("rtl_bt: Update RTL8851B BT USB firmware to
  0x048A_D230").

  [Test Case]

  $ checkbox-cli run
  com.canonical.plainbox::suspend/suspend_advanced_auto

  [Where problems could occur]

  This updates opaque firmware blobs, so it could bring further stability issues
  and/or power consumption changes.

  [Other Info]

  While RTL8851B is only supported in oem-6.5 and linux/mantic >= 6.4, only 
jammy
  and mantic are nominated for fix.

  = original bug report ==

  [issue 1]

  After disabling BT and leaving it idle for a period, manually turning
  on the RTL8851BE will fail. (Can't reproduce on Wifi functionality.)

  Test step:
  1. Insert RTL8851BE Wifi card and install Ubuntu 22.04 OS. (Kernel : 6.5.0)
  2. Check BT function after boot into OS.
  3. Manually turn OFF BT function. Then wait for 1 minute.
  4. Manually turn ON the BT function.
  5. Unable to enable BT function. (issue occurs)

  [issue 2]

  System usb got tx command timeout after suspend resume.

  Log:

  Got read usb descriptor fail after suspend resume.

  Sep 11 16:37:37 ubuntu kernel: usb 1-14: reset full-speed USB device number 3 
using xhci_hcd
  Sep 11 16:37:37 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
  Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
  Sep 11 16:37:38 ubuntu kernel: usb 1-14: reset full-speed USB device number 3 
using xhci_hcd
  Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
  Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
  Sep 11 16:37:39 ubuntu kernel: usb 1-14: reset full-speed USB device number 3 
using xhci_hcd

  And tx command timeout.

  Sep 11 16:37:41 ubuntu kernel: Bluetooth: hci0: Opcode 0x2041 failed: -110
  Sep 11 16:37:41 ubuntu kernel: Bluetooth: hci0: command 0x2041 tx timeout
  Sep 11 16:37:41 ubuntu kernel: usb 1-14: new full-speed USB device number 4 
using xhci_hcd
  Sep 11 16:37:41 ubuntu kernel: usb 1-14: device descriptor read/64, error -71

  Test step:
  1. Install dell-bto-jammy-jellyfish-abra-X96-20230822-1.iso
  2. Boot into OS
  3. checkbox-cli run com.canonical.plainbox::suspend/suspend_advanced_auto

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

[Timo Aaltonen]

The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Multiple RTL8851BE BT stability issues

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-firmware source package in Mantic:
  Fix Committed

Bug description:
  [SRU Justification]

  [Impact]

  There are multiple stability issues for RTL8851B.

  Issue-1:

  After disabling BT and leaving it idle for a period, manually turning on the
  RTL8851BE will fail.

  Issue-2:

  Failed to probe Bluetooth USB interface after resumed from suspend. There may 
be
  either failure to read device descriptors:

usb 1-14: device descriptor read/64, error -71

  or tx command timeout:

Bluetooth: hci0: Opcode 0x2041 failed: -110
Bluetooth: hci0: command 0x2041 tx timeout

  [Fix]

  Upstream commit addc33924 ("rtl_bt: Update RTL8851B BT USB firmware to
  0x048A_D230").

  [Test Case]

  $ checkbox-cli run
  com.canonical.plainbox::suspend/suspend_advanced_auto

  [Where problems could occur]

  This updates opaque firmware blobs, so it could bring further stability issues
  and/or power consumption changes.

  [Other Info]

  While RTL8851B is only supported in oem-6.5 and linux/mantic >= 6.4, only 
jammy
  and mantic are nominated for fix.

  = original bug report ==

  [issue 1]

  After disabling BT and leaving it idle for a period, manually turning
  on the RTL8851BE will fail. (Can't reproduce on Wifi functionality.)

  Test step:
  1. Insert RTL8851BE Wifi card and install Ubuntu 22.04 OS. (Kernel : 6.5.0)
  2. Check BT function after boot into OS.
  3. Manually turn OFF BT function. Then wait for 1 minute.
  4. Manually turn ON the BT function.
  5. Unable to enable BT function. (issue occurs)

  [issue 2]

  System usb got tx command timeout after suspend resume.

  Log:

  Got read usb descriptor fail after suspend resume.

  Sep 11 16:37:37 ubuntu kernel: usb 1-14: reset full-speed USB device number 3 
using xhci_hcd
  Sep 11 16:37:37 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
  Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
  Sep 11 16:37:38 ubuntu kernel: usb 1-14: reset full-speed USB device number 3 
using xhci_hcd
  Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
  Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
  Sep 11 16:37:39 ubuntu kernel: usb 1-14: reset full-speed USB device number 3 
using xhci_hcd

  And tx command timeout.

  Sep 11 16:37:41 ubuntu kernel: Bluetooth: hci0: Opcode 0x2041 failed: -110
  Sep 11 16:37:41 ubuntu kernel: Bluetooth: hci0: command 0x2041 tx timeout
  Sep 11 16:37:41 ubuntu kernel: usb 1-14: new full-speed USB device number 4 
using xhci_hcd
  Sep 11 16:37:41 ubuntu kernel: usb 1-14: device descriptor read/64, error -71

  Test step:
  1. Install dell-bto-jammy-jellyfish-abra-X96-20230822-1.iso
  2. Boot into OS
  3. checkbox-cli run com.canonical.plainbox::suspend/suspend_advanced_auto

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2037224/+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 2038893] Re: probe-bcache[132]: unhandled signal 11 code 0x1 at 0x0038004000000004

[Launchpad Bug Tracker]

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

** Changed in: bcache-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  probe-bcache[132]: unhandled signal 11 code 0x1 at 0x00380044

Status in bcache-tools package in Ubuntu:
  Confirmed
Status in linux-riscv package in Ubuntu:
  Confirmed

Bug description:
  Running http://cdimage.ubuntu.com/ubuntu-server/daily-
  preinstalled/20231010/mantic-preinstalled-server-riscv64.img.xz on
  QEMU with

  qemu-system-riscv64 -machine virt -nographic -m 2048 -smp 4 -bios
  /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin -kernel
  /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf -device virtio-net-
  device,netdev=eth0 -netdev user,id=eth0 -device virtio-rng-pci -drive
  file=mantic-preinstalled-server-riscv64.img,format=raw,if=virtio

  a crash was reported:

  Starting systemd-udevd version 253.5-1ubuntu6
  [3.919909] probe-bcache[132]: unhandled signal 11 code 0x1 at 
0x00380044
  [3.920554] CPU: 3 PID: 132 Comm: probe-bcache Not tainted 6.5.0-9-generic 
#9.1-Ubuntu
  [3.921064] Hardware name: riscv-virtio,qemu (DT)
  [3.921382] epc : 00380044 ra : 7fffadf8ac82 sp : 
7fffce174160
  [3.921750]  gp : 5fd56800 tp : 7fffade18780 t0 : 
1000
  [3.922110]  t1 : 5fd53a3c t2 : 0034e6b4 s0 : 
7fffae006ae0
  [3.922422]  s1 : 7fffce174c78 a0 : 7fffce174178 a1 : 
7fffae006ae0
  [3.922751]  a2 : 00022560 a3 : 7fff a4 : 

  [3.923121]  a5 : 00380045 a6 : 0007d436 a7 : 
001d
  [3.923576]  s2 : 0001 s3 : 7fffae005d80 s4 : 
0003
  [3.923913]  s5 : 7d4352a0 s6 :  s7 : 
7fffce174160
  [3.924251]  s8 : 7fffce174a30 s9 : 7fffadfb86f0 s10: 
7fffce174178
  [3.924585]  s11: 7fffce174188 t3 : 7fffadf8abe8 t4 : 

  [3.924897]  t5 : 7fffadfdda40 t6 : 7fffadfde028
  [3.925090] status: 00024020 badaddr: 00380044 cause: 
000c
  [3.933878] probe-bcache[130]: unhandled signal 11 code 0x1 at 
0x00380044
  [3.934386] CPU: 1 PID: 130 Comm: probe-bcache Not tainted 6.5.0-9-generic 
#9.1-Ubuntu
  [3.934742] Hardware name: riscv-virtio,qemu (DT)
  [3.934974] epc : 00380044 ra : 7fff9b9acc82 sp : 
7fffe3a88160
  [3.935316]  gp : 91f30800 tp : 7fff9b83a780 t0 : 
1000
  [3.935869]  t1 : 91f2da3c t2 : 0034e6b4 s0 : 
7fff9ba28ae0
  [3.936224]  s1 : 7fffe3a88c78 a0 : 7fffe3a88178 a1 : 
7fff9ba28ae0
  [3.936606]  a2 : 00022560 a3 : 7fff a4 : 

  [3.937030]  a5 : 00380045 a6 : 000b3fa0 a7 : 
001d
  [3.937443]  s2 : 0001 s3 : 7fff9ba27d80 s4 : 
0003
  [3.937868]  s5 : b3f9f2a0 s6 :  s7 : 
7fffe3a88160
  [3.938261]  s8 : 7fffe3a88a30 s9 : 7fff9b9da6f0 s10: 
7fffe3a88178
  [3.938681]  s11: 7fffe3a88188 t3 : 7fff9b9acbe8 t4 : 

  [3.939113]  t5 : 7fff9b9ffa40 t6 : 7fff9ba00028
  [3.939469] status: 00024020 badaddr: 00380044 cause: 
000c
  [3.951861] probe-bcache[129]: unhandled signal 11 code 0x1 at 
0x00380044
  [3.952290] CPU: 0 PID: 129 Comm: probe-bcache Not tainted 6.5.0-9-generic 
#9.1-Ubuntu
  [3.952680] Hardware name: riscv-virtio,qemu (DT)
  [3.952887] epc : 00380044 ra : 7fff86598c82 sp : 
7fffea625160
  [3.953236]  gp : 74eb1800 tp : 7fff86426780 t0 : 
1000
  [3.953582]  t1 : 74eaea3c t2 : 0034e6b4 s0 : 
7fff86614ae0
  [3.953936]  s1 : 7fffea625c78 a0 : 7fffea625178 a1 : 
7fff86614ae0
  [3.954302]  a2 : 00022560 a3 : 7fff a4 : 

  [3.954700]  a5 : 00380045 a6 : 0009411b a7 : 
001d
  [3.955114]  s2 : 0001 s3 : 7fff86613d80 s4 : 
0003
  [3.955657]  s5 : 9411a2a0 s6 :  s7 : 
7fffea625160
  [3.956018]  s8 : 7fffea625a30 s9 : 7fff865c66f0 s10: 
7fffea625178
  [3.956368]  s11: 7fffea625188 t3 : 7fff86598be8 t4 : 

  [3.956741]  t5 : 7fff865eba40 t6 : 7fff865ec028
  [3.957026] status: 00024020 badaddr: 00380044 cause: 
000c
  Begin: Loading essential drivers ... [6.255484] raid6: int64x8  gen()   
635 MB/s

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  

[Kernel-packages] [Bug 2038745] Update Released

[Timo Aaltonen]

The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox)
  driver installed

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-firmware source package in Lunar:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Released

Bug description:
  [Impact]


  NV31 XTX/XTW cannot boot into Ubuntu 22.04.3 after upgrading distro to
  latest Ubuntu 22.04.3 kernel and firmware


  Not repro with NV21 XL or W6800



  [Fix]
  Cherry-pick the latest PMFW 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/smu_13_0_0.bin



  [Other Info]


  The IMU FW included in Linux firmware package needs to be paired with
  the latest PMFW smu_13_0_0.bin for Navi31

  Jammy firmware updates only include latest IMU firmware.


  https://www.ubuntuupdates.org/package/core/jammy/main/updates/linux-
  firmware


  20220329.git681281e4-0ubuntu3.19


  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/gc_11_0_0_imu.bin
  (Missing) 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/smu_13_0_0.bin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038745/+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 2038745] Re: NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox) driver installed

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.21

---
linux-firmware (20220329.git681281e4-0ubuntu3.21) jammy; urgency=medium

  * linux-firmware is outdated (LP: #2033441)
- nvidia: update Tu10x and Tu11x signed firmware to support newer Turing HW
  * NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox) 
driver installed (LP: #2038745)
- amdgpu: update SMU 13.0.0 firmware for amd.5.5 release
- amdgpu: update SMU 13.0.7 firmware for amd.5.5 release

linux-firmware (20220329.git681281e4-0ubuntu3.20) jammy; urgency=medium

  * Multiple RTL8851BE BT stability issues (LP: #2037224)
- rtl_bt: Update RTL8851B BT USB firmware to 0x048A_D230

 -- Juerg Haefliger   Tue, 10 Oct 2023
11:34:40 +0200

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

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

Title:
  NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox)
  driver installed

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-firmware source package in Lunar:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Released

Bug description:
  [Impact]


  NV31 XTX/XTW cannot boot into Ubuntu 22.04.3 after upgrading distro to
  latest Ubuntu 22.04.3 kernel and firmware


  Not repro with NV21 XL or W6800



  [Fix]
  Cherry-pick the latest PMFW 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/smu_13_0_0.bin



  [Other Info]


  The IMU FW included in Linux firmware package needs to be paired with
  the latest PMFW smu_13_0_0.bin for Navi31

  Jammy firmware updates only include latest IMU firmware.


  https://www.ubuntuupdates.org/package/core/jammy/main/updates/linux-
  firmware


  20220329.git681281e4-0ubuntu3.19


  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/gc_11_0_0_imu.bin
  (Missing) 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/smu_13_0_0.bin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038745/+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 2038765] Re: df: /sys/firmware/efi/efivars: Invalid argument causes error on login/live session

[Launchpad Bug Tracker]

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

** Changed in: lightdm (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/2038765

Title:
  df: /sys/firmware/efi/efivars: Invalid argument causes error on
  login/live session

Status in lightdm package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  df: /sys/firmware/efi/efivars: Invalid argument appears on first
  display of the  live session - I note subsequently that at the end of
  the installation curtin fails due to an efivars error - looking at
  syslog I saw various efivars errors so I'm filing this with the kernel
  since this is the first instance.

  Note - raised separate issue for the installation crash which has now
  been duplicated against
  https://bugs.launchpad.net/subiquity/+bug/2003222

  i.e. running grep efivars /var/log/*

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-7-generic 6.5.0-7.7
  ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
  Uname: Linux 6.5.0-7-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu-budgie   2077 F wireplumber
   /dev/snd/seq:ubuntu-budgie   2074 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CasperVersion: 1.486
  CurrentDesktop: Budgie:GNOME
  Date: Sun Oct  8 16:27:29 2023
  LiveMediaBuild: Ubuntu-Budgie 23.10 "Mantic Minotaur" - Daily amd64 
(20231008.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
layerfs-path=minimal.standard.live.squashfs --- quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-7-generic N/A
   linux-backports-modules-6.5.0-7-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP91.88Z.00D9.B00.1802021100
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-6F01561E16C75D06
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro9,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-6F01561E16C75D06
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP91.88Z.00D9.B00.1802021100:bd02/02/2018:br0.1:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:skuSystemSKU#:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro9,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/2038765/+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 2038893] Re: probe-bcache[132]: unhandled signal 11 code 0x1 at 0x0038004000000004

[Launchpad Bug Tracker]

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

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

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

Title:
  probe-bcache[132]: unhandled signal 11 code 0x1 at 0x00380044

Status in bcache-tools package in Ubuntu:
  Confirmed
Status in linux-riscv package in Ubuntu:
  Confirmed

Bug description:
  Running http://cdimage.ubuntu.com/ubuntu-server/daily-
  preinstalled/20231010/mantic-preinstalled-server-riscv64.img.xz on
  QEMU with

  qemu-system-riscv64 -machine virt -nographic -m 2048 -smp 4 -bios
  /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin -kernel
  /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf -device virtio-net-
  device,netdev=eth0 -netdev user,id=eth0 -device virtio-rng-pci -drive
  file=mantic-preinstalled-server-riscv64.img,format=raw,if=virtio

  a crash was reported:

  Starting systemd-udevd version 253.5-1ubuntu6
  [3.919909] probe-bcache[132]: unhandled signal 11 code 0x1 at 
0x00380044
  [3.920554] CPU: 3 PID: 132 Comm: probe-bcache Not tainted 6.5.0-9-generic 
#9.1-Ubuntu
  [3.921064] Hardware name: riscv-virtio,qemu (DT)
  [3.921382] epc : 00380044 ra : 7fffadf8ac82 sp : 
7fffce174160
  [3.921750]  gp : 5fd56800 tp : 7fffade18780 t0 : 
1000
  [3.922110]  t1 : 5fd53a3c t2 : 0034e6b4 s0 : 
7fffae006ae0
  [3.922422]  s1 : 7fffce174c78 a0 : 7fffce174178 a1 : 
7fffae006ae0
  [3.922751]  a2 : 00022560 a3 : 7fff a4 : 

  [3.923121]  a5 : 00380045 a6 : 0007d436 a7 : 
001d
  [3.923576]  s2 : 0001 s3 : 7fffae005d80 s4 : 
0003
  [3.923913]  s5 : 7d4352a0 s6 :  s7 : 
7fffce174160
  [3.924251]  s8 : 7fffce174a30 s9 : 7fffadfb86f0 s10: 
7fffce174178
  [3.924585]  s11: 7fffce174188 t3 : 7fffadf8abe8 t4 : 

  [3.924897]  t5 : 7fffadfdda40 t6 : 7fffadfde028
  [3.925090] status: 00024020 badaddr: 00380044 cause: 
000c
  [3.933878] probe-bcache[130]: unhandled signal 11 code 0x1 at 
0x00380044
  [3.934386] CPU: 1 PID: 130 Comm: probe-bcache Not tainted 6.5.0-9-generic 
#9.1-Ubuntu
  [3.934742] Hardware name: riscv-virtio,qemu (DT)
  [3.934974] epc : 00380044 ra : 7fff9b9acc82 sp : 
7fffe3a88160
  [3.935316]  gp : 91f30800 tp : 7fff9b83a780 t0 : 
1000
  [3.935869]  t1 : 91f2da3c t2 : 0034e6b4 s0 : 
7fff9ba28ae0
  [3.936224]  s1 : 7fffe3a88c78 a0 : 7fffe3a88178 a1 : 
7fff9ba28ae0
  [3.936606]  a2 : 00022560 a3 : 7fff a4 : 

  [3.937030]  a5 : 00380045 a6 : 000b3fa0 a7 : 
001d
  [3.937443]  s2 : 0001 s3 : 7fff9ba27d80 s4 : 
0003
  [3.937868]  s5 : b3f9f2a0 s6 :  s7 : 
7fffe3a88160
  [3.938261]  s8 : 7fffe3a88a30 s9 : 7fff9b9da6f0 s10: 
7fffe3a88178
  [3.938681]  s11: 7fffe3a88188 t3 : 7fff9b9acbe8 t4 : 

  [3.939113]  t5 : 7fff9b9ffa40 t6 : 7fff9ba00028
  [3.939469] status: 00024020 badaddr: 00380044 cause: 
000c
  [3.951861] probe-bcache[129]: unhandled signal 11 code 0x1 at 
0x00380044
  [3.952290] CPU: 0 PID: 129 Comm: probe-bcache Not tainted 6.5.0-9-generic 
#9.1-Ubuntu
  [3.952680] Hardware name: riscv-virtio,qemu (DT)
  [3.952887] epc : 00380044 ra : 7fff86598c82 sp : 
7fffea625160
  [3.953236]  gp : 74eb1800 tp : 7fff86426780 t0 : 
1000
  [3.953582]  t1 : 74eaea3c t2 : 0034e6b4 s0 : 
7fff86614ae0
  [3.953936]  s1 : 7fffea625c78 a0 : 7fffea625178 a1 : 
7fff86614ae0
  [3.954302]  a2 : 00022560 a3 : 7fff a4 : 

  [3.954700]  a5 : 00380045 a6 : 0009411b a7 : 
001d
  [3.955114]  s2 : 0001 s3 : 7fff86613d80 s4 : 
0003
  [3.955657]  s5 : 9411a2a0 s6 :  s7 : 
7fffea625160
  [3.956018]  s8 : 7fffea625a30 s9 : 7fff865c66f0 s10: 
7fffea625178
  [3.956368]  s11: 7fffea625188 t3 : 7fff86598be8 t4 : 

  [3.956741]  t5 : 7fff865eba40 t6 : 7fff865ec028
  [3.957026] status: 00024020 badaddr: 00380044 cause: 
000c
  Begin: Loading essential drivers ... [6.255484] raid6: int64x8  gen()   
635 MB/s

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  

[Kernel-packages] [Bug 2038920] Re: Nezha D1: usb 1-1: device descriptor read/64, error -71

[Launchpad Bug Tracker]

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

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

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

Title:
  Nezha D1: usb 1-1: device descriptor read/64, error -71

Status in linux-riscv package in Ubuntu:
  Confirmed

Bug description:
  On the Nezha D1 board USB does not work correctly.

  I have connected a USB keyboard and get errors like:

  [ 4458.313671] usb 1-1: device descriptor read/64, error -71
  [ 4459.189686] usb 1-1: device descriptor read/64, error -71
  [ 4460.157594] usb 4-1: device descriptor read/64, error -62
  [ 4460.461621] usb 4-1: device descriptor read/64, error -62
  [ 4460.953646] usb 4-1: device descriptor read/64, error -62
  [ 4461.257626] usb 4-1: device descriptor read/64, error -62

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
  Uname: Linux 6.5.0-9-generic riscv64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20231010
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue Oct 10 12:20:40 2023
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2038920/+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 2038933] Re: sun8i-dw-hdmi 5500000.hdmi: Couldn't get the HDMI PHY

[Launchpad Bug Tracker]

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

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

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

Title:
  sun8i-dw-hdmi 550.hdmi: Couldn't get the HDMI PHY

Status in linux-riscv package in Ubuntu:
  Confirmed

Bug description:
  I am testing the Mantic preinstalled image on the LicheeRV Dock. HDMI
  output is not working.

  There is a kernel message "sun8i-dw-hdmi 550.hdmi: Couldn't get
  the HDMI PHY".

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
  Uname: Linux 6.5.0-9-generic riscv64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20231010
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue Oct 10 14:42:06 2023
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2038933/+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 2039151] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 2039151

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Support speaker mute hotkey for Cirrus CS35L41 HDA codec

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

Bug description:
  [Impact]
  Some systems use a special hotkey to mute speaker audio. On systems using 
CS35L41 HDA which have this hotkey, add a mechanism which uses ACPI 
notifications to detect whether the hotkey is triggered to switch the mute 
state.

  [Fix]
  Backport the fix from Cirrus on linux-next 
https://lore.kernel.org/alsa-devel/87fs36egnv.wl-ti...@suse.de/T/#t.

  [Test Case]
  1. Power on the machine with CS35L41 HDA and the speaker mute hotkey.
  2. Verify the audio functions
  3. Verify if the speaker can be mute/unmute by the hotkey.

  [Where problems could occur]
  Only affect specific laptops with the CS35L41 HDA and the speaker mute hotkey 
on keyboard. The impact is restricted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2039151/+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 2039151] [NEW] Support speaker mute hotkey for Cirrus CS35L41 HDA codec

[Chris Chiu]

Public bug reported:

[Impact]
Some systems use a special hotkey to mute speaker audio. On systems using 
CS35L41 HDA which have this hotkey, add a mechanism which uses ACPI 
notifications to detect whether the hotkey is triggered to switch the mute 
state.

[Fix]
Backport the fix from Cirrus on linux-next 
https://lore.kernel.org/alsa-devel/87fs36egnv.wl-ti...@suse.de/T/#t.

[Test Case]
1. Power on the machine with CS35L41 HDA and the speaker mute hotkey.
2. Verify the audio functions
3. Verify if the speaker can be mute/unmute by the hotkey.

[Where problems could occur]
Only affect specific laptops with the CS35L41 HDA and the speaker mute hotkey 
on keyboard. The impact is restricted.

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

** Affects: linux (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-6.5 (Ubuntu Jammy)
 Importance: Undecided
 Status: In Progress

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

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


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

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

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

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

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

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

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

** No longer affects: linux-oem-6.1 (Ubuntu)

** No longer affects: linux-oem-6.1 (Ubuntu Jammy)

** No longer affects: linux-oem-6.1 (Ubuntu Mantic)

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

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

Title:
  Support speaker mute hotkey for Cirrus CS35L41 HDA codec

Status in HWE Next:
  New
Status in linux 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-6.5 source package in Jammy:
  In Progress
Status in linux source package in Mantic:
  New
Status in linux-oem-6.5 source package in Mantic:
  New

Bug description:
  [Impact]
  Some systems use a special hotkey to mute speaker audio. On systems using 
CS35L41 HDA which have this hotkey, add a mechanism which uses ACPI 
notifications to detect whether the hotkey is triggered to switch the mute 
state.

  [Fix]
  Backport the fix from Cirrus on linux-next 
https://lore.kernel.org/alsa-devel/87fs36egnv.wl-ti...@suse.de/T/#t.

  [Test Case]
  1. Power on the machine with CS35L41 HDA and the speaker mute hotkey.
  2. Verify the audio functions
  3. Verify if the speaker can be mute/unmute by the hotkey.

  [Where problems could occur]
  Only affect specific laptops with the CS35L41 HDA and the speaker mute hotkey 
on keyboard. The impact is restricted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2039151/+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 2037316] Re: SEV_SNP failure to init

[Stefan Bader]

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

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

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

Title:
  SEV_SNP failure to init

Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Fix Released
Status in linux-aws source package in Jammy:
  Invalid
Status in linux-gcp source package in Jammy:
  Fix Committed
Status in linux-aws source package in Lunar:
  Fix Committed
Status in linux-gcp source package in Lunar:
  Fix Committed
Status in linux-aws source package in Mantic:
  Fix Released
Status in linux-gcp source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  * Kernel fails to boot on SEV-SNP instances when compiled with GCC
  12.3.0

  [Fix]

  *
  https://lore.kernel.org/lkml/20230912002703.3924521-1-acdun...@google.com/

  [Test Case]

  * Compile tested
  * Boot tested
  * Tested by Google

  [Where things could go wrong]

  * Patches relatively isolated and maintain similar checking
  functionality, just earlier in boot. Likely a low chance of
  regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2037316/+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 2031302] Re: test_290_config_hardened_usercopy in ubuntu_qrt_kernel_security failed with J-oem-6.5 / M-linux (HAVE_HARDENED_USERCOPY_ALLOCATOR does not exist anymore)

[Paolo Pisati]

** No longer affects: linux (Ubuntu Mantic)

** No longer affects: linux (Ubuntu)

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

Title:
  test_290_config_hardened_usercopy in ubuntu_qrt_kernel_security failed
  with J-oem-6.5 / M-linux (HAVE_HARDENED_USERCOPY_ALLOCATOR does not
  exist anymore)

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  New

Bug description:
  This test requires HARDENED_USERCOPY to be unset.

  Test log:
   Running 'python3 ./test-kernel-security.py -v 
KernelSecurityConfigTest.test_290_config_hardened_usercopy'
   Running test: './test-kernel-security.py' distro: 'Ubuntu 22.04' kernel: 
'6.5.0-1002.2 (Ubuntu 6.5.0-1002.2-oem 6.5.0-rc4)' arch: 'amd64' init: 
'systemd' uid: 0/0 SUDO_USER: 'ubuntu')
   test_290_config_hardened_usercopy (__main__.KernelSecurityConfigTest)
   Ensure CONFIG_HARDENED_USERCOPY is set ... (skipped: HARDENED_USERCOPY 
depends on the allocator and strict devmem) FAIL
   
   ==
   FAIL: test_290_config_hardened_usercopy (__main__.KernelSecurityConfigTest)
   Ensure CONFIG_HARDENED_USERCOPY is set
   --
   Traceback (most recent call last):
 File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py",
 line 2724, in test_290_config_hardened_usercopy
   self.assertKernelConfigUnset(config_name)
 File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py",
 line 223, in assertKernelConfigUnset
   self.assertFalse(self._test_config(name),
   AssertionError: True is not false : HARDENED_USERCOPY option was expected to 
be unset in the kernel config
   
   --
   Ran 1 test in 0.007s
   
   FAILED (failures=1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/2031302/+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 2039141] Re: linux-tools-raspi is missing at least one module needed by usbip

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  linux-tools-raspi is missing at least one module needed by usbip

Status in linux-raspi package in Ubuntu:
  New

Bug description:
  my install command-line was sudo apt install linux-tools-raspi

  if is search for it with apt - I find it. This bug reporting tool told
  me it doesn't exist.

  ~$ apt search linux-tools-raspi
  Sorting... Done
  Full Text Search... Done
  linux-tools-raspi/jammy-updates,jammy-security 5.15.0.1038.36 armhf
Raspberry Pi Linux kernel tools

  linux-tools-raspi-nolpae/jammy-updates,jammy-security 5.15.0.1038.36 armhf
Raspberry Pi no-LPAE Linux kernel tools (dummy transitional package)

  https://manpages.ubuntu.com/manpages/jammy/man1/usbip.8.html

  I believe that for usbip bind --busid=1-1.x to work. 
  sudo modprobe usbip_host must run.
  This module is not installed.

  ~$ usbip list -l
   - busid 1-1.1 (0424:ec00)
 Microchip Technology, Inc. (formerly SMSC) : SMSC9512/9514 Fast Ethernet 
Adapter (0424:ec00)

   - busid 1-1.3 (046d:c52b)
 Logitech, Inc. : Unifying Receiver (046d:c52b)

   - busid 1-1.5 (1a86:55d4)
 QinHeng Electronics : unknown product (1a86:55d4)

  ~$ modprobe usbip_host
  modprobe: FATAL: Module usbip_host not found in directory 
/lib/modules/5.15.0-1038-raspi

  
  ~$ usbip bind --busid=1-1.5
  usbip: error: error unbinding device 1-1.5 from driver
  usbip: error: could not unbind driver from device on busid 1-1.5

  
  It would be good if the man page showed the basic use case of binding a local 
usb device, and connecting from a client.

  I have only installed the linux-tools-raspi package out of the linux-
  tools family.

  Cheers...

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-tools-raspi 5.15.0.1038.36
  ProcVersionSignature: Ubuntu 5.15.0-1038.41-raspi 5.15.116
  Uname: Linux 5.15.0-1038-raspi armv7l
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.15.0-1038-raspi.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: armhf
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: unknown
  CloudArchitecture: armv7l
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: config-disk (/dev/mmcblk0p1)
  Date: Thu Oct 12 17:14:53 2023
  ImageMediaBuild: 20230807.2
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb:
   Bus 001 Device 005: ID 1a86:55d4 QinHeng Electronics SONOFF Zigbee 3.0 USB 
Dongle Plus V2
   Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) 
SMSC9512/9514 Fast Ethernet Adapter
   Bus 001 Device 002: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) 
SMC9514 Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:
   
  ProcEnviron:
   LANG=C.UTF-8
   TERM=xterm-kitty
   PATH=(custom, no user)
   SHELL=/bin/bash
  ProcFB: 0 BCM2708 FB
  ProcKernelCmdLine: coherent_pool=1M snd_bcm2835.enable_compat_alsa=0 
snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1200 
bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  
console=ttyAMA0,115200 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable 
rootfstype=ext4 rootwait fixrtc quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-1038-raspi N/A
   linux-backports-modules-5.15.0-1038-raspi  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.19
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux-raspi
  StagingDrivers: vc_sm_cma bcm2835_v4l2 bcm2835_isp bcm2835_codec snd_bcm2835 
bcm2835_mmal_vchiq
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2039141/+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 2039141] [NEW] linux-tools-raspi is missing at least one module needed by usbip

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

my install command-line was sudo apt install linux-tools-raspi

if is search for it with apt - I find it. This bug reporting tool told
me it doesn't exist.

~$ apt search linux-tools-raspi
Sorting... Done
Full Text Search... Done
linux-tools-raspi/jammy-updates,jammy-security 5.15.0.1038.36 armhf
  Raspberry Pi Linux kernel tools

linux-tools-raspi-nolpae/jammy-updates,jammy-security 5.15.0.1038.36 armhf
  Raspberry Pi no-LPAE Linux kernel tools (dummy transitional package)

https://manpages.ubuntu.com/manpages/jammy/man1/usbip.8.html

I believe that for usbip bind --busid=1-1.x to work. 
sudo modprobe usbip_host must run.
This module is not installed.

~$ usbip list -l
 - busid 1-1.1 (0424:ec00)
   Microchip Technology, Inc. (formerly SMSC) : SMSC9512/9514 Fast Ethernet 
Adapter (0424:ec00)

 - busid 1-1.3 (046d:c52b)
   Logitech, Inc. : Unifying Receiver (046d:c52b)

 - busid 1-1.5 (1a86:55d4)
   QinHeng Electronics : unknown product (1a86:55d4)

~$ modprobe usbip_host
modprobe: FATAL: Module usbip_host not found in directory 
/lib/modules/5.15.0-1038-raspi


~$ usbip bind --busid=1-1.5
usbip: error: error unbinding device 1-1.5 from driver
usbip: error: could not unbind driver from device on busid 1-1.5


It would be good if the man page showed the basic use case of binding a local 
usb device, and connecting from a client.

I have only installed the linux-tools-raspi package out of the linux-
tools family.

Cheers...

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-tools-raspi 5.15.0.1038.36
ProcVersionSignature: Ubuntu 5.15.0-1038.41-raspi 5.15.116
Uname: Linux 5.15.0-1038-raspi armv7l
AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.15.0-1038-raspi.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: armhf
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
CasperMD5CheckResult: unknown
CloudArchitecture: armv7l
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: config-disk (/dev/mmcblk0p1)
Date: Thu Oct 12 17:14:53 2023
ImageMediaBuild: 20230807.2
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci:
 
Lspci-vt: -[:00]-
Lsusb:
 Bus 001 Device 005: ID 1a86:55d4 QinHeng Electronics SONOFF Zigbee 3.0 USB 
Dongle Plus V2
 Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 003: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) 
SMSC9512/9514 Fast Ethernet Adapter
 Bus 001 Device 002: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) 
SMC9514 Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
PciMultimedia:
 
ProcEnviron:
 LANG=C.UTF-8
 TERM=xterm-kitty
 PATH=(custom, no user)
 SHELL=/bin/bash
ProcFB: 0 BCM2708 FB
ProcKernelCmdLine: coherent_pool=1M snd_bcm2835.enable_compat_alsa=0 
snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1200 
bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  
console=ttyAMA0,115200 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable 
rootfstype=ext4 rootwait fixrtc quiet splash
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-1038-raspi N/A
 linux-backports-modules-5.15.0-1038-raspi  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.19
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux-raspi
StagingDrivers: vc_sm_cma bcm2835_v4l2 bcm2835_isp bcm2835_codec snd_bcm2835 
bcm2835_mmal_vchiq
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:

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


** Tags: apport-bug armhf armhf-image jammy raspi-image staging uec-images
-- 
linux-tools-raspi is missing at least one module needed by usbip
https://bugs.launchpad.net/bugs/2039141
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-raspi in Ubuntu.

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

[Kernel-packages] [Bug 2039144] [NEW] [X13s] Set unique wifi mac address

[Juerg Haefliger]

Public bug reported:

Currently, the wifi NIC comes up with a random MAC address which causes
issues in some environments (routers sending out 'new device added'
messages after every reboot).

Instead, set a unique MAC address at boot and let network manager handle
MAC randomization if that is desired.

** Affects: ubuntu-concept
 Importance: Undecided
 Status: New

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

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

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

Title:
  [X13s] Set unique wifi mac address

Status in ubuntu-concept:
  New
Status in linux-meta-laptop package in Ubuntu:
  New

Bug description:
  Currently, the wifi NIC comes up with a random MAC address which
  causes issues in some environments (routers sending out 'new device
  added' messages after every reboot).

  Instead, set a unique MAC address at boot and let network manager
  handle MAC randomization if that is desired.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-concept/+bug/2039144/+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 2031302] Re: test_290_config_hardened_usercopy in ubuntu_qrt_kernel_security failed with J-oem-6.5 / M-linux (HAVE_HARDENED_USERCOPY_ALLOCATOR does not exist anymore)

[Paolo Pisati]

** Summary changed:

- test_290_config_hardened_usercopy in ubuntu_qrt_kernel_security failed with 
J-oem-6.5 (HAVE_HARDENED_USERCOPY_ALLOCATOR does not exist anymore)
+ test_290_config_hardened_usercopy in ubuntu_qrt_kernel_security failed with 
J-oem-6.5 / M-linux (HAVE_HARDENED_USERCOPY_ALLOCATOR does not exist anymore)

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

Title:
  test_290_config_hardened_usercopy in ubuntu_qrt_kernel_security failed
  with J-oem-6.5 / M-linux (HAVE_HARDENED_USERCOPY_ALLOCATOR does not
  exist anymore)

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  New
Status in linux source package in Mantic:
  Incomplete

Bug description:
  This test requires HARDENED_USERCOPY to be unset.

  Test log:
   Running 'python3 ./test-kernel-security.py -v 
KernelSecurityConfigTest.test_290_config_hardened_usercopy'
   Running test: './test-kernel-security.py' distro: 'Ubuntu 22.04' kernel: 
'6.5.0-1002.2 (Ubuntu 6.5.0-1002.2-oem 6.5.0-rc4)' arch: 'amd64' init: 
'systemd' uid: 0/0 SUDO_USER: 'ubuntu')
   test_290_config_hardened_usercopy (__main__.KernelSecurityConfigTest)
   Ensure CONFIG_HARDENED_USERCOPY is set ... (skipped: HARDENED_USERCOPY 
depends on the allocator and strict devmem) FAIL
   
   ==
   FAIL: test_290_config_hardened_usercopy (__main__.KernelSecurityConfigTest)
   Ensure CONFIG_HARDENED_USERCOPY is set
   --
   Traceback (most recent call last):
 File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py",
 line 2724, in test_290_config_hardened_usercopy
   self.assertKernelConfigUnset(config_name)
 File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py",
 line 223, in assertKernelConfigUnset
   self.assertFalse(self._test_config(name),
   AssertionError: True is not false : HARDENED_USERCOPY option was expected to 
be unset in the kernel config
   
   --
   Ran 1 test in 0.007s
   
   FAILED (failures=1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/2031302/+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 2031302] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 2031302

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  test_290_config_hardened_usercopy in ubuntu_qrt_kernel_security failed
  with J-oem-6.5 / M-linux (HAVE_HARDENED_USERCOPY_ALLOCATOR does not
  exist anymore)

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  New
Status in linux source package in Mantic:
  Incomplete

Bug description:
  This test requires HARDENED_USERCOPY to be unset.

  Test log:
   Running 'python3 ./test-kernel-security.py -v 
KernelSecurityConfigTest.test_290_config_hardened_usercopy'
   Running test: './test-kernel-security.py' distro: 'Ubuntu 22.04' kernel: 
'6.5.0-1002.2 (Ubuntu 6.5.0-1002.2-oem 6.5.0-rc4)' arch: 'amd64' init: 
'systemd' uid: 0/0 SUDO_USER: 'ubuntu')
   test_290_config_hardened_usercopy (__main__.KernelSecurityConfigTest)
   Ensure CONFIG_HARDENED_USERCOPY is set ... (skipped: HARDENED_USERCOPY 
depends on the allocator and strict devmem) FAIL
   
   ==
   FAIL: test_290_config_hardened_usercopy (__main__.KernelSecurityConfigTest)
   Ensure CONFIG_HARDENED_USERCOPY is set
   --
   Traceback (most recent call last):
 File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py",
 line 2724, in test_290_config_hardened_usercopy
   self.assertKernelConfigUnset(config_name)
 File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py",
 line 223, in assertKernelConfigUnset
   self.assertFalse(self._test_config(name),
   AssertionError: True is not false : HARDENED_USERCOPY option was expected to 
be unset in the kernel config
   
   --
   Ran 1 test in 0.007s
   
   FAILED (failures=1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/2031302/+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 2031302] Re: test_290_config_hardened_usercopy in ubuntu_qrt_kernel_security failed with J-oem-6.5 (HAVE_HARDENED_USERCOPY_ALLOCATOR does not exist anymore)

[Paolo Pisati]

I've sent a pull req to fix the test:

https://code.launchpad.net/~p-pisati/qa-regression-testing/+git/qa-
regression-testing/+merge/453326

basically, the HAVE_HARDENED_USERCOPY_ALLOCATOR has been retired in
v6.5-rc1 so the test thinks the option is off and thus the test should
always fail.

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

** No longer affects: linux (Ubuntu Jammy)

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

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

** No longer affects: linux-oem-6.5 (Ubuntu Mantic)

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

Title:
  test_290_config_hardened_usercopy in ubuntu_qrt_kernel_security failed
  with J-oem-6.5 / M-linux (HAVE_HARDENED_USERCOPY_ALLOCATOR does not
  exist anymore)

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  New
Status in linux source package in Mantic:
  Incomplete

Bug description:
  This test requires HARDENED_USERCOPY to be unset.

  Test log:
   Running 'python3 ./test-kernel-security.py -v 
KernelSecurityConfigTest.test_290_config_hardened_usercopy'
   Running test: './test-kernel-security.py' distro: 'Ubuntu 22.04' kernel: 
'6.5.0-1002.2 (Ubuntu 6.5.0-1002.2-oem 6.5.0-rc4)' arch: 'amd64' init: 
'systemd' uid: 0/0 SUDO_USER: 'ubuntu')
   test_290_config_hardened_usercopy (__main__.KernelSecurityConfigTest)
   Ensure CONFIG_HARDENED_USERCOPY is set ... (skipped: HARDENED_USERCOPY 
depends on the allocator and strict devmem) FAIL
   
   ==
   FAIL: test_290_config_hardened_usercopy (__main__.KernelSecurityConfigTest)
   Ensure CONFIG_HARDENED_USERCOPY is set
   --
   Traceback (most recent call last):
 File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py",
 line 2724, in test_290_config_hardened_usercopy
   self.assertKernelConfigUnset(config_name)
 File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py",
 line 223, in assertKernelConfigUnset
   self.assertFalse(self._test_config(name),
   AssertionError: True is not false : HARDENED_USERCOPY option was expected to 
be unset in the kernel config
   
   --
   Ran 1 test in 0.007s
   
   FAILED (failures=1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/2031302/+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 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

[Lukas Märdian]

** Tags added: rls-jj-incoming

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Triaged
Status in systemd source package in Jammy:
  New

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037667/+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 2034491] Re: Fix blank display when Thunderbolt monitor is plugged second time

[Kai-Heng Feng]

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

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

Title:
  Fix blank display when Thunderbolt monitor is plugged second time

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  When a Thunderbolt monitor gets plugged to an AMD laptop for second time, the 
Thunderbolt monitor remains blank.

  [Fix]
  Reinitialize TMU and perform proper Time Synchronization Handshake every time.

  [Test]
  The Thunderbolt monitor still has image after many replugging.

  [Where problems could occur]
  This change the flow on disabling TMU, which is responsible for time 
synchronization, so behavior of Thunderbolt docking might be affected. Per my 
limited test no issue has been observed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2034491/+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 2034504] Re: Enable ASPM for NVMe behind VMD

[Kai-Heng Feng]

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

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

Title:
  Enable ASPM for NVMe behind VMD

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  New
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  ASPM of NVMe behind VMD is not enabled when BIOS FADT doesn't allow ASPM to 
be modified.
  That causes higher overall power consumption.

  [Fix]
  Allow ASPM to be enabled.
  While at this, remove old cruft that can interfere upstream VMD driver.

  [Test]
  Check the value of `/sys/kernel/debug/pmc_core/slp_s0_residency_usec`. Now 
system can reach deepest power saving state during sleep.

  [Where problems could occur]
  Some NVMe may have I/O issue when ASPM is enabled. But for this scenario the 
issue will also appear when VMD is disabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2034504/+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 2035313] Re: Fix non-working I219 after system sleep

[Kai-Heng Feng]

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

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

Title:
  Fix non-working I219 after system sleep

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  Intel I219 ethernet stops working after system sleep.

  [Fix]
  Force resume Intel ME to fix I219. It's not surprising because ME/AMT is
  controlled through Intel I219.

  [Test]
  Use `ping 1.1.1.1` to test if I219 is still alive. With the patch
  applied, the ethernet can survive several system sleeps.

  [Where problems could occur] 
  The commit essentially disables direct-complete optimization, so it
  will make system suspend/resume slightly slower.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2035313/+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 2036377] Re: Fix RCU warning on AMD laptops

[Kai-Heng Feng]

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

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

Title:
  Fix RCU warning on AMD laptops

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

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

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

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

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

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


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