date:20221207

P.S. Although I have seen the bug recently, it doesn't seem to be
happening often enough right now for me to verify a new kernel with
confidence in a short timeframe.

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

Title:
  pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-
  Fatal), type=Transaction Layer, (Requester ID)

Status in HWE Next:
  Fix Committed
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-5.14 source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  My kernel log periodically bursts with:

  [10405.588287] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.593393] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.598564] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.603829] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.609563] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.614959] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.620296] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.625554] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.631180] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.636495] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.641867] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.647169] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.652919] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.658369] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.663803] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.669263] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.675130] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.680699] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.686267] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.691759] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 

  This has happened even since I got the machine. It also happened with
  5.15.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-15-generic 5.19.0-15.15
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan2477 F wireplumber
   /dev/snd/seq:dan2474 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Tue Sep  6 13:52:35 2022
  InstallationDate: Installed on 2022-07-20 (47 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
  MachineType: Intel(R) Client Systems NUC12DCMi7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic 
root=UUID=a69020a6-a1dd-436c-b75a-be890a4063be ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-15-generic N/A
   linux-backports-modules-5.19.0-15-generic  N/A
   linux-firmware 20220831.gitd3c92280-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/20/2021
  dmi.bios.release: 5.24
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: EDADL579.0046.2021.1220.2351
  dmi.board.name: NUC12EDBi7
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M27908-302
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0

[Kernel-packages] [Bug 1988797] Re: pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)

My affected system is running lunar. What kernel should I test there?

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

Title:
  pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-
  Fatal), type=Transaction Layer, (Requester ID)

Status in HWE Next:
  Fix Committed
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-5.14 source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  My kernel log periodically bursts with:

  [10405.588287] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.593393] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.598564] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.603829] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.609563] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.614959] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.620296] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.625554] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.631180] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.636495] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.641867] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.647169] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.652919] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.658369] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.663803] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.669263] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.675130] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.680699] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.686267] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.691759] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 

  This has happened even since I got the machine. It also happened with
  5.15.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-15-generic 5.19.0-15.15
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan2477 F wireplumber
   /dev/snd/seq:dan2474 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Tue Sep  6 13:52:35 2022
  InstallationDate: Installed on 2022-07-20 (47 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
  MachineType: Intel(R) Client Systems NUC12DCMi7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic 
root=UUID=a69020a6-a1dd-436c-b75a-be890a4063be ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-15-generic N/A
   linux-backports-modules-5.19.0-15-generic  N/A
   linux-firmware 20220831.gitd3c92280-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/20/2021
  dmi.bios.release: 5.24
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: EDADL579.0046.2021.1220.2351
  dmi.board.name: NUC12EDBi7
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M27908-302
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 3.7
  dmi.modalias:

Re: [Kernel-packages] [Bug 1995329] Re: [HP EliteBook 840 G8] [Intel AX201] Devices pair and connect, but immediately (4-5 secs) disconnect

2022-12-07 Thread Petter Sundlöf

I'll try it when I have a free usb stick available here. Although I'm on
22.10 currently, but I guess that's not entirely relevant

Den tors 8 dec. 2022 kl 07:55 skrev Kai-Heng Feng <
1995...@bugs.launchpad.net>:

> Most likely a firmware regression... can you please try 22.04 daily build?
> https://cdimages.ubuntu.com/jammy/daily-live/current/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1995329
>
> Title:
>   [HP EliteBook 840 G8] [Intel AX201] Devices pair and connect, but
>   immediately (4-5 secs) disconnect
>
> Status in bluez package in Ubuntu:
>   New
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Recently upgraded to 22.10 (from I believe 20.04, not actually
>   completely sure) and both of my Bluetooth devices have stopped
>   working.
>
>   They can pair and connect initially, but disconnect after 4-5 seconds.
>
>   My headphones worked a while, but have not since been able to have
>   them stay connected.
>
>   Here's an output from bluetoothctl, which doesn't say much?
>
>   Agent registered
>   [CHG] Controller 10:3D:1C:43:3B:C6 Pairable: yes
>   [CHG] Device 94:DB:56:4F:20:7F Connected: yes
>   [CHG] Controller 10:3D:1C:43:3B:C6 Discovering: yes
>   [NEW] Device CB:78:4F:E1:45:7D LE_WH-1000XM4
>   [CHG] Device 94:DB:56:4F:20:7F Connected: no
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
>   [CHG] Device CB:78:4F:E1:45:7D TxPower: -21
>   [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Key: 0x012d
>   [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Value:
> 04 00 01 31 05 01 74 84 12 86 04 40 d5 00 00 00  ...1..t@
> 00 00 00 ...
>   [CHG] Device CB:78:4F:E1:45:7D ServiceData Key:
> fe2c--1000-8000-00805f9b34fb
>   [CHG] Device CB:78:4F:E1:45:7D ServiceData Value:
> 00 90 87 04 02 48 e2 09 0e 30 0b 11 7a   .H...0..z
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -39
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -39
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -39
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -39
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
>   [NEW] Device D9:A2:A2:B7:40:35 P mesh
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
>   [CHG] Device CB:78:4F:E1:45:7D ServiceData Key:
> fe2c--1000-8000-00805f9b34fb
>   [CHG] Device CB:78:4F:E1:45:7D ServiceData Value:
> 00 90 88 b5 06 90 44 00 8d e6 00 11 30   ..D.0
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
>   [CHG] Device 94:DB:56:4F:20:7F Connected: yes
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
>   [CHG] Device 94:DB:56:4F:20:7F Connected: no
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
>   [bluetooth]#
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
>   [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Key: 0x012d
>   [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Value:
> 04 00 01 31 05 01 74 84 12 86 04 60 d5 00 00 00  ...1..t`
> 00 00 00 ...
>   [CHG] Device CB:78:4F:E1:45:7D ServiceData Key:
> fe2c--1000-8000-00805f9b34fb
>   [CHG] Device CB:78:4F:E1:45:7D ServiceData Value:
> 00 90 14 08 8e 2b 3a 42 02 89 00 11 74   .+:Bt
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
>   [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
>

[Kernel-packages] [Bug 1988797] Re: pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)

Daniel, the issue is fixed by the proposed kernel at my end. Does this
also fix the issue you saw?

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

Title:
  pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-
  Fatal), type=Transaction Layer, (Requester ID)

Status in HWE Next:
  Fix Committed
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-5.14 source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  My kernel log periodically bursts with:

  [10405.588287] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.593393] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.598564] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.603829] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.609563] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.614959] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.620296] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.625554] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.631180] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.636495] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.641867] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.647169] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.652919] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.658369] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.663803] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.669263] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.675130] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.680699] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.686267] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.691759] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 

  This has happened even since I got the machine. It also happened with
  5.15.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-15-generic 5.19.0-15.15
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan2477 F wireplumber
   /dev/snd/seq:dan2474 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Tue Sep  6 13:52:35 2022
  InstallationDate: Installed on 2022-07-20 (47 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
  MachineType: Intel(R) Client Systems NUC12DCMi7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic 
root=UUID=a69020a6-a1dd-436c-b75a-be890a4063be ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-15-generic N/A
   linux-backports-modules-5.19.0-15-generic  N/A
   linux-firmware 20220831.gitd3c92280-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/20/2021
  dmi.bios.release: 5.24
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: EDADL579.0046.2021.1220.2351
  dmi.board.name: NUC12EDBi7
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M27908-302
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 3.7
  dmi.modalias:

[Kernel-packages] [Bug 1995329] Re: [HP EliteBook 840 G8] [Intel AX201] Devices pair and connect, but immediately (4-5 secs) disconnect

Most likely a firmware regression... can you please try 22.04 daily build?
https://cdimages.ubuntu.com/jammy/daily-live/current/

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

Title:
  [HP EliteBook 840 G8] [Intel AX201] Devices pair and connect, but
  immediately (4-5 secs) disconnect

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Recently upgraded to 22.10 (from I believe 20.04, not actually
  completely sure) and both of my Bluetooth devices have stopped
  working.

  They can pair and connect initially, but disconnect after 4-5 seconds.

  My headphones worked a while, but have not since been able to have
  them stay connected.

  Here's an output from bluetoothctl, which doesn't say much?

  Agent registered
  [CHG] Controller 10:3D:1C:43:3B:C6 Pairable: yes
  [CHG] Device 94:DB:56:4F:20:7F Connected: yes
  [CHG] Controller 10:3D:1C:43:3B:C6 Discovering: yes
  [NEW] Device CB:78:4F:E1:45:7D LE_WH-1000XM4
  [CHG] Device 94:DB:56:4F:20:7F Connected: no
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D TxPower: -21
  [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Key: 0x012d
  [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Value:
04 00 01 31 05 01 74 84 12 86 04 40 d5 00 00 00  ...1..t@
00 00 00 ... 
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: 
fe2c--1000-8000-00805f9b34fb
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Value:
00 90 87 04 02 48 e2 09 0e 30 0b 11 7a   .H...0..z   
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -39
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -39
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -39
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -39
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [NEW] Device D9:A2:A2:B7:40:35 P mesh
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: 
fe2c--1000-8000-00805f9b34fb
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Value:
00 90 88 b5 06 90 44 00 8d e6 00 11 30   ..D.0   
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device 94:DB:56:4F:20:7F Connected: yes
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device 94:DB:56:4F:20:7F Connected: no
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [bluetooth]# 
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Key: 0x012d
  [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Value:
04 00 01 31 05 01 74 84 12 86 04 60 d5 00 00 00  ...1..t`
00 00 00 ... 
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: 
fe2c--1000-8000-00805f9b34fb
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Value:
00 90 14 08 8e 2b 3a 42 02 89 00 11 74   .+:Bt   
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [DEL] Device D9:A2:A2:B7:40:35 P mesh
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG]

[Kernel-packages] [Bug 1995904] Re: Computer freezes or is stuck

Possibly a kernel issue, please perform a kernel bisection:
https://wiki.ubuntu.com/Kernel/KernelBisection

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

Title:
  Computer freezes or is stuck

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  13-15 year old Toshiba laptop (Toshiba Satellite C665D) consistently runs 
into problems trying to run Ubuntu server 22.04.1. If left alone it will output 
"Uhhuh. NMI received for for unknown reason 2d on cpu 0. Do you have a strange 
power saving mode enabled? Dazed and confused, but trying to continue" 
repeatedly over and over disabling any input. Other times when running it would 
just freeze altogether needing a forced restart. The computer uses a AMD E-450 
APU with Radeon HD Graphics (dual core @ 1650MHz) with 4GB of ram and the bios 
is InsydeH2O version 1.8 rev 3.5. I tried "intel_idle.max_cstate=0" and 
"processor.max_cstate=0" to no avail as a user on askUbuntu suggested I should 
disable c-states, however there is no option in the bios.
  I am terribly sorry but I do not know what source package is causing this. I 
am very new to Ubuntu and Linux in general.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995904/+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 1995966] Re: RTS522A SD card reader on Lenovo P14s not working in Ubuntu 22.10

Please attach full dmesg after the card is inserted.

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

Title:
  RTS522A SD card reader on Lenovo P14s not working in Ubuntu 22.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Ubuntu 22.10 (uname -a says 5.19.0-23-generic #24-Ubuntu SMP
  PREEMPT_DYNAMIC Fri Oct 14 15:39:57 UTC 2022 x86_64 x86_64 x86_64
  GNU/Linux) on Lenovo P14s laptop.

  There is built-in SD card reader, which does not work. i e., when I
  insert SD card, it is not mounted or recognized at all.

  Please note this is not a problem of the SD card, because this SD card
  works on older Lenovo laptop (with different SD card reader) with
  Ubuntu (so it is not some "special", incompatible SD card).

  lspci says:

  04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI 
Express Card Reader [10ec:522a] (rev 01)
  Subsystem: Lenovo RTS522A PCI Express Card Reader [17aa:5094]
  Kernel driver in use: rtsx_pci
  Kernel modules: rtsx_pci

  lsmod | grep rtsx_pci says:
  rtsx_pci_sdmmc 36864  0
  rtsx_pci  106496  1 rtsx_pci_sdmmc

  I guess it is a kernel problem? Or there is another solution?
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-24 (16 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: LENOVO 21A0S05000
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  Tags:  kinetic wayland-session
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 06/27/2022
  dmi.bios.release: 1.19
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET49W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21A0S05000
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 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.19
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET49W(1.19):bd06/27/2022:br1.19:efr1.19:svnLENOVO:pn21A0S05000:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0S05000:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21A0S05000
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995966/+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 1995957] Re: Add cs35l41 firmware loading support

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

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

Title:
  Add cs35l41 firmware loading support

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  New
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-firmware source package in Kinetic:
  Fix Released
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  Speakers on some laptops are rather quiet even with max volume.

  [Fix]
  Loading firmware to make cs35l41 speaker amplifier really work.

  [Test]
  With the fix applied, the speaker has become really loud as intended.

  [Where problems could occur]
  Most commits are refactoring codes on both ASoC and HDA parts, so things
  can be missed.

  Other than that, the change is strictly limited to cs35l41, so the
  regression scope is rather narrow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1995957/+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 1996092] Re: Macbook boots with linux-image-4.15.0-192-generic (4.15.0-192.203) but freezes with newer kernels (4.15.0-193.204, 4.15.0-194.205, 4.15.0-196.207)

That kernel is quite old, maybe give 22.04 a try?

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

Title:
  Macbook boots with linux-image-4.15.0-192-generic (4.15.0-192.203) but
  freezes with newer kernels (4.15.0-193.204,4.15.0-194.205,
  4.15.0-196.207)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have old MacBook with broken main Graphic Controller
  (a well-known hardware issue https://discussions.apple.com/thread/251049873 ).

  So I switch to use Integrated Graphics Controller.

  I am using Ubuntu 18.04.6 LTS and after an 'apt update' laptop doesn't boot 
(freeze during boot).
  I looked for latest updated packages and I found:
   
  linux-image-4.15.0-192-generic 4.15.0-192.203 amd64
  =>
  linux-image-4.15.0-193-generic 4.15.0-193.204 amd64

  So, MacBook boots linux-image-4.15.0-192-generic correctly, but it
  doesn't boot with newer kernels (4.15.0-193.204,4.15.0-194.205,
  4.15.0-196.207)

  I could not find which change is included in newer kernels that did
  this issue.

  How could I support about this issue?

  
  PD:
  Added bellow some additional information and attached 'lspci-vnvn.log' file

  
  $ sudo lshw
  macbookpro  
  description: Notebook
  product: MacBookPro8,2 (System SKU#)
  vendor: Apple Inc.
  ...

  

  lspci-vnvn.log

  00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation 
Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) 
(prog-if 00 [VGA controller])
Subsystem: Apple Inc. 2nd Generation Core Processor Family Integrated 
Graphics Controller [106b:00dc]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996092/+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 1996208] Re: kernel: nvme nvme0: failed to set APST feature (2)

Does the NVMe work?

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

Title:
  kernel: nvme nvme0: failed to set APST feature (2)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  always my computer on show me this error: kernel: nvme nvme0: failed to set 
APST feature (2)
  this error start with update kernel 5.15.0-52
  well i check the logs and saw this:

  kernel: nvme nvme0: failed to set APST feature (2)
  [7.163360] kernel: nvme nvme0: allocated 64 MiB host memory buffer.
  [7.184123] kernel: nvme nvme0: 4/0/0 default/read/poll queues
  [7.201139] kernel:  nvme0n1: p1 p2
  [7.268310] kernel: usb 1-3: new full-speed USB device number 2 using 
xhci_h>
  [7.311210] kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
  [7.311225] kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
  [7.311239] kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
  [7.311251] kernel: ata4: SATA link down (SStatus 4 SControl 300)
  [7.311264] kernel: ata6: SATA link down (SStatus 4 SControl 300)
  [7.311278] kernel: ata3: SATA link down (SStatus 4 SControl 300)
  [7.312183] kernel: ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PC>
  [7.312217] kernel:
  [7.312218] kernel: No Local Variables are initialized for Method [_GTF]
  [7.312219] kernel:
  [7.312220] kernel: No Arguments are initialized for method [_GTF]
  [7.312221] kernel:
7.31] kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due>
  [7.312325] kernel: ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PC>
  [7.312357] kernel:
  [7.312359] kernel: No Local Variables are initialized for Method [_GTF]
  [7.312359] kernel:
  [7.312360] kernel: No Arguments are initialized for method [_GTF]
  [7.312361] kernel:
  [7.312362] kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT4._GTF 
due>
  [7.312399] kernel: ata5.00: ATA-10: CT240BX500SSD1, M6CR054, max UDMA/133
  [7.312420] kernel: ata1.00: ATA-8: Hitachi HTS542525K9SA00, BBFOC31P, max 
U>
  [7.312699] kernel: ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PC>
  [7.312731] kernel:
  [7.312732] kernel: No Local Variables are initialized for Method [_GTF]
  [7.312733] kernel:
  [7.312734] kernel: No Arguments are initialized for method [_GTF]
  7.312736] kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT1._GTF due>
  [7.312768] kernel: ata2.00: ATA-9: HGST HTS541010A9E680, JA0OA710, max 
UDMA>
  [7.313013] kernel: ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ 
(depth >
  [7.313420] kernel: ata5.00: 468862128 sectors, multi 1: LBA48 NCQ (depth 
32>
  [7.314598] kernel: ata1.00: ATA Identify Device Log not supported
  [7.314601] kernel: ata1.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 
3>
  [7.314706] kernel: ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PC>
  [7.314738] kernel:
  [7.314740] kernel: No Local Variables are initialized for Method [_GTF]
  [7.314740] kernel:
  [7.314741] kernel: No Arguments are initialized for method [_GTF]
  [7.314742] kernel:
  [7.314743] kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT1._GTF 
due>
  [7.315039] kernel: ata2.00: configured for UDMA/133
  [7.315707] kernel: ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PC>
  [7.315740] kernel:
  [7.315741] kernel: No Local Variables are initialized for Method [_GTF]
  [7.315742] kernel:
  [7.315742] kernel: No Arguments are initialized for method [_GTF]
  [7.315743] kernel:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996208/+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 1996740] Re: 5.15.0-53-generic no longer boots

Is it a laptop? Does the internal eDP panel also have this issue?

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

Title:
  5.15.0-53-generic no longer boots

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

Bug description:
  == SRU Justification ==
  [Impact]
  "UBUNTU: SAUCE: Revert "drm/amd/display: Add helper for blanking all dp
  displays" caused AMD Navi10 GFX to panic at boot.

  [Fix]
  Backport the revised version of "drm/amd/display: Add helper for
  blanking all dp displays".

  [Test]
  Users confirmed the issue went away with this fix.
  We also verified the original issue we fixed didn't reappear.

  [Where problems could occur]
  We didn't test all the combination of dce110/dcn10/dcn30/dcn31, so many
  cases are untested, hence the potential risk is there.

  == Original Bug Report ==

  Running Ubuntu 22.04.1 Jammy.
  After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no 
longer fully boots.
  After the normal splash screen the screen goes black and the computer is not 
reachable on the network. Changing to another TTY does not work.

  New kernel version: 5.15.0-53.59

  I will attach the output of journalctl -b -1, please let me know what other 
info you need.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  johan  2549 F pulseaudio
   /dev/snd/controlC0:  johan  2549 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2020-12-01 (714 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  IwConfig:
   lono wireless extensions.

   enp37s0   no wireless extensions.

   wgnfs no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7C52
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic 
root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-52-generic N/A
   linux-backports-modules-5.15.0-52-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.6
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-52-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago)
  UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 07/23/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 3.G0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M-A PRO MAX (MS-7C52)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7C52
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996740/+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 1999031] Re: Multiple display issues after upgrade of XPS 15 7590 with Ubuntu 22.10

Yes please open a new bug for the driver issue by running:

  ubuntu-bug software-properties-gtk


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

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

Title:
  Multiple display issues after upgrade of XPS 15 7590 with Ubuntu 22.10

Status in linux package in Ubuntu:
  Invalid

Bug description:
  After updating Ubuntu on a Dell XPS 15 7590 from version 22.04 to
  22.10 Kinetic (presently running 5.19.0-27), there are multiple
  display issues.

  - Brightness is set at 100% and cannot be changed.
  - Brightness controls do not work, they are assigned different types of 
controls, brightness down button maximizes an internet window, brightness up 
shows the page code (see video file  attached).
  - Display driver is reported to have been installed manually, which obviously 
it was not, graphic adapter drivers (Nouveau or NVidia legacy) cannot be 
selected (see screenshot attached).

  Obviously all these issues remain after switching from XOrg to Wayland
  (running Ubuntu on Wayland) and rebooting the laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-27.28-generic 5.19.17
  Uname: Linux 5.19.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.86.01  Wed Oct 26 
09:12:38 UTC 2022
   GCC version:
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  7 14:00:24 2022
  DistUpgraded: 2022-12-03 12:58:58,725 DEBUG icon theme changed, re-reading
  DistroCodename: kinetic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:0905]
     Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:0905]
  InstallationDate: Installed on 2022-06-16 (174 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. XPS 15 7590
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-27-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to kinetic on 2022-12-03 (4 days ago)
  dmi.bios.date: 09/14/2022
  dmi.bios.release: 1.19
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.19.0
  dmi.board.name: 0T8KGX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.0:bd09/14/2022:br1.19:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0T8KGX:rvrA00:cvnDellInc.:ct10:cvr:sku0905:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 7590
  dmi.product.sku: 0905
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/1999031/+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 1999031] Re: Multiple display issues after upgrade of XPS 15 7590 with Ubuntu 22.10

2022-12-07 Thread atactic

Daniel, very good hint, it works when holding [Fn] down.
Then I can also toggle the function keys action by pressing [Fn]+[ESC] (that 
has a small Fn lock icon painted on it), did not even know about this. 
There is also a disable Fn-Lock option in the BIOS settings, POST-Behaviour, 
but this remains effect-less on deactivating the Fn-Lock, have still to do it 
manually after start-up.

So what is the way forward now, do I have to fill another bug report for
the separate display driver issue?

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

Title:
  Multiple display issues after upgrade of XPS 15 7590 with Ubuntu 22.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating Ubuntu on a Dell XPS 15 7590 from version 22.04 to
  22.10 Kinetic (presently running 5.19.0-27), there are multiple
  display issues.

  - Brightness is set at 100% and cannot be changed.
  - Brightness controls do not work, they are assigned different types of 
controls, brightness down button maximizes an internet window, brightness up 
shows the page code (see video file  attached).
  - Display driver is reported to have been installed manually, which obviously 
it was not, graphic adapter drivers (Nouveau or NVidia legacy) cannot be 
selected (see screenshot attached).

  Obviously all these issues remain after switching from XOrg to Wayland
  (running Ubuntu on Wayland) and rebooting the laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-27.28-generic 5.19.17
  Uname: Linux 5.19.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.86.01  Wed Oct 26 
09:12:38 UTC 2022
   GCC version:
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  7 14:00:24 2022
  DistUpgraded: 2022-12-03 12:58:58,725 DEBUG icon theme changed, re-reading
  DistroCodename: kinetic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:0905]
     Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:0905]
  InstallationDate: Installed on 2022-06-16 (174 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. XPS 15 7590
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-27-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to kinetic on 2022-12-03 (4 days ago)
  dmi.bios.date: 09/14/2022
  dmi.bios.release: 1.19
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.19.0
  dmi.board.name: 0T8KGX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.0:bd09/14/2022:br1.19:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0T8KGX:rvrA00:cvnDellInc.:ct10:cvr:sku0905:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 7590
  dmi.product.sku: 0905
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/1999031/+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 1999094] Re: mm:vma05 in ubuntu_ltp fails with '[vdso] bug not patched' on kinetic/linux 5.19.0-27.28

2022-12-07 Thread Po-Hsu Lin

** Tags added: 5.19 kinetic sru-20221114 ubuntu-ltp

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

Title:
  mm:vma05 in ubuntu_ltp fails with '[vdso] bug not patched' on
  kinetic/linux 5.19.0-27.28

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Kinetic:
  Incomplete

Bug description:
  This test fails on 5.19.0-27.28 in cycle 2022.11.14 on most if not all
  instances.

  Running tests...
  vma05 1 TINFO: timeout per run is 0h 5m 0s
  vma05 1 TFAIL: [vdso] bug not patched
  vma05 2 TINFO: AppArmor enabled, this may affect test results
  vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires 
super/root)
  vma05 2 TINFO: loaded AppArmor profiles: none
  
  Looking at the contents of the triggered backtrace, on 5.19.0-26 the contents 
look like this:

  vma05 1 TPASS: [vsyscall] reported correctly
  vma05 1 TINFO: TRACE=Reading symbols from vma05_vdso...
  [New LWP 418325]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `vma05_vdso'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  __pthread_kill_implementation (no_tid=0, signo=11,
  threadid=) at ./nptl/pthread_kill.c:44

  Thread 1 (Thread 0x7f3093c4e740 (LWP 418325)):
  #0  __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44
  #1  __pthread_kill_internal (signo=11, threadid=) at 
./nptl/pthread_kill.c:78
  #2  __GI___pthread_kill (threadid=, signo=signo@entry=11) at 
./nptl/pthread_kill.c:89
  #3  0x7f3093a3bc46 in __GI_raise (sig=sig@entry=11) at 
../sysdeps/posix/raise.c:26
  #4  0x55f54287a072 in main () at vma05_vdso.c:5
  vma05 1 TPASS: [vdso] backtrace complete
  --
  while on 5.19.0-27.28 it looks like this:
  vma05 1 TINFO: TRACE=Reading symbols from vma05_vdso...
  [New LWP 1501]
  Core was generated by `vma05_vdso'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x7f9b3c09226b in ?? ()

  Thread 1 (LWP 1501):
  #0  0x7f9b3c09226b in ?? ()
  Backtrace stopped: Cannot access memory at address 0x7ffc216242b0
  vma05 1 TFAIL: [vdso] bug not patched
  vma05 2 TINFO: AppArmor enabled, this may affect test results
  vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires 
super/root)
  vma05 2 TINFO: loaded AppArmor profiles: none

  Suggesting that this bug has somehow been reintroduced. Will look into
  this further.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1999094/+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 1990985] Re: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems

This bug is awaiting verification that the linux/5.19.0-27.28 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-kinetic' to 'verification-done-kinetic'. If the
problem still exists, change the tag 'verification-needed-kinetic' to
'verification-failed-kinetic'.

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-kinetic-linux verification-needed-kinetic

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

Title:
  ACPI: processor idle: Practically limit "Dummy wait" workaround to old
  Intel systems

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed

