date:20231207

You have been subscribed to a public bug:

I was using:
Ubuntu 20.04 (installed a month ago, updated recently)
Vmware Workstation 16 (Ubuntu 20.04 VM)
Nvidia GTX 1080 TI Driver Version: 450.80.02 CUDA Version: 11.0

What happened:
System instantly became unresponsive. Mouse stopped moving, keyboard had no 
effect (tried ALT+F2). I had to press and hold the power button until the 
system hard reset. This is the second time I observed this type issue, but last 
time, the mouse would move with extreme lag.

/var/log/syslog:
Nov  5 11:54:37 eypc crash_20201105115437_38.dmp[0]: Uploading dump 
(out-of-process)#012/tmp/dumps/crash_20201105115437_38.dmp
Nov  5 11:54:38 eypc crash_20201105115437_38.dmp[0]: Finished uploading 
minidump (out-of-process): success = yes
Nov  5 11:54:38 eypc crash_20201105115437_38.dmp[0]: response: 
CrashID=bp-373c5190-00a9-43c1-aa4c-80c4a2201105
Nov  5 11:54:38 eypc crash_20201105115437_38.dmp[0]: file 
''/tmp/dumps/crash_20201105115437_38.dmp'', upload yes: 
''CrashID=bp-373c5190-00a9-43c1-aa4c-80c4a2201105''
Nov  5 11:55:02 eypc kernel: [47695.080487] GpuWatchdog[35222]: segfault at 0 
ip 7f3832af62dd sp 7f38278c34d0 error 6 in 
libcef.so[7f382ed7+69a4000]
Nov  5 11:55:02 eypc kernel: [47695.080492] Code: 00 79 09 48 8b 7d a0 e8 21 80 
c1 02 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 
00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 c1 a5 37 03 01 80 bd 
7f ff

Since the computer restarted, the log saved in /tmp is gone.

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


** Tags: crash gpu nvidia
-- 
System becomes un-responsive due to gpu segfault
https://bugs.launchpad.net/bugs/1903203
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

2023-12-07 Thread Christian Rohmann

FWIW, we updated our NICs to 4.30 as they were individually purchased
and not part of pre-built servers and also have this issue.

So in essence the issue also exists with the latest firmware.

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

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

Status in linux package in Ubuntu:
  Confirmed

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

  Details:

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

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

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

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

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

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

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

  - the switch does log that the bond is flapping
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 12 20:05 seq
   crw-rw 1 root audio 116, 33 Sep 12 20:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-22 (24 days ago)
  InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release 
amd64 (20230810)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7515
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 mgag200drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-83-generic 
root=UUID=cfb5f171-77e6-4fcd-947b-52901f51b26a ro
  ProcVersionSignature: Ubuntu 5.15.0-83.92-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-83-generic N/A
   linux-backports-modules-5.15.0-83-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.18
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-83-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 07/27/2023
  dmi.bios.release: 2.12
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.12.4
  dmi.board.name: 0J91V2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.12.4:bd07/27/2023:br2.12:svnDellInc.:pnPowerEdgeR7515:pvr:rvnDellInc.:rn0J91V2:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=08FD;ModelName=PowerEdgeR7515:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7515
  dmi.product.sku: SKU=08FD;ModelName=PowerEdge R7515
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 15 03:13 seq
   crw-rw 1 root audio 116, 33 Sep 15 03:13 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: Cannot stat file /proc/215602/fd/10: Permission denied
   Cannot stat file /proc/323635/fd/10: Permission denied
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.3.4.7:5248/MAAS/metadata/)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7525
  NonfreeKerne

[Kernel-packages] [Bug 2045947] [NEW] spidev0 missing on raspberrypi5 on ubuntu 23.10 server version

2023-12-07 Thread Ajay

Public bug reported:

While trying to access spidev0 on ubuntu 23.10 server version for
raspberrypi model 5 did not find spidev0.

On further debugging with raspi team it was observed that DMA is not set.
Link to the discussion: 
https://forums.raspberrypi.com/viewtopic.php?t=360436&start=25

ubuntu@ubuntu:~$  sudo modprobe configs
ubuntu@ubuntu:~$ zcat /proc/config.gz | grep DW_AXI_DMAC
# CONFIG_DW_AXI_DMAC is not set

Details of platform used

ubuntu@ubuntu:~$ ls -al /dev/spi*
crw--- 1 root root 153, 0 Dec  7 16:14 /dev/spidev10.0

ubuntu@ubuntu:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 23.10
Release:23.10
Codename:   mantic
ubuntu@ubuntu:~$ cat /etc/os-release
PRETTY_NAME="Ubuntu 23.10"
NAME="Ubuntu"
VERSION_ID="23.10"
VERSION="23.10 (Mantic Minotaur)"
VERSION_CODENAME=mantic
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/";
SUPPORT_URL="https://help.ubuntu.com/";
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
UBUNTU_CODENAME=mantic
LOGO=ubuntu-logo

ubuntu@ubuntu:~$ cat /proc/cpuinfo | grep Model
Model   : Raspberry Pi 5 Model B Rev 1.0

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

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

Title:
  spidev0 missing on raspberrypi5 on ubuntu 23.10 server version

Status in linux-raspi package in Ubuntu:
  New

Bug description:
  While trying to access spidev0 on ubuntu 23.10 server version for
  raspberrypi model 5 did not find spidev0.

  On further debugging with raspi team it was observed that DMA is not set.
  Link to the discussion: 
https://forums.raspberrypi.com/viewtopic.php?t=360436&start=25

  ubuntu@ubuntu:~$  sudo modprobe configs
  ubuntu@ubuntu:~$ zcat /proc/config.gz | grep DW_AXI_DMAC
  # CONFIG_DW_AXI_DMAC is not set

  Details of platform used

  ubuntu@ubuntu:~$ ls -al /dev/spi*
  crw--- 1 root root 153, 0 Dec  7 16:14 /dev/spidev10.0

  ubuntu@ubuntu:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 23.10
  Release:23.10
  Codename:   mantic
  ubuntu@ubuntu:~$ cat /etc/os-release
  PRETTY_NAME="Ubuntu 23.10"
  NAME="Ubuntu"
  VERSION_ID="23.10"
  VERSION="23.10 (Mantic Minotaur)"
  VERSION_CODENAME=mantic
  ID=ubuntu
  ID_LIKE=debian
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  UBUNTU_CODENAME=mantic
  LOGO=ubuntu-logo

  ubuntu@ubuntu:~$ cat /proc/cpuinfo | grep Model
  Model   : Raspberry Pi 5 Model B Rev 1.0

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


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

[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform

2023-12-07 Thread You-Sheng Yang

verified ipu6-drivers/mantic-proposed version
0~git202310180730.3f813580-0ubuntu0.23.10.1

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

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

Title:
  Support mipi camera on Intel Meteor Lake platform

Status in HWE Next:
  New
Status in ipu6-drivers package in Ubuntu:
  Fix Released
Status in ivsc-driver package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Jammy:
  Won't Fix
Status in ivsc-driver source package in Jammy:
  Won't Fix
Status in linux source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in ipu6-drivers source package in Mantic:
  Fix Committed
Status in ivsc-driver source package in Mantic:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in ipu6-drivers source package in Noble:
  Fix Released
Status in ivsc-driver source package in Noble:
  Fix Released
Status in linux source package in Noble:
  Triaged
Status in linux-firmware source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justification]

  == ipu6-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  Based on upstream tag
  https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019,
  and an additional patch to enable/fix compilation of additional sensor
  modules.

  [Test Case]

  This is verified on MTL Lattice and VSC platforms, as well as previous
  generations e.g. TGL and ADL.

  To actually verify the camera framework:
  ```
  # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14
  # reboot into the 6.5.0-14.14 kernel
  $ sudo apt install intel-ipu6-dkms intel-vsc-dkms
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, 
and their dependencies, are fetched from the oem-solutions-group PPA. 
Everything else must come from the mantic archive.

  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  This is a new platform. We've been verifying its functions and features, and
  are still polishing it.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == ivsc-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform. Need both
  firmware and driver change to probe the hardware correctly.

  [Fix]

  4 commits from the latest trunk branch on upstream repository
  https://github.com/intel/ivsc-driver.

  [Test Case]

  With all other changes in position, Intel VSC driver modules are to be
  loaded as a soft dependency of some selected camera sensor modules.
  LJCA modules should be loaded automatically on MTL platforms as well.

  To actually verify the camera framework:
  ```
  # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14
  # reboot into the 6.5.0-14.14 kernel
  $ sudo apt install intel-ipu6-dkms intel-vsc-dkms
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, 
and their dependencies, are fetched from the oem-solutions-group PPA. 
Everything else must come from the mantic archive.

  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  While it changes how LJCA modules match from ACPI ID, it's also tested
  and verified on previous generations using IVSC, e.g. TGL, ADL.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == linux/linux-oem-6.5 ==

  [Impact]

  Need kernel driver fixes for int3472/iommu for Intel IPU6 platform on
  MTL.

  [Fix]

  Two fixes in need. One, we need IOMMU passthrough for MTL platform.
  The other, fix is for handshake pin support for Lattice MIPI
  aggregator.

  The Intel IPU6 camera drivers are not yet all upstreamed yet. So far
  Intel VSC, LJCA (the previous MIPI aggregator for ADL/RPL platforms

[Kernel-packages] [Bug 2045931] Re: ps3 sixasis controller request pin to connect to bt

2023-12-07 Thread Daniel van Vugt

This sounds like it might be a feature and the bug was that previous
versions DIDN'T ask. Try entering PIN: 

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

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

Title:
  ps3 sixasis controller request pin to connect to bt

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able
  to connect my PS3 Sixasis controller via bluetooth. It is aking to
  enter a PIN in the device (not possible to enter a pin in the
  gamepad).

  Source pacakge (from "apt list -a bluez"):

  bluez/jammy-updates,jammy-security 5.64-0ubuntu1.1 amd64

  Once downgraded to 5.64-0ubuntu1 version, gamepad connects OK again
  without asking for a connection PIN.

  Ubuntu release:
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  Package version:
  bluez:
Installed: 5.64-0ubuntu1.1

  Expected to happen:
  Connect PS3 Controller by Bluetooth without asking for a PIN code

  Happened instead:
  PS3 Controller cannot connect because PIN code is requested

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931/+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 2045931] Re: ps3 sixasis controller request pin to connect to bt

2023-12-07 Thread Daniel van Vugt

** Tags added: jammy regression-update

** Changed in: bluez (Ubuntu)
 Assignee: (unassigned) => Nishit Majithia (0xnishit)

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

Title:
  ps3 sixasis controller request pin to connect to bt

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able
  to connect my PS3 Sixasis controller via bluetooth. It is aking to
  enter a PIN in the device (not possible to enter a pin in the
  gamepad).

  Source pacakge (from "apt list -a bluez"):

  bluez/jammy-updates,jammy-security 5.64-0ubuntu1.1 amd64

  Once downgraded to 5.64-0ubuntu1 version, gamepad connects OK again
  without asking for a connection PIN.

  Ubuntu release:
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  Package version:
  bluez:
Installed: 5.64-0ubuntu1.1

  Expected to happen:
  Connect PS3 Controller by Bluetooth without asking for a PIN code

  Happened instead:
  PS3 Controller cannot connect because PIN code is requested

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931/+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 2045855] Re: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: end of file on stdin at conffile prompt

2023-12-07 Thread Daniel van Vugt

It looks like the problem was just no response provided to:

Configuration file '/etc/bluetooth/input.conf'
 ==> File on system created by you or by a script.
 ==> File also in package provided by package maintainer.
   어떻게 하시겠습니까? 다음 중에 하나를 선택할 수 있습니다:
Y 또는 I : 패키지 관리자의 버전을 설치합니다
N 또는 O : 현재 설치된 버전을 유지합니다
   D : 버전 간의 차이점을 표시합니다
   Z : 프로세스를 백그라운드로 하고 상황을 알아봅니다
기본값으로 현재 버전을 그대로 유지합니다.
*** input.conf (Y/I/N/O/D/Z) [기본값=N] ?  

Was the user ever aware of the prompt or was it hidden during upgrade?

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

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

Title:
  package bluez 5.64-0ubuntu1.1 failed to install/upgrade: end of file
  on stdin at conffile prompt

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I did not recognized the error.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: bluez 5.64-0ubuntu1.1
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  AptOrdering:
   bluez:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Dec  7 15:44:57 2023
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2021-01-30 (1040 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. OptiPlex 7010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic 
root=UUID=1aa27b2f-8d22-4b4e-931f-bd8e304ed0d4 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.10, Python 3.10.12, unpackaged
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.11
  SourcePackage: bluez
  Title: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: end of file 
on stdin at conffile prompt
  UpgradeStatus: Upgraded to jammy on 2023-03-28 (253 days ago)
  dmi.bios.date: 03/25/2013
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0GY6Y8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd03/25/2013:br4.6:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0GY6Y8:rvrA00:cvnDellInc.:ct6:cvr:sku:
  dmi.product.name: OptiPlex 7010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:1A:7D:DA:71:03  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:1332 acl:0 sco:0 events:84 errors:0
TX bytes:3786 acl:0 sco:0 commands:81 errors:0
  mtime.conffile..etc.bluetooth.input.conf: 2020-04-03T15:47:01
  mtime.conffile..etc.bluetooth.main.conf: 2020-02-26T18:57:50
  mtime.conffile..etc.bluetooth.network.conf: 2012-12-25T02:46:55
  mtime.conffile..etc.dbus-1.system.d.bluetooth.conf: 2022-03-24T15:30:38
  mtime.conffile..etc.init.d.bluetooth: 2020-02-26T18:57:50
  rfkill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

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


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

[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs

2023-12-07 Thread Mike Ferreira

Wait... I seem to be confused by this:
>>>
mafoelffen@noble-d05:~$ apt-cache show zfsutils-linux | grep 'Package:\|Breaks:'
Package: zfsutils-linux
Breaks: openrc, spl (<< 0.7.9-2), spl-dkms (<< 0.8.0~rc1), zfs-dkms (>> 
2.2.2-0ubuntu1...), zfs-dkms (<< 2.2.2-0ubuntu1)
>>>
Does that mean, even though zfs-dkms is built from zfs-linux 2.2.2, that if 
installed it will break ZFS... and therefore no longer works?

On Rick's 2.2.2 blew out access to all his pools. He had to revert to
2.2.1, and restore plus add zfs-dkms back in, just to stay running.

My machine is still doing fine.

Should we start a new bug report against zfs-dkms for Noble on the
above? That just doesn't sound logical somehow.

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

Title:
  Multiple data corruption issues in zfs

Status in zfs-linux package in Ubuntu:
  Fix Committed
Status in zfs-linux source package in Xenial:
  Confirmed
Status in zfs-linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Focal:
  Confirmed
Status in zfs-linux source package in Jammy:
  Confirmed
Status in zfs-linux source package in Lunar:
  Confirmed
Status in zfs-linux source package in Mantic:
  In Progress
Status in zfs-linux source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

   * Multiple data corruption issues have been identified and fixed in
  ZFS. Some of them, at varying real-life reproducibility frequency have
  been deterimed to affect very old zfs releases. Recommendation is to
  upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
  ensure users get other potentially related fixes and runtime tunables
  to possibly mitigate other bugs that are related and are being fixed
  upstream for future releases.

   * For jammy the 2.1.14 upgrade will bring HWE kernel support and also
  compatiblity/support for hardened kernel builds that mitigate SLS
  (straight-line-speculation).

  [ Test Plan ]

   * !!! Danger !!! use reproducer from
  https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
  and confirm if that issue is resolved or not. Do not run on production
  ZFS pools / systems.

   * autopkgtest pass (from https://ubuntu-archive-
  team.ubuntu.com/proposed-migration/ )

   * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )

   * kernel regression zfs testsuite pass (from Kernel team RT test
  results summary, private)

   * zsys integration test pass (upgrade of zsys installed systems for
  all releases)

   * zsys install test pass (for daily images of LTS releases only that
  have such installer support, as per iso tracker test case)

   * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
  2.1.14, and test LXD on these updated kernels)

  
  [ Where problems could occur ]

   * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will 
introduce slight slow down on amd64 (for hw accelerated assembly code-paths 
only in the encryption primitives)
   
   * Uncertain of the perfomance impact of the extra checks in dnat patch fix 
itself. Possibly affecting speed of operation, at the benefit of correctness.

  [ Other Info ]
   
   * https://github.com/openzfs/zfs/pull/15571 is most current consideration of 
affairs

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


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

[Kernel-packages] [Bug 1988582] Re: RT test failures: ubuntu_lxc lxc-test-api-reboot and lxc-test-shutdowntest

2023-12-07 Thread Po-Hsu Lin

This can be found on J-oracle-6.5.0-1013.13~22.04.4 as well.

** Tags added: 6.5 sru-20231030

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

Title:
  RT test failures: ubuntu_lxc  lxc-test-api-reboot and lxc-test-
  shutdowntest

Status in ubuntu-kernel-tests:
  New
Status in linux-oracle package in Ubuntu:
  New

Bug description:
  ubuntu_lxc test failures for cases lxc-test-api-reboot and lxc-test-
  shutdowntest. These tests fail since 5.15.

  Kernel source: linux-oracle
  Test name: ubuntu_lxc
  Test case: lxc-test-shutdowntest
  
+++-+---+---+---++
  | Kernel | BM.Standard.A1.160 | BM.Standard2.52 | VM.DenseIO2.8 | 
VM.Standard.A1.Flex-4c.8m | VM.Standard.E3.Flex-4c.8m | VM.Standard2.1 |
  
+++-+---+---+---++
  | 5.15.0-1017.22 |FAIL|   FAIL  |  FAIL | 
   FAIL   |FAIL   |  FAIL  |
  | 5.15.0-1013.17 |FAIL|   FAIL  |  FAIL | 
   FAIL   |FAIL   |  FAIL  |
  | 5.15.0-1007.9  |FAIL|   PASS  |  PASS | 
   PASS   |PASS   |  PASS  |
  | 5.15.0-1005.7  |FAIL|   PASS  |  PASS | 
   PASS   |PASS   |  PASS  |
  | 5.15.0-1004.6  |FAIL|   PASS  |  PASS | 
   PASS   |PASS   |  PASS  |
  | 5.13.0-1031.36 |PASS|   PASS  |  PASS | 
   PASS   |PASS   |  PASS  |
  | 5.13.0-1029.34 |PASS|   PASS  |  PASS | 
   PASS   |PASS   |  PASS  |
  | 5.13.0-1028.33 |PASS|   PASS  |  PASS | 
   PASS   |PASS   |  PASS  |
  | 5.13.0-1027.32 ||   PASS  |  PASS | 
   PASS   |PASS   |  PASS  |
  | 5.13.0-1026.31 ||   PASS  |  PASS | 
   PASS   |PASS   |  PASS  |
  | 5.13.0-1025.30 ||   PASS  |  PASS | 
   PASS   |PASS   |  PASS  |
  | 5.13.0-1024.29 ||   PASS  |  PASS | 
   PASS   |PASS   |  PASS  |
  | 5.13.0-1023.28 ||   PASS  |  PASS | 
   PASS   |PASS   |  PASS  |
  | 5.13.0-1022.27 ||   PASS  |  PASS | 
   PASS   |PASS   |  PASS  |
  | 5.13.0-1019.23 ||   PASS  |  PASS | 
   PASS   |PASS   |  PASS  |
  | 5.13.0-1018.22 ||   PASS  |  PASS | 
   PASS   |PASS   |  PASS  |
  | 5.13.0-1017.21 ||   PASS  |  PASS | 
   PASS   |PASS   |  PASS  |
  | 5.13.0-1016.20 ||   PASS  |  PASS | 
  |PASS   |  PASS  |
  | 5.13.0-1011.13 ||   PASS  |  PASS | 
  |PASS   |  PASS  |
  | 5.13.0-1010.12 || |  PASS | 
  |PASS   |  PASS  |
  
+++-+---+---+---++

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1988582/+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 2038774] Re: Cursor dissappears in full screen

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Cursor dissappears in full screen

Status in linux package in Ubuntu:
  Expired

Bug description:
  Only started recently, but not all apps.
  Some snap, flatpak, or deb.
  Snap: youtube music desktop
  Flatpak: Easy effects
  Deb: MultiViewer

  When in windowed mode the cursor is fine,
  But in full screen mode in some apps it is invisible.

  Ubuntu 20.04.3 LTS
  Kernel: 5.15.0-86
  Window system: wayland
  Gnome: 42.9
  Mesa: 23.0.4-ubuntu1~22.04.1
  Cpu/gpu: AMD Kaveri A10-7800

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038774/+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 2007875] Re: Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently

2023-12-07 Thread Kai-Chuan Hsieh

reply #44

Hello,

We've done the firmware update on 22.04, could you try to remove linux-
modules-iwlwifi deb and use the in-tree kernel to see if you can still
reproduce the issue.

Thanks,

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

Title:
  Ubuntu 22.04 XPS 13 plus 9320  kernel 6.0 OEM and 5.19 breaks wifi
  frequently

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in oem-somerville-tentacool-meta package in Ubuntu:
  Invalid
Status in linux-firmware source package in Jammy:
  Fix Released
Status in oem-somerville-tentacool-meta source package in Jammy:
  Confirmed
Status in linux-firmware source package in Kinetic:
  Fix Released
Status in oem-somerville-tentacool-meta source package in Kinetic:
  Invalid
Status in linux-firmware source package in Lunar:
  Fix Released
Status in oem-somerville-tentacool-meta source package in Lunar:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  backport-iwlwifi-dkms/kinetic is being built into hwe-5.19 kernel, and
  -73 firmware are supported bug missing. On one user reported issue,
  this fixes WiFi stability on 5G band.

  [Fix]

  New upstreamed firmware revision fixes this issue.

  [Test Case]

  1. Boot hwe-5.19 kernel
  2. iwlwifi-so-a0-gf-a0-73.ucode firmware should be loaded
  3. Browse the web, usually takes between 1 and 5 minutes
  4. Networking will cut out

  [Where problems could occur]

  This affects only users need both backport-iwlwifi-dkms and hwe-5.19
  kernel on WiFi stability.

  [Other Info]

  While Kinetic and above have them all, only Jammy is nominated.

  == original bug report ==

  I'm using the stock Dell Ubuntu 22.04 image on my XPS 13 Plus (9320).
  Recently I received some kernel updates, the 5.19 kernel used in 22.10
  and a 6.0 oem kernel. Both updates break wifi. It seems to only do so
  on newer 5.7 GHz access points.

  1. Boot latest 6.0 oem kernel
  2. Browse the web, usually takes between 1 and 5 minutes.
  3. Networking will cut out.

  Disabling networking and starting again will fix it until it happens
  again in a few minutes. This will repeat indefinitely, essentially
  making wireless useless.

  The attached dmesg log reliably shows up when it fails, showing
  iwlwifi failing and a (network?) hardware reset request.

  It witnessed this happen months ago on 22.10, which led me to using
  the Dell stock 22.04 image. But it seems even the newer OEM kernel is
  affected.

  A workaround is to select the older 5.15 kernel in grub. I find on
  this laptop, one must hit escape precisely 1 second after seeing the
  Dell logo on boot. Alternatively one could edit /etc/grub/default and
  set a longer timeout.

  Let me know if this bug report would be better to go to Dell as a
  support request instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2007875/+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 2042902] Re: ucm2: soundwire: add rt713 SDCA device

2023-12-07 Thread Artur Pak

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

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

** Tags removed: verification-needed

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

Title:
  ucm2: soundwire: add rt713 SDCA device

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

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

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

  [ Test Plan ]
  Device with the soundwire card

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

  Before fix:

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

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

  After fix: after adding patch files

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

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

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

  [Where problems could occur]

   * This change adds new hardware support.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2042902/+subscriptions


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

[Kernel-packages] [Bug 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build

2023-12-07 Thread Mike Ferreira

Just passed on to me from FL140:
https://github.com/openzfs/zfs/issues/15586#issuecomment-1836806381

Is an updated script to manually build and install the OpenZFS native
deb packages, including 'zfs-dkms' 2.2.2.

** Bug watch added: github.com/openzfs/zfs/issues #15586
   https://github.com/openzfs/zfs/issues/15586

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

Title:
  zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build
  kernel module.

  Genrated Crash report, but couldn't send it on it's own.

  Error it kept throwing was:
  >>>
  Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ...
  Loading new zfs-2.1.5 DKMS files...
  Building for 6.2.0-36-generic 6.2.0-37-generic
  Building initial module for 6.2.0-36-generic
  configure: error:
   *** None of the expected "iops->get_acl()" interfaces were detected.
   *** This may be because your kernel version is newer than what is
   *** supported, or you are using a patched custom kernel with
   *** incompatible modifications.
   ***
   *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2
   *** Compatible Kernels: 3.10 - 5.19

  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/zfs-dkms.0.crash'
  Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64)
  Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information.
  dpkg: error processing package zfs-dkms (--configure):
   installed zfs-dkms package post-installation script subprocess returned 
error exit status 10
  >>>

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sat Nov 25 21:00:27 2023
  InstallationDate: Installed on 2021-09-23 (793 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: zfs-linux
  UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago)

  To recreate:
  - Install Ubuntu 22.04.3.
  - Update to current.
  - Install package 'zfs-dkms'

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


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

[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs

2023-12-07 Thread Mike Ferreira

Rick and I have been testing the Proposed 2.2.2 packages in Noble since
yesterday morning. Great so far.

@fl140 -- 
Thanks you for the link. I'll pass that on.

Waiting to see if anything of this helps with: zfs-dkms
2.1.5-1ubuntu6~22.04.2 https://bugs.launchpad.net/ubuntu/+source/zfs-
linux/+bug/2044630... But I know that is (1) focal-lunar (some Mantic),
and (2) most likely just a regression issue like the last update had
with zfs-dkms 2.1.5-1ubuntu6~22.04.1
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2030100. Where
the make did not recognize that kernels after 5.19.0 are supported. It's
not needed by most now, but some of us still need it for out of series
kernel testing.

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

Title:
  Multiple data corruption issues in zfs

Status in zfs-linux package in Ubuntu:
  Fix Committed
Status in zfs-linux source package in Xenial:
  Confirmed
Status in zfs-linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Focal:
  Confirmed
Status in zfs-linux source package in Jammy:
  Confirmed
Status in zfs-linux source package in Lunar:
  Confirmed
Status in zfs-linux source package in Mantic:
  In Progress
Status in zfs-linux source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

   * Multiple data corruption issues have been identified and fixed in
  ZFS. Some of them, at varying real-life reproducibility frequency have
  been deterimed to affect very old zfs releases. Recommendation is to
  upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
  ensure users get other potentially related fixes and runtime tunables
  to possibly mitigate other bugs that are related and are being fixed
  upstream for future releases.

   * For jammy the 2.1.14 upgrade will bring HWE kernel support and also
  compatiblity/support for hardened kernel builds that mitigate SLS
  (straight-line-speculation).

  [ Test Plan ]

   * !!! Danger !!! use reproducer from
  https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
  and confirm if that issue is resolved or not. Do not run on production
  ZFS pools / systems.

   * autopkgtest pass (from https://ubuntu-archive-
  team.ubuntu.com/proposed-migration/ )

   * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )

   * kernel regression zfs testsuite pass (from Kernel team RT test
  results summary, private)

   * zsys integration test pass (upgrade of zsys installed systems for
  all releases)

   * zsys install test pass (for daily images of LTS releases only that
  have such installer support, as per iso tracker test case)

   * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
  2.1.14, and test LXD on these updated kernels)

  
  [ Where problems could occur ]

   * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will 
introduce slight slow down on amd64 (for hw accelerated assembly code-paths 
only in the encryption primitives)
   
   * Uncertain of the perfomance impact of the extra checks in dnat patch fix 
itself. Possibly affecting speed of operation, at the benefit of correctness.

  [ Other Info ]
   
   * https://github.com/openzfs/zfs/pull/15571 is most current consideration of 
affairs

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


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

[Kernel-packages] [Bug 2045931] [NEW] ps3 sixasis controller request pin to connect to bt

2023-12-07 Thread Carlos

Public bug reported:

Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able
to connect my PS3 Sixasis controller via bluetooth. It is aking to enter
a PIN in the device (not possible to enter a pin in the gamepad).

Source pacakge (from "apt list -a bluez"):

bluez/jammy-updates,jammy-security 5.64-0ubuntu1.1 amd64

Once downgraded to 5.64-0ubuntu1 version, gamepad connects OK again
without asking for a connection PIN.

Ubuntu release:
Description:Ubuntu 22.04.3 LTS
Release:22.04

Package version:
bluez:
  Installed: 5.64-0ubuntu1.1

Expected to happen:
Connect PS3 Controller by Bluetooth without asking for a PIN code

Happened instead:
PS3 Controller cannot connect because PIN code is requested

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

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

Title:
  ps3 sixasis controller request pin to connect to bt

Status in bluez package in Ubuntu:
  New

Bug description:
  Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able
  to connect my PS3 Sixasis controller via bluetooth. It is aking to
  enter a PIN in the device (not possible to enter a pin in the
  gamepad).

  Source pacakge (from "apt list -a bluez"):

  bluez/jammy-updates,jammy-security 5.64-0ubuntu1.1 amd64

  Once downgraded to 5.64-0ubuntu1 version, gamepad connects OK again
  without asking for a connection PIN.

  Ubuntu release:
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  Package version:
  bluez:
Installed: 5.64-0ubuntu1.1

  Expected to happen:
  Connect PS3 Controller by Bluetooth without asking for a PIN code

  Happened instead:
  PS3 Controller cannot connect because PIN code is requested

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


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

[Kernel-packages] [Bug 2044722] Re: Enabling fips-preview on Jammy AWS fails with: Depends: linux-aws-fips (>= 5.15.0.1042.43) but it is not installable

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

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

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

Title:
  Enabling fips-preview on Jammy AWS fails with: Depends: linux-aws-fips
  (>= 5.15.0.1042.43) but it is not installable

Status in linux-aws package in Ubuntu:
  Confirmed

Bug description:
  I'm testing the fips-review packages on AWS for Jammy. That fails
  with:

  Unexpected APT error.
  Failed running command 'apt-get install --assume-yes --allow-downgrades -o 
Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" 
ubuntu-aws-fips' [exit(100)]. Message: E: Unable to correct problems, you have 
held broken packages.

  Steps to reproduce:

  1) aws ec2 run-instances --image-id 