Bug description:
  IMPACT:
  Old, circa 2002 chipsets have a bug: they don't go idle when they are
  supposed to.  So, a workaround was added to slow the CPU down and
  ensure that the CPU waits a bit for the chipset to actually go idle.
  This workaround is ancient and has been in place in some form since
  the original kernel ACPI implementation.

  But, this workaround is very painful on modern systems.  The "inl()"
  can take thousands of cycles (see Link: for some more detailed
  numbers and some fun kernel archaeology).

  First and foremost, modern systems should not be using this code.
  Typical Intel systems have not used it in over a decade because it is
  horribly inferior to MWAIT-based idle.

  Despite this, people do seem to be tripping over this workaround on
  AMD system today.

  Limit the "dummy wait" workaround to Intel systems.  Keep Modern AMD
  systems from tripping over the workaround.  Remotely modern Intel
  systems use intel_idle instead of this code and will, in practice,
  remain unaffected by the dummy wait.

  Reported-by: K Prateek Nayak 
  Suggested-by: Rafael J. Wysocki 
  Signed-off-by: Dave Hansen 
  Reviewed-by: Mario Limonciello 
  Tested-by: K Prateek Nayak 
  Link: 
https://lore.kernel.org/all/20220921063638.2489-1-kprateek.na...@amd.com/
  Link: https://lkml.kernel.org/r/20220922184745.3252932-1-dave.han...@intel.com

  FIX:

  This issue pertains to  all Zen based processors starting with
  Naples(Zen1). All LTS releases will need this fix:

  
https://github.com/torvalds/linux/commit/e400ad8b7e6a1b9102123c6240289a811501f7d9

  TESTCASE:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990985/+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 1999031] Status changed to Confirmed

This change was made by a bot.

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

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

Title:
  Multiple display issues after upgrade of XPS 15 7590 with Ubuntu 22.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating Ubuntu on a Dell XPS 15 7590 from version 22.04 to
  22.10 Kinetic (presently running 5.19.0-27), there are multiple
  display issues.

  - Brightness is set at 100% and cannot be changed.
  - Brightness controls do not work, they are assigned different types of 
controls, brightness down button maximizes an internet window, brightness up 
shows the page code (see video file  attached).
  - Display driver is reported to have been installed manually, which obviously 
it was not, graphic adapter drivers (Nouveau or NVidia legacy) cannot be 
selected (see screenshot attached).

  Obviously all these issues remain after switching from XOrg to Wayland
  (running Ubuntu on Wayland) and rebooting the laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-27.28-generic 5.19.17
  Uname: Linux 5.19.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.86.01  Wed Oct 26 
09:12:38 UTC 2022
   GCC version:
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  7 14:00:24 2022
  DistUpgraded: 2022-12-03 12:58:58,725 DEBUG icon theme changed, re-reading
  DistroCodename: kinetic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:0905]
     Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:0905]
  InstallationDate: Installed on 2022-06-16 (174 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. XPS 15 7590
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-27-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to kinetic on 2022-12-03 (4 days ago)
  dmi.bios.date: 09/14/2022
  dmi.bios.release: 1.19
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.19.0
  dmi.board.name: 0T8KGX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.0:bd09/14/2022:br1.19:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0T8KGX:rvrA00:cvnDellInc.:ct10:cvr:sku0905:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 7590
  dmi.product.sku: 0905
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/1999031/+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 1990985] Re: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems

This bug is awaiting verification that the linux-
bluefield/5.15.0-1010.12 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' to 'verification-
done-jammy'. If the problem still exists, change the tag 'verification-
needed-jammy' to 'verification-failed-jammy'.

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 removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-bluefield verification-needed-jammy

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

Title:
  ACPI: processor idle: Practically limit "Dummy wait" workaround to old
  Intel systems

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed

Bug description:
  IMPACT:
  Old, circa 2002 chipsets have a bug: they don't go idle when they are
  supposed to.  So, a workaround was added to slow the CPU down and
  ensure that the CPU waits a bit for the chipset to actually go idle.
  This workaround is ancient and has been in place in some form since
  the original kernel ACPI implementation.

  But, this workaround is very painful on modern systems.  The "inl()"
  can take thousands of cycles (see Link: for some more detailed
  numbers and some fun kernel archaeology).

  First and foremost, modern systems should not be using this code.
  Typical Intel systems have not used it in over a decade because it is
  horribly inferior to MWAIT-based idle.

  Despite this, people do seem to be tripping over this workaround on
  AMD system today.

  Limit the "dummy wait" workaround to Intel systems.  Keep Modern AMD
  systems from tripping over the workaround.  Remotely modern Intel
  systems use intel_idle instead of this code and will, in practice,
  remain unaffected by the dummy wait.

  Reported-by: K Prateek Nayak 
  Suggested-by: Rafael J. Wysocki 
  Signed-off-by: Dave Hansen 
  Reviewed-by: Mario Limonciello 
  Tested-by: K Prateek Nayak 
  Link: 
https://lore.kernel.org/all/20220921063638.2489-1-kprateek.na...@amd.com/
  Link: https://lkml.kernel.org/r/20220922184745.3252932-1-dave.han...@intel.com

  FIX:

  This issue pertains to  all Zen based processors starting with
  Naples(Zen1). All LTS releases will need this fix:

  
https://github.com/torvalds/linux/commit/e400ad8b7e6a1b9102123c6240289a811501f7d9

  TESTCASE:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990985/+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 1999031] Re: Multiple display issues after upgrade of XPS 15 7590 with Ubuntu 22.10

We'll focus on the brightness issues here, which partly sounds like a
keyboard issue. Did you try holding down Fn while pressing the
brightness keys? It might just be in Fn-lock mode.

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

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

Title:
  Multiple display issues after upgrade of XPS 15 7590 with Ubuntu 22.10

Status in linux package in Ubuntu:
  New

Bug description:
  After updating Ubuntu on a Dell XPS 15 7590 from version 22.04 to
  22.10 Kinetic (presently running 5.19.0-27), there are multiple
  display issues.

  - Brightness is set at 100% and cannot be changed.
  - Brightness controls do not work, they are assigned different types of 
controls, brightness down button maximizes an internet window, brightness up 
shows the page code (see video file  attached).
  - Display driver is reported to have been installed manually, which obviously 
it was not, graphic adapter drivers (Nouveau or NVidia legacy) cannot be 
selected (see screenshot attached).

  Obviously all these issues remain after switching from XOrg to Wayland
  (running Ubuntu on Wayland) and rebooting the laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-27.28-generic 5.19.17
  Uname: Linux 5.19.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.86.01  Wed Oct 26 
09:12:38 UTC 2022
   GCC version:
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  7 14:00:24 2022
  DistUpgraded: 2022-12-03 12:58:58,725 DEBUG icon theme changed, re-reading
  DistroCodename: kinetic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:0905]
     Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:0905]
  InstallationDate: Installed on 2022-06-16 (174 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. XPS 15 7590
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-27-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to kinetic on 2022-12-03 (4 days ago)
  dmi.bios.date: 09/14/2022
  dmi.bios.release: 1.19
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.19.0
  dmi.board.name: 0T8KGX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.0:bd09/14/2022:br1.19:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0T8KGX:rvrA00:cvnDellInc.:ct10:cvr:sku0905:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 7590
  dmi.product.sku: 0905
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/1999031/+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 1999031] [NEW] Multiple display issues after upgrade of XPS 15 7590 with Ubuntu 22.10

2022-12-07 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

After updating Ubuntu on a Dell XPS 15 7590 from version 22.04 to 22.10
Kinetic (presently running 5.19.0-27), there are multiple display
issues.

- Brightness is set at 100% and cannot be changed.
- Brightness controls do not work, they are assigned different types of 
controls, brightness down button maximizes an internet window, brightness up 
shows the page code (see video file  attached).
- Display driver is reported to have been installed manually, which obviously 
it was not, graphic adapter drivers (Nouveau or NVidia legacy) cannot be 
selected (see screenshot attached).

Obviously all these issues remain after switching from XOrg to Wayland
(running Ubuntu on Wayland) and rebooting the laptop.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-27.28-generic 5.19.17
Uname: Linux 5.19.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.86.01  Wed Oct 26 09:12:38 
UTC 2022
 GCC version:
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec  7 14:00:24 2022
DistUpgraded: 2022-12-03 12:58:58,725 DEBUG icon theme changed, re-reading
DistroCodename: kinetic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (rev 02) 
(prog-if 00 [VGA controller])
   Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:0905]
   Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:0905]
InstallationDate: Installed on 2022-06-16 (174 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: Dell Inc. XPS 15 7590
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-27-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to kinetic on 2022-12-03 (4 days ago)
dmi.bios.date: 09/14/2022
dmi.bios.release: 1.19
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.19.0
dmi.board.name: 0T8KGX
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.0:bd09/14/2022:br1.19:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0T8KGX:rvrA00:cvnDellInc.:ct10:cvr:sku0905:
dmi.product.family: XPS
dmi.product.name: XPS 15 7590
dmi.product.sku: 0905
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug kinetic ubuntu wayland-session
-- 
Multiple display issues after upgrade of XPS 15 7590 with Ubuntu 22.10 
https://bugs.launchpad.net/bugs/1999031
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 1989172] Re: mlxbf-pmc: error when reading unprogrammed events

2022-12-07 Thread Shravan Kumar Ramani

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

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

Title:
  mlxbf-pmc: error when reading unprogrammed events

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

Bug description:
  SRU Justification:

  [Impact]
  When the counters are not programmed to monitor any events, reading the 
"event" file results in the following error:
  cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argument
  This is misleading and instead needs to indicate that the counter is 
currently not enabled.

  [Fix]
  * First, skip the check for whether the counter is enabled when reading the 
event info. If the counter is not enabled, it should return 0, which is the 
default value when coming out of reset.
  * 0 is not a valid event in most blocks as per the respective event lists, so 
add a "Disable" event to all the event lists.

  [Test Case]
  Without the fix, reading any "event" file right after reset when the counters 
are not programmed should result in the following error:
  cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argumen
  With the fix, it should instead print:
  0x0: DISABLE

  [Regression Potential]
  Can be considered minimal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1989172/+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 1995109] Re: bluefield-edac: Potentially overflowing expression

2022-12-07 Thread Shravan Kumar Ramani

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

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

Title:
  bluefield-edac: Potentially overflowing expression

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Focal:
  Fix Committed
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]
  Potential integer overflow in men_ctrl_idx detected by static tool analyser.

  [Fix]
  Declare as type u64 instead of type int

  [Test Case]
  NA since the variable is read from the ACPI table

  [Regression Potential]
  Can be considered minimal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1995109/+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 1990985] Re: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems

This bug is awaiting verification that the linux-
azure-4.15/4.15.0-1157.172 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-bionic' to
'verification-done-bionic'. If the problem still exists, change the tag
'verification-needed-bionic' to 'verification-failed-bionic'.

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 removed: verification-done-bionic
** Tags added: kernel-spammed-bionic-linux-azure-4.15 verification-needed-bionic

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

Title:
  ACPI: processor idle: Practically limit "Dummy wait" workaround to old
  Intel systems

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed

Bug description:
  IMPACT:
  Old, circa 2002 chipsets have a bug: they don't go idle when they are
  supposed to.  So, a workaround was added to slow the CPU down and
  ensure that the CPU waits a bit for the chipset to actually go idle.
  This workaround is ancient and has been in place in some form since
  the original kernel ACPI implementation.

  But, this workaround is very painful on modern systems.  The "inl()"
  can take thousands of cycles (see Link: for some more detailed
  numbers and some fun kernel archaeology).

  First and foremost, modern systems should not be using this code.
  Typical Intel systems have not used it in over a decade because it is
  horribly inferior to MWAIT-based idle.

  Despite this, people do seem to be tripping over this workaround on
  AMD system today.

  Limit the "dummy wait" workaround to Intel systems.  Keep Modern AMD
  systems from tripping over the workaround.  Remotely modern Intel
  systems use intel_idle instead of this code and will, in practice,
  remain unaffected by the dummy wait.

  Reported-by: K Prateek Nayak 
  Suggested-by: Rafael J. Wysocki 
  Signed-off-by: Dave Hansen 
  Reviewed-by: Mario Limonciello 
  Tested-by: K Prateek Nayak 
  Link: 
https://lore.kernel.org/all/20220921063638.2489-1-kprateek.na...@amd.com/
  Link: https://lkml.kernel.org/r/20220922184745.3252932-1-dave.han...@intel.com

  FIX:

  This issue pertains to  all Zen based processors starting with
  Naples(Zen1). All LTS releases will need this fix:

  
https://github.com/torvalds/linux/commit/e400ad8b7e6a1b9102123c6240289a811501f7d9

  TESTCASE:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990985/+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 1996740] Re: 5.15.0-53-generic no longer boots

2022-12-07 Thread Scott P

I want to raise the possibility that this fix (or another one) in the
new kernel update has begun preventing me from Blanking my DP monitors.

I had previously been experiencing xorg cpu spikes and softlocks when my
monitors Blanked, but now, they refuse to Blank at all. They disconnect
for a brief moment and they reactivate. I can see my mouse cursor
reappear on screen.

I have an AMD Ryzen 5700u (includes renoir graphics). Using amdgpu
(default).

So this new kernel is better than the last kernel with xorg softlocks
that prevented me from accessing my system but might have
introduced/revealed another less severe bug.

I tried to hunt down what amdgpu impacting changes were made to the
latest ubuntu kernel and I think this is the only one?

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

Title:
5.15.0-53-generic no longer boots

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

Bug description:
== SRU Justification ==
[Impact]
"UBUNTU: SAUCE: Revert "drm/amd/display: Add helper for blanking all dp
displays" caused AMD Navi10 GFX to panic at boot.

[Fix]
Backport the revised version of "drm/amd/display: Add helper for
blanking all dp displays".

[Test]
Users confirmed the issue went away with this fix.
We also verified the original issue we fixed didn't reappear.

[Where problems could occur]
We didn't test all the combination of dce110/dcn10/dcn30/dcn31, so many
cases are untested, hence the potential risk is there.

== Original Bug Report ==

Running Ubuntu 22.04.1 Jammy.
After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no
longer fully boots.
After the normal splash screen the screen goes black and the computer is not
reachable on the network. Changing to another TTY does not work.

New kernel version: 5.15.0-53.59

I will attach the output of journalctl -b -1, please let me know what other
info you need.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: johan 2549 F pulseaudio
/dev/snd/controlC0: johan 2549 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2020-12-01 (714 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
IwConfig:
lono wireless extensions.

enp37s0 no wireless extensions.

wgnfs no wireless extensions.
MachineType: Micro-Star International Co., Ltd. MS-7C52
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic
root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
RelatedPackageVersions:
linux-restricted-modules-5.15.0-52-generic N/A
linux-backports-modules-5.15.0-52-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.6
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: jammy wayland-session
Uname: Linux 5.15.0-52-generic x86_64
UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago)
UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare
sudo
_MarkForUpload: True
dmi.bios.date: 07/23/2022
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 3.G0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B450M-A PRO MAX (MS-7C52)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7C52
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996740/+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 1999094] Re: mm:vma05 fails with '[vdso] bug not patched' on kinetic/linux 5.19.0-27.28

2022-12-07 Thread Luke Nowakowski-Krijger

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

** Summary changed:

-  mm:vma05 fails with '[vdso] bug not patched' on kinetic/linux 5.19.0-27.28
+ mm:vma05 in ubuntu_ltp fails with '[vdso] bug not patched' on kinetic/linux 
5.19.0-27.28

** Description changed:

  This test fails on 5.19.0-27.28 in cycle 2022.11.14 on most if not all
  instances.
  
  Running tests...
  vma05 1 TINFO: timeout per run is 0h 5m 0s
  vma05 1 TFAIL: [vdso] bug not patched
  vma05 2 TINFO: AppArmor enabled, this may affect test results
  vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires 
super/root)
  vma05 2 TINFO: loaded AppArmor profiles: none
- 
- Looking at the contents of the triggered backtrace, on 5.19.0-26 the
- contents look like this:
+ 
+ Looking at the contents of the triggered backtrace, on 5.19.0-26 the contents 
look like this:
  
  vma05 1 TPASS: [vsyscall] reported correctly
  vma05 1 TINFO: TRACE=Reading symbols from vma05_vdso...
  [New LWP 418325]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `vma05_vdso'.
  Program terminated with signal SIGSEGV, Segmentation fault.
- #0  __pthread_kill_implementation (no_tid=0, signo=11, 
- threadid=) at ./nptl/pthread_kill.c:44
+ #0  __pthread_kill_implementation (no_tid=0, signo=11,
+ threadid=) at ./nptl/pthread_kill.c:44
  
  Thread 1 (Thread 0x7f3093c4e740 (LWP 418325)):
  #0  __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44
  #1  __pthread_kill_internal (signo=11, threadid=) at 
./nptl/pthread_kill.c:78
  #2  __GI___pthread_kill (threadid=, signo=signo@entry=11) at 
./nptl/pthread_kill.c:89
  #3  0x7f3093a3bc46 in __GI_raise (sig=sig@entry=11) at 
../sysdeps/posix/raise.c:26
  #4  0x55f54287a072 in main () at vma05_vdso.c:5
  vma05 1 TPASS: [vdso] backtrace complete
- 
- 
+ --
  while on 5.19.0-27.28 it looks like this:
  vma05 1 TINFO: TRACE=Reading symbols from vma05_vdso...
  [New LWP 1501]
  Core was generated by `vma05_vdso'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x7f9b3c09226b in ?? ()
  
  Thread 1 (LWP 1501):
  #0  0x7f9b3c09226b in ?? ()
  Backtrace stopped: Cannot access memory at address 0x7ffc216242b0
  vma05 1 TFAIL: [vdso] bug not patched
  vma05 2 TINFO: AppArmor enabled, this may affect test results
  vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires 
super/root)
  vma05 2 TINFO: loaded AppArmor profiles: none
  
  Suggesting that this bug has somehow been reintroduced. Will look into
  this further.

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

Title:
  mm:vma05 in ubuntu_ltp fails with '[vdso] bug not patched' on
  kinetic/linux 5.19.0-27.28

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Kinetic:
  Incomplete

Bug description:
  This test fails on 5.19.0-27.28 in cycle 2022.11.14 on most if not all
  instances.

  Running tests...
  vma05 1 TINFO: timeout per run is 0h 5m 0s
  vma05 1 TFAIL: [vdso] bug not patched
  vma05 2 TINFO: AppArmor enabled, this may affect test results
  vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires 
super/root)
  vma05 2 TINFO: loaded AppArmor profiles: none
  
  Looking at the contents of the triggered backtrace, on 5.19.0-26 the contents 
look like this:

  vma05 1 TPASS: [vsyscall] reported correctly
  vma05 1 TINFO: TRACE=Reading symbols from vma05_vdso...
  [New LWP 418325]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `vma05_vdso'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  __pthread_kill_implementation (no_tid=0, signo=11,
  threadid=) at ./nptl/pthread_kill.c:44

  Thread 1 (Thread 0x7f3093c4e740 (LWP 418325)):
  #0  __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44
  #1  __pthread_kill_internal (signo=11, threadid=) at 
./nptl/pthread_kill.c:78
  #2  __GI___pthread_kill (threadid=, signo=signo@entry=11) at 
./nptl/pthread_kill.c:89
  #3  0x7f3093a3bc46 in __GI_raise (sig=sig@entry=11) at 
../sysdeps/posix/raise.c:26
  #4  0x55f54287a072 in main () at vma05_vdso.c:5
  vma05 1 TPASS: [vdso] backtrace complete
  --
  while on 5.19.0-27.28 it looks like this:
  vma05 1 TINFO: TRACE=Reading symbols from vma05_vdso...
  [New LWP 1501]
  Core was generated by `vma05_vdso'.
  Program terminated with signal

[Kernel-packages] [Bug 1999094] Missing required logs.

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

apport-collect 1999094

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

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

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

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

** Changed in: linux (Ubuntu Kinetic)
   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/1999094

Title:
  mm:vma05 in ubuntu_ltp fails with '[vdso] bug not patched' on
  kinetic/linux 5.19.0-27.28

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Kinetic:
  Incomplete

Bug description:
  This test fails on 5.19.0-27.28 in cycle 2022.11.14 on most if not all
  instances.

  Running tests...
  vma05 1 TINFO: timeout per run is 0h 5m 0s
  vma05 1 TFAIL: [vdso] bug not patched
  vma05 2 TINFO: AppArmor enabled, this may affect test results
  vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires 
super/root)
  vma05 2 TINFO: loaded AppArmor profiles: none
  
  Looking at the contents of the triggered backtrace, on 5.19.0-26 the contents 
look like this:

  vma05 1 TPASS: [vsyscall] reported correctly
  vma05 1 TINFO: TRACE=Reading symbols from vma05_vdso...
  [New LWP 418325]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `vma05_vdso'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  __pthread_kill_implementation (no_tid=0, signo=11,
  threadid=) at ./nptl/pthread_kill.c:44

  Thread 1 (Thread 0x7f3093c4e740 (LWP 418325)):
  #0  __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44
  #1  __pthread_kill_internal (signo=11, threadid=) at 
./nptl/pthread_kill.c:78
  #2  __GI___pthread_kill (threadid=, signo=signo@entry=11) at 
./nptl/pthread_kill.c:89
  #3  0x7f3093a3bc46 in __GI_raise (sig=sig@entry=11) at 
../sysdeps/posix/raise.c:26
  #4  0x55f54287a072 in main () at vma05_vdso.c:5
  vma05 1 TPASS: [vdso] backtrace complete
  --
  while on 5.19.0-27.28 it looks like this:
  vma05 1 TINFO: TRACE=Reading symbols from vma05_vdso...
  [New LWP 1501]
  Core was generated by `vma05_vdso'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x7f9b3c09226b in ?? ()

  Thread 1 (LWP 1501):
  #0  0x7f9b3c09226b in ?? ()
  Backtrace stopped: Cannot access memory at address 0x7ffc216242b0
  vma05 1 TFAIL: [vdso] bug not patched
  vma05 2 TINFO: AppArmor enabled, this may affect test results
  vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires 
super/root)
  vma05 2 TINFO: loaded AppArmor profiles: none

  Suggesting that this bug has somehow been reintroduced. Will look into
  this further.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1999094/+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 1995957] Re: Add cs35l41 firmware loading support

This bug is awaiting verification that the linux-oem-5.17/5.17.0-1025.26
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' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

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 removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-oem-5.17 verification-needed-jammy

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

Title:
  Add cs35l41 firmware loading support

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  New
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-firmware source package in Kinetic:
  Fix Released
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  Speakers on some laptops are rather quiet even with max volume.

  [Fix]
  Loading firmware to make cs35l41 speaker amplifier really work.

  [Test]
  With the fix applied, the speaker has become really loud as intended.

  [Where problems could occur]
  Most commits are refactoring codes on both ASoC and HDA parts, so things
  can be missed.

  Other than that, the change is strictly limited to cs35l41, so the
  regression scope is rather narrow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1995957/+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 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

This bug is awaiting verification that the linux-oem-5.17/5.17.0-1025.26
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' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

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

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991366/+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 1993563] Re: support for same series backports versioning numbers

This bug is awaiting verification that the linux-oem-5.17/5.17.0-1025.26
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' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

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-oem-5.17 verification-needed-jammy

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

Title:
  support for same series backports versioning numbers

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed

Bug description:
  packaging support for sameport versioning numbers

  Allow generating kernel packages, that use backports mechanism within
  the same series. For example linux-lowlatancy linux-riscv.

  Those kernels already have customized packaging to achieve the above,
  this is introducing standard support for this in the main kernels for
  jammy and kinetic series.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993563/+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 1978986] Re: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average luminance

This bug is awaiting verification that the linux-oem-5.17/5.17.0-1025.26
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' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

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

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

Title:
  [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-
  average luminance

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-5.14 source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  The brightness is not changed obviously during 200 to 255 on AMD
  or 400 to 512 on Intel..

  [Fix]
  Read HDR meta to detect the max and min luminance.
  max_cll defines the content light luminance for individual pixel.
  max_fall defines frame-average level luminance.
  Use max_fall value instead of max_cll as a limit for brightness control.

  [Test]
  Verified on AMD Cezanne, Barcelo, Rembrandt and Intel ADL, also on LCD panel 
and OLED panel. The brightness is changed more obivously on OLED panel, and
  no affect on LCD panel.

  [Where problems could occur]
  Low risk, It may cause the max brightness can't be set.

  All 3 patches are in drm-misc tree.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1978986/+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 1995041] Re: Fix ath11k deadlock on WCN6855

This bug is awaiting verification that the linux-oem-5.17/5.17.0-1025.26
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' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

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

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

Title:
  Fix ath11k deadlock on WCN6855

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  ath11k is in deadlock when stress reboot or suspend on WCN6855.
  sometimes kernel hang.

  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Call Trace:
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: 
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __schedule+0x240/0x5a0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? resched_curr+0x52/0xc0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule+0x55/0xd0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule_timeout+0x115/0x150
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? raw_spin_rq_unlock+0x10/0x30
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? try_to_wake_up+0x211/0x600
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_ce_send+0x17a/0x2e0 [ath11k]
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: wait_for_completion+0x8b/0xf0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __flush_work.isra.0+0x171/0x270
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? flush_workqueue_prep_pwqs+0x140/0x140
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __cancel_work_timer+0x11b/0x1a0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? 
ath11k_mac_config_mon_status_default+0xcc/0x170 [ath11k]
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: cancel_work_sync+0x10/0x20
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ath11k_mac_op_stop+0x9f/0x1e0 [ath11k]
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: drv_stop+0x45/0x110 [mac80211]

  [Fix]
  Fix this by switching from using regulatory_set_wiphy_regd_sync() to
  regulatory_set_wiphy_regd(). Now cfg80211 will schedule another workqueue 
which
  handles the locking on it's own. So the ath11k workqueue can simply exit 
without
  taking any locks, avoiding the deadlock.

  [Test]
  Verified on hardware, stress reboot and suspend 30 times OK.

  [Where problems could occur]
  It may break ath11k wifi driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1995041/+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 1995573] Re: Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536]

This bug is awaiting verification that the linux-oem-5.17/5.17.0-1025.26
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' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

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-oem-5.17 verification-needed-jammy

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

Title:
  Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-5.17 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  Screen cannot turn on after screen is off

  [Fix]
  Below commit from v6.0-rc1 fixes the issue
  c577b2f43e80 drm/mgag200: Enable atomic gamma lut update

  And applied some other commits to fix the conflicts
  c48a36301634 drm/mgag200: Optimize damage clips
  3064debaf55e drm/mgag200: Add FB_DAMAGE_CLIPS support
  5913ab941d6e drm/mgag200: Acquire I/O lock while reading EDID
  931e3f3a0e99 drm/mgag200: Protect concurrent access to I/O registers with lock
  e13f13e039dc drm: Add DRM-managed mutex_init()

  [Tests]
  Verified on the machine with Matrox G200eW3 [102b:0536] graphics card.

  [Where problems could occur]
  The commits to solve the conflicts are trivial, and not likely to introduce 
regressions. The fix patch change a lot of code and hard to evaluate the risk, 
but check the latest linus/master tree and linux-next/master tree, there is no 
fixed commit for all these cherry-picked commits, so should be safe to include 
them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1995573/+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 1991608] Re: TEE Support for CCP driver

This bug is awaiting verification that the linux-oem-5.17/5.17.0-1025.26
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' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

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

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

Title:
  TEE Support for CCP driver

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  In Progress
Status in linux-oem-5.17 source package in Lunar:
  Invalid
Status in linux-oem-6.0 source package in Lunar:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  Missing support for of AMD Secure Processor device for PCI ID 0x14CA.

  [Fix]

  A patch is being proposed in upstream and CC-ed stable.

  [Test Case]

  Without a proper fix, following error appears in dmesg:

ccp :02:00.5: tee: missing driver data
ccp :02:00.5: tee initialization failed

  [Where problems could occur]

  This adds a new driver data entry to support ccp device that provides
  both sev and tee feature at the same time.

  [Other Info]

  While this is proposed to stable 5.15+, all kernels >= 5.15 are
  nominated for fix.

  == original bug description ==

  Client and datacenter Zen4 SOC same PCI-ID but offer different
  functionality from the PSP.

  Genoa offers SEV, Client part offers TEE.
  This patch fixes an ERR level message and CCP driver functionality not 
working.

  ccp :02:00.5: tee: missing driver data
  ccp :02:00.5: tee initialization failed

  https://lore.kernel.org/linux-
  
crypto/20220928184506.13981-1-mario.limoncie...@amd.com/T/#m1b933ea4b961d17cb1be5be74e2d22a860507ca0

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991608/+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 1996048] Re: Screen freeze after resuming from suspend (nvme0: I/O timeout)

This bug is awaiting verification that the linux-oem-5.17/5.17.0-1025.26
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' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

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 removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-oem-5.17 verification-needed-jammy

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

Title:
  Screen freeze after resuming from suspend (nvme0: I/O timeout)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  In Progress
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  In Progress
Status in linux-oem-5.17 source package in Lunar:
  Invalid
Status in linux-oem-6.0 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  The system hangs after S3 with VMD mode is on.

  [Fix]
  Intel provides a fix and still under discussion
  
https://patchwork.kernel.org/project/linux-pci/patch/20221107182735.381552-1-francisco.munoz.r...@linux.intel.com/

  The patch is not finalized, so submit SRU to OEM kernels only, and
  will submit to other series kernels once the patch is accepted by
  upstream.

  [Test]
  Verified by us and ODM.

  [Where problems could occur]
  The VMCONFIG_MSI_REMAP bit is missing after S3, set it back won't lead to any 
regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1996048/+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 1998883] Re: Micron NVME storage failure [1344, 5407]

This bug is awaiting verification that the linux-oem-5.17/5.17.0-1025.26
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' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

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-oem-5.17 verification-needed-jammy

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

Title:
  Micron NVME storage failure [1344,5407]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  Micron NVME storage fails to init with below error messages
  [ 8.965698] nvme nvme1: Duplicate cntlid 0 with nvme0, subsys 
nqn.2014-08.org.nvmexpress:uuid:834ae34b-0ef0-8a48-ac5a-3006545c2b7f, rejecting
  [ 8.966111] nvme nvme1: Removing after probe failure status: -22

  [Fix]
  The patch from v5.19 add a quirk for Micron NVME fixes this issue
 41f38043f884 nvme: add a bogus subsystem NQN quirk for Micron MTFDKBA2T0TFH

  [Test]
  Verified with 5.17 OEM kernel on the reported machine.
  Didn't verify with 5.15 Jammy kernel, but confirmed the kernel could be 
compiled.

  [Where problems could occur]
  The impact should be low as it adds one device ID into a quirk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1998883/+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 1997200] Re: Mediatek WLAN RZ616(MT7922) SAR table control

This bug is awaiting verification that the linux-oem-5.17/5.17.0-1025.26
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' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

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-oem-5.17 verification-needed-jammy

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

Title:
  Mediatek WLAN RZ616(MT7922) SAR table control

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-firmware source package in Kinetic:
  Fix Committed
Status in linux-oem-5.17 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  In order to make sure the amount of RF energy being absorbed by our bodies is 
safe according to the FCC’s guidelines, products must undergo and pass SAR 
testing.

  [Fix]
  Add ACPI SAR table control to pass the testing.

  [Test]
  the unit is 0.5dBm in following:

  Without the SAR table control:
  $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user
  CCK (user)  :N.AN.AN.AN.A
  OFDM (user) : 40 40 40 40 40 40 40 40
  HT20 (user) : 40 40 40 40 40 40 40 40
  HT40 (user) : 40 40 40 40 40 40 40 40 
40
  VHT20 (user): 40 40 40 40 40 40 40 40 
40 40  0  0
  VHT40 (user): 40 40 40 40 40 40 40 40 
40 40  0  0
  VHT80 (user): 40 40 40 40 40 40 40 40 
40 40  0  0
  VHT160 (user)   : 40 40 40 40 40 40 40 40 
40 40  0  0
  HE26 (user) : 40 40 40 40 40 40 40 40 
40 40 40 40
  HE52 (user) : 40 40 40 40 40 40 40 40 
40 40 40 40
  HE106 (user): 40 40 40 40 40 40 40 40 
40 40 40 40
  HE242 (user): 40 40 40 40 40 40 40 40 
40 40 40 40
  HE484 (user): 40 40 40 40 40 40 40 40 
40 40 40 40
  HE996 (user): 40 40 40 40 40 40 40 40 
40 40 40 40
  HE996x2 (user)  : 40 40 40 40 40 40 40 40 
40 40 40 40

  After enabled SAR table control:
  $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user
  CCK (user)  :N.AN.AN.AN.A
  OFDM (user) : 26 26 26 26 26 26 26 26
  HT20 (user) : 26 26 26 26 26 26 26 26
  HT40 (user) : 26 26 26 26 26 26 26 26 
26
  VHT20 (user): 26 26 26 26 26 26 26 26 
26 26  0  0
  VHT40 (user): 26 26 26 26 26 26 26 26 
26 26  0  0
  VHT80 (user): 26 26 26 26 26 26 26 26 
26 26  0  0
  VHT160 (user)   : 26 26 26 26 26 26 26 26 
26 26  0  0
  HE26 (user) : 26 26 26 26 26 26 26 26 
26 26 26 26
  HE52 (user) : 26 26 26 26 26 26 26 26 
26 26 26 26
  HE106 (user): 26 26 26 26 26 26 26 26 
26 26 26 26
  HE242 (user): 26 26 26 26 26 26 26 26 
26 26 26 26
  HE484 (user): 26 26 26 26 26 26 26 26 
26 26 26 26
  HE996 (user): 26 26 26 26 26 26 26 26 
26 26 26 26
  HE996x2 (user)  : 26 26 26 26 26 26 26 26 
26 26 26 26

  Also done stress test with iperf, all works fine.

  [Where problems could occur]
  It

[Kernel-packages] [Bug 1998106] Re: Fix AMD-PState driver for Genoa CPU

This bug is awaiting verification that the linux-oem-5.17/5.17.0-1025.26
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' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

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-oem-5.17 verification-needed-jammy

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

Title:
  Fix AMD-PState driver for Genoa CPU

Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Committed
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-5.14 source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid

Bug description:
  [Impact]

  During AMD Genoa development, the datacenter team identified
  performance regressions that were root caused in the amd-pstate
  driver. A first round of fixes already landed upstream (v6.1-rc7) in
  the amd-pstate driver, and should be backported to all the affected
  kernels.

  [Fix]

  Backport the upstream amd-pstate fixes:

  https://lore.kernel.org/linux-
  
pm/20221117073541.3350600-1-perry.y...@amd.com/T/#m4616d857ca472937d1e1d31131ddc3261fa17b2a

  [Regression potential]

  Clean cherry-picks of already upstream (v6.1-rc7) fixes, impact a
  single driver (amd-pstate) and the new mode (passive) is disabled by
  default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998106/+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 1998905] Re: Rear Audio port sometimes has no audio output after reboot(Cirrus Logic)

This bug is awaiting verification that the linux-oem-5.17/5.17.0-1025.26
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' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

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-oem-5.17 verification-needed-jammy

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

Title:
  Rear Audio port sometimes has no audio output after reboot(Cirrus
  Logic)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.17 source package in Jammy:
  In Progress
Status in linux-oem-6.0 source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  In Progress
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  In Progress
Status in linux-oem-5.17 source package in Lunar:
  Invalid
Status in linux-oem-6.0 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  On the development, we found sometimes there is no audio output device when 
headphone is connected to the rear audio jack.

  [Fix]
  Cirrus Logic provides a patch to fix this
  
https://patchwork.kernel.org/project/alsa-devel/patch/20221205145713.23852-1-vita...@opensource.cirrus.com/

  The patch has been accepted but still not shown in the upstream tree,
  so submit this patch to oem kernels first, and will submit it to other
  generic ubuntu kernels.

  [Test]
  Verified by our QA and ODM.

  [Where problems could occur]
  It extends the delay time, should be no harm for existing platforms.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1998905/+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 1999094] [NEW] mm:vma05 fails with '[vdso] bug not patched' on kinetic/linux 5.19.0-27.28

2022-12-07 Thread Luke Nowakowski-Krijger

Public bug reported:

This test fails on 5.19.0-27.28 in cycle 2022.11.14 on most if not all
instances.

Running tests...
vma05 1 TINFO: timeout per run is 0h 5m 0s
vma05 1 TFAIL: [vdso] bug not patched
vma05 2 TINFO: AppArmor enabled, this may affect test results
vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires 
super/root)
vma05 2 TINFO: loaded AppArmor profiles: none

Looking at the contents of the triggered backtrace, on 5.19.0-26 the
contents look like this:

vma05 1 TPASS: [vsyscall] reported correctly
vma05 1 TINFO: TRACE=Reading symbols from vma05_vdso...
[New LWP 418325]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `vma05_vdso'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  __pthread_kill_implementation (no_tid=0, signo=11, 
threadid=) at ./nptl/pthread_kill.c:44

Thread 1 (Thread 0x7f3093c4e740 (LWP 418325)):
#0  __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44
#1  __pthread_kill_internal (signo=11, threadid=) at 
./nptl/pthread_kill.c:78
#2  __GI___pthread_kill (threadid=, signo=signo@entry=11) at 
./nptl/pthread_kill.c:89
#3  0x7f3093a3bc46 in __GI_raise (sig=sig@entry=11) at 
../sysdeps/posix/raise.c:26
#4  0x55f54287a072 in main () at vma05_vdso.c:5
vma05 1 TPASS: [vdso] backtrace complete


while on 5.19.0-27.28 it looks like this:
vma05 1 TINFO: TRACE=Reading symbols from vma05_vdso...
[New LWP 1501]
Core was generated by `vma05_vdso'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f9b3c09226b in ?? ()

Thread 1 (LWP 1501):
#0  0x7f9b3c09226b in ?? ()
Backtrace stopped: Cannot access memory at address 0x7ffc216242b0
vma05 1 TFAIL: [vdso] bug not patched
vma05 2 TINFO: AppArmor enabled, this may affect test results
vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires 
super/root)
vma05 2 TINFO: loaded AppArmor profiles: none

Suggesting that this bug has somehow been reintroduced. Will look into
this further.

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

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

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

** Also affects: ubuntu
   Importance: Undecided
   Status: New

** No longer affects: ubuntu

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

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

Title:
   mm:vma05 fails with '[vdso] bug not patched' on kinetic/linux
  5.19.0-27.28

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Kinetic:
  New

Bug description:
  This test fails on 5.19.0-27.28 in cycle 2022.11.14 on most if not all
  instances.

  Running tests...
  vma05 1 TINFO: timeout per run is 0h 5m 0s
  vma05 1 TFAIL: [vdso] bug not patched
  vma05 2 TINFO: AppArmor enabled, this may affect test results
  vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires 
super/root)
  vma05 2 TINFO: loaded AppArmor profiles: none

  Looking at the contents of the triggered backtrace, on 5.19.0-26 the
  contents look like this:

  vma05 1 TPASS: [vsyscall] reported correctly
  vma05 1 TINFO: TRACE=Reading symbols from vma05_vdso...
  [New LWP 418325]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `vma05_vdso'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  __pthread_kill_implementation (no_tid=0, signo=11, 
  threadid=) at ./nptl/pthread_kill.c:44

  Thread 1 (Thread 0x7f3093c4e740 (LWP 418325)):
  #0  __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44
  #1  __pthread_kill_internal (signo=11, threadid=) at 
./nptl/pthread_kill.c:78
  #2  __GI___pthread_kill (threadid=, signo=signo@entry=11) at 
./nptl/pthread_kill.c:89
  #3  0x7f3093a3bc46 in __GI_raise (sig=sig@entry=11) at 
../sysdeps/posix/raise.c:26
  #4  0x55f54287a072 in main () at vma05_vdso.c:5
  vma05 1 TPASS: [vdso] backtrace complete

  
  while on 5.19.0-27.28 it looks like this:
  vma05 1 TINFO: TRACE=Reading symbols from vma05_vdso...
  [New LWP 1501]
  Core was generated by `vma05_vdso'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x7f9b3c09226b in ?? ()

  Thread 1 (LWP 1501):
  #0  0x7f9b3c09226b in ?? ()
  Backtrace stopped: Cannot access memory at address 0x7ffc216242b0
  vma05 1 TFAIL: [vdso] bug not patched
  vma05 2 TINFO: AppArmor enabled, this may affect test results
  vma05 2 TINFO: it can be disabled with

[Kernel-packages] [Bug 1990920] Re: Fix resume on AMD platforms when TBT monitor is plugged

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

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

Title:
  Fix resume on AMD platforms when TBT monitor is plugged

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-5.14 source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  When TBT monitor is connected to AMD platform, system resume will hit
  stack corruption or BUG_ON() macro.

  [Fix]
  Revert the offending commit and handle MST properly.

  [Test]
  The system can resume normally and no more kernel splat.
   
  [Where problems could occur]
  The new logic is restriced to MST hub, so normal DP/HDMI usage should be
  unaffected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1990920/+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 352556] Re: [REGRESSION] Mobo Asus P5Q * needs newer Alsa to work again SPDIF

2022-12-07 Thread Paul White

alsa-driver task did not expire due to assignment
Last comment re issue was in 2009
No reply to comment #16 after over two years so closing

** Changed in: alsa-driver (Ubuntu)
 Assignee: Ubuntu Audio Team (ubuntu-audio) => (unassigned)

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  [REGRESSION] Mobo Asus P5Q * needs newer Alsa to work again SPDIF

Status in alsa-driver package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Expired

Bug description:
  I upgraded to Jaunty and the alsa provided doesn't work with the
  integrated chip:

  82801JI (ICH10 Family) HD Audio

  The fix is to compile by yourself alsa and force "options snd-hda-intel 
model=6stack-dig" in
  /etc/modprobe.d/alsa-base.conf

  please see: http://ubuntuforums.org/showthread.php?t=1100747

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/352556/+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 1990985] Re: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems

2022-12-07 Thread Kim Naru

** Tags removed: kernel-spammed-bionic-linux-azure-4.15 
kernel-spammed-jammy-linux-bluefield kernel-spammed-kinetic-linux 
verification-needed-bionic verification-needed-jammy verification-needed-kinetic
** Tags added: verification- verification-done-jammy

** Tags removed: verification-

** Tags added: verification-done-bionic

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

Title:
  ACPI: processor idle: Practically limit "Dummy wait" workaround to old
  Intel systems

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed

Bug description:
  IMPACT:
  Old, circa 2002 chipsets have a bug: they don't go idle when they are
  supposed to.  So, a workaround was added to slow the CPU down and
  ensure that the CPU waits a bit for the chipset to actually go idle.
  This workaround is ancient and has been in place in some form since
  the original kernel ACPI implementation.

  But, this workaround is very painful on modern systems.  The "inl()"
  can take thousands of cycles (see Link: for some more detailed
  numbers and some fun kernel archaeology).

  First and foremost, modern systems should not be using this code.
  Typical Intel systems have not used it in over a decade because it is
  horribly inferior to MWAIT-based idle.

  Despite this, people do seem to be tripping over this workaround on
  AMD system today.

  Limit the "dummy wait" workaround to Intel systems.  Keep Modern AMD
  systems from tripping over the workaround.  Remotely modern Intel
  systems use intel_idle instead of this code and will, in practice,
  remain unaffected by the dummy wait.

  Reported-by: K Prateek Nayak 
  Suggested-by: Rafael J. Wysocki 
  Signed-off-by: Dave Hansen 
  Reviewed-by: Mario Limonciello 
  Tested-by: K Prateek Nayak 
  Link: 
https://lore.kernel.org/all/20220921063638.2489-1-kprateek.na...@amd.com/
  Link: https://lkml.kernel.org/r/20220922184745.3252932-1-dave.han...@intel.com

  FIX:

  This issue pertains to  all Zen based processors starting with
  Naples(Zen1). All LTS releases will need this fix:

  
https://github.com/torvalds/linux/commit/e400ad8b7e6a1b9102123c6240289a811501f7d9

  TESTCASE:

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-hwe-5.15/5.15.0.57.63~20.04.23)

2022-12-07 Thread Ubuntu SRU Bot

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

systemd/unknown (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-meta-hwe-5.15

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Won't Fix
Status in linux-azure-edge source package in Precise:
  Won't Fix
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1999079] Re: Kinetic update: upstream stable patchset 2022-12-07

2022-12-07 Thread Kamal Mostafa

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    upstream stable patchset 2022-12-07
+    from git://git.kernel.org/
  
-upstream stable patchset 2022-12-07
-from git://git.kernel.org/
+ can: j1939: transport: j1939_session_skb_drop_old(): spin_unlock_irqrestore() 
before kfree_skb()
+ can: kvaser_usb: Fix possible completions during init_completion
+ ALSA: Use del_timer_sync() before freeing timer
+ ALSA: usb-audio: Add quirks for M-Audio Fast Track C400/600
+ ALSA: au88x0: use explicitly signed char
+ ALSA: rme9652: use explicitly signed char
+ USB: add RESET_RESUME quirk for NVIDIA Jetson devices in RCM
+ usb: gadget: uvc: fix sg handling in error case
+ usb: gadget: uvc: fix sg handling during video encode
+ usb: dwc3: gadget: Stop processing more requests on IMI
+ usb: dwc3: gadget: Don't set IMI for no_interrupt
+ usb: bdc: change state when port disconnected
+ usb: xhci: add XHCI_SPURIOUS_SUCCESS to ASM1042 despite being a V0.96 
controller
+ mtd: rawnand: marvell: Use correct logic for nand-keep-config
+ xhci: Add quirk to reset host back to default state at shutdown
+ xhci-pci: Set runtime PM as default policy on all xHC 1.2 or later devices
+ xhci: Remove device endpoints from bandwidth list when freeing the device
+ tools: iio: iio_utils: fix digit calculation
+ iio: light: tsl2583: Fix module unloading
+ iio: temperature: ltc2983: allocate iio channels once
+ iio: adxl372: Fix unsafe buffer attributes
+ fbdev: smscufx: Fix several use-after-free bugs
+ cpufreq: intel_pstate: Read all MSRs on the target CPU
+ cpufreq: intel_pstate: hybrid: Use known scaling factor for P-cores
+ fs/binfmt_elf: Fix memory leak in load_elf_binary()
+ exec: Copy oldsighand->action under spin-lock
+ mac802154: Fix LQI recording
+ scsi: qla2xxx: Use transport-defined speed mask for supported_speeds
+ drm/amdgpu: disallow gfxoff until GC IP blocks complete s2idle resume
+ drm/msm/dsi: fix memory corruption with too many bridges
+ drm/msm/hdmi: fix memory corruption with too many bridges
+ drm/msm/dp: fix IRQ lifetime
+ coresight: cti: Fix hang in cti_disable_hw()
+ mmc: sdhci_am654: 'select', not 'depends' REGMAP_MMIO
+ mmc: core: Fix kernel panic when remove non-standard SDIO card
+ mmc: sdhci-pci-core: Disable ES for ASUS BIOS on Jasper Lake
+ mmc: sdhci-esdhc-imx: Propagate ESDHC_FLAG_HS400* only on 8bit bus
+ counter: microchip-tcb-capture: Handle Signal1 read and Synapse
+ kernfs: fix use-after-free in __kernfs_remove
+ pinctrl: Ingenic: JZ4755 bug fixes
+ ARC: mm: fix leakage of memory allocated for PTE
+ perf auxtrace: Fix address filter symbol name match for modules
+ s390/futex: add missing EX_TABLE entry to __futex_atomic_op()
+ s390/pci: add missing EX_TABLE entries to 
__pcistg_mio_inuser()/__pcilg_mio_inuser()
+ mmc: block: Remove error check of hw_reset on reset
+ ethtool: eeprom: fix null-deref on genl_info in dump
+ net: ieee802154: fix error return code in dgram_bind()
+ media: v4l2: Fix v4l2_i2c_subdev_set_name function documentation
+ media: atomisp: prevent integer overflow in sh_css_set_black_frame()
+ drm/msm: Fix return type of mdp4_lvds_connector_mode_valid
+ KVM: selftests: Fix number of pages for memory slot in 
memslot_modification_stress_test
+ ASoC: qcom: lpass-cpu: mark HDMI TX registers as volatile
+ perf: Fix missing SIGTRAPs
+ sched/core: Fix comparison in sched_group_cookie_match()
+ arc: iounmap() arg is volatile
+ mtd: rawnand: intel: Add missing of_node_put() in ebu_nand_probe()
+ ASoC: qcom: lpass-cpu: Mark HDMI TX parity register as volatile
+ ALSA: ac97: fix possible memory leak in snd_ac97_dev_register()
+ perf/x86/intel/lbr: Use setup_clear_cpu_cap() instead of clear_cpu_cap()
+ tipc: fix a null-ptr-deref in tipc_topsrv_accept
+ net: netsec: fix error handling in netsec_register_mdio()
+ net: hinic: fix incorrect assignment issue in hinic_set_interrupt_cfg()
+ net: hinic: fix memory leak when reading function table
+ net: hinic: fix the issue of CMDQ memory leaks
+ net: hinic: fix the issue of double release MBOX callback of VF
+ net: macb: Specify PHY PM

[Kernel-packages] [Bug 1999079] Re: Kinetic update: upstream stable patchset 2022-12-07

2022-12-07 Thread Kamal Mostafa

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

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

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

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

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

Title:
  Kinetic update: upstream stable patchset 2022-12-07

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

Bug description:
  SRU Justification

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

     upstream stable patchset 2022-12-07

  Ported from the following upstream stable releases:
  v5.15.77, v6.0.7

     from git://git.kernel.org/

  can: j1939: transport: j1939_session_skb_drop_old(): spin_unlock_irqrestore() 
before kfree_skb()
  can: kvaser_usb: Fix possible completions during init_completion
  ALSA: Use del_timer_sync() before freeing timer
  ALSA: usb-audio: Add quirks for M-Audio Fast Track C400/600
  ALSA: au88x0: use explicitly signed char
  ALSA: rme9652: use explicitly signed char
  USB: add RESET_RESUME quirk for NVIDIA Jetson devices in RCM
  usb: gadget: uvc: fix sg handling in error case
  usb: gadget: uvc: fix sg handling during video encode
  usb: dwc3: gadget: Stop processing more requests on IMI
  usb: dwc3: gadget: Don't set IMI for no_interrupt
  usb: bdc: change state when port disconnected
  usb: xhci: add XHCI_SPURIOUS_SUCCESS to ASM1042 despite being a V0.96 
controller
  mtd: rawnand: marvell: Use correct logic for nand-keep-config
  xhci: Add quirk to reset host back to default state at shutdown
  xhci-pci: Set runtime PM as default policy on all xHC 1.2 or later devices
  xhci: Remove device endpoints from bandwidth list when freeing the device
  tools: iio: iio_utils: fix digit calculation
  iio: light: tsl2583: Fix module unloading
  iio: temperature: ltc2983: allocate iio channels once
  iio: adxl372: Fix unsafe buffer attributes
  fbdev: smscufx: Fix several use-after-free bugs
  cpufreq: intel_pstate: Read all MSRs on the target CPU
  cpufreq: intel_pstate: hybrid: Use known scaling factor for P-cores
  fs/binfmt_elf: Fix memory leak in load_elf_binary()
  exec: Copy oldsighand->action under spin-lock
  mac802154: Fix LQI recording
  scsi: qla2xxx: Use transport-defined speed mask for supported_speeds
  drm/amdgpu: disallow gfxoff until GC IP blocks complete s2idle resume
  drm/msm/dsi: fix memory corruption with too many bridges
  drm/msm/hdmi: fix memory corruption with too many bridges
  drm/msm/dp: fix IRQ lifetime
  coresight: cti: Fix hang in cti_disable_hw()
  mmc: sdhci_am654: 'select', not 'depends' REGMAP_MMIO
  mmc: core: Fix kernel panic when remove non-standard SDIO card
  mmc: sdhci-pci-core: Disable ES for ASUS BIOS on Jasper Lake
  mmc: sdhci-esdhc-imx: Propagate ESDHC_FLAG_HS400* only on 8bit bus
  counter: microchip-tcb-capture: Handle Signal1 read and Synapse
  kernfs: fix use-after-free in __kernfs_remove
  pinctrl: Ingenic: JZ4755 bug fixes
  ARC: mm: fix leakage of memory allocated for PTE
  perf auxtrace: Fix address filter symbol name match for modules
  s390/futex: add missing EX_TABLE entry to __futex_atomic_op()
  s390/pci: add missing EX_TABLE entries to 
__pcistg_mio_inuser()/__pcilg_mio_inuser()
  mmc: block: Remove error check of hw_reset on reset
  ethtool: eeprom: fix null-deref on genl_info in dump
  net: ieee802154: fix error return code in dgram_bind()
  media: v4l2: Fix v4l2_i2c_subdev_set_name function documentation
  media: atomisp: prevent integer overflow in sh_css_set_black_frame()
  drm/msm: Fix return type of mdp4_lvds_connector_mode_valid
  KVM: selftests: Fix number of pages for memory slot in 
memslot_modification_stress_test
  ASoC: qcom: lpass-cpu: mark HDMI TX registers as volatile
  perf: Fix missing SIGTRAPs
  sched/core: Fix comparison in sched_group_cookie_match()
  arc: iounmap() arg is volatile
  mtd: rawnand: intel: Add missing of_node_put() in ebu_nand_probe()
  ASoC: qcom: lpass-cpu: Mark HDMI TX parity register as volatile
  ALSA: ac97: fix possible memory leak in snd_ac97_dev_register()
  perf/x86/intel/lbr: Use setup_clear_cpu_cap() instead of clear_cpu_cap()
  tipc: fix a null-ptr-deref in tipc_topsrv_accept
  net: netsec: fix error handling in netsec_register_mdio()
  net: hinic: fix incorrect assignment issue in hinic_set_interrupt_cfg()

[Kernel-packages] [Bug 1995528] Re: Focal update: v5.4.217 upstream stable release

2022-12-07 Thread Andy Whitcroft

** Tags removed: kernel-spammed-focal-linux

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

Title:
  Focal update: v5.4.217 upstream stable release

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