resolve:ssm:/aws/service/canonical/ubuntu/server/22.04/stable/current/amd64/hvm/ebs-gp2/ami-id
 --instance-type m6a.large --key-name toabctl
  2) ssh into the instance
  3) ua attach $MY_UA_TOKEN
  4) ua enable fips-preview # (answer with yes)

  The result is:

  # ua enable fips-preview
  One moment, checking your subscription first
  FIPS Preview cannot be enabled with Livepatch.
  Disable Livepatch and proceed to enable FIPS Preview? (y/N) y
  Disabling incompatible service: Livepatch
  This will install crypto packages that have been submitted to NIST for review
  but do not have FIPS certification yet. Use this for early access to the FIPS
  modules.
  Please note that the Livepatch service will be unavailable after
  this operation.
  Warning: This action can take some time and cannot be undone.
  Are you sure? (y/N) y
  Updating FIPS Preview package lists
  Installing FIPS Preview packages
  Updating standard Ubuntu package lists
  Could not enable FIPS Preview.
  Updating package lists
  Unexpected APT error.
  Failed running command 'apt-get install --assume-yes --allow-downgrades -o 
Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" 
ubuntu-aws-fips' [exit(100)]. Message: E: Unable to correct problems, you have 
held broken packages.

  See /var/log/ubuntu-advantage.log

  From that log:
  ["2023-11-27T09:58:33.581", "DEBUG", "ubuntupro.system", "subp", 714, "Failed 
running command 'apt-get install --assume-yes --allow-downgrades -o 
Dpkg::Options::=\"--force-confdef\" -o Dpkg::Options::=\"--force-confold\" 
ubuntu-aws-fips' [exit(100)]. Mes
  sage: E: Unable to correct problems, you have held broken packages.\n", {}]
  ["2023-11-27T09:58:33.581", "WARNING", "ubuntupro.system", "subp", 715, 
"Stderr: E: Unable to correct problems, you have held broken 
packages.\n\nStdout: Reading package lists...\nBuilding dependency 
tree...\nReading state information...\nSome packages c
  ould not be installed. This may mean that you have\nrequested an impossible 
situation or if you are using the unstable\ndistribution that some required 
packages have not yet been created\nor been moved out of Incoming.\nThe 
following information may help
   to resolve the situation:\n\nThe following packages have unmet 
dependencies:\n ubuntu-aws-fips : Depends: linux-aws-fips (>= 5.15.0.1042.43) 
but it is not installable\n", {}]

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-advantage-tools 30~22.04
  ProcVersionSignature: Ubuntu 6.2.0-1016.16~22.04.1-aws 6.2.16
  Uname: Linux 6.2.0-1016-aws x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: aws
  CloudName: aws
  CloudPlatform: ec2
  CloudRegion: eu-central-1
  CloudSubPlatform: metadata (http://169.254.169.254)
  Date: Mon Nov 27 09:59:57 2023
  Ec2AMI: ami-097610d2a71255e7d
  Ec2AMIManifest: (unknown)
  Ec2Architecture: x86_64
  Ec2AvailabilityZone: eu-central-1a
  Ec2Imageid: ami-097610d2a71255e7d
  Ec2InstanceType: m6a.large
  Ec2Instancetype: m6a.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Ec2Region: eu-central-1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-advantage-tools
  UpgradeStatus: No upgrade log present (probably fresh install)
  cloud-id.txt: aws
  livepatch-status.txt-error:
   Failed running command '/snap/bin/canonical-livepatch status' [exit(1)]. 
Message: Machine is not enabled. Please run 'sudo canonical-livepatch enable' 
with the
   token obtained from https://ubuntu.com/livepatch.
  pro-journal.txt:
   Nov 27 09:57:07.273351 ip-172-31-20-161 systemd[1]: Condition check resulted 
in Ubuntu Pro reboot cmds being skipped.
   Nov 27 09:57:13.549831 ip-172-31-20-161 systemd[1]: Condition check resulted 
in Ubuntu Pro Background Auto Attach being skipped.
  uaclient.conf:
   contract_url: https://contracts.canonical.com
   log_level: debug


  Note: there is no hold package:
  # apt-mark showhold
  root@ip-172-31-20-161:~#

To man

[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform

Hello You-Sheng, or anyone else affected,

Accepted ipu6-drivers into mantic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/ipu6-drivers/0~git202310180730.3f813580-0ubuntu0.23.10.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
mantic to verification-done-mantic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-mantic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

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

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

Title:
  Support mipi camera on Intel Meteor Lake platform

Status in HWE Next:
  New
Status in ipu6-drivers package in Ubuntu:
  Fix Released
Status in ivsc-driver package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Jammy:
  Won't Fix
Status in ivsc-driver source package in Jammy:
  Won't Fix
Status in linux source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in ipu6-drivers source package in Mantic:
  Fix Committed
Status in ivsc-driver source package in Mantic:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in ipu6-drivers source package in Noble:
  Fix Released
Status in ivsc-driver source package in Noble:
  Fix Released
Status in linux source package in Noble:
  Triaged
Status in linux-firmware source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justification]

  == ipu6-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  Based on upstream tag
  https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019,
  and an additional patch to enable/fix compilation of additional sensor
  modules.

  [Test Case]

  This is verified on MTL Lattice and VSC platforms, as well as previous
  generations e.g. TGL and ADL.

  To actually verify the camera framework:
  ```
  # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14
  # reboot into the 6.5.0-14.14 kernel
  $ sudo apt install intel-ipu6-dkms intel-vsc-dkms
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, 
and their dependencies, are fetched from the oem-solutions-group PPA. 
Everything else must come from the mantic archive.

  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  This is a new platform. We've been verifying its functions and features, and
  are still polishing it.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == ivsc-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform. Need both
  firmware and driver change to probe the hardware correctly.

  [Fix]

  4 commits from the latest trunk branch on upstream repository
  https://github.com/intel/ivsc-driver.

  [Test Case]

  With all other changes in position, Intel VSC driver modules are to be
  loaded as a soft dependency of some selected camera sensor modules.
  LJCA modules should be loaded automatically on MTL platforms as well.

  To actually verify the camera framework:
  ```
  # enable mantic-proposed, update the kernel, make sure you ge

[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs

Could https://github.com/openzfs/zfs/pull/15651 be picked up for this
update still?

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

Title:
  Multiple data corruption issues in zfs

Status in zfs-linux package in Ubuntu:
  Fix Committed
Status in zfs-linux source package in Xenial:
  Confirmed
Status in zfs-linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Focal:
  Confirmed
Status in zfs-linux source package in Jammy:
  Confirmed
Status in zfs-linux source package in Lunar:
  Confirmed
Status in zfs-linux source package in Mantic:
  In Progress
Status in zfs-linux source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

   * Multiple data corruption issues have been identified and fixed in
  ZFS. Some of them, at varying real-life reproducibility frequency have
  been deterimed to affect very old zfs releases. Recommendation is to
  upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
  ensure users get other potentially related fixes and runtime tunables
  to possibly mitigate other bugs that are related and are being fixed
  upstream for future releases.

   * For jammy the 2.1.14 upgrade will bring HWE kernel support and also
  compatiblity/support for hardened kernel builds that mitigate SLS
  (straight-line-speculation).

  [ Test Plan ]

   * !!! Danger !!! use reproducer from
  https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
  and confirm if that issue is resolved or not. Do not run on production
  ZFS pools / systems.

   * autopkgtest pass (from https://ubuntu-archive-
  team.ubuntu.com/proposed-migration/ )

   * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )

   * kernel regression zfs testsuite pass (from Kernel team RT test
  results summary, private)

   * zsys integration test pass (upgrade of zsys installed systems for
  all releases)

   * zsys install test pass (for daily images of LTS releases only that
  have such installer support, as per iso tracker test case)

   * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
  2.1.14, and test LXD on these updated kernels)

  
  [ Where problems could occur ]

   * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will 
introduce slight slow down on amd64 (for hw accelerated assembly code-paths 
only in the encryption primitives)
   
   * Uncertain of the perfomance impact of the extra checks in dnat patch fix 
itself. Possibly affecting speed of operation, at the benefit of correctness.

  [ Other Info ]
   
   * https://github.com/openzfs/zfs/pull/15571 is most current consideration of 
affairs

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


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

[Kernel-packages] [Bug 2040181] Update Released

The verification of the Stable Release Update for zfs-linux 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 zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2040181

Title:
  upgrade zfs-linux to 2.2.0 final

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Mantic:
  Fix Committed
Status in zfs-linux source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

   * Potential data loss with zfs 2.2.0-rc3 resolved in -rc5, proposal
  to update to final

   * Ubuntu Mantic shipped 2.2.0-rc3 with approximately 10 additional
  cherrypicks, or kernel team created fixes that got contributed &
  accepted upstream. At the time this was the only way to get zfs
  working with  v6.5 kernels and also drop the need for shiftfs (due to
  zfs impovements). Since us shipping this package, upstream has
  identified and fixed multiple small bugfixes in the subsequent RC and
  the final releases, including one bug fix that can lead to potential
  data loss.

   * The 2.2.0 release branch was frozen for a long time already, and
  outstanding number of commits of fixes that Mantic does not have is
  less than 30 small patches.

   * Proposal to upgrade our build to 2.2.0 final, pick up all the
  regression fixes, and drop all the cherrypicked patches that enable
  v6.5 support. This will give us the best kernel driver to support in
  the runnup to next Ubuntu LTS.

  [ Test Plan ]

   * autopkgtest pass

   * kernel regression zfs testsuite pass

   * zsys integration test pass

   * LXD support retested

  [ Where problems could occur ]

   * LXD snap in edge shipped zfs tooling of RC5 version until 16th
  October when they upgraded to 2.2.0 final, there are no kernel-
  userspace incompatiblities between RC & final, but we should
  explicitly test this.

  [ Other Info ]

   * Upstream is alerting us to the potential data loss and requesting
  upgrade to 2.2.0-rc5 or better.

  [ Abbriviated changes being introduced ]

  $ git log --oneline 4a104ac047..95785196f2 -- cmd/ lib/ module/os/linux/ | 
grep -v compat
  810fc49a3e Ensure we call fput when cloning fails due to different devices.
  a80e1f1c90 zvol: Temporally disable blk-mq
  33d7c2d165 import: require force when cachefile hostid doesn't match on-disk
  8015e2ea66 Add '-u' - nomount flag for zfs set
  c53bc3837c Improve the handling of sharesmb,sharenfs properties
  e9dc31c74e Update the behavior of mountpoint property
  608741d062 Report ashift of L2ARC devices in zdb
  0ce1b2ca19 Invoke zdb by guid to avoid import errors
  0aabd6b482 ZIL: Avoid dbuf_read() in ztest_get_data()
  a199cac6cd status: report pool suspension state under failmode=continue
  729507d309 Fix occasional rsend test crashes
  3af63683fe cmd: add 'help' subcommand to zpool and zfs
  9aa1a2878e Fix incorrect expected error in ztest
  f7a07d76ee Retire z_nr_znodes
  54c6fbd378 zed: Allow autoreplace and fault LEDs for removed vdevs
  32949f2560 Relax error reporting in zpool import and zpool split
  63159e5bda checkstyle: fix action failures
  e99e684b33 zed: update zed.d/statechange-slot_off.sh
  d19304ffee zed: Add zedlet to power off slot when drive is faulted
  92f095a903 copy_file_range: fix fallback when source create on same txg
  895cb689d3 zfs_clone_range should return a descriptive error codes
  6bdc7259d1 libzfs: sendrecv: send_progress_thread: handle SIGINFO/SIGUSR1
  df8c9f351d ZIL: Second attempt to reduce scope of zl_issuer_lock.
  0ae7bfc0a4 zpool_vdev_remove() should handle EALREADY error return
  bd1eab16eb linux: zfs: ctldir: set [amc]time to snapshot's creation property
  c47f0f4417 linux/copy_file_range: properly request a fallback copy on Linux 
<5.3
  12f2b1f65e zdb: include cloned blocks in block statistics

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


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

[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs

Oh, I missed this bit in https://bugs.launchpad.net/ubuntu/+source/zfs-
linux/+bug/2040181/comments/10 in the other bug:

"It is still worth it to release this sru, before staging the next one
in proposed"

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

Title:
  Multiple data corruption issues in zfs

Status in zfs-linux package in Ubuntu:
  Fix Committed
Status in zfs-linux source package in Xenial:
  Confirmed
Status in zfs-linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Focal:
  Confirmed
Status in zfs-linux source package in Jammy:
  Confirmed
Status in zfs-linux source package in Lunar:
  Confirmed
Status in zfs-linux source package in Mantic:
  In Progress
Status in zfs-linux source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

   * Multiple data corruption issues have been identified and fixed in
  ZFS. Some of them, at varying real-life reproducibility frequency have
  been deterimed to affect very old zfs releases. Recommendation is to
  upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
  ensure users get other potentially related fixes and runtime tunables
  to possibly mitigate other bugs that are related and are being fixed
  upstream for future releases.

   * For jammy the 2.1.14 upgrade will bring HWE kernel support and also
  compatiblity/support for hardened kernel builds that mitigate SLS
  (straight-line-speculation).

  [ Test Plan ]

   * !!! Danger !!! use reproducer from
  https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
  and confirm if that issue is resolved or not. Do not run on production
  ZFS pools / systems.

   * autopkgtest pass (from https://ubuntu-archive-
  team.ubuntu.com/proposed-migration/ )

   * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )

   * kernel regression zfs testsuite pass (from Kernel team RT test
  results summary, private)

   * zsys integration test pass (upgrade of zsys installed systems for
  all releases)

   * zsys install test pass (for daily images of LTS releases only that
  have such installer support, as per iso tracker test case)

   * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
  2.1.14, and test LXD on these updated kernels)

  
  [ Where problems could occur ]

   * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will 
introduce slight slow down on amd64 (for hw accelerated assembly code-paths 
only in the encryption primitives)
   
   * Uncertain of the perfomance impact of the extra checks in dnat patch fix 
itself. Possibly affecting speed of operation, at the benefit of correctness.

  [ Other Info ]
   
   * https://github.com/openzfs/zfs/pull/15571 is most current consideration of 
affairs

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


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

[Kernel-packages] [Bug 2045778] Re: panic due to unhandled page fault via BPF_PROG_RUN syscall

2023-12-07 Thread Joseph Salisbury

We would like to collect some additional information about your system.
>From a terminal, please run the following:

apport-collect BUG_ID
or to a file:
apport-bug --save /tmp/report.BUG_ID linux

If apport can't be run:
1) uname -a > uname-a.log
2) dmesg > dmesg.log
3) sudo lspci -vvnn > lspci-vvnn.log
4) cat /proc/version_signature > version.log


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

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

** Changed in: linux-azure (Ubuntu)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

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

Title:
  panic due to unhandled page fault via BPF_PROG_RUN syscall

Status in linux-azure package in Ubuntu:
  Triaged

Bug description:
  Here is a kernel oops triggered from user space by invoking a BPF
  program:

  [ 1191.051531] BUG: unable to handle page fault for address: ea053c70
  [ 1191.053848] #PF: supervisor read access in kernel mode
  [ 1191.055183] #PF: error_code(0x) - not-present page
  [ 1191.056513] PGD 334e15067 P4D 334e15067 PUD 334e17067 PMD 0 
  [ 1191.058016] Oops:  [#1] SMP NOPTI
  [ 1191.058984] CPU: 1 PID: 2557 Comm: ebpf.test Not tainted 6.2.0-1016-azure 
#16~22.04.1-Ubuntu
  [ 1191.061167] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090008  12/07/2018
  [ 1191.063804] RIP: 0010:bpf_test_run+0x104/0x2e0
  [ 1191.065064] Code: 00 00 48 89 90 50 14 00 00 48 89 b5 60 ff ff ff eb 3e 0f 
1f 44 00 00 48 8b 53 30 4c 89 ee 4c 89 e7 e8 50 8c f8 ff 89 c2 66 90 <48> 8b 45 
80 4d 89 f0 48 8d 4d 8c be 01 00 00 00 48 8d 7d a0 89 10
  [ 1191.069766] RSP: 0018:a64e03053c50 EFLAGS: 00010246
  [ 1191.071117] RAX: 0001 RBX: a64e0005a000 RCX: 
a64e03053c3f
  [ 1191.073415] RDX: 0001 RSI: a64e03053c3f RDI: 
8a468580
  [ 1191.075351] RBP: ea053cf0 R08:  R09: 

  [ 1191.077722] R10:  R11:  R12: 
97dc75673c00
  [ 1191.079681] R13: a64e0005a048 R14: a64e03053d34 R15: 
0001
  [ 1191.081636] FS:  7fd4a2ffd640() GS:97df6fc8() 
knlGS:
  [ 1191.083866] CS:  0010 DS:  ES:  CR0: 80050033
  [ 1191.085455] CR2: ea053c70 CR3: 00019ff80001 CR4: 
00370ee0
  [ 1191.087405] Call Trace:
  [ 1191.088121]  
  [ 1191.088745]  ? show_regs+0x6a/0x80
  [ 1191.089710]  ? __die+0x25/0x70
  [ 1191.090591]  ? page_fault_oops+0x79/0x180
  [ 1191.091708]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.093027]  ? search_exception_tables+0x61/0x70
  [ 1191.094421]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.095686]  ? kernelmode_fixup_or_oops+0xa2/0x120
  [ 1191.097014]  ? __bad_area_nosemaphore+0x16f/0x280
  [ 1191.098323]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.099584]  ? apparmor_file_alloc_security+0x1f/0xd0
  [ 1191.100989]  ? bad_area_nosemaphore+0x16/0x20
  [ 1191.102235]  ? do_kern_addr_fault+0x62/0x80
  [ 1191.103393]  ? exc_page_fault+0xd8/0x160
  [ 1191.104505]  ? asm_exc_page_fault+0x27/0x30
  [ 1191.105669]  ? bpf_test_run+0x104/0x2e0
  [ 1191.106745]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.108010]  ? bpf_prog_test_run_skb+0x2e4/0x4f0
  [ 1191.109350]  ? __fdget+0x13/0x20
  [ 1191.110304]  ? __sys_bpf+0x706/0xea0
  [ 1191.111299]  ? __x64_sys_bpf+0x1a/0x30
  [ 1191.112307]  ? do_syscall_64+0x5c/0x90
  [ 1191.113366]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.114634]  ? exit_to_user_mode_loop+0xec/0x160
  [ 1191.115929]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.117466]  ? __set_task_blocked+0x29/0x70
  [ 1191.118904]  ? exit_to_user_mode_prepare+0x49/0x100
  [ 1191.120482]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.122073]  ? sigprocmask+0xb8/0xe0
  [ 1191.123360]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.124868]  ? exit_to_user_mode_prepare+0x49/0x100
  [ 1191.126523]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.128028]  ? syscall_exit_to_user_mode+0x27/0x40
  [ 1191.129599]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.131033]  ? do_syscall_64+0x69/0x90
  [ 1191.132242]  ? srso_alias_return_thunk+0x5/0x7f
  [ 1191.134199]  ? do_syscall_64+0x69/0x90
  [ 1191.135504]  ? entry_SYSCALL_64_after_hwframe+0x73/0xdd
  [ 1191.137137]  
  [ 1191.137942] Modules linked in: nft_chain_nat xt_MASQUERADE nf_nat 
nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter bridge stp 
llc xt_tcpudp tls xt_owner xt_conntrack nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 nft_compat nf_tables libcrc32c nfnetlink overlay nvme_fabrics 
udf crc_itu_t binfmt_misc nls_iso8859_1 kvm_amd ccp joydev kvm hid_generic 
irqbypass crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic 
ghash_clmulni_intel sha512_ssse3 aesni_intel crypto_simd cryptd hyperv_drm 
drm_kms_helper syscopyarea sysfillrect serio_raw sysimgblt drm_shm

[Kernel-packages] [Bug 2043197] Re: USB bus error after upgrading to proposed kernel on lunar, jammy and focal

This bug is awaiting verification that the linux-oracle/5.4.0-1115.124
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-oracle' to 'verification-done-
focal-linux-oracle'. If the problem still exists, change the tag
'verification-needed-focal-linux-oracle' to 'verification-failed-focal-
linux-oracle'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-focal-linux-oracle-v2 
verification-needed-focal-linux-oracle

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

Title:
  USB bus error after upgrading to proposed kernel on lunar, jammy and
  focal

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  USB SuperSpeed (3.0) devcies can't be enumerated on Lunar/Jammy kernel.

  [Fix]
  Use logarithmic encoding for the bMaxPacketSize0 value.

  [Test]
  With the patch applied, SuperSpeed devices can be enumerated across
  several reboots.

  [Where problems could occur]
  The switch case for Wireless USB (not USB WiFi dongle) was removed by
  the fix. I am not aware of the existence of any Wireless USB device. But
  if they do exist, this patch may the packet size encoding on them.

  == Original Bug Report ==
  [Summary]
  Some of machines in cert lab after upgrading to proposed kernel on jammy and 
lunar, all usb devices were gone.

  I found this issue on linux-image-6.2.0-38-generic and linux-
  image-5.15.0-90-generic on some specific machines.

  Since some of machines are using usb ethernet adapter so after
  upgrading, those machines are not accessible.

  Following are the machine list I've seen impacted by this issue, I
  believe there will be more if I check further.

  https://certification.canonical.com/hardware/202005-27899/
  https://certification.canonical.com/hardware/201903-26881/
  https://certification.canonical.com/hardware/201903-26932/
  https://certification.canonical.com/hardware/202005-27944/
  https://certification.canonical.com/hardware/202008-28166/
  https://certification.canonical.com/hardware/202008-28167/
  https://certification.canonical.com/hardware/202102-28728/
  https://certification.canonical.com/hardware/202008-28176/
  https://certification.canonical.com/hardware/202008-28177/
  https://certification.canonical.com/hardware/202202-29946/

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-90-generic 5.15.0-90.100
  ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131
  Uname: Linux 5.15.0-90-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.15.0-90-generic.
  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/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/)
  Date: Fri Nov 10 12:04:10 2023
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth
   Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Wide Vision HD Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProOne 600 G6
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic 
root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-90-generic N/A
   linux-backports-modules-5.15.0-90-generic  N/A
   linux-firmware 20220329.git6812

[Kernel-packages] [Bug 2043197] Re: USB bus error after upgrading to proposed kernel on lunar, jammy and focal

This bug is awaiting verification that the linux-
gcp-5.15/5.15.0-1048.56~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
gcp-5.15' to 'verification-done-focal-linux-gcp-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-gcp-5.15'
to 'verification-failed-focal-linux-gcp-5.15'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-focal-linux-gcp-5.15-v2 
verification-needed-focal-linux-gcp-5.15

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

Title:
  USB bus error after upgrading to proposed kernel on lunar, jammy and
  focal

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  USB SuperSpeed (3.0) devcies can't be enumerated on Lunar/Jammy kernel.

  [Fix]
  Use logarithmic encoding for the bMaxPacketSize0 value.

  [Test]
  With the patch applied, SuperSpeed devices can be enumerated across
  several reboots.

  [Where problems could occur]
  The switch case for Wireless USB (not USB WiFi dongle) was removed by
  the fix. I am not aware of the existence of any Wireless USB device. But
  if they do exist, this patch may the packet size encoding on them.

  == Original Bug Report ==
  [Summary]
  Some of machines in cert lab after upgrading to proposed kernel on jammy and 
lunar, all usb devices were gone.

  I found this issue on linux-image-6.2.0-38-generic and linux-
  image-5.15.0-90-generic on some specific machines.

  Since some of machines are using usb ethernet adapter so after
  upgrading, those machines are not accessible.

  Following are the machine list I've seen impacted by this issue, I
  believe there will be more if I check further.

  https://certification.canonical.com/hardware/202005-27899/
  https://certification.canonical.com/hardware/201903-26881/
  https://certification.canonical.com/hardware/201903-26932/
  https://certification.canonical.com/hardware/202005-27944/
  https://certification.canonical.com/hardware/202008-28166/
  https://certification.canonical.com/hardware/202008-28167/
  https://certification.canonical.com/hardware/202102-28728/
  https://certification.canonical.com/hardware/202008-28176/
  https://certification.canonical.com/hardware/202008-28177/
  https://certification.canonical.com/hardware/202202-29946/

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-90-generic 5.15.0-90.100
  ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131
  Uname: Linux 5.15.0-90-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.15.0-90-generic.
  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/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/)
  Date: Fri Nov 10 12:04:10 2023
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth
   Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Wide Vision HD Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProOne 600 G6
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic 
root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-90-generic N/A
   linux-backports-modules-5.15.0-90-generic  N/A
   linux-firmware

[Kernel-packages] [Bug 2043197] Re: USB bus error after upgrading to proposed kernel on lunar, jammy and focal

This bug is awaiting verification that the linux-oracle/5.4.0-1115.124
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-oracle' to 'verification-done-
focal-linux-oracle'. If the problem still exists, change the tag
'verification-needed-focal-linux-oracle' to 'verification-failed-focal-
linux-oracle'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  USB bus error after upgrading to proposed kernel on lunar, jammy and
  focal

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  USB SuperSpeed (3.0) devcies can't be enumerated on Lunar/Jammy kernel.

  [Fix]
  Use logarithmic encoding for the bMaxPacketSize0 value.

  [Test]
  With the patch applied, SuperSpeed devices can be enumerated across
  several reboots.

  [Where problems could occur]
  The switch case for Wireless USB (not USB WiFi dongle) was removed by
  the fix. I am not aware of the existence of any Wireless USB device. But
  if they do exist, this patch may the packet size encoding on them.

  == Original Bug Report ==
  [Summary]
  Some of machines in cert lab after upgrading to proposed kernel on jammy and 
lunar, all usb devices were gone.

  I found this issue on linux-image-6.2.0-38-generic and linux-
  image-5.15.0-90-generic on some specific machines.

  Since some of machines are using usb ethernet adapter so after
  upgrading, those machines are not accessible.

  Following are the machine list I've seen impacted by this issue, I
  believe there will be more if I check further.

  https://certification.canonical.com/hardware/202005-27899/
  https://certification.canonical.com/hardware/201903-26881/
  https://certification.canonical.com/hardware/201903-26932/
  https://certification.canonical.com/hardware/202005-27944/
  https://certification.canonical.com/hardware/202008-28166/
  https://certification.canonical.com/hardware/202008-28167/
  https://certification.canonical.com/hardware/202102-28728/
  https://certification.canonical.com/hardware/202008-28176/
  https://certification.canonical.com/hardware/202008-28177/
  https://certification.canonical.com/hardware/202202-29946/

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-90-generic 5.15.0-90.100
  ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131
  Uname: Linux 5.15.0-90-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.15.0-90-generic.
  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/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/)
  Date: Fri Nov 10 12:04:10 2023
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth
   Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Wide Vision HD Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProOne 600 G6
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic 
root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-90-generic N/A
   linux-backports-modules-5.15.0-90-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.22
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackag

[Kernel-packages] [Bug 2043197] Re: USB bus error after upgrading to proposed kernel on lunar, jammy and focal

This bug is awaiting verification that the linux-iot/5.4.0-1028.29
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-iot' to 'verification-done-focal-
linux-iot'. If the problem still exists, change the tag 'verification-
needed-focal-linux-iot' to 'verification-failed-focal-linux-iot'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-focal-linux-iot-v2 
verification-needed-focal-linux-iot

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

Title:
  USB bus error after upgrading to proposed kernel on lunar, jammy and
  focal

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  USB SuperSpeed (3.0) devcies can't be enumerated on Lunar/Jammy kernel.

  [Fix]
  Use logarithmic encoding for the bMaxPacketSize0 value.

  [Test]
  With the patch applied, SuperSpeed devices can be enumerated across
  several reboots.

  [Where problems could occur]
  The switch case for Wireless USB (not USB WiFi dongle) was removed by
  the fix. I am not aware of the existence of any Wireless USB device. But
  if they do exist, this patch may the packet size encoding on them.

  == Original Bug Report ==
  [Summary]
  Some of machines in cert lab after upgrading to proposed kernel on jammy and 
lunar, all usb devices were gone.

  I found this issue on linux-image-6.2.0-38-generic and linux-
  image-5.15.0-90-generic on some specific machines.

  Since some of machines are using usb ethernet adapter so after
  upgrading, those machines are not accessible.

  Following are the machine list I've seen impacted by this issue, I
  believe there will be more if I check further.

  https://certification.canonical.com/hardware/202005-27899/
  https://certification.canonical.com/hardware/201903-26881/
  https://certification.canonical.com/hardware/201903-26932/
  https://certification.canonical.com/hardware/202005-27944/
  https://certification.canonical.com/hardware/202008-28166/
  https://certification.canonical.com/hardware/202008-28167/
  https://certification.canonical.com/hardware/202102-28728/
  https://certification.canonical.com/hardware/202008-28176/
  https://certification.canonical.com/hardware/202008-28177/
  https://certification.canonical.com/hardware/202202-29946/

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-90-generic 5.15.0-90.100
  ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131
  Uname: Linux 5.15.0-90-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.15.0-90-generic.
  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/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/)
  Date: Fri Nov 10 12:04:10 2023
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth
   Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Wide Vision HD Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProOne 600 G6
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic 
root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-90-generic N/A
   linux-backports-modules-5.15.0-90-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.22
  RfK

[Kernel-packages] [Bug 2043197] Re: USB bus error after upgrading to proposed kernel on lunar, jammy and focal

This bug is awaiting verification that the linux-raspi/5.4.0-1100.112
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-raspi' to 'verification-done-focal-
linux-raspi'. If the problem still exists, change the tag 'verification-
needed-focal-linux-raspi' to 'verification-failed-focal-linux-raspi'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-focal-linux-raspi-v2 
verification-needed-focal-linux-raspi

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

Title:
  USB bus error after upgrading to proposed kernel on lunar, jammy and
  focal

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  USB SuperSpeed (3.0) devcies can't be enumerated on Lunar/Jammy kernel.

  [Fix]
  Use logarithmic encoding for the bMaxPacketSize0 value.

  [Test]
  With the patch applied, SuperSpeed devices can be enumerated across
  several reboots.

  [Where problems could occur]
  The switch case for Wireless USB (not USB WiFi dongle) was removed by
  the fix. I am not aware of the existence of any Wireless USB device. But
  if they do exist, this patch may the packet size encoding on them.

  == Original Bug Report ==
  [Summary]
  Some of machines in cert lab after upgrading to proposed kernel on jammy and 
lunar, all usb devices were gone.

  I found this issue on linux-image-6.2.0-38-generic and linux-
  image-5.15.0-90-generic on some specific machines.

  Since some of machines are using usb ethernet adapter so after
  upgrading, those machines are not accessible.

  Following are the machine list I've seen impacted by this issue, I
  believe there will be more if I check further.

  https://certification.canonical.com/hardware/202005-27899/
  https://certification.canonical.com/hardware/201903-26881/
  https://certification.canonical.com/hardware/201903-26932/
  https://certification.canonical.com/hardware/202005-27944/
  https://certification.canonical.com/hardware/202008-28166/
  https://certification.canonical.com/hardware/202008-28167/
  https://certification.canonical.com/hardware/202102-28728/
  https://certification.canonical.com/hardware/202008-28176/
  https://certification.canonical.com/hardware/202008-28177/
  https://certification.canonical.com/hardware/202202-29946/

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-90-generic 5.15.0-90.100
  ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131
  Uname: Linux 5.15.0-90-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.15.0-90-generic.
  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/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/)
  Date: Fri Nov 10 12:04:10 2023
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth
   Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Wide Vision HD Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProOne 600 G6
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic 
root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-90-generic N/A
   linux-backports-modules-5.15.0-90-generic  N/A
   linux-firmware 20220329.git681281e4-0u

[Kernel-packages] [Bug 2043197] Re: USB bus error after upgrading to proposed kernel on lunar, jammy and focal

This bug is awaiting verification that the linux-gkeop/5.4.0-1083.87
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-gkeop' to 'verification-done-focal-
linux-gkeop'. If the problem still exists, change the tag 'verification-
needed-focal-linux-gkeop' to 'verification-failed-focal-linux-gkeop'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-focal-linux-gkeop-v2 
verification-needed-focal-linux-gkeop

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

Title:
  USB bus error after upgrading to proposed kernel on lunar, jammy and
  focal

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  USB SuperSpeed (3.0) devcies can't be enumerated on Lunar/Jammy kernel.

  [Fix]
  Use logarithmic encoding for the bMaxPacketSize0 value.

  [Test]
  With the patch applied, SuperSpeed devices can be enumerated across
  several reboots.

  [Where problems could occur]
  The switch case for Wireless USB (not USB WiFi dongle) was removed by
  the fix. I am not aware of the existence of any Wireless USB device. But
  if they do exist, this patch may the packet size encoding on them.

  == Original Bug Report ==
  [Summary]
  Some of machines in cert lab after upgrading to proposed kernel on jammy and 
lunar, all usb devices were gone.

  I found this issue on linux-image-6.2.0-38-generic and linux-
  image-5.15.0-90-generic on some specific machines.

  Since some of machines are using usb ethernet adapter so after
  upgrading, those machines are not accessible.

  Following are the machine list I've seen impacted by this issue, I
  believe there will be more if I check further.

  https://certification.canonical.com/hardware/202005-27899/
  https://certification.canonical.com/hardware/201903-26881/
  https://certification.canonical.com/hardware/201903-26932/
  https://certification.canonical.com/hardware/202005-27944/
  https://certification.canonical.com/hardware/202008-28166/
  https://certification.canonical.com/hardware/202008-28167/
  https://certification.canonical.com/hardware/202102-28728/
  https://certification.canonical.com/hardware/202008-28176/
  https://certification.canonical.com/hardware/202008-28177/
  https://certification.canonical.com/hardware/202202-29946/

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-90-generic 5.15.0-90.100
  ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131
  Uname: Linux 5.15.0-90-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.15.0-90-generic.
  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/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/)
  Date: Fri Nov 10 12:04:10 2023
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth
   Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Wide Vision HD Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProOne 600 G6
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic 
root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-90-generic N/A
   linux-backports-modules-5.15.0-90-generic  N/A
   linux-firmware 20220329.git681281e4-0ub

[Kernel-packages] [Bug 2043197] Re: USB bus error after upgrading to proposed kernel on lunar, jammy and focal

This bug is awaiting verification that the linux-
lowlatency/5.15.0-91.101 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-lowlatency' to
'verification-done-jammy-linux-lowlatency'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-lowlatency' to
'verification-failed-jammy-linux-lowlatency'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-lowlatency-v2 
verification-needed-jammy-linux-lowlatency

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

Title:
  USB bus error after upgrading to proposed kernel on lunar, jammy and
  focal

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  USB SuperSpeed (3.0) devcies can't be enumerated on Lunar/Jammy kernel.

  [Fix]
  Use logarithmic encoding for the bMaxPacketSize0 value.

  [Test]
  With the patch applied, SuperSpeed devices can be enumerated across
  several reboots.

  [Where problems could occur]
  The switch case for Wireless USB (not USB WiFi dongle) was removed by
  the fix. I am not aware of the existence of any Wireless USB device. But
  if they do exist, this patch may the packet size encoding on them.

  == Original Bug Report ==
  [Summary]
  Some of machines in cert lab after upgrading to proposed kernel on jammy and 
lunar, all usb devices were gone.

  I found this issue on linux-image-6.2.0-38-generic and linux-
  image-5.15.0-90-generic on some specific machines.

  Since some of machines are using usb ethernet adapter so after
  upgrading, those machines are not accessible.

  Following are the machine list I've seen impacted by this issue, I
  believe there will be more if I check further.

  https://certification.canonical.com/hardware/202005-27899/
  https://certification.canonical.com/hardware/201903-26881/
  https://certification.canonical.com/hardware/201903-26932/
  https://certification.canonical.com/hardware/202005-27944/
  https://certification.canonical.com/hardware/202008-28166/
  https://certification.canonical.com/hardware/202008-28167/
  https://certification.canonical.com/hardware/202102-28728/
  https://certification.canonical.com/hardware/202008-28176/
  https://certification.canonical.com/hardware/202008-28177/
  https://certification.canonical.com/hardware/202202-29946/

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-90-generic 5.15.0-90.100
  ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131
  Uname: Linux 5.15.0-90-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.15.0-90-generic.
  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/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/)
  Date: Fri Nov 10 12:04:10 2023
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth
   Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Wide Vision HD Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProOne 600 G6
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic 
root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-90-generic N/A
   linux-backports-modules-5.15.0-90-generic  N/A
   linux-firmware

[Kernel-packages] [Bug 2043197] Re: USB bus error after upgrading to proposed kernel on lunar, jammy and focal

This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1046.52 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-done-jammy-linux-intel-iotg'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-failed-jammy-linux-intel-iotg'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-intel-iotg-v2 
verification-needed-jammy-linux-intel-iotg

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

Title:
  USB bus error after upgrading to proposed kernel on lunar, jammy and
  focal

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  USB SuperSpeed (3.0) devcies can't be enumerated on Lunar/Jammy kernel.

  [Fix]
  Use logarithmic encoding for the bMaxPacketSize0 value.

  [Test]
  With the patch applied, SuperSpeed devices can be enumerated across
  several reboots.

  [Where problems could occur]
  The switch case for Wireless USB (not USB WiFi dongle) was removed by
  the fix. I am not aware of the existence of any Wireless USB device. But
  if they do exist, this patch may the packet size encoding on them.

  == Original Bug Report ==
  [Summary]
  Some of machines in cert lab after upgrading to proposed kernel on jammy and 
lunar, all usb devices were gone.

  I found this issue on linux-image-6.2.0-38-generic and linux-
  image-5.15.0-90-generic on some specific machines.

  Since some of machines are using usb ethernet adapter so after
  upgrading, those machines are not accessible.

  Following are the machine list I've seen impacted by this issue, I
  believe there will be more if I check further.

  https://certification.canonical.com/hardware/202005-27899/
  https://certification.canonical.com/hardware/201903-26881/
  https://certification.canonical.com/hardware/201903-26932/
  https://certification.canonical.com/hardware/202005-27944/
  https://certification.canonical.com/hardware/202008-28166/
  https://certification.canonical.com/hardware/202008-28167/
  https://certification.canonical.com/hardware/202102-28728/
  https://certification.canonical.com/hardware/202008-28176/
  https://certification.canonical.com/hardware/202008-28177/
  https://certification.canonical.com/hardware/202202-29946/

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-90-generic 5.15.0-90.100
  ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131
  Uname: Linux 5.15.0-90-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.15.0-90-generic.
  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/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/)
  Date: Fri Nov 10 12:04:10 2023
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth
   Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Wide Vision HD Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProOne 600 G6
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic 
root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-90-generic N/A
   linux-backports-modules-5.15.0-90-generic  N/A
   linux-firmware

[Kernel-packages] [Bug 2043197] Re: USB bus error after upgrading to proposed kernel on lunar, jammy and focal

This bug is awaiting verification that the linux-gkeop/5.15.0-1034.40
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-gkeop' to 'verification-done-jammy-
linux-gkeop'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-gkeop' to 'verification-failed-jammy-linux-gkeop'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-gkeop-v2 
verification-needed-jammy-linux-gkeop

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

Title:
  USB bus error after upgrading to proposed kernel on lunar, jammy and
  focal

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  USB SuperSpeed (3.0) devcies can't be enumerated on Lunar/Jammy kernel.

  [Fix]
  Use logarithmic encoding for the bMaxPacketSize0 value.

  [Test]
  With the patch applied, SuperSpeed devices can be enumerated across
  several reboots.

  [Where problems could occur]
  The switch case for Wireless USB (not USB WiFi dongle) was removed by
  the fix. I am not aware of the existence of any Wireless USB device. But
  if they do exist, this patch may the packet size encoding on them.

  == Original Bug Report ==
  [Summary]
  Some of machines in cert lab after upgrading to proposed kernel on jammy and 
lunar, all usb devices were gone.

  I found this issue on linux-image-6.2.0-38-generic and linux-
  image-5.15.0-90-generic on some specific machines.

  Since some of machines are using usb ethernet adapter so after
  upgrading, those machines are not accessible.

  Following are the machine list I've seen impacted by this issue, I
  believe there will be more if I check further.

  https://certification.canonical.com/hardware/202005-27899/
  https://certification.canonical.com/hardware/201903-26881/
  https://certification.canonical.com/hardware/201903-26932/
  https://certification.canonical.com/hardware/202005-27944/
  https://certification.canonical.com/hardware/202008-28166/
  https://certification.canonical.com/hardware/202008-28167/
  https://certification.canonical.com/hardware/202102-28728/
  https://certification.canonical.com/hardware/202008-28176/
  https://certification.canonical.com/hardware/202008-28177/
  https://certification.canonical.com/hardware/202202-29946/

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-90-generic 5.15.0-90.100
  ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131
  Uname: Linux 5.15.0-90-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.15.0-90-generic.
  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/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/)
  Date: Fri Nov 10 12:04:10 2023
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth
   Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Wide Vision HD Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProOne 600 G6
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic 
root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-90-generic N/A
   linux-backports-modules-5.15.0-90-generic  N/A
   linux-firmware 20220329.git681281e4-0u

[Kernel-packages] [Bug 2033406] Re: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module

This bug is awaiting verification that the linux-
gcp-5.15/5.15.0-1048.56~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
gcp-5.15' to 'verification-done-focal-linux-gcp-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-gcp-5.15'
to 'verification-failed-focal-linux-gcp-5.15'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-focal-linux-gcp-5.15-v2 
verification-needed-focal-linux-gcp-5.15

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

Title:
  [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module

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

Bug description:
  == SRU Justification ==
  The CONFIG_WWAN config is set to 'Y' for the generic and most derivative 
kernels.  This is affecting custom driver development for some partners.

  Change this config to be a loadable module and include it in linux-
  modules-*.

  Make this change to -generic kernels, so all derivatives will inherit
  it.

  
  == Fix ==
  UBUNTU: [Packaging] Make WWAN driver loadable modules

  
  == Regression Potential ==
  Medium.  This change is only to WWAN, and is changing it to a loadable module 
and not removing it.

  == Test Case ==
  A test kernel was built with this patch and tested by a partner.  It was also 
compile and boot tested internally.  Testing will also be performed on a WWAN 
device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033406/+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 2033406] Re: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module

This bug is awaiting verification that the linux-
lowlatency/5.15.0-91.101 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-lowlatency' to
'verification-done-jammy-linux-lowlatency'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-lowlatency' to
'verification-failed-jammy-linux-lowlatency'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-lowlatency-v2 
verification-needed-jammy-linux-lowlatency

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