Bug description:
  SRU Justification

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

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

  xfs: fix misuse of the XFS_ATTR_INCOMPLETE flag
  xfs: introduce XFS_MAX_FILEOFF
  xfs: truncate should remove all blocks, not just to the end of the page cache
  xfs: fix s_maxbytes computation on 32-bit kernels
  xfs: fix IOCB_NOWAIT handling in xfs_file_dio_aio_read
  xfs: refactor remote attr value buffer invalidation
  xfs: fix memory corruption during remote attr value buffer invalidation
  xfs: move incore structures out of xfs_da_format.h
  xfs: streamline xfs_attr3_leaf_inactive
  xfs: fix uninitialized variable in xfs_attr3_leaf_inactive
  xfs: remove unused variable 'done'
  Makefile.extrawarn: Move -Wcast-function-type-strict to W=1
  docs: update mediator information in CoC docs
  Linux 5.4.217
  UBUNTU: Upstream stable to v5.4.217

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995528/+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 1998154] Re: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive

2022-12-07 Thread Steve Langasek

Promoting gcc-12 and cpp-12 binaries was sufficient to fix this.

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

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

Title:
  dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under
  universe archive

Status in OEM Priority Project:
  New
Status in dkms package in Ubuntu:
  Invalid

Bug description:
  [Description]

  The latest dkms(2.8.7-2ubuntu2.1) depends on gcc-12 which is in
  universe archive.

  https://packages.ubuntu.com/search?keywords=gcc-12
  gcc-12 is under main for kinect, and the patches are cherry-picked from 
kinect/stable, I suppose it is a mistake for jammy in universe.

  [debian/changelog]

  dkms (2.8.7-2ubuntu2.1) jammy; urgency=medium

  Cherry-pick patches from kinetic/stable to address building dkms
  modules correctly for HWE kernels (LP: #1991664):

  Fix dkms-autopkgtest when a given dkms package is built into the
  kernel already of the same version. (i.e. zfs-linux on Ubuntu).

  Use exact compiler for dkms as used to build the kernel, when
  possible.

  Depend on gcc-12 to build modules for HWE kernels correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1998154/+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 1970495] Re: Window manager freezes when plugging in USB-C dock with external monitor ([drm] ERROR mstb 00000000f21f0a30 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed)

2022-12-07 Thread Valentijn Sessink

My Thinkpad X1 gen 6 with Ubuntu 22.04, Lenovo 40AJ dock with 4K LG
monitor with DP cable, will sometimes just show 2 or 4 lines with "DPCD
read on addr 0x4b0 for 1 bytes NAKed", after which the system will just
continue to work. But sometimes the "1 bytes NAKed" messages just keep
running - which is when the session will crash, eventually.

If I connect the dock with the laptop LCD on, the "1 bytes NAKed" will
freeze the LCD. When I'm fast enough to disconnect the DP cable, the LCD
unfreezes. However, reconnecting the DP will re-freeze the LCD.

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

Title:
  Window manager freezes when plugging in USB-C dock with external
  monitor ([drm] *ERROR* mstb f21f0a30 port 1: DPCD read on addr
  0x4b0 for 1 bytes NAKed)

Status in GNOME Shell:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  1. Problem DOES appear on Lenovo T470s (Intel).
  2. Problem DOES appear on Lenovo T14 Gen2 (AMD).
  3. Problem does NOT appear on either of the above *when in the Live 
Installer*.

  I specifically checked that my dock behaved well under the Live
  Installer before deciding to move my workstations to Jammy. Upon
  logging into a fresh Jammy install, I found the following problem
  behavior: When the dock is plugged in, the built-in display freezes
  and the dock-attached displays power up but never render anything (ie,
  they stay black). Unplugging the USB-C cable gets mouse/keyboard
  response back on the built-in display.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 18:32:35 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1970495/+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 1999082] [NEW] linux-modules-nvidia-510-server fails to install

2022-12-07 Thread Ian May

Public bug reported:

$ sudo apt install linux-modules-nvidia-510-server-$(uname -r)
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 linux-modules-nvidia-510-server-5.4.0-135-generic : Depends: 
linux-signatures-nvidia-5.4.0-135-generic (= 5.4.0-135.152) but 5.4.0-135.152+1 
is to be installed
 Depends: 
nvidia-kernel-common-510-server (<= 510.85.02-1) but it is not going to be 
installed
 Depends: 
nvidia-kernel-common-510-server (>= 510.85.02) but it is not going to be 
installed
E: Unable to correct problems, you have held broken packages.


$ lsb_release -rd
Description:Ubuntu 20.04.5 LTS
Release:20.04

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

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

Title:
  linux-modules-nvidia-510-server fails to install

Status in nvidia-graphics-drivers-510-server package in Ubuntu:
  New

Bug description:
  $ sudo apt install linux-modules-nvidia-510-server-$(uname -r)
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   linux-modules-nvidia-510-server-5.4.0-135-generic : Depends: 
linux-signatures-nvidia-5.4.0-135-generic (= 5.4.0-135.152) but 5.4.0-135.152+1 
is to be installed
   Depends: 
nvidia-kernel-common-510-server (<= 510.85.02-1) but it is not going to be 
installed
   Depends: 
nvidia-kernel-common-510-server (>= 510.85.02) but it is not going to be 
installed
  E: Unable to correct problems, you have held broken packages.

  
  $ lsb_release -rd
  Description:  Ubuntu 20.04.5 LTS
  Release:  20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510-server/+bug/1999082/+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 1998154] Re: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive

2022-12-07 Thread Steve Langasek

Because gcc-12 source is in main already, *and* is already published in
jammy-{security,updates}, it seems it is straightforward to simply
promote the binaries to solve this problem.

I'll work on this; it may take a couple of rounds to get all the
dependencies promoted.

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

Title:
  dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under
  universe archive

Status in OEM Priority Project:
  New
Status in dkms package in Ubuntu:
  Confirmed

Bug description:
  [Description]

  The latest dkms(2.8.7-2ubuntu2.1) depends on gcc-12 which is in
  universe archive.

  https://packages.ubuntu.com/search?keywords=gcc-12
  gcc-12 is under main for kinect, and the patches are cherry-picked from 
kinect/stable, I suppose it is a mistake for jammy in universe.

  [debian/changelog]

  dkms (2.8.7-2ubuntu2.1) jammy; urgency=medium

  Cherry-pick patches from kinetic/stable to address building dkms
  modules correctly for HWE kernels (LP: #1991664):

  Fix dkms-autopkgtest when a given dkms package is built into the
  kernel already of the same version. (i.e. zfs-linux on Ubuntu).

  Use exact compiler for dkms as used to build the kernel, when
  possible.

  Depend on gcc-12 to build modules for HWE kernels correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1998154/+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 1818228] Missing required logs.

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

apport-collect 1818228

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

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

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

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

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

Title:
  thunderbolt

Status in linux package in Ubuntu:
  Incomplete
Status in thunderbolt-tools package in Ubuntu:
  New

Bug description:
  [   51.501462] [ cut here ]
  [   51.501465] thunderbolt :08:00.0: interrupt for TX ring 0 is already 
disabled
  [   51.501480] WARNING: CPU: 4 PID: 82 at 
/build/linux-uQJ2um/linux-4.15.0/drivers/thunderbolt/nhi.c:106 
ring_interrupt_active+0x20c/0x270 [thunderbolt]
  [   51.501481] Modules linked in: rfcomm ccm thunderbolt cmac bnep arc4 
snd_hda_codec_hdmi nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic 
hid_multitouch dell_wmi dell_laptop dell_smbios wmi_bmof intel_wmi_thunderbolt 
intel_rapl mxm_wmi x86_pkg_temp_thermal intel_powerclamp coretemp 
dell_wmi_descriptor dcdbas kvm_intel dell_smm_hwmon kvm irqbypass snd_hda_intel 
crct10dif_pclmul crc32_pclmul snd_hda_codec ghash_clmulni_intel snd_hda_core 
pcbc snd_hwdep snd_pcm ath10k_pci aesni_intel ath10k_core aes_x86_64 
crypto_simd glue_helper cryptd snd_seq_midi ath uvcvideo intel_cstate 
snd_seq_midi_event snd_rawmidi intel_rapl_perf mac80211 snd_seq 
videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_seq_device snd_timer 
serio_raw videobuf2_core cdc_ether btusb usbnet videodev btrtl snd btbcm idma64 
btintel
  [   51.501517]  r8152 virt_dma media soundcore joydev rtsx_pci_ms mii 
input_leds cfg80211 bluetooth memstick ecdh_generic mei_me intel_lpss_pci 
processor_thermal_device mei shpchp intel_soc_dts_iosf intel_lpss 
intel_pch_thermal nvidia_uvm(POE) int3400_thermal int3403_thermal 
int340x_thermal_zone wmi acpi_thermal_rel mac_hid intel_hid acpi_pad 
sparse_keymap sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables 
autofs4 hid_generic usbhid ses enclosure scsi_transport_sas uas usb_storage 
nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) i915 i2c_algo_bit 
drm_kms_helper syscopyarea sysfillrect sysimgblt rtsx_pci_sdmmc fb_sys_fops 
ahci nvme ipmi_devintf psmouse drm nvme_core rtsx_pci libahci ipmi_msghandler 
i2c_hid hid video
  [   51.501552] CPU: 4 PID: 82 Comm: kworker/u16:1 Tainted: PW  OE
4.15.0-45-generic #48-Ubuntu
  [   51.501553] Hardware name: Dell Inc. XPS 15 9560/05FFDN, BIOS 1.12.1 
10/02/2018
  [   51.501556] Workqueue: kacpi_hotplug acpi_hotplug_work_fn
  [   51.501561] RIP: 0010:ring_interrupt_active+0x20c/0x270 [thunderbolt]
  [   51.501562] RSP: 0018:9eb4c1befb38 EFLAGS: 00010082
  [   51.501563] RAX:  RBX:  RCX: 
0006
  [   51.501564] RDX: 0007 RSI: 0092 RDI: 
92e47e516490
  [   51.501565] RBP: 9eb4c1befb70 R08: 0001 R09: 
0529
  [   51.501566] R10: 0040 R11:  R12: 
c1d90a1d
  [   51.501567] R13: 00038200 R14: 92e4641d3c00 R15: 
c1d90a14
  [   51.501568] FS:  () GS:92e47e50() 
knlGS:
  [   51.501569] CS:  0010 DS:  ES:  CR0: 80050033
  [   51.501570] CR2: 1fbc9e7103f8 CR3: 2660a004 CR4: 
003606e0
  [   51.501570] Call Trace:
  [   51.501575]  tb_ring_stop+0x109/0x160 [thunderbolt]
  [   51.501578]  tb_ctl_stop+0x45/0xc0 [thunderbolt]
  [   51.501582]  tb_domain_remove+0x42/0x70 [thunderbolt]
  [   51.501585]  nhi_remove+0x4b/0x60 [thunderbolt]
  [   51.501588]  pci_device_remove+0x3e/0xb0
  [   51.501590]  device_release_driver_internal+0x15b/0x240
  [   51.501592]  device_release_driver+0x12/0x20
  [   51.501594]  pci_stop_bus_device+0x7f/0xa0
  [   51.501595]  pci_stop_and_remove_bus_device+0x12/0x20
  [   51.501597]  trim_stale_devices+0x11d/0x150
  [   51.501598]  trim_stale_devices+0xa9/0x150
  [   51.501599]  trim_stale_devices+0xbb/0x150
  [   51.501600]  ? get_slot_status+0xa2/0x100
  [   51.501601]  acpiphp_check_bridge.part.7+0x100/0x140
  [   51.501602]  acpiphp_hotplug_notify+0x18e/0x220
  [   51.501603]  ? free_bridge+0x100/0x100
  [   51.501605]  acpi_device_hotplug+0xa4/0x4b0
  [   51.501607]  acpi_hotplug_work_fn+0x1e/0x30
  [   51.501609]  process_one_work+0x1de/0x410
  [   51.501610]  worker_thread+0x32/0x410
  [   51.501612]  kthread+0x121/0x140
  [   51.501613]  ?

[Kernel-packages] [Bug 1999079] [NEW] Kinetic update: upstream stable patchset 2022-12-07

2022-12-07 Thread Kamal Mostafa

Public bug reported:


SRU Justification

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

   upstream stable patchset 2022-12-07
   from git://git.kernel.org/

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

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


** Tags: kernel-stable-tracking-bug

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

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

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

Title:
  Kinetic update: upstream stable patchset 2022-12-07

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Kinetic:
  New

Bug description:
  
  SRU Justification

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

 upstream stable patchset 2022-12-07
 from git://git.kernel.org/

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

2022-12-07 Thread Colin Ian King

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

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

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

Title:
  thunderbolt

Status in linux package in Ubuntu:
  Incomplete
Status in thunderbolt-tools package in Ubuntu:
  New

Bug description:
  [   51.501462] [ cut here ]
  [   51.501465] thunderbolt :08:00.0: interrupt for TX ring 0 is already 
disabled
  [   51.501480] WARNING: CPU: 4 PID: 82 at 
/build/linux-uQJ2um/linux-4.15.0/drivers/thunderbolt/nhi.c:106 
ring_interrupt_active+0x20c/0x270 [thunderbolt]
  [   51.501481] Modules linked in: rfcomm ccm thunderbolt cmac bnep arc4 
snd_hda_codec_hdmi nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic 
hid_multitouch dell_wmi dell_laptop dell_smbios wmi_bmof intel_wmi_thunderbolt 
intel_rapl mxm_wmi x86_pkg_temp_thermal intel_powerclamp coretemp 
dell_wmi_descriptor dcdbas kvm_intel dell_smm_hwmon kvm irqbypass snd_hda_intel 
crct10dif_pclmul crc32_pclmul snd_hda_codec ghash_clmulni_intel snd_hda_core 
pcbc snd_hwdep snd_pcm ath10k_pci aesni_intel ath10k_core aes_x86_64 
crypto_simd glue_helper cryptd snd_seq_midi ath uvcvideo intel_cstate 
snd_seq_midi_event snd_rawmidi intel_rapl_perf mac80211 snd_seq 
videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_seq_device snd_timer 
serio_raw videobuf2_core cdc_ether btusb usbnet videodev btrtl snd btbcm idma64 
btintel
  [   51.501517]  r8152 virt_dma media soundcore joydev rtsx_pci_ms mii 
input_leds cfg80211 bluetooth memstick ecdh_generic mei_me intel_lpss_pci 
processor_thermal_device mei shpchp intel_soc_dts_iosf intel_lpss 
intel_pch_thermal nvidia_uvm(POE) int3400_thermal int3403_thermal 
int340x_thermal_zone wmi acpi_thermal_rel mac_hid intel_hid acpi_pad 
sparse_keymap sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables 
autofs4 hid_generic usbhid ses enclosure scsi_transport_sas uas usb_storage 
nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) i915 i2c_algo_bit 
drm_kms_helper syscopyarea sysfillrect sysimgblt rtsx_pci_sdmmc fb_sys_fops 
ahci nvme ipmi_devintf psmouse drm nvme_core rtsx_pci libahci ipmi_msghandler 
i2c_hid hid video
  [   51.501552] CPU: 4 PID: 82 Comm: kworker/u16:1 Tainted: PW  OE
4.15.0-45-generic #48-Ubuntu
  [   51.501553] Hardware name: Dell Inc. XPS 15 9560/05FFDN, BIOS 1.12.1 
10/02/2018
  [   51.501556] Workqueue: kacpi_hotplug acpi_hotplug_work_fn
  [   51.501561] RIP: 0010:ring_interrupt_active+0x20c/0x270 [thunderbolt]
  [   51.501562] RSP: 0018:9eb4c1befb38 EFLAGS: 00010082
  [   51.501563] RAX:  RBX:  RCX: 
0006
  [   51.501564] RDX: 0007 RSI: 0092 RDI: 
92e47e516490
  [   51.501565] RBP: 9eb4c1befb70 R08: 0001 R09: 
0529
  [   51.501566] R10: 0040 R11:  R12: 
c1d90a1d
  [   51.501567] R13: 00038200 R14: 92e4641d3c00 R15: 
c1d90a14
  [   51.501568] FS:  () GS:92e47e50() 
knlGS:
  [   51.501569] CS:  0010 DS:  ES:  CR0: 80050033
  [   51.501570] CR2: 1fbc9e7103f8 CR3: 2660a004 CR4: 
003606e0
  [   51.501570] Call Trace:
  [   51.501575]  tb_ring_stop+0x109/0x160 [thunderbolt]
  [   51.501578]  tb_ctl_stop+0x45/0xc0 [thunderbolt]
  [   51.501582]  tb_domain_remove+0x42/0x70 [thunderbolt]
  [   51.501585]  nhi_remove+0x4b/0x60 [thunderbolt]
  [   51.501588]  pci_device_remove+0x3e/0xb0
  [   51.501590]  device_release_driver_internal+0x15b/0x240
  [   51.501592]  device_release_driver+0x12/0x20
  [   51.501594]  pci_stop_bus_device+0x7f/0xa0
  [   51.501595]  pci_stop_and_remove_bus_device+0x12/0x20
  [   51.501597]  trim_stale_devices+0x11d/0x150
  [   51.501598]  trim_stale_devices+0xa9/0x150
  [   51.501599]  trim_stale_devices+0xbb/0x150
  [   51.501600]  ? get_slot_status+0xa2/0x100
  [   51.501601]  acpiphp_check_bridge.part.7+0x100/0x140
  [   51.501602]  acpiphp_hotplug_notify+0x18e/0x220
  [   51.501603]  ? free_bridge+0x100/0x100
  [   51.501605]  acpi_device_hotplug+0xa4/0x4b0
  [   51.501607]  acpi_hotplug_work_fn+0x1e/0x30
  [   51.501609]  process_one_work+0x1de/0x410
  [   51.501610]  worker_thread+0x32/0x410
  [   51.501612]  kthread+0x121/0x140
  [   51.501613]  ? process_one_work+0x410/0x410
  [   51.501615]  ? kthread_create_worker_on_cpu+0x70/0x70
  [   51.501617]  ret_from_fork+0x35/0x40
  [   51.501618] Code: 00 48 89 55 c8 44 89 45 d4 e8 21 a0 8c ee 44 8b 45 d4 48 
8b 55 c8 4d 89 f9 4c 89 e1 48 89 c6 48 c7 c7 38 12 d9 c1 e8 b4 d8 30 ee <0f> 0b 
e9 36 ff ff ff 41 0f b6 46 78 d3 e0 09 c7 e9 cd fe ff ff 
  [   51.501644] ---[ end trace dbb8a6822d824854 ]---

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1997757] Re: No more sound after upgrade to linux-image-6.0.0-1007-oem

please test 1008 from proposed

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

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

** Changed in: linux-oem-6.0 (Ubuntu Jammy)
   Status: New => Incomplete

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

Title:
  No more sound after upgrade to linux-image-6.0.0-1007-oem

Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  Incomplete

Bug description:
  Description:KDE neon 5.26
  Release:22.04

  After upgrade from  linux-image-6.0.0-1006-oem to linux-image-6.0.0-1007-oem 
I don't have sound anymore.
  I believe that the relevant dmesg message is this one, as it is not printed 
with the linux-image-6.0.0-1006-oem version:

  I think this bug is connected with this bub from Debian.
  https://lists.debian.org/debian-kernel/2022/10/msg00301.html

  Log:

  [5.535620] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI 
class/subclass/prog-if info 0x040100
  [5.535644] sof-audio-pci-intel-tgl :00:1f.3: Digital mics found on 
Skylake+ platform, using SOF driver
  [5.535650] sof-audio-pci-intel-tgl :00:1f.3: enabling device ( -> 
0002)
  [5.535784] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI 
class/subclass/prog-if 0x040100
  [5.535850] sof-audio-pci-intel-tgl :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [5.544186] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode
  [5.605507] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 5
  [5.605509] sof-audio-pci-intel-tgl :00:1f.3: using HDA machine driver 
skl_hda_dsp_generic now
  [5.605511] sof-audio-pci-intel-tgl :00:1f.3: DMICs detected in NHLT 
tables: 2
  [5.606867] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 
2:0:0-b678a
  [5.606869] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:20:0 
Kernel ABI 3:23:0
  [5.606872] sof-audio-pci-intel-tgl :00:1f.3: unknown sof_ext_man 
header type 3 size 0x30
  [5.613329] iwlwifi :00:14.3: Detected RF HR B3, rfid=0x10a100
  [5.679733] iwlwifi :00:14.3: base HW address: 8c:1d:96:08:c0:32
  [5.691036] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 
2:0:0-b678a
  [5.691039] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:20:0 
Kernel ABI 3:23:0
  [5.695325] iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0
  [5.703514] sof-audio-pci-intel-tgl :00:1f.3: Topology: ABI 3:20:0 
Kernel ABI 3:23:0
  [5.703670] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: Parent card not 
yet available, widget card binding deferred
  [5.706576] snd_hda_codec_hdmi ehdaudio0D2: failed to create hda codec -12
  [5.706661] snd_hda_codec_hdmi ehdaudio0D2: ASoC: error at 
snd_soc_component_probe on ehdaudio0D2: -12
  [5.706676] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: failed to 
instantiate card -12
  [5.706767] skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with 
error -12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1997757/+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 1998510] Re: Jammy update: v6.0.10 upstream stable release

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

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

Title:
  Jammy update: v6.0.10 upstream stable release

Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  New

Bug description:
  
  SRU Justification

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

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

  
  Linux 6.0.10
  ntfs: check overflow when iterating ATTR_RECORDs
  ntfs: fix out-of-bounds read in ntfs_attr_find()
  ntfs: fix use-after-free in ntfs_attr_find()
  bpf: Prevent bpf program recursion for raw tracepoint probes
  net/9p: use a dedicated spinlock for trans_fd
  mm: fs: initialize fsdata passed to write_begin/write_end interface
  rseq: Use pr_warn_once() when deprecated/unknown ABI flags are encountered
  wifi: wext: use flex array destination for memcpy()
  netlink: Bounds-check struct nlmsgerr creation
  9p/trans_fd: always use O_NONBLOCK read/write
  gfs2: Switch from strlcpy to strscpy
  gfs2: Check sb_bsize_shift after reading superblock
  9p: trans_fd/p9_conn_cancel: drop client lock earlier
  KVM: x86/xen: Fix eventfd error handling in kvm_xen_eventfd_assign()
  kcm: avoid potential race in kcm_tx_work
  tcp: cdg: allow tcp_cdg_release() to be called multiple times
  macvlan: enforce a consistent minimal mtu
  Input: i8042 - fix leaking of platform device on module removal
  arm64/mm: fix incorrect file_map_count for non-leaf pmd/pud
  tracing: Fix potential null-pointer-access of entry in list 'tr->err_log'
  kprobes: Skip clearing aggrprobe's post_handler in kprobe-on-ftrace case
  scsi: scsi_debug: Fix possible UAF in sdebug_add_host_helper()
  scsi: target: tcm_loop: Fix possible name leak in tcm_loop_setup_hba_bus()
  net: use struct_group to copy ip/ipv6 header addresses
  net: usb: smsc95xx: fix external PHY reset
  tracing: Fix warning on variable 'struct trace_array'
  ring-buffer: Include dropped pages in counting dirty patches
  perf/x86/amd: Fix crash due to race between amd_pmu_enable_all, perf NMI and 
throttling
  vfio: Split the register_device ops call into functions
  vfio: Rename vfio_ioctl_check_extension()
  perf: Improve missing SIGTRAP checking
  ASoC: SOF: topology: No need to assign core ID if token parsing failed
  nvme: ensure subsystem reset is single threaded
  nvme: restrict management ioctls to admin
  perf/x86/intel/pt: Fix sampling using single range output
  perf/x86/amd/uncore: Fix memory leak for events array
  x86/fpu: Drop fpregs lock before inheriting FPU permissions
  x86/sgx: Add overflow check in sgx_validate_offset_length()
  blk-cgroup: properly pin the parent in blkcg_css_online
  misc/vmw_vmci: fix an infoleak in vmci_host_do_receive_datagram()
  s390/dcssblk: fix deadlock when adding a DCSS
  docs/driver-api/miscellaneous: Remove kernel-doc of serial_core.c
  docs: update mediator contact information in CoC doc
  mmc: sdhci-pci: Fix possible memory leak caused by missing pci_dev_put()
  mmc: sdhci-pci-o2micro: fix card detect fail issue caused by CD# debounce 
timeout
  mmc: core: properly select voltage range without power cycle
  firmware: coreboot: Register bus in module init
  iommu/vt-d: Set SRE bit only when hardware has SRS cap
  iommu/vt-d: Preset Access bit for IOVA in FL non-leaf paging entries
  scsi: zfcp: Fix double free of FSF request when qdio send fails
  net: phy: marvell: add sleep time after enabling the loopback bit
  maccess: Fix writing offset in case of fault in strncpy_from_kernel_nofault()
  Input: iforce - invert valid length check when fetching device IDs
  ceph: avoid putting the realm twice when decoding snaps fails
  io_uring: disallow self-propelled ring polling
  io_uring: fix multishot recv request leaks
  io_uring: fix multishot accept request leaks
  io_uring: fix tw losing poll events
  serial: 8250_lpss: Use 16B DMA burst with Elkhart Lake
  serial: 8250_lpss: Configure DMA also w/o DMA filter
  serial: 8250: Flush DMA Rx on RLSI
  serial: 8250: Fall back to non-DMA Rx if IIR_RDI occurs
  dm ioctl: fix misbehavior if list_versions races with module loading
  dm bufio: Fix missing decrement of no_sleep_enabled if dm_bufio_client_create 
failed
  iio: pressure: ms5611: changed hardcoded SPI speed to value limited
  iio: pressure: ms5611: fixed value compensation bug
  iio: adc: mp2629: fix potential array out of bound access

[Kernel-packages] [Bug 1994038] Re: Jammy update: v6.0.3 upstream stable release

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

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

Title:
  Jammy update: v6.0.3 upstream stable release

Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  Fix Released

Bug description:
  
  SRU Justification

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1994038/+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 1996080] Re: Jammy update: v6.0.4 upstream stable release

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

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

Title:
  Jammy update: v6.0.4 upstream stable release

Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  New

Bug description:
  
  SRU Justification

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1996080/+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 1995511] Re: net-build failed in ubuntu_kernel_selftests with 6.0 kernel

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

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

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

Title:
  net-build failed in ubuntu_kernel_selftests with 6.0 kernel

Status in ubuntu-kernel-tests:
  New
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  New

Bug description:
  Issue found with J-oem-6.0.0-1007.7

  This is not a regression, issue exists before this kernel.

  make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
  make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
  gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include  
  reuseport_bpf.c  -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf
  gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include  
  reuseport_bpf_cpu.c  -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf_cpu
  gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include  
  reuseport_bpf_numa.c -lnuma -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf_numa
  gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include  
  reuseport_dualstack.c  -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_dualstack
  gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include  
  reuseaddr_conflict.c  -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseaddr_conflict
  gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include  
  tls.c  -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/tls
  make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
  make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
  stderr:
  tls.c:32:50: error: field ‘sm4gcm’ has incomplete type
 32 | struct tls12_crypto_info_sm4_gcm sm4gcm;
|  ^~
  tls.c:33:50: error: field ‘sm4ccm’ has incomplete type
 33 | struct tls12_crypto_info_sm4_ccm sm4ccm;
|  ^~
  tls.c: In function ‘tls_crypto_info_init’:
  tls.c:56:14: error: ‘TLS_CIPHER_SM4_GCM’ undeclared (first use in this 
function); did you mean ‘TLS_CIPHER_AES_GCM_256’?
 56 | case TLS_CIPHER_SM4_GCM:
|  ^~
|  TLS_CIPHER_AES_GCM_256
  tls.c:56:14: note: each undeclared identifier is reported only once for each 
function it appears in
  tls.c:57:37: error: invalid application of ‘sizeof’ to incomplete type 
‘struct tls12_crypto_info_sm4_gcm’
 57 | tls12->len = sizeof(struct tls12_crypto_info_sm4_gcm);
| ^~
  tls.c:61:14: error: ‘TLS_CIPHER_SM4_CCM’ undeclared (first use in this 
function); did you mean ‘TLS_CIPHER_AES_CCM_128’?
 61 | case TLS_CIPHER_SM4_CCM:
|  ^~
|  TLS_CIPHER_AES_CCM_128
  tls.c:62:37: error: invalid application of ‘sizeof’ to incomplete type 
‘struct tls12_crypto_info_sm4_ccm’
 62 | tls12->len = sizeof(struct tls12_crypto_info_sm4_ccm);
| ^~
  tls.c: At top level:
  tls.c:268:24: error: ‘TLS_CIPHER_SM4_GCM’ undeclared here (not in a 
function); did you mean ‘TLS_CIPHER_AES_GCM_256’?
268 | .cipher_type = TLS_CIPHER_SM4_GCM,
|^~
|TLS_CIPHER_AES_GCM_256
  tls.c:274:24: error: ‘TLS_CIPHER_SM4_CCM’ undeclared here (not in a 
function); did you mean ‘TLS_CIPHER_AES_CCM_128’?
274 | .cipher_type = TLS_CIPHER_SM4_CCM,
|^~
|

[Kernel-packages] [Bug 1996083] Re: Jammy update: v6.0.6 upstream stable release

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

** Changed in: linux-oem-6.0 (Ubuntu Jammy)
   Status: New => Fix Committed

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

Title:
  Jammy update: v6.0.6 upstream stable release

Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed

Bug description:
  
  SRU Justification

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1996083/+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 1996081] Re: Jammy update: v6.0.5 upstream stable release

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

** Changed in: linux-oem-6.0 (Ubuntu Jammy)
   Status: New => Fix Committed

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

Title:
  Jammy update: v6.0.5 upstream stable release

Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed

Bug description:
  
  SRU Justification

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1996081/+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 1996783] Re: Jammy update: v6.0.8 upstream stable release

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

** Changed in: linux-oem-6.0 (Ubuntu Jammy)
   Status: New => Fix Committed

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

Title:
  Jammy update: v6.0.8 upstream stable release

Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed

Bug description:
  
  SRU Justification

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

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

  
  Linux 6.0.8
  wifi: brcmfmac: Fix potential buffer overflow in brcmf_fweh_event_worker()
  drm/i915/sdvo: Setup DDC fully before output init
  drm/i915/sdvo: Filter out invalid outputs more sensibly
  drm/amd/display: Update DSC capabilitie for DCN314
  drm/amd/display: Update latencies on DCN321
  drm/amdgpu: disable GFXOFF during compute for GFX11
  drm/rockchip: dsi: Force synchronous probe
  drm/rockchip: dsi: Clean up 'usage_mode' when failing to attach
  cifs: fix regression in very old smb1 mounts
  ext4,f2fs: fix readahead of verity data
  KVM: x86: emulator: update the emulation mode after CR0 write
  KVM: x86: emulator: update the emulation mode after rsm
  KVM: x86: emulator: introduce emulator_recalc_and_set_mode
  KVM: x86: emulator: em_sysexit should update ctxt->mode
  KVM: x86: smm: number of GPRs in the SMRAM image depends on the image format
  KVM: arm64: Fix SMPRI_EL1/TPIDR2_EL0 trapping on VHE
  KVM: arm64: Fix bad dereference on MTE-enabled systems
  KVM: Reject attempts to consume or refresh inactive gfn_to_pfn_cache
  KVM: Initialize gfn_to_pfn_cache locks in dedicated helper
  KVM: VMX: fully disable SGX if SECONDARY_EXEC_ENCLS_EXITING unavailable
  KVM: VMX: Ignore guest CPUID for host userspace writes to DEBUGCTL
  KVM: VMX: Fold vmx_supported_debugctl() into vcpu_supported_debugctl()
  KVM: VMX: Advertise PMU LBRs if and only if perf supports LBRs
  KVM: x86: Mask off reserved bits in CPUID.801FH
  KVM: x86: Mask off reserved bits in CPUID.8001H
  KVM: x86: Mask off reserved bits in CPUID.8008H
  KVM: x86: Mask off reserved bits in CPUID.801AH
  KVM: x86: Mask off reserved bits in CPUID.8006H
  x86/syscall: Include asm/ptrace.h in syscall_wrapper header
  x86/tdx: Panic on bad configs that #VE on "private" memory access
  x86/tdx: Prepare for using "INFO" call for a second purpose
  ext4: update the backup superblock's at the end of the online resize
  ext4: fix BUG_ON() when directory entry has invalid rec_len
  ext4: fix warning in 'ext4_da_release_space'
  parisc: Avoid printing the hardware path twice
  parisc: Export iosapic_serial_irq() symbol for serial port driver
  parisc: Make 8250_gsc driver dependend on CONFIG_PARISC
  net: also flag accepted sockets supporting msghdr originated zerocopy
  net: remove SOCK_SUPPORT_ZC from sockmap
  perf/x86/intel: Fix pebs event constraints for SPR
  perf/x86/intel: Add Cooper Lake stepping to isolation_ucodes[]
  perf/x86/intel: Fix pebs event constraints for ICL
  ARM: dts: imx6dl-yapp4: Do not allow PM to switch PU regulator off on Q/QP
  arm64: entry: avoid kprobe recursion
  net/ulp: remove SOCK_SUPPORT_ZC from tls sockets
  efi: efivars: Fix variable writes with unsupported query_variable_store()
  efi: random: Use 'ACPI reclaim' memory for random seed
  efi: random: reduce seed size to 32 bytes
  selftests/landlock: Build without static libraries
  fuse: fix readdir cache race
  fuse: add file_modified() to fallocate
  capabilities: fix potential memleak on error path from vfs_getxattr_alloc()
  tracing/histogram: Update document for KEYS_MAX size
  tools/nolibc/string: Fix memcmp() implementation
  ring-buffer: Check for NULL cpu_buffer in ring_buffer_wake_waiters()
  kprobe: reverse kp->flags when arm_kprobe failed
  tracing: kprobe: Fix memory leak in test_gen_kprobe/kretprobe_cmd()
  fprobe: Check rethook_alloc() return in rethook initialization
  tracing/fprobe: Fix to check whether fprobe is registered correctly
  ftrace: Fix use-after-free for dynamic ftrace_ops
  cxl/region: Fix 'distance' calculation with passthrough ports
  cxl/region: Fix cxl_region leak, cleanup targets at region delete
  cxl/region: Fix region HPA ordering validation
  cxl/region: Fix decoder allocation crash
  cxl/pmem: Fix cxl_pmem_region and cxl_memdev leak
  ACPI: NUMA: Add CXL CFMWS 'nodes' to the possible nodes set
  btrfs: fix a memory allocation failure

[Kernel-packages] [Bug 1996174] Re: CVE-2016-3672 in ubuntu_cve_kernel failed with J-oem-6.0

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

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

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

Title:
  CVE-2016-3672 in ubuntu_cve_kernel failed with J-oem-6.0

Status in ubuntu-kernel-tests:
  New
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  New

Bug description:
  Issue found with J-oem-6.0.0-1007

  This is not a regression as this failure can be found with older
  kernel (6.0.0-1004.4) as well

  Test log:
   STARTubuntu_cve_kernel.CVE-2016-3672
ubuntu_cve_kernel.CVE-2016-3672timestamp=1666797878timeout=900
localtime=Oct 26 15:24:38   
   Persistent state client._record_indent now set to 2
   Persistent state client.unexpected_reboot now set to 
('ubuntu_cve_kernel.CVE-2016-3672', 'ubuntu_cve_kernel.CVE-2016-3672')
   Waiting for pid 55210 for 900 seconds
   System python is too old, crash handling disabled
   *** CVE-2016-3672 ***
   Running 'make -C 
/home/ubuntu/autotest/client/tests/ubuntu_cve_kernel/cves/CVE-2016-3672 check'
   [stdout] make: Entering directory 
'/home/ubuntu/autotest/client/tests/ubuntu_cve_kernel/cves/CVE-2016-3672'
   [stdout] gcc -o show_maps show_maps.c -m32
   [stdout] sudo -u ubuntu ./check.sh
   [stdout] make: Leaving directory 
'/home/ubuntu/autotest/client/tests/ubuntu_cve_kernel/cves/CVE-2016-3672'
   [stderr] make: *** [Makefile:11: check] Error 1

  A manual test shows this test case is a bit flaky for some reason:
  ubuntu@curly:~/autotest-client-tests/ubuntu_cve_kernel/cves/CVE-2016-3672$ 
for i in {1..10}; do make check; echo $?; make clean; done
  gcc -o show_maps show_maps.c -m32
  sudo -u ubuntu ./check.sh
  0
  rm -f show_maps
  gcc -o show_maps show_maps.c -m32
  sudo -u ubuntu ./check.sh
  0
  rm -f show_maps
  gcc -o show_maps show_maps.c -m32
  sudo -u ubuntu ./check.sh
  0
  rm -f show_maps
  gcc -o show_maps show_maps.c -m32
  sudo -u ubuntu ./check.sh
  make: *** [Makefile:11: check] Error 1
  2
  rm -f show_maps
  gcc -o show_maps show_maps.c -m32
  sudo -u ubuntu ./check.sh
  0
  rm -f show_maps
  gcc -o show_maps show_maps.c -m32
  sudo -u ubuntu ./check.sh
  make: *** [Makefile:11: check] Error 1
  2
  rm -f show_maps
  gcc -o show_maps show_maps.c -m32
  sudo -u ubuntu ./check.sh
  0
  rm -f show_maps
  gcc -o show_maps show_maps.c -m32
  sudo -u ubuntu ./check.sh
  0
  rm -f show_maps
  gcc -o show_maps show_maps.c -m32
  sudo -u ubuntu ./check.sh
  0
  rm -f show_maps
  gcc -o show_maps show_maps.c -m32
  sudo -u ubuntu ./check.sh
  0
  rm -f show_maps

  I don't recall we have this issue with other kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1996174/+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 1996785] Re: Jammy update: v6.0.9 upstream stable release

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

** Changed in: linux-oem-6.0 (Ubuntu Jammy)
   Status: New => Fix Committed

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

Title:
  Jammy update: v6.0.9 upstream stable release

Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed

Bug description:
  
  SRU Justification

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

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

  
  Linux 6.0.9
  x86/cpu: Restore AMD's DE_CFG MSR after resume
  ALSA: memalloc: Try dma_alloc_noncontiguous() at first
  drm/amdkfd: Migrate in CPU page fault use current mm
  dmaengine: at_hdmac: Check return code of dma_async_device_register
  dmaengine: at_hdmac: Fix impossible condition
  dmaengine: at_hdmac: Don't allow CPU to reorder channel enable
  dmaengine: at_hdmac: Fix completion of unissued descriptor in case of errors
  dmaengine: at_hdmac: Fix descriptor handling when issuing it to hardware
  dmaengine: at_hdmac: Fix concurrency over the active list
  dmaengine: at_hdmac: Free the memset buf without holding the chan lock
  dmaengine: at_hdmac: Fix concurrency over descriptor
  dmaengine: at_hdmac: Fix concurrency problems by removing atc_complete_all()
  dmaengine: at_hdmac: Protect atchan->status with the channel lock
  dmaengine: at_hdmac: Do not call the complete callback on device_terminate_all
  dmaengine: at_hdmac: Fix premature completion of desc in issue_pending
  dmaengine: at_hdmac: Start transfer for cyclic channels in issue_pending
  dmaengine: at_hdmac: Don't start transactions at tx_submit level
  dmaengine: at_hdmac: Fix at_lli struct definition
  can: dev: fix skb drop check
  KVM: SVM: move guest vmsave/vmload back to assembly
  KVM: SVM: retrieve VMCB from assembly
  KVM: SVM: Only dump VMSA to klog at KERN_DEBUG level
  KVM: SVM: adjust register allocation for __svm_vcpu_run()
  KVM: SVM: replace regs argument of __svm_vcpu_run() with vcpu_svm
  KVM: x86: use a separate asm-offsets.c file
  KVM: x86/pmu: Do not speculatively query Intel GP PMCs that don't exist yet
  KVM: x86/mmu: Block all page faults during kvm_zap_gfn_range()
  can: rcar_canfd: Add missing ECC error checks for channels 2-7
  can: isotp: fix tx state handling for echo tx processing
  can: j1939: j1939_send_one(): fix missing CAN header initialization
  mm/shmem: use page_mapping() to detect page cache for uffd continue
  mm/memremap.c: map FS_DAX device memory as decrypted
  mm/damon/dbgfs: check if rm_contexts input is for a real context
  dmaengine: idxd: Do not enable user type Work Queue without Shared Virtual 
Addressing
  mm: hugetlb_vmemmap: include missing linux/moduleparam.h
  arch/x86/mm/hugetlbpage.c: pud_huge() returns 0 when using 2-level paging
  spi: intel: Use correct mask for flash and protected regions
  udf: Fix a slab-out-of-bounds write bug in udf_find_entry()
  mms: sdhci-esdhc-imx: Fix SDHCI_RESET_ALL for CQHCI
  net: ethernet: ti: am65-cpsw: Fix segmentation fault at module unload
  phy: qcom-qmp-combo: fix NULL-deref on runtime resume
  io_uring: check for rollover of buffer ID when providing buffers
  btrfs: zoned: initialize device's zone info for seeding
  btrfs: zoned: clone zoned device info when cloning a device
  btrfs: selftests: fix wrong error check in btrfs_free_dummy_root()
  btrfs: fix match incorrectly in dev_args_match_device
  wifi: ath11k: avoid deadlock during regulatory update in ath11k_regd_update()
  platform/x86: hp_wmi: Fix rfkill causing soft blocked wifi
  drm/amdkfd: Fix error handling in kfd_criu_restore_events
  drm/amdkfd: Fix error handling in criu_checkpoint
  drm/amdgpu: disable BACO on special BEIGE_GOBY card
  drm/amdgpu: workaround for TLB seq race
  drm/amd/display: Update SR watermarks for DCN314
  drm/amd/pm: update SMU IP v13.0.4 msg interface header
  drm/amd/display: Fix reg timeout in enc314_enable_fifo
  drm/i915/dmabuf: fix sg_table handling in map_dma_buf
  nilfs2: fix use-after-free bug of ns_writer on remount
  nilfs2: fix deadlock in nilfs_count_free_blocks()
  ata: libata-scsi: fix SYNCHRONIZE CACHE (16) command failure
  vmlinux.lds.h: Fix placement of '.data..decrypted' section
  ALSA: usb-audio: Add DSD support for Accuphase DAC-60
  ALSA: usb-audio: Add quirk entry for M-Audio Micro
  ALSA: usb-audio: Yet more regression for for the delayed card registration

[Kernel-packages] [Bug 1996134] Re: test_resolved_domain_restricted_dns in networkd-test.py from systemd ADT failed with J-oem-6.0.0-1007

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

** Changed in: linux-oem-6.0 (Ubuntu Jammy)
   Status: New => Triaged

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

Title:
  test_resolved_domain_restricted_dns in networkd-test.py from systemd
  ADT failed with J-oem-6.0.0-1007

Status in ubuntu-kernel-tests:
  New
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  Triaged

Bug description:
  This issue does not exist with J-oem-6.0.0-1006

  With systemd 249.11-0ubuntu3.6

  ubuntu@curly:~/systemd-249.11/test$  sudo ./networkd-test.py ; uname -a
  systemd-network:x:100:102:systemd Network 
Management,,,:/run/systemd:/usr/sbin/nologin
  test_bridge_init (__main__.BridgeTest) ... ok
  test_bridge_port_priority (__main__.BridgeTest) ... ok
  test_bridge_port_priority_set_zero (__main__.BridgeTest)
  It should be possible to set the bridge port priority to 0 ... ok
  test_bridge_port_property (__main__.BridgeTest)
  Test the "[Bridge]" section keys ... ok
  test_coldplug_dhcp_ip4_only (__main__.DnsmasqClientTest) ... ok
  test_coldplug_dhcp_ip4_only_no_ra (__main__.DnsmasqClientTest) ... ok
  test_coldplug_dhcp_ip6 (__main__.DnsmasqClientTest) ... ok
  test_coldplug_dhcp_yes_ip4 (__main__.DnsmasqClientTest) ... ok
  test_coldplug_dhcp_yes_ip4_no_ra (__main__.DnsmasqClientTest) ... ok
  test_hotplug_dhcp_ip4 (__main__.DnsmasqClientTest) ... ok
  test_hotplug_dhcp_ip6 (__main__.DnsmasqClientTest) ... ok
  test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
  resolved: domain-restricted DNS servers ... ERROR
  test_resolved_etc_hosts (__main__.DnsmasqClientTest)
  resolved queries to /etc/hosts ... ok
  test_route_only_dns (__main__.DnsmasqClientTest) ... ok
  test_route_only_dns_all_domains (__main__.DnsmasqClientTest) ... ok
  test_transient_hostname (__main__.DnsmasqClientTest)
  networkd sets transient hostname from DHCP ... ok
  test_transient_hostname_with_static (__main__.DnsmasqClientTest)
  transient hostname is not applied if static hostname exists ... ok
  test_basic_matching (__main__.MatchClientTest)
  Verify the Name= line works throughout this class. ... ok
  test_inverted_matching (__main__.MatchClientTest)
  Verify that a '!'-prefixed value inverts the match. ... ok
  test_coldplug_dhcp_ip4_only (__main__.NetworkdClientTest) ... ok
  test_coldplug_dhcp_ip4_only_no_ra (__main__.NetworkdClientTest) ... ok
  test_coldplug_dhcp_ip6 (__main__.NetworkdClientTest) ... skipped 'networkd 
does not have DHCPv6 server support'
  test_coldplug_dhcp_yes_ip4 (__main__.NetworkdClientTest) ... ok
  test_coldplug_dhcp_yes_ip4_no_ra (__main__.NetworkdClientTest) ... ok
  test_dhcp_timezone (__main__.NetworkdClientTest)
  networkd sets time zone from DHCP ... ok
  test_dropin (__main__.NetworkdClientTest) ... ok
  test_hotplug_dhcp_ip4 (__main__.NetworkdClientTest) ... ok
  test_hotplug_dhcp_ip6 (__main__.NetworkdClientTest) ... skipped 'networkd 
does not have DHCPv6 server support'
  test_route_only_dns (__main__.NetworkdClientTest) ... ok
  test_route_only_dns_all_domains (__main__.NetworkdClientTest) ... ok
  test_search_domains (__main__.NetworkdClientTest) ... ok
  test_catchall_config (__main__.UnmanagedClientTest)
  Verify link states with a catch-all config, hot-plug. ... ok
  test_catchall_config_coldplug (__main__.UnmanagedClientTest)
  Verify link states with a catch-all config, cold-plug. ... ok
  test_unmanaged_setting (__main__.UnmanagedClientTest)
  Verify link states with Unmanaged= settings, hot-plug. ... ok
  test_unmanaged_setting_coldplug (__main__.UnmanagedClientTest)
  Verify link states with Unmanaged= settings, cold-plug. ... ok

  ==
  ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
  resolved: domain-restricted DNS servers
  --
  Traceback (most recent call last):
File "/home/ubuntu/systemd-249.11/test/./networkd-test.py", line 678, in 
test_resolved_domain_restricted_dns
  out = subprocess.check_output(['resolvectl', 'query', 'math.lab'])
File "/usr/lib/python3.10/subprocess.py", line 420, in check_output
  return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.10/subprocess.py", line 524, in run
  raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' 
returned non-zero exit status 1.

  --
  Ran 35 tests in 156.268s

  FAILED (errors=1, skipped=2)
  Linux curly 6.0.0-1007-oem #7-Ubuntu SMP PREEMPT_DYNAMIC Tue Oct 25 18:05:20 
UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

  
  Here is the test log with J-oem-6.0.0-1006

[Kernel-packages] [Bug 1996084] Re: Jammy update: v6.0.7 upstream stable release

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

** Changed in: linux-oem-6.0 (Ubuntu Jammy)
   Status: New => Fix Committed

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

Title:
  Jammy update: v6.0.7 upstream stable release

Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed

Bug description:
  
  SRU Justification

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1996084/+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 1984103] Re: [UBUNTU 22.04] s390/qeth: cache link_info for ethtool

2022-12-07 Thread Frank Heimes

This bug was not requested for linux-bluefield.
Hence I'll just set the tag 'verification-done-jammy' to unblock the further 
process.

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

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

Title:
  [UBUNTU 22.04] s390/qeth: cache link_info for ethtool

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  == SRU Justification ==
  Since commit e6e771b3d897 ("s390/qeth: detach netdevice while card is 
offline") there was a timing window during recovery, that qeth_query_card_info 
could be   sent to the card, even before it was ready for it, leading to a 
failing cardrecovery. There is evidence that this window was hit, as not 
all callers of get_link_ksettings() check for netif_device_present.

  This patch (Mainline commit 7a07a29e4f67) fixes the regression caused
  by commit e6e771b3d897.

  Commit 7a07a29e4f67 is in mainline as of v6.0-rc1.

  This patch is being requested in Jammy 5.15 and Kinetic 5.19.

  == Fix ==
  7a07a29e4f67 ("s390/qeth: cache link_info for ethtool")

  == Regression Potential ==
  Low.  This patch has been accepted in upstream stable and is limited to
  the s390/qeth card.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  == Comment: #0 - J?rn Siglen  - 2022-08-09 07:38:27 ==
  +++ This bug was initially created as a clone of Bug #199319 +++

  Description:   s390/qeth: cache link_info for ethtool
  Symptom:   lost of IP connection and log entries in journalctl:
    kernel: qeth 0.0.0365: The qeth device driver failed to
    recover an error on the device
  Problem:   Since commit e6e771b3d897
   ("s390/qeth: detach netdevice while card is offline")
     there was a timing window during recovery, that
     qeth_query_card_info could be sent to the card, even before it
     was ready for it, leading to a failing card recovery. There is
     evidence that this window was hit, as not all callers of
     get_link_ksettings() check for netif_device_present.
  Solution:  Use cached values in qeth_get_link_ksettings(), instead of
     calling qeth_query_card_info() and falling back to default
     values in case it fails. Link info is already updated when the
     card goes online, e.g. after STARTLAN (physical link up). Set
     the link info to default values, when the card goes offline or
     at STOPLAN (physical link down). A follow-on patch will improve
     values reported for link down.
     Fixes: e6e771b3d897
     ("s390/qeth: detach netdevice while card is offline")
  Reproduction:  enforce a eth device recvoery, while running ethtool multiple
     times in parallel and using iperf to get load on the interface.
  Upstream-ID:   7a07a29e4f6713b224f3bcde5f835e777301bdb8

  
https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f

  applicable for most kernel > 3.14

  == Comment: #3 - J?rn Siglen  - 2022-08-09 07:54:41 ==
  the inital update came in with kernel 5.1 upstream, but we found it 
backported in many older kernel versions

  == Comment: #4 - J?rn Siglen  - 2022-08-09 08:03:09 ==
  the acceptance info of the patch can be found here:
  
https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1984103/+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 1991774] Re: Memory leak while using NFQUEUE to delegate the decision on TCP packets to userspace processes

This bug is awaiting verification that the linux-
azure-4.15/4.15.0-1157.172 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-bionic' to
'verification-done-bionic'. If the problem still exists, change the tag
'verification-needed-bionic' to 'verification-failed-bionic'.

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 removed: verification-done-bionic
** Tags added: kernel-spammed-bionic-linux-azure-4.15 verification-needed-bionic

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

Title:
  Memory leak while using NFQUEUE to delegate the decision on TCP
  packets to userspace processes

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  Environment: v4.15.0-177-generic Xenial ESM

  Using NFQUEUE to delegate the decision on TCP packets to userspace processes 
will cause memory leak.
  The symptom is that TCP slab objects will accumulate and eventually cause OOM.

  [Fix]

  There is a discrepancy between backport and upstream commit.

  [Upstream Commit c3873070247d9e3c7a6b0cf9bf9b45e8018427b1]
  diff --git a/include/net/netfilter/nf_queue.h 