Title:
  [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module

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

Bug description:
  == SRU Justification ==
  The CONFIG_WWAN config is set to 'Y' for the generic and most derivative 
kernels.  This is affecting custom driver development for some partners.

  Change this config to be a loadable module and include it in linux-
  modules-*.

  Make this change to -generic kernels, so all derivatives will inherit
  it.

  
  == Fix ==
  UBUNTU: [Packaging] Make WWAN driver loadable modules

  
  == Regression Potential ==
  Medium.  This change is only to WWAN, and is changing it to a loadable module 
and not removing it.

  == Test Case ==
  A test kernel was built with this patch and tested by a partner.  It was also 
compile and boot tested internally.  Testing will also be performed on a WWAN 
device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033406/+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 2033406] Re: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module

This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1046.52 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-done-jammy-linux-intel-iotg'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-failed-jammy-linux-intel-iotg'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-intel-iotg-v2 
verification-needed-jammy-linux-intel-iotg

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

Title:
  [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module

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

Bug description:
  == SRU Justification ==
  The CONFIG_WWAN config is set to 'Y' for the generic and most derivative 
kernels.  This is affecting custom driver development for some partners.

  Change this config to be a loadable module and include it in linux-
  modules-*.

  Make this change to -generic kernels, so all derivatives will inherit
  it.

  
  == Fix ==
  UBUNTU: [Packaging] Make WWAN driver loadable modules

  
  == Regression Potential ==
  Medium.  This change is only to WWAN, and is changing it to a loadable module 
and not removing it.

  == Test Case ==
  A test kernel was built with this patch and tested by a partner.  It was also 
compile and boot tested internally.  Testing will also be performed on a WWAN 
device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033406/+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 2033406] Re: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module

This bug is awaiting verification that the linux-gkeop/5.15.0-1034.40
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-gkeop' to 'verification-done-jammy-
linux-gkeop'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-gkeop' to 'verification-failed-jammy-linux-gkeop'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-gkeop-v2 
verification-needed-jammy-linux-gkeop

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

Title:
  [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module

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

Bug description:
  == SRU Justification ==
  The CONFIG_WWAN config is set to 'Y' for the generic and most derivative 
kernels.  This is affecting custom driver development for some partners.

  Change this config to be a loadable module and include it in linux-
  modules-*.

  Make this change to -generic kernels, so all derivatives will inherit
  it.

  
  == Fix ==
  UBUNTU: [Packaging] Make WWAN driver loadable modules

  
  == Regression Potential ==
  Medium.  This change is only to WWAN, and is changing it to a loadable module 
and not removing it.

  == Test Case ==
  A test kernel was built with this patch and tested by a partner.  It was also 
compile and boot tested internally.  Testing will also be performed on a WWAN 
device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033406/+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 2035123] Re: scripts/pahole-flags.sh change return to exit 0

This bug is awaiting verification that the linux-
gcp-5.15/5.15.0-1048.56~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
gcp-5.15' to 'verification-done-focal-linux-gcp-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-gcp-5.15'
to 'verification-failed-focal-linux-gcp-5.15'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-focal-linux-gcp-5.15-v2 
verification-needed-focal-linux-gcp-5.15

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

Title:
  scripts/pahole-flags.sh change return to exit 0

Status in linux package in Ubuntu:
  Fix Released
Status in linux-bluefield package in Ubuntu:
  Triaged
Status in linux source package in Jammy:
  Fix Released
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/2035123

  [Impact]

  When building the Jammy linux-bluefield kernel tree on a system
  without pahole installed, the following warning is emitted:

  ./scripts/pahole-flags.sh: line 7: return: can only `return' from a
  function or sourced script

  scripts/pahole-flags.sh attempts to return from an if statement that
  is not within a function, and generates a warning.

  The fix is straightforward, changing return to an exit 0.

  --- a/scripts/pahole-flags.sh
  +++ b/scripts/pahole-flags.sh
  @@ -4,7 +4,7 @@
   extra_paholeopt=

   if ! [ -x "$(command -v ${PAHOLE})" ]; then
  -   return
  +   exit 0
   fi

  [Testcase]

  Clone the linux-bluefield kernel tree and build it on a arm64 system without
  pahole installed.

  A test kernel is available with the fix applied in:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf368560-test

  Both linux-bluefield and ubuntu-jammy build correctly.

  [Fix]

  This was fixed by Linus Torvalds in the following merge commit:

  commit fc02cb2b37fe2cbf1d3334b9f0f0eab9431766c4
  Merge: bfc484fe6abb 84882cf72cd7
  Author: Linus Torvalds 
  Date:   Tue Nov 2 06:20:58 2021 -0700
  Subject: Merge tag 'net-next-for-5.16' of 
git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next
  Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fc02cb2b37fe2cbf1d3334b9f0f0eab9431766c4

  Note, the original commit does not have the fix included:

  commit 9741e07ece7c247dd65e1aa01e16b683f01c05a8
  Author: Jiri Olsa 
  Date:   Fri Oct 29 14:57:29 2021 +0200
  Subject: kbuild: Unify options for BTF generation for vmlinux and modules
  Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9741e07ece7c247dd65e1aa01e16b683f01c05a8

  The Ubuntu kernel cherry-picked the original commit and did not pick up the
  silent fix made in the merge commit. Submitting the silent fix as a SAUCE 
patch
  with changelog describing the change.

  Note: I know SAUCE patches are bad, but in this scenario, to revert
  the initial commit and re-apply the fixed version would require us to
  revert two additional dependency commits, making six patches to
  review, vs, a one line change in a SAUCE commit that has a real
  changelog entry.

  [Where problems could occur]

  The Ubuntu kernel is built with pahole enabled, and requires pahole to
  be installed as a build dependency. It is extremely unlikely that any
  users are disabling pahole at build time, apart from linux-bluefield
  engineers.

  If a regression were to occur, engineers would see errors during build
  time about scripts/pahole-flags.sh not executing properly.

  [Other info]

  Linus remarked about the issue in the following lkml discussion:

  
https://lore.kernel.org/lkml/CAHk-=wgdE6=ob5nf60gvryag24mkajbgjf3jpufme1k_upb...@mail.gmail.com/
  
https://lore.kernel.org/lkml/CAHk-=wgPZM4bN=LUCrMkG3FX808QSLm6Uv6ixm5P350_7c=x...@mail.gmail.com/

  This was silently Incorporated into the linux-stable commit:

  commit 0baced0e0938f2895ceba54038eaf15ed91032e7 5.15.y
  From: Jiri Olsa 
  Date: Sun, 4 Sep 2022 15:19:00 +0200
  Subject: kbuild: Unify options for BTF generation for vmlinux and modules
  Link: 
https://github.com/gregkh/linux/commit/0baced0e0938f2895ceba54038eaf15ed91032e7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035123/+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 2035123] Re: scripts/pahole-flags.sh change return to exit 0

This bug is awaiting verification that the linux-
lowlatency/5.15.0-91.101 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-lowlatency' to
'verification-done-jammy-linux-lowlatency'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-lowlatency' to
'verification-failed-jammy-linux-lowlatency'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-lowlatency-v2 
verification-needed-jammy-linux-lowlatency

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

Title:
  scripts/pahole-flags.sh change return to exit 0

Status in linux package in Ubuntu:
  Fix Released
Status in linux-bluefield package in Ubuntu:
  Triaged
Status in linux source package in Jammy:
  Fix Released
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/2035123

  [Impact]

  When building the Jammy linux-bluefield kernel tree on a system
  without pahole installed, the following warning is emitted:

  ./scripts/pahole-flags.sh: line 7: return: can only `return' from a
  function or sourced script

  scripts/pahole-flags.sh attempts to return from an if statement that
  is not within a function, and generates a warning.

  The fix is straightforward, changing return to an exit 0.

  --- a/scripts/pahole-flags.sh
  +++ b/scripts/pahole-flags.sh
  @@ -4,7 +4,7 @@
   extra_paholeopt=

   if ! [ -x "$(command -v ${PAHOLE})" ]; then
  -   return
  +   exit 0
   fi

  [Testcase]

  Clone the linux-bluefield kernel tree and build it on a arm64 system without
  pahole installed.

  A test kernel is available with the fix applied in:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf368560-test

  Both linux-bluefield and ubuntu-jammy build correctly.

  [Fix]

  This was fixed by Linus Torvalds in the following merge commit:

  commit fc02cb2b37fe2cbf1d3334b9f0f0eab9431766c4
  Merge: bfc484fe6abb 84882cf72cd7
  Author: Linus Torvalds 
  Date:   Tue Nov 2 06:20:58 2021 -0700
  Subject: Merge tag 'net-next-for-5.16' of 
git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next
  Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fc02cb2b37fe2cbf1d3334b9f0f0eab9431766c4

  Note, the original commit does not have the fix included:

  commit 9741e07ece7c247dd65e1aa01e16b683f01c05a8
  Author: Jiri Olsa 
  Date:   Fri Oct 29 14:57:29 2021 +0200
  Subject: kbuild: Unify options for BTF generation for vmlinux and modules
  Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9741e07ece7c247dd65e1aa01e16b683f01c05a8

  The Ubuntu kernel cherry-picked the original commit and did not pick up the
  silent fix made in the merge commit. Submitting the silent fix as a SAUCE 
patch
  with changelog describing the change.

  Note: I know SAUCE patches are bad, but in this scenario, to revert
  the initial commit and re-apply the fixed version would require us to
  revert two additional dependency commits, making six patches to
  review, vs, a one line change in a SAUCE commit that has a real
  changelog entry.

  [Where problems could occur]

  The Ubuntu kernel is built with pahole enabled, and requires pahole to
  be installed as a build dependency. It is extremely unlikely that any
  users are disabling pahole at build time, apart from linux-bluefield
  engineers.

  If a regression were to occur, engineers would see errors during build
  time about scripts/pahole-flags.sh not executing properly.

  [Other info]

  Linus remarked about the issue in the following lkml discussion:

  
https://lore.kernel.org/lkml/CAHk-=wgdE6=ob5nf60gvryag24mkajbgjf3jpufme1k_upb...@mail.gmail.com/
  
https://lore.kernel.org/lkml/CAHk-=wgPZM4bN=LUCrMkG3FX808QSLm6Uv6ixm5P350_7c=x...@mail.gmail.com/

  This was silently Incorporated into the linux-stable commit:

  commit 0baced0e0938f2895ceba54038eaf15ed91032e7 5.15.y
  From: Jiri Olsa 
  Date: Sun, 4 Sep 2022 15:19:00 +0200
  Subject: kbuild: Unify options for BTF generation for vmlinux and modules
  Link: 
https://github.com/gregkh/linux/commit/0baced0e0938f2895ceba54038eaf15ed91032e7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035123/+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 2035123] Re: scripts/pahole-flags.sh change return to exit 0

This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1046.52 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-done-jammy-linux-intel-iotg'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-failed-jammy-linux-intel-iotg'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-intel-iotg-v2 
verification-needed-jammy-linux-intel-iotg

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

Title:
  scripts/pahole-flags.sh change return to exit 0

Status in linux package in Ubuntu:
  Fix Released
Status in linux-bluefield package in Ubuntu:
  Triaged
Status in linux source package in Jammy:
  Fix Released
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/2035123

  [Impact]

  When building the Jammy linux-bluefield kernel tree on a system
  without pahole installed, the following warning is emitted:

  ./scripts/pahole-flags.sh: line 7: return: can only `return' from a
  function or sourced script

  scripts/pahole-flags.sh attempts to return from an if statement that
  is not within a function, and generates a warning.

  The fix is straightforward, changing return to an exit 0.

  --- a/scripts/pahole-flags.sh
  +++ b/scripts/pahole-flags.sh
  @@ -4,7 +4,7 @@
   extra_paholeopt=

   if ! [ -x "$(command -v ${PAHOLE})" ]; then
  -   return
  +   exit 0
   fi

  [Testcase]

  Clone the linux-bluefield kernel tree and build it on a arm64 system without
  pahole installed.

  A test kernel is available with the fix applied in:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf368560-test

  Both linux-bluefield and ubuntu-jammy build correctly.

  [Fix]

  This was fixed by Linus Torvalds in the following merge commit:

  commit fc02cb2b37fe2cbf1d3334b9f0f0eab9431766c4
  Merge: bfc484fe6abb 84882cf72cd7
  Author: Linus Torvalds 
  Date:   Tue Nov 2 06:20:58 2021 -0700
  Subject: Merge tag 'net-next-for-5.16' of 
git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next
  Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fc02cb2b37fe2cbf1d3334b9f0f0eab9431766c4

  Note, the original commit does not have the fix included:

  commit 9741e07ece7c247dd65e1aa01e16b683f01c05a8
  Author: Jiri Olsa 
  Date:   Fri Oct 29 14:57:29 2021 +0200
  Subject: kbuild: Unify options for BTF generation for vmlinux and modules
  Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9741e07ece7c247dd65e1aa01e16b683f01c05a8

  The Ubuntu kernel cherry-picked the original commit and did not pick up the
  silent fix made in the merge commit. Submitting the silent fix as a SAUCE 
patch
  with changelog describing the change.

  Note: I know SAUCE patches are bad, but in this scenario, to revert
  the initial commit and re-apply the fixed version would require us to
  revert two additional dependency commits, making six patches to
  review, vs, a one line change in a SAUCE commit that has a real
  changelog entry.

  [Where problems could occur]

  The Ubuntu kernel is built with pahole enabled, and requires pahole to
  be installed as a build dependency. It is extremely unlikely that any
  users are disabling pahole at build time, apart from linux-bluefield
  engineers.

  If a regression were to occur, engineers would see errors during build
  time about scripts/pahole-flags.sh not executing properly.

  [Other info]

  Linus remarked about the issue in the following lkml discussion:

  
https://lore.kernel.org/lkml/CAHk-=wgdE6=ob5nf60gvryag24mkajbgjf3jpufme1k_upb...@mail.gmail.com/
  
https://lore.kernel.org/lkml/CAHk-=wgPZM4bN=LUCrMkG3FX808QSLm6Uv6ixm5P350_7c=x...@mail.gmail.com/

  This was silently Incorporated into the linux-stable commit:

  commit 0baced0e0938f2895ceba54038eaf15ed91032e7 5.15.y
  From: Jiri Olsa 
  Date: Sun, 4 Sep 2022 15:19:00 +0200
  Subject: kbuild: Unify options for BTF generation for vmlinux and modules
  Link: 
https://github.com/gregkh/linux/commit/0baced0e0938f2895ceba54038eaf15ed91032e7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035123/+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 2035123] Re: scripts/pahole-flags.sh change return to exit 0

This bug is awaiting verification that the linux-gkeop/5.15.0-1034.40
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-gkeop' to 'verification-done-jammy-
linux-gkeop'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-gkeop' to 'verification-failed-jammy-linux-gkeop'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-gkeop-v2 
verification-needed-jammy-linux-gkeop

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

Title:
  scripts/pahole-flags.sh change return to exit 0

Status in linux package in Ubuntu:
  Fix Released
Status in linux-bluefield package in Ubuntu:
  Triaged
Status in linux source package in Jammy:
  Fix Released
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/2035123

  [Impact]

  When building the Jammy linux-bluefield kernel tree on a system
  without pahole installed, the following warning is emitted:

  ./scripts/pahole-flags.sh: line 7: return: can only `return' from a
  function or sourced script

  scripts/pahole-flags.sh attempts to return from an if statement that
  is not within a function, and generates a warning.

  The fix is straightforward, changing return to an exit 0.

  --- a/scripts/pahole-flags.sh
  +++ b/scripts/pahole-flags.sh
  @@ -4,7 +4,7 @@
   extra_paholeopt=

   if ! [ -x "$(command -v ${PAHOLE})" ]; then
  -   return
  +   exit 0
   fi

  [Testcase]

  Clone the linux-bluefield kernel tree and build it on a arm64 system without
  pahole installed.

  A test kernel is available with the fix applied in:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf368560-test

  Both linux-bluefield and ubuntu-jammy build correctly.

  [Fix]

  This was fixed by Linus Torvalds in the following merge commit:

  commit fc02cb2b37fe2cbf1d3334b9f0f0eab9431766c4
  Merge: bfc484fe6abb 84882cf72cd7
  Author: Linus Torvalds 
  Date:   Tue Nov 2 06:20:58 2021 -0700
  Subject: Merge tag 'net-next-for-5.16' of 
git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next
  Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fc02cb2b37fe2cbf1d3334b9f0f0eab9431766c4

  Note, the original commit does not have the fix included:

  commit 9741e07ece7c247dd65e1aa01e16b683f01c05a8
  Author: Jiri Olsa 
  Date:   Fri Oct 29 14:57:29 2021 +0200
  Subject: kbuild: Unify options for BTF generation for vmlinux and modules
  Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9741e07ece7c247dd65e1aa01e16b683f01c05a8

  The Ubuntu kernel cherry-picked the original commit and did not pick up the
  silent fix made in the merge commit. Submitting the silent fix as a SAUCE 
patch
  with changelog describing the change.

  Note: I know SAUCE patches are bad, but in this scenario, to revert
  the initial commit and re-apply the fixed version would require us to
  revert two additional dependency commits, making six patches to
  review, vs, a one line change in a SAUCE commit that has a real
  changelog entry.

  [Where problems could occur]

  The Ubuntu kernel is built with pahole enabled, and requires pahole to
  be installed as a build dependency. It is extremely unlikely that any
  users are disabling pahole at build time, apart from linux-bluefield
  engineers.

  If a regression were to occur, engineers would see errors during build
  time about scripts/pahole-flags.sh not executing properly.

  [Other info]

  Linus remarked about the issue in the following lkml discussion:

  
https://lore.kernel.org/lkml/CAHk-=wgdE6=ob5nf60gvryag24mkajbgjf3jpufme1k_upb...@mail.gmail.com/
  
https://lore.kernel.org/lkml/CAHk-=wgPZM4bN=LUCrMkG3FX808QSLm6Uv6ixm5P350_7c=x...@mail.gmail.com/

  This was silently Incorporated into the linux-stable commit:

  commit 0baced0e0938f2895ceba54038eaf15ed91032e7 5.15.y
  From: Jiri Olsa 
  Date: Sun, 4 Sep 2022 15:19:00 +0200
  Subject: kbuild: Unify options for BTF generation for vmlinux and modules
  Link: 
https://github.com/gregkh/linux/commit/0baced0e0938f2895ceba54038eaf15ed91032e7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035123/+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 2037513] Re: HP ProBook 450 G8 Notebook fail to wifi test

This bug is awaiting verification that the linux-
gcp-5.15/5.15.0-1048.56~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
gcp-5.15' to 'verification-done-focal-linux-gcp-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-gcp-5.15'
to 'verification-failed-focal-linux-gcp-5.15'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-focal-linux-gcp-5.15-v2 
verification-needed-focal-linux-gcp-5.15

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

Title:
  HP ProBook 450 G8 Notebook fail to wifi test

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-signed-hwe-5.15 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-signed-hwe-5.15 source package in Jammy:
  Invalid

Bug description:
  I'm reviewing the SRU test result on this machine.
  I found that this machine always fails to wifi test and also pop out a lot of 
error message in dmesg.

  It's not a regression, since according to previous test run it has failed 
already.
  Just because we missed reviewing it for a while.

  The journal log is attach, please check further hardware informations
  at https://certification.canonical.com/hardware/202106-29176/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-86-generic 5.15.0-86.96~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-86.96~20.04.1-generic 5.15.122
  Uname: Linux 5.15.0-86-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Sep 27 15:47:37 2023
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-focal-amd64-20220621-7+pc-stella-cmit-focal-amd64+X00
  InstallationDate: Installed on 2023-09-25 (2 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20220621-04:14
  SourcePackage: linux-signed-hwe-5.15
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2037513/+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 2037513] Re: HP ProBook 450 G8 Notebook fail to wifi test

This bug is awaiting verification that the linux-gkeop/5.15.0-1034.40
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-gkeop' to 'verification-done-jammy-
linux-gkeop'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-gkeop' to 'verification-failed-jammy-linux-gkeop'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-gkeop-v2 
verification-needed-jammy-linux-gkeop

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

Title:
  HP ProBook 450 G8 Notebook fail to wifi test

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-signed-hwe-5.15 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-signed-hwe-5.15 source package in Jammy:
  Invalid

Bug description:
  I'm reviewing the SRU test result on this machine.
  I found that this machine always fails to wifi test and also pop out a lot of 
error message in dmesg.

  It's not a regression, since according to previous test run it has failed 
already.
  Just because we missed reviewing it for a while.

  The journal log is attach, please check further hardware informations
  at https://certification.canonical.com/hardware/202106-29176/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-86-generic 5.15.0-86.96~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-86.96~20.04.1-generic 5.15.122
  Uname: Linux 5.15.0-86-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Sep 27 15:47:37 2023
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-focal-amd64-20220621-7+pc-stella-cmit-focal-amd64+X00
  InstallationDate: Installed on 2023-09-25 (2 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20220621-04:14
  SourcePackage: linux-signed-hwe-5.15
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2037513/+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 2037513] Re: HP ProBook 450 G8 Notebook fail to wifi test

This bug is awaiting verification that the linux-
lowlatency/5.15.0-91.101 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-lowlatency' to
'verification-done-jammy-linux-lowlatency'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-lowlatency' to
'verification-failed-jammy-linux-lowlatency'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-lowlatency-v2 
verification-needed-jammy-linux-lowlatency

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

Title:
  HP ProBook 450 G8 Notebook fail to wifi test

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-signed-hwe-5.15 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-signed-hwe-5.15 source package in Jammy:
  Invalid

Bug description:
  I'm reviewing the SRU test result on this machine.
  I found that this machine always fails to wifi test and also pop out a lot of 
error message in dmesg.

  It's not a regression, since according to previous test run it has failed 
already.
  Just because we missed reviewing it for a while.

  The journal log is attach, please check further hardware informations
  at https://certification.canonical.com/hardware/202106-29176/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-86-generic 5.15.0-86.96~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-86.96~20.04.1-generic 5.15.122
  Uname: Linux 5.15.0-86-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Sep 27 15:47:37 2023
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-focal-amd64-20220621-7+pc-stella-cmit-focal-amd64+X00
  InstallationDate: Installed on 2023-09-25 (2 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20220621-04:14
  SourcePackage: linux-signed-hwe-5.15
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2037513/+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 2037513] Re: HP ProBook 450 G8 Notebook fail to wifi test

This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1046.52 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-done-jammy-linux-intel-iotg'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-failed-jammy-linux-intel-iotg'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-intel-iotg-v2 
verification-needed-jammy-linux-intel-iotg

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

Title:
  HP ProBook 450 G8 Notebook fail to wifi test

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-signed-hwe-5.15 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-signed-hwe-5.15 source package in Jammy:
  Invalid

Bug description:
  I'm reviewing the SRU test result on this machine.
  I found that this machine always fails to wifi test and also pop out a lot of 
error message in dmesg.

  It's not a regression, since according to previous test run it has failed 
already.
  Just because we missed reviewing it for a while.

  The journal log is attach, please check further hardware informations
  at https://certification.canonical.com/hardware/202106-29176/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-86-generic 5.15.0-86.96~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-86.96~20.04.1-generic 5.15.122
  Uname: Linux 5.15.0-86-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Sep 27 15:47:37 2023
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-focal-amd64-20220621-7+pc-stella-cmit-focal-amd64+X00
  InstallationDate: Installed on 2023-09-25 (2 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20220621-04:14
  SourcePackage: linux-signed-hwe-5.15
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2037513/+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 2039439] Re: usbip: error: failed to open /usr/share/hwdata//usb.ids

This bug is awaiting verification that the linux-
gcp-5.15/5.15.0-1048.56~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
gcp-5.15' to 'verification-done-focal-linux-gcp-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-gcp-5.15'
to 'verification-failed-focal-linux-gcp-5.15'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-focal-linux-gcp-5.15-v2 
verification-needed-focal-linux-gcp-5.15

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

Title:
  usbip: error: failed to open /usr/share/hwdata//usb.ids

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

Bug description:
  [Impact]

  usbip from linux-tools tries to access /usr/share/hwdata/usb.ids which
  is provided by the hwdata package which is not installed by default.

  $ usbip list -l
  usbip: error: failed to open /usr/share/hwdata//usb.ids
   - busid 1-1.1.1 (0424:7800)
     unknown vendor : unknown product (0424:7800)

  [Test Case]

  $ apt install linux-tools-
  $ usbip list -l
   - busid 1-1.1.1 (0424:7800)
 Microchip Technology, Inc. (formerly SMSC) : unknown product (0424:7800)

  [Fix]

  Make hwdata a dependency of linux-tools-common.

  [Regression Potential]

  A trivial package (hwdata) is installed as a dependency. Can't think
  of any problems this could cause other than a theoretical package
  installation failure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039439/+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 2039439] Re: usbip: error: failed to open /usr/share/hwdata//usb.ids

This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1046.52 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-done-jammy-linux-intel-iotg'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-failed-jammy-linux-intel-iotg'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-intel-iotg-v2 
verification-needed-jammy-linux-intel-iotg

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

Title:
  usbip: error: failed to open /usr/share/hwdata//usb.ids

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

Bug description:
  [Impact]

  usbip from linux-tools tries to access /usr/share/hwdata/usb.ids which
  is provided by the hwdata package which is not installed by default.

  $ usbip list -l
  usbip: error: failed to open /usr/share/hwdata//usb.ids
   - busid 1-1.1.1 (0424:7800)
     unknown vendor : unknown product (0424:7800)

  [Test Case]

  $ apt install linux-tools-
  $ usbip list -l
   - busid 1-1.1.1 (0424:7800)
 Microchip Technology, Inc. (formerly SMSC) : unknown product (0424:7800)

  [Fix]

  Make hwdata a dependency of linux-tools-common.

  [Regression Potential]

  A trivial package (hwdata) is installed as a dependency. Can't think
  of any problems this could cause other than a theoretical package
  installation failure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039439/+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 2039439] Re: usbip: error: failed to open /usr/share/hwdata//usb.ids

This bug is awaiting verification that the linux-
lowlatency/5.15.0-91.101 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-lowlatency' to
'verification-done-jammy-linux-lowlatency'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-lowlatency' to
'verification-failed-jammy-linux-lowlatency'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-lowlatency-v2 
verification-needed-jammy-linux-lowlatency

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

Title:
  usbip: error: failed to open /usr/share/hwdata//usb.ids

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

Bug description:
  [Impact]

  usbip from linux-tools tries to access /usr/share/hwdata/usb.ids which
  is provided by the hwdata package which is not installed by default.

  $ usbip list -l
  usbip: error: failed to open /usr/share/hwdata//usb.ids
   - busid 1-1.1.1 (0424:7800)
     unknown vendor : unknown product (0424:7800)

  [Test Case]

  $ apt install linux-tools-
  $ usbip list -l
   - busid 1-1.1.1 (0424:7800)
 Microchip Technology, Inc. (formerly SMSC) : unknown product (0424:7800)

  [Fix]

  Make hwdata a dependency of linux-tools-common.

  [Regression Potential]

  A trivial package (hwdata) is installed as a dependency. Can't think
  of any problems this could cause other than a theoretical package
  installation failure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039439/+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 2039439] Re: usbip: error: failed to open /usr/share/hwdata//usb.ids

This bug is awaiting verification that the linux-gkeop/5.15.0-1034.40
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-gkeop' to 'verification-done-jammy-
linux-gkeop'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-gkeop' to 'verification-failed-jammy-linux-gkeop'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-gkeop-v2 
verification-needed-jammy-linux-gkeop

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

Title:
  usbip: error: failed to open /usr/share/hwdata//usb.ids

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

Bug description:
  [Impact]

  usbip from linux-tools tries to access /usr/share/hwdata/usb.ids which
  is provided by the hwdata package which is not installed by default.

  $ usbip list -l
  usbip: error: failed to open /usr/share/hwdata//usb.ids
   - busid 1-1.1.1 (0424:7800)
     unknown vendor : unknown product (0424:7800)

  [Test Case]

  $ apt install linux-tools-
  $ usbip list -l
   - busid 1-1.1.1 (0424:7800)
 Microchip Technology, Inc. (formerly SMSC) : unknown product (0424:7800)

  [Fix]

  Make hwdata a dependency of linux-tools-common.

  [Regression Potential]

  A trivial package (hwdata) is installed as a dependency. Can't think
  of any problems this could cause other than a theoretical package
  installation failure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039439/+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 2039575] Re: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes

This bug is awaiting verification that the linux-
gcp-5.15/5.15.0-1048.56~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
gcp-5.15' to 'verification-done-focal-linux-gcp-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-gcp-5.15'
to 'verification-failed-focal-linux-gcp-5.15'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-focal-linux-gcp-5.15-v2 
verification-needed-focal-linux-gcp-5.15

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

Title:
  SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

   * There is a wrong bucket calculation for payload of exactly 4096 bytes
 in SMC stats counters.

   * SMC_STAT_PAYLOAD_SUB and SMC_STAT_RMB_SIZE_SUB have these issues.

   * The impact is that a system silently updates an incorrect stats counter
 in case the underlying kernel is not UBSAN enabled.
 (Difficult to detect.)

   * But if a kernel is UBSAN enabled, one will see a UBSAN
 'array-index-out-of-bounds' warning every time this occurs, like:
 [ 26.335381] UBSAN: array-index-out-of-bounds in 
/build/linux-O6Qi7m/linux-5.15.0/net/smc/af_smc.c:2402:3
 [ 26.335385] index -1 is out of range for type 'u64 [9]'
 [ 26.335388] CPU: 0 PID: 274 Comm: iperf3 Tainted: G E 5.15.0-79-generic 
#86-Ubuntu
 [ 26.335391] Hardware name: IBM 8561 T01 772 (KVM/Linux)
 [ 26.335393] Call Trace:
 [ 26.335397] [] dump_stack_lvl+0x62/0x80
 [ 26.335404] [] ubsan_epilogue+0x1c/0x48
 [ 26.335406] [] __ubsan_handle_out_of_bounds+0x94/0xa0
 [ 26.335411] [<03ff8033f9da>] smc_sendmsg+0x2aa/0x2d0 [smc]
 [ 26.335425] [] sock_sendmsg+0x64/0x80
 [ 26.335431] [] sock_write_iter+0x72/0xa0
 [ 26.335433] [] new_sync_write+0x100/0x190
 [ 26.335438] [] vfs_write+0x1e8/0x280
 [ 26.335440] [] ksys_write+0xb4/0x100
 [ 26.335442] [] __do_syscall+0x1bc/0x1f0
 [ 26.335446] [] system_call+0x78/0xa0

  [Fix]

   * a950a5921db4 a950a5921db450c74212327f69950ff03419483a "net/smc: Fix
  pos miscalculation in statistics"

  [Test Plan]

   * Since this got identified while the livepatch for jammy patches got added,
 one could run a simiar (or the same) test like mentioned at LP#1639924
 (but only jammy comes with official livepatch support).

   * Alternatively a dedicated SMC stats counters test with a payload of
 exactly 4096 bytes could be done (which is probably easier):

   * Install uperf (https://uperf.org/ - https://github.com/uperf/uperf).
 (Wondering if it makes sense to pick this up as Debian/Ubuntu package ?!)

   * Reset SMC-D stats on client and server side.

   * Start uperf at the server side using: # uperf -vs

   * Update profile with remote IP (server IP)
 and start uperf at client: # uperf -vai 5 -m rr1c-4kx4k---1.xml
 with uperf profile:
 # cat rr1c-4kx4k---1.xml
 
 
  
  
  
  
   

   
   


   
   

   
  
 
   
   * The smcd stats output is:
 # smcd -d stats reset
 SMC-D Connections Summary
   Total connections handled 2
   SMC connections 2 (client 2, server 0)
 v1 0
 v2 2
   Handshake errors 0 (client 0, server 0)
   Avg requests per SMC conn 14.0
   TCP fallback 0 (client 0, server 0)
 RX Stats
   Data transmitted (Bytes) 5796 (5.796K)
   Total requests 9
   Buffer full 0 (0.00%)
   Buffer downgrades 0
   Buffer reuses 0
 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB
   Bufs 0 0 0 2 0 0 0 1
   Reqs 8 0 0 0 0 0 0 0
 TX Stats
   Data transmitted (Bytes) 9960 (9.960K)
   Total requests 19
   Buffer full 0 (0.00%)
   Buffer full (remote) 0 (0.00%)
   Buffer too small 0 (0.00%)
   Buffer too small (remote) 0 (0.00%)
   Buffer downgrades 0
   Buffer reuses 0
 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB
   Bufs 0 2 0 0 0 0 0 0
   Reqs 18 0 0 0 0 0 0 1
 Extras
   Special so

[Kernel-packages] [Bug 2039575] Re: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes

This bug is awaiting verification that the linux-
lowlatency/5.15.0-91.101 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-lowlatency' to
'verification-done-jammy-linux-lowlatency'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-lowlatency' to
'verification-failed-jammy-linux-lowlatency'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-lowlatency-v2 
verification-needed-jammy-linux-lowlatency

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

Title:
  SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

   * There is a wrong bucket calculation for payload of exactly 4096 bytes
 in SMC stats counters.

   * SMC_STAT_PAYLOAD_SUB and SMC_STAT_RMB_SIZE_SUB have these issues.

   * The impact is that a system silently updates an incorrect stats counter
 in case the underlying kernel is not UBSAN enabled.
 (Difficult to detect.)

   * But if a kernel is UBSAN enabled, one will see a UBSAN
 'array-index-out-of-bounds' warning every time this occurs, like:
 [ 26.335381] UBSAN: array-index-out-of-bounds in 
/build/linux-O6Qi7m/linux-5.15.0/net/smc/af_smc.c:2402:3
 [ 26.335385] index -1 is out of range for type 'u64 [9]'
 [ 26.335388] CPU: 0 PID: 274 Comm: iperf3 Tainted: G E 5.15.0-79-generic 
#86-Ubuntu
 [ 26.335391] Hardware name: IBM 8561 T01 772 (KVM/Linux)
 [ 26.335393] Call Trace:
 [ 26.335397] [] dump_stack_lvl+0x62/0x80
 [ 26.335404] [] ubsan_epilogue+0x1c/0x48
 [ 26.335406] [] __ubsan_handle_out_of_bounds+0x94/0xa0
 [ 26.335411] [<03ff8033f9da>] smc_sendmsg+0x2aa/0x2d0 [smc]
 [ 26.335425] [] sock_sendmsg+0x64/0x80
 [ 26.335431] [] sock_write_iter+0x72/0xa0
 [ 26.335433] [] new_sync_write+0x100/0x190
 [ 26.335438] [] vfs_write+0x1e8/0x280
 [ 26.335440] [] ksys_write+0xb4/0x100
 [ 26.335442] [] __do_syscall+0x1bc/0x1f0
 [ 26.335446] [] system_call+0x78/0xa0

  [Fix]

   * a950a5921db4 a950a5921db450c74212327f69950ff03419483a "net/smc: Fix
  pos miscalculation in statistics"

  [Test Plan]

   * Since this got identified while the livepatch for jammy patches got added,
 one could run a simiar (or the same) test like mentioned at LP#1639924
 (but only jammy comes with official livepatch support).

   * Alternatively a dedicated SMC stats counters test with a payload of
 exactly 4096 bytes could be done (which is probably easier):

   * Install uperf (https://uperf.org/ - https://github.com/uperf/uperf).
 (Wondering if it makes sense to pick this up as Debian/Ubuntu package ?!)

   * Reset SMC-D stats on client and server side.

   * Start uperf at the server side using: # uperf -vs

   * Update profile with remote IP (server IP)
 and start uperf at client: # uperf -vai 5 -m rr1c-4kx4k---1.xml
 with uperf profile:
 # cat rr1c-4kx4k---1.xml
 
 
  
  
  
  
   

   
   


   
   

   
  
 
   
   * The smcd stats output is:
 # smcd -d stats reset
 SMC-D Connections Summary
   Total connections handled 2
   SMC connections 2 (client 2, server 0)
 v1 0
 v2 2
   Handshake errors 0 (client 0, server 0)
   Avg requests per SMC conn 14.0
   TCP fallback 0 (client 0, server 0)
 RX Stats
   Data transmitted (Bytes) 5796 (5.796K)
   Total requests 9
   Buffer full 0 (0.00%)
   Buffer downgrades 0
   Buffer reuses 0
 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB
   Bufs 0 0 0 2 0 0 0 1
   Reqs 8 0 0 0 0 0 0 0
 TX Stats
   Data transmitted (Bytes) 9960 (9.960K)
   Total requests 19
   Buffer full 0 (0.00%)
   Buffer full (remote) 0 (0.00%)
   Buffer too small 0 (0.00%)
   Buffer too small (remote) 0 (0.00%)
   Buffer downgrades 0
   Buffer reuses 0
 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB
   Bufs 0 2 0 0 0 0 0 0
   Reqs 18 0 0 0 0 0 0 1
 Extras
   Specia

[Kernel-packages] [Bug 2039575] Re: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes

This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1046.52 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-done-jammy-linux-intel-iotg'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-failed-jammy-linux-intel-iotg'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-intel-iotg-v2 
verification-needed-jammy-linux-intel-iotg

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

Title:
  SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

   * There is a wrong bucket calculation for payload of exactly 4096 bytes
 in SMC stats counters.

   * SMC_STAT_PAYLOAD_SUB and SMC_STAT_RMB_SIZE_SUB have these issues.

   * The impact is that a system silently updates an incorrect stats counter
 in case the underlying kernel is not UBSAN enabled.
 (Difficult to detect.)

   * But if a kernel is UBSAN enabled, one will see a UBSAN
 'array-index-out-of-bounds' warning every time this occurs, like:
 [ 26.335381] UBSAN: array-index-out-of-bounds in 
/build/linux-O6Qi7m/linux-5.15.0/net/smc/af_smc.c:2402:3
 [ 26.335385] index -1 is out of range for type 'u64 [9]'
 [ 26.335388] CPU: 0 PID: 274 Comm: iperf3 Tainted: G E 5.15.0-79-generic 
#86-Ubuntu
 [ 26.335391] Hardware name: IBM 8561 T01 772 (KVM/Linux)
 [ 26.335393] Call Trace:
 [ 26.335397] [] dump_stack_lvl+0x62/0x80
 [ 26.335404] [] ubsan_epilogue+0x1c/0x48
 [ 26.335406] [] __ubsan_handle_out_of_bounds+0x94/0xa0
 [ 26.335411] [<03ff8033f9da>] smc_sendmsg+0x2aa/0x2d0 [smc]
 [ 26.335425] [] sock_sendmsg+0x64/0x80
 [ 26.335431] [] sock_write_iter+0x72/0xa0
 [ 26.335433] [] new_sync_write+0x100/0x190
 [ 26.335438] [] vfs_write+0x1e8/0x280
 [ 26.335440] [] ksys_write+0xb4/0x100
 [ 26.335442] [] __do_syscall+0x1bc/0x1f0
 [ 26.335446] [] system_call+0x78/0xa0

  [Fix]

   * a950a5921db4 a950a5921db450c74212327f69950ff03419483a "net/smc: Fix
  pos miscalculation in statistics"

  [Test Plan]

   * Since this got identified while the livepatch for jammy patches got added,
 one could run a simiar (or the same) test like mentioned at LP#1639924
 (but only jammy comes with official livepatch support).

   * Alternatively a dedicated SMC stats counters test with a payload of
 exactly 4096 bytes could be done (which is probably easier):

   * Install uperf (https://uperf.org/ - https://github.com/uperf/uperf).
 (Wondering if it makes sense to pick this up as Debian/Ubuntu package ?!)

   * Reset SMC-D stats on client and server side.

   * Start uperf at the server side using: # uperf -vs

   * Update profile with remote IP (server IP)
 and start uperf at client: # uperf -vai 5 -m rr1c-4kx4k---1.xml
 with uperf profile:
 # cat rr1c-4kx4k---1.xml
 
 
  
  
  
  
   

   
   


   
   

   
  
 
   
   * The smcd stats output is:
 # smcd -d stats reset
 SMC-D Connections Summary
   Total connections handled 2
   SMC connections 2 (client 2, server 0)
 v1 0
 v2 2
   Handshake errors 0 (client 0, server 0)
   Avg requests per SMC conn 14.0
   TCP fallback 0 (client 0, server 0)
 RX Stats
   Data transmitted (Bytes) 5796 (5.796K)
   Total requests 9
   Buffer full 0 (0.00%)
   Buffer downgrades 0
   Buffer reuses 0
 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB
   Bufs 0 0 0 2 0 0 0 1
   Reqs 8 0 0 0 0 0 0 0
 TX Stats
   Data transmitted (Bytes) 9960 (9.960K)
   Total requests 19
   Buffer full 0 (0.00%)
   Buffer full (remote) 0 (0.00%)
   Buffer too small 0 (0.00%)
   Buffer too small (remote) 0 (0.00%)
   Buffer downgrades 0
   Buffer reuses 0
 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB
   Bufs 0 2 0 0 0 0 0 0
   Reqs 18 0 0 0 0 0 0 1
 Extras
   Speci

[Kernel-packages] [Bug 2039575] Re: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes

This bug is awaiting verification that the linux-gkeop/5.15.0-1034.40
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-gkeop' to 'verification-done-jammy-
linux-gkeop'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-gkeop' to 'verification-failed-jammy-linux-gkeop'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-gkeop-v2 
verification-needed-jammy-linux-gkeop

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

Title:
  SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

   * There is a wrong bucket calculation for payload of exactly 4096 bytes
 in SMC stats counters.

   * SMC_STAT_PAYLOAD_SUB and SMC_STAT_RMB_SIZE_SUB have these issues.

   * The impact is that a system silently updates an incorrect stats counter
 in case the underlying kernel is not UBSAN enabled.
 (Difficult to detect.)

   * But if a kernel is UBSAN enabled, one will see a UBSAN
 'array-index-out-of-bounds' warning every time this occurs, like:
 [ 26.335381] UBSAN: array-index-out-of-bounds in 
/build/linux-O6Qi7m/linux-5.15.0/net/smc/af_smc.c:2402:3
 [ 26.335385] index -1 is out of range for type 'u64 [9]'
 [ 26.335388] CPU: 0 PID: 274 Comm: iperf3 Tainted: G E 5.15.0-79-generic 
#86-Ubuntu
 [ 26.335391] Hardware name: IBM 8561 T01 772 (KVM/Linux)
 [ 26.335393] Call Trace:
 [ 26.335397] [] dump_stack_lvl+0x62/0x80
 [ 26.335404] [] ubsan_epilogue+0x1c/0x48
 [ 26.335406] [] __ubsan_handle_out_of_bounds+0x94/0xa0
 [ 26.335411] [<03ff8033f9da>] smc_sendmsg+0x2aa/0x2d0 [smc]
 [ 26.335425] [] sock_sendmsg+0x64/0x80
 [ 26.335431] [] sock_write_iter+0x72/0xa0
 [ 26.335433] [] new_sync_write+0x100/0x190
 [ 26.335438] [] vfs_write+0x1e8/0x280
 [ 26.335440] [] ksys_write+0xb4/0x100
 [ 26.335442] [] __do_syscall+0x1bc/0x1f0
 [ 26.335446] [] system_call+0x78/0xa0

  [Fix]

   * a950a5921db4 a950a5921db450c74212327f69950ff03419483a "net/smc: Fix
  pos miscalculation in statistics"

  [Test Plan]

   * Since this got identified while the livepatch for jammy patches got added,
 one could run a simiar (or the same) test like mentioned at LP#1639924
 (but only jammy comes with official livepatch support).

   * Alternatively a dedicated SMC stats counters test with a payload of
 exactly 4096 bytes could be done (which is probably easier):

   * Install uperf (https://uperf.org/ - https://github.com/uperf/uperf).
 (Wondering if it makes sense to pick this up as Debian/Ubuntu package ?!)

   * Reset SMC-D stats on client and server side.

   * Start uperf at the server side using: # uperf -vs

   * Update profile with remote IP (server IP)
 and start uperf at client: # uperf -vai 5 -m rr1c-4kx4k---1.xml
 with uperf profile:
 # cat rr1c-4kx4k---1.xml
 
 
  
  
  
  
   

   
   


   
   

   
  
 
   
   * The smcd stats output is:
 # smcd -d stats reset
 SMC-D Connections Summary
   Total connections handled 2
   SMC connections 2 (client 2, server 0)
 v1 0
 v2 2
   Handshake errors 0 (client 0, server 0)
   Avg requests per SMC conn 14.0
   TCP fallback 0 (client 0, server 0)
 RX Stats
   Data transmitted (Bytes) 5796 (5.796K)
   Total requests 9
   Buffer full 0 (0.00%)
   Buffer downgrades 0
   Buffer reuses 0
 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB
   Bufs 0 0 0 2 0 0 0 1
   Reqs 8 0 0 0 0 0 0 0
 TX Stats
   Data transmitted (Bytes) 9960 (9.960K)
   Total requests 19
   Buffer full 0 (0.00%)
   Buffer full (remote) 0 (0.00%)
   Buffer too small 0 (0.00%)
   Buffer too small (remote) 0 (0.00%)
   Buffer downgrades 0
   Buffer reuses 0
 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB
   Bufs 0 2 0 0 0 0 0 0
   Reqs 18 0 0 0 0 0 0 1
 Extras
   Special socket calls 0
 cork 0

[Kernel-packages] [Bug 2040157] Re: Unable to use nvme drive to install Ubuntu 23.10

This bug is awaiting verification that the linux-
gcp-5.15/5.15.0-1048.56~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
gcp-5.15' to 'verification-done-focal-linux-gcp-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-gcp-5.15'
to 'verification-failed-focal-linux-gcp-5.15'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-focal-linux-gcp-5.15-v2 
verification-needed-focal-linux-gcp-5.15

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

Title:
  Unable to use nvme drive to install Ubuntu 23.10

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

Bug description:
  The 6.5 kernel in the 23.10 installer ISO is unable to work with an
  NVME drive in the laptop, and it is not possible to install Ubuntu. It
  might be related to Kernel bug
  https://bugzilla.kernel.org/show_bug.cgi?id=217802 fixed in 6.5.6.

  dmesg:
  [   42.116742] nvme nvme0: controller is down; will reset: CSTS=0x, 
PCI_STATUS=0x
  [   42.116764] nvme nvme0: Does your device have a faulty power saving mode 
enabled?
  [   42.116769] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 
pcie_aspm=off" and report a bug
  [   42.149334] nvme0n1: I/O Cmd(0x2) @ LBA 370339840, 8 blocks, I/O Error 
(sct 0x3 / sc 0x71) 
  [   42.149357] I/O error, dev nvme0n1, sector 370339840 op 0x0:(READ) flags 
0x80700 phys_seg 1 prio class 2
  [   42.164760] nvme :04:00.0: Unable to change power state from D3cold to 
D0, device inaccessible
  [   42.165160] nvme nvme0: Disabling device after reset failure: -19
  [   42.180818] Buffer I/O error on dev nvme0n1p7, logical block 0, async page 
read

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

  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
  CRDA: N/A
  CasperMD5CheckResult: pass
  CasperVersion: 1.486
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 10:53:50 2023
  LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.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-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2023
  dmi.bios.release: 1.33
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.33.0
  dmi.board.name: 0R6JFH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.33.0:bd07/04/2023:br1.33:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:sku07BF:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.product.sku: 07BF
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040157/+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 2040157] Re: Unable to use nvme drive to install Ubuntu 23.10

This bug is awaiting verification that the linux-
lowlatency/5.15.0-91.101 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-lowlatency' to
'verification-done-jammy-linux-lowlatency'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-lowlatency' to
'verification-failed-jammy-linux-lowlatency'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-lowlatency-v2 
verification-needed-jammy-linux-lowlatency

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

Title:
  Unable to use nvme drive to install Ubuntu 23.10

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

Bug description:
  The 6.5 kernel in the 23.10 installer ISO is unable to work with an
  NVME drive in the laptop, and it is not possible to install Ubuntu. It
  might be related to Kernel bug
  https://bugzilla.kernel.org/show_bug.cgi?id=217802 fixed in 6.5.6.

  dmesg:
  [   42.116742] nvme nvme0: controller is down; will reset: CSTS=0x, 
PCI_STATUS=0x
  [   42.116764] nvme nvme0: Does your device have a faulty power saving mode 
enabled?
  [   42.116769] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 
pcie_aspm=off" and report a bug
  [   42.149334] nvme0n1: I/O Cmd(0x2) @ LBA 370339840, 8 blocks, I/O Error 
(sct 0x3 / sc 0x71) 
  [   42.149357] I/O error, dev nvme0n1, sector 370339840 op 0x0:(READ) flags 
0x80700 phys_seg 1 prio class 2
  [   42.164760] nvme :04:00.0: Unable to change power state from D3cold to 
D0, device inaccessible
  [   42.165160] nvme nvme0: Disabling device after reset failure: -19
  [   42.180818] Buffer I/O error on dev nvme0n1p7, logical block 0, async page 
read

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

  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
  CRDA: N/A
  CasperMD5CheckResult: pass
  CasperVersion: 1.486
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 10:53:50 2023
  LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.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-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2023
  dmi.bios.release: 1.33
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.33.0
  dmi.board.name: 0R6JFH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.33.0:bd07/04/2023:br1.33:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:sku07BF:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.product.sku: 07BF
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040157/+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 2040157] Re: Unable to use nvme drive to install Ubuntu 23.10

This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1046.52 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-done-jammy-linux-intel-iotg'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-failed-jammy-linux-intel-iotg'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-intel-iotg-v2 
verification-needed-jammy-linux-intel-iotg

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

Title:
  Unable to use nvme drive to install Ubuntu 23.10

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

Bug description:
  The 6.5 kernel in the 23.10 installer ISO is unable to work with an
  NVME drive in the laptop, and it is not possible to install Ubuntu. It
  might be related to Kernel bug
  https://bugzilla.kernel.org/show_bug.cgi?id=217802 fixed in 6.5.6.

  dmesg:
  [   42.116742] nvme nvme0: controller is down; will reset: CSTS=0x, 
PCI_STATUS=0x
  [   42.116764] nvme nvme0: Does your device have a faulty power saving mode 
enabled?
  [   42.116769] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 
pcie_aspm=off" and report a bug
  [   42.149334] nvme0n1: I/O Cmd(0x2) @ LBA 370339840, 8 blocks, I/O Error 
(sct 0x3 / sc 0x71) 
  [   42.149357] I/O error, dev nvme0n1, sector 370339840 op 0x0:(READ) flags 
0x80700 phys_seg 1 prio class 2
  [   42.164760] nvme :04:00.0: Unable to change power state from D3cold to 
D0, device inaccessible
  [   42.165160] nvme nvme0: Disabling device after reset failure: -19
  [   42.180818] Buffer I/O error on dev nvme0n1p7, logical block 0, async page 
read

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

  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
  CRDA: N/A
  CasperMD5CheckResult: pass
  CasperVersion: 1.486
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 10:53:50 2023
  LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.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-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2023
  dmi.bios.release: 1.33
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.33.0
  dmi.board.name: 0R6JFH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.33.0:bd07/04/2023:br1.33:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:sku07BF:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.product.sku: 07BF
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040157/+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 2040157] Re: Unable to use nvme drive to install Ubuntu 23.10

This bug is awaiting verification that the linux-gkeop/5.15.0-1034.40
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-gkeop' to 'verification-done-jammy-
linux-gkeop'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-gkeop' to 'verification-failed-jammy-linux-gkeop'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-gkeop-v2 
verification-needed-jammy-linux-gkeop

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

Title:
  Unable to use nvme drive to install Ubuntu 23.10

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

Bug description:
  The 6.5 kernel in the 23.10 installer ISO is unable to work with an
  NVME drive in the laptop, and it is not possible to install Ubuntu. It
  might be related to Kernel bug
  https://bugzilla.kernel.org/show_bug.cgi?id=217802 fixed in 6.5.6.

  dmesg:
  [   42.116742] nvme nvme0: controller is down; will reset: CSTS=0x, 
PCI_STATUS=0x
  [   42.116764] nvme nvme0: Does your device have a faulty power saving mode 
enabled?
  [   42.116769] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 
pcie_aspm=off" and report a bug
  [   42.149334] nvme0n1: I/O Cmd(0x2) @ LBA 370339840, 8 blocks, I/O Error 
(sct 0x3 / sc 0x71) 
  [   42.149357] I/O error, dev nvme0n1, sector 370339840 op 0x0:(READ) flags 
0x80700 phys_seg 1 prio class 2
  [   42.164760] nvme :04:00.0: Unable to change power state from D3cold to 
D0, device inaccessible
  [   42.165160] nvme nvme0: Disabling device after reset failure: -19
  [   42.180818] Buffer I/O error on dev nvme0n1p7, logical block 0, async page 
read

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

  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
  CRDA: N/A
  CasperMD5CheckResult: pass
  CasperVersion: 1.486
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 10:53:50 2023
  LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.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-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2023
  dmi.bios.release: 1.33
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.33.0
  dmi.board.name: 0R6JFH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.33.0:bd07/04/2023:br1.33:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:sku07BF:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.product.sku: 07BF
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040157/+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 2033406] Re: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module

This bug was fixed in the package linux - 5.15.0-91.101