b/include/net/netfilter/nf_queue.h
  index 9eed51e920e8..980daa6e1e3a 100644
  --- a/include/net/netfilter/nf_queue.h
  +++ b/include/net/netfilter/nf_queue.h
  @@ -37,7 +37,7 @@ void nf_register_queue_handler(const struct 
nf_queue_handler *qh);
   void nf_unregister_queue_handler(void);
   void nf_reinject(struct nf_queue_entry *entry, unsigned int verdict);

  -void nf_queue_entry_get_refs(struct nf_queue_entry *entry);
  +bool nf_queue_entry_get_refs(struct nf_queue_entry *entry);
   void nf_queue_entry_free(struct nf_queue_entry *entry);

   static inline void init_hashrandom(u32 *jhash_initval)
  diff --git a/net/netfilter/nf_queue.c b/net/netfilter/nf_queue.c
  index 5ab0680db445..e39549c55945 100644
  --- a/net/netfilter/nf_queue.c
  +++ b/net/netfilter/nf_queue.c
  @@ -96,19 +96,21 @@ static void __nf_queue_entry_init_physdevs(struct 
nf_queue_entry *entry)
   }

   /* Bump dev refs so they don't vanish while packet is out */
  -void nf_queue_entry_get_refs(struct nf_queue_entry *entry)
  +bool nf_queue_entry_get_refs(struct nf_queue_entry *entry)
   {
    struct nf_hook_state *state = >state;

  + if (state->sk && !refcount_inc_not_zero(>sk->sk_refcnt))
  + return false;
  +
    dev_hold(state->in);
    dev_hold(state->out);
  - if (state->sk)
  - sock_hold(state->sk);

   #if IS_ENABLED(CONFIG_BRIDGE_NETFILTER)
    dev_hold(entry->physin);
    dev_hold(entry->physout);
   #endif
  + return true;
   }
   EXPORT_SYMBOL_GPL(nf_queue_entry_get_refs);

  @@ -196,7 +198,10 @@ static int __nf_queue(struct sk_buff *skb, const
  struct nf_hook_state *state,

    __nf_queue_entry_init_physdevs(entry);

  - nf_queue_entry_get_refs(entry);
  + if (!nf_queue_entry_get_refs(entry)) {
  + kfree(entry);
  + return -ENOTCONN;
  + }

    switch (entry->state.pf) {
    case AF_INET:
  diff --git a/net/netfilter/nfnetlink_queue.c b/net/netfilter/nfnetlink_queue.c
  index ea2d9c2a44cf..64a6acb6aeae 100644
  --- a/net/netfilter/nfnetlink_queue.c
  +++ b/net/netfilter/nfnetlink_queue.c
  @@ -710,9 +710,15 @@ static struct nf_queue_entry *
   nf_queue_entry_dup(struct nf_queue_entry *e)
   {
    struct nf_queue_entry *entry = kmemdup(e, e->size, GFP_ATOMIC);
  - if (entry)
  - nf_queue_entry_get_refs(entry);
  - return entry;
  +
  + if (!entry)
  + return NULL;
  +
  + if (nf_queue_entry_get_refs(entry))
  + return entry;
  +
  + kfree(entry);
  + return NULL;
   }

   #if IS_ENABLED(CONFIG_BRIDGE_NETFILTER)

  [Backport Commit 4d032d60432327f068f03b516f5b6c51ceb17d15]
  diff --git a/include/net/netfilter/nf_queue.h 
b/include/net/netfilter/nf_queue.h
  index 814058d0f167..f38cc6092c5a 100644
  --- a/include/net/netfilter/nf_queue.h
  +++ b/include/net/netfilter/nf_queue.h
  @@ -32,7 +32,7 @@ void nf_register_queue_handler(struct net *net, const 
struct nf_queue_handler *q
   void nf_unregister_queue_handler(struct net *net);
   void nf_reinject(struct nf_queue_entry *entry, unsigned int verdict);

  -void nf_queue_entry_get_refs(struct nf_queue_entry *entry);
  +bool nf_queue_entry_get_refs(struct nf_queue_entry *entry);
   void nf_queue_entry_release_refs(struct nf_queue_entry *entry);

   static inline void init_hashrandom(u32 *jhash_initval)
  diff --git a/net/netfilter/nf_queue.c b/net/netfilter/nf_queue.c
  index

[Kernel-packages] [Bug 1989144] Re: unprivileged users may trigger page cache invalidation WARN

This bug is awaiting verification that the linux-
azure-4.15/4.15.0-1157.172 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-bionic' to
'verification-done-bionic'. If the problem still exists, change the tag
'verification-needed-bionic' to 'verification-failed-bionic'.

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-bionic-linux-azure-4.15 verification-needed-bionic

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

Title:
  unprivileged users may trigger page cache invalidation WARN

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

Bug description:
  [Impact]
  Unprivileged users may trigger a page cache invalidation failure when doing 
parallel direct I/O and buffered I/O. On some kernels, that may lead to a WARN.

  [   22.415082] WARNING: CPU: 3 PID: 3404 at 
/build/linux-GtMq7R/linux-4.15.0/fs/iomap.c:903 iomap_dio_actor+0xbd/0x460
  [   22.415083] Modules linked in: xfs isofs kvm_intel kvm irqbypass joydev 
input_leds serio_raw ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp 
libiscsi scsi_transport_iscsi autofs4 btrfs zstd_compress raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd 
psmouse ahci libahci virtio_blk virtio_net
  [   22.415099] CPU: 3 PID: 3404 Comm: xfs_io Not tainted 4.15.0-192-generic 
#203-Ubuntu
  [   22.415100] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 
1.15.0-1 04/01/2014
  [   22.415103] RIP: 0010:iomap_dio_actor+0xbd/0x460
  [   22.415104] RSP: 0018:b7c782fe7bf0 EFLAGS: 00010202
  [   22.415104] RAX: 0002 RBX:  RCX: 
0009
  [   22.415105] RDX: 01ff RSI:  RDI: 
b7c782fe7e20
  [   22.415105] RBP: b7c782fe7c68 R08: b7c782fe7c88 R09: 
9bbc9f48fba0
  [   22.415106] R10: 0001 R11:  R12: 
0009
  [   22.415106] R13: 9bbc9f48fba0 R14: b7c782fe7c88 R15: 
1000
  [   22.415107] FS:  7f2b802ed700() GS:9bbcbfd8() 
knlGS:
  [   22.415107] CS:  0010 DS:  ES:  CR0: 80050033
  [   22.415108] CR2: 01639000 CR3: 1e6b0003 CR4: 
00760ee0
  [   22.415110] PKRU: 5554
  [   22.415110] Call Trace:
  [   22.415122]  ? iomap_dio_zero+0x130/0x130
  [   22.415123]  iomap_apply+0xa5/0x120
  [   22.415124]  ? iomap_dio_zero+0x130/0x130
  [   22.415125]  iomap_dio_rw+0x2f3/0x430
  [   22.415126]  ? iomap_dio_zero+0x130/0x130
  [   22.415148]  xfs_file_dio_aio_read+0x68/0xf0 [xfs]
  [   22.415157]  ? xfs_file_dio_aio_read+0x68/0xf0 [xfs]
  [   22.415165]  xfs_file_read_iter+0xbf/0xe0 [xfs]
  [   22.415170]  new_sync_read+0xe4/0x130
  [   22.415171]  __vfs_read+0x29/0x40
  [   22.415172]  vfs_read+0x8e/0x130
  [   22.415173]  SyS_pread64+0x95/0xb0
  [   22.415176]  do_syscall_64+0x73/0x130
  [   22.415183]  entry_SYSCALL_64_after_hwframe+0x41/0xa6
  [   22.415184] RIP: 0033:0x7f2b7fbc0b73
  [   22.415185] RSP: 002b:7ffc134e1a58 EFLAGS: 0246 ORIG_RAX: 
0011
  [   22.415186] RAX: ffda RBX:  RCX: 
7f2b7fbc0b73
  [   22.415186] RDX: 1000 RSI: 01639000 RDI: 
0003
  [   22.415186] RBP:  R08:  R09: 

  [   22.415187] R10:  R11: 0246 R12: 
7ffc134e1b00
  [   22.415187] R13: 0002 R14:  R15: 

  [   22.415188] Code: 21 d0 48 89 45 a0 0f 85 aa 03 00 00 41 0f b7 46 18 66 83 
f8 03 0f 84 7e 02 00 00 66 83 f8 04 74 52 66 83 f8 01 0f 84 c8 02 00 00 <0f> 0b 
48 c7 45 a0 fb ff ff ff 48 8b 5d d0 65 48 33 1c 25 28 00 

  [Test case]
  Run xfstests generic/446 test.

  [Potential regressions]
  Data corruption could be caused, though it is expected to be caused in such 
scenarions anyway. That should affecte direct I/O.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989144/+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 1990985] Re: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems

This bug is awaiting verification that the linux-
azure-4.15/4.15.0-1157.172 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-bionic' to
'verification-done-bionic'. If the problem still exists, change the tag
'verification-needed-bionic' to 'verification-failed-bionic'.

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 removed: verification-done-bionic
** Tags added: kernel-spammed-bionic-linux-azure-4.15 verification-needed-bionic

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

Title:
  ACPI: processor idle: Practically limit "Dummy wait" workaround to old
  Intel systems

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed

Bug description:
  IMPACT:
  Old, circa 2002 chipsets have a bug: they don't go idle when they are
  supposed to.  So, a workaround was added to slow the CPU down and
  ensure that the CPU waits a bit for the chipset to actually go idle.
  This workaround is ancient and has been in place in some form since
  the original kernel ACPI implementation.

  But, this workaround is very painful on modern systems.  The "inl()"
  can take thousands of cycles (see Link: for some more detailed
  numbers and some fun kernel archaeology).

  First and foremost, modern systems should not be using this code.
  Typical Intel systems have not used it in over a decade because it is
  horribly inferior to MWAIT-based idle.

  Despite this, people do seem to be tripping over this workaround on
  AMD system today.

  Limit the "dummy wait" workaround to Intel systems.  Keep Modern AMD
  systems from tripping over the workaround.  Remotely modern Intel
  systems use intel_idle instead of this code and will, in practice,
  remain unaffected by the dummy wait.

  Reported-by: K Prateek Nayak 
  Suggested-by: Rafael J. Wysocki 
  Signed-off-by: Dave Hansen 
  Reviewed-by: Mario Limonciello 
  Tested-by: K Prateek Nayak 
  Link: 
https://lore.kernel.org/all/20220921063638.2489-1-kprateek.na...@amd.com/
  Link: https://lkml.kernel.org/r/20220922184745.3252932-1-dave.han...@intel.com

  FIX:

  This issue pertains to  all Zen based processors starting with
  Naples(Zen1). All LTS releases will need this fix:

  
https://github.com/torvalds/linux/commit/e400ad8b7e6a1b9102123c6240289a811501f7d9

  TESTCASE:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990985/+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 1990690] Re: Users belonging to video group may trigger a deadlock WARN

This bug is awaiting verification that the linux-
azure-4.15/4.15.0-1157.172 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-bionic' to
'verification-done-bionic'. If the problem still exists, change the tag
'verification-needed-bionic' to 'verification-failed-bionic'.

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-bionic-linux-azure-4.15 verification-needed-bionic

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

Title:
  Users belonging to video group may trigger a deadlock WARN

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

Bug description:
  [Impact]
  One of the fixing commits for CVE-2021-33655, commit 159a96b199b4
  ("fbcon: Prevent that screen size is smaller than font size") introduced
  an extraneous lock_fb_info line into the ioctl flow in fbmem.c.

  This line only exists in bionic tree.

  Users belonging to video group may trigger a deadlock and potentially
  lock the system.

  
  WARNING: possible recursive locking detected
  4.15.0-195-generic #206 Not tainted
  
  refresh/1248 is trying to acquire lock:
    (_info->lock){+.+.}, at: [<4c154cfe>] lock_fb_info+0x1d/0x40

  but task is already holding lock:
    (_info->lock){+.+.}, at: [<4c154cfe>] lock_fb_info+0x1d/0x40

  other info that might help us debug this:
    Possible unsafe locking scenario:
  CPU0
  
     lock(_info->lock);
     lock(_info->lock);

  *** DEADLOCK ***
    May be due to missing lock nesting notation
   2 locks held by refresh/1248:
    #0:  (console_lock){+.+.}, at: [<8000aa2b>] do_fb_ioctl+0x435/0x5e0
    #1:  (_info->lock){+.+.}, at: [<4c154cfe>] lock_fb_info+0x1d/0x40

  stack backtrace:
   CPU: 0 PID: 1248 Comm: refresh Not tainted 4.15.0-195-generic #206
   Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014
   Call Trace:
    dump_stack+0x98/0xd2
    __lock_acquire+0x736/0x1480
    ? sched_clock_local+0x17/0x90
    ? sched_clock+0x9/0x10
    ? sched_clock_local+0x17/0x90
    lock_acquire+0xa3/0x1e0
    ? lock_acquire+0xa3/0x1e0
    ? lock_fb_info+0x1d/0x40
    ? lock_fb_info+0x1d/0x40
    __mutex_lock+0x65/0x970
    ? lock_fb_info+0x1d/0x40
    ? sched_clock_local+0x17/0x90
    ? lock_acquire+0xa3/0x1e0
    mutex_lock_nested+0x1b/0x20
    ? mutex_lock_nested+0x1b/0x20
    lock_fb_info+0x1d/0x40
    do_fb_ioctl+0x57a/0x5e0
    ? __fd_install+0x5/0x250
    fb_ioctl+0x33/0x40
    ? fb_ioctl+0x33/0x40
    do_vfs_ioctl+0xa9/0x6d0
    ? putname+0x4c/0x60
    ? do_sys_open+0x13d/0x370
    SyS_ioctl+0x79/0x90
    do_syscall_64+0x7b/0x1e0
    entry_SYSCALL_64_after_hwframe+0x46/0xbb
   RIP: 0033:0x7f22acca7217
   RSP: 002b:7ffe2a930b48 EFLAGS: 0213 ORIG_RAX: 0010
   RAX: ffda RBX:  RCX: 7f22acca7217
   RDX: 7ffe2a930c30 RSI: 4601 RDI: 0003
   RBP: 7ffe2a930d40 R08:  R09: 
   R10:  R11: 0213 R12: 5624ac8fc7c0
   R13: 7ffe2a930e20 R14:  R15: 

  [Test case]
  Run a sample framebuffer userspace test to call FBIOPUT_VSCREENINFO
  and verified with LOCKDEP.

  [Potential regressions]
  There are no new potential regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990690/+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 1990698] Re: Bionic update: upstream stable patchset 2022-09-23

2022-12-07 Thread Andy Whitcroft

** Tags removed: kernel-spammed-bionic-linux-aws kernel-spammed-bionic-
linux-azure-4.15 verification-needed-bionic

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

Title:
  Bionic update: upstream stable patchset 2022-09-23

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

Bug description:
  SRU Justification

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

     upstream stable patchset 2022-09-23

  Ported from the following upstream stable releases:
  v4.14.291, v4.19.256

     from git://git.kernel.org/

  Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put
  ntfs: fix use-after-free in ntfs_ucsncmp()
  ARM: crypto: comment out gcc warning that breaks clang builds
  mt7601u: add USB device ID for some versions of XiaoDu WiFi Dongle.
  ACPI: video: Force backlight native for some TongFang devices
  macintosh/adb: fix oob read in do_adb_query() function
  Makefile: link with -z noexecstack --no-warn-rwx-segments
  x86: link vdso and boot with -z noexecstack --no-warn-rwx-segments
  ALSA: bcd2000: Fix a UAF bug on the error path of probing
  add barriers to buffer_uptodate and set_buffer_uptodate
  HID: wacom: Don't register pad_input for touch switch
  KVM: SVM: Don't BUG if userspace injects an interrupt with GIF=0
  KVM: x86: Mark TSS busy during LTR emulation _after_ all fault checks
  KVM: x86: Set error code to segment selector on LLDT/LTR non-canonical #GP
  ALSA: hda/conexant: Add quirk for LENOVO 20149 Notebook model
  ALSA: hda/cirrus - support for iMac 12,1 model
  vfs: Check the truncate maximum size in inode_newsize_ok()
  fs: Add missing umask strip in vfs_tmpfile
  usbnet: Fix linkwatch use-after-free on disconnect
  parisc: Fix device names in /proc/iomem
  drm/nouveau: fix another off-by-one in nvbios_addr
  drm/amdgpu: Check BO's requested pinning domains against its preferred_domains
  iio: light: isl29028: Fix the warning in isl29028_remove()
  fuse: limit nsec
  md-raid10: fix KASAN warning
  ia64, processor: fix -Wincompatible-pointer-types in ia64_get_irr()
  PCI: Add defines for normal and subtractive PCI bridges
  powerpc/fsl-pci: Fix Class Code of PCIe Root Port
  powerpc/powernv: Avoid crashing if rng is NULL
  MIPS: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK
  USB: HCD: Fix URB giveback issue in tasklet function
  netfilter: nf_tables: fix null deref due to zeroed list head
  arm64: Do not forget syscall when starting a new thread.
  arm64: fix oops in concurrently setting insn_emulation sysctls
  ext2: Add more validity checks for inode counts
  ARM: dts: imx6ul: add missing properties for sram
  ARM: dts: imx6ul: fix qspi node compatible
  ARM: OMAP2+: display: Fix refcount leak bug
  ACPI: PM: save NVS memory for Lenovo G40-45
  ACPI: LPSS: Fix missing check in register_device_clock()
  PM: hibernate: defer device probing when resuming from hibernation
  selinux: Add boundary check in put_entry()
  ARM: findbit: fix overflowing offset
  ARM: bcm: Fix refcount leak in bcm_kona_smc_init
  x86/pmem: Fix platform-device leak in error path
  ARM: dts: ast2500-evb: fix board compatible
  soc: fsl: guts: machine variable might be unset
  cpufreq: zynq: Fix refcount leak in zynq_get_revision
  ARM: dts: qcom: pm8841: add required thermal-sensor-cells
  arm64: dts: qcom: msm8916: Fix typo in pronto remoteproc node
  regulator: of: Fix refcount leak bug in of_get_regulation_constraints()
  thermal/tools/tmon: Include pthread and time headers in tmon.h
  dm: return early from dm_pr_call() if DM device is suspended
  drm/radeon: fix potential buffer overflow in ni_set_mc_special_registers()
  drm/mediatek: Add pull-down MIPI operation in mtk_dsi_poweroff function
  i2c: Fix a potential use after free
  wifi: iwlegacy: 4965: fix potential off-by-one overflow in 
il4965_rs_fill_link_cmd()
  drm: bridge: adv7511: Add check for mipi_dsi_driver_register
  media: hdpvr: fix error value returns in hdpvr_read
  drm/vc4: dsi: Correct DSI divider calculations
  drm/rockchip: vop: Don't crash for invalid duplicate_state()
  drm/mediatek: dpi: Remove output format of YUV
  drm: bridge: sii8620: fix possible off-by-one
  media: platform: mtk-mdp: Fix mdp_ipi_comm structure alignment
  tcp: make retransmitted SKB fit into the send window
  selftests: timers: valid-adjtimex: build fix for newer toolchains
  selftests: timers: clocksource-switch: fix passing errors from child
  fs:

[Kernel-packages] [Bug 1996740] Re: 5.15.0-53-generic no longer boots

This bug is awaiting verification that the linux-aws/5.15.0-1027.31
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' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

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-aws verification-needed-jammy

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

Title:
  5.15.0-53-generic no longer boots

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

Bug description:
  == SRU Justification ==
  [Impact]
  "UBUNTU: SAUCE: Revert "drm/amd/display: Add helper for blanking all dp
  displays" caused AMD Navi10 GFX to panic at boot.

  [Fix]
  Backport the revised version of "drm/amd/display: Add helper for
  blanking all dp displays".

  [Test]
  Users confirmed the issue went away with this fix.
  We also verified the original issue we fixed didn't reappear.

  [Where problems could occur]
  We didn't test all the combination of dce110/dcn10/dcn30/dcn31, so many
  cases are untested, hence the potential risk is there.

  == Original Bug Report ==

  Running Ubuntu 22.04.1 Jammy.
  After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no 
longer fully boots.
  After the normal splash screen the screen goes black and the computer is not 
reachable on the network. Changing to another TTY does not work.

  New kernel version: 5.15.0-53.59

  I will attach the output of journalctl -b -1, please let me know what other 
info you need.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  johan  2549 F pulseaudio
   /dev/snd/controlC0:  johan  2549 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2020-12-01 (714 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  IwConfig:
   lono wireless extensions.

   enp37s0   no wireless extensions.

   wgnfs no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7C52
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic 
root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-52-generic N/A
   linux-backports-modules-5.15.0-52-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.6
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-52-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago)
  UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 07/23/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 3.G0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M-A PRO MAX (MS-7C52)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7C52
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996740/+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 1852741] Re: [22.10 FEAT] zKVM: Crypto Passthrough Hotplug - kernel part

2022-12-07 Thread Frank Heimes

Initial bug was reported just for jammy.
So to unblock the process I'm marking this as verification-done.

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

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

Title:
  [22.10 FEAT] zKVM: Crypto Passthrough Hotplug - kernel part

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  The initial implementation of Crypto Passthrough for KVM does not include 
hotplug. This feature adds hotplug support, which allows to dynamically assign 
and remove crypto adapters to/from a running KVM guest.
  [
  Available with kernel 5.3
  ]
  new target kernel: 5.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1852741/+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 1980621] Re: Fix blank screen on Thinkpad ADL 4K+ panel

This bug is awaiting verification that the linux-
bluefield/5.15.0-1010.12 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' to 'verification-
done-jammy'. If the problem still exists, change the tag 'verification-
needed-jammy' to 'verification-failed-jammy'.

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 removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-bluefield verification-needed-jammy

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

Title:
  Fix blank screen on Thinkpad ADL 4K+ panel

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Won't Fix
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  Set screen off on ThinkPad P1G5 with 4k+ panel.
  The screen will never be back.

  [Fix]
  It's a upstream kernel regression.
  And reverted by upstream.

  [Test]
  Verified on hardware, screen on/off 20 times OK.

  [Where problems could occur]
  Low risk, it reverts a regression and may break i915 driver.

  On 5.14-oem and Jammy kernel, This commit was claimed to backport
  commit 73867c8709b5 ("drm/i915/display: Remove check for low voltage sku for 
max dp source rate")
  But it's not kind of it.
  So revert it instead.

  On 5.17 kernel, revert it by upstream commit.

  Unstable kernel already got it.

  
  V2:
  [Impact]
  Set screen off on ThinkPad P1G5 with 4k+ panel.
  The screen will never be back.

  [Fix]
  Reload link rate as WA to fix the issue.

  [Test]
  Verified on hardware, screen on/off 20 times OK.

  [Where problems could occur]
  It may break DP output on Intel platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1980621/+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 1965927] Re: [Ubuntu 22.04] mpt3sas: Request to include latest bug fix patches

This bug is awaiting verification that the linux-
bluefield/5.15.0-1010.12 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' to 'verification-
done-jammy'. If the problem still exists, change the tag 'verification-
needed-jammy' to 'verification-failed-jammy'.

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 removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-bluefield verification-needed-jammy

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

Title:
[Ubuntu 22.04] mpt3sas: Request to include latest bug fix patches

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

Bug description:
[Impact]
Request to include below mpt3sas driver bug fix patches in Ubuntu 22.04
kernel. These patches got accepted by the upstream and please find the
corresponding commit IDs as below,

5db207d66d mpt3sas: Fix incorrect 4gb boundary check
ca23ac823c mpt3sas: Remove scsi_dma_map errors messages
9211faa39a scsi: mpt3sas: Update persistent trigger pages from sysfs interface

[Fix]
Below is the summary of each of the above bug fix commits,

1. mpt3sas: Fix incorrect 4gb boundary check:
Without this patch, driver was checking whether any of it's pool crosses
the 4gb boundary or not using the pool's virtual address instead of using it's
dma address. So some time driver may false positively assume that the pool as
crossed the 4gb boundary region (as it observes that pool's virtual address is
crossing the 4gb boundary) even though it is really not.

2. mpt3sas: Remove scsi_dma_map errors messages:
When driver set the DMA mask to 32bit then we observe that the SWIOTLB
bounce buffers are getting exhausted quickly. For most of the IOs driver
observe that scsi_dma_map() API returned with failure status and hence driver
was printing below error message. Since this error message is getting printed
per IO and if user issues heavy IOs then we observe that kernel overwhelmed
with this error message. Also we will observe the kernel panic when the serial
console is enabled. So to limit this issue, we removed this error message
though this patch.
"scsi_dma_map failed: request for 1310720 bytes!"

3. mpt3sas: Update persistent trigger pages from sysfs interface:
When user set's any diag buffer trigger conditions then driver has to save
these trigger conditions in the controller Firmware's NVRAM region. So that
when system reboots then driver can get these trigger conditions from
Firmware's NVRAM region and set these trigger conditions automatically. so that
user no need to set these conditions again. Without this patch driver was not
not saving these user provided trigger conditions in the Firmware's NVRAM
region.

Please let me if I have missed to add any data.

[Test Plan]

1. All drives attached to the controller are Enumerated in OS
2. IO stress for 5Hrs
3. Created a filesystem and done some IO transitions
4. Controller reset and TMs and while IOs are running
5. driver load and unload
6. Reboot loop
7. Verified that the diag trigger settings are persistent across the reboots.

[Where problems could occur]

The regression risk is low.

[Other Info]

https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/mpt3sas_lp_1965927

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

[Kernel-packages] [Bug 1978986] Re: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average luminance

This bug is awaiting verification that the linux-
bluefield/5.15.0-1010.12 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' to 'verification-
done-jammy'. If the problem still exists, change the tag 'verification-
needed-jammy' to 'verification-failed-jammy'.

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 removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-bluefield verification-needed-jammy

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

Title:
  [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-
  average luminance

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-5.14 source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  The brightness is not changed obviously during 200 to 255 on AMD
  or 400 to 512 on Intel..

  [Fix]
  Read HDR meta to detect the max and min luminance.
  max_cll defines the content light luminance for individual pixel.
  max_fall defines frame-average level luminance.
  Use max_fall value instead of max_cll as a limit for brightness control.

  [Test]
  Verified on AMD Cezanne, Barcelo, Rembrandt and Intel ADL, also on LCD panel 
and OLED panel. The brightness is changed more obivously on OLED panel, and
  no affect on LCD panel.

  [Where problems could occur]
  Low risk, It may cause the max brightness can't be set.

  All 3 patches are in drm-misc tree.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1978986/+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 1980829] Re: System freeze after resuming from suspend due to PCI ASPM settings

This bug is awaiting verification that the linux-
bluefield/5.15.0-1010.12 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' to 'verification-
done-jammy'. If the problem still exists, change the tag 'verification-
needed-jammy' to 'verification-failed-jammy'.

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 removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-bluefield verification-needed-jammy

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

Title:
  System freeze after resuming from suspend due to PCI ASPM settings

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux-oem-6.0 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-5.14 source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  For Jammy/Kinetic SRU

  [Impact]
  While doing some tests such as suspend/resume or CPU stress tests the system 
would hang.

  [Fix]
  The 2 commits fix the issue, but still not get accepted yet.
  
https://patchwork.ozlabs.org/project/linux-pci/patch/20220705060014.10050-1-vid...@nvidia.com/
  
https://patchwork.ozlabs.org/project/linux-pci/patch/20220509073639.2048236-1-kai.heng.f...@canonical.com/

  So, I created a DMI quirk to make the patches only affects on listed
  platforms.

  [Test]
  Verified on the failed machines and ODM also verified on their side.

  [Where problems could occur]
  The patches only affects on the listed platforms, and won't affect other 
platforms.

  ==

  [Impact]
  While doing some tests such as suspend/resume or CPU stress tests the system 
would hang.

  [Fix]
  The 2 commits fix the issue, but still not get accepted yet.
  
https://patchwork.ozlabs.org/project/linux-pci/patch/20220705060014.10050-1-vid...@nvidia.com/
  
https://patchwork.ozlabs.org/project/linux-pci/patch/20220509073639.2048236-1-kai.heng.f...@canonical.com/

  [Test]
  Verified on the failed machines and ODM also verified on their side.

  [Where problems could occur]
  The 2 patches look pretty safe to me, they try to preserve the ASPM state of 
devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1980829/+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 1987232] Re: WARN in trace_event_dyn_put_ref

This bug is awaiting verification that the linux-
bluefield/5.15.0-1010.12 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' to 'verification-
done-jammy'. If the problem still exists, change the tag 'verification-
needed-jammy' to 'verification-failed-jammy'.

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 removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-bluefield verification-needed-jammy

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

Title:
  WARN in trace_event_dyn_put_ref

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Confirmed