---
linux (5.15.0-91.101) jammy; urgency=medium

  * jammy/linux: 5.15.0-91.101 -proposed tracker (LP: #2043452)

  * USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix oversight in SuperSpeed initialization

linux (5.15.0-90.100) jammy; urgency=medium

  * jammy/linux: 5.15.0-90.100 -proposed tracker (LP: #2041603)

  * CVE-2023-25775
- RDMA/irdma: Remove irdma_uk_mw_bind()
- RDMA/irdma: Remove irdma_sc_send_lsmm_nostag()
- RDMA/irdma: Remove irdma_cqp_up_map_cmd()
- RDMA/irdma: Remove irdma_get_hw_addr()
- RDMA/irdma: Make irdma_uk_cq_init() return a void
- RDMA/irdma: optimize rx path by removing unnecessary copy
- RDMA/irdma: Remove enum irdma_status_code
- RDMA/irdma: Remove excess error variables
- RDMA/irdma: Prevent zero-length STAG registration

  * CVE-2023-39189
- netfilter: nfnetlink_osf: avoid OOB read

  * SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes
(LP: #2039575)
- net/smc: Fix pos miscalculation in statistics

  * CVE-2023-45871
- igb: set max size RX buffer when store bad packet is enabled

  * CVE-2023-39193
- netfilter: xt_sctp: validate the flag_info count

  * CVE-2023-39192
- netfilter: xt_u32: validate user space input

  * CVE-2023-31085
- ubi: Refuse attaching if mtd's erasesize is 0

  * CVE-2023-5717
- perf: Disallow mis-matched inherited group reads

  * CVE-2023-5178
- nvmet-tcp: Fix a possible UAF in queue intialization setup

  * CVE-2023-5158
- vringh: don't use vringh_kiov_advance() in vringh_iov_xfer()

  * [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module
(LP: #2033406)
- [Packaging] Make WWAN driver loadable modules

  * HP ProBook 450 G8 Notebook fail to wifi test (LP: #2037513)
- iwlwifi: mvm: Don't fail if PPAG isn't supported
- wifi: iwlwifi: fw: skip PPAG for JF

  * usbip: error: failed to open /usr/share/hwdata//usb.ids (LP: #2039439)
- [Packaging] Make linux-tools-common depend on hwdata

  * scripts/pahole-flags.sh change return to exit 0 (LP: #2035123)
- SAUCE: scripts/pahole-flags.sh change return to exit 0

  * Unable to use nvme drive to install Ubuntu 23.10 (LP: #2040157)
- misc: rtsx: Fix some platforms can not boot and move the l1ss judgment to
  probe

  * Jammy update: v5.15.131 upstream stable release (LP: #2039610)
- erofs: ensure that the post-EOF tails are all zeroed
- ksmbd: fix wrong DataOffset validation of create context
- ksmbd: replace one-element array with flex-array member in struct
  smb2_ea_info
- ARM: pxa: remove use of symbol_get()
- mmc: au1xmmc: force non-modular build and remove symbol_get usage
- net: enetc: use EXPORT_SYMBOL_GPL for enetc_phc_index
- rtc: ds1685: use EXPORT_SYMBOL_GPL for ds1685_rtc_poweroff
- modules: only allow symbol_get of EXPORT_SYMBOL_GPL modules
- USB: serial: option: add Quectel EM05G variant (0x030e)
- USB: serial: option: add FOXCONN T99W368/T99W373 product
- ALSA: usb-audio: Fix init call orders for UAC1
- usb: dwc3: meson-g12a: do post init to fix broken usb after resumption
- usb: chipidea: imx: improve logic if samsung,picophy-* parameter is 0
- HID: wacom: remove the battery when the EKR is off
- staging: rtl8712: fix race condition
- Bluetooth: btsdio: fix use after free bug in btsdio_remove due to race
  condition
- wifi: mt76: mt7921: do not support one stream on secondary antenna only
- serial: qcom-geni: fix opp vote on shutdown
- serial: sc16is7xx: fix broken port 0 uart init
- serial: sc16is7xx: fix bug when first setting GPIO direction
- firmware: stratix10-svc: Fix an NULL vs IS_ERR() bug in probe
- fsi: master-ast-cf: Add MODULE_FIRMWARE macro
- tcpm: Avoid soft reset when partner does not support get_status
- nilfs2: fix general protection fault in nilfs_lookup_dirty_data_buffers()
- nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse
- pinctrl: amd: Don't show `Invalid config param` errors
- usb: typec: tcpci: move tcpci.h to include/linux/usb/
- usb: typec: tcpci: clear the fault status bit
- Linux 5.15.131

  * Jammy update: v5.15.130 upstream stable release (LP: #2039608)
- ACPI: thermal: Drop nocrt parameter
- module: Expose module_init_layout_section()
- arm64: module-plts: inline linux/moduleloader.h
- arm64: module: Use module_init_layout_section() to spot init sections
- ARM: module: Use module_init_layout_section() to spot init sections
- rcu: Prevent expedited GP from enabling tick on offline CPU
- rcu-tasks: Fix IPI failure handling in trc_wait_for_one_reader
- rcu-tasks: Wait for trc_read_check_handler() IPIs
- rcu-tasks: Add trc_inspect_reader() checks for exiting critical section
- Linux 5.15.130

  * CVE-2023-42754
-

[Kernel-packages] [Bug 2035123] Re: scripts/pahole-flags.sh change return to exit 0

This bug was fixed in the package linux - 5.15.0-91.101

---
linux (5.15.0-91.101) jammy; urgency=medium

  * jammy/linux: 5.15.0-91.101 -proposed tracker (LP: #2043452)

  * USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix oversight in SuperSpeed initialization

linux (5.15.0-90.100) jammy; urgency=medium

  * jammy/linux: 5.15.0-90.100 -proposed tracker (LP: #2041603)

  * CVE-2023-25775
- RDMA/irdma: Remove irdma_uk_mw_bind()
- RDMA/irdma: Remove irdma_sc_send_lsmm_nostag()
- RDMA/irdma: Remove irdma_cqp_up_map_cmd()
- RDMA/irdma: Remove irdma_get_hw_addr()
- RDMA/irdma: Make irdma_uk_cq_init() return a void
- RDMA/irdma: optimize rx path by removing unnecessary copy
- RDMA/irdma: Remove enum irdma_status_code
- RDMA/irdma: Remove excess error variables
- RDMA/irdma: Prevent zero-length STAG registration

  * CVE-2023-39189
- netfilter: nfnetlink_osf: avoid OOB read

  * SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes
(LP: #2039575)
- net/smc: Fix pos miscalculation in statistics

  * CVE-2023-45871
- igb: set max size RX buffer when store bad packet is enabled

  * CVE-2023-39193
- netfilter: xt_sctp: validate the flag_info count

  * CVE-2023-39192
- netfilter: xt_u32: validate user space input

  * CVE-2023-31085
- ubi: Refuse attaching if mtd's erasesize is 0

  * CVE-2023-5717
- perf: Disallow mis-matched inherited group reads

  * CVE-2023-5178
- nvmet-tcp: Fix a possible UAF in queue intialization setup

  * CVE-2023-5158
- vringh: don't use vringh_kiov_advance() in vringh_iov_xfer()

  * [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module
(LP: #2033406)
- [Packaging] Make WWAN driver loadable modules

  * HP ProBook 450 G8 Notebook fail to wifi test (LP: #2037513)
- iwlwifi: mvm: Don't fail if PPAG isn't supported
- wifi: iwlwifi: fw: skip PPAG for JF

  * usbip: error: failed to open /usr/share/hwdata//usb.ids (LP: #2039439)
- [Packaging] Make linux-tools-common depend on hwdata

  * scripts/pahole-flags.sh change return to exit 0 (LP: #2035123)
- SAUCE: scripts/pahole-flags.sh change return to exit 0

  * Unable to use nvme drive to install Ubuntu 23.10 (LP: #2040157)
- misc: rtsx: Fix some platforms can not boot and move the l1ss judgment to
  probe

  * Jammy update: v5.15.131 upstream stable release (LP: #2039610)
- erofs: ensure that the post-EOF tails are all zeroed
- ksmbd: fix wrong DataOffset validation of create context
- ksmbd: replace one-element array with flex-array member in struct
  smb2_ea_info
- ARM: pxa: remove use of symbol_get()
- mmc: au1xmmc: force non-modular build and remove symbol_get usage
- net: enetc: use EXPORT_SYMBOL_GPL for enetc_phc_index
- rtc: ds1685: use EXPORT_SYMBOL_GPL for ds1685_rtc_poweroff
- modules: only allow symbol_get of EXPORT_SYMBOL_GPL modules
- USB: serial: option: add Quectel EM05G variant (0x030e)
- USB: serial: option: add FOXCONN T99W368/T99W373 product
- ALSA: usb-audio: Fix init call orders for UAC1
- usb: dwc3: meson-g12a: do post init to fix broken usb after resumption
- usb: chipidea: imx: improve logic if samsung,picophy-* parameter is 0
- HID: wacom: remove the battery when the EKR is off
- staging: rtl8712: fix race condition
- Bluetooth: btsdio: fix use after free bug in btsdio_remove due to race
  condition
- wifi: mt76: mt7921: do not support one stream on secondary antenna only
- serial: qcom-geni: fix opp vote on shutdown
- serial: sc16is7xx: fix broken port 0 uart init
- serial: sc16is7xx: fix bug when first setting GPIO direction
- firmware: stratix10-svc: Fix an NULL vs IS_ERR() bug in probe
- fsi: master-ast-cf: Add MODULE_FIRMWARE macro
- tcpm: Avoid soft reset when partner does not support get_status
- nilfs2: fix general protection fault in nilfs_lookup_dirty_data_buffers()
- nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse
- pinctrl: amd: Don't show `Invalid config param` errors
- usb: typec: tcpci: move tcpci.h to include/linux/usb/
- usb: typec: tcpci: clear the fault status bit
- Linux 5.15.131

  * Jammy update: v5.15.130 upstream stable release (LP: #2039608)
- ACPI: thermal: Drop nocrt parameter
- module: Expose module_init_layout_section()
- arm64: module-plts: inline linux/moduleloader.h
- arm64: module: Use module_init_layout_section() to spot init sections
- ARM: module: Use module_init_layout_section() to spot init sections
- rcu: Prevent expedited GP from enabling tick on offline CPU
- rcu-tasks: Fix IPI failure handling in trc_wait_for_one_reader
- rcu-tasks: Wait for trc_read_check_handler() IPIs
- rcu-tasks: Add trc_inspect_reader() checks for exiting critical section
- Linux 5.15.130

  * CVE-2023-42754
-

[Kernel-packages] [Bug 2037513] Re: HP ProBook 450 G8 Notebook fail to wifi test

This bug was fixed in the package linux - 5.15.0-91.101

---
linux (5.15.0-91.101) jammy; urgency=medium

  * jammy/linux: 5.15.0-91.101 -proposed tracker (LP: #2043452)

  * USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix oversight in SuperSpeed initialization

linux (5.15.0-90.100) jammy; urgency=medium

  * jammy/linux: 5.15.0-90.100 -proposed tracker (LP: #2041603)

  * CVE-2023-25775
- RDMA/irdma: Remove irdma_uk_mw_bind()
- RDMA/irdma: Remove irdma_sc_send_lsmm_nostag()
- RDMA/irdma: Remove irdma_cqp_up_map_cmd()
- RDMA/irdma: Remove irdma_get_hw_addr()
- RDMA/irdma: Make irdma_uk_cq_init() return a void
- RDMA/irdma: optimize rx path by removing unnecessary copy
- RDMA/irdma: Remove enum irdma_status_code
- RDMA/irdma: Remove excess error variables
- RDMA/irdma: Prevent zero-length STAG registration

  * CVE-2023-39189
- netfilter: nfnetlink_osf: avoid OOB read

  * SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes
(LP: #2039575)
- net/smc: Fix pos miscalculation in statistics

  * CVE-2023-45871
- igb: set max size RX buffer when store bad packet is enabled

  * CVE-2023-39193
- netfilter: xt_sctp: validate the flag_info count

  * CVE-2023-39192
- netfilter: xt_u32: validate user space input

  * CVE-2023-31085
- ubi: Refuse attaching if mtd's erasesize is 0

  * CVE-2023-5717
- perf: Disallow mis-matched inherited group reads

  * CVE-2023-5178
- nvmet-tcp: Fix a possible UAF in queue intialization setup

  * CVE-2023-5158
- vringh: don't use vringh_kiov_advance() in vringh_iov_xfer()

  * [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module
(LP: #2033406)
- [Packaging] Make WWAN driver loadable modules

  * HP ProBook 450 G8 Notebook fail to wifi test (LP: #2037513)
- iwlwifi: mvm: Don't fail if PPAG isn't supported
- wifi: iwlwifi: fw: skip PPAG for JF

  * usbip: error: failed to open /usr/share/hwdata//usb.ids (LP: #2039439)
- [Packaging] Make linux-tools-common depend on hwdata

  * scripts/pahole-flags.sh change return to exit 0 (LP: #2035123)
- SAUCE: scripts/pahole-flags.sh change return to exit 0

  * Unable to use nvme drive to install Ubuntu 23.10 (LP: #2040157)
- misc: rtsx: Fix some platforms can not boot and move the l1ss judgment to
  probe

  * Jammy update: v5.15.131 upstream stable release (LP: #2039610)
- erofs: ensure that the post-EOF tails are all zeroed
- ksmbd: fix wrong DataOffset validation of create context
- ksmbd: replace one-element array with flex-array member in struct
  smb2_ea_info
- ARM: pxa: remove use of symbol_get()
- mmc: au1xmmc: force non-modular build and remove symbol_get usage
- net: enetc: use EXPORT_SYMBOL_GPL for enetc_phc_index
- rtc: ds1685: use EXPORT_SYMBOL_GPL for ds1685_rtc_poweroff
- modules: only allow symbol_get of EXPORT_SYMBOL_GPL modules
- USB: serial: option: add Quectel EM05G variant (0x030e)
- USB: serial: option: add FOXCONN T99W368/T99W373 product
- ALSA: usb-audio: Fix init call orders for UAC1
- usb: dwc3: meson-g12a: do post init to fix broken usb after resumption
- usb: chipidea: imx: improve logic if samsung,picophy-* parameter is 0
- HID: wacom: remove the battery when the EKR is off
- staging: rtl8712: fix race condition
- Bluetooth: btsdio: fix use after free bug in btsdio_remove due to race
  condition
- wifi: mt76: mt7921: do not support one stream on secondary antenna only
- serial: qcom-geni: fix opp vote on shutdown
- serial: sc16is7xx: fix broken port 0 uart init
- serial: sc16is7xx: fix bug when first setting GPIO direction
- firmware: stratix10-svc: Fix an NULL vs IS_ERR() bug in probe
- fsi: master-ast-cf: Add MODULE_FIRMWARE macro
- tcpm: Avoid soft reset when partner does not support get_status
- nilfs2: fix general protection fault in nilfs_lookup_dirty_data_buffers()
- nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse
- pinctrl: amd: Don't show `Invalid config param` errors
- usb: typec: tcpci: move tcpci.h to include/linux/usb/
- usb: typec: tcpci: clear the fault status bit
- Linux 5.15.131

  * Jammy update: v5.15.130 upstream stable release (LP: #2039608)
- ACPI: thermal: Drop nocrt parameter
- module: Expose module_init_layout_section()
- arm64: module-plts: inline linux/moduleloader.h
- arm64: module: Use module_init_layout_section() to spot init sections
- ARM: module: Use module_init_layout_section() to spot init sections
- rcu: Prevent expedited GP from enabling tick on offline CPU
- rcu-tasks: Fix IPI failure handling in trc_wait_for_one_reader
- rcu-tasks: Wait for trc_read_check_handler() IPIs
- rcu-tasks: Add trc_inspect_reader() checks for exiting critical section
- Linux 5.15.130

  * CVE-2023-42754
-

[Kernel-packages] [Bug 2038382] Re: Jammy update: v5.15.127 upstream stable release

This bug was fixed in the package linux - 5.15.0-91.101

---
linux (5.15.0-91.101) jammy; urgency=medium

  * jammy/linux: 5.15.0-91.101 -proposed tracker (LP: #2043452)

  * USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix oversight in SuperSpeed initialization

linux (5.15.0-90.100) jammy; urgency=medium

  * jammy/linux: 5.15.0-90.100 -proposed tracker (LP: #2041603)

  * CVE-2023-25775
- RDMA/irdma: Remove irdma_uk_mw_bind()
- RDMA/irdma: Remove irdma_sc_send_lsmm_nostag()
- RDMA/irdma: Remove irdma_cqp_up_map_cmd()
- RDMA/irdma: Remove irdma_get_hw_addr()
- RDMA/irdma: Make irdma_uk_cq_init() return a void
- RDMA/irdma: optimize rx path by removing unnecessary copy
- RDMA/irdma: Remove enum irdma_status_code
- RDMA/irdma: Remove excess error variables
- RDMA/irdma: Prevent zero-length STAG registration

  * CVE-2023-39189
- netfilter: nfnetlink_osf: avoid OOB read

  * SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes
(LP: #2039575)
- net/smc: Fix pos miscalculation in statistics

  * CVE-2023-45871
- igb: set max size RX buffer when store bad packet is enabled

  * CVE-2023-39193
- netfilter: xt_sctp: validate the flag_info count

  * CVE-2023-39192
- netfilter: xt_u32: validate user space input

  * CVE-2023-31085
- ubi: Refuse attaching if mtd's erasesize is 0

  * CVE-2023-5717
- perf: Disallow mis-matched inherited group reads

  * CVE-2023-5178
- nvmet-tcp: Fix a possible UAF in queue intialization setup

  * CVE-2023-5158
- vringh: don't use vringh_kiov_advance() in vringh_iov_xfer()

  * [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module
(LP: #2033406)
- [Packaging] Make WWAN driver loadable modules

  * HP ProBook 450 G8 Notebook fail to wifi test (LP: #2037513)
- iwlwifi: mvm: Don't fail if PPAG isn't supported
- wifi: iwlwifi: fw: skip PPAG for JF

  * usbip: error: failed to open /usr/share/hwdata//usb.ids (LP: #2039439)
- [Packaging] Make linux-tools-common depend on hwdata

  * scripts/pahole-flags.sh change return to exit 0 (LP: #2035123)
- SAUCE: scripts/pahole-flags.sh change return to exit 0

  * Unable to use nvme drive to install Ubuntu 23.10 (LP: #2040157)
- misc: rtsx: Fix some platforms can not boot and move the l1ss judgment to
  probe

  * Jammy update: v5.15.131 upstream stable release (LP: #2039610)
- erofs: ensure that the post-EOF tails are all zeroed
- ksmbd: fix wrong DataOffset validation of create context
- ksmbd: replace one-element array with flex-array member in struct
  smb2_ea_info
- ARM: pxa: remove use of symbol_get()
- mmc: au1xmmc: force non-modular build and remove symbol_get usage
- net: enetc: use EXPORT_SYMBOL_GPL for enetc_phc_index
- rtc: ds1685: use EXPORT_SYMBOL_GPL for ds1685_rtc_poweroff
- modules: only allow symbol_get of EXPORT_SYMBOL_GPL modules
- USB: serial: option: add Quectel EM05G variant (0x030e)
- USB: serial: option: add FOXCONN T99W368/T99W373 product
- ALSA: usb-audio: Fix init call orders for UAC1
- usb: dwc3: meson-g12a: do post init to fix broken usb after resumption
- usb: chipidea: imx: improve logic if samsung,picophy-* parameter is 0
- HID: wacom: remove the battery when the EKR is off
- staging: rtl8712: fix race condition
- Bluetooth: btsdio: fix use after free bug in btsdio_remove due to race
  condition
- wifi: mt76: mt7921: do not support one stream on secondary antenna only
- serial: qcom-geni: fix opp vote on shutdown
- serial: sc16is7xx: fix broken port 0 uart init
- serial: sc16is7xx: fix bug when first setting GPIO direction
- firmware: stratix10-svc: Fix an NULL vs IS_ERR() bug in probe
- fsi: master-ast-cf: Add MODULE_FIRMWARE macro
- tcpm: Avoid soft reset when partner does not support get_status
- nilfs2: fix general protection fault in nilfs_lookup_dirty_data_buffers()
- nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse
- pinctrl: amd: Don't show `Invalid config param` errors
- usb: typec: tcpci: move tcpci.h to include/linux/usb/
- usb: typec: tcpci: clear the fault status bit
- Linux 5.15.131

  * Jammy update: v5.15.130 upstream stable release (LP: #2039608)
- ACPI: thermal: Drop nocrt parameter
- module: Expose module_init_layout_section()
- arm64: module-plts: inline linux/moduleloader.h
- arm64: module: Use module_init_layout_section() to spot init sections
- ARM: module: Use module_init_layout_section() to spot init sections
- rcu: Prevent expedited GP from enabling tick on offline CPU
- rcu-tasks: Fix IPI failure handling in trc_wait_for_one_reader
- rcu-tasks: Wait for trc_read_check_handler() IPIs
- rcu-tasks: Add trc_inspect_reader() checks for exiting critical section
- Linux 5.15.130

  * CVE-2023-42754
-

[Kernel-packages] [Bug 2038486] Re: Jammy update: v5.15.128 upstream stable release

This bug was fixed in the package linux - 5.15.0-91.101

---
linux (5.15.0-91.101) jammy; urgency=medium

  * jammy/linux: 5.15.0-91.101 -proposed tracker (LP: #2043452)

  * USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix oversight in SuperSpeed initialization

linux (5.15.0-90.100) jammy; urgency=medium

  * jammy/linux: 5.15.0-90.100 -proposed tracker (LP: #2041603)

  * CVE-2023-25775
- RDMA/irdma: Remove irdma_uk_mw_bind()
- RDMA/irdma: Remove irdma_sc_send_lsmm_nostag()
- RDMA/irdma: Remove irdma_cqp_up_map_cmd()
- RDMA/irdma: Remove irdma_get_hw_addr()
- RDMA/irdma: Make irdma_uk_cq_init() return a void
- RDMA/irdma: optimize rx path by removing unnecessary copy
- RDMA/irdma: Remove enum irdma_status_code
- RDMA/irdma: Remove excess error variables
- RDMA/irdma: Prevent zero-length STAG registration

  * CVE-2023-39189
- netfilter: nfnetlink_osf: avoid OOB read

  * SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes
(LP: #2039575)
- net/smc: Fix pos miscalculation in statistics

  * CVE-2023-45871
- igb: set max size RX buffer when store bad packet is enabled

  * CVE-2023-39193
- netfilter: xt_sctp: validate the flag_info count

  * CVE-2023-39192
- netfilter: xt_u32: validate user space input

  * CVE-2023-31085
- ubi: Refuse attaching if mtd's erasesize is 0

  * CVE-2023-5717
- perf: Disallow mis-matched inherited group reads

  * CVE-2023-5178
- nvmet-tcp: Fix a possible UAF in queue intialization setup

  * CVE-2023-5158
- vringh: don't use vringh_kiov_advance() in vringh_iov_xfer()

  * [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module
(LP: #2033406)
- [Packaging] Make WWAN driver loadable modules

  * HP ProBook 450 G8 Notebook fail to wifi test (LP: #2037513)
- iwlwifi: mvm: Don't fail if PPAG isn't supported
- wifi: iwlwifi: fw: skip PPAG for JF

  * usbip: error: failed to open /usr/share/hwdata//usb.ids (LP: #2039439)
- [Packaging] Make linux-tools-common depend on hwdata

  * scripts/pahole-flags.sh change return to exit 0 (LP: #2035123)
- SAUCE: scripts/pahole-flags.sh change return to exit 0

  * Unable to use nvme drive to install Ubuntu 23.10 (LP: #2040157)
- misc: rtsx: Fix some platforms can not boot and move the l1ss judgment to
  probe

  * Jammy update: v5.15.131 upstream stable release (LP: #2039610)
- erofs: ensure that the post-EOF tails are all zeroed
- ksmbd: fix wrong DataOffset validation of create context
- ksmbd: replace one-element array with flex-array member in struct
  smb2_ea_info
- ARM: pxa: remove use of symbol_get()
- mmc: au1xmmc: force non-modular build and remove symbol_get usage
- net: enetc: use EXPORT_SYMBOL_GPL for enetc_phc_index
- rtc: ds1685: use EXPORT_SYMBOL_GPL for ds1685_rtc_poweroff
- modules: only allow symbol_get of EXPORT_SYMBOL_GPL modules
- USB: serial: option: add Quectel EM05G variant (0x030e)
- USB: serial: option: add FOXCONN T99W368/T99W373 product
- ALSA: usb-audio: Fix init call orders for UAC1
- usb: dwc3: meson-g12a: do post init to fix broken usb after resumption
- usb: chipidea: imx: improve logic if samsung,picophy-* parameter is 0
- HID: wacom: remove the battery when the EKR is off
- staging: rtl8712: fix race condition
- Bluetooth: btsdio: fix use after free bug in btsdio_remove due to race
  condition
- wifi: mt76: mt7921: do not support one stream on secondary antenna only
- serial: qcom-geni: fix opp vote on shutdown
- serial: sc16is7xx: fix broken port 0 uart init
- serial: sc16is7xx: fix bug when first setting GPIO direction
- firmware: stratix10-svc: Fix an NULL vs IS_ERR() bug in probe
- fsi: master-ast-cf: Add MODULE_FIRMWARE macro
- tcpm: Avoid soft reset when partner does not support get_status
- nilfs2: fix general protection fault in nilfs_lookup_dirty_data_buffers()
- nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse
- pinctrl: amd: Don't show `Invalid config param` errors
- usb: typec: tcpci: move tcpci.h to include/linux/usb/
- usb: typec: tcpci: clear the fault status bit
- Linux 5.15.131

  * Jammy update: v5.15.130 upstream stable release (LP: #2039608)
- ACPI: thermal: Drop nocrt parameter
- module: Expose module_init_layout_section()
- arm64: module-plts: inline linux/moduleloader.h
- arm64: module: Use module_init_layout_section() to spot init sections
- ARM: module: Use module_init_layout_section() to spot init sections
- rcu: Prevent expedited GP from enabling tick on offline CPU
- rcu-tasks: Fix IPI failure handling in trc_wait_for_one_reader
- rcu-tasks: Wait for trc_read_check_handler() IPIs
- rcu-tasks: Add trc_inspect_reader() checks for exiting critical section
- Linux 5.15.130

  * CVE-2023-42754
-

[Kernel-packages] [Bug 2038652] Re: Focal update: v5.4.253 upstream stable release

This bug was fixed in the package linux - 5.4.0-169.187

---
linux (5.4.0-169.187) focal; urgency=medium

  * focal/linux: 5.4.0-169.187 -proposed tracker (LP: #2044375)

  * USB bus error after upgrading to proposed kernel on lunar, jammy and focal
(LP: #2043197)
- USB: core: Fix oversight in SuperSpeed initialization

  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
- [Packaging] resync update-dkms-versions helper
- [Packaging] update annotations scripts

linux (5.4.0-168.186) focal; urgency=medium

  * focal/linux: 5.4.0-168.186 -proposed tracker (LP: #2041652)

  * Focal update: v5.4.257 upstream stable release (LP: #2040284)
- erofs: ensure that the post-EOF tails are all zeroed
- ARM: pxa: remove use of symbol_get()
- mmc: au1xmmc: force non-modular build and remove symbol_get usage
- net: enetc: use EXPORT_SYMBOL_GPL for enetc_phc_index
- rtc: ds1685: use EXPORT_SYMBOL_GPL for ds1685_rtc_poweroff
- modules: only allow symbol_get of EXPORT_SYMBOL_GPL modules
- USB: serial: option: add Quectel EM05G variant (0x030e)
- USB: serial: option: add FOXCONN T99W368/T99W373 product
- HID: wacom: remove the battery when the EKR is off
- staging: rtl8712: fix race condition
- Bluetooth: btsdio: fix use after free bug in btsdio_remove due to race
  condition
- serial: sc16is7xx: fix bug when first setting GPIO direction
- firmware: stratix10-svc: Fix an NULL vs IS_ERR() bug in probe
- fsi: master-ast-cf: Add MODULE_FIRMWARE macro
- nilfs2: fix general protection fault in nilfs_lookup_dirty_data_buffers()
- nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse
- pinctrl: amd: Don't show `Invalid config param` errors
- 9p: virtio: make sure 'offs' is initialized in zc_request
- ASoC: da7219: Flush pending AAD IRQ when suspending
- ASoC: da7219: Check for failure reading AAD IRQ events
- ethernet: atheros: fix return value check in atl1c_tso_csum()
- vxlan: generalize vxlan_parse_gpe_hdr and remove unused args
- m68k: Fix invalid .section syntax
- s390/dasd: use correct number of retries for ERP requests
- s390/dasd: fix hanging device after request requeue
- fs/nls: make load_nls() take a const parameter
- ASoc: codecs: ES8316: Fix DMIC config
- ASoC: atmel: Fix the 8K sample parameter in I2SC master
- platform/x86: intel: hid: Always call BTNL ACPI method
- platform/x86: huawei-wmi: Silence ambient light sensor
- security: keys: perform capable check only on privileged operations
- clk: fixed-mmio: make COMMON_CLK_FIXED_MMIO depend on HAS_IOMEM
- net: usb: qmi_wwan: add Quectel EM05GV2
- idmaengine: make FSL_EDMA and INTEL_IDMA64 depends on HAS_IOMEM
- scsi: qedi: Fix potential deadlock on &qedi_percpu->p_work_lock
- netlabel: fix shift wrapping bug in netlbl_catmap_setlong()
- bnx2x: fix page fault following EEH recovery
- sctp: handle invalid error codes without calling BUG()
- cifs: add a warning when the in-flight count goes negative
- scsi: storvsc: Always set no_report_opcodes
- ALSA: seq: oss: Fix racy open/close of MIDI devices
- platform/mellanox: Fix mlxbf-tmfifo not handling all virtio CONSOLE
  notifications
- powerpc/32s: Fix assembler warning about r0
- udf: Check consistency of Space Bitmap Descriptor
- udf: Handle error when adding extent to a file
- Revert "net: macsec: preserve ingress frame ordering"
- reiserfs: Check the return value from __getblk()
- eventfd: Export eventfd_ctx_do_read()
- eventfd: prevent underflow for eventfd semaphores
- new helper: lookup_positive_unlocked()
- fs: Fix error checking for d_hash_and_lookup()
- tmpfs: verify {g,u}id mount options correctly
- OPP: Fix passing 0 to PTR_ERR in _opp_attach_genpd()
- x86/asm: Make more symbols local
- x86/boot: Annotate local functions
- x86/decompressor: Don't rely on upper 32 bits of GPRs being preserved
- perf/imx_ddr: don't enable counter0 if none of 4 counters are used
- cpufreq: powernow-k8: Use related_cpus instead of cpus in driver.exit()
- bpf: Clear the probe_addr for uprobe
- tcp: tcp_enter_quickack_mode() should be static
- regmap: rbtree: Use alloc_flags for memory allocations
- spi: tegra20-sflash: fix to check return value of platform_get_irq() in
  tegra_sflash_probe()
- can: gs_usb: gs_usb_receive_bulk_callback(): count RX overflow errors also
  in case of OOM
- wifi: mwifiex: Fix OOB and integer underflow when rx packets
- mwifiex: switch from 'pci_' to 'dma_' API
- wifi: mwifiex: fix error recovery in PCIE buffer descriptor management
- crypto: stm32 - Properly handle pm_runtime_get failing
- Bluetooth: nokia: fix value check in nokia_bluetooth_serdev_probe()
- crypto: caam - fix unchecked return value error
- hwrng: iproc-rng200 - use semicolons rat

[Kernel-packages] [Bug 2039291] Re: Focal update: v5.4.254 upstream stable release

This bug was fixed in the package linux - 5.4.0-169.187

---
linux (5.4.0-169.187) focal; urgency=medium

  * focal/linux: 5.4.0-169.187 -proposed tracker (LP: #2044375)

  * USB bus error after upgrading to proposed kernel on lunar, jammy and focal
(LP: #2043197)
- USB: core: Fix oversight in SuperSpeed initialization

  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
- [Packaging] resync update-dkms-versions helper
- [Packaging] update annotations scripts

linux (5.4.0-168.186) focal; urgency=medium

  * focal/linux: 5.4.0-168.186 -proposed tracker (LP: #2041652)

  * Focal update: v5.4.257 upstream stable release (LP: #2040284)
- erofs: ensure that the post-EOF tails are all zeroed
- ARM: pxa: remove use of symbol_get()
- mmc: au1xmmc: force non-modular build and remove symbol_get usage
- net: enetc: use EXPORT_SYMBOL_GPL for enetc_phc_index
- rtc: ds1685: use EXPORT_SYMBOL_GPL for ds1685_rtc_poweroff
- modules: only allow symbol_get of EXPORT_SYMBOL_GPL modules
- USB: serial: option: add Quectel EM05G variant (0x030e)
- USB: serial: option: add FOXCONN T99W368/T99W373 product
- HID: wacom: remove the battery when the EKR is off
- staging: rtl8712: fix race condition
- Bluetooth: btsdio: fix use after free bug in btsdio_remove due to race
  condition
- serial: sc16is7xx: fix bug when first setting GPIO direction
- firmware: stratix10-svc: Fix an NULL vs IS_ERR() bug in probe
- fsi: master-ast-cf: Add MODULE_FIRMWARE macro
- nilfs2: fix general protection fault in nilfs_lookup_dirty_data_buffers()
- nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse
- pinctrl: amd: Don't show `Invalid config param` errors
- 9p: virtio: make sure 'offs' is initialized in zc_request
- ASoC: da7219: Flush pending AAD IRQ when suspending
- ASoC: da7219: Check for failure reading AAD IRQ events
- ethernet: atheros: fix return value check in atl1c_tso_csum()
- vxlan: generalize vxlan_parse_gpe_hdr and remove unused args
- m68k: Fix invalid .section syntax
- s390/dasd: use correct number of retries for ERP requests
- s390/dasd: fix hanging device after request requeue
- fs/nls: make load_nls() take a const parameter
- ASoc: codecs: ES8316: Fix DMIC config
- ASoC: atmel: Fix the 8K sample parameter in I2SC master
- platform/x86: intel: hid: Always call BTNL ACPI method
- platform/x86: huawei-wmi: Silence ambient light sensor
- security: keys: perform capable check only on privileged operations
- clk: fixed-mmio: make COMMON_CLK_FIXED_MMIO depend on HAS_IOMEM
- net: usb: qmi_wwan: add Quectel EM05GV2
- idmaengine: make FSL_EDMA and INTEL_IDMA64 depends on HAS_IOMEM
- scsi: qedi: Fix potential deadlock on &qedi_percpu->p_work_lock
- netlabel: fix shift wrapping bug in netlbl_catmap_setlong()
- bnx2x: fix page fault following EEH recovery
- sctp: handle invalid error codes without calling BUG()
- cifs: add a warning when the in-flight count goes negative
- scsi: storvsc: Always set no_report_opcodes
- ALSA: seq: oss: Fix racy open/close of MIDI devices
- platform/mellanox: Fix mlxbf-tmfifo not handling all virtio CONSOLE
  notifications
- powerpc/32s: Fix assembler warning about r0
- udf: Check consistency of Space Bitmap Descriptor
- udf: Handle error when adding extent to a file
- Revert "net: macsec: preserve ingress frame ordering"
- reiserfs: Check the return value from __getblk()
- eventfd: Export eventfd_ctx_do_read()
- eventfd: prevent underflow for eventfd semaphores
- new helper: lookup_positive_unlocked()
- fs: Fix error checking for d_hash_and_lookup()
- tmpfs: verify {g,u}id mount options correctly
- OPP: Fix passing 0 to PTR_ERR in _opp_attach_genpd()
- x86/asm: Make more symbols local
- x86/boot: Annotate local functions
- x86/decompressor: Don't rely on upper 32 bits of GPRs being preserved
- perf/imx_ddr: don't enable counter0 if none of 4 counters are used
- cpufreq: powernow-k8: Use related_cpus instead of cpus in driver.exit()
- bpf: Clear the probe_addr for uprobe
- tcp: tcp_enter_quickack_mode() should be static
- regmap: rbtree: Use alloc_flags for memory allocations
- spi: tegra20-sflash: fix to check return value of platform_get_irq() in
  tegra_sflash_probe()
- can: gs_usb: gs_usb_receive_bulk_callback(): count RX overflow errors also
  in case of OOM
- wifi: mwifiex: Fix OOB and integer underflow when rx packets
- mwifiex: switch from 'pci_' to 'dma_' API
- wifi: mwifiex: fix error recovery in PCIE buffer descriptor management
- crypto: stm32 - Properly handle pm_runtime_get failing
- Bluetooth: nokia: fix value check in nokia_bluetooth_serdev_probe()
- crypto: caam - fix unchecked return value error
- hwrng: iproc-rng200 - use semicolons rat

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

This bug was fixed in the package linux - 5.15.0-91.101

---
linux (5.15.0-91.101) jammy; urgency=medium

  * jammy/linux: 5.15.0-91.101 -proposed tracker (LP: #2043452)

  * USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix oversight in SuperSpeed initialization

linux (5.15.0-90.100) jammy; urgency=medium

  * jammy/linux: 5.15.0-90.100 -proposed tracker (LP: #2041603)

  * CVE-2023-25775
- RDMA/irdma: Remove irdma_uk_mw_bind()
- RDMA/irdma: Remove irdma_sc_send_lsmm_nostag()
- RDMA/irdma: Remove irdma_cqp_up_map_cmd()
- RDMA/irdma: Remove irdma_get_hw_addr()
- RDMA/irdma: Make irdma_uk_cq_init() return a void
- RDMA/irdma: optimize rx path by removing unnecessary copy
- RDMA/irdma: Remove enum irdma_status_code
- RDMA/irdma: Remove excess error variables
- RDMA/irdma: Prevent zero-length STAG registration

  * CVE-2023-39189
- netfilter: nfnetlink_osf: avoid OOB read

  * SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes
(LP: #2039575)
- net/smc: Fix pos miscalculation in statistics

  * CVE-2023-45871
- igb: set max size RX buffer when store bad packet is enabled

  * CVE-2023-39193
- netfilter: xt_sctp: validate the flag_info count

  * CVE-2023-39192
- netfilter: xt_u32: validate user space input

  * CVE-2023-31085
- ubi: Refuse attaching if mtd's erasesize is 0

  * CVE-2023-5717
- perf: Disallow mis-matched inherited group reads

  * CVE-2023-5178
- nvmet-tcp: Fix a possible UAF in queue intialization setup

  * CVE-2023-5158
- vringh: don't use vringh_kiov_advance() in vringh_iov_xfer()

  * [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module
(LP: #2033406)
- [Packaging] Make WWAN driver loadable modules

  * HP ProBook 450 G8 Notebook fail to wifi test (LP: #2037513)
- iwlwifi: mvm: Don't fail if PPAG isn't supported
- wifi: iwlwifi: fw: skip PPAG for JF

  * usbip: error: failed to open /usr/share/hwdata//usb.ids (LP: #2039439)
- [Packaging] Make linux-tools-common depend on hwdata

  * scripts/pahole-flags.sh change return to exit 0 (LP: #2035123)
- SAUCE: scripts/pahole-flags.sh change return to exit 0

  * Unable to use nvme drive to install Ubuntu 23.10 (LP: #2040157)
- misc: rtsx: Fix some platforms can not boot and move the l1ss judgment to
  probe

  * Jammy update: v5.15.131 upstream stable release (LP: #2039610)
- erofs: ensure that the post-EOF tails are all zeroed
- ksmbd: fix wrong DataOffset validation of create context
- ksmbd: replace one-element array with flex-array member in struct
  smb2_ea_info
- ARM: pxa: remove use of symbol_get()
- mmc: au1xmmc: force non-modular build and remove symbol_get usage
- net: enetc: use EXPORT_SYMBOL_GPL for enetc_phc_index
- rtc: ds1685: use EXPORT_SYMBOL_GPL for ds1685_rtc_poweroff
- modules: only allow symbol_get of EXPORT_SYMBOL_GPL modules
- USB: serial: option: add Quectel EM05G variant (0x030e)
- USB: serial: option: add FOXCONN T99W368/T99W373 product
- ALSA: usb-audio: Fix init call orders for UAC1
- usb: dwc3: meson-g12a: do post init to fix broken usb after resumption
- usb: chipidea: imx: improve logic if samsung,picophy-* parameter is 0
- HID: wacom: remove the battery when the EKR is off
- staging: rtl8712: fix race condition
- Bluetooth: btsdio: fix use after free bug in btsdio_remove due to race
  condition
- wifi: mt76: mt7921: do not support one stream on secondary antenna only
- serial: qcom-geni: fix opp vote on shutdown
- serial: sc16is7xx: fix broken port 0 uart init
- serial: sc16is7xx: fix bug when first setting GPIO direction
- firmware: stratix10-svc: Fix an NULL vs IS_ERR() bug in probe
- fsi: master-ast-cf: Add MODULE_FIRMWARE macro
- tcpm: Avoid soft reset when partner does not support get_status
- nilfs2: fix general protection fault in nilfs_lookup_dirty_data_buffers()
- nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse
- pinctrl: amd: Don't show `Invalid config param` errors
- usb: typec: tcpci: move tcpci.h to include/linux/usb/
- usb: typec: tcpci: clear the fault status bit
- Linux 5.15.131

  * Jammy update: v5.15.130 upstream stable release (LP: #2039608)
- ACPI: thermal: Drop nocrt parameter
- module: Expose module_init_layout_section()
- arm64: module-plts: inline linux/moduleloader.h
- arm64: module: Use module_init_layout_section() to spot init sections
- ARM: module: Use module_init_layout_section() to spot init sections
- rcu: Prevent expedited GP from enabling tick on offline CPU
- rcu-tasks: Fix IPI failure handling in trc_wait_for_one_reader
- rcu-tasks: Wait for trc_read_check_handler() IPIs
- rcu-tasks: Add trc_inspect_reader() checks for exiting critical section
- Linux 5.15.130

  * CVE-2023-42754
-

[Kernel-packages] [Bug 2039439] Re: usbip: error: failed to open /usr/share/hwdata//usb.ids

This bug was fixed in the package linux - 5.15.0-91.101

---
linux (5.15.0-91.101) jammy; urgency=medium

  * jammy/linux: 5.15.0-91.101 -proposed tracker (LP: #2043452)

  * USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix oversight in SuperSpeed initialization

linux (5.15.0-90.100) jammy; urgency=medium

  * jammy/linux: 5.15.0-90.100 -proposed tracker (LP: #2041603)

  * CVE-2023-25775
- RDMA/irdma: Remove irdma_uk_mw_bind()
- RDMA/irdma: Remove irdma_sc_send_lsmm_nostag()
- RDMA/irdma: Remove irdma_cqp_up_map_cmd()
- RDMA/irdma: Remove irdma_get_hw_addr()
- RDMA/irdma: Make irdma_uk_cq_init() return a void
- RDMA/irdma: optimize rx path by removing unnecessary copy
- RDMA/irdma: Remove enum irdma_status_code
- RDMA/irdma: Remove excess error variables
- RDMA/irdma: Prevent zero-length STAG registration

  * CVE-2023-39189
- netfilter: nfnetlink_osf: avoid OOB read

  * SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes
(LP: #2039575)
- net/smc: Fix pos miscalculation in statistics

  * CVE-2023-45871
- igb: set max size RX buffer when store bad packet is enabled

  * CVE-2023-39193
- netfilter: xt_sctp: validate the flag_info count

  * CVE-2023-39192
- netfilter: xt_u32: validate user space input

  * CVE-2023-31085
- ubi: Refuse attaching if mtd's erasesize is 0

  * CVE-2023-5717
- perf: Disallow mis-matched inherited group reads

  * CVE-2023-5178
- nvmet-tcp: Fix a possible UAF in queue intialization setup

  * CVE-2023-5158
- vringh: don't use vringh_kiov_advance() in vringh_iov_xfer()

  * [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module
(LP: #2033406)
- [Packaging] Make WWAN driver loadable modules

  * HP ProBook 450 G8 Notebook fail to wifi test (LP: #2037513)
- iwlwifi: mvm: Don't fail if PPAG isn't supported
- wifi: iwlwifi: fw: skip PPAG for JF

  * usbip: error: failed to open /usr/share/hwdata//usb.ids (LP: #2039439)
- [Packaging] Make linux-tools-common depend on hwdata

  * scripts/pahole-flags.sh change return to exit 0 (LP: #2035123)
- SAUCE: scripts/pahole-flags.sh change return to exit 0

  * Unable to use nvme drive to install Ubuntu 23.10 (LP: #2040157)
- misc: rtsx: Fix some platforms can not boot and move the l1ss judgment to
  probe

  * Jammy update: v5.15.131 upstream stable release (LP: #2039610)
- erofs: ensure that the post-EOF tails are all zeroed
- ksmbd: fix wrong DataOffset validation of create context
- ksmbd: replace one-element array with flex-array member in struct
  smb2_ea_info
- ARM: pxa: remove use of symbol_get()
- mmc: au1xmmc: force non-modular build and remove symbol_get usage
- net: enetc: use EXPORT_SYMBOL_GPL for enetc_phc_index
- rtc: ds1685: use EXPORT_SYMBOL_GPL for ds1685_rtc_poweroff
- modules: only allow symbol_get of EXPORT_SYMBOL_GPL modules
- USB: serial: option: add Quectel EM05G variant (0x030e)
- USB: serial: option: add FOXCONN T99W368/T99W373 product
- ALSA: usb-audio: Fix init call orders for UAC1
- usb: dwc3: meson-g12a: do post init to fix broken usb after resumption
- usb: chipidea: imx: improve logic if samsung,picophy-* parameter is 0
- HID: wacom: remove the battery when the EKR is off
- staging: rtl8712: fix race condition
- Bluetooth: btsdio: fix use after free bug in btsdio_remove due to race
  condition
- wifi: mt76: mt7921: do not support one stream on secondary antenna only
- serial: qcom-geni: fix opp vote on shutdown
- serial: sc16is7xx: fix broken port 0 uart init
- serial: sc16is7xx: fix bug when first setting GPIO direction
- firmware: stratix10-svc: Fix an NULL vs IS_ERR() bug in probe
- fsi: master-ast-cf: Add MODULE_FIRMWARE macro
- tcpm: Avoid soft reset when partner does not support get_status
- nilfs2: fix general protection fault in nilfs_lookup_dirty_data_buffers()
- nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse
- pinctrl: amd: Don't show `Invalid config param` errors
- usb: typec: tcpci: move tcpci.h to include/linux/usb/
- usb: typec: tcpci: clear the fault status bit
- Linux 5.15.131

  * Jammy update: v5.15.130 upstream stable release (LP: #2039608)
- ACPI: thermal: Drop nocrt parameter
- module: Expose module_init_layout_section()
- arm64: module-plts: inline linux/moduleloader.h
- arm64: module: Use module_init_layout_section() to spot init sections
- ARM: module: Use module_init_layout_section() to spot init sections
- rcu: Prevent expedited GP from enabling tick on offline CPU
- rcu-tasks: Fix IPI failure handling in trc_wait_for_one_reader
- rcu-tasks: Wait for trc_read_check_handler() IPIs
- rcu-tasks: Add trc_inspect_reader() checks for exiting critical section
- Linux 5.15.130

  * CVE-2023-42754
-

[Kernel-packages] [Bug 2039440] Re: Focal update: v5.4.255 upstream stable release

This bug was fixed in the package linux - 5.4.0-169.187

---
linux (5.4.0-169.187) focal; urgency=medium

  * focal/linux: 5.4.0-169.187 -proposed tracker (LP: #2044375)

  * USB bus error after upgrading to proposed kernel on lunar, jammy and focal
(LP: #2043197)
- USB: core: Fix oversight in SuperSpeed initialization

  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
- [Packaging] resync update-dkms-versions helper
- [Packaging] update annotations scripts

linux (5.4.0-168.186) focal; urgency=medium

  * focal/linux: 5.4.0-168.186 -proposed tracker (LP: #2041652)

  * Focal update: v5.4.257 upstream stable release (LP: #2040284)
- erofs: ensure that the post-EOF tails are all zeroed
- ARM: pxa: remove use of symbol_get()
- mmc: au1xmmc: force non-modular build and remove symbol_get usage
- net: enetc: use EXPORT_SYMBOL_GPL for enetc_phc_index
- rtc: ds1685: use EXPORT_SYMBOL_GPL for ds1685_rtc_poweroff
- modules: only allow symbol_get of EXPORT_SYMBOL_GPL modules
- USB: serial: option: add Quectel EM05G variant (0x030e)
- USB: serial: option: add FOXCONN T99W368/T99W373 product
- HID: wacom: remove the battery when the EKR is off
- staging: rtl8712: fix race condition
- Bluetooth: btsdio: fix use after free bug in btsdio_remove due to race
  condition
- serial: sc16is7xx: fix bug when first setting GPIO direction
- firmware: stratix10-svc: Fix an NULL vs IS_ERR() bug in probe
- fsi: master-ast-cf: Add MODULE_FIRMWARE macro
- nilfs2: fix general protection fault in nilfs_lookup_dirty_data_buffers()
- nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse
- pinctrl: amd: Don't show `Invalid config param` errors
- 9p: virtio: make sure 'offs' is initialized in zc_request
- ASoC: da7219: Flush pending AAD IRQ when suspending
- ASoC: da7219: Check for failure reading AAD IRQ events
- ethernet: atheros: fix return value check in atl1c_tso_csum()
- vxlan: generalize vxlan_parse_gpe_hdr and remove unused args
- m68k: Fix invalid .section syntax
- s390/dasd: use correct number of retries for ERP requests
- s390/dasd: fix hanging device after request requeue
- fs/nls: make load_nls() take a const parameter
- ASoc: codecs: ES8316: Fix DMIC config
- ASoC: atmel: Fix the 8K sample parameter in I2SC master
- platform/x86: intel: hid: Always call BTNL ACPI method
- platform/x86: huawei-wmi: Silence ambient light sensor
- security: keys: perform capable check only on privileged operations
- clk: fixed-mmio: make COMMON_CLK_FIXED_MMIO depend on HAS_IOMEM
- net: usb: qmi_wwan: add Quectel EM05GV2
- idmaengine: make FSL_EDMA and INTEL_IDMA64 depends on HAS_IOMEM
- scsi: qedi: Fix potential deadlock on &qedi_percpu->p_work_lock
- netlabel: fix shift wrapping bug in netlbl_catmap_setlong()
- bnx2x: fix page fault following EEH recovery
- sctp: handle invalid error codes without calling BUG()
- cifs: add a warning when the in-flight count goes negative
- scsi: storvsc: Always set no_report_opcodes
- ALSA: seq: oss: Fix racy open/close of MIDI devices
- platform/mellanox: Fix mlxbf-tmfifo not handling all virtio CONSOLE
  notifications
- powerpc/32s: Fix assembler warning about r0
- udf: Check consistency of Space Bitmap Descriptor
- udf: Handle error when adding extent to a file
- Revert "net: macsec: preserve ingress frame ordering"
- reiserfs: Check the return value from __getblk()
- eventfd: Export eventfd_ctx_do_read()
- eventfd: prevent underflow for eventfd semaphores
- new helper: lookup_positive_unlocked()
- fs: Fix error checking for d_hash_and_lookup()
- tmpfs: verify {g,u}id mount options correctly
- OPP: Fix passing 0 to PTR_ERR in _opp_attach_genpd()
- x86/asm: Make more symbols local
- x86/boot: Annotate local functions
- x86/decompressor: Don't rely on upper 32 bits of GPRs being preserved
- perf/imx_ddr: don't enable counter0 if none of 4 counters are used
- cpufreq: powernow-k8: Use related_cpus instead of cpus in driver.exit()
- bpf: Clear the probe_addr for uprobe
- tcp: tcp_enter_quickack_mode() should be static
- regmap: rbtree: Use alloc_flags for memory allocations
- spi: tegra20-sflash: fix to check return value of platform_get_irq() in
  tegra_sflash_probe()
- can: gs_usb: gs_usb_receive_bulk_callback(): count RX overflow errors also
  in case of OOM
- wifi: mwifiex: Fix OOB and integer underflow when rx packets
- mwifiex: switch from 'pci_' to 'dma_' API
- wifi: mwifiex: fix error recovery in PCIE buffer descriptor management
- crypto: stm32 - Properly handle pm_runtime_get failing
- Bluetooth: nokia: fix value check in nokia_bluetooth_serdev_probe()
- crypto: caam - fix unchecked return value error
- hwrng: iproc-rng200 - use semicolons rat

[Kernel-packages] [Bug 2039446] Re: Focal update: v5.4.256 upstream stable release

This bug was fixed in the package linux - 5.4.0-169.187

---
linux (5.4.0-169.187) focal; urgency=medium

  * focal/linux: 5.4.0-169.187 -proposed tracker (LP: #2044375)

  * USB bus error after upgrading to proposed kernel on lunar, jammy and focal
(LP: #2043197)
- USB: core: Fix oversight in SuperSpeed initialization

  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
- [Packaging] resync update-dkms-versions helper
- [Packaging] update annotations scripts

linux (5.4.0-168.186) focal; urgency=medium

  * focal/linux: 5.4.0-168.186 -proposed tracker (LP: #2041652)

  * Focal update: v5.4.257 upstream stable release (LP: #2040284)
- erofs: ensure that the post-EOF tails are all zeroed
- ARM: pxa: remove use of symbol_get()
- mmc: au1xmmc: force non-modular build and remove symbol_get usage
- net: enetc: use EXPORT_SYMBOL_GPL for enetc_phc_index
- rtc: ds1685: use EXPORT_SYMBOL_GPL for ds1685_rtc_poweroff
- modules: only allow symbol_get of EXPORT_SYMBOL_GPL modules
- USB: serial: option: add Quectel EM05G variant (0x030e)
- USB: serial: option: add FOXCONN T99W368/T99W373 product
- HID: wacom: remove the battery when the EKR is off
- staging: rtl8712: fix race condition
- Bluetooth: btsdio: fix use after free bug in btsdio_remove due to race
  condition
- serial: sc16is7xx: fix bug when first setting GPIO direction
- firmware: stratix10-svc: Fix an NULL vs IS_ERR() bug in probe
- fsi: master-ast-cf: Add MODULE_FIRMWARE macro
- nilfs2: fix general protection fault in nilfs_lookup_dirty_data_buffers()
- nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse
- pinctrl: amd: Don't show `Invalid config param` errors
- 9p: virtio: make sure 'offs' is initialized in zc_request
- ASoC: da7219: Flush pending AAD IRQ when suspending
- ASoC: da7219: Check for failure reading AAD IRQ events
- ethernet: atheros: fix return value check in atl1c_tso_csum()
- vxlan: generalize vxlan_parse_gpe_hdr and remove unused args
- m68k: Fix invalid .section syntax
- s390/dasd: use correct number of retries for ERP requests
- s390/dasd: fix hanging device after request requeue
- fs/nls: make load_nls() take a const parameter
- ASoc: codecs: ES8316: Fix DMIC config
- ASoC: atmel: Fix the 8K sample parameter in I2SC master
- platform/x86: intel: hid: Always call BTNL ACPI method
- platform/x86: huawei-wmi: Silence ambient light sensor
- security: keys: perform capable check only on privileged operations
- clk: fixed-mmio: make COMMON_CLK_FIXED_MMIO depend on HAS_IOMEM
- net: usb: qmi_wwan: add Quectel EM05GV2
- idmaengine: make FSL_EDMA and INTEL_IDMA64 depends on HAS_IOMEM
- scsi: qedi: Fix potential deadlock on &qedi_percpu->p_work_lock
- netlabel: fix shift wrapping bug in netlbl_catmap_setlong()
- bnx2x: fix page fault following EEH recovery
- sctp: handle invalid error codes without calling BUG()
- cifs: add a warning when the in-flight count goes negative
- scsi: storvsc: Always set no_report_opcodes
- ALSA: seq: oss: Fix racy open/close of MIDI devices
- platform/mellanox: Fix mlxbf-tmfifo not handling all virtio CONSOLE
  notifications
- powerpc/32s: Fix assembler warning about r0
- udf: Check consistency of Space Bitmap Descriptor
- udf: Handle error when adding extent to a file
- Revert "net: macsec: preserve ingress frame ordering"
- reiserfs: Check the return value from __getblk()
- eventfd: Export eventfd_ctx_do_read()
- eventfd: prevent underflow for eventfd semaphores
- new helper: lookup_positive_unlocked()
- fs: Fix error checking for d_hash_and_lookup()
- tmpfs: verify {g,u}id mount options correctly
- OPP: Fix passing 0 to PTR_ERR in _opp_attach_genpd()
- x86/asm: Make more symbols local
- x86/boot: Annotate local functions
- x86/decompressor: Don't rely on upper 32 bits of GPRs being preserved
- perf/imx_ddr: don't enable counter0 if none of 4 counters are used
- cpufreq: powernow-k8: Use related_cpus instead of cpus in driver.exit()
- bpf: Clear the probe_addr for uprobe
- tcp: tcp_enter_quickack_mode() should be static
- regmap: rbtree: Use alloc_flags for memory allocations
- spi: tegra20-sflash: fix to check return value of platform_get_irq() in
  tegra_sflash_probe()
- can: gs_usb: gs_usb_receive_bulk_callback(): count RX overflow errors also
  in case of OOM
- wifi: mwifiex: Fix OOB and integer underflow when rx packets
- mwifiex: switch from 'pci_' to 'dma_' API
- wifi: mwifiex: fix error recovery in PCIE buffer descriptor management
- crypto: stm32 - Properly handle pm_runtime_get failing
- Bluetooth: nokia: fix value check in nokia_bluetooth_serdev_probe()
- crypto: caam - fix unchecked return value error
- hwrng: iproc-rng200 - use semicolons rat

[Kernel-packages] [Bug 2039575] Re: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes

This bug was fixed in the package linux - 5.15.0-91.101

---
linux (5.15.0-91.101) jammy; urgency=medium

  * jammy/linux: 5.15.0-91.101 -proposed tracker (LP: #2043452)

  * USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix oversight in SuperSpeed initialization

linux (5.15.0-90.100) jammy; urgency=medium

  * jammy/linux: 5.15.0-90.100 -proposed tracker (LP: #2041603)

  * CVE-2023-25775
- RDMA/irdma: Remove irdma_uk_mw_bind()
- RDMA/irdma: Remove irdma_sc_send_lsmm_nostag()
- RDMA/irdma: Remove irdma_cqp_up_map_cmd()
- RDMA/irdma: Remove irdma_get_hw_addr()
- RDMA/irdma: Make irdma_uk_cq_init() return a void
- RDMA/irdma: optimize rx path by removing unnecessary copy
- RDMA/irdma: Remove enum irdma_status_code
- RDMA/irdma: Remove excess error variables
- RDMA/irdma: Prevent zero-length STAG registration

  * CVE-2023-39189
- netfilter: nfnetlink_osf: avoid OOB read

  * SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes
(LP: #2039575)
- net/smc: Fix pos miscalculation in statistics

  * CVE-2023-45871
- igb: set max size RX buffer when store bad packet is enabled

  * CVE-2023-39193
- netfilter: xt_sctp: validate the flag_info count

  * CVE-2023-39192
- netfilter: xt_u32: validate user space input

  * CVE-2023-31085
- ubi: Refuse attaching if mtd's erasesize is 0

  * CVE-2023-5717
- perf: Disallow mis-matched inherited group reads

  * CVE-2023-5178
- nvmet-tcp: Fix a possible UAF in queue intialization setup

  * CVE-2023-5158
- vringh: don't use vringh_kiov_advance() in vringh_iov_xfer()

  * [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module
(LP: #2033406)
- [Packaging] Make WWAN driver loadable modules

  * HP ProBook 450 G8 Notebook fail to wifi test (LP: #2037513)
- iwlwifi: mvm: Don't fail if PPAG isn't supported
- wifi: iwlwifi: fw: skip PPAG for JF

  * usbip: error: failed to open /usr/share/hwdata//usb.ids (LP: #2039439)
- [Packaging] Make linux-tools-common depend on hwdata

  * scripts/pahole-flags.sh change return to exit 0 (LP: #2035123)
- SAUCE: scripts/pahole-flags.sh change return to exit 0

  * Unable to use nvme drive to install Ubuntu 23.10 (LP: #2040157)
- misc: rtsx: Fix some platforms can not boot and move the l1ss judgment to
  probe

  * Jammy update: v5.15.131 upstream stable release (LP: #2039610)
- erofs: ensure that the post-EOF tails are all zeroed
- ksmbd: fix wrong DataOffset validation of create context
- ksmbd: replace one-element array with flex-array member in struct
  smb2_ea_info
- ARM: pxa: remove use of symbol_get()
- mmc: au1xmmc: force non-modular build and remove symbol_get usage
- net: enetc: use EXPORT_SYMBOL_GPL for enetc_phc_index
- rtc: ds1685: use EXPORT_SYMBOL_GPL for ds1685_rtc_poweroff
- modules: only allow symbol_get of EXPORT_SYMBOL_GPL modules
- USB: serial: option: add Quectel EM05G variant (0x030e)
- USB: serial: option: add FOXCONN T99W368/T99W373 product
- ALSA: usb-audio: Fix init call orders for UAC1
- usb: dwc3: meson-g12a: do post init to fix broken usb after resumption
- usb: chipidea: imx: improve logic if samsung,picophy-* parameter is 0
- HID: wacom: remove the battery when the EKR is off
- staging: rtl8712: fix race condition
- Bluetooth: btsdio: fix use after free bug in btsdio_remove due to race
  condition
- wifi: mt76: mt7921: do not support one stream on secondary antenna only
- serial: qcom-geni: fix opp vote on shutdown
- serial: sc16is7xx: fix broken port 0 uart init
- serial: sc16is7xx: fix bug when first setting GPIO direction
- firmware: stratix10-svc: Fix an NULL vs IS_ERR() bug in probe
- fsi: master-ast-cf: Add MODULE_FIRMWARE macro
- tcpm: Avoid soft reset when partner does not support get_status
- nilfs2: fix general protection fault in nilfs_lookup_dirty_data_buffers()
- nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse
- pinctrl: amd: Don't show `Invalid config param` errors
- usb: typec: tcpci: move tcpci.h to include/linux/usb/
- usb: typec: tcpci: clear the fault status bit
- Linux 5.15.131

  * Jammy update: v5.15.130 upstream stable release (LP: #2039608)
- ACPI: thermal: Drop nocrt parameter
- module: Expose module_init_layout_section()
- arm64: module-plts: inline linux/moduleloader.h
- arm64: module: Use module_init_layout_section() to spot init sections
- ARM: module: Use module_init_layout_section() to spot init sections
- rcu: Prevent expedited GP from enabling tick on offline CPU
- rcu-tasks: Fix IPI failure handling in trc_wait_for_one_reader
- rcu-tasks: Wait for trc_read_check_handler() IPIs
- rcu-tasks: Add trc_inspect_reader() checks for exiting critical section
- Linux 5.15.130

  * CVE-2023-42754
-

[Kernel-packages] [Bug 2039608] Re: Jammy update: v5.15.130 upstream stable release

This bug was fixed in the package linux - 5.15.0-91.101

---
linux (5.15.0-91.101) jammy; urgency=medium

  * jammy/linux: 5.15.0-91.101 -proposed tracker (LP: #2043452)

  * USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix oversight in SuperSpeed initialization

linux (5.15.0-90.100) jammy; urgency=medium

  * jammy/linux: 5.15.0-90.100 -proposed tracker (LP: #2041603)

  * CVE-2023-25775
- RDMA/irdma: Remove irdma_uk_mw_bind()
- RDMA/irdma: Remove irdma_sc_send_lsmm_nostag()
- RDMA/irdma: Remove irdma_cqp_up_map_cmd()
- RDMA/irdma: Remove irdma_get_hw_addr()
- RDMA/irdma: Make irdma_uk_cq_init() return a void
- RDMA/irdma: optimize rx path by removing unnecessary copy
- RDMA/irdma: Remove enum irdma_status_code
- RDMA/irdma: Remove excess error variables
- RDMA/irdma: Prevent zero-length STAG registration

  * CVE-2023-39189
- netfilter: nfnetlink_osf: avoid OOB read

  * SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes
(LP: #2039575)
- net/smc: Fix pos miscalculation in statistics

  * CVE-2023-45871
- igb: set max size RX buffer when store bad packet is enabled

  * CVE-2023-39193
- netfilter: xt_sctp: validate the flag_info count

  * CVE-2023-39192
- netfilter: xt_u32: validate user space input

  * CVE-2023-31085
- ubi: Refuse attaching if mtd's erasesize is 0

  * CVE-2023-5717
- perf: Disallow mis-matched inherited group reads

  * CVE-2023-5178
- nvmet-tcp: Fix a possible UAF in queue intialization setup

  * CVE-2023-5158
- vringh: don't use vringh_kiov_advance() in vringh_iov_xfer()

  * [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module
(LP: #2033406)
- [Packaging] Make WWAN driver loadable modules

  * HP ProBook 450 G8 Notebook fail to wifi test (LP: #2037513)
- iwlwifi: mvm: Don't fail if PPAG isn't supported
- wifi: iwlwifi: fw: skip PPAG for JF

  * usbip: error: failed to open /usr/share/hwdata//usb.ids (LP: #2039439)
- [Packaging] Make linux-tools-common depend on hwdata

  * scripts/pahole-flags.sh change return to exit 0 (LP: #2035123)
- SAUCE: scripts/pahole-flags.sh change return to exit 0

  * Unable to use nvme drive to install Ubuntu 23.10 (LP: #2040157)
- misc: rtsx: Fix some platforms can not boot and move the l1ss judgment to
  probe

  * Jammy update: v5.15.131 upstream stable release (LP: #2039610)
- erofs: ensure that the post-EOF tails are all zeroed
- ksmbd: fix wrong DataOffset validation of create context
- ksmbd: replace one-element array with flex-array member in struct
  smb2_ea_info
- ARM: pxa: remove use of symbol_get()
- mmc: au1xmmc: force non-modular build and remove symbol_get usage
- net: enetc: use EXPORT_SYMBOL_GPL for enetc_phc_index
- rtc: ds1685: use EXPORT_SYMBOL_GPL for ds1685_rtc_poweroff
- modules: only allow symbol_get of EXPORT_SYMBOL_GPL modules
- USB: serial: option: add Quectel EM05G variant (0x030e)
- USB: serial: option: add FOXCONN T99W368/T99W373 product
- ALSA: usb-audio: Fix init call orders for UAC1
- usb: dwc3: meson-g12a: do post init to fix broken usb after resumption
- usb: chipidea: imx: improve logic if samsung,picophy-* parameter is 0
- HID: wacom: remove the battery when the EKR is off
- staging: rtl8712: fix race condition
- Bluetooth: btsdio: fix use after free bug in btsdio_remove due to race
  condition
- wifi: mt76: mt7921: do not support one stream on secondary antenna only
- serial: qcom-geni: fix opp vote on shutdown
- serial: sc16is7xx: fix broken port 0 uart init
- serial: sc16is7xx: fix bug when first setting GPIO direction
- firmware: stratix10-svc: Fix an NULL vs IS_ERR() bug in probe
- fsi: master-ast-cf: Add MODULE_FIRMWARE macro
- tcpm: Avoid soft reset when partner does not support get_status
- nilfs2: fix general protection fault in nilfs_lookup_dirty_data_buffers()
- nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse
- pinctrl: amd: Don't show `Invalid config param` errors
- usb: typec: tcpci: move tcpci.h to include/linux/usb/
- usb: typec: tcpci: clear the fault status bit
- Linux 5.15.131

  * Jammy update: v5.15.130 upstream stable release (LP: #2039608)
- ACPI: thermal: Drop nocrt parameter
- module: Expose module_init_layout_section()
- arm64: module-plts: inline linux/moduleloader.h
- arm64: module: Use module_init_layout_section() to spot init sections
- ARM: module: Use module_init_layout_section() to spot init sections
- rcu: Prevent expedited GP from enabling tick on offline CPU
- rcu-tasks: Fix IPI failure handling in trc_wait_for_one_reader
- rcu-tasks: Wait for trc_read_check_handler() IPIs
- rcu-tasks: Add trc_inspect_reader() checks for exiting critical section
- Linux 5.15.130

  * CVE-2023-42754
-

[Kernel-packages] [Bug 2039610] Re: Jammy update: v5.15.131 upstream stable release

This bug was fixed in the package linux - 5.15.0-91.101

---
linux (5.15.0-91.101) jammy; urgency=medium

  * jammy/linux: 5.15.0-91.101 -proposed tracker (LP: #2043452)

  * USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix oversight in SuperSpeed initialization

linux (5.15.0-90.100) jammy; urgency=medium

  * jammy/linux: 5.15.0-90.100 -proposed tracker (LP: #2041603)

  * CVE-2023-25775
- RDMA/irdma: Remove irdma_uk_mw_bind()
- RDMA/irdma: Remove irdma_sc_send_lsmm_nostag()
- RDMA/irdma: Remove irdma_cqp_up_map_cmd()
- RDMA/irdma: Remove irdma_get_hw_addr()
- RDMA/irdma: Make irdma_uk_cq_init() return a void
- RDMA/irdma: optimize rx path by removing unnecessary copy
- RDMA/irdma: Remove enum irdma_status_code
- RDMA/irdma: Remove excess error variables
- RDMA/irdma: Prevent zero-length STAG registration

  * CVE-2023-39189
- netfilter: nfnetlink_osf: avoid OOB read

  * SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes
(LP: #2039575)
- net/smc: Fix pos miscalculation in statistics

  * CVE-2023-45871
- igb: set max size RX buffer when store bad packet is enabled

  * CVE-2023-39193
- netfilter: xt_sctp: validate the flag_info count

  * CVE-2023-39192
- netfilter: xt_u32: validate user space input

  * CVE-2023-31085
- ubi: Refuse attaching if mtd's erasesize is 0

  * CVE-2023-5717
- perf: Disallow mis-matched inherited group reads

  * CVE-2023-5178
- nvmet-tcp: Fix a possible UAF in queue intialization setup

  * CVE-2023-5158
- vringh: don't use vringh_kiov_advance() in vringh_iov_xfer()

  * [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module
(LP: #2033406)
- [Packaging] Make WWAN driver loadable modules

  * HP ProBook 450 G8 Notebook fail to wifi test (LP: #2037513)
- iwlwifi: mvm: Don't fail if PPAG isn't supported
- wifi: iwlwifi: fw: skip PPAG for JF

  * usbip: error: failed to open /usr/share/hwdata//usb.ids (LP: #2039439)
- [Packaging] Make linux-tools-common depend on hwdata

  * scripts/pahole-flags.sh change return to exit 0 (LP: #2035123)
- SAUCE: scripts/pahole-flags.sh change return to exit 0

  * Unable to use nvme drive to install Ubuntu 23.10 (LP: #2040157)
- misc: rtsx: Fix some platforms can not boot and move the l1ss judgment to
  probe

  * Jammy update: v5.15.131 upstream stable release (LP: #2039610)
- erofs: ensure that the post-EOF tails are all zeroed
- ksmbd: fix wrong DataOffset validation of create context
- ksmbd: replace one-element array with flex-array member in struct
  smb2_ea_info
- ARM: pxa: remove use of symbol_get()
- mmc: au1xmmc: force non-modular build and remove symbol_get usage
- net: enetc: use EXPORT_SYMBOL_GPL for enetc_phc_index
- rtc: ds1685: use EXPORT_SYMBOL_GPL for ds1685_rtc_poweroff
- modules: only allow symbol_get of EXPORT_SYMBOL_GPL modules
- USB: serial: option: add Quectel EM05G variant (0x030e)
- USB: serial: option: add FOXCONN T99W368/T99W373 product
- ALSA: usb-audio: Fix init call orders for UAC1
- usb: dwc3: meson-g12a: do post init to fix broken usb after resumption
- usb: chipidea: imx: improve logic if samsung,picophy-* parameter is 0
- HID: wacom: remove the battery when the EKR is off
- staging: rtl8712: fix race condition
- Bluetooth: btsdio: fix use after free bug in btsdio_remove due to race
  condition
- wifi: mt76: mt7921: do not support one stream on secondary antenna only
- serial: qcom-geni: fix opp vote on shutdown
- serial: sc16is7xx: fix broken port 0 uart init
- serial: sc16is7xx: fix bug when first setting GPIO direction
- firmware: stratix10-svc: Fix an NULL vs IS_ERR() bug in probe
- fsi: master-ast-cf: Add MODULE_FIRMWARE macro
- tcpm: Avoid soft reset when partner does not support get_status
- nilfs2: fix general protection fault in nilfs_lookup_dirty_data_buffers()
- nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse
- pinctrl: amd: Don't show `Invalid config param` errors
- usb: typec: tcpci: move tcpci.h to include/linux/usb/
- usb: typec: tcpci: clear the fault status bit
- Linux 5.15.131

  * Jammy update: v5.15.130 upstream stable release (LP: #2039608)
- ACPI: thermal: Drop nocrt parameter
- module: Expose module_init_layout_section()
- arm64: module-plts: inline linux/moduleloader.h
- arm64: module: Use module_init_layout_section() to spot init sections
- ARM: module: Use module_init_layout_section() to spot init sections
- rcu: Prevent expedited GP from enabling tick on offline CPU
- rcu-tasks: Fix IPI failure handling in trc_wait_for_one_reader
- rcu-tasks: Wait for trc_read_check_handler() IPIs
- rcu-tasks: Add trc_inspect_reader() checks for exiting critical section
- Linux 5.15.130

  * CVE-2023-42754
-

[Kernel-packages] [Bug 2040157] Re: Unable to use nvme drive to install Ubuntu 23.10

This bug was fixed in the package linux - 5.15.0-91.101

---
linux (5.15.0-91.101) jammy; urgency=medium

  * jammy/linux: 5.15.0-91.101 -proposed tracker (LP: #2043452)

  * USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix oversight in SuperSpeed initialization

linux (5.15.0-90.100) jammy; urgency=medium

  * jammy/linux: 5.15.0-90.100 -proposed tracker (LP: #2041603)

  * CVE-2023-25775
- RDMA/irdma: Remove irdma_uk_mw_bind()
- RDMA/irdma: Remove irdma_sc_send_lsmm_nostag()
- RDMA/irdma: Remove irdma_cqp_up_map_cmd()
- RDMA/irdma: Remove irdma_get_hw_addr()
- RDMA/irdma: Make irdma_uk_cq_init() return a void
- RDMA/irdma: optimize rx path by removing unnecessary copy
- RDMA/irdma: Remove enum irdma_status_code
- RDMA/irdma: Remove excess error variables
- RDMA/irdma: Prevent zero-length STAG registration

  * CVE-2023-39189
- netfilter: nfnetlink_osf: avoid OOB read

  * SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes
(LP: #2039575)
- net/smc: Fix pos miscalculation in statistics

  * CVE-2023-45871
- igb: set max size RX buffer when store bad packet is enabled

  * CVE-2023-39193
- netfilter: xt_sctp: validate the flag_info count

  * CVE-2023-39192
- netfilter: xt_u32: validate user space input

  * CVE-2023-31085
- ubi: Refuse attaching if mtd's erasesize is 0

  * CVE-2023-5717
- perf: Disallow mis-matched inherited group reads

  * CVE-2023-5178
- nvmet-tcp: Fix a possible UAF in queue intialization setup

  * CVE-2023-5158
- vringh: don't use vringh_kiov_advance() in vringh_iov_xfer()

  * [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module
(LP: #2033406)
- [Packaging] Make WWAN driver loadable modules

  * HP ProBook 450 G8 Notebook fail to wifi test (LP: #2037513)
- iwlwifi: mvm: Don't fail if PPAG isn't supported
- wifi: iwlwifi: fw: skip PPAG for JF

  * usbip: error: failed to open /usr/share/hwdata//usb.ids (LP: #2039439)
- [Packaging] Make linux-tools-common depend on hwdata

  * scripts/pahole-flags.sh change return to exit 0 (LP: #2035123)
- SAUCE: scripts/pahole-flags.sh change return to exit 0

  * Unable to use nvme drive to install Ubuntu 23.10 (LP: #2040157)
- misc: rtsx: Fix some platforms can not boot and move the l1ss judgment to
  probe

  * Jammy update: v5.15.131 upstream stable release (LP: #2039610)
- erofs: ensure that the post-EOF tails are all zeroed
- ksmbd: fix wrong DataOffset validation of create context
- ksmbd: replace one-element array with flex-array member in struct
  smb2_ea_info
- ARM: pxa: remove use of symbol_get()
- mmc: au1xmmc: force non-modular build and remove symbol_get usage
- net: enetc: use EXPORT_SYMBOL_GPL for enetc_phc_index
- rtc: ds1685: use EXPORT_SYMBOL_GPL for ds1685_rtc_poweroff
- modules: only allow symbol_get of EXPORT_SYMBOL_GPL modules
- USB: serial: option: add Quectel EM05G variant (0x030e)
- USB: serial: option: add FOXCONN T99W368/T99W373 product
- ALSA: usb-audio: Fix init call orders for UAC1
- usb: dwc3: meson-g12a: do post init to fix broken usb after resumption
- usb: chipidea: imx: improve logic if samsung,picophy-* parameter is 0
- HID: wacom: remove the battery when the EKR is off
- staging: rtl8712: fix race condition
- Bluetooth: btsdio: fix use after free bug in btsdio_remove due to race
  condition
- wifi: mt76: mt7921: do not support one stream on secondary antenna only
- serial: qcom-geni: fix opp vote on shutdown
- serial: sc16is7xx: fix broken port 0 uart init
- serial: sc16is7xx: fix bug when first setting GPIO direction
- firmware: stratix10-svc: Fix an NULL vs IS_ERR() bug in probe
- fsi: master-ast-cf: Add MODULE_FIRMWARE macro
- tcpm: Avoid soft reset when partner does not support get_status
- nilfs2: fix general protection fault in nilfs_lookup_dirty_data_buffers()
- nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse
- pinctrl: amd: Don't show `Invalid config param` errors
- usb: typec: tcpci: move tcpci.h to include/linux/usb/
- usb: typec: tcpci: clear the fault status bit
- Linux 5.15.131

  * Jammy update: v5.15.130 upstream stable release (LP: #2039608)
- ACPI: thermal: Drop nocrt parameter
- module: Expose module_init_layout_section()
- arm64: module-plts: inline linux/moduleloader.h
- arm64: module: Use module_init_layout_section() to spot init sections
- ARM: module: Use module_init_layout_section() to spot init sections
- rcu: Prevent expedited GP from enabling tick on offline CPU
- rcu-tasks: Fix IPI failure handling in trc_wait_for_one_reader
- rcu-tasks: Wait for trc_read_check_handler() IPIs
- rcu-tasks: Add trc_inspect_reader() checks for exiting critical section
- Linux 5.15.130

  * CVE-2023-42754
-

[Kernel-packages] [Bug 2040284] Re: Focal update: v5.4.257 upstream stable release

This bug was fixed in the package linux - 5.4.0-169.187

---
linux (5.4.0-169.187) focal; urgency=medium

  * focal/linux: 5.4.0-169.187 -proposed tracker (LP: #2044375)

  * USB bus error after upgrading to proposed kernel on lunar, jammy and focal
(LP: #2043197)
- USB: core: Fix oversight in SuperSpeed initialization

  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
- [Packaging] resync update-dkms-versions helper
- [Packaging] update annotations scripts

linux (5.4.0-168.186) focal; urgency=medium

  * focal/linux: 5.4.0-168.186 -proposed tracker (LP: #2041652)

  * Focal update: v5.4.257 upstream stable release (LP: #2040284)
- erofs: ensure that the post-EOF tails are all zeroed
- ARM: pxa: remove use of symbol_get()
- mmc: au1xmmc: force non-modular build and remove symbol_get usage
- net: enetc: use EXPORT_SYMBOL_GPL for enetc_phc_index
- rtc: ds1685: use EXPORT_SYMBOL_GPL for ds1685_rtc_poweroff
- modules: only allow symbol_get of EXPORT_SYMBOL_GPL modules
- USB: serial: option: add Quectel EM05G variant (0x030e)
- USB: serial: option: add FOXCONN T99W368/T99W373 product
- HID: wacom: remove the battery when the EKR is off
- staging: rtl8712: fix race condition
- Bluetooth: btsdio: fix use after free bug in btsdio_remove due to race
  condition
- serial: sc16is7xx: fix bug when first setting GPIO direction
- firmware: stratix10-svc: Fix an NULL vs IS_ERR() bug in probe
- fsi: master-ast-cf: Add MODULE_FIRMWARE macro
- nilfs2: fix general protection fault in nilfs_lookup_dirty_data_buffers()
- nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse
- pinctrl: amd: Don't show `Invalid config param` errors
- 9p: virtio: make sure 'offs' is initialized in zc_request
- ASoC: da7219: Flush pending AAD IRQ when suspending
- ASoC: da7219: Check for failure reading AAD IRQ events
- ethernet: atheros: fix return value check in atl1c_tso_csum()
- vxlan: generalize vxlan_parse_gpe_hdr and remove unused args
- m68k: Fix invalid .section syntax
- s390/dasd: use correct number of retries for ERP requests
- s390/dasd: fix hanging device after request requeue
- fs/nls: make load_nls() take a const parameter
- ASoc: codecs: ES8316: Fix DMIC config
- ASoC: atmel: Fix the 8K sample parameter in I2SC master
- platform/x86: intel: hid: Always call BTNL ACPI method
- platform/x86: huawei-wmi: Silence ambient light sensor
- security: keys: perform capable check only on privileged operations
- clk: fixed-mmio: make COMMON_CLK_FIXED_MMIO depend on HAS_IOMEM
- net: usb: qmi_wwan: add Quectel EM05GV2
- idmaengine: make FSL_EDMA and INTEL_IDMA64 depends on HAS_IOMEM
- scsi: qedi: Fix potential deadlock on &qedi_percpu->p_work_lock
- netlabel: fix shift wrapping bug in netlbl_catmap_setlong()
- bnx2x: fix page fault following EEH recovery
- sctp: handle invalid error codes without calling BUG()
- cifs: add a warning when the in-flight count goes negative
- scsi: storvsc: Always set no_report_opcodes
- ALSA: seq: oss: Fix racy open/close of MIDI devices
- platform/mellanox: Fix mlxbf-tmfifo not handling all virtio CONSOLE
  notifications
- powerpc/32s: Fix assembler warning about r0
- udf: Check consistency of Space Bitmap Descriptor
- udf: Handle error when adding extent to a file
- Revert "net: macsec: preserve ingress frame ordering"
- reiserfs: Check the return value from __getblk()
- eventfd: Export eventfd_ctx_do_read()
- eventfd: prevent underflow for eventfd semaphores
- new helper: lookup_positive_unlocked()
- fs: Fix error checking for d_hash_and_lookup()
- tmpfs: verify {g,u}id mount options correctly
- OPP: Fix passing 0 to PTR_ERR in _opp_attach_genpd()
- x86/asm: Make more symbols local
- x86/boot: Annotate local functions
- x86/decompressor: Don't rely on upper 32 bits of GPRs being preserved
- perf/imx_ddr: don't enable counter0 if none of 4 counters are used
- cpufreq: powernow-k8: Use related_cpus instead of cpus in driver.exit()
- bpf: Clear the probe_addr for uprobe
- tcp: tcp_enter_quickack_mode() should be static
- regmap: rbtree: Use alloc_flags for memory allocations
- spi: tegra20-sflash: fix to check return value of platform_get_irq() in
  tegra_sflash_probe()
- can: gs_usb: gs_usb_receive_bulk_callback(): count RX overflow errors also
  in case of OOM
- wifi: mwifiex: Fix OOB and integer underflow when rx packets
- mwifiex: switch from 'pci_' to 'dma_' API
- wifi: mwifiex: fix error recovery in PCIE buffer descriptor management
- crypto: stm32 - Properly handle pm_runtime_get failing
- Bluetooth: nokia: fix value check in nokia_bluetooth_serdev_probe()
- crypto: caam - fix unchecked return value error
- hwrng: iproc-rng200 - use semicolons rat

[Kernel-packages] [Bug 2040300] Re: Azure: Improve SQL DB latency

This bug was fixed in the package linux-azure - 5.15.0-1053.61

---
linux-azure (5.15.0-1053.61) jammy; urgency=medium

  * jammy/linux-azure: 5.15.0-1053.61 -proposed tracker (LP: #2041565)

  * Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper

  * Azure: Improve SQL DB latency (LP: #2040300)
- tcp: Set pingpong threshold via sysctl

  [ Ubuntu: 5.15.0-91.101 ]

  * jammy/linux: 5.15.0-91.101 -proposed tracker (LP: #2043452)
  * USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix oversight in SuperSpeed initialization

  [ Ubuntu: 5.15.0-90.100 ]

  * jammy/linux: 5.15.0-90.100 -proposed tracker (LP: #2041603)
  * CVE-2023-25775
- RDMA/irdma: Remove irdma_uk_mw_bind()
- RDMA/irdma: Remove irdma_sc_send_lsmm_nostag()
- RDMA/irdma: Remove irdma_cqp_up_map_cmd()
- RDMA/irdma: Remove irdma_get_hw_addr()
- RDMA/irdma: Make irdma_uk_cq_init() return a void
- RDMA/irdma: optimize rx path by removing unnecessary copy
- RDMA/irdma: Remove enum irdma_status_code
- RDMA/irdma: Remove excess error variables
- RDMA/irdma: Prevent zero-length STAG registration
  * CVE-2023-39189
- netfilter: nfnetlink_osf: avoid OOB read
  * SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes
(LP: #2039575)
- net/smc: Fix pos miscalculation in statistics
  * CVE-2023-45871
- igb: set max size RX buffer when store bad packet is enabled
  * CVE-2023-39193
- netfilter: xt_sctp: validate the flag_info count
  * CVE-2023-39192
- netfilter: xt_u32: validate user space input
  * CVE-2023-31085
- ubi: Refuse attaching if mtd's erasesize is 0
  * CVE-2023-5717
- perf: Disallow mis-matched inherited group reads
  * CVE-2023-5178
- nvmet-tcp: Fix a possible UAF in queue intialization setup
  * CVE-2023-5158
- vringh: don't use vringh_kiov_advance() in vringh_iov_xfer()
  * [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module
(LP: #2033406)
- [Packaging] Make WWAN driver loadable modules
  * HP ProBook 450 G8 Notebook fail to wifi test (LP: #2037513)
- iwlwifi: mvm: Don't fail if PPAG isn't supported
- wifi: iwlwifi: fw: skip PPAG for JF
  * usbip: error: failed to open /usr/share/hwdata//usb.ids (LP: #2039439)
- [Packaging] Make linux-tools-common depend on hwdata
  * scripts/pahole-flags.sh change return to exit 0 (LP: #2035123)
- SAUCE: scripts/pahole-flags.sh change return to exit 0
  * Unable to use nvme drive to install Ubuntu 23.10 (LP: #2040157)
- misc: rtsx: Fix some platforms can not boot and move the l1ss judgment to
  probe
  * Jammy update: v5.15.131 upstream stable release (LP: #2039610)
- erofs: ensure that the post-EOF tails are all zeroed
- ksmbd: fix wrong DataOffset validation of create context
- ksmbd: replace one-element array with flex-array member in struct
  smb2_ea_info
- ARM: pxa: remove use of symbol_get()
- mmc: au1xmmc: force non-modular build and remove symbol_get usage
- net: enetc: use EXPORT_SYMBOL_GPL for enetc_phc_index
- rtc: ds1685: use EXPORT_SYMBOL_GPL for ds1685_rtc_poweroff
- modules: only allow symbol_get of EXPORT_SYMBOL_GPL modules
- USB: serial: option: add Quectel EM05G variant (0x030e)
- USB: serial: option: add FOXCONN T99W368/T99W373 product
- ALSA: usb-audio: Fix init call orders for UAC1
- usb: dwc3: meson-g12a: do post init to fix broken usb after resumption
- usb: chipidea: imx: improve logic if samsung,picophy-* parameter is 0
- HID: wacom: remove the battery when the EKR is off
- staging: rtl8712: fix race condition
- Bluetooth: btsdio: fix use after free bug in btsdio_remove due to race
  condition
- wifi: mt76: mt7921: do not support one stream on secondary antenna only
- serial: qcom-geni: fix opp vote on shutdown
- serial: sc16is7xx: fix broken port 0 uart init
- serial: sc16is7xx: fix bug when first setting GPIO direction
- firmware: stratix10-svc: Fix an NULL vs IS_ERR() bug in probe
- fsi: master-ast-cf: Add MODULE_FIRMWARE macro
- tcpm: Avoid soft reset when partner does not support get_status
- nilfs2: fix general protection fault in nilfs_lookup_dirty_data_buffers()
- nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse
- pinctrl: amd: Don't show `Invalid config param` errors
- usb: typec: tcpci: move tcpci.h to include/linux/usb/
- usb: typec: tcpci: clear the fault status bit
- Linux 5.15.131
  * Jammy update: v5.15.130 upstream stable release (LP: #2039608)
- ACPI: thermal: Drop nocrt parameter
- module: Expose module_init_layout_section()
- arm64: module-plts: inline linux/moduleloader.h
- arm64: module: Use module_init_layout_section() to spot init sections
- ARM: module: Use module_init_layout_section() to spot init sections
- rcu: Prevent expedited GP from enabling tick

[Kernel-packages] [Bug 2040524] Re: openvswitch fails on raspberry pi 4

This bug was fixed in the package linux-raspi - 5.15.0-1044.47

---
linux-raspi (5.15.0-1044.47) jammy; urgency=medium

  * jammy/linux-raspi: 5.15.0-1044.47 -proposed tracker (LP: #2041598)

  * [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module
(LP: #2033406)
- [Packaging] raspi: Make WWAN driver loadable modules

  * openvswitch fails on raspberry pi 4 (LP: #2040524)
- [Packaging] raspi: Include openvswitch in linux-modules

  [ Ubuntu: 5.15.0-91.101 ]

  * jammy/linux: 5.15.0-91.101 -proposed tracker (LP: #2043452)
  * USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix oversight in SuperSpeed initialization

  [ Ubuntu: 5.15.0-90.100 ]

  * jammy/linux: 5.15.0-90.100 -proposed tracker (LP: #2041603)
  * CVE-2023-25775
- RDMA/irdma: Remove irdma_uk_mw_bind()
- RDMA/irdma: Remove irdma_sc_send_lsmm_nostag()
- RDMA/irdma: Remove irdma_cqp_up_map_cmd()
- RDMA/irdma: Remove irdma_get_hw_addr()
- RDMA/irdma: Make irdma_uk_cq_init() return a void
- RDMA/irdma: optimize rx path by removing unnecessary copy
- RDMA/irdma: Remove enum irdma_status_code
- RDMA/irdma: Remove excess error variables
- RDMA/irdma: Prevent zero-length STAG registration
  * CVE-2023-39189
- netfilter: nfnetlink_osf: avoid OOB read
  * SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes
(LP: #2039575)
- net/smc: Fix pos miscalculation in statistics
  * CVE-2023-45871
- igb: set max size RX buffer when store bad packet is enabled
  * CVE-2023-39193
- netfilter: xt_sctp: validate the flag_info count
  * CVE-2023-39192
- netfilter: xt_u32: validate user space input
  * CVE-2023-31085
- ubi: Refuse attaching if mtd's erasesize is 0
  * CVE-2023-5717
- perf: Disallow mis-matched inherited group reads
  * CVE-2023-5178
- nvmet-tcp: Fix a possible UAF in queue intialization setup
  * CVE-2023-5158
- vringh: don't use vringh_kiov_advance() in vringh_iov_xfer()
  * [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module
(LP: #2033406)
- [Packaging] Make WWAN driver loadable modules
  * HP ProBook 450 G8 Notebook fail to wifi test (LP: #2037513)
- iwlwifi: mvm: Don't fail if PPAG isn't supported
- wifi: iwlwifi: fw: skip PPAG for JF
  * usbip: error: failed to open /usr/share/hwdata//usb.ids (LP: #2039439)
- [Packaging] Make linux-tools-common depend on hwdata
  * scripts/pahole-flags.sh change return to exit 0 (LP: #2035123)
- SAUCE: scripts/pahole-flags.sh change return to exit 0
  * Unable to use nvme drive to install Ubuntu 23.10 (LP: #2040157)
- misc: rtsx: Fix some platforms can not boot and move the l1ss judgment to
  probe
  * Jammy update: v5.15.131 upstream stable release (LP: #2039610)
- erofs: ensure that the post-EOF tails are all zeroed
- ksmbd: fix wrong DataOffset validation of create context
- ksmbd: replace one-element array with flex-array member in struct
  smb2_ea_info
- ARM: pxa: remove use of symbol_get()
- mmc: au1xmmc: force non-modular build and remove symbol_get usage
- net: enetc: use EXPORT_SYMBOL_GPL for enetc_phc_index
- rtc: ds1685: use EXPORT_SYMBOL_GPL for ds1685_rtc_poweroff
- modules: only allow symbol_get of EXPORT_SYMBOL_GPL modules
- USB: serial: option: add Quectel EM05G variant (0x030e)
- USB: serial: option: add FOXCONN T99W368/T99W373 product
- ALSA: usb-audio: Fix init call orders for UAC1
- usb: dwc3: meson-g12a: do post init to fix broken usb after resumption
- usb: chipidea: imx: improve logic if samsung,picophy-* parameter is 0
- HID: wacom: remove the battery when the EKR is off
- staging: rtl8712: fix race condition
- Bluetooth: btsdio: fix use after free bug in btsdio_remove due to race
  condition
- wifi: mt76: mt7921: do not support one stream on secondary antenna only
- serial: qcom-geni: fix opp vote on shutdown
- serial: sc16is7xx: fix broken port 0 uart init
- serial: sc16is7xx: fix bug when first setting GPIO direction
- firmware: stratix10-svc: Fix an NULL vs IS_ERR() bug in probe
- fsi: master-ast-cf: Add MODULE_FIRMWARE macro
- tcpm: Avoid soft reset when partner does not support get_status
- nilfs2: fix general protection fault in nilfs_lookup_dirty_data_buffers()
- nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse
- pinctrl: amd: Don't show `Invalid config param` errors
- usb: typec: tcpci: move tcpci.h to include/linux/usb/
- usb: typec: tcpci: clear the fault status bit
- Linux 5.15.131
  * Jammy update: v5.15.130 upstream stable release (LP: #2039608)
- ACPI: thermal: Drop nocrt parameter
- module: Expose module_init_layout_section()
- arm64: module-plts: inline linux/moduleloader.h
- arm64: module: Use module_init_layout_section() to spot init sections
- ARM: module: Use module_init_layou

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

This bug was fixed in the package linux-bluefield - 5.4.0-1076.82

---
linux-bluefield (5.4.0-1076.82) focal; urgency=medium

  * focal/linux-bluefield: 5.4.0-1076.82 -proposed tracker (LP:
#2041621)

  * pwr-mlxbf: Several bug fixes for focal (LP: #2041996)
- SAUCE: Fix race condition between loading pwr-mlxbf.c and gpio-mlxbf2.c
  drivers
- SAUCE: pwr-mlxbf.c: rmmod results in kernel panic due to access to NULL
  pointer
- SAUCE: pwr-mlxbf: support graceful reboot instead of soft reset

  [ Ubuntu: 5.4.0-169.187 ]

  * focal/linux: 5.4.0-169.187 -proposed tracker (LP: #2044375)
  * USB bus error after upgrading to proposed kernel on lunar, jammy and focal
(LP: #2043197)
- USB: core: Fix oversight in SuperSpeed initialization
  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
- [Packaging] resync update-dkms-versions helper
- [Packaging] update annotations scripts

  [ Ubuntu: 5.4.0-168.186 ]

  * focal/linux: 5.4.0-168.186 -proposed tracker (LP: #2041652)
  * Focal update: v5.4.257 upstream stable release (LP: #2040284)
- erofs: ensure that the post-EOF tails are all zeroed
- ARM: pxa: remove use of symbol_get()
- mmc: au1xmmc: force non-modular build and remove symbol_get usage
- net: enetc: use EXPORT_SYMBOL_GPL for enetc_phc_index
- rtc: ds1685: use EXPORT_SYMBOL_GPL for ds1685_rtc_poweroff
- modules: only allow symbol_get of EXPORT_SYMBOL_GPL modules
- USB: serial: option: add Quectel EM05G variant (0x030e)
- USB: serial: option: add FOXCONN T99W368/T99W373 product
- HID: wacom: remove the battery when the EKR is off
- staging: rtl8712: fix race condition
- Bluetooth: btsdio: fix use after free bug in btsdio_remove due to race
  condition
- serial: sc16is7xx: fix bug when first setting GPIO direction
- firmware: stratix10-svc: Fix an NULL vs IS_ERR() bug in probe
- fsi: master-ast-cf: Add MODULE_FIRMWARE macro
- nilfs2: fix general protection fault in nilfs_lookup_dirty_data_buffers()
- nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse
- pinctrl: amd: Don't show `Invalid config param` errors
- 9p: virtio: make sure 'offs' is initialized in zc_request
- ASoC: da7219: Flush pending AAD IRQ when suspending
- ASoC: da7219: Check for failure reading AAD IRQ events
- ethernet: atheros: fix return value check in atl1c_tso_csum()
- vxlan: generalize vxlan_parse_gpe_hdr and remove unused args
- m68k: Fix invalid .section syntax
- s390/dasd: use correct number of retries for ERP requests
- s390/dasd: fix hanging device after request requeue
- fs/nls: make load_nls() take a const parameter
- ASoc: codecs: ES8316: Fix DMIC config
- ASoC: atmel: Fix the 8K sample parameter in I2SC master
- platform/x86: intel: hid: Always call BTNL ACPI method
- platform/x86: huawei-wmi: Silence ambient light sensor
- security: keys: perform capable check only on privileged operations
- clk: fixed-mmio: make COMMON_CLK_FIXED_MMIO depend on HAS_IOMEM
- net: usb: qmi_wwan: add Quectel EM05GV2
- idmaengine: make FSL_EDMA and INTEL_IDMA64 depends on HAS_IOMEM
- scsi: qedi: Fix potential deadlock on &qedi_percpu->p_work_lock
- netlabel: fix shift wrapping bug in netlbl_catmap_setlong()
- bnx2x: fix page fault following EEH recovery
- sctp: handle invalid error codes without calling BUG()
- cifs: add a warning when the in-flight count goes negative
- scsi: storvsc: Always set no_report_opcodes
- ALSA: seq: oss: Fix racy open/close of MIDI devices
- platform/mellanox: Fix mlxbf-tmfifo not handling all virtio CONSOLE
  notifications
- powerpc/32s: Fix assembler warning about r0
- udf: Check consistency of Space Bitmap Descriptor
- udf: Handle error when adding extent to a file
- Revert "net: macsec: preserve ingress frame ordering"
- reiserfs: Check the return value from __getblk()
- eventfd: Export eventfd_ctx_do_read()
- eventfd: prevent underflow for eventfd semaphores
- new helper: lookup_positive_unlocked()
- fs: Fix error checking for d_hash_and_lookup()
- tmpfs: verify {g,u}id mount options correctly
- OPP: Fix passing 0 to PTR_ERR in _opp_attach_genpd()
- x86/asm: Make more symbols local
- x86/boot: Annotate local functions
- x86/decompressor: Don't rely on upper 32 bits of GPRs being preserved
- perf/imx_ddr: don't enable counter0 if none of 4 counters are used
- cpufreq: powernow-k8: Use related_cpus instead of cpus in driver.exit()
- bpf: Clear the probe_addr for uprobe
- tcp: tcp_enter_quickack_mode() should be static
- regmap: rbtree: Use alloc_flags for memory allocations
- spi: tegra20-sflash: fix to check return value of platform_get_irq() in
  tegra_sflash_probe()
- can: gs_usb: gs_usb_receive_bulk_callback(): count RX overflow errors also
  in case of OOM
- wif

[Kernel-packages] [Bug 2043197] Re: USB bus error after upgrading to proposed kernel on lunar, jammy and focal

This bug was fixed in the package linux - 5.15.0-91.101

---
linux (5.15.0-91.101) jammy; urgency=medium

  * jammy/linux: 5.15.0-91.101 -proposed tracker (LP: #2043452)

  * USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix oversight in SuperSpeed initialization

linux (5.15.0-90.100) jammy; urgency=medium

  * jammy/linux: 5.15.0-90.100 -proposed tracker (LP: #2041603)

  * CVE-2023-25775
- RDMA/irdma: Remove irdma_uk_mw_bind()
- RDMA/irdma: Remove irdma_sc_send_lsmm_nostag()
- RDMA/irdma: Remove irdma_cqp_up_map_cmd()
- RDMA/irdma: Remove irdma_get_hw_addr()
- RDMA/irdma: Make irdma_uk_cq_init() return a void
- RDMA/irdma: optimize rx path by removing unnecessary copy
- RDMA/irdma: Remove enum irdma_status_code
- RDMA/irdma: Remove excess error variables
- RDMA/irdma: Prevent zero-length STAG registration

  * CVE-2023-39189
- netfilter: nfnetlink_osf: avoid OOB read

  * SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes
(LP: #2039575)
- net/smc: Fix pos miscalculation in statistics

  * CVE-2023-45871
- igb: set max size RX buffer when store bad packet is enabled

  * CVE-2023-39193
- netfilter: xt_sctp: validate the flag_info count

  * CVE-2023-39192
- netfilter: xt_u32: validate user space input

  * CVE-2023-31085
- ubi: Refuse attaching if mtd's erasesize is 0

  * CVE-2023-5717
- perf: Disallow mis-matched inherited group reads

  * CVE-2023-5178
- nvmet-tcp: Fix a possible UAF in queue intialization setup

  * CVE-2023-5158
- vringh: don't use vringh_kiov_advance() in vringh_iov_xfer()

  * [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module
(LP: #2033406)
- [Packaging] Make WWAN driver loadable modules

  * HP ProBook 450 G8 Notebook fail to wifi test (LP: #2037513)
- iwlwifi: mvm: Don't fail if PPAG isn't supported
- wifi: iwlwifi: fw: skip PPAG for JF

  * usbip: error: failed to open /usr/share/hwdata//usb.ids (LP: #2039439)
- [Packaging] Make linux-tools-common depend on hwdata

  * scripts/pahole-flags.sh change return to exit 0 (LP: #2035123)
- SAUCE: scripts/pahole-flags.sh change return to exit 0

  * Unable to use nvme drive to install Ubuntu 23.10 (LP: #2040157)
- misc: rtsx: Fix some platforms can not boot and move the l1ss judgment to
  probe

  * Jammy update: v5.15.131 upstream stable release (LP: #2039610)
- erofs: ensure that the post-EOF tails are all zeroed
- ksmbd: fix wrong DataOffset validation of create context
- ksmbd: replace one-element array with flex-array member in struct
  smb2_ea_info
- ARM: pxa: remove use of symbol_get()
- mmc: au1xmmc: force non-modular build and remove symbol_get usage
- net: enetc: use EXPORT_SYMBOL_GPL for enetc_phc_index
- rtc: ds1685: use EXPORT_SYMBOL_GPL for ds1685_rtc_poweroff
- modules: only allow symbol_get of EXPORT_SYMBOL_GPL modules
- USB: serial: option: add Quectel EM05G variant (0x030e)
- USB: serial: option: add FOXCONN T99W368/T99W373 product
- ALSA: usb-audio: Fix init call orders for UAC1
- usb: dwc3: meson-g12a: do post init to fix broken usb after resumption
- usb: chipidea: imx: improve logic if samsung,picophy-* parameter is 0
- HID: wacom: remove the battery when the EKR is off
- staging: rtl8712: fix race condition
- Bluetooth: btsdio: fix use after free bug in btsdio_remove due to race
  condition
- wifi: mt76: mt7921: do not support one stream on secondary antenna only
- serial: qcom-geni: fix opp vote on shutdown
- serial: sc16is7xx: fix broken port 0 uart init
- serial: sc16is7xx: fix bug when first setting GPIO direction
- firmware: stratix10-svc: Fix an NULL vs IS_ERR() bug in probe
- fsi: master-ast-cf: Add MODULE_FIRMWARE macro
- tcpm: Avoid soft reset when partner does not support get_status
- nilfs2: fix general protection fault in nilfs_lookup_dirty_data_buffers()
- nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse
- pinctrl: amd: Don't show `Invalid config param` errors
- usb: typec: tcpci: move tcpci.h to include/linux/usb/
- usb: typec: tcpci: clear the fault status bit
- Linux 5.15.131

  * Jammy update: v5.15.130 upstream stable release (LP: #2039608)
- ACPI: thermal: Drop nocrt parameter
- module: Expose module_init_layout_section()
- arm64: module-plts: inline linux/moduleloader.h
- arm64: module: Use module_init_layout_section() to spot init sections
- ARM: module: Use module_init_layout_section() to spot init sections
- rcu: Prevent expedited GP from enabling tick on offline CPU
- rcu-tasks: Fix IPI failure handling in trc_wait_for_one_reader
- rcu-tasks: Wait for trc_read_check_handler() IPIs
- rcu-tasks: Add trc_inspect_reader() checks for exiting critical section
- Linux 5.15.130

  * CVE-2023-42754
-

[Kernel-packages] [Bug 2043197] Re: USB bus error after upgrading to proposed kernel on lunar, jammy and focal

This bug was fixed in the package linux - 5.4.0-169.187

---
linux (5.4.0-169.187) focal; urgency=medium

  * focal/linux: 5.4.0-169.187 -proposed tracker (LP: #2044375)

  * USB bus error after upgrading to proposed kernel on lunar, jammy and focal
(LP: #2043197)
- USB: core: Fix oversight in SuperSpeed initialization

  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
- [Packaging] resync update-dkms-versions helper
- [Packaging] update annotations scripts

linux (5.4.0-168.186) focal; urgency=medium

  * focal/linux: 5.4.0-168.186 -proposed tracker (LP: #2041652)

  * Focal update: v5.4.257 upstream stable release (LP: #2040284)
- erofs: ensure that the post-EOF tails are all zeroed
- ARM: pxa: remove use of symbol_get()
- mmc: au1xmmc: force non-modular build and remove symbol_get usage
- net: enetc: use EXPORT_SYMBOL_GPL for enetc_phc_index
- rtc: ds1685: use EXPORT_SYMBOL_GPL for ds1685_rtc_poweroff
- modules: only allow symbol_get of EXPORT_SYMBOL_GPL modules
- USB: serial: option: add Quectel EM05G variant (0x030e)
- USB: serial: option: add FOXCONN T99W368/T99W373 product
- HID: wacom: remove the battery when the EKR is off
- staging: rtl8712: fix race condition
- Bluetooth: btsdio: fix use after free bug in btsdio_remove due to race
  condition
- serial: sc16is7xx: fix bug when first setting GPIO direction
- firmware: stratix10-svc: Fix an NULL vs IS_ERR() bug in probe
- fsi: master-ast-cf: Add MODULE_FIRMWARE macro
- nilfs2: fix general protection fault in nilfs_lookup_dirty_data_buffers()
- nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse
- pinctrl: amd: Don't show `Invalid config param` errors
- 9p: virtio: make sure 'offs' is initialized in zc_request
- ASoC: da7219: Flush pending AAD IRQ when suspending
- ASoC: da7219: Check for failure reading AAD IRQ events
- ethernet: atheros: fix return value check in atl1c_tso_csum()
- vxlan: generalize vxlan_parse_gpe_hdr and remove unused args
- m68k: Fix invalid .section syntax
- s390/dasd: use correct number of retries for ERP requests
- s390/dasd: fix hanging device after request requeue
- fs/nls: make load_nls() take a const parameter
- ASoc: codecs: ES8316: Fix DMIC config
- ASoC: atmel: Fix the 8K sample parameter in I2SC master
- platform/x86: intel: hid: Always call BTNL ACPI method
- platform/x86: huawei-wmi: Silence ambient light sensor
- security: keys: perform capable check only on privileged operations
- clk: fixed-mmio: make COMMON_CLK_FIXED_MMIO depend on HAS_IOMEM
- net: usb: qmi_wwan: add Quectel EM05GV2
- idmaengine: make FSL_EDMA and INTEL_IDMA64 depends on HAS_IOMEM
- scsi: qedi: Fix potential deadlock on &qedi_percpu->p_work_lock
- netlabel: fix shift wrapping bug in netlbl_catmap_setlong()
- bnx2x: fix page fault following EEH recovery
- sctp: handle invalid error codes without calling BUG()
- cifs: add a warning when the in-flight count goes negative
- scsi: storvsc: Always set no_report_opcodes
- ALSA: seq: oss: Fix racy open/close of MIDI devices
- platform/mellanox: Fix mlxbf-tmfifo not handling all virtio CONSOLE
  notifications
- powerpc/32s: Fix assembler warning about r0
- udf: Check consistency of Space Bitmap Descriptor
- udf: Handle error when adding extent to a file
- Revert "net: macsec: preserve ingress frame ordering"
- reiserfs: Check the return value from __getblk()
- eventfd: Export eventfd_ctx_do_read()
- eventfd: prevent underflow for eventfd semaphores
- new helper: lookup_positive_unlocked()
- fs: Fix error checking for d_hash_and_lookup()
- tmpfs: verify {g,u}id mount options correctly
- OPP: Fix passing 0 to PTR_ERR in _opp_attach_genpd()
- x86/asm: Make more symbols local
- x86/boot: Annotate local functions
- x86/decompressor: Don't rely on upper 32 bits of GPRs being preserved
- perf/imx_ddr: don't enable counter0 if none of 4 counters are used
- cpufreq: powernow-k8: Use related_cpus instead of cpus in driver.exit()
- bpf: Clear the probe_addr for uprobe
- tcp: tcp_enter_quickack_mode() should be static
- regmap: rbtree: Use alloc_flags for memory allocations
- spi: tegra20-sflash: fix to check return value of platform_get_irq() in
  tegra_sflash_probe()
- can: gs_usb: gs_usb_receive_bulk_callback(): count RX overflow errors also
  in case of OOM
- wifi: mwifiex: Fix OOB and integer underflow when rx packets
- mwifiex: switch from 'pci_' to 'dma_' API
- wifi: mwifiex: fix error recovery in PCIE buffer descriptor management
- crypto: stm32 - Properly handle pm_runtime_get failing
- Bluetooth: nokia: fix value check in nokia_bluetooth_serdev_probe()
- crypto: caam - fix unchecked return value error
- hwrng: iproc-rng200 - use semicolons rat

[Kernel-packages] [Bug 1912935] Re: battery drain while notebook off / shutdown

2023-12-07 Thread Martien Lagerweij

Outcome of testing with your kernel 6.5.0-2007-oem:
1) with your kernel batttery drain is 8% in 4 days;
2) with Ubuntu 22.04 6.2.0-37 kernel also 8% in 4 days;
3) with power reset workaround (see #49 above) it is 2% in 4 days.
So my conclusion is that 6.5.0-2007-oem has same battery drain still.
Hope this helps you find a good solution.

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

Title:
  battery drain while notebook off / shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  my battery drains around 15 to 20 percent a day when shutdown on linux ubuntu.
  It is an HP notebook HP 15s-eq0355ng , Ryzen 5 3500U , Vega8 .

  Tested:

  - with ubuntu 20.04
  - Kernel 5.4, 5.8 (hwe) and the current mainline kernel 5.11 (rc4)
  - no usb devices are plugged in
  - no wake ob lan available
  - no USB power when off (checked with optical mouse)
  - no visible LEDs are on when shutdown

  I reinstalled window 10, when shutdown from windows there is no
  (visible) battery drain (or significantly lower).

  Linux is unusable on this device, if the battery drains in a short
  time to 0% percent. This cause battery damage ...

  ---

  Tested TLP with default settings and activated
  DEVICES_TO_DISABLE_ON_SHUTDOWN (bluetooth wifi wwan), same power
  consumption after shutdown.

  Same power consumption on 20.10 (Groovy Gorilla).

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  test953 F pulseaudio
   /dev/snd/controlC0:  test953 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-24 (0 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  MachineType: HP HP Laptop 15s-eq0xxx
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic 
root=UUID=17ad50f6-ec98-46b2-8c2e-c169f9baace8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-64-generic N/A
   linux-backports-modules-5.4.0-64-generic  N/A
   linux-firmware1.187.8
  Tags:  focal
  Uname: Linux 5.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.vendor: AMI
  dmi.bios.version: F.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86FD
  dmi.board.vendor: HP
  dmi.board.version: 99.40
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.30:bd11/18/2020:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.40:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15s-eq0xxx
  dmi.product.sku: 20T63EA#ABD
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912935/+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 2042568] Re: Azure - Kernel crashes when removing gpu from pci

2023-12-07 Thread Tim Gardner

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

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

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

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

Title:
  Azure - Kernel crashes when removing gpu from pci

Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Jammy:
  Fix Committed
Status in linux-azure source package in Lunar:
  Fix Committed

Bug description:
  [Description]

  On a VM on Azure with a Tesla gpu it was noticed that when removing
  the gpu from the pci the vm would crash. In case the nvidia drivers
  are loaded, the machine won't crash. Instead the removing process will
  hang and the machine will crash on reboot.

  This is related to bug [1].
  The bug reported in [1] regards another driver but the root cause is the same.
  It is still investigated whether this is a bug in pci, or it is a bug of 
various drivers on how they use pci.

  For this case we have identified that removing commit [2] prevents the
  kernel crashes.

  Azure has requested to revert this commit, at least for the time being.
  This commit is not in upstream, so it just need to be reverted from Ubuntu 
kernels.

  [Test Case]

  On an Azure vm with a gpu :

  # echo '1' > /sys/bus/pci/devices/0001:00:00.0/remove

  where '0001:00:00.0' the pci address of the gpu.
  The vm will crash.

  [Where things could go wrong]

  The commit to be reverted was included in a patchset to address lp
  bugs https://bugs.launchpad.net/bugs/2023071 and
  https://bugs.launchpad.net/bugs/2023594

  However this commit just reduces boot time and removing shall not introduce 
any regressions.
  Side effects will be increase in the boot time.

  [Other]

  Only Ubuntu azure kernels are affected :

  - Jammy 5.15
  - Lunar 6.2

  Focal is also affected since it's using 5.15 kernel.
  This commit does not appear in Mantic 6.5 kernel.

  [1] https://bugzilla.kernel.org/show_bug.cgi?id=215515
  [2] 
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/+git/jammy/commit/?h=Ubuntu-azure-5.15.0-1043.50&id=75af0c10b3703400890d314d1d91d25294234a81

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


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

[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs

https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2040181
updating mantic to 2.2.0 final is in mantic-proposed, and this bug here
is in mantic-unapproved.

Should we drop 2.2.0 from mantic-proposed in favor of this one here?

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

Title:
  Multiple data corruption issues in zfs

Status in zfs-linux package in Ubuntu:
  Fix Committed
Status in zfs-linux source package in Xenial:
  Confirmed
Status in zfs-linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Focal:
  Confirmed
Status in zfs-linux source package in Jammy:
  Confirmed
Status in zfs-linux source package in Lunar:
  Confirmed
Status in zfs-linux source package in Mantic:
  In Progress
Status in zfs-linux source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

   * Multiple data corruption issues have been identified and fixed in
  ZFS. Some of them, at varying real-life reproducibility frequency have
  been deterimed to affect very old zfs releases. Recommendation is to
  upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
  ensure users get other potentially related fixes and runtime tunables
  to possibly mitigate other bugs that are related and are being fixed
  upstream for future releases.

   * For jammy the 2.1.14 upgrade will bring HWE kernel support and also
  compatiblity/support for hardened kernel builds that mitigate SLS
  (straight-line-speculation).

  [ Test Plan ]

   * !!! Danger !!! use reproducer from
  https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
  and confirm if that issue is resolved or not. Do not run on production
  ZFS pools / systems.

   * autopkgtest pass (from https://ubuntu-archive-
  team.ubuntu.com/proposed-migration/ )

   * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )

   * kernel regression zfs testsuite pass (from Kernel team RT test
  results summary, private)

   * zsys integration test pass (upgrade of zsys installed systems for
  all releases)

   * zsys install test pass (for daily images of LTS releases only that
  have such installer support, as per iso tracker test case)

   * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
  2.1.14, and test LXD on these updated kernels)

  
  [ Where problems could occur ]

   * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will 
introduce slight slow down on amd64 (for hw accelerated assembly code-paths 
only in the encryption primitives)
   
   * Uncertain of the perfomance impact of the extra checks in dnat patch fix 
itself. Possibly affecting speed of operation, at the benefit of correctness.

  [ Other Info ]
   
   * https://github.com/openzfs/zfs/pull/15571 is most current consideration of 
affairs

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


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

[Kernel-packages] [Bug 2045855] Re: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: end of file on stdin at conffile prompt

2023-12-07 Thread Mark Esler

hi @yudamjoo o/

Please check the end of your `DpkgTerminalLog.txt` file.

To fix CVE-2023-45866 [0] a configuration file
(`/etc/bluetooth/input.conf`) was changed. If there had been edits made
to this file before updating BlueZ, apt will ask what you want to do
with the configuration file. "Y" is likely the right option if you do
not intend to have custom changes in `/etc/bluetooth/input.conf`.

Here's an example of me asking apt to show the config differences ("D") before 
accepting the new changes ("Y"):
```
$ sudo apt install bluez
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be upgraded:
  bluez
1 upgraded, 0 newly installed, 0 to remove and 157 not upgraded.
Need to get 1,106 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 https://redacted.launchpadcontent.net/ubuntu-security/ppa/ubuntu 
jammy/main amd64 bluez amd64 5.64-0ubuntu1.1 [1,106 kB]
Fetched 1,106 kB in 1s (884 kB/s)
(Reading database ... 161840 files and directories currently installed.)
Preparing to unpack .../bluez_5.64-0ubuntu1.1_amd64.deb ...
Unpacking bluez (5.64-0ubuntu1.1) over (5.64-0ubuntu1) ...
Setting up bluez (5.64-0ubuntu1.1) ...

Configuration file '/etc/bluetooth/input.conf'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
Y or I  : install the package maintainer's version
N or O  : keep your currently-installed version
  D : show the differences between the versions
  Z : start a shell to examine the situation
 The default action is to keep your current version.
*** input.conf (Y/I/N/O/D/Z) [default=N] ? D
--- /etc/bluetooth/input.conf   2023-03-21 08:04:20.023928226 -0500
+++ /etc/bluetooth/input.conf.dpkg-new  2023-11-29 05:31:28.0 -0600
@@ -17,8 +17,8 @@
 # platforms may want to make sure that input connections only come from bonded
 # device connections. Several older mice have been known for not supporting
 # pairing/encryption.
-# Defaults to false to maximize device compatibility.
-ClassicBondedOnly=true
+# Defaults to true for security.
+#ClassicBondedOnly=true
 
 # LE upgrade security
 # Enables upgrades of security automatically if required.

Configuration file '/etc/bluetooth/input.conf'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
Y or I  : install the package maintainer's version
N or O  : keep your currently-installed version
  D : show the differences between the versions
  Z : start a shell to examine the situation
 The default action is to keep your current version.
*** input.conf (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/bluetooth/input.conf ...
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for dbus (1.12.20-2ubuntu4.1) ...
```

[0] https://ubuntu.com/security/notices/USN-6540-1

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

** Information type changed from Private Security to Public

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

Title:
  package bluez 5.64-0ubuntu1.1 failed to install/upgrade: end of file
  on stdin at conffile prompt

Status in bluez package in Ubuntu:
  New

Bug description:
  I did not recognized the error.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: bluez 5.64-0ubuntu1.1
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  AptOrdering:
   bluez:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Dec  7 15:44:57 2023
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2021-01-30 (1040 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. OptiPlex 7010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic 
root=UUID=1aa27b2f-8d22-4b4e-931f-bd8e304ed0d4 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.10, Python 3.10.12, unpackaged
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.11
  SourcePackage: bluez
  Title: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: end of file 
on stdin at conffile prompt
  UpgradeStatus: Upgraded to jammy on 2023-03-28 (253 days ago)
  dmi.bios.date: 03/25/2013
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0GY6Y8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.

[Kernel-packages] [Bug 2045919] [NEW] mlxbf-bootctl: fails to report info about cards using dev keys

2023-12-07 Thread David Thompson

Public bug reported:

SRU Justification:

[Impact]

There is a gap in the mlxbf-bootctl driver logic, resulting in failure to
report when a secure boot enabled card is using development keys. The program
will instead report lifecycle state as "GA Secured" which is misleading.

[Fix]

Bring in the following upstream commit from linux-next:
  "mlxbf-bootctl: correctly identify secure boot with development keys"

[Test Case]

Enable secure boot on a BF3 card that is using development keys
Login as root on BF3
Run the command "mlxbf-bootctl"
Verify that the "lifecycle state" row shows "Secured (development)"

[Regression Potential]

Low risk change, cherry pick of upstream approved commit

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

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

Title:
  mlxbf-bootctl: fails to report info about cards using dev keys

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  SRU Justification:

  [Impact]

  There is a gap in the mlxbf-bootctl driver logic, resulting in failure to
  report when a secure boot enabled card is using development keys. The program
  will instead report lifecycle state as "GA Secured" which is misleading.

  [Fix]

  Bring in the following upstream commit from linux-next:
"mlxbf-bootctl: correctly identify secure boot with development keys"

  [Test Case]

  Enable secure boot on a BF3 card that is using development keys
  Login as root on BF3
  Run the command "mlxbf-bootctl"
  Verify that the "lifecycle state" row shows "Secured (development)"

  [Regression Potential]

  Low risk change, cherry pick of upstream approved commit

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


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

[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform

2023-12-07 Thread You-Sheng Yang

Attach a second proprosed revision of ipu6-drivers/mantic. Changes:
* removed v6.6 patches
* removed patch to build additional camera sensors that are not yet required 
for mantic.

** Patch added: 
"ipu6-drivers_0~git202310180730.3f813580-0ubuntu0.23.10.1~exp.3.debdiff"
   
https://bugs.launchpad.net/ubuntu/mantic/+source/ipu6-drivers/+bug/2031412/+attachment/5727334/+files/ipu6-drivers_0~git202310180730.3f813580-0ubuntu0.23.10.1~exp.3.debdiff

** Patch removed: 
"ipu6-drivers_0~git202310180730.3f813580-0ubuntu0.23.10.1~exp.1.debdiff"
   
https://bugs.launchpad.net/ubuntu/mantic/+source/ipu6-drivers/+bug/2031412/+attachment/5717464/+files/ipu6-drivers_0~git202310180730.3f813580-0ubuntu0.23.10.1~exp.1.debdiff

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

Title:
  Support mipi camera on Intel Meteor Lake platform

Status in HWE Next:
  New
Status in ipu6-drivers package in Ubuntu:
  Fix Released
Status in ivsc-driver package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Jammy:
  Won't Fix
Status in ivsc-driver source package in Jammy:
  Won't Fix
Status in linux source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in ipu6-drivers source package in Mantic:
  In Progress
Status in ivsc-driver source package in Mantic:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in ipu6-drivers source package in Noble:
  Fix Released
Status in ivsc-driver source package in Noble:
  Fix Released
Status in linux source package in Noble:
  Triaged
Status in linux-firmware source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justification]

  == ipu6-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  Based on upstream tag
  https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019,
  and an additional patch to enable/fix compilation of additional sensor
  modules.

  [Test Case]

  This is verified on MTL Lattice and VSC platforms, as well as previous
  generations e.g. TGL and ADL.

  To actually verify the camera framework:
  ```
  # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14
  # reboot into the 6.5.0-14.14 kernel
  $ sudo apt install intel-ipu6-dkms intel-vsc-dkms
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, 
and their dependencies, are fetched from the oem-solutions-group PPA. 
Everything else must come from the mantic archive.

  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  This is a new platform. We've been verifying its functions and features, and
  are still polishing it.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == ivsc-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform. Need both
  firmware and driver change to probe the hardware correctly.

  [Fix]

  4 commits from the latest trunk branch on upstream repository
  https://github.com/intel/ivsc-driver.

  [Test Case]

  With all other changes in position, Intel VSC driver modules are to be
  loaded as a soft dependency of some selected camera sensor modules.
  LJCA modules should be loaded automatically on MTL platforms as well.

  To actually verify the camera framework:
  ```
  # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14
  # reboot into the 6.5.0-14.14 kernel
  $ sudo apt install intel-ipu6-dkms intel-vsc-dkms
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, 
and their dependencies, are fetched from the oem-solutions-group PPA. 
Everything else must come from the mantic archive.

  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  While it changes how LJCA modules match from ACPI ID, it's also tested
  and verified on previous generations using IVSC, e.g. TGL, ADL.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and ye

[Kernel-packages] [Bug 2040181] Re: upgrade zfs-linux to 2.2.0 final

2023-12-07 Thread Mauricio Faria de Oliveira

Hi Dimitri,

Thanks for the details of the test plan execution!

That covers the kernel module/filesystem code quite well, thanks,
and there's the userspace tooling changes left, as you mentioned.

> In practice this SRU is already released to most users via LXD and via kernel 
> upgrades. 
> The change this sru release will introduce is userspace tooling update, which 
> was minor in this update.

I looked up the changes to userspace commands (in subdir `zfs/cmd/`),
and would agree they are (mostly) minor, with a few notes to have
documented (and for others to review), but IMHO, none are blocking
for the release of this SRU.

cheers,
Mauricio

Related commits:

$ git log --oneline zfs-2.2.0-rc3..zfs-2.2.0 -- cmd/
33d7c2d165c2 import: require force when cachefile hostid doesn't match 
on-disk
8015e2ea66b4 Add '-u' - nomount flag for zfs set
c53bc3837cb6 Improve the handling of sharesmb,sharenfs properties
e9dc31c74e7b Update the behavior of mountpoint property
608741d062fe Report ashift of L2ARC devices in zdb
0ce1b2ca1930 Invoke zdb by guid to avoid import errors
0aabd6b48228 ZIL: Avoid dbuf_read() in ztest_get_data()
3af63683fe07 cmd: add 'help' subcommand to zpool and zfs
9aa1a2878ea9 Fix incorrect expected error in ztest
54c6fbd378ea zed: Allow autoreplace and fault LEDs for removed vdevs
32949f2560bf Relax error reporting in zpool import and zpool split
63159e5bda1c checkstyle: fix action failures
e99e684b337b zed: update zed.d/statechange-slot_off.sh
d19304ffeec5 zed: Add zedlet to power off slot when drive is faulted
df8c9f351dab ZIL: Second attempt to reduce scope of zl_issuer_lock.
12f2b1f65e91 zdb: include cloned blocks in block statistics

Spotted changes/commits:

1) Config option with typo

commit d19304ffeec50ebc02cf4496c14e8945c74fb76a
Author: Tony Hutter 
Date:   Thu Aug 24 11:59:03 2023 -0700

zed: Add zedlet to power off slot when drive is faulted

If ZED_POWER_OFF_ENCLOUSRE_SLOT_ON_FAULT is enabled in zed.rc, then
power off the drive's slot in the enclosure if it becomes FAULTED.
This can help silence misbehaving drives.  This assumes your drive
enclosure fully supports slot power control via sysfs.

This new option is disabled by default, good.
However, the option has a typo, so I submitted patch [1] upstream,
and it would be nice if we pick it up later on.

[1] https://github.com/openzfs/zfs/pull/15651

...

2) zpool import/split no longer reflect errors to mount/share

commit 32949f2560bf35ec86dfa5d984514908e0eb3ecc
Author: Umer Saleem 
Date:   Sat Sep 2 05:25:11 2023 +0500

Relax error reporting in zpool import and zpool split

For zpool import and zpool split, zpool_enable_datasets is called
to mount and share all datasets in a pool. If there is an error
while mounting or sharing any dataset in the pool, the status of
import or split is reported as failure. However, the changes do
show up in zpool list.

This commit updates the error reporting in zpool import and zpool
split path. More descriptive messages are shown to user in case
there is an error during mount or share. Errors in mount or share
do not effect the overall status of zpool import and zpool split.

...

3) zed can now autoreplace vdevs marked as REMOVED

This change is effective by default, since zed/config option are.

commit 54c6fbd378eaa402eff34acf6a91c02d6cf9da11
Author: Tony Hutter 
Date:   Mon Sep 18 16:25:58 2023 -0700

zed: Allow autoreplace and fault LEDs for removed vdevs

Allow zed to autoreplace vdevs marked as REMOVED.  Also update
statechange-led zedlet to toggle fault LEDs for REMOVED vdevs.

Reviewed-by: Brian Behlendorf 
Signed-off-by: Tony Hutter 
Closes #15281

See,

$ git show 
54c6fbd378eaa402eff34acf6a91c02d6cf9da11:cmd/zed/zed.d/statechange-led.sh | 
grep 'if .*ZED'
if [ "${ZED_USE_ENCLOSURE_LEDS}" != "1" ] ; then

$ sudo apt update && sudo apt install -y zfsutils-linux

$ systemctl status zfs-zed.service | grep Active:
 Active: active (running) ...

$ grep ZED_USE_ENCLOSURE_LEDS /etc/zfs/zed.d/zed.rc
ZED_USE_ENCLOSURE_LEDS=1

...

4) Changes to mountpoint property handling / remounting

This is a behavior change, but it looks like a good/consistent one,
adopted by upstream between RC and Release time, so it seems worse
to diverge from upstream when we do a similar RC to Release update.

And in case of impact to particular users/scripts/scenarios, there
is a new option to fall back to previous behavior.

commit e9dc31c74e7b28a0cb2a321bc220074f6461d231
Author: Umer Saleem 
Date:   Tue Sep 5 13:27:53 2023 +0500

Update the behavior of mountpoint property

...

To make the behavior consistent in case dataset is mounted or
unmounted, we should try to mount the dataset whenever mountpoint
property is updated. This would result in

[Kernel-packages] [Bug 2045913] [NEW] Update the NVIDIA 535 driver

2023-12-07 Thread Alberto Milone

Public bug reported:

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

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

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

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

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

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

[Discussion]

[Changelog]

** Affects: nvidia-graphics-drivers-525 (Ubuntu)
 Importance: High
 Assignee: Alberto Milone (albertomilone)
 Status: In Progress

** Changed in: nvidia-graphics-drivers-525 (Ubuntu)
   Importance: Undecided => High

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

Title:
  Update the NVIDIA 535 driver

Status in nvidia-graphics-drivers-525 package in Ubuntu:
  In Progress

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

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

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

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

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

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

  [Discussion]

  [Changelog]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-525/+bug/2045913/+subscriptions


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

[Kernel-packages] [Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

2023-12-07 Thread Andre Ruiz

Yeah, I knew about that 4.30 update in Intel website, but it is not present on 
Dell tools yet and the customer did not want to void their warranty 
(potentially), so I did not try it. That is something to keep in mind while we 
debug it.

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

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

Status in linux package in Ubuntu:
  Confirmed

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

  Details:

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

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

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

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

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

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

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

  - the switch does log that the bond is flapping
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 12 20:05 seq
   crw-rw 1 root audio 116, 33 Sep 12 20:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-22 (24 days ago)
  InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release 
amd64 (20230810)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7515
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 mgag200drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-83-generic 
root=UUID=cfb5f171-77e6-4fcd-947b-52901f51b26a ro
  ProcVersionSignature: Ubuntu 5.15.0-83.92-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-83-generic N/A
   linux-backports-modules-5.15.0-83-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.18
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-83-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 07/27/2023
  dmi.bios.release: 2.12
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.12.4
  dmi.board.name: 0J91V2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.12.4:bd07/27/2023:br2.12:svnDellInc.:pnPowerEdgeR7515:pvr:rvnDellInc.:rn0J91V2:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=08FD;ModelName=PowerEdgeR7515:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7515
  dmi.product.sku: SKU=08FD;ModelName=PowerEdge R7515
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 15 03:13 seq
   crw-rw 1 root audio 116, 33 Sep 15 03:13 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: Cannot stat file /proc/215602/fd/10: Permission denied
   Cannot stat file /proc/323635/fd/10: Permission denied
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.3.4.7:5248/MAAS/metadata/)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Machine

[Kernel-packages] [Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

2023-12-07 Thread Bartosz Woronicz

@Andre,

I successfully installed on the machines with NVMUpdate64 tool. That is
on HPE machines.


$ sudo ./nvmupdate64e 

Intel(R) Ethernet NVM Update Tool
NVMUpdate version 1.39.56.8
Copyright(C) 2013 - 2023 Intel Corporation.


WARNING: To avoid damage to your device, do not stop the update or reboot or 
power off the system during this update.
Inventory in progress. Please wait [**+...]


Num Description  Ver.(hex)  DevId S:BStatus
=== ==  = == ==
01) Intel(R) Ethernet Network Adapter   4.48(4.30)   159B 00:016 Up to date
E810-XXV-2 
02) Intel(R) Ethernet Network Adapter N/A(N/A)   1521 00:072 Update not
I350-T4 for OCP NIC 3.0  available 


Tool execution completed with the following status: An error occurred accessing 
the device.
Press any key to exit.

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

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

Status in linux package in Ubuntu:
  Confirmed

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

  Details:

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 2045899] Re: More amdgpu crashes: pagefaults, ring timeouts and parser bugs

Waiting for 6.5.13 to actually build but on 6.6.0-14 from proposed now
which is based on 6.6.3 which probably has all the fancy patches too

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

Title:
  More amdgpu crashes: pagefaults, ring timeouts and parser bugs

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  New

Bug description:
  I think running the Mattermost snap forced to Wayland rendering
  *eventually* seems to crash amdgpu, it recovers at the kernel level
  but the GUI doesn't actually recover and I also can switch tty with
  the keyboard.

  I have attached the two crashes from yesterday, they look slightly
  different but may be the same cause:

  
  LastDmesg.txt contains the journalctl -k -b of the last failed boot, 
OlderDmesg.txt contains the same for the crash before that.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Thu Dec  7 13:09:42 2023
  InstallationDate: Installed on 2022-11-26 (376 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic 
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash zswap.enabled=1 
zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2023
  dmi.bios.release: 1.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R23ET71W (1.47 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21CF004PGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76538 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.28
  dmi.modalias: 
dmi:bvnLENOVO:bvrR23ET71W(1.47):bd09/14/2023:br1.47:efr1.28:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3:
  dmi.product.family: ThinkPad T14 Gen 3
  dmi.product.name: 21CF004PGE
  dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3
  dmi.product.version: ThinkPad T14 Gen 3
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045899/+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 2045899] Re: More amdgpu crashes: pagefaults, ring timeouts and parser bugs

2023-12-07 Thread Timo Aaltonen

please try a later point release mainline kernel:

https://kernel.ubuntu.com/mainline/v6.5.13/

which is also the last one for 6.5

** 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/2045899

Title:
  More amdgpu crashes: pagefaults, ring timeouts and parser bugs

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  New

Bug description:
  I think running the Mattermost snap forced to Wayland rendering
  *eventually* seems to crash amdgpu, it recovers at the kernel level
  but the GUI doesn't actually recover and I also can switch tty with
  the keyboard.

  I have attached the two crashes from yesterday, they look slightly
  different but may be the same cause:

  
  LastDmesg.txt contains the journalctl -k -b of the last failed boot, 
OlderDmesg.txt contains the same for the crash before that.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Thu Dec  7 13:09:42 2023
  InstallationDate: Installed on 2022-11-26 (376 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic 
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash zswap.enabled=1 
zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2023
  dmi.bios.release: 1.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R23ET71W (1.47 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21CF004PGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76538 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.28
  dmi.modalias: 
dmi:bvnLENOVO:bvrR23ET71W(1.47):bd09/14/2023:br1.47:efr1.28:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3:
  dmi.product.family: ThinkPad T14 Gen 3
  dmi.product.name: 21CF004PGE
  dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3
  dmi.product.version: ThinkPad T14 Gen 3
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045899/+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 2045899] Re: More amdgpu crashes: pagefaults, ring timeouts and parser bugs

These ones I don't remember seeing before:

[drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

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

Title:
  More amdgpu crashes: pagefaults, ring timeouts and parser bugs

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  New

Bug description:
  I think running the Mattermost snap forced to Wayland rendering
  *eventually* seems to crash amdgpu, it recovers at the kernel level
  but the GUI doesn't actually recover and I also can switch tty with
  the keyboard.

  I have attached the two crashes from yesterday, they look slightly
  different but may be the same cause:

  
  LastDmesg.txt contains the journalctl -k -b of the last failed boot, 
OlderDmesg.txt contains the same for the crash before that.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Thu Dec  7 13:09:42 2023
  InstallationDate: Installed on 2022-11-26 (376 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic 
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash zswap.enabled=1 
zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2023
  dmi.bios.release: 1.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R23ET71W (1.47 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21CF004PGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76538 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.28
  dmi.modalias: 
dmi:bvnLENOVO:bvrR23ET71W(1.47):bd09/14/2023:br1.47:efr1.28:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3:
  dmi.product.family: ThinkPad T14 Gen 3
  dmi.product.name: 21CF004PGE
  dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3
  dmi.product.version: ThinkPad T14 Gen 3
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045899/+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 2044131] Re: i915 regression introduced with 5.5 kernel

2023-12-07 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  i915 regression introduced with 5.5 kernel

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  New
Status in linux source package in Focal:
  New
Status in linux source package in Jammy:
  New
Status in linux source package in Mantic:
  New
Status in linux source package in Noble:
  New

Bug description:
  [ Impact ]
  Commit 8f4b1068e7fc3df1a77ac8151767e56b208cc87f introduced some timing checks 
which have been proven invalid for at least some hardware setups. A user trying 
to run Focal with HWE 5.15 kernel is not able to get any video output.
  After going through bisection between 5.4 and 5.5 this commit was identified. 
Reverting it on top of Focal HWE kernel fixes the issue.

  The issue has been addressed upstream in DRM tree
  (20c2dbff342aec13bf93c2f6c951da198916a455) and has been merge into
  linux-next (e0ef2daa8ca8ce4dbc2fd0959e383b753a87fd7d).

  dmesg and lspci from the affected configuration are attached to this
  bug.

  [ Test Plan ]
  1. Boot the affected hardware with Ubuntu desktop running kernel v5.5 or 
higher.
  2. Wait until boot finishes and see the blank screen.

  Actual result: there is no video output visible.
  Expected result: normal boot process should be visible (e.g. splash), then 
GUI should appear.

  [ Where problem could occur ]
  This bug was a result of assumptions in the checks that turned out to be not 
valid for some hardware. The checks were removed from global intel_mode_valid 
function and moved into connector specific .mode_valid() hooks, entirely 
skiping BXT/GLK DSI connectors.

  This should keep the checks where appropriate and skip for hardware
  that does not comply to them.

  [ Other info ]

  Original bug description:

  There is a regression preventing a user to upgrade from 5.4 kernel to 
anything that's higher than 5.5. When using such kernel the image orientation 
is wrong (rotated by 90°C). Also the kernel log contains:
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Unknown revid 0x06
  wrz 15 09:19:49 desktop kernel: rtw_8821ce :01:00.0: Firmware version 
24.8.0, H2C version 12
  wrz 15 09:19:49 desktop kernel: Console: switching to colour dummy device 
80x25
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: deactivate vga 
console
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] couldn't get memory 
information
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: changed VGA 
decodes: olddecodes=io+mem,decodes=io+mem:o>
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Finished loading DMC 
firmware i915/glk_dmc_ver1_04.bin (v>
  wrz 15 09:19:49 desktop kernel: 

  wrz 15 09:19:49 desktop kernel: UBSAN: array-index-out-of-bounds in 
/build/linux-hwe-5.15-DZkSuT/linux-hwe-5.15-5.>
  wrz 15 09:19:49 desktop kernel: index 5 is out of range for type 'u32 [5]'

  (full stack trace attached)

  The video hardware in use is:
  00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 605 
[8086:3185] (rev 06) (prog-if 00 [VGA controller])
  (...)
  Kernel driver in use: i915
  Kernel modules: i915

  The user wanted to upgrade from bionic to focal with HWE kernel (they
  needed it due to some networking hardware they wanted to have
  supported by the newer kernel).

  The user was testing mainline stable kernels and noticed that the last
  working kernel was the 5.4 series, while anything starting from 5.5
  and above is BROKEN (symptoms as described in the first paragraph
  above).

  Together with the user we have run a bisection between v5.4 and v5.5 on the 
upstream stable kernel and we were able to identify the first broken commit to 
be:
  8f4b1068e7fc3df1a77ac8151767e56b208cc87f drm/i915: Check some transcoder 
timing minimum limits

  To confirm I have reverted this change on top of the HWE kernel for
  focal and the user have confirmed that this resolved the issue (test
  build available at ppa:dgadomski/kernel-sf368743).

  I am not fully sure what the purpose of this patch was, but I assume
  the regression was not intended and the hardware should be still
  supported.

  Attaching lshw and lspci output.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2044131/+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 2045899] Re: More amdgpu crashes: pagefaults, ring timeouts and parser bugs

I saw similar messages in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032386 but that
only caused hangs and not block the entire desktop (and Firefox is good
now so I don't know)

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

Title:
  More amdgpu crashes: pagefaults, ring timeouts and parser bugs

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  New

Bug description:
  I think running the Mattermost snap forced to Wayland rendering
  *eventually* seems to crash amdgpu, it recovers at the kernel level
  but the GUI doesn't actually recover and I also can switch tty with
  the keyboard.

  I have attached the two crashes from yesterday, they look slightly
  different but may be the same cause:

  
  LastDmesg.txt contains the journalctl -k -b of the last failed boot, 
OlderDmesg.txt contains the same for the crash before that.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Thu Dec  7 13:09:42 2023
  InstallationDate: Installed on 2022-11-26 (376 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic 
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash zswap.enabled=1 
zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2023
  dmi.bios.release: 1.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R23ET71W (1.47 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21CF004PGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76538 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.28
  dmi.modalias: 
dmi:bvnLENOVO:bvrR23ET71W(1.47):bd09/14/2023:br1.47:efr1.28:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3:
  dmi.product.family: ThinkPad T14 Gen 3
  dmi.product.name: 21CF004PGE
  dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3
  dmi.product.version: ThinkPad T14 Gen 3
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045899/+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 2045899] Re: More amdgpu crashes: pagefaults, ring timeouts and parser bugs

** Attachment added: "OlderDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045899/+attachment/5727266/+files/OlderDmesg.txt

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

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

Title:
  More amdgpu crashes: pagefaults, ring timeouts and parser bugs

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  New

Bug description:
  I think running the Mattermost snap forced to Wayland rendering
  *eventually* seems to crash amdgpu, it recovers at the kernel level
  but the GUI doesn't actually recover and I also can switch tty with
  the keyboard.

  I have attached the two crashes from yesterday, they look slightly
  different but may be the same cause:

  
  LastDmesg.txt contains the journalctl -k -b of the last failed boot, 
OlderDmesg.txt contains the same for the crash before that.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Thu Dec  7 13:09:42 2023
  InstallationDate: Installed on 2022-11-26 (376 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic 
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash zswap.enabled=1 
zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2023
  dmi.bios.release: 1.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R23ET71W (1.47 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21CF004PGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76538 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.28
  dmi.modalias: 
dmi:bvnLENOVO:bvrR23ET71W(1.47):bd09/14/2023:br1.47:efr1.28:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3:
  dmi.product.family: ThinkPad T14 Gen 3
  dmi.product.name: 21CF004PGE
  dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3
  dmi.product.version: ThinkPad T14 Gen 3
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045899/+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 2045899] [NEW] More amdgpu crashes: pagefaults, ring timeouts and parser bugs

Public bug reported:

I think running the Mattermost snap forced to Wayland rendering
*eventually* seems to crash amdgpu, it recovers at the kernel level but
the GUI doesn't actually recover and I also can switch tty with the
keyboard.

I have attached the two crashes from yesterday, they look slightly
different but may be the same cause:


LastDmesg.txt contains the journalctl -k -b of the last failed boot, 
OlderDmesg.txt contains the same for the crash before that.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.5.0-14-generic 6.5.0-14.14
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Thu Dec  7 13:09:42 2023
InstallationDate: Installed on 2022-11-26 (376 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic 
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash zswap.enabled=1 
zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc 
vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-6.5.0-14-generic N/A
 linux-backports-modules-6.5.0-14-generic  N/A
 linux-firmware20230919.git3672ccab-0ubuntu2.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/14/2023
dmi.bios.release: 1.47
dmi.bios.vendor: LENOVO
dmi.bios.version: R23ET71W (1.47 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21CF004PGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76538 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.28
dmi.modalias: 
dmi:bvnLENOVO:bvrR23ET71W(1.47):bd09/14/2023:br1.47:efr1.28:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3:
dmi.product.family: ThinkPad T14 Gen 3
dmi.product.name: 21CF004PGE
dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3
dmi.product.version: ThinkPad T14 Gen 3
dmi.sys.vendor: LENOVO

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

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


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

** Attachment added: "LastDmesg.txt"
   
https://bugs.launchpad.net/bugs/2045899/+attachment/5727244/+files/LastDmesg.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/2045899

Title:
  More amdgpu crashes: pagefaults, ring timeouts and parser bugs

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  New

Bug description:
  I think running the Mattermost snap forced to Wayland rendering
  *eventually* seems to crash amdgpu, it recovers at the kernel level
  but the GUI doesn't actually recover and I also can switch tty with
  the keyboard.

  I have attached the two crashes from yesterday, they look slightly
  different but may be the same cause:

  
  LastDmesg.txt contains the journalctl -k -b of the last failed boot, 
OlderDmesg.txt contains the same for the crash before that.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Thu Dec  7 13:09:42 2023
  InstallationDate: Installed on 2022-11-26 (376 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic 
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash zswap.enabled=1 
zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2023
  dmi.bios.release: 1.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R23ET71W (1.47 )
  dmi.board.asset.tag: Not

[Kernel-packages] [Bug 2045754] Re: [Arc A770] Graphics card driver crash

2023-12-07 Thread Pepijn de Vos

Same thing happened again today, but this time it fully crashed the PC
after a few seconds of flickering.

I'll keep an eye on if it also happens in Arch Linux or Windows.

** Attachment added: "dmesg-gpu2-txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045754/+attachment/5727221/+files/dmesg-gpu2-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/2045754

Title:
  [Arc A770] Graphics card driver crash

Status in linux package in Ubuntu:
  New

Bug description:
  I was just browsing the web when the bottom half of the display became black, 
the cursor froze, and everything started flickering.
  I think eventually KDE crashed and some terminal messages were shown.

  I Ctrl+alt+f3 to a terminal and shut down from there.
  The terminal was glitchy with random artifacts but visible.

  After reboot everything is working again for now.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Dec  6 12:03:24 2023
  DistUpgraded: 2023-11-06 09:55:34,023 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation DG2 [Arc A770] [8086:56a0] (rev 08) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation DG2 [Arc A770] [8086:1020]
  InstallationDate: Installed on 2022-10-30 (402 days ago)
  InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=bcf965e4-1a60-42fe-8033-214524d1908b ro quiet 
cryptdevice=UUID=66cc3c7b-e0bd-4535-b634-d56226dd88f1:luks-66cc3c7b-e0bd-4535-b634-d56226dd88f1
 root=/dev/mapper/luks-66cc3c7b-e0bd-4535-b634-d56226dd88f1 splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to mantic on 2023-11-06 (30 days ago)
  dmi.bios.date: 05/18/2023
  dmi.bios.release: 16.18
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1618
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING X670E-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1618:bd05/18/2023:br16.18:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX670E-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045754/+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 2039375] Re: Green screen

2023-12-07 Thread Joshua

I've got the same problem. I'm not sure that any sort of log collection
is impossible however, as the system doesn't crash until after GUI
login. I can switch to text only (ctrl-alt-F2) and login that way. A
crash report is saved when the crash occurs - I can collect some stuff
after rebooting. problem has persisted through next kernel releases, I'm
getting this with 5.15.0-89 now. See attached.

attaching crash info.

I'd have to say blueman-applet is not what I expected to see here.

** Attachment added: "Crash file generated for me with this green screen crash"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039375/+attachment/5727220/+files/_usr_bin_blueman-applet.1000.crash

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

Title:
Green screen

Status in linux package in Ubuntu:
Confirmed

Bug description:
This morning I did the kernel update that arrived yesterday. Now, after I
login I get a solid green screen and that's where it stays.
the upgrade took the machine from:
vmlinuz-5.15.0-84-generic
To:
vmlinuz-5.15.0-86-generic

I rebooted into 84-generic and everything worked correctly, as pre-
update.

See more :
https://forums.linuxmint.com/viewtopic.php?t=405203&e=1&view=unread#unread

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039375/+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 2044131] Re: i915 regression introduced with 5.5 kernel

2023-12-07 Thread Bug Watch Updater

** Changed in: linux
   Status: Unknown => 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/2044131

Title:
  i915 regression introduced with 5.5 kernel

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  New
Status in linux source package in Focal:
  New
Status in linux source package in Jammy:
  New
Status in linux source package in Mantic:
  New
Status in linux source package in Noble:
  New

Bug description:
  [ Impact ]
  Commit 8f4b1068e7fc3df1a77ac8151767e56b208cc87f introduced some timing checks 
which have been proven invalid for at least some hardware setups. A user trying 
to run Focal with HWE 5.15 kernel is not able to get any video output.
  After going through bisection between 5.4 and 5.5 this commit was identified. 
Reverting it on top of Focal HWE kernel fixes the issue.

  The issue has been addressed upstream in DRM tree
  (20c2dbff342aec13bf93c2f6c951da198916a455) and has been merge into
  linux-next (e0ef2daa8ca8ce4dbc2fd0959e383b753a87fd7d).

  dmesg and lspci from the affected configuration are attached to this
  bug.

  [ Test Plan ]
  1. Boot the affected hardware with Ubuntu desktop running kernel v5.5 or 
higher.
  2. Wait until boot finishes and see the blank screen.

  Actual result: there is no video output visible.
  Expected result: normal boot process should be visible (e.g. splash), then 
GUI should appear.

  [ Where problem could occur ]
  This bug was a result of assumptions in the checks that turned out to be not 
valid for some hardware. The checks were removed from global intel_mode_valid 
function and moved into connector specific .mode_valid() hooks, entirely 
skiping BXT/GLK DSI connectors.

  This should keep the checks where appropriate and skip for hardware
  that does not comply to them.

  [ Other info ]

  Original bug description:

  There is a regression preventing a user to upgrade from 5.4 kernel to 
anything that's higher than 5.5. When using such kernel the image orientation 
is wrong (rotated by 90°C). Also the kernel log contains:
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Unknown revid 0x06
  wrz 15 09:19:49 desktop kernel: rtw_8821ce :01:00.0: Firmware version 
24.8.0, H2C version 12
  wrz 15 09:19:49 desktop kernel: Console: switching to colour dummy device 
80x25
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: deactivate vga 
console
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] couldn't get memory 
information
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: changed VGA 
decodes: olddecodes=io+mem,decodes=io+mem:o>
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Finished loading DMC 
firmware i915/glk_dmc_ver1_04.bin (v>
  wrz 15 09:19:49 desktop kernel: 

  wrz 15 09:19:49 desktop kernel: UBSAN: array-index-out-of-bounds in 
/build/linux-hwe-5.15-DZkSuT/linux-hwe-5.15-5.>
  wrz 15 09:19:49 desktop kernel: index 5 is out of range for type 'u32 [5]'

  (full stack trace attached)

  The video hardware in use is:
  00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 605 
[8086:3185] (rev 06) (prog-if 00 [VGA controller])
  (...)
  Kernel driver in use: i915
  Kernel modules: i915

  The user wanted to upgrade from bionic to focal with HWE kernel (they
  needed it due to some networking hardware they wanted to have
  supported by the newer kernel).

  The user was testing mainline stable kernels and noticed that the last
  working kernel was the 5.4 series, while anything starting from 5.5
  and above is BROKEN (symptoms as described in the first paragraph
  above).

  Together with the user we have run a bisection between v5.4 and v5.5 on the 
upstream stable kernel and we were able to identify the first broken commit to 
be:
  8f4b1068e7fc3df1a77ac8151767e56b208cc87f drm/i915: Check some transcoder 
timing minimum limits

  To confirm I have reverted this change on top of the HWE kernel for
  focal and the user have confirmed that this resolved the issue (test
  build available at ppa:dgadomski/kernel-sf368743).

  I am not fully sure what the purpose of this patch was, but I assume
  the regression was not intended and the hardware should be still
  supported.

  Attaching lshw and lspci output.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2044131/+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 2044131] Re: i915 regression introduced with 5.5 kernel

** Description changed:

+ [ Impact ]
+ Commit 8f4b1068e7fc3df1a77ac8151767e56b208cc87f introduced some timing checks 
which have been proven invalid for at least some hardware setups. A user trying 
to run Focal with HWE 5.15 kernel is not able to get any video output.
+ After going through bisection between 5.4 and 5.5 this commit was identified. 
Reverting it on top of Focal HWE kernel fixes the issue.
+ 
+ The issue has been addressed upstream in DRM tree
+ (20c2dbff342aec13bf93c2f6c951da198916a455) and has been merge into
+ linux-next (e0ef2daa8ca8ce4dbc2fd0959e383b753a87fd7d).
+ 
+ dmesg and lspci from the affected configuration are attached to this
+ bug.
+ 
+ [ Test Plan ]
+ 1. Boot the affected hardware with Ubuntu desktop running kernel v5.5 or 
higher.
+ 2. Wait until boot finishes and see the blank screen.
+ 
+ Actual result: there is no video output visible.
+ Expected result: normal boot process should be visible (e.g. splash), then 
GUI should appear.
+ 
+ [ Where problem could occur ]
+ This bug was a result of assumptions in the checks that turned out to be not 
valid for some hardware. The checks were removed from global intel_mode_valid 
function and moved into connector specific .mode_valid() hooks, entirely 
skiping BXT/GLK DSI connectors.
+ 
+ This should keep the checks where appropriate and skip for hardware that
+ does not comply to them.
+ 
+ [ Other info ]
+ 
+ Original bug description:
+ 
  There is a regression preventing a user to upgrade from 5.4 kernel to 
anything that's higher than 5.5. When using such kernel the image orientation 
is wrong (rotated by 90°C). Also the kernel log contains:
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Unknown revid 0x06
  wrz 15 09:19:49 desktop kernel: rtw_8821ce :01:00.0: Firmware version 
24.8.0, H2C version 12
  wrz 15 09:19:49 desktop kernel: Console: switching to colour dummy device 
80x25
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: deactivate vga 
console
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] couldn't get memory 
information
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: changed VGA 
decodes: olddecodes=io+mem,decodes=io+mem:o>
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Finished loading DMC 
firmware i915/glk_dmc_ver1_04.bin (v>
  wrz 15 09:19:49 desktop kernel: 

  wrz 15 09:19:49 desktop kernel: UBSAN: array-index-out-of-bounds in 
/build/linux-hwe-5.15-DZkSuT/linux-hwe-5.15-5.>
  wrz 15 09:19:49 desktop kernel: index 5 is out of range for type 'u32 [5]'
  
  (full stack trace attached)
  
  The video hardware in use is:
  00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 605 
[8086:3185] (rev 06) (prog-if 00 [VGA controller])
  (...)
  Kernel driver in use: i915
  Kernel modules: i915
  
  The user wanted to upgrade from bionic to focal with HWE kernel (they
  needed it due to some networking hardware they wanted to have supported
  by the newer kernel).
  
  The user was testing mainline stable kernels and noticed that the last
  working kernel was the 5.4 series, while anything starting from 5.5 and
  above is BROKEN (symptoms as described in the first paragraph above).
  
  Together with the user we have run a bisection between v5.4 and v5.5 on the 
upstream stable kernel and we were able to identify the first broken commit to 
be:
  8f4b1068e7fc3df1a77ac8151767e56b208cc87f drm/i915: Check some transcoder 
timing minimum limits
  
  To confirm I have reverted this change on top of the HWE kernel for
  focal and the user have confirmed that this resolved the issue (test
  build available at ppa:dgadomski/kernel-sf368743).
  
  I am not fully sure what the purpose of this patch was, but I assume the
  regression was not intended and the hardware should be still supported.
  
  Attaching lshw and lspci output.

** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #9720
   https://gitlab.freedesktop.org/drm/intel/-/issues/9720

** Also affects: linux via
   https://gitlab.freedesktop.org/drm/intel/-/issues/9720
   Importance: Unknown
   Status: Unknown

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

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

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

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

** Patch added: 
"0001-drm-i915-Skip-some-timing-checks-on-BXT-GLK-DSI-tran.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044131/+attachment/5727219/+files/0001-drm-i915-Skip-some-timing-checks-on-BXT-GLK-DSI-tran.patch

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

Title:
  i915 regression introduced with 5.5 kernel

Statu

[Kernel-packages] [Bug 2045891] Re: Regression: MODE_H_ILLEGAL starting from kernel v5.5 for UHD 605 [8086:2212]

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


** Patch added: 
"0001-drm-i915-Skip-some-timing-checks-on-BXT-GLK-DSI-tran.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045891/+attachment/5727218/+files/0001-drm-i915-Skip-some-timing-checks-on-BXT-GLK-DSI-tran.patch

** Description changed:

  [ Impact ]
  Commit 8f4b1068e7fc3df1a77ac8151767e56b208cc87f introduced some timing checks 
which have been proven invalid for at least some hardware setups. A user trying 
to run Focal with HWE 5.15 kernel is not able to get any video output.
  After going through bisection between 5.4 and 5.5 this commit was identified. 
Reverting it on top of Focal HWE kernel fixes the issue.
  
  The issue has been addressed upstream in DRM tree
  (20c2dbff342aec13bf93c2f6c951da198916a455) and has been merge into
  linux-next (e0ef2daa8ca8ce4dbc2fd0959e383b753a87fd7d).
  
  dmesg and lspci from the affected configuration are attached to this
  bug.
  
  [ Test Plan ]
  1. Boot the affected hardware with Ubuntu desktop running kernel v5.5 or 
higher.
  2. Wait until boot finishes and see the blank screen.
  
  Actual result: there is no video output visible.
  Expected result: normal boot process should be visible (e.g. splash), then 
GUI should appear.
  
  [ Where problem could occur ]
  This bug was a result of assumptions in the checks that turned out to be not 
valid for some hardware. The checks were removed from global intel_mode_valid 
function and moved into connector specific .mode_valid() hooks, entirely 
skiping BXT/GLK DSI connectors.
  
  This should keep the checks where appropriate and skip for hardware that
  does not comply to them.
  
  [ Other info ]
  
  Upstream bug description:
  Prior to kernel v5.5 the setup was working fine. Starting with that release 
the display goes blank. What is visible in the logs:
  UBSAN: array-index-out-of-bounds in 
/build/linux-hwe-5.15-5Tb11x/linux-hwe-5.15-5.15.0/drivers/gpu/drm/i915/display/intel_display.c:12564:20
  index 5 is out of range for type 'u32 [5]'
  
  After a bisection I was able to determine that it started with commit 
8f4b1068e7fc3df1a77ac8151767e56b208cc87f.
  Apparently what happens is this test causes intel_mode_valid to exit with 
MODE_H_ILLEGAL:
  if (mode->htotal - mode->hdisplay < 32)
- return MODE_H_ILLEGAL;
+ return MODE_H_ILLEGAL;
  
  According to the output in the journal:
  [drm]] Modeline "800x1280": 50 54000 800 810 820 830 1280 1290 1300 1310 0x8 
0xa
  so in this case htotal is 830 and hdisplay is 800 which makes this condition 
true and determines the mode is illegal. As a result the display is blank.
  Reverting the commit in question restores full functionality

** This bug has been marked a duplicate of bug 2044131
   i915 regression introduced with 5.5 kernel

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

Title:
  Regression: MODE_H_ILLEGAL starting from kernel v5.5 for UHD 605
  [8086:2212]

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  New
Status in linux source package in Focal:
  New
Status in linux source package in Jammy:
  New
Status in linux source package in Mantic:
  New
Status in linux source package in Noble:
  New

Bug description:
  [ Impact ]
  Commit 8f4b1068e7fc3df1a77ac8151767e56b208cc87f introduced some timing checks 
which have been proven invalid for at least some hardware setups. A user trying 
to run Focal with HWE 5.15 kernel is not able to get any video output.
  After going through bisection between 5.4 and 5.5 this commit was identified. 
Reverting it on top of Focal HWE kernel fixes the issue.

  The issue has been addressed upstream in DRM tree
  (20c2dbff342aec13bf93c2f6c951da198916a455) and has been merge into
  linux-next (e0ef2daa8ca8ce4dbc2fd0959e383b753a87fd7d).

  dmesg and lspci from the affected configuration are attached to this
  bug.

  [ Test Plan ]
  1. Boot the affected hardware with Ubuntu desktop running kernel v5.5 or 
higher.
  2. Wait until boot finishes and see the blank screen.

  Actual result: there is no video output visible.
  Expected result: normal boot process should be visible (e.g. splash), then 
GUI should appear.

  [ Where problem could occur ]
  This bug was a result of assumptions in the checks that turned out to be not 
valid for some hardware. The checks were removed from global intel_mode_valid 
function and moved into connector specific .mode_valid() hooks, entirely 
skiping BXT/GLK DSI connectors.

  This should keep the checks where appropriate and skip for hardware
  that does not comply to them.

  [ Other info ]

  Upstream bug description:
  Prior to kernel v5.5 the setup was working fine. Starting with that release 
the display goes blank. What is visible in the logs:
  UBSAN: array-index-out-of-bounds in 
/build/linux-hwe-5.15-5Tb11x/linux-hwe-5.15-5.15.0/

[Kernel-packages] [Bug 2045891] Re: Regression: MODE_H_ILLEGAL starting from kernel v5.5 for UHD 605 [8086:2212]

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

Adding dmesg and lspci from affected system

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045891/+attachment/5727216/+files/dmesg

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

Title:
  Regression: MODE_H_ILLEGAL starting from kernel v5.5 for UHD 605
  [8086:2212]

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  New
Status in linux source package in Focal:
  New
Status in linux source package in Jammy:
  New
Status in linux source package in Mantic:
  New
Status in linux source package in Noble:
  New

Bug description:
  [ Impact ]
  Commit 8f4b1068e7fc3df1a77ac8151767e56b208cc87f introduced some timing checks 
which have been proven invalid for at least some hardware setups. A user trying 
to run Focal with HWE 5.15 kernel is not able to get any video output.
  After going through bisection between 5.4 and 5.5 this commit was identified. 
Reverting it on top of Focal HWE kernel fixes the issue.

  The issue has been addressed upstream in DRM tree
  (20c2dbff342aec13bf93c2f6c951da198916a455) and has been merge into
  linux-next (e0ef2daa8ca8ce4dbc2fd0959e383b753a87fd7d).

  dmesg and lspci from the affected configuration are attached to this
  bug.

  [ Test Plan ]
  1. Boot the affected hardware with Ubuntu desktop running kernel v5.5 or 
higher.
  2. Wait until boot finishes and see the blank screen.

  Actual result: there is no video output visible.
  Expected result: normal boot process should be visible (e.g. splash), then 
GUI should appear.

  [ Where problem could occur ]
  This bug was a result of assumptions in the checks that turned out to be not 
valid for some hardware. The checks were removed from global intel_mode_valid 
function and moved into connector specific .mode_valid() hooks, entirely 
skiping BXT/GLK DSI connectors.

  This should keep the checks where appropriate and skip for hardware
  that does not comply to them.

  [ Other info ]

  Upstream bug description:
  Prior to kernel v5.5 the setup was working fine. Starting with that release 
the display goes blank. What is visible in the logs:
  UBSAN: array-index-out-of-bounds in 
/build/linux-hwe-5.15-5Tb11x/linux-hwe-5.15-5.15.0/drivers/gpu/drm/i915/display/intel_display.c:12564:20
  index 5 is out of range for type 'u32 [5]'

  After a bisection I was able to determine that it started with commit 
8f4b1068e7fc3df1a77ac8151767e56b208cc87f.
  Apparently what happens is this test causes intel_mode_valid to exit with 
MODE_H_ILLEGAL:
  if (mode->htotal - mode->hdisplay < 32)
  return MODE_H_ILLEGAL;

  According to the output in the journal:
  [drm]] Modeline "800x1280": 50 54000 800 810 820 830 1280 1290 1300 1310 0x8 
0xa
  so in this case htotal is 830 and hdisplay is 800 which makes this condition 
true and determines the mode is illegal. As a result the display is blank.
  Reverting the commit in question restores full functionality

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2045891/+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 2045891] Re: Regression: MODE_H_ILLEGAL starting from kernel v5.5 for UHD 605 [8086:2212]