Bug description:
  [SRU Justification]

  Impact: Some imbalanced ref-counting produces kernel warnings
  regularly. Since it is a warning level, this triggers system
  monitoring on servers which in turn causes unnecessary work for
  inspecting the logs.

  Fix: There is a fix upstream and also backported to the upstream
  stable branch. However we are still a bit behind catching up with the
  latest versions. Since this is having quite an impact and the fix is
  rather straight forward, we pull this in from upstream stable ahead of
  time.

  Test case: tbd

  Regression potential: Regressions would manifest as different errors
  related to ref-counting.

  ---

  I have systems that are regularly hitting a WARN in
  trace_event_dyn_put_ref.

  The exact message is:

  WARNING: CPU: 1 PID: 30309 at kernel/trace/trace_dynevent.c:46
  +trace_event_dyn_put_ref+0x15/0x20

  With the following stacktrace:

   perf_trace_init+0x8f/0xd0
   perf_tp_event_init+0x1f/0x40
   perf_try_init_event+0x4a/0x130
   perf_event_alloc+0x497/0xf40
   __do_sys_perf_event_open+0x1d4/0xf70
   __x64_sys_perf_event_open+0x20/0x30
   do_syscall_64+0x5c/0xc0
   entry_SYSCALL_64_after_hwframe+0x44/0xae

  I've debugged this and worked with upstream to get a fix into Linux.
  It was recently merged in 6.0-rc2.  See here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.0-rc2=7249921d94ff64f67b733eca0b68853a62032b3d

  The problem started appearing as soon as our systems picked up the 
linux-aws-5.15 branch for Focal.  (That was 5.15.0-1015-aws, if memory serves). 
 Could you please cherry pick this fix and pull it back to the the linux and 
linux-aws kernels for Focal?  There's test here: 
https://lore.kernel.org/all/cover.1660347763.git.k...@templeofstupid.com/ that 
reproduces the problem very reliably for me.  With the patch applied, I no 
longer get the WARNs.
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 22 17:32 seq
   crw-rw 1 root audio 116, 33 Aug 22 17:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.24
  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: skip
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Amazon EC2 c5d.12xlarge
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1015-aws 
root=PARTUUID=4986e35b-1bd5-45d3-b528-fa2edb861a38 ro console=tty1 
console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1
  ProcVersionSignature: Ubuntu 5.15.0-1015.19~20.04.1-aws 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-1015-aws N/A
   linux-backports-modules-5.15.0-1015-aws  N/A
   linux-firmware   N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.15.0-1015-aws x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: False
  dmi.bios.date: 10/16/2017
  dmi.bios.release: 1.0
  dmi.bios.vendor: Amazon EC2
  dmi.bios.version: 1.0
  dmi.board.asset.tag: i-03f5d8581c7ad94aa
  dmi.board.vendor: Amazon EC2
  dmi.chassis.asset.tag: Amazon EC2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Amazon EC2
  dmi.modalias:

[Kernel-packages] [Bug 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed

This bug is awaiting verification that the linux-
bluefield/5.15.0-1010.12 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' to 'verification-
done-jammy'. If the problem still exists, change the tag 'verification-
needed-jammy' to 'verification-failed-jammy'.

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 removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-bluefield verification-needed-jammy

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

Title:
  scsi: hisi_sas: Increase debugfs_dump_index after dump is  completed

Status in kunpeng920:
  Fix Released
Status in kunpeng920 ubuntu-20.04-hwe series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  Trigger dump on hisi_sas in debugfs will cause kernel oops.

  [Test Plan]
  1) modprobe hisi_sas_main with "debugfs_enable=1"
  2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump
  3) dmesg | grep Oops

  [Regression Risk]
  Only touch code in hisi_sas. Need to run full test on hisi_sas. Other 
drivers/platforms are not affected.

  
  [Bug Description]
   When the hisi_sas_main driver is loaded, the DFX function is enabled. When 
the dump is triggered or the SAS controller is reset, call_trace is displayed. 
In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled.

  [Steps to Reproduce]
  1)dmesg -C
  2)dmesg
  3)lsblk
  4)lsscsi -p
  5)lsmod | grep hisi_sas_v3
  6)rmmod hisi_sas_v3_hw
  7)rmmod hisi_sas_main
  8)modprobe hisi_sas_main debugfs_enable=1
  9)modprobe hisi_sas_v3_hw
  10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/
  11)ll
  12)echo 1 > trigger_dump
  13)echo 1 > trigger_dump
  14)dmesg

  [Actual Results]
  [ 1005.899976] sas: broadcast received: 0
  [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8
  [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change
  [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0
  [ 1005.901793] sas: broadcast received: 0
  [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8
  [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change
  [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0
  [ 1005.903586] sas: broadcast received: 0
  [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8
  [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change
  [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0
  [ 1005.905404] sas: broadcast received: 0
  [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8
  [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change
  [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0
  [ 1005.907182] sas: broadcast received: 0
  [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8
  [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change
  [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0
  [ 1005.909025] sas: broadcast received: 0
  [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8
  [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change
  [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0
  [ 1005.910947] sas: broadcast received: 0
  [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8
  [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change
  [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0
  [ 1005.912877] sas: broadcast received: 0
  [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8
  [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change
  [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0
  [ 1005.915221] sas: broadcast received: 0
  [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170
  [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change
  [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0
  [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk
  [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk
  [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues
  [ 1008.112712] scsi host6: hisi_sas_v3_hw
  [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues
  [ 1010.433120] scsi host7: hisi_sas_v3_hw
  root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0#

  [Expected Results]
  Recurrence Logs：
  [ 360.441633] SET = 0, FnV = 0
  [ 360.444689] EA = 0, S1PTW = 0
  [ 360.447863] Data abort info:
  [ 360.450783] ISV = 0, ISS = 0x0044
  [

[Kernel-packages] [Bug 1990242] Re: Intel graphic driver is not probing[8086:468b]

This bug is awaiting verification that the linux-
bluefield/5.15.0-1010.12 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' to 'verification-
done-jammy'. If the problem still exists, change the tag 'verification-
needed-jammy' to 'verification-failed-jammy'.

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-bluefield verification-needed-jammy

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

Title:
  Intel graphic driver is not probing[8086:468b]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  Got blank screen after entered desktop

  [Fix]
  Below commit in linux-next fixes the issue.
  6215a7c8f552 drm/i915: Add new ADL-S pci id

  [Test]
  Verified on the target machine.

  [Where problems could occur]
  It only adds an ID to the list, should be pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1990242/+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 1989218] Re: Jammy update: v5.15.59 upstream stable release

** Tags removed: verification-needed-jammy

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

Title:
  Jammy update: v5.15.59 upstream stable release

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

Bug description:
  SRU Justification

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

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

  Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put
  Revert "ocfs2: mount shared volume without ha stack"
  ntfs: fix use-after-free in ntfs_ucsncmp()
  fs: sendfile handles O_NONBLOCK of out_fd
  secretmem: fix unhandled fault in truncate
  mm: fix page leak with multiple threads mapping the same page
  hugetlb: fix memoryleak in hugetlb_mcopy_atomic_pte
  asm-generic: remove a broken and needless ifdef conditional
  s390/archrandom: prevent CPACF trng invocations in interrupt context
  nouveau/svm: Fix to migrate all requested pages
  drm/simpledrm: Fix return type of simpledrm_simple_display_pipe_mode_valid()
  watch_queue: Fix missing rcu annotation
  watch_queue: Fix missing locking in add_watch_to_object()
  tcp: Fix data-races around sysctl_tcp_dsack.
  tcp: Fix a data-race around sysctl_tcp_app_win.
  tcp: Fix a data-race around sysctl_tcp_adv_win_scale.
  tcp: Fix a data-race around sysctl_tcp_frto.
  tcp: Fix a data-race around sysctl_tcp_nometrics_save.
  tcp: Fix data-races around sysctl_tcp_no_ssthresh_metrics_save.
  ice: check (DD | EOF) bits on Rx descriptor rather than (EOP | RS)
  ice: do not setup vlan for loopback VSI
  scsi: ufs: host: Hold reference returned by of_parse_phandle()
  Revert "tcp: change pingpong threshold to 3"
  octeontx2-pf: Fix UDP/TCP src and dst port tc filters
  tcp: Fix data-races around sysctl_tcp_moderate_rcvbuf.
  tcp: Fix a data-race around sysctl_tcp_limit_output_bytes.
  tcp: Fix a data-race around sysctl_tcp_challenge_ack_limit.
  scsi: core: Fix warning in scsi_alloc_sgtables()
  scsi: mpt3sas: Stop fw fault watchdog work item during system shutdown
  net: ping6: Fix memleak in ipv6_renew_options().
  ipv6/addrconf: fix a null-ptr-deref bug for ip6_ptr
  net/tls: Remove the context from the list in tls_device_down
  igmp: Fix data-races around sysctl_igmp_qrv.
  net: pcs: xpcs: propagate xpcs_read error to xpcs_get_state_c37_sgmii
  net: sungem_phy: Add of_node_put() for reference returned by of_get_parent()
  tcp: Fix a data-race around sysctl_tcp_min_tso_segs.
  tcp: Fix a data-race around sysctl_tcp_min_rtt_wlen.
  tcp: Fix a data-race around sysctl_tcp_autocorking.
  tcp: Fix a data-race around sysctl_tcp_invalid_ratelimit.
  Documentation: fix sctp_wmem in ip-sysctl.rst
  macsec: fix NULL deref in macsec_add_rxsa
  macsec: fix error message in macsec_add_rxsa and _txsa
  macsec: limit replay window size with XPN
  macsec: always read MACSEC_SA_ATTR_PN as a u64
  net: macsec: fix potential resource leak in macsec_add_rxsa() and 
macsec_add_txsa()
  net: mld: fix reference count leak in mld_{query | report}_work()
  tcp: Fix data-races around sk_pacing_rate.
  net: Fix data-races around sysctl_[rw]mem(_offset)?.
  tcp: Fix a data-race around sysctl_tcp_comp_sack_delay_ns.
  tcp: Fix a data-race around sysctl_tcp_comp_sack_slack_ns.
  tcp: Fix a data-race around sysctl_tcp_comp_sack_nr.
  tcp: Fix data-races around sysctl_tcp_reflect_tos.
  ipv4: Fix data-races around sysctl_fib_notify_on_flag_change.
  i40e: Fix interface init with MSI interrupts (no MSI-X)
  sctp: fix sleep in atomic context bug in timer handlers
  octeontx2-pf: cn10k: Fix egress ratelimit configuration
  virtio-net: fix the race between refill work and close
  perf symbol: Correct address for bss symbols
  sfc: disable softirqs for ptp TX
  sctp: leave the err path free in sctp_stream_init to sctp_stream_free
  ARM: crypto: comment out gcc warning that breaks clang builds
  mm/hmm: fault non-owner device private entries
  page_alloc: fix invalid watermark check on a negative value
  ARM: 9216/1: Fix MAX_DMA_ADDRESS overflow
  EDAC/ghes: Set the DIMM label unconditionally
  docs/kernel-parameters: Update descriptions for "mitigations=" param with 
retbleed
  locking/rwsem: Allow slowpath writer to ignore handoff bit if not set by 
first waiter
  x86/bugs: Do not enable IBPB at firmware entry when IBPB is not available
  Linux 5.15.59
  UBUNTU: Upstream stable to v5.15.59

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1981649] Re: Jammy update: v5.15.44 upstream stable release

** Tags removed: verification-needed-jammy

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

Title:
  Jammy update: v5.15.44 upstream stable release

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

Bug description:
  
  SRU Justification

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981649/+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 1991403] Re: mlxbf_gige: fix devm_ioremap error handling

This bug is awaiting verification that the linux-
bluefield/5.15.0-1010.12 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' to 'verification-
done-jammy'. If the problem still exists, change the tag 'verification-
needed-jammy' to 'verification-failed-jammy'.

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-bluefield verification-needed-jammy

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

Title:
  mlxbf_gige: fix devm_ioremap error handling

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

Bug description:
  SRU Justification:

  [Impact]

  The following upstream commit was recently added to Jammy:
3a1a274e933f mlxbf_gige: compute MDIO period based on i1clk

  This patch added driver logic that includes a "devm_ioremap"
  call, but the error handling logic pertaining to this call
  is incorrect.

  [Fix]

  The "devm_ioremap" function returns NULL on error, it doesn't 
  return error pointers.  The error handling logic has been
  fixed accordingly.

  [Test Case]

  Boot platform and bring up "oob_net0" interface properly
  Test that network traffic works properly

  [Regression Potential]

  Low, as the patch was reviewed upstream

  [Other]

  None

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1991403/+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 1986798] Re: Remove unused variable from i915 psr

This bug is awaiting verification that the linux-
bluefield/5.15.0-1010.12 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' to 'verification-
done-jammy'. If the problem still exists, change the tag 'verification-
needed-jammy' to 'verification-failed-jammy'.

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-bluefield verification-needed-jammy

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

Title:
  Remove unused variable from i915 psr

Status in linux package in Ubuntu:
  Won't Fix
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  Compiler warns unused variable after commit 0c1d6921b07c ("UBUNTU:
  SAUCE: drm/i915/display/psr: Reinstate fix for TGL + AUO panel flicker")

  [Fix]
  The variable is unused, remove it.

  [Test]
  Compiler no longer warns about it.

  [Where problems could occur]
  Nothing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986798/+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 1982968] Re: Jammy update: v5.15.47 upstream stable release

** Tags removed: verification-needed-jammy

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

Title:
  Jammy update: v5.15.47 upstream stable release

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

Bug description:
  SRU Justification

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

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

  pcmcia: db1xxx_ss: restrict to MIPS_DB1XXX boards
  staging: greybus: codecs: fix type confusion of list iterator variable
  iio: adc: ad7124: Remove shift from scan_type
  lkdtm/bugs: Check for the NULL pointer after calling kmalloc
  lkdtm/bugs: Don't expect thread termination without CONFIG_UBSAN_TRAP
  tty: goldfish: Use tty_port_destroy() to destroy port
  tty: serial: owl: Fix missing clk_disable_unprepare() in owl_uart_probe
  tty: n_tty: Restore EOF push handling behavior
  serial: 8250_aspeed_vuart: Fix potential NULL dereference in 
aspeed_vuart_probe
  tty: serial: fsl_lpuart: fix potential bug when using both of_alias_get_id 
and ida_simple_get
  remoteproc: imx_rproc: Ignore create mem entry for resource table
  usb: usbip: fix a refcount leak in stub_probe()
  usb: usbip: add missing device lock on tweak configuration cmd
  USB: storage: karma: fix rio_karma_init return
  usb: musb: Fix missing of_node_put() in omap2430_probe
  staging: fieldbus: Fix the error handling path in anybuss_host_common_probe()
  pwm: lp3943: Fix duty calculation in case period was clamped
  pwm: raspberrypi-poe: Fix endianness in firmware struct
  rpmsg: qcom_smd: Fix irq_of_parse_and_map() return value
  usb: dwc3: gadget: Replace list_for_each_entry_safe() if using giveback
  usb: dwc3: pci: Fix pm_runtime_get_sync() error checking
  misc: fastrpc: fix an incorrect NULL check on list iterator
  firmware: stratix10-svc: fix a missing check on list iterator
  usb: typec: mux: Check dev_set_name() return value
  rpmsg: virtio: Fix possible double free in rpmsg_probe()
  rpmsg: virtio: Fix possible double free in rpmsg_virtio_add_ctrl_dev()
  rpmsg: virtio: Fix the unregistration of the device rpmsg_ctrl
  iio: adc: stmpe-adc: Fix wait_for_completion_timeout return value check
  iio: proximity: vl53l0x: Fix return value check of wait_for_completion_timeout
  iio: adc: sc27xx: fix read big scale voltage not right
  iio: adc: sc27xx: Fine tune the scale calibration values
  rpmsg: qcom_smd: Fix returning 0 if irq_of_parse_and_map() fails
  pvpanic: Fix typos in the comments
  misc/pvpanic: Convert regular spinlock into trylock on panic path
  phy: qcom-qmp: fix pipe-clock imbalance on power-on failure
  power: supply: axp288_fuel_gauge: Drop BIOS version check from "T3 MRD" DMI 
quirk
  serial: sifive: Report actual baud base rather than fixed 115200
  export: fix string handling of namespace in EXPORT_SYMBOL_NS
  soundwire: intel: prevent pm_runtime resume prior to system suspend
  coresight: cpu-debug: Replace mutex with mutex_trylock on panic notifier
  ksmbd: fix reference count leak in smb_check_perm_dacl()
  extcon: ptn5150: Add queue work sync before driver release
  soc: rockchip: Fix refcount leak in rockchip_grf_init
  clocksource/drivers/riscv: Events are stopped during CPU suspend
  ARM: dts: aspeed: ast2600-evb: Enable RX delay for MAC0/MAC1
  rtc: mt6397: check return value after calling platform_get_resource()
  rtc: ftrtc010: Use platform_get_irq() to get the interrupt
  rtc: ftrtc010: Fix error handling in ftrtc010_rtc_probe
  staging: r8188eu: add check for kzalloc
  tty: n_gsm: Don't ignore write return value in gsmld_output()
  tty: n_gsm: Fix packet data hex dump output
  serial: meson: acquire port->lock in startup()
  serial: 8250_fintek: Check SER_RS485_RTS_* only with RS485
  serial: cpm_uart: Fix build error without CONFIG_SERIAL_CPM_CONSOLE
  serial: digicolor-usart: Don't allow CS5-6
  serial: rda-uart: Don't allow CS5-6
  serial: txx9: Don't allow CS5-6
  serial: sh-sci: Don't allow CS5-6
  serial: sifive: Sanitize CSIZE and c_iflag
  serial: st-asc: Sanitize CSIZE and correct PARENB for CS7
  serial: stm32-usart: Correct CSIZE, bits, and parity
  firmware: dmi-sysfs: Fix memory leak in dmi_sysfs_register_handle
  bus: ti-sysc: Fix warnings for unbind for serial
  driver: base: fix UAF when driver_attach failed
  driver core: fix deadlock in __device_attach
  watchdog: rti-wdt: Fix pm_runtime_get_sync() error checking
  watchdog: ts4800_wdt: Fix refcount leak in ts4800_wdt_probe

[Kernel-packages] [Bug 1981883] Re: amdgpu module crash after 5.15 kernel update

This bug is awaiting verification that the linux-
bluefield/5.15.0-1010.12 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' to 'verification-
done-jammy'. If the problem still exists, change the tag 'verification-
needed-jammy' to 'verification-failed-jammy'.

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 removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-bluefield verification-needed-jammy

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

Title:
  amdgpu module crash after 5.15 kernel update

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

Bug description:
  [SRU Justification]

  Impact: The 5.15 kernel series introduced a regression compared to
  5.13 related to virtual display code on AMD GPUs. This causes crashes
  for cloud/VM users back to Focal (using rolling cloud or HWE kernels).

  Fix: Upstream stable 5.15.61 contains a fix for this which is only
  needed there since later kernel version have that code rewritten
  again. This change would get picked up normally in the next stable
  cycle after 2022.09.19. But given the impact we would apply the
  following patch from 5.15.61 ahead of time:

commit 27f8f5219fe4658537ba28fd01657e1062ac3960 linux-5.15.y
"drm/amdgpu: fix check in fbdev init"

  Test case: Booting the affected kernel on a VM which passes through
  AMD GPU hardware.

  Regression potential: Worst case some driver functions will not get
  disabled where they did before.

  --- original description ---

  The kernel 5.15 amdgpu module crashes on load with a “BUG: kernel NULL
  pointer dereference” on Amazon EC2 G4ad hardware (custom AMD Radeon
  V520 Pro datacenter GPU) on focal (HWE) and jammy with kernel
  5.15.0-1011 and possibly earlier, up through latest (revision
  1015.19). This crash bug did not exist in any of the focal HWE 5.13
  kernels.

  This is probably an upstream kernel bug, but I am also filing it here
  because existing focal users on EC2 will suddenly stop having access
  to their AMD GPUs after a reboot once the new 5.15 HWE kernel is
  installed.

  The full backtrace from dmesg is below. The offending function call
  which crashes in the 5.15 kernel corresponds to this source (sorry,
  not the right source tree, but the same driver)
  
https://github.com/torvalds/linux/blob/8bb7eca972ad531c9b149c0a51ab43a417385813/drivers/gpu/drm/amd/amdgpu/amdgpu_fb.c#L345

  A workaround that I have discovered is adding “options amdgpu
  virtual_display=;” to a new modprobe.d configuration file - something
  which shouldn’t be required, but is at least harmless.

  Here is the relevant BUG message and backtrace from dmesg:

  [  318.111721] BUG: kernel NULL pointer dereference, address: 
  [  318.115443] #PF: supervisor instruction fetch in kernel mode
  [  318.118443] #PF: error_code(0x0010) - not-present page
  [  318.121177] PGD 0 P4D 0
  [  318.122688] Oops: 0010 [#1] SMP NOPTI
  [  318.124592] CPU: 6 PID: 13667 Comm: modprobe Tainted: GW 
5.15.0-1015-aws #19~20.04.1-Ubuntu
  [  318.129711] Hardware name: Amazon EC2 g4ad.2xlarge/, BIOS 1.0 10/16/2017
  [  318.133167] RIP: 0010:0x0
  [  318.134704] Code: Unable to access opcode bytes at RIP 0xffd6.
  [  318.138291] RSP: 0018:9841828d78e0 EFLAGS: 00010246
  [  318.140938] RAX:  RBX: 8a4f16ae8000 RCX: 
0001
  [  318.144604] RDX:  RSI: 0003 RDI: 
8a4f16ae8000
  [  318.148319] RBP: 9841828d7908 R08: 8a4f02460278 R09: 
8a4f06422c40
  [  318.152151] R10: c01c42494f8a R11: 8a4f01dcb5b8 R12: 
8a4f024602e8
  [  318.155929] R13: c107e4a0 R14:  R15: 
8a4f02460010
  [  318.159685] FS:  7f8afdc1c740() GS:8a55f098() 
knlGS:
  [  318.163897] CS:  0010 DS:  ES:  CR0: 80050033
  [  318.167038] CR2: ffd6 CR3: 00011817e000 CR4: 
003506e0
  [  318.170758] Call Trace:
  [  318.173964]  
  [  318.176822]  __drm_helper_disable_unused_functions+0xe7/0x100 
[drm_kms_helper]
  [  318.184230]  drm_helper_disable_unused_functions+0x44/0x50 [drm_kms_helper]
  [  318.189761]  amdgpu_fbdev_init+0x104/0x110 [amdgpu]
  [  318.194264]  amdgpu_device_init.cold+0x7cc/0xc48 [amdgpu]
  [  318.199061]  ? pci_read_config_byte+0x27/0x40
  [  318.203206]  amdgpu_driver_load_kms+0x1e/0x270 [amdgpu]
  [  318.207901]  amdgpu_pci_probe+0x1ea/0x290 [amdgpu]
  [  318.212445]  local_pci_probe+0x4b/0x90
  [

[Kernel-packages] [Bug 1987451] Re: Jammy update: v5.15.54 upstream stable release

** Tags removed: verification-needed-jammy

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

Title:
  Jammy update: v5.15.54 upstream stable release

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

Bug description:
  SRU Justification

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

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

  mm/slub: add missing TID updates on slab deactivation
  mm/filemap: fix UAF in find_lock_entries
  Revert "selftests/bpf: Add test for bpf_timer overwriting crash"
  ALSA: usb-audio: Workarounds for Behringer UMC 204/404 HD
  ALSA: hda/realtek: Add quirk for Clevo L140PU
  ALSA: cs46xx: Fix missing snd_card_free() call at probe error
  can: bcm: use call_rcu() instead of costly synchronize_rcu()
  can: grcan: grcan_probe(): remove extra of_node_get()
  can: gs_usb: gs_usb_open/close(): fix memory leak
  can: m_can: m_can_chip_config(): actually enable internal timestamping
  can: m_can: m_can_{read_fifo,echo_tx_event}(): shift timestamp to full 32 bits
  can: mcp251xfd: mcp251xfd_regmap_crc_read(): improve workaround handling for 
mcp2517fd
  can: mcp251xfd: mcp251xfd_regmap_crc_read(): update workaround broken CRC on 
TBC register
  bpf: Fix incorrect verifier simulation around jmp32's jeq/jne
  bpf: Fix insufficient bounds propagation from adjust_scalar_min_max_vals
  usbnet: fix memory leak in error case
  net: rose: fix UAF bug caused by rose_t0timer_expiry
  netfilter: nft_set_pipapo: release elements in clone from abort path
  btrfs: rename btrfs_alloc_chunk to btrfs_create_chunk
  btrfs: add additional parameters to btrfs_init_tree_ref/btrfs_init_data_ref
  btrfs: fix invalid delayed ref after subvolume creation failure
  btrfs: fix warning when freeing leaf after subvolume creation failure
  Input: cpcap-pwrbutton - handle errors from platform_get_irq()
  Input: goodix - change goodix_i2c_write() len parameter type to int
  Input: goodix - add a goodix.h header file
  Input: goodix - refactor reset handling
  Input: goodix - try not to touch the reset-pin on x86/ACPI devices
  dma-buf/poll: Get a file reference for outstanding fence callbacks
  btrfs: fix deadlock between chunk allocation and chunk btree modifications
  drm/i915: Disable bonding on gen12+ platforms
  drm/i915/gt: Register the migrate contexts with their engines
  drm/i915: Replace the unconditional clflush with drm_clflush_virt_range()
  media: ir_toy: prevent device from hanging during transmit
  memory: renesas-rpc-if: Avoid unaligned bus access for HyperFlash
  ath11k: add hw_param for wakeup_mhi
  qed: Improve the stack space of filter_config()
  platform/x86: wmi: introduce helper to convert driver to WMI driver
  platform/x86: wmi: Replace read_takes_no_args with a flags field
  platform/x86: wmi: Fix driver->notify() vs ->probe() race
  mt76: mt7921: get rid of mt7921_mac_set_beacon_filter
  mt76: mt7921: introduce mt7921_mcu_set_beacon_filter utility routine
  mt76: mt7921: fix a possible race enabling/disabling runtime-pm
  bpf: Stop caching subprog index in the bpf_pseudo_func insn
  bpf, arm64: Use emit_addr_mov_i64() for BPF_PSEUDO_FUNC
  riscv: defconfig: enable DRM_NOUVEAU
  RISC-V: defconfigs: Set CONFIG_FB=y, for FB console
  net/mlx5e: Check action fwd/drop flag exists also for nic flows
  net/mlx5e: Split actions_match_supported() into a sub function
  net/mlx5e: TC, Reject rules with drop and modify hdr action
  net/mlx5e: TC, Reject rules with forward and drop actions
  ASoC: rt5682: Avoid the unexpected IRQ event during going to suspend
  ASoC: rt5682: Re-detect the combo jack after resuming
  ASoC: rt5682: Fix deadlock on resume
  netfilter: nf_tables: convert pktinfo->tprot_set to flags field
  netfilter: nft_payload: support for inner header matching / mangling
  netfilter: nft_payload: don't allow th access for fragments
  s390/boot: allocate amode31 section in decompressor
  s390/setup: use physical pointers for memblock_reserve()
  s390/setup: preserve memory at OLDMEM_BASE and OLDMEM_SIZE
  ibmvnic: init init_done_rc earlier
  ibmvnic: clear fop when retrying probe
  ibmvnic: Allow queueing resets during probe
  virtio-blk: avoid preallocating big SGL for data
  io_uring: ensure that fsnotify is always called
  block: use bdev_get_queue() in bio.c
  block: only mark bio as tracked if it really is tracked
  block: fix rq-qos breakage from skipping rq_qos_done_bio()
  stddef: Introduce

[Kernel-packages] [Bug 1987998] Re: LSM: Configuring Too Many LSMs Causes Kernel Panic on Boot

This bug is awaiting verification that the linux-
bluefield/5.15.0-1010.12 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' to 'verification-
done-jammy'. If the problem still exists, change the tag 'verification-
needed-jammy' to 'verification-failed-jammy'.

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 removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-bluefield verification-needed-jammy

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

Title:
  LSM: Configuring Too Many LSMs Causes Kernel Panic on Boot

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

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

  [Impact]

  The Ubuntu kernel carries an out of tree patchet, known as "LSM:
  Module stacking for AppArmor" upstream, to enable stackable LSMs for
  containers. The revision the Ubuntu kernel carries is an older one,
  from 2020, and has some slight divergences from the latest revision in
  development.

  One such divergence, is support for Landlock as a stackable LSM. When
  the stackable LSM patchset was applied, Landlock was still in
  development and not mainlined yet, and wasn't present in the earlier
  revision of the "LSM: Module stacking for AppArmor" patchset. Support
  for this was added by us.

  There was a minor omission made during enabling support for Landlock.
  The LSM slot type was marked as LSMBLOB_NEEDED, when it should have
  been LSMBLOB_NOT_NEEDED.

  Landlock itself does not provide any of the hooks that use a struct
  lsmblob, such as secid_to_secctx, secctx_to_secid, inode_getsecid,
  cred_getsecid, kernel_act_as task_getsecid_subj task_getsecid_obj and
  ipc_getsecid.

  When we set .slot = LSMBLOB_NEEDED, this indicates that we need an
  entry in struct lsmblob, and we need to increment LSMBLOB_ENTRIES by
  one to fit the entry into the secid array:

  #define LSMBLOB_ENTRIES ( \
     (IS_ENABLED(CONFIG_SECURITY_SELINUX) ? 1 : 0) + \
     (IS_ENABLED(CONFIG_SECURITY_SMACK) ? 1 : 0) + \
     (IS_ENABLED(CONFIG_SECURITY_APPARMOR) ? 1 : 0) + \
     (IS_ENABLED(CONFIG_BPF_LSM) ? 1 : 0))

  struct lsmblob {
     u32 secid[LSMBLOB_ENTRIES];
  };

  Currently, we don't increment LSMBLOB_ENTRIES by one to make an entry
  for Landlock, so for the Ubuntu kernel, we can fit a maximum of two
  entries, one for Apparmor and one for bpf.

  If you try and configure three LSMs like so and reboot:

  GRUB_CMDLINE_LINUX_DEFAULT="lsm=landlock,bpf,apparmor"

  You will receive the following panic:

  LSM: Security Framework initializing
  landlock: Up and running.
  LSM support for eBPF active
  Kernel panic - not syncing: security_add_hooks Too many LSMs registered.
  CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.0-46-generic #49-Ubuntu
  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014
  Call Trace:
   
   show_stack+0x52/0x5c
   dump_stack_lvl+0x4a/0x63
   dump_stack+0x10/0x16
   panic+0x149/0x321
   security_add_hooks+0x45/0x13a
   apparmor_init+0x189/0x1ef
   initialize_lsm+0x54/0x74
   ordered_lsm_init+0x379/0x392
   security_init+0x40/0x49
   start_kernel+0x466/0x4dc
   x86_64_start_reservations+0x24/0x2a
   x86_64_start_kernel+0xe4/0xef
   secondary_startup_64_no_verify+0xc2/0xcb
   
  ---[ end Kernel panic - not syncing: security_add_hooks Too many LSMs 
registered. ]---

  There is a check added in security_add_hooks() that makes sure that
  you cannot configure too many LSMs:

  if (lsmid->slot == LSMBLOB_NEEDED) {
   if (lsm_slot >= LSMBLOB_ENTRIES)
    panic("%s Too many LSMs registered.\n", __func__);
   lsmid->slot = lsm_slot++;
   init_debug("%s assigned lsmblob slot %d\n", lsmid->lsm,
   lsmid->slot);
  }

  A workaround is to enable no more than 2 LSMs until this is fixed.

  [Fix]

  If you read the following mailing list thread on linux-security-
  modules from May 2021:

  https://lore.kernel.org/selinux/202105141224.942DE93@keescook/T/

  It is explained that Landlock does not provide any of the hooks that
  use a struct lsmblob, such as secid_to_secctx, secctx_to_secid,
  inode_getsecid, cred_getsecid, kernel_act_as task_getsecid_subj
  task_getsecid_obj and ipc_getsecid.

  I verified this with:

  ubuntu-jammy$ grep -Rin "secid_to_secctx" security/landlock/
  ubuntu-jammy$ grep -Rin "secctx_to_secid" security/landlock/
  ubuntu-jammy$ grep -Rin "inode_getsecid" security/landlock/
  ubuntu-jammy$ grep -Rin

[Kernel-packages] [Bug 1983149] Re: Jammy update: v5.15.49 upstream stable release

** Tags removed: verification-needed-jammy

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

Title:
  Jammy update: v5.15.49 upstream stable release

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

Bug description:
  SRU Justification

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

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

  Revert "drm/amd/display: Fix DCN3 B0 DP Alt Mapping"
  nfsd: Replace use of rwsem with errseq_t
  arm64: dts: imx8mm-beacon: Enable RTS-CTS on UART3
  arm64: dts: imx8mn-beacon: Enable RTS-CTS on UART3
  powerpc/kasan: Silence KASAN warnings in __get_wchan()
  ASoC: nau8822: Add operation for internal PLL off and on
  drm/amd/display: Read Golden Settings Table from VBIOS
  drm/amdkfd: Use mmget_not_zero in MMU notifier
  dma-debug: make things less spammy under memory pressure
  ASoC: cs42l52: Fix TLV scales for mixer controls
  ASoC: cs35l36: Update digital volume TLV
  ASoC: cs53l30: Correct number of volume levels on SX controls
  ASoC: cs42l52: Correct TLV for Bypass Volume
  ASoC: cs42l56: Correct typo in minimum level for SX volume controls
  ASoC: cs42l51: Correct minimum value for SX volume control
  drm/amdkfd: add pinned BOs to kfd_bo_list
  ata: libata-core: fix NULL pointer deref in ata_host_alloc_pinfo()
  quota: Prevent memory allocation recursion while holding dq_lock
  ASoC: wm8962: Fix suspend while playing music
  ASoC: es8328: Fix event generation for deemphasis control
  ASoC: wm_adsp: Fix event generation for wm_adsp_fw_put()
  Input: soc_button_array - also add Lenovo Yoga Tablet2 1051F to 
dmi_use_low_level_irq
  scsi: vmw_pvscsi: Expand vcpuHint to 16 bits
  scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO is aborted
  scsi: lpfc: Fix port stuck in bypassed state after LIP in PT2PT topology
  scsi: lpfc: Allow reduced polling rate for nvme_admin_async_event cmd 
completion
  scsi: mpt3sas: Fix out-of-bounds compiler warning
  scsi: ipr: Fix missing/incorrect resource cleanup in error case
  scsi: pmcraid: Fix missing resource cleanup in error case
  ALSA: hda/realtek - Add HW8326 support
  virtio-mmio: fix missing put_device() when vm_cmdline_parent registration 
failed
  nfc: nfcmrvl: Fix memory leak in nfcmrvl_play_deferred
  ipv6: Fix signed integer overflow in l2tp_ip6_sendmsg
  net: ethernet: mtk_eth_soc: fix misuse of mem alloc interface 
netdev[napi]_alloc_frag
  gcc-12: disable '-Wdangling-pointer' warning for now
  mellanox: mlx5: avoid uninitialized variable warning with gcc-12
  MIPS: Loongson-3: fix compile mips cpu_hwmon as module build error.
  random: credit cpu and bootloader seeds by default
  gpio: dwapb: Don't print error on -EPROBE_DEFER
  platform/x86: gigabyte-wmi: Add Z690M AORUS ELITE AX DDR4 support
  platform/x86: gigabyte-wmi: Add support for B450M DS3H-CF
  platform/x86/intel: hid: Add Surface Go to VGBS allow list
  staging: r8188eu: fix rtw_alloc_hwxmits error detection for now
  staging: r8188eu: Use zeroing allocator in wpa_set_encryption()
  staging: r8188eu: Fix warning of array overflow in ioctl_linux.c
  pNFS: Don't keep retrying if the server replied NFS4ERR_LAYOUTUNAVAILABLE
  pNFS: Avoid a live lock condition in pnfs_update_layout()
  sunrpc: set cl_max_connect when cloning an rpc_clnt
  clocksource: hyper-v: unexport __init-annotated hv_init_clocksource()
  i40e: Fix adding ADQ filter to TC0
  i40e: Fix calculating the number of queue pairs
  i40e: Fix call trace in setup_tx_descriptors
  Drivers: hv: vmbus: Release cpu lock in error case
  tty: goldfish: Fix free_irq() on remove
  misc: atmel-ssc: Fix IRQ check in ssc_probe
  io_uring: fix races with file table unregister
  io_uring: fix races with buffer table unregister
  drm/i915/reset: Fix error_state_read ptr + offset use
  net: hns3: split function hclge_update_port_base_vlan_cfg()
  net: hns3: set port base vlan tbl_sta to false before removing old vlan
  net: hns3: don't push link state to VF if unalive
  net: hns3: fix tm port shapping of fibre port is incorrect after driver 
initialization
  nvme: add device name to warning in uuid_show()
  mlxsw: spectrum_cnt: Reorder counter pools
  net: bgmac: Fix an erroneous kfree() in bgmac_remove()
  net: ax25: Fix deadlock caused by skb_recv_datagram in ax25_recvmsg
  arm64: ftrace: fix branch range checks
  arm64: ftrace: consistently handle PLTs.
  certs/blacklist_hashes.c: fix const confusion in certs blacklist

[Kernel-packages] [Bug 1989578] Re: Add HDMI codec ID for Intel Raptor Lake

This bug is awaiting verification that the linux-
bluefield/5.15.0-1010.12 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' to 'verification-
done-jammy'. If the problem still exists, change the tag 'verification-
needed-jammy' to 'verification-failed-jammy'.

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-bluefield verification-needed-jammy

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

Title:
  Add HDMI codec ID for Intel Raptor Lake

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]
  The HDAudio is not functional on some RaptorLake machines. The audio codec is 
failed to be probed so no PCM stream available for audio functions.

  [Fix]
  Backport the patch from upstream which adds the support for the HDMI codec ID 
on RaptorLake.

  [Test]
  Power on the machine and check if the audio function's working with alsa 
utilities.

  [Where problems could occur]
  The change only applies to the new RaptorLake Intel HDA controller and HDMI 
codec.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1989578/+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 1989221] Re: Jammy update: v5.15.60 upstream stable release

** Tags removed: verification-needed-jammy

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

Title:
  Jammy update: v5.15.60 upstream stable release

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

Bug description:
  SRU Justification

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

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

  x86/speculation: Make all RETbleed mitigations 64-bit only
  selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads
  selftests/bpf: Check dst_port only on the client socket
  block: fix default IO priority handling again
  tools/vm/slabinfo: Handle files in debugfs
  ACPI: video: Force backlight native for some TongFang devices
  ACPI: video: Shortening quirk list by identifying Clevo by board_name only
  ACPI: APEI: Better fix to avoid spamming the console with old error logs
  crypto: arm64/poly1305 - fix a read out-of-bound
  KVM: x86: do not report a vCPU as preempted outside instruction boundaries
  KVM: x86: do not set st->preempted when going back to user space
  KVM: selftests: Make hyperv_clock selftest more stable
  tools/kvm_stat: fix display of error when multiple processes are found
  selftests: KVM: Handle compiler optimizations in ucall
  KVM: x86/svm: add __GFP_ACCOUNT to __sev_dbg_{en,de}crypt_user()
  arm64: set UXN on swapper page tables
  btrfs: zoned: prevent allocation from previous data relocation BG
  btrfs: zoned: fix critical section of relocation inode writeback
  Bluetooth: hci_bcm: Add BCM4349B1 variant
  Bluetooth: hci_bcm: Add DT compatible for CYW55572
  dt-bindings: bluetooth: broadcom: Add BCM4349B1 DT binding
  Bluetooth: btusb: Add support of IMC Networks PID 0x3568
  Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04CA:0x4007
  Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04C5:0x1675
  Bluetooth: btusb: Add Realtek RTL8852C support ID 0x0CB8:0xC558
  Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3587
  Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3586
  macintosh/adb: fix oob read in do_adb_query() function
  x86/speculation: Add RSB VM Exit protections
  x86/speculation: Add LFENCE to RSB fill sequence
  Linux 5.15.60
  UBUNTU: Upstream stable to v5.15.60

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989221/+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 1991112] Re: mlxbf_gige: compute MDIO period based on i1clk

This bug is awaiting verification that the linux-
bluefield/5.15.0-1010.12 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' to 'verification-
done-jammy'. If the problem still exists, change the tag 'verification-
needed-jammy' to 'verification-failed-jammy'.

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-bluefield verification-needed-jammy

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

Title:
  mlxbf_gige: compute MDIO period based on i1clk

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

Bug description:
  The following upstream patch should be cherry picked to jammy kernel:

  3a1a274e933f mlxbf_gige: compute MDIO period based on i1clk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1991112/+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 1989495] Re: mlxbf_gige: need to clear MDIO gateway lock after read

This bug is awaiting verification that the linux-
bluefield/5.15.0-1010.12 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' to 'verification-
done-jammy'. If the problem still exists, change the tag 'verification-
needed-jammy' to 'verification-failed-jammy'.

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-bluefield verification-needed-jammy

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

Title:
  mlxbf_gige: need to clear MDIO gateway lock after read

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

Bug description:
  SRU Justification:

  [Impact]
  The BlueField-2 GIGE logic accesses the MDIO device via reads/writes
  to a gateway (GW) register. The MDIO GW lock is set after read. Make
  sure to always clear to indicate that the GW register is not being used.
  If the lock is mistakenly interpreted as ACTIVE, then subsequent MDIO
  accesses will be blocked and PHY device will be inaccessible.

  [Fix]
  For each MDIO read and write transaction, the last step should
  be to clear the MDIO GW lock.

  [Test Case]
  Boot the BlueField-2 platform
  Bring up the "oob_net0" interface via DHCP or static IP
  Ping and file transfer over "oob_net0" should work properly
  Bounce the "oob_net0" interface a few times and repeat tests

  [Regression Potential]
  * Low risk for causing a regression, tested well in our lab.

  [Other]
  * None

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1989495/+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 1990240] Re: To support Intel Maple Ridge Thunderbolt [8086:1134]

This bug is awaiting verification that the linux-
bluefield/5.15.0-1010.12 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' to 'verification-
done-jammy'. If the problem still exists, change the tag 'verification-
needed-jammy' to 'verification-failed-jammy'.

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-bluefield verification-needed-jammy

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

Title:
  To support Intel Maple Ridge Thunderbolt [8086:1134]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  The TBT ID[8086:1134] the new project uses is not listed in the driver.

  [Fix]
  Intel submits this as we requested which is still in linux-next
  https://lore.kernel.org/linux-usb/20220908104320.3409720-1-gil.f...@intel.com/

  [Where problems could occur]
  Adding only one ID, should be pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1990240/+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 1991151] Re: mlxbf_gige: need to revert SAUCE patch for "clear MDIO gateway lock"

This bug is awaiting verification that the linux-
bluefield/5.15.0-1010.12 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' to 'verification-
done-jammy'. If the problem still exists, change the tag 'verification-
needed-jammy' to 'verification-failed-jammy'.

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-bluefield verification-needed-jammy

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

Title:
  mlxbf_gige: need to revert SAUCE patch for "clear MDIO gateway lock"

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

Bug description:
  SRU Justification:

  [Impact]

  The Jammy repo contains the following SAUCE patch:
  UBUNTU: SAUCE: mlxbf_gige: clear MDIO gateway lock after read

  This patch is now in mainline Linux kernel, so the SAUCE patch
  can be reverted and replaced with the upstream commit SHA.

  [Fix]

  The fix requires two parts, the first of which is addressed by
  this bug. A second bug will be created to add the upstream
  commit to the repo. The fix to this bug is a revert of the SAUCE patch
  8d2dbbd437a1 UBUNTU: SAUCE: mlxbf_gige: clear MDIO gateway lock after read

  [Test Case]

  Boot platform and bring up "oob_net0" interface properly
  Test that network traffic works properly

  [Regression Potential]

  Low, as this logic is well tested.

  [Other]

  Will add a note to this bug with the second bug's number,
  after the second bug is created. The second bug is for
  adding the upstream commit to the Jammy repo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1991151/+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 1983656] Re: iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500

This bug is awaiting verification that the linux-
bluefield/5.15.0-1010.12 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' to 'verification-
done-jammy'. If the problem still exists, change the tag 'verification-
needed-jammy' to 'verification-failed-jammy'.

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 removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-bluefield verification-needed-jammy

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

Title:
  iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed

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

  [Impact]

  Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b]
  get no traffic flow and produce error messages in both the host and
  guest during network configuration.

  Environment: Ubuntu OpenStack Focal-Ussuri with OVN
  Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE
  Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy

  Host Error Messages:
  ice :98:00.1: VF 7 failed opcode 6, retval: -5

  Guest Error Messages:
  iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6

  In the context of these errors "6" refers to the value of
  VIRTCHNL_OP_CONFIG_VSI_QUEUES

  It was found in these cases that the VM is able to successfully
  transmit packets but never receives any and the RX packet drop
  counters for the VF in "ip link" on the host increase equal to the RX
  packet count.

  There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d
  claiming to resolve this error in some cases. It is already included
  in 5.15.0-41-generic and did not resolve the issue.

  The following conditions are required to trigger the bug:
  - A port VLAN must be assigned by the host
  - The MTU must be set >1500 by the guest

  There is no workaround, Intel E810 SR-IOV VFs with MTU >1500 cannot be
  used without these patches.

  [Fix]

  iavf currently sets the maximum packet size to IAVF_MAX_RXBUFFER, but
  on the previous ice driver, it was decremented by VLAN_HLEN to make
  some space to fit the VLAN header. This doesn't happen on iavf, and we
  end up trying to use a packet size larger than IAVF_MAX_RXBUFFER,
  causing the IAVF_ERR_PARAM error.

  The fix is to change the maximum packet size from IAVF_MAX_RXBUFFER to
  max_mtu received from the PF via GET_VF_RESOURCES msg.

  Also pick up a necessary commit for i40e to announce the correct
  maximum packet size by GET_VF_RESOURCES msg.

  This has been fixed by the following commits:

  commit 399c98c4dc50b7eb7e9f24da7ffdda6f025676ef
  Author: Michal Jaron 
  Date:   Tue Sep 13 15:38:35 2022 +0200
  Subject: iavf: Fix set max MTU size with port VLAN and jumbo frames
  Link: 
https://github.com/torvalds/linux/commit/399c98c4dc50b7eb7e9f24da7ffdda6f025676ef

  commit 372539def2824c43b6afe2403045b140f65c5acc
  Author: Michal Jaron 
  Date:   Tue Sep 13 15:38:36 2022 +0200
  Subject: i40e: Fix VF set max MTU size
  Link: 
https://github.com/torvalds/linux/commit/372539def2824c43b6afe2403045b140f65c5acc

  A test kernel is available in the following ppa:

  https://launchpad.net/~arif-ali/+archive/ubuntu/sf00343742

  If you install the test kernel to a compute host and VM, when you
  attach a VF and set the MTU to 9000, it succeeds, and traffic can
  flow.

  [Test Plan]

  Create a Focal VM and assign an Intel E810 (ice) SR-IOV VF with a port
  vlan:

  Openstack works, as does creating a VM directly with uvtool/libvirt.

  $ uvt-kvm create focal-test release=focal

  Using the document to understand SRIOV basics in the link below

  
https://www.intel.com/content/www/us/en/developer/articles/technical/configure-
  sr-iov-network-virtual-functions-in-linux-kvm.html

  The following command show all the bus info for all the network
  devices

  $ lshw -c network -businfo

  Choose one, as shown below

  pci@:17:01.4  ens2f0v4 networkEthernet Adaptive
  Virtual Function

  We can then add the following into the XML definition via “virsh edit
  focal-test”

  
    
  
    
   
  
    
  

  Then we stop and start the VM via "virsh shutdown focal-test" and then
  "virsh start focal-test". We can then login to the VM using the
  command below

  $ uvt-kvm ssh focal-test

  Once you have logged in, run the

[Kernel-packages] [Bug 1988809] Re: ip/nexthop: fix default address selection for connected nexthop

This bug is awaiting verification that the linux-
bluefield/5.15.0-1010.12 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' to 'verification-
done-jammy'. If the problem still exists, change the tag 'verification-
needed-jammy' to 'verification-failed-jammy'.

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 removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-bluefield verification-needed-jammy

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

Title:
  ip/nexthop: fix default address selection for connected nexthop

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

Bug description:
  [Impact]

  Packets sent by userland apps are rejected/dropped if the source
  address is not specified and the corresponding route is using a
  connected nexthop object.

  This bug exists since linux v5.3 and has been fixed in v5.19 by the following 
upstream commits:
   - 747c14307214 ("ip: fix dflt addr selection for connected nexthop")
 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=747c14307214
   - cd72e61bad14 ("selftests/net: test nexthop without gw")
 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cd72e61bad14
   - eb55dc09b5dd ("ip: fix triggering of 'icmp redirect'")
 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb55dc09b5dd

  The last commit (v6.0) fixes a regression introduced by the first
  commit.

  [Test Case]

  A detailed test case is explained in the first commit and a self-test
  is added in the second commit.

  [Regression Potential]

  The patch modifies some internal routing states. It has been living in the 
upstream trees for 2 months and the reported regression about icmp redirects 
has been fixed.
  The risk of regression should be contained.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988809/+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 1990554] Re: Jammy update: v5.15.62 upstream stable release

** Tags removed: verification-needed-jammy

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

Title:
  Jammy update: v5.15.62 upstream stable release

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

Bug description:
  SRU Justification

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

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

  io_uring: use original request task for inflight tracking
  tee: add overflow check in register_shm_helper()
  net_sched: cls_route: disallow handle of 0
  ksmbd: prevent out of bound read for SMB2_WRITE
  ksmbd: fix heap-based overflow in set_ntacl_dacl()
  btrfs: only write the sectors in the vertical stripe which has data stripes
  btrfs: raid56: don't trust any cached sector in __raid56_parity_recover()
  Linux 5.15.62
  UBUNTU: Upstream stable to v5.15.62

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990554/+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 1991551] Re: i2c-mlxbf.c: Sync up driver with upstreaming

This bug is awaiting verification that the linux-
bluefield/5.15.0-1010.12 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' to 'verification-
done-jammy'. If the problem still exists, change the tag 'verification-
needed-jammy' to 'verification-failed-jammy'.

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-bluefield verification-needed-jammy

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

Title:
  i2c-mlxbf.c: Sync up driver with upstreaming

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

Bug description:
  SRU Justification:

  [Impact]

  Several i2c-mlxbf.c patches have been upstreamed recently and are in
  linux-next at the moment. So revert all changes in both Focal (5.4)
  and Jammy (5.15) and cherry-pick all changes from linux-next master.

  IMPORTANT NOTE: The new linux i2c support for BF3 also REQUIRES
  upgrading the UEFI firmware version. For BF1 and BF2 however, this
  driver should be backward compatible with older UEFI versions.

  [Fix]

  * There is a total of 17 commits: 8 reverts, 8 cherry-picks from
  linux-next and one internal "UBUNTU: SAUCE:" to ad the driver version.
  Following is the list of commits cherry-picked.

  * i2c: mlxbf: incorrect base address passed during io write
  From 


  * i2c: mlxbf: prevent stack overflow in mlxbf_i2c_smbus_start_transaction()
  From 


  * i2c: mlxbf: remove IRQF_ONESHOT
  From 


  * i2c: mlxbf: Fix frequency calculation
  From 


  * i2c: mlxbf: support lock mechanism
  From 


  * i2c: mlxbf: add multi slave functionality
  From 


  * i2c: mlxbf: support BlueField-3 SoC
  From 


  * i2c: mlxbf: remove device tree support
  From 


  * Also add the i2c driver version to keep track of the changes
  internally.

  [Test Case]

  * Check that the i2c driver loads without errors on BF1 and BF2 (dmesg, and 
check i2c1 sysfs is created)
  * Check that the i2c module can be removed and reloaded without errors.
  * Check that IPMB services work successfully on systems with BMC. This is the 
best way to test the i2c driver. Run ipmitool command from the BF: ipmitool mc 
info
  * Run ipmitool from the BMC as well: ipmitool -I ipmb mc info
  * This driver should be backward compatible
  * Make sure this driver is backward compatible with older UEFI version (only 
applicable for BF1 and BF2)
  * Make sure this driver works for BF1, BF2 and BF3 with the latest UEFI 
version.

  [Regression Potential]

  * The i2c driver could fail to load because the UEFI firmware hasn't been 
upgraded
  * The i2c driver would fail to load due to a bug
  * IPMB code which utilises the i2c driver fails to work (ipmitool commands)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1991551/+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 1995148] Re: mlxbf_gige: need to add BlueField-3 support

This bug is awaiting verification that the linux-
bluefield/5.15.0-1010.12 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' to 'verification-
done-jammy'. If the problem still exists, change the tag 'verification-
needed-jammy' to 'verification-failed-jammy'.

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-bluefield verification-needed-jammy

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

Title:
  mlxbf_gige: need to add BlueField-3 support

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

Bug description:
  SRU Justification:

  [Impact]

  The GIGE driver ("mlxbf_gige") in the Jammy repo does not yet
  support the BlueField-3 SoC.  The "mlxbf_gige" driver which
  supports BlueField-2 SoC currently will be extended to include
  the BlueField-3 support.

  [Fix]
  The BlueField-3 support will be provided in the form of a set
  of 4 patches, to be sent in as a pull request. 

  [Test Case]
  BlueField-2: Boot platform and bring up "oob_net0" interface properly
   Test that network traffic works properly
  BlueField-3: Tested in simulator platforms and early silicon

  [Regression Potential]
  Since this is initial support there is chance of regression
  on BlueField-2 platforms, but it's been tested there.

  [Other]
  n/a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1995148/+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 1983146] Re: Jammy update: v5.15.48 upstream stable release