[Kernel-packages] [Bug 1965968] Re: post jammy update, black/flickering screen on boot

[Daniel van Vugt]

OK then next please try https://kernel.ubuntu.com/~kernel-
ppa/mainline/v5.14/

If it works then next try: https://kernel.ubuntu.com/~kernel-
ppa/mainline/v5.14.10/

If it fails then try: https://kernel.ubuntu.com/~kernel-
ppa/mainline/v5.13/

We need to find the version where the black screen started.

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

Title:
  post jammy update, black/flickering screen on boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After initial jammy upgrade things were working fine, but after a
  recent update the machine boots to a blank screen.  There are
  occasional purplish flickers that seem to correspond with keypresses,
  but even blindly typing the encrypted disk password doesn't appear to
  advance the boot process to gdm.

  Plugging in an external monitor does fix the issue and allow boot to
  proceed, but obviously doesn't help if not near an external monitor.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: plymouth 0.9.5+git20211018-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Tue Mar 22 09:22:26 2022
  DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
  InstallationDate: Installed on 2019-08-17 (948 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  MachineType: Dell Inc. XPS 15 9575
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic 
root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic 
root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7
  SourcePackage: plymouth
  TextPlymouth: 
/usr/share/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth
  UpgradeStatus: Upgraded to jammy on 2022-03-18 (3 days ago)
  dmi.bios.date: 03/25/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.1
  dmi.board.name: 0N338G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1963555] Re: xhci: Fix command ring abort, write all 64 bits to CRCR register.

[Amedee Van Gasse]

I have expected this to happen not just for USB input devices but for
all USB devices, like your external drives. I just don't have any other
devices at hand to verify.

For reference, here's a related question on AskUbuntu:
https://askubuntu.com/questions/1394480/keyboard-mouse-stop-working-
with-kernel-ubuntu-5-13-0-22-22-387-g0fc979747dec

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

Title:
  xhci: Fix command ring abort, write all 64 bits to CRCR register.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upstream mainline kernel includes patch v5.15-rc5-4-gff0e50d3564f.
  This patch was included in the Ubuntu kernel as 
Ubuntu-5.13.0-22.22-387-g0fc979747dec, available in Ubuntu kernels 5.13.0-23 
and up.

  The patch is incomplete, which causes an issue with some xHC controllers.
  An additional patch was made to the upstream mainline kernel, which fixes the 
issue that was introduced: v5.16-rc3-1-g09f736aa9547. This patch does not yet 
have a corresponding commit in the Ubuntu kernel repository for Ubuntu 21.10; 
and Ubuntu 22.04 will use the 5.15 kernel, which does also not include the 
second patch.

  Discussion of the first patch (already in Ubuntu kernel) can be found
  on the kernel.org mailing list:
  
https://lore.kernel.org/r/20211008092547.3996295-5-mathias.ny...@linux.intel.com

  Discussion of the second patch (not yet in Ubuntu kernel):
  
https://lore.kernel.org/all/20211126122340.1193239-2-mathias.ny...@linux.intel.com/

  Request to include upstream patch v5.16-rc3-1-g09f736aa9547 into the
  kernels for Ubuntu 21.10 (5.13 kernels) and Ubuntu 22.04 LTS (5.15
  kernels).

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-22-generic 5.13.0-22.22
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  amedee 4158 F pulseaudio
   /dev/snd/controlC3:  amedee 4158 F pulseaudio
   /dev/snd/controlC0:  amedee 4158 F pulseaudio
   /dev/snd/controlC1:  amedee 4158 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  3 22:23:43 2022
  HibernationDevice: RESUME=UUID=edec0bf3-448f-4e5c-a21a-ef9624572973
  InstallationDate: Installed on 2022-01-30 (32 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Z370 AORUS Gaming K3
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-22-generic N/A
   linux-backports-modules-5.13.0-22-generic  N/A
   linux-firmware 1.201.4
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/28/2019
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F15a
  dmi.board.asset.tag: Default string
  dmi.board.name: Z370 AORUS Gaming K3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF15a:bd11/28/2019:br5.12:svnGigabyteTechnologyCo.,Ltd.:pnZ370AORUSGamingK3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370AORUSGamingK3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z370 AORUS Gaming K3
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Kernel-packages] [Bug 1917471] Re: [Regression] Bus Fatal Error observed when reboot on BCM5720

[Kai-Heng Feng]

Can you please try "reboot=" kernel parameter? the value can be "bios,
acpi, kbd, triple, efi, or pci".

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

Title:
  [Regression] Bus Fatal Error observed when reboot on BCM5720

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

Bug description:
  following error messages are observed

  [  146.429212] shutdown[1]: Rebooting.
  [  146.435151] kvm: exiting hardware virtualization
  [  146.575319] megaraid_sas :67:00.0: megasas_disable_intr_fusion is 
called outbound_intr_mask:0x4009
  [  148.088133] [qede_unload:2236(eno12409)]Link is down
  [  148.183618] qede :31:00.1: Ending qede_remove successfully
  [  148.518541] [qede_unload:2236(eno12399)]Link is down
  [  148.625066] qede :31:00.0: Ending qede_remove successfully
  [  148.762067] ACPI: Preparing to enter system sleep state S5
  [  148.794638] {1}[Hardware Error]: Hardware error from APEI Generic Hardware 
Error Source: 5
  [  148.803731] {1}[Hardware Error]: event severity: recoverable
  [  148.810191] {1}[Hardware Error]:  Error 0, type: fatal
  [  148.816088] {1}[Hardware Error]:   section_type: PCIe error
  [  148.822391] {1}[Hardware Error]:   port_type: 0, PCIe end point
  [  148.829026] {1}[Hardware Error]:   version: 3.0
  [  148.834266] {1}[Hardware Error]:   command: 0x0006, status: 0x0010
  [  148.841140] {1}[Hardware Error]:   device_id: :04:00.0
  [  148.847309] {1}[Hardware Error]:   slot: 0
  [  148.852077] {1}[Hardware Error]:   secondary_bus: 0x00
  [  148.857876] {1}[Hardware Error]:   vendor_id: 0x14e4, device_id: 0x165f
  [  148.865145] {1}[Hardware Error]:   class_code: 02
  [  148.870845] {1}[Hardware Error]:   aer_uncor_status: 0x0010, 
aer_uncor_mask: 0x0001
  [  148.879842] {1}[Hardware Error]:   aer_uncor_severity: 0x000ef030
  [  148.886575] {1}[Hardware Error]:   TLP Header: 4001 030f 90028090 

  [  148.894823] tg3 :04:00.0: AER: aer_status: 0x0010, aer_mask: 
0x0001
  [  148.902795] tg3 :04:00.0: AER:[20] UnsupReq   (First)
  [  148.910234] tg3 :04:00.0: AER: aer_layer=Transaction Layer, 
aer_agent=Requester ID
  [  148.918806] tg3 :04:00.0: AER: aer_uncor_severity: 0x000ef030
  [  148.925558] tg3 :04:00.0: AER:   TLP Header: 4001 030f 
90028090 
  [  148.933984] reboot: Restarting system
  [  148.938319] reboot: machine restart

  
  I  have observed the following. when I test older kernel 

  
  Kernel  version   Fatal Error
  5.4.0-42.46   No
  5.4.0-45.49   No
  5.4.0-47.51   No
  5.4.0-48.52   No
  5.4.0-51.56   No
  5.4.0-52.57   No
  5.4.0-53.59   No
  5.4.0-54.60   No
  5.4.0-58.64   No
  5.4.0-59.65   yes
  5.4.0-60.67   yes

  
  later I have bisect kernel between 5.4.0-58.64 and 5.4.0-59.65.

  looks like due to the following patch we are observing this issue. The
  driver is not handling D3 state properly

  PCI/ACPI: Whitelist hotplug ports for D3 if power managed by ACPI

  https://kernel.ubuntu.com/git/ubuntu/ubuntu-
  focal.git/commit/?id=b9319dd02269593911403dd5d684368bcef3261d

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


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

[Kernel-packages] [Bug 1965882] Re: [nouveau] External monitor plugged into (secondary) Nvidia GPU is all white (plus a little flicker)

[Daniel van Vugt]

Maybe this was caused by an Ubuntu config change? Building 5.14.20 and
5.14.1 from git results in failure now. Only the mainline debs of those
versions succeed.

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

Title:
  [nouveau] External monitor plugged into (secondary) Nvidia GPU is all
  white (plus a little flicker)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  External monitor plugged into (secondary) Nvidia GPU is all white
  (plus a little flicker) for gnome-shell/mutter when using nouveau. The
  primary GPU (i915) still works fine.

  This seems to be a kernel regression...

  FAIL: 5.17.0-051700drmtip20220322-generic
  FAIL: 5.17.0-051700-generic
  FAIL: 5.15.0-23-generic
  FAIL: 5.14.21-051421-generic
  PASS: 5.14.20-051420-generic
  PASS: 5.14.18-051418-generic
  PASS: 5.14.15-051415-generic
  PASS: 5.14.10-051410-generic
  PASS: 5.14.0-051400-generic
  PASS: 5.13.19-051319-generic
  PASS: 5.10.107-0510107-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-23-generic 5.15.0-23.23
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/by-id', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: pass
  Date: Tue Mar 22 16:35:58 2022
  InstallationDate: Installed on 2021-11-05 (136 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103)
  MachineType: Intel(R) Client Systems NUC9i7QNX
  ProcFB:
   0 i915drmfb
   1 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash 
nvidia-drm.modeset=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: QXCFL579.0034.2019.1125.1436
  dmi.board.name: NUC9i7QNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K49245-402
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 24.33
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX:
  dmi.product.family: QN
  dmi.product.name: NUC9i7QNX
  dmi.product.sku: BXNUC9i7QNX
  dmi.product.version: K49244-403
  dmi.sys.vendor: Intel(R) Client Systems

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


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

[Kernel-packages] [Bug 1965467] Re: Need to reset MT7921 BT when the firmware hang or command no response

[AceLan Kao]

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

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

Title:
  Need to reset MT7921 BT when the firmware hang or command no response

Status in HWE Next:
  New
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  Encounter BT command timeout issue when doing reboot test, and BT becomes 
unusable.
  Mar 15 22:04:44 u-Inspiron-15-3525 kernel: [ 463.633675] usb 3-4: reset 
high-speed USB device number 3 using xhci_hcd
  Mar 15 22:04:45 u-Inspiron-15-3525 kernel: [ 465.027012] Bluetooth: hci0: 
command 0x2005 tx timeout
  Mar 15 22:04:47 u-Inspiron-15-3525 kernel: [ 467.043176] Bluetooth: hci0: 
command 0x2041 tx timeout

  [Fix]
  Backport below 2 commit from v5.15-rc1 fix this issue
  e947802657cb Bluetooth: btusb: Support Bluetooth Reset for Mediatek 
Chip(MT7921)
  0b10c8c84c0c Bluetooth: btusb: Record debug log for Mediatek Chip.

  [Test]
  Verified on the problem machine, and confirmed it works

  [Where problems could occur]
  It adds a new function to cmd_timeout callback, so it won't affect old 
behaviors. This only affects the chip which has command timeout issue, and 
could reset the chip when encounter the issue.

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


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

[Kernel-packages] [Bug 1965467] Re: Need to reset MT7921 BT when the firmware hang or command no response

[Kai-Chuan Hsieh]

Test on WVB4-DVT2-A2, BIOS 1.2.0. reboot 50 times consecutively.

Didn't see consecutive Bluetooth tx timeout.

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

Title:
  Need to reset MT7921 BT when the firmware hang or command no response

Status in HWE Next:
  New
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  Encounter BT command timeout issue when doing reboot test, and BT becomes 
unusable.
  Mar 15 22:04:44 u-Inspiron-15-3525 kernel: [ 463.633675] usb 3-4: reset 
high-speed USB device number 3 using xhci_hcd
  Mar 15 22:04:45 u-Inspiron-15-3525 kernel: [ 465.027012] Bluetooth: hci0: 
command 0x2005 tx timeout
  Mar 15 22:04:47 u-Inspiron-15-3525 kernel: [ 467.043176] Bluetooth: hci0: 
command 0x2041 tx timeout

  [Fix]
  Backport below 2 commit from v5.15-rc1 fix this issue
  e947802657cb Bluetooth: btusb: Support Bluetooth Reset for Mediatek 
Chip(MT7921)
  0b10c8c84c0c Bluetooth: btusb: Record debug log for Mediatek Chip.

  [Test]
  Verified on the problem machine, and confirmed it works

  [Where problems could occur]
  It adds a new function to cmd_timeout callback, so it won't affect old 
behaviors. This only affects the chip which has command timeout issue, and 
could reset the chip when encounter the issue.

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


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

[Kernel-packages] [Bug 1962569] Re: jammy/linux-oem-5.17: 5.17.0-1001.1 -proposed tracker

[Ubuntu Kernel Bot]

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

** This bug is no longer a duplicate of bug 1965324
   jammy/linux-oem-5.17: 5.17.0-1002.2 -proposed tracker
** This bug has been marked a duplicate of bug 1966046
   jammy/linux-oem-5.17:  -proposed tracker

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

Title:
  jammy/linux-oem-5.17: 5.17.0-1001.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow boot-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrg series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrs series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Incomplete
Status in Kernel SRU Workflow sru-review series:
  Fix Released
Status in linux-oem-5.17 package in Ubuntu:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  built:
route-entry: 2
  delta:
promote-to-proposed:
- signed
- lrs
- lrm
- main
- meta
- lrg
sru-review:
- main
- lrg
- meta
- lrm
- signed
- lrs
  kernel-stable-master-bug: 1964766
  packages:
lrg: linux-restricted-generate-oem-5.17
lrm: linux-restricted-modules-oem-5.17
lrs: linux-restricted-signatures-oem-5.17
main: linux-oem-5.17
meta: linux-meta-oem-5.17
signed: linux-signed-oem-5.17
  phase: Testing
  phase-changed: Monday, 14. March 2022 22:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -s testing in progress
regression-testing: Stalled -s testing FAILED
  synthetic:
:promote-to-as-proposed: Fix Released
  variant: debs
  versions:
lrm: 5.17.0-1001.1+2
main: 5.17.0-1001.1
meta: 5.17.0.1001.1+1
signed: 5.17.0-1001.1
  versions-clamp:
self: 5.17.0-1001.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1962569/+subscriptions


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

[Kernel-packages] [Bug 1965002] Re: AWS: Hibernate resume crashes when platform changes

[Ubuntu Kernel Bot]

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

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: verification-needed-focal

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

Title:
  AWS: Hibernate resume crashes when platform changes

Status in linux-aws package in Ubuntu:
  Fix Committed
Status in linux-aws source package in Focal:
  Fix Committed
Status in linux-aws source package in Impish:
  Fix Committed
Status in linux-aws source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  At present, if a virt instance is hibernated and restarted in a
  different environment, the instance will crash. We have seen
  situations where customers have to enable support cases to recover an
  instance. The proposed patch is supposed to enable the kernel to
  detect the change and reboot the instance instead of crashing. In the
  ACPI specification; there is a 'hardware signature' field in the ACPI
  tables, and the OS can reboot cleanly if/when that signature changes,
  instead of attempting the resume and crashing.

  [Fix]
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=74d9
  
https://lore.kernel.org/lkml/9099d8903e9b2b16daec712acc9aa533fe84d102.ca...@infradead.org/T/#u

  [Test Case]

  Hibernate an AWS instance, resume on a different platform. Positive
  test results from Amazon engineers.

  [Where things could go wrong]

  Resume currently crashes when a hibernated instance is migrated to a
  new machine. It can't get much worse, unless the initial hibernate
  fails.

  [Other Info]

  SF: #00330794

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


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

[Kernel-packages] [Bug 1966056] [NEW] Jammy update: v5.15.29 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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


Linux 5.15.29
vhost: allow batching hint without size
Revert "net: dsa: mv88e6xxx: flush switchdev FDB workqueue before removing VLAN"
block: drop unused includes in 
riscv: dts: k210: fix broken IRQs on hart1
drm/i915: Workaround broken BIOS DBUF configuration on TGL/RKL
btrfs: make send work with concurrent block group relocation
drm/panel: Select DRM_DP_HELPER for DRM_PANEL_EDP
x86/traps: Mark do_int3() NOKPROBE_SYMBOL
x86/sgx: Free backing memory after faulting the enclave page
x86/boot: Add setup_indirect support in early_memremap_is_setup_data()
x86/boot: Fix memremap of setup_indirect structures
watch_queue: Make comment about setting ->defunct more accurate
watch_queue: Fix lack of barrier/sync/lock between post and read
watch_queue: Free the alloc bitmap when the watch_queue is torn down
watch_queue: Fix the alloc bitmap size to reflect notes allocated
watch_queue: Fix to always request a pow-of-2 pipe ring size
watch_queue: Fix to release page in ->release()
watch_queue, pipe: Free watchqueue state after clearing pipe ring
watch_queue: Fix filter limit check
ARM: fix Thumb2 regression with Spectre BHB
net/mlx5: Fix offloading with ESWITCH_IPV4_TTL_MODIFY_ENABLE
virtio: acknowledge all features before access
virtio: unexport virtio_finalize_features
KVM: x86/mmu: kvm_faultin_pfn has to return false if pfh is returned
swiotlb: rework "fix info leak with DMA_FROM_DEVICE"
arm64: kasan: fix include error in MTE functions
arm64: Ensure execute-only permissions are not allowed without EPAN
arm64: dts: marvell: armada-37xx: Remap IO space to bus address 0x0
tracing/osnoise: Force quiescent states while tracing
riscv: Fix auipc+jalr relocation range checks
mmc: meson: Fix usage of meson_mmc_post_req()
riscv: alternative only works on !XIP_KERNEL
net: macb: Fix lost RX packet wakeup race in NAPI receive
staging: gdm724x: fix use after free in gdm_lte_rx()
staging: rtl8723bs: Fix access-point mode deadlock
fuse: fix pipe buffer lifetime for direct_io
fuse: fix fileattr op failure
ARM: Spectre-BHB: provide empty stub for non-config
selftests/memfd: clean up mapping in mfd_fail_write
selftest/vm: fix map_fixed_noreplace test failure
tracing/osnoise: Make osnoise_main to sleep for microseconds
tracing: Ensure trace buffer is at least 4096 bytes large
ipv6: prevent a possible race condition with lifetimes
Revert "xen-netback: Check for hotplug-status existence before watching"
Revert "xen-netback: remove 'hotplug-status' once it has served its purpose"
drm/amdgpu: bypass tiling flag check in virtual display case (v2)
gpio: Return EPROBE_DEFER if gc->to_irq is NULL
PCI: Mark all AMD Navi10 and Navi14 GPU ATS as broken
hwmon: (pmbus) Clear pmbus fault/warning bits after read
net-sysfs: add check for netdevice being present to speed_show
x86/kvm: Don't use pv tlb/ipi/sched_yield if on 1 vCPU
drm/vc4: hdmi: Unregister codec device on unbind
spi: rockchip: terminate dma transmission when slave abort
spi: rockchip: Fix error in getting num-cs property
kvm: x86: Disable KVM_HC_CLOCK_PAIRING if tsc is in always catchup mode
KVM: Fix lockdep false negative during host resume
pinctrl: tigerlake: Revert "Add Alder Lake-M ACPI ID"
usb: dwc3: pci: add support for the Intel Raptor Lake-S
swiotlb: fix info leak with DMA_FROM_DEVICE
selftests/bpf: Add test for bpf_timer overwriting crash
net: phy: meson-gxl: improve link-up behavior
net: bcmgenet: Don't claim WOL when its not available
sctp: fix kernel-infoleak for SCTP sockets
net: phy: DP83822: clear MISR2 register to disable interrupts
gianfar: ethtool: Fix refcount leak in gfar_get_ts_info
gpio: ts4900: Do not set DAT and OE together
selftests: pmtu.sh: Kill nettest processes launched in subshell.
selftests: pmtu.sh: Kill tcpdump processes launched by subshell.
NFC: port100: fix use-after-free in port100_send_complete
net/mlx5e: Lag, Only handle events from highest priority multipath entry
net/mlx5: Fix a race on command flush flow
net/mlx5: Fix size field in bufferx_reg struct
ax25: Fix NULL pointer dereference in ax25_kill_by_device
net: marvell: prestera: Add missing of_node_put() in 
prestera_switch_set_base_mac_addr
net: ethernet: lpc_eth: Handle error for clk_enable
net: ethernet: ti: cpts: Handle error for clk_enable
tipc: fix incorrect order of state message data sanity check
ethernet: Fix error handling in xemaclite_of_probe
ice: Fix curr_link_speed advertised speed
ice: Don't use GFP_KERNEL in atomic context
ice

[Kernel-packages] [Bug 1966055] [NEW] Jammy update: v5.15.28 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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


Linux 5.15.28
Revert "ACPI: PM: s2idle: Cancel wakeup before dispatching EC GPE"
xen/netfront: react properly to failing gnttab_end_foreign_access_ref()
xen/gnttab: fix gnttab_end_foreign_access() without page specified
xen/pvcalls: use alloc/free_pages_exact()
xen/9p: use alloc/free_pages_exact()
xen: remove gnttab_query_foreign_access()
xen/gntalloc: don't use gnttab_query_foreign_access()
xen/scsifront: don't use gnttab_query_foreign_access() for mapped status
xen/netfront: don't use gnttab_query_foreign_access() for mapped status
xen/blkfront: don't use gnttab_query_foreign_access() for mapped status
xen/grant-table: add gnttab_try_end_foreign_access()
xen/xenbus: don't let xenbus_grant_ring() remove grants in error case
ARM: fix build warning in proc-v7-bugs.c
arm64: Do not include __READ_ONCE() block in assembly files
ARM: Do not use NOCROSSREFS directive with ld.lld
ARM: fix co-processor register typo
ARM: fix build error when BPF_SYSCALL is disabled
arm64: proton-pack: Include unprivileged eBPF status in Spectre v2 mitigation 
reporting
arm64: Use the clearbhb instruction in mitigations
KVM: arm64: Allow SMCCC_ARCH_WORKAROUND_3 to be discovered and migrated
arm64: Mitigate spectre style branch history side channels
arm64: proton-pack: Report Spectre-BHB vulnerabilities as part of Spectre-v2
arm64: Add percpu vectors for EL1
arm64: entry: Add macro for reading symbol addresses from the trampoline
arm64: entry: Add vectors that have the bhb mitigation sequences
arm64: entry: Add non-kpti __bp_harden_el1_vectors for mitigations
arm64: entry: Allow the trampoline text to occupy multiple pages
arm64: entry: Make the kpti trampoline's kpti sequence optional
arm64: entry: Move trampoline macros out of ifdef'd section
arm64: entry: Don't assume tramp_vectors is the start of the vectors
arm64: entry: Allow tramp_alias to access symbols after the 4K boundary
arm64: entry: Move the trampoline data page before the text page
arm64: entry: Free up another register on kpti's tramp_exit path
arm64: entry: Make the trampoline cleanup optional
KVM: arm64: Allow indirect vectors to be used without SPECTRE_V3A
arm64: spectre: Rename spectre_v4_patch_fw_mitigation_conduit
arm64: entry.S: Add ventry overflow sanity checks
arm64: cpufeature: add HWCAP for FEAT_RPRES
arm64: cpufeature: add HWCAP for FEAT_AFP
arm64: add ID_AA64ISAR2_EL1 sys register
arm64: Add Cortex-X2 CPU part definition
arm64: Add HWCAP for self-synchronising virtual counter
arm64: Add Neoverse-N2, Cortex-A710 CPU part definition
ARM: include unprivileged BPF status in Spectre V2 reporting
ARM: Spectre-BHB workaround
ARM: use LOADADDR() to get load address of sections
ARM: early traps initialisation
ARM: report Spectre v2 status through sysfs
x86/speculation: Warn about eIBRS + LFENCE + Unprivileged eBPF + SMT
x86/speculation: Warn about Spectre v2 LFENCE mitigation
x86/speculation: Update link to AMD speculation whitepaper
x86/speculation: Use generic retpoline by default on AMD
x86/speculation: Include unprivileged eBPF status in Spectre v2 mitigation 
reporting
Documentation/hw-vuln: Update spectre doc
x86/speculation: Add eIBRS + Retpoline options
x86/speculation: Rename RETPOLINE_AMD to RETPOLINE_LFENCE
x86,bugs: Unconditionally allow spectre_v2=retpoline,amd
slip: fix macro redefine warning

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

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


** Tags: kernel-stable-tracking-bug

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

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

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: 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/1966055

Title:
  Jammy update: v5.15.28 upstream stable release

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

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

[Kernel-packages] [Bug 1966057] [NEW] Jammy update: v5.15.30 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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

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

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


** Tags: kernel-stable-tracking-bug

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

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

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: 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/1966057

Title:
  Jammy update: v5.15.30 upstream stable release

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

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.30 upstream stable release
 from git://git.kernel.org/

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


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

[Kernel-packages] [Bug 1964796] Re: Fix unmatched ASMedia ASM2824 PCIe link training

[Alexandre Ghiti]

A similar patch that solves the same issue was actually merged for 5.18
[1].

I encountered this bug with our current u-boot (2022.01+dfsg-2ubuntu1)
and linux kernel (5.15.0-1004.4): I applied the patch in [1] on top of
5.15.0-1004.4 successfully and it solved the problem. So as you already
tagged it, this should be cherry-picked for 22.04. A similar patch for
u-boot exists, I'll report a new bug there.

Thanks

[1] https://patchwork.kernel.org/project/linux-
riscv/patch/20220318152430.526320-1-ben.do...@codethink.co.uk/

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

Title:
  Fix unmatched ASMedia ASM2824 PCIe link training

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  
https://lore.kernel.org/all/alpine.deb.2.21.2202010240190.58...@angie.orcam.me.uk/raw

  It has been discovered that Unmatched board ships ASMedia ASM2824 PCIe
  which frequently fails to complete link training and negotiate stable
  and fast speeds.

  To ensure PCIe devices on Unmatched board can operate with stable and
  predictable link speeds cherry-pick upstream submitted patch that
  resolves the issue.

  It is currently applied as a SAUCE patch, whilst the upstream
  inclusion review is ongoing.

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


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

[Kernel-packages] [Bug 1966061] [NEW] thinkpad_acpi: Support privacy-screen

[Bin Li]

Public bug reported:

On 5.15.0-23-generic, the lcdshadow is not synced.

$ cat /proc/acpi/ibm/lcdshadow
status: 0
commands: 0, 1

And after press the Fn + D, the screen display angle changed, but the
content of /proc/acpi/ibm/lcdshadow d0 not change.

** Affects: oem-priority
 Importance: Undecided
 Status: New

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


** Tags: oem-priority originate-from-1956808 sutton

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

Title:
  thinkpad_acpi: Support privacy-screen

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On 5.15.0-23-generic, the lcdshadow is not synced.

  $ cat /proc/acpi/ibm/lcdshadow
  status: 0
  commands: 0, 1

  And after press the Fn + D, the screen display angle changed, but the
  content of /proc/acpi/ibm/lcdshadow d0 not change.

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


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

[Kernel-packages] [Bug 1966061] Re: thinkpad_acpi: Support privacy-screen

[Bin Li]

Found a patch, not verified yet.

commit e8b7eb66738f559da1688ef3e4038180d7343547
Author: Hans de Goede 
Date:   Tue Oct 5 22:23:19 2021 +0200

platform/x86: thinkpad_acpi: Get privacy-screen / lcdshadow ACPI handles 
only once

Get the privacy-screen / lcdshadow ACPI handles once and cache them,
instead of retrieving them every time we need them.

Reviewed-by: Emil Velikov 
Reviewed-by: Lyude Paul 
Reviewed-by: Mark Pearson 
Signed-off-by: Hans de Goede 
Link: 
https://patchwork.freedesktop.org/patch/msgid/20211005202322.700909-8-hdego...@redhat.com


** Tags added: oem-priority originate-from-1956808 sutton

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

Title:
  thinkpad_acpi: Support privacy-screen

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On 5.15.0-23-generic, the lcdshadow is not synced.

  $ cat /proc/acpi/ibm/lcdshadow
  status: 0
  commands: 0, 1

  And after press the Fn + D, the screen display angle changed, but the
  content of /proc/acpi/ibm/lcdshadow d0 not change.

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


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

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

[Ubuntu Kernel Bot]

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

apport-collect 1966061

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

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

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

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

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

Title:
  thinkpad_acpi: Support privacy-screen

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On 5.15.0-23-generic, the lcdshadow is not synced.

  $ cat /proc/acpi/ibm/lcdshadow
  status: 0
  commands: 0, 1

  And after press the Fn + D, the screen display angle changed, but the
  content of /proc/acpi/ibm/lcdshadow d0 not change.

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


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

[Kernel-packages] [Bug 1966066] [NEW] audio from external sound card is distorted

[Hampus Lundberg]

Public bug reported:

The sound card is a Focusrite Scarlett 2i2.

The sound is distorted everywhere.

Sound via HDMI works.

Seen others having the same problem:
https://askubuntu.com/questions/138284/how-to-downgrade-a-package-via-
apt-get

ubuntu release: Ubuntu 20.04.4 LTS
package name involved in bug: linux-image-5.13.0-37-generic

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 23 12:56:02 2022
InstallationDate: Installed on 2020-12-18 (459 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: linux-signed-hwe-5.13
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-5.13 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  audio from external sound card is distorted

Status in linux-signed-hwe-5.13 package in Ubuntu:
  New

Bug description:
  The sound card is a Focusrite Scarlett 2i2.

  The sound is distorted everywhere.

  Sound via HDMI works.

  Seen others having the same problem:
  https://askubuntu.com/questions/138284/how-to-downgrade-a-package-via-
  apt-get

  ubuntu release: Ubuntu 20.04.4 LTS
  package name involved in bug: linux-image-5.13.0-37-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 12:56:02 2022
  InstallationDate: Installed on 2020-12-18 (459 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1966066/+subscriptions


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

[Kernel-packages] [Bug 1962477] Re: Can't pair Bluetooth devices using TP-Link UB500 Adaptor

[Launchpad Bug Tracker]

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

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

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

Title:
  Can't pair Bluetooth devices using TP-Link UB500 Adaptor

Status in linux-signed-hwe-5.8 package in Ubuntu:
  Confirmed

Bug description:
  $ lsusb
  Bus 001 Device 006: ID 2357:0604 TP-Link TP-Link UB500 Adapter

  Other users have fixed by patching the kernel:
  https://askubuntu.com/questions/1370663/bluetooth-scan-doesnt-detect-
  any-device-on-ubuntu-21-10

  Please add support for this device so that Users don't need to patch
  the kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-59-generic 5.8.0-59.66~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-59-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Feb 28 22:31:55 2022
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1962477/+subscriptions


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

[Kernel-packages] [Bug 1966066] Re: audio from external sound card is distorted

[Launchpad Bug Tracker]

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

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

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

Title:
  audio from external sound card is distorted

Status in linux-signed-hwe-5.13 package in Ubuntu:
  Confirmed

Bug description:
  The sound card is a Focusrite Scarlett 2i2.

  The sound is distorted everywhere.

  Sound via HDMI works.

  Seen others having the same problem:
  https://askubuntu.com/questions/138284/how-to-downgrade-a-package-via-
  apt-get

  ubuntu release: Ubuntu 20.04.4 LTS
  package name involved in bug: linux-image-5.13.0-37-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 12:56:02 2022
  InstallationDate: Installed on 2020-12-18 (459 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1966066/+subscriptions


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

[Kernel-packages] [Bug 1966066] Re: audio from external sound card is distorted

[rebd]

I think these might be related
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1966060

Other people seem to be having issues with the latest kernel
https://forums.linuxmint.com/viewtopic.php?f=49&t=370408

If I roll back to 5.13.0-35, the audio seemsto work just fine.

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

Title:
  audio from external sound card is distorted

Status in linux-signed-hwe-5.13 package in Ubuntu:
  Confirmed

Bug description:
  The sound card is a Focusrite Scarlett 2i2.

  The sound is distorted everywhere.

  Sound via HDMI works.

  Seen others having the same problem:
  https://askubuntu.com/questions/138284/how-to-downgrade-a-package-via-
  apt-get

  ubuntu release: Ubuntu 20.04.4 LTS
  package name involved in bug: linux-image-5.13.0-37-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 12:56:02 2022
  InstallationDate: Installed on 2020-12-18 (459 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1966066/+subscriptions


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

[Kernel-packages] [Bug 1798166] Re: “Mouse battery low” notification can't be disabled

[Jon Grah]

I'm using Ubuntu 20.04.4 LTS and GNOME 3.36.8

Still having this problem.  Very surprised it has lasted this long. In
any case, if it is fixed, will this change make it to the next LTS
update?

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

Title:
  “Mouse battery low” notification can't be disabled

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Invalid

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/108

  ---

  I have a wireless mouse powered by non-rechargeable battery. The mouse
  works absolutely fine even with low battery level. Problem is, Ubuntu
  gives notifications about the battery level all the time.

  I have had this issue for almost two months now, and mouse is working
  perfectly. I had to click away the notification almost every time I
  moved the mouse. I was then able to make the notifications appear less
  frequently, but the notification still always appear after some
  interval, and always after I log in.

  Here are some specific things I have tried, they have not helped.

  https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery-
  low-notification-in-ubuntu-18-04

  1)
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  2)
  I assume the packet in question is notify-osd, not sure.
  notify-osd:
    Installed: (none)
    Candidate: 0.9.35+16.04.20160415-0ubuntu2
    Version table:
   0.9.35+16.04.20160415-0ubuntu2 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) I expected that no notifications would appear when notifications
  are set to off

  4) Mouse battery low - notification always appears
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ohto   2927 F...m pulseaudio
   /dev/snd/controlC0:  ohto   2927 F pulseaudio
   /dev/snd/controlC1:  ohto   2927 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-07-28 (79 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1
  ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F12
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77X-UP5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions


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

[Kernel-packages] [Bug 1965846] Re: Enable the mic-mute led on Dell XPS 9315

[Chris Chiu]

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

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

** Changed in: linux-oem-5.14 (Ubuntu Focal)
 Assignee: (unassigned) => Chris Chiu (mschiu77)

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

Title:
  Enable the mic-mute led on Dell XPS 9315

Status in HWE Next:
  New
Status in linux-oem-5.14 package in Ubuntu:
  In Progress
Status in linux-oem-5.14 source package in Focal:
  In Progress

Bug description:
  [Impact]
  On Dell's XPS 9315, the MIC-Mute function is working but the LED(on F4) state 
is not changed accordingly.

  [Fix]
  Dell's mic mute support in privacy mode has been upstream, but the the 
mic-mute led support is still SAUCE patch which is maintained with DMI based 
quirk. Add a new SKU for XPS 9315 until Dell's official fix for the mic-mute 
led.

  [Test Case]
  1. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD 
icon.
  2. The mic-mute led should be ON when mic-mute enabled, OFF when disabled.

  [Where problems could occur]
  It's only working on the particular SKU defined in DMI table. Will need to 
drop it when Dell release the official solution.

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


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

[Kernel-packages] [Bug 1917471] Re: [Regression] Bus Fatal Error observed when reboot on BCM5720

[Jeff Lane]

** Description changed:

+ impact
+ being noticed a lot, only affects 5.4, fix in subsequent failures
+ 
+ The offending patch was removed in 20.10 and later kernels (it was
+ reverted upstream not long after being merged into mainline but we never
+ reverted it)
+ 
+ 
  following error messages are observed
  
  [  146.429212] shutdown[1]: Rebooting.
  [  146.435151] kvm: exiting hardware virtualization
  [  146.575319] megaraid_sas :67:00.0: megasas_disable_intr_fusion is 
called outbound_intr_mask:0x4009
  [  148.088133] [qede_unload:2236(eno12409)]Link is down
  [  148.183618] qede :31:00.1: Ending qede_remove successfully
  [  148.518541] [qede_unload:2236(eno12399)]Link is down
  [  148.625066] qede :31:00.0: Ending qede_remove successfully
  [  148.762067] ACPI: Preparing to enter system sleep state S5
  [  148.794638] {1}[Hardware Error]: Hardware error from APEI Generic Hardware 
Error Source: 5
  [  148.803731] {1}[Hardware Error]: event severity: recoverable
  [  148.810191] {1}[Hardware Error]:  Error 0, type: fatal
  [  148.816088] {1}[Hardware Error]:   section_type: PCIe error
  [  148.822391] {1}[Hardware Error]:   port_type: 0, PCIe end point
  [  148.829026] {1}[Hardware Error]:   version: 3.0
  [  148.834266] {1}[Hardware Error]:   command: 0x0006, status: 0x0010
  [  148.841140] {1}[Hardware Error]:   device_id: :04:00.0
  [  148.847309] {1}[Hardware Error]:   slot: 0
  [  148.852077] {1}[Hardware Error]:   secondary_bus: 0x00
  [  148.857876] {1}[Hardware Error]:   vendor_id: 0x14e4, device_id: 0x165f
  [  148.865145] {1}[Hardware Error]:   class_code: 02
  [  148.870845] {1}[Hardware Error]:   aer_uncor_status: 0x0010, 
aer_uncor_mask: 0x0001
  [  148.879842] {1}[Hardware Error]:   aer_uncor_severity: 0x000ef030
  [  148.886575] {1}[Hardware Error]:   TLP Header: 4001 030f 90028090 

  [  148.894823] tg3 :04:00.0: AER: aer_status: 0x0010, aer_mask: 
0x0001
  [  148.902795] tg3 :04:00.0: AER:[20] UnsupReq   (First)
  [  148.910234] tg3 :04:00.0: AER: aer_layer=Transaction Layer, 
aer_agent=Requester ID
  [  148.918806] tg3 :04:00.0: AER: aer_uncor_severity: 0x000ef030
  [  148.925558] tg3 :04:00.0: AER:   TLP Header: 4001 030f 
90028090 
  [  148.933984] reboot: Restarting system
  [  148.938319] reboot: machine restart
  
- 
- I  have observed the following. when I test older kernel 
- 
+ I  have observed the following. when I test older kernel
  
  Kernel  version   Fatal Error
  5.4.0-42.46   No
  5.4.0-45.49   No
  5.4.0-47.51   No
  5.4.0-48.52   No
  5.4.0-51.56   No
  5.4.0-52.57   No
  5.4.0-53.59   No
  5.4.0-54.60   No
  5.4.0-58.64   No
  5.4.0-59.65   yes
  5.4.0-60.67   yes
  
- 
  later I have bisect kernel between 5.4.0-58.64 and 5.4.0-59.65.
  
  looks like due to the following patch we are observing this issue. The
  driver is not handling D3 state properly
  
  PCI/ACPI: Whitelist hotplug ports for D3 if power managed by ACPI
  
  https://kernel.ubuntu.com/git/ubuntu/ubuntu-
  focal.git/commit/?id=b9319dd02269593911403dd5d684368bcef3261d

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

Title:
  [Regression] Bus Fatal Error observed when reboot on BCM5720

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

Bug description:
  impact
  being noticed a lot, only affects 5.4, fix in subsequent failures

  The offending patch was removed in 20.10 and later kernels (it was
  reverted upstream not long after being merged into mainline but we
  never reverted it)


  following error messages are observed

  [  146.429212] shutdown[1]: Rebooting.
  [  146.435151] kvm: exiting hardware virtualization
  [  146.575319] megaraid_sas :67:00.0: megasas_disable_intr_fusion is 
called outbound_intr_mask:0x4009
  [  148.088133] [qede_unload:2236(eno12409)]Link is down
  [  148.183618] qede :31:00.1: Ending qede_remove successfully
  [  148.518541] [qede_unload:2236(eno12399)]Link is down
  [  148.625066] qede :31:00.0: Ending qede_remove successfully
  [  148.762067] ACPI: Preparing to enter system sleep state S5
  [  148.794638] {1}[Hardware Error]: Hardware error from APEI Generic Hardware 
Error Source: 5
  [  148.803731] {1}[Hardware Error]: event severity: recoverable
  [  148.810191] {1}[Hardware Error]:  Error 0, type: fatal
  [  148.816088] {1}[Hardware Error]:   section_type: PCIe error
  [  148.822391] {1}[Hardware Error]:   port_type: 0, PCIe end point
  [  148.829026] {1}[Hardware Error]:   version: 3.0
  [  148.834266] {1}[Hardware Error]:   command: 0x0006, status: 0x0010
  [  148.841140] {1}[Hardware Error]:   device_id: :04:00.0
  [  148.847309] {1}[Hardware Err

[Kernel-packages] [Bug 1965241] Re: Include DPC Fixes in Ubuntu 22.04 and 20.04

[Jeff Lane]

** Description changed:

- These are some of the DPC fixes which help in handling some of the
- failure cases of DownPort Containment events. Without these, recovery
- from DPC event fails and NVMe endpoint is not accessible for some of the
- scenarios.
+ Impact:
+ 
+ Target kernels: 5.15
+ 
+ 
+ 
+ 
+ 
+ These are some of the DPC fixes which help in handling some of the failure 
cases of DownPort Containment events. Without these, recovery from DPC event 
fails and NVMe endpoint is not accessible for some of the scenarios.
  
  Upstream kernel patches to be included into Ubuntu 22.04 SRU and into
  Ubuntu 20.04.5:
  
+ Already in Jammy as of Ubuntu-5.15.0-1.1
  PCI/portdrv: Enable Bandwidth Notification only if port supports it
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6&id=00823dcbdd415c868390feaca16f0265101efab4
  
+ Not yet pulled
  PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6&id=ea401499e943c307e6d44af6c2b4e068643e7884

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

Title:
  Include DPC Fixes in Ubuntu 22.04 and 20.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Impact:

  Target kernels: 5.15




  
  These are some of the DPC fixes which help in handling some of the failure 
cases of DownPort Containment events. Without these, recovery from DPC event 
fails and NVMe endpoint is not accessible for some of the scenarios.

  Upstream kernel patches to be included into Ubuntu 22.04 SRU and into
  Ubuntu 20.04.5:

  Already in Jammy as of Ubuntu-5.15.0-1.1
  PCI/portdrv: Enable Bandwidth Notification only if port supports it
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6&id=00823dcbdd415c868390feaca16f0265101efab4

  Not yet pulled
  PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6&id=ea401499e943c307e6d44af6c2b4e068643e7884

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


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

[Kernel-packages] [Bug 1948636] Re: Ubuntu 22.04 Feature Request-NVMe: Include libnvme package

[Jeff Lane]

** Changed in: linux (Ubuntu Jammy)
   Status: Incomplete => 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/1948636

Title:
  Ubuntu 22.04 Feature Request-NVMe: Include libnvme package

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

Bug description:
  Upstream (Keith Busch) has started to revive libnvme with the hope of having 
nvme-cli use libnvme in future. New features like CDC client will be developed 
on libnvme.
  Upstream plans are to make libnvme a standalone package that other projects 
would depend on.

  We request that Ubuntu 22.04 carry the new libnvme package.
  https://github.com/linux-nvme/libnvme

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


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

[Kernel-packages] [Bug 1934620] Re: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS

[Jeff Lane]

** Changed in: linux (Ubuntu)
   Status: Won't Fix => 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/1934620

Title:
  NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup
  failed if SR-IOV is disabled in BIOS

Status in dellserver:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installing NVidia A100-80GB GPUs in R750XA fails to initialize BAR memory 
space for GPUs.
  Multiple error messages in kernel.log file.

  Summary:
  * Dell prefers to set SRIOV to disabled in bios globally
  * This bug does not occur IF:
  SRIOV is enabled in BIOS OR
  "pci=realloc=off" is passed to the kernel at boot time
  * This bug only affects systems with NVIDIA A100-80GB GPUs, it does not 
affect systems with NVIDIA A100-40GB GPUs

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


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

[Kernel-packages] [Bug 1966089] [NEW] Update OS policy capability handshake

[Colin Ian King]

Public bug reported:

== SRU JAMMY ==

Update int340x OS policy capability handshake; required for full
functionality in thermald 2.4.9 to improve functionality for newer H/W.

== The fix ==

Upstream commit:

commit c7ff29763989bd09c433f73fae3c1e1c15d9cda4
Author: Srinivas Pandruvada 
Date:   Mon Mar 14 15:09:37 2022 -0700

thermal: int340x: Update OS policy capability handshake

Update the firmware with OS supported policies mask, so that firmware can
relinquish its internal controls. Without this update several Tiger Lake
laptops gets performance limited with in few seconds of executing in
turbo region.

The existing way of enumerating firmware policies via IDSP method and
selecting policy by directly writing those policy UUIDS via _OSC method
is not supported in newer generation of hardware.

There is a new UUID "B23BA85D-C8B7-3542-88DE-8DE2FFCFD698" is defined for
updating policy capabilities. As part of ACPI _OSC method:

Arg0 - UUID: B23BA85D-C8B7-3542-88DE-8DE2FFCFD698
Arg1 - Rev ID: 1
Arg2 - Count: 2
Arg3 - Capability buffers: Array of Arg2 DWORDS

DWORD1: As defined in the ACPI 5.0 Specification
- Bit 0: Query Flag
- Bits 1-3: Always 0
- Bits 4-31: Reserved

DWORD2 and beyond:
- Bit0: set to 1 to indicate Intel(R) Dynamic Tuning is active, 0 to
indicate it is disabled and legacy thermal mechanism should
be enabled.
- Bit1: set to 1 to indicate Intel(R) Dynamic Tuning is controlling
active cooling, 0 to indicate bios shall enable legacy thermal
zone with active trip point.
- Bit2: set to 1 to indicate Intel(R) Dynamic Tuning is controlling
passive cooling, 0 to indicate bios shall enable legacy thermal
zone with passive trip point.
- Bit3: set to 1 to indicate Intel(R) Dynamic Tuning is handling
critical trip point, 0 to indicate bios shall enable legacy
thermal zone with critical trip point.
- Bits 4:31: Reserved

From sysfs interface, there is an existing interface to update policy
UUID using attribute "current_uuid". User space can write the same UUID
for ACTIVE, PASSIVE and CRITICAL policy. Driver converts these UUIDs to
DWORD2 Bit 1 to Bit 3. When any of the policy is activated by user
space it is assumed that dynamic tuning is active.

For example
$cd /sys/bus/platform/devices/INTC1040:00/uuids
To support active policy
$echo "3A95C389-E4B8-4629-A526-C52C88626BAE" > current_uuid
To support passive policy
$echo "42A441D6-AE6A-462b-A84B-4A8CE79027D3" > current_uuid
To support critical policy
$echo "97C68AE7-15FA-499c-B8C9-5DA81D606E0A" > current_uuid

To check all the supported policies
$cat current_uuid
3A95C389-E4B8-4629-A526-C52C88626BAE
42A441D6-AE6A-462b-A84B-4A8CE79027D3
97C68AE7-15FA-499c-B8C9-5DA81D606E0A

To match the bit format for DWORD2, rearranged enum int3400_thermal_uuid
and int3400_thermal_uuids[] by swapping current INT3400_THERMAL_ACTIVE
and INT3400_THERMAL_PASSIVE_1.

If the policies are enumerated via IDSP method then legacy method is
used, if not the new method is used to update policy support.

Signed-off-by: Srinivas Pandruvada 
Signed-off-by: Rafael J. Wysocki 

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Andrea Righi (arighi)
 Status: New

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Andrea Righi (arighi)

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

Title:
  Update OS policy capability handshake

Status in linux package in Ubuntu:
  New

Bug description:
  == SRU JAMMY ==

  Update int340x OS policy capability handshake; required for full
  functionality in thermald 2.4.9 to improve functionality for newer
  H/W.

  == The fix ==

  Upstream commit:

  commit c7ff29763989bd09c433f73fae3c1e1c15d9cda4
  Author: Srinivas Pandruvada 
  Date:   Mon Mar 14 15:09:37 2022 -0700

  thermal: int340x: Update OS policy capability handshake
  
  Update the firmware with OS supported policies mask, so that firmware can
  relinquish its internal controls. Without this update several Tiger Lake
  laptops gets performance limited with in few seconds of executing in
  turbo region.
  
  The existing way of enumerating firmware policies via IDSP method and
  selecting policy by directly writing those policy UUIDS via _OSC method
  is not supported in newer generation of hardware.
  
  There is a new UUID "B23BA85D-C8B7-3542-88DE-8DE2FFCFD698" is defined for
  updating policy capabilities. As part of ACPI _OSC method:
  
  Arg0 - UUID: B23BA85D-C8B7-3542-88DE-8DE2FFCFD698
  Arg1 - Rev ID: 1
  Arg2 - Count: 2
  Arg3 - Capabi

[Kernel-packages] [Bug 1966089] Re: Update OS policy capability handshake

[Colin Ian King]

This fix was requested by the thermald developer Srinivas Pandruvada to
support the new version of thermald.

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

Title:
  Update OS policy capability handshake

Status in linux package in Ubuntu:
  New

Bug description:
  == SRU JAMMY ==

  Update int340x OS policy capability handshake; required for full
  functionality in thermald 2.4.9 to improve functionality for newer
  H/W.

  == The fix ==

  Upstream commit:

  commit c7ff29763989bd09c433f73fae3c1e1c15d9cda4
  Author: Srinivas Pandruvada 
  Date:   Mon Mar 14 15:09:37 2022 -0700

  thermal: int340x: Update OS policy capability handshake
  
  Update the firmware with OS supported policies mask, so that firmware can
  relinquish its internal controls. Without this update several Tiger Lake
  laptops gets performance limited with in few seconds of executing in
  turbo region.
  
  The existing way of enumerating firmware policies via IDSP method and
  selecting policy by directly writing those policy UUIDS via _OSC method
  is not supported in newer generation of hardware.
  
  There is a new UUID "B23BA85D-C8B7-3542-88DE-8DE2FFCFD698" is defined for
  updating policy capabilities. As part of ACPI _OSC method:
  
  Arg0 - UUID: B23BA85D-C8B7-3542-88DE-8DE2FFCFD698
  Arg1 - Rev ID: 1
  Arg2 - Count: 2
  Arg3 - Capability buffers: Array of Arg2 DWORDS
  
  DWORD1: As defined in the ACPI 5.0 Specification
  - Bit 0: Query Flag
  - Bits 1-3: Always 0
  - Bits 4-31: Reserved
  
  DWORD2 and beyond:
  - Bit0: set to 1 to indicate Intel(R) Dynamic Tuning is active, 0 to
  indicate it is disabled and legacy thermal mechanism should
  be enabled.
  - Bit1: set to 1 to indicate Intel(R) Dynamic Tuning is controlling
  active cooling, 0 to indicate bios shall enable legacy thermal
  zone with active trip point.
  - Bit2: set to 1 to indicate Intel(R) Dynamic Tuning is controlling
  passive cooling, 0 to indicate bios shall enable legacy thermal
  zone with passive trip point.
  - Bit3: set to 1 to indicate Intel(R) Dynamic Tuning is handling
  critical trip point, 0 to indicate bios shall enable legacy
  thermal zone with critical trip point.
  - Bits 4:31: Reserved
  
  From sysfs interface, there is an existing interface to update policy
  UUID using attribute "current_uuid". User space can write the same UUID
  for ACTIVE, PASSIVE and CRITICAL policy. Driver converts these UUIDs to
  DWORD2 Bit 1 to Bit 3. When any of the policy is activated by user
  space it is assumed that dynamic tuning is active.
  
  For example
  $cd /sys/bus/platform/devices/INTC1040:00/uuids
  To support active policy
  $echo "3A95C389-E4B8-4629-A526-C52C88626BAE" > current_uuid
  To support passive policy
  $echo "42A441D6-AE6A-462b-A84B-4A8CE79027D3" > current_uuid
  To support critical policy
  $echo "97C68AE7-15FA-499c-B8C9-5DA81D606E0A" > current_uuid
  
  To check all the supported policies
  $cat current_uuid
  3A95C389-E4B8-4629-A526-C52C88626BAE
  42A441D6-AE6A-462b-A84B-4A8CE79027D3
  97C68AE7-15FA-499c-B8C9-5DA81D606E0A
  
  To match the bit format for DWORD2, rearranged enum int3400_thermal_uuid
  and int3400_thermal_uuids[] by swapping current INT3400_THERMAL_ACTIVE
  and INT3400_THERMAL_PASSIVE_1.
  
  If the policies are enumerated via IDSP method then legacy method is
  used, if not the new method is used to update policy support.
  
  Signed-off-by: Srinivas Pandruvada 
  Signed-off-by: Rafael J. Wysocki 

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


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

[Kernel-packages] [Bug 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time

[David Ober]

Following instruction in forwarded email after appling the alsa-ucm-
conf=1.2.2-1ubuntu0.12sutton1 package the rear microphone jack works
correctly

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

Title:
  The rear panel of Lenovo P620 doesn't support more than one audio
  device at the same time

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Confirmed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  After backporting following patches from PA and alsa-ucm-conf and then
  it works.

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355

  https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB-
  Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51]

  Here is the test PPA:
  https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test

  Since the upstream not yet accepted those patches, the regression
  potential may quite high.

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


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

[Kernel-packages] [Bug 1966090] [NEW] Linux 5.4.0-105 breaks Bluetooth and makes system too slow to use

[Julien Villemure]

Public bug reported:

Currently running this kernel which is working fine:

Linux 5.4.0-104-generic #118-Ubuntu SMP Wed Mar 2 19:02:41 UTC 2022
x86_64 x86_64 x86_64 GNU/Linux

Immediately after installing the latest kernel update to Linux 5.4.0-105
and rebooting, Bluetooth stops working and my system becomes too slow to
use.

The following error is printed endlessly to console multiple times per
second by Bluetooth hci:

Malicious advertising data. Stopping processing

I don't have the exact log because my system was unusable beyond reading
the console and I had to force reboot, but that was definitely the
message that was printed.

I had no Bluetooth devices powered on (just my laptop's adapter I
guess).

Reverted to kernel 5.4.0-104 and problems are gone.

See the lspci-vnvn.log but keep in mind that I generated it on the
working 5.4.0-104 kernel, as it was impossible to do anything on
5.4.0-105.

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


** Tags: bluetooth hci kernel

** Attachment added: "Output of lspci -vnvn"
   
https://bugs.launchpad.net/bugs/1966090/+attachment/5572199/+files/lspci-vnvn.log

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

Title:
  Linux 5.4.0-105 breaks Bluetooth and makes system too slow to use

Status in linux package in Ubuntu:
  New

Bug description:
  Currently running this kernel which is working fine:

  Linux 5.4.0-104-generic #118-Ubuntu SMP Wed Mar 2 19:02:41 UTC 2022
  x86_64 x86_64 x86_64 GNU/Linux

  Immediately after installing the latest kernel update to Linux
  5.4.0-105 and rebooting, Bluetooth stops working and my system becomes
  too slow to use.

  The following error is printed endlessly to console multiple times per
  second by Bluetooth hci:

  Malicious advertising data. Stopping processing

  I don't have the exact log because my system was unusable beyond
  reading the console and I had to force reboot, but that was definitely
  the message that was printed.

  I had no Bluetooth devices powered on (just my laptop's adapter I
  guess).

  Reverted to kernel 5.4.0-104 and problems are gone.

  See the lspci-vnvn.log but keep in mind that I generated it on the
  working 5.4.0-104 kernel, as it was impossible to do anything on
  5.4.0-105.

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


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

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

[Ubuntu Kernel Bot]

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

apport-collect 1966089

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

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

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

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

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

Title:
  Update OS policy capability handshake

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  == SRU JAMMY ==

  Update int340x OS policy capability handshake; required for full
  functionality in thermald 2.4.9 to improve functionality for newer
  H/W.

  == The fix ==

  Upstream commit:

  commit c7ff29763989bd09c433f73fae3c1e1c15d9cda4
  Author: Srinivas Pandruvada 
  Date:   Mon Mar 14 15:09:37 2022 -0700

  thermal: int340x: Update OS policy capability handshake
  
  Update the firmware with OS supported policies mask, so that firmware can
  relinquish its internal controls. Without this update several Tiger Lake
  laptops gets performance limited with in few seconds of executing in
  turbo region.
  
  The existing way of enumerating firmware policies via IDSP method and
  selecting policy by directly writing those policy UUIDS via _OSC method
  is not supported in newer generation of hardware.
  
  There is a new UUID "B23BA85D-C8B7-3542-88DE-8DE2FFCFD698" is defined for
  updating policy capabilities. As part of ACPI _OSC method:
  
  Arg0 - UUID: B23BA85D-C8B7-3542-88DE-8DE2FFCFD698
  Arg1 - Rev ID: 1
  Arg2 - Count: 2
  Arg3 - Capability buffers: Array of Arg2 DWORDS
  
  DWORD1: As defined in the ACPI 5.0 Specification
  - Bit 0: Query Flag
  - Bits 1-3: Always 0
  - Bits 4-31: Reserved
  
  DWORD2 and beyond:
  - Bit0: set to 1 to indicate Intel(R) Dynamic Tuning is active, 0 to
  indicate it is disabled and legacy thermal mechanism should
  be enabled.
  - Bit1: set to 1 to indicate Intel(R) Dynamic Tuning is controlling
  active cooling, 0 to indicate bios shall enable legacy thermal
  zone with active trip point.
  - Bit2: set to 1 to indicate Intel(R) Dynamic Tuning is controlling
  passive cooling, 0 to indicate bios shall enable legacy thermal
  zone with passive trip point.
  - Bit3: set to 1 to indicate Intel(R) Dynamic Tuning is handling
  critical trip point, 0 to indicate bios shall enable legacy
  thermal zone with critical trip point.
  - Bits 4:31: Reserved
  
  From sysfs interface, there is an existing interface to update policy
  UUID using attribute "current_uuid". User space can write the same UUID
  for ACTIVE, PASSIVE and CRITICAL policy. Driver converts these UUIDs to
  DWORD2 Bit 1 to Bit 3. When any of the policy is activated by user
  space it is assumed that dynamic tuning is active.
  
  For example
  $cd /sys/bus/platform/devices/INTC1040:00/uuids
  To support active policy
  $echo "3A95C389-E4B8-4629-A526-C52C88626BAE" > current_uuid
  To support passive policy
  $echo "42A441D6-AE6A-462b-A84B-4A8CE79027D3" > current_uuid
  To support critical policy
  $echo "97C68AE7-15FA-499c-B8C9-5DA81D606E0A" > current_uuid
  
  To check all the supported policies
  $cat current_uuid
  3A95C389-E4B8-4629-A526-C52C88626BAE
  42A441D6-AE6A-462b-A84B-4A8CE79027D3
  97C68AE7-15FA-499c-B8C9-5DA81D606E0A
  
  To match the bit format for DWORD2, rearranged enum int3400_thermal_uuid
  and int3400_thermal_uuids[] by swapping current INT3400_THERMAL_ACTIVE
  and INT3400_THERMAL_PASSIVE_1.
  
  If the policies are enumerated via IDSP method then legacy method is
  used, if not the new method is used to update policy support.
  
  Signed-off-by: Srinivas Pandruvada 
  Signed-off-by: Rafael J. Wysocki 

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


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

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

[Ubuntu Kernel Bot]

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

apport-collect 1966090

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

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

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

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

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

Title:
  Linux 5.4.0-105 breaks Bluetooth and makes system too slow to use

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Currently running this kernel which is working fine:

  Linux 5.4.0-104-generic #118-Ubuntu SMP Wed Mar 2 19:02:41 UTC 2022
  x86_64 x86_64 x86_64 GNU/Linux

  Immediately after installing the latest kernel update to Linux
  5.4.0-105 and rebooting, Bluetooth stops working and my system becomes
  too slow to use.

  The following error is printed endlessly to console multiple times per
  second by Bluetooth hci:

  Malicious advertising data. Stopping processing

  I don't have the exact log because my system was unusable beyond
  reading the console and I had to force reboot, but that was definitely
  the message that was printed.

  I had no Bluetooth devices powered on (just my laptop's adapter I
  guess).

  Reverted to kernel 5.4.0-104 and problems are gone.

  See the lspci-vnvn.log but keep in mind that I generated it on the
  working 5.4.0-104 kernel, as it was impossible to do anything on
  5.4.0-105.

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


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

[Kernel-packages] [Bug 1966090] Re: Linux 5.4.0-105 breaks Bluetooth and makes system too slow to use

[Julien Villemure]

apport isn't installed, and installing it would uninstall systemd-
coredump. I am hoping the attached output of `lspci -vnvn` is enough.
Please let me know if it isn't.

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

** Description changed:

  Currently running this kernel which is working fine:
  
  Linux 5.4.0-104-generic #118-Ubuntu SMP Wed Mar 2 19:02:41 UTC 2022
  x86_64 x86_64 x86_64 GNU/Linux
  
  Immediately after installing the latest kernel update to Linux 5.4.0-105
- and rebooting, Bluetooth stops working and my system becomes too slow to
- use.
+ and rebooting, the following error is printed endlessly to console
+ multiple times per second by Bluetooth hci:
  
- The following error is printed endlessly to console multiple times per
- second by Bluetooth hci:
- 
- Malicious advertising data. Stopping processing
+ Malicious advertising data. Stopping processing
  
  I don't have the exact log because my system was unusable beyond reading
  the console and I had to force reboot, but that was definitely the
  message that was printed.
  
- I had no Bluetooth devices powered on (just my laptop's adapter I
- guess).
+ I have no Bluetooth devices powered on when booting (just my laptop's
+ adapter I guess).
+ 
+ The system is also too slow to do anything, I have to force reboot.
  
  Reverted to kernel 5.4.0-104 and problems are gone.
  
  See the lspci-vnvn.log but keep in mind that I generated it on the
  working 5.4.0-104 kernel, as it was impossible to do anything on
  5.4.0-105.

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

Title:
  Linux 5.4.0-105 breaks Bluetooth and makes system too slow to use

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Currently running this kernel which is working fine:

  Linux 5.4.0-104-generic #118-Ubuntu SMP Wed Mar 2 19:02:41 UTC 2022
  x86_64 x86_64 x86_64 GNU/Linux

  Immediately after installing the latest kernel update to Linux
  5.4.0-105 and rebooting, the following error is printed endlessly to
  console multiple times per second by Bluetooth hci:

  Malicious advertising data. Stopping processing

  I don't have the exact log because my system was unusable beyond
  reading the console and I had to force reboot, but that was definitely
  the message that was printed.

  I have no Bluetooth devices powered on when booting (just my laptop's
  adapter I guess).

  The system is also too slow to do anything, I have to force reboot.

  Reverted to kernel 5.4.0-104 and problems are gone.

  See the lspci-vnvn.log but keep in mind that I generated it on the
  working 5.4.0-104 kernel, as it was impossible to do anything on
  5.4.0-105.

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


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

[Kernel-packages] [Bug 1966093] [NEW] Update the 510 UDA NVIDIA driver series in Bionic, Focal, and Impish

[Alberto Milone]

Public bug reported:

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

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

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

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

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

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

[Discussion]

[Changelog]

=== impish/focal/bionic ===

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

** Affects: nvidia-graphics-drivers-510 (Ubuntu)
 Importance: Undecided
 Status: Fix Committed

** Affects: linux-restricted-modules (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: nvidia-graphics-drivers-510 (Ubuntu Bionic)
 Importance: High
 Assignee: Alberto Milone (albertomilone)
 Status: In Progress

** Affects: linux-restricted-modules (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: nvidia-graphics-drivers-510 (Ubuntu Focal)
 Importance: High
 Assignee: Alberto Milone (albertomilone)
 Status: In Progress

** Affects: linux-restricted-modules (Ubuntu Impish)
 Importance: Undecided
 Status: New

** Affects: nvidia-graphics-drivers-510 (Ubuntu Impish)
 Importance: High
 Assignee: Alberto Milone (albertomilone)
 Status: In Progress

** Also affects: nvidia-graphics-drivers-510 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-510 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-510 (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-510 (Ubuntu)
   Status: New => Fix Committed

** Changed in: nvidia-graphics-drivers-510 (Ubuntu Bionic)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-510 (Ubuntu Focal)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-510 (Ubuntu Impish)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-510 (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: nvidia-graphics-drivers-510 (Ubuntu Focal)
   Status: New => In Progress

** Changed in: nvidia-graphics-drivers-510 (Ubuntu Impish)
   Status: New => In Progress

** Changed in: nvidia-graphics-drivers-510 (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: nvidia-graphics-drivers-510 (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: nvidia-graphics-drivers-510 (Ubuntu Impish)
   Importance: Undecided => High

** Also affects: linux-restricted-modules (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 in Ubuntu.
https://bugs.launchpad.net/bugs/1966093

Title:
  Update the 510 UDA NVIDIA driver series in Bionic, Focal, and Impish

Status in linux-restricted-modules package in Ubuntu:
  New
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Fix Committed
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-510 source package in Bionic:
  In Progress
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-510 source package in Focal:
  In Progress
Status in linux-restricted-modules source package in Impish:
  New
Status in nvidia-graphics-drivers-510 source package in Impish:
  In Progress

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

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

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

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

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

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

[Kernel-packages] [Bug 1966093] Re: Update the 510 UDA NVIDIA driver series in Bionic, Focal, and Impish

[Alberto Milone]

** Description changed:

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.
  
  See the changelog entry below for a full list of changes and bugs.
  
  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates
  
  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu
  
  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.
  
  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.
  
  [Discussion]
  
  [Changelog]
  
  === impish/focal/bionic ===
+ 
+   * New upstream release (LP: #1966093):
+ - Added support for the following GPUs:
+ NVIDIA RTX A4000H
+ NVIDIA RTX A5500
+ - Fixed a bug that could cause displays with HDMI or DisplayPort
+   audio to be deselected as the default audio output device after
+   resuming from suspend.
+ - Fixed a regression that could cause OpenGL applications to hang
+   or render incorrectly after suspend/resume cycles or VT-
+   switches
+ - Fixed a bug, introduced in 495.29.05, that caused GPU "Model:"
+   in /proc/driver/nvidia/gpus//information
+   to be "Unknown" for some GPUs.

** Summary changed:

- Update the 510 UDA NVIDIA driver series in Bionic, Focal, and Impish
+ Update to the 510.60.02 UDA NVIDIA driver series in Bionic, Focal, and Impish

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

** Changed in: linux-restricted-modules (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: linux-restricted-modules (Ubuntu Focal)
   Status: New => Triaged

** Changed in: linux-restricted-modules (Ubuntu Impish)
   Status: New => Triaged

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

** Changed in: linux-restricted-modules (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: linux-restricted-modules (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: linux-restricted-modules (Ubuntu Impish)
   Importance: Undecided => High

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

Title:
  Update to the 510.60.02 UDA NVIDIA driver series in Bionic, Focal, and
  Impish

Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Fix Committed
Status in linux-restricted-modules source package in Bionic:
  Triaged
Status in nvidia-graphics-drivers-510 source package in Bionic:
  In Progress
Status in linux-restricted-modules source package in Focal:
  Triaged
Status in nvidia-graphics-drivers-510 source package in Focal:
  In Progress
Status in linux-restricted-modules source package in Impish:
  Triaged
Status in nvidia-graphics-drivers-510 source package in Impish:
  In Progress

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

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

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

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

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

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

  [Discussion]

  [Changelog]

  === impish/focal/bionic ===

* New upstream release (LP: #1966093):
  - Added support for the following GPUs:
  NVIDIA RTX A4000H
  NVIDIA RTX A5500
  - Fixed a bug that could cause displays with HDMI or DisplayPort
audio to be deselected as the default audio output device after
resuming from suspend.
  - Fixed a regression that could cause OpenGL applications to hang
or render incorrectly after suspend/resume cycles or VT-
switches
  - Fixed a bug, introduced in 495.29.05, that caused GPU "Model:"
in /proc/driver/nvidia/gpus//information
to be "Unknown" for some GPUs.

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

[Kernel-packages] [Bug 1962578] Re: [UBUNTU 20.04] Fix SIGP processing on KVM/s390

[bugproxy]

--- Comment From far...@us.ibm.com 2022-03-23 11:42 EDT---
Verified with the assistance of kvm-unit-tests patches described here:
https://lore.kernel.org/r/20220311173822.1234617-1-far...@linux.ibm.com/

...and further examination of the s390dbf/kvm- contents for a
running guest. Rolled back the kernel version on each release to ensure
I had a "bad" state, as well as the version in -proposed. Everything
behaves as I expected. THANK YOU!

Tested Focal:
5.4.0-100.113 (FAILS)
5.4.0-106.120 (WORKS)

Tested Impish:
5.13.0-30.33 (FAILS)
5.13.0-38.43 (WORKS)

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

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

Title:
  [UBUNTU 20.04] Fix SIGP processing on KVM/s390

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Impish:
  Fix Committed

Bug description:
  SRU Justification:
  ==

  [Impact]

  * The SIGP processing on KVM/s390x is incorrect and not fully conform to
    the 'Principles of Operations', the IBM Z architecture definition
    and documentation.

  * KVM: SIGP RESTART is reporting a CPU state 'stopped' after SIGP RESTART
    was issued, while it should report a 'busy' condition until the CPU is
    really started.

  * The fix for this consists of three patches:
    812de04661c4 "KVM: s390: Clarify SIGP orders versus STOP/RESTART"
    435d17955519 "KVM: s390: Add a routine for setting userspace CPU state"
    4563bcad46bf "KVM: s390: Simplify SIGP Set Arch handling"
    whereas 812de04661c4 already landed via upstream stable,
    hence only two are left and need to be cherry-picked:

  [Fix]

  * 67cf68b6a5ccac8bc7dfef0a220b59af4c83fd2c 67cf68b6a5cc "KVM: s390:
  Add a routine for setting userspace CPU state"

  * 8eeba194a32e0f50329354a696baaa2e3d9accc5 8eeba194a32e "KVM: s390:
  Simplify SIGP Set Arch handling"

  [Test Case]

  * Install an LPAR on IBM Z (z13+) or LinuxONE (Emperor / Rockhopper)
    with Ubuntu Server 20.04 using kernel standard kernel 5.4.

  * Setup this LPAR as QEMU/KVM host and a focal VM as guest.

  * The test itself is the following unit test:
    https://lore.kernel.org/r/20220303210425.1693486-1-far...@linux.ibm.com/

  * The test and verification will be done by the IBM Z team.

  [Where problems could occur]

  * A broken patch could harm KVM ioctl on s390x or the (virtual) CPU
    state control in general.

  * The SIGP handing (on s390x) can become broken, which could lead to
    incorrect (virtual) CPU states.

  * In worst case KVM can become broken on s390x entirely.

  * The modified code is all s390x specific QEMU/KVM code,
    no common code is touched.

  [Other]

  * The two remaining patches are upstream since 5.16,
    the first one already landed in 5.4 via upstream stable bug LP#1959701
    and in 5.13 via upstream stable bug LP#1960861.

  * The patches already landed in jammy (master-next) based on LP#1959735,
    hence only SRU to impish and focal is needed.

  * This patches got discussed here:
    https://lore.kernel.org/all/20211008203112.1979843-2-far...@linux.ibm.com/

  * This not only fixes the SIGP processing, but is also important in terms of
    long term maintainability.

  __

  Description:
     KVM: SIGP RESTART is reporting a CPU state 'stopped' after SIGP RESTART 
was issued, while it should report a 'busy' condition until the CPU is really 
started.

   The patches to fix this have already been picked for jammy/master-
  next:

  812de04661c4 "KVM: s390: Clarify SIGP orders versus STOP/RESTART"
  435d17955519 "KVM: s390: Add a routine for setting userspace CPU state"
  4563bcad46bf "KVM: s390: Simplify SIGP Set Arch handling"

   For Ubuntu 20.04 the focal/master-next already contains:
  d74b0d2d38d3 KVM: s390: Clarify SIGP orders versus STOP/RESTART

   so we additionally need the following two upstream commits in focal
  67cf68b6a5cc KVM: s390: Add a routine for setting userspace CPU state
  8eeba194a32e KVM: s390: Simplify SIGP Set Arch handling

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1962578/+subscriptions


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

[Kernel-packages] [Bug 1966098] [NEW] linux-azure: arm64 network performance improvement

[Tim Gardner]

Public bug reported:

SRU Justification

[Impact]

The Microsoft validation team found the issue on arm64 Hyperv where
server throughput was reduced by < 50%.

[Fix]

https://lore.kernel.org/lkml/1647533563-2170-1-git-send-email-
mikel...@microsoft.com/T/#t

[Where things could go wrong]

Network performance could get worse, or data could be corrupted.

[Other Info]

SF: #00310705

** Affects: linux-azure (Ubuntu)
 Importance: Medium
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress

** Affects: linux-azure (Ubuntu Impish)
 Importance: Medium
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress

** Affects: linux-azure (Ubuntu Jammy)
 Importance: Medium
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress

** Description changed:

  SRU Justification
  
  [Impact]
  
- The Microsoft validation team found the issue on arm64 Hyperv where server 
throughput was
- reduced by < 50%.
+ The Microsoft validation team found the issue on arm64 Hyperv where
+ server throughput was reduced by < 50%.
  
  [Fix]
  
  https://lore.kernel.org/lkml/1647533563-2170-1-git-send-email-
  mikel...@microsoft.com/T/#t
  
  [Where things could go wrong]
  
  Network performance could get worse, or data could be corrupted.
  
  [Other Info]
  
  SF: #00310705

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

Title:
  linux-azure: arm64 network performance improvement

Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-azure source package in Impish:
  In Progress
Status in linux-azure source package in Jammy:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  The Microsoft validation team found the issue on arm64 Hyperv where
  server throughput was reduced by < 50%.

  [Fix]

  https://lore.kernel.org/lkml/1647533563-2170-1-git-send-email-
  mikel...@microsoft.com/T/#t

  [Where things could go wrong]

  Network performance could get worse, or data could be corrupted.

  [Other Info]

  SF: #00310705

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


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

[Kernel-packages] [Bug 1965968] Re: post jammy update, black/flickering screen on boot

[Joe Barnett]

v5.14: black screen
v5.13: black screen with i915.enable_psr=0, works without

went back and tried the initial 5.13.0-35 as well, and it also does the
black screen with i915.enable_psr=0


will try to find the first mainline 5.13 that doesn't work today (or if they 
all 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/1965968

Title:
  post jammy update, black/flickering screen on boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After initial jammy upgrade things were working fine, but after a
  recent update the machine boots to a blank screen.  There are
  occasional purplish flickers that seem to correspond with keypresses,
  but even blindly typing the encrypted disk password doesn't appear to
  advance the boot process to gdm.

  Plugging in an external monitor does fix the issue and allow boot to
  proceed, but obviously doesn't help if not near an external monitor.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: plymouth 0.9.5+git20211018-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Tue Mar 22 09:22:26 2022
  DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
  InstallationDate: Installed on 2019-08-17 (948 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  MachineType: Dell Inc. XPS 15 9575
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic 
root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic 
root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7
  SourcePackage: plymouth
  TextPlymouth: 
/usr/share/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth
  UpgradeStatus: Upgraded to jammy on 2022-03-18 (3 days ago)
  dmi.bios.date: 03/25/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.1
  dmi.board.name: 0N338G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1966098] Re: linux-azure: arm64 network performance improvement

[Tim Gardner]

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

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

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

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

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

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

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

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

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

Title:
  linux-azure: arm64 network performance improvement

Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-azure source package in Impish:
  In Progress
Status in linux-azure source package in Jammy:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  The Microsoft validation team found the issue on arm64 Hyperv where
  server throughput was reduced by < 50%.

  [Fix]

  https://lore.kernel.org/lkml/1647533563-2170-1-git-send-email-
  mikel...@microsoft.com/T/#t

  [Where things could go wrong]

  Network performance could get worse, or data could be corrupted.

  [Other Info]

  SF: #00310705

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


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

[Kernel-packages] [Bug 1845797]

[csights]

(In reply to Josh from comment #29)

If you could git bisect the kernel and find out which commit breaks
between 5.16.11 and 5.16.13 you might get some attention and keep the
gains.

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

Title:
  Microphone not detected Lenovo Yoga S940

Status in Linux:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo
  Yoga S940

  Attached the screen of gnome sound control panel.

  Inxi output:

  System:Host:  Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: 
Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) 
  Machine:   Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga 
S940-14IWL serial:  
 Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial:  UEFI: LENOVO v: AKCN34WW date: 06/12/2019 
  CPU:   Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT 
MCP L2 cache: 8192 KiB 
 Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 
2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 
 8: 2229 
  Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: 
snd_hda_intel 
 Sound Server: ALSA v: k5.3.0-13-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniele2239 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-12 (17 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81Q7
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-13-generic N/A
   linux-backports-modules-5.3.0-13-generic  N/A
   linux-firmware1.182
  Tags:  eoan
  Uname: Linux 5.3.0-13-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-21 (8 days ago)
  UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AKCN34WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga S940-14IWL
  dmi.modalias: 
dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL:
  dmi.product.family: Yoga S940-14IWL
  dmi.product.name: 81Q7
  dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL
  dmi.product.version: Lenovo Yoga S940-14IWL
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1845797]

[freedman.joshua]

5.16.11 works, is there a reason you said to bisect between 5.16.11 and
5.16.13 and not 5.16.12?

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

Title:
  Microphone not detected Lenovo Yoga S940

Status in Linux:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo
  Yoga S940

  Attached the screen of gnome sound control panel.

  Inxi output:

  System:Host:  Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: 
Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) 
  Machine:   Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga 
S940-14IWL serial:  
 Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial:  UEFI: LENOVO v: AKCN34WW date: 06/12/2019 
  CPU:   Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT 
MCP L2 cache: 8192 KiB 
 Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 
2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 
 8: 2229 
  Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: 
snd_hda_intel 
 Sound Server: ALSA v: k5.3.0-13-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniele2239 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-12 (17 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81Q7
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-13-generic N/A
   linux-backports-modules-5.3.0-13-generic  N/A
   linux-firmware1.182
  Tags:  eoan
  Uname: Linux 5.3.0-13-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-21 (8 days ago)
  UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AKCN34WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga S940-14IWL
  dmi.modalias: 
dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL:
  dmi.product.family: Yoga S940-14IWL
  dmi.product.name: 81Q7
  dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL
  dmi.product.version: Lenovo Yoga S940-14IWL
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1845797]

[freedman.joshua]

Ahh, because I said 5.16.13 didn't work; sorry ;p

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

Title:
  Microphone not detected Lenovo Yoga S940

Status in Linux:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo
  Yoga S940

  Attached the screen of gnome sound control panel.

  Inxi output:

  System:Host:  Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: 
Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) 
  Machine:   Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga 
S940-14IWL serial:  
 Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial:  UEFI: LENOVO v: AKCN34WW date: 06/12/2019 
  CPU:   Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT 
MCP L2 cache: 8192 KiB 
 Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 
2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 
 8: 2229 
  Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: 
snd_hda_intel 
 Sound Server: ALSA v: k5.3.0-13-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniele2239 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-12 (17 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81Q7
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-13-generic N/A
   linux-backports-modules-5.3.0-13-generic  N/A
   linux-firmware1.182
  Tags:  eoan
  Uname: Linux 5.3.0-13-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-21 (8 days ago)
  UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AKCN34WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga S940-14IWL
  dmi.modalias: 
dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL:
  dmi.product.family: Yoga S940-14IWL
  dmi.product.name: 81Q7
  dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL
  dmi.product.version: Lenovo Yoga S940-14IWL
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1845797]

[freedman.joshua]

(In reply to C Sights from comment #30)
> (In reply to Josh from comment #29)
> 
> If you could git bisect the kernel and find out which commit breaks between
> 5.16.11 and 5.16.13 you might get some attention and keep the gains.

Ok, so 5.16.11 is good, 5.16.12 is bad.  I looked at the git bisect
tool, but I don't know enough to say what commits are relevant and or
bad/good.

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

Title:
  Microphone not detected Lenovo Yoga S940

Status in Linux:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo
  Yoga S940

  Attached the screen of gnome sound control panel.

  Inxi output:

  System:Host:  Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: 
Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) 
  Machine:   Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga 
S940-14IWL serial:  
 Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial:  UEFI: LENOVO v: AKCN34WW date: 06/12/2019 
  CPU:   Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT 
MCP L2 cache: 8192 KiB 
 Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 
2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 
 8: 2229 
  Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: 
snd_hda_intel 
 Sound Server: ALSA v: k5.3.0-13-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniele2239 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-12 (17 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81Q7
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-13-generic N/A
   linux-backports-modules-5.3.0-13-generic  N/A
   linux-firmware1.182
  Tags:  eoan
  Uname: Linux 5.3.0-13-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-21 (8 days ago)
  UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AKCN34WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga S940-14IWL
  dmi.modalias: 
dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL:
  dmi.product.family: Yoga S940-14IWL
  dmi.product.name: 81Q7
  dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL
  dmi.product.version: Lenovo Yoga S940-14IWL
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1966089] Re: Update OS policy capability handshake

[Colin Ian King]

See: https://lists.ubuntu.com/archives/kernel-
team/2022-March/128871.html

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

Title:
  Update OS policy capability handshake

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  == SRU JAMMY ==

  Update int340x OS policy capability handshake; required for full
  functionality in thermald 2.4.9 to improve functionality for newer
  H/W.

  == The fix ==

  Upstream commit:

  commit c7ff29763989bd09c433f73fae3c1e1c15d9cda4
  Author: Srinivas Pandruvada 
  Date:   Mon Mar 14 15:09:37 2022 -0700

  thermal: int340x: Update OS policy capability handshake
  
  Update the firmware with OS supported policies mask, so that firmware can
  relinquish its internal controls. Without this update several Tiger Lake
  laptops gets performance limited with in few seconds of executing in
  turbo region.
  
  The existing way of enumerating firmware policies via IDSP method and
  selecting policy by directly writing those policy UUIDS via _OSC method
  is not supported in newer generation of hardware.
  
  There is a new UUID "B23BA85D-C8B7-3542-88DE-8DE2FFCFD698" is defined for
  updating policy capabilities. As part of ACPI _OSC method:
  
  Arg0 - UUID: B23BA85D-C8B7-3542-88DE-8DE2FFCFD698
  Arg1 - Rev ID: 1
  Arg2 - Count: 2
  Arg3 - Capability buffers: Array of Arg2 DWORDS
  
  DWORD1: As defined in the ACPI 5.0 Specification
  - Bit 0: Query Flag
  - Bits 1-3: Always 0
  - Bits 4-31: Reserved
  
  DWORD2 and beyond:
  - Bit0: set to 1 to indicate Intel(R) Dynamic Tuning is active, 0 to
  indicate it is disabled and legacy thermal mechanism should
  be enabled.
  - Bit1: set to 1 to indicate Intel(R) Dynamic Tuning is controlling
  active cooling, 0 to indicate bios shall enable legacy thermal
  zone with active trip point.
  - Bit2: set to 1 to indicate Intel(R) Dynamic Tuning is controlling
  passive cooling, 0 to indicate bios shall enable legacy thermal
  zone with passive trip point.
  - Bit3: set to 1 to indicate Intel(R) Dynamic Tuning is handling
  critical trip point, 0 to indicate bios shall enable legacy
  thermal zone with critical trip point.
  - Bits 4:31: Reserved
  
  From sysfs interface, there is an existing interface to update policy
  UUID using attribute "current_uuid". User space can write the same UUID
  for ACTIVE, PASSIVE and CRITICAL policy. Driver converts these UUIDs to
  DWORD2 Bit 1 to Bit 3. When any of the policy is activated by user
  space it is assumed that dynamic tuning is active.
  
  For example
  $cd /sys/bus/platform/devices/INTC1040:00/uuids
  To support active policy
  $echo "3A95C389-E4B8-4629-A526-C52C88626BAE" > current_uuid
  To support passive policy
  $echo "42A441D6-AE6A-462b-A84B-4A8CE79027D3" > current_uuid
  To support critical policy
  $echo "97C68AE7-15FA-499c-B8C9-5DA81D606E0A" > current_uuid
  
  To check all the supported policies
  $cat current_uuid
  3A95C389-E4B8-4629-A526-C52C88626BAE
  42A441D6-AE6A-462b-A84B-4A8CE79027D3
  97C68AE7-15FA-499c-B8C9-5DA81D606E0A
  
  To match the bit format for DWORD2, rearranged enum int3400_thermal_uuid
  and int3400_thermal_uuids[] by swapping current INT3400_THERMAL_ACTIVE
  and INT3400_THERMAL_PASSIVE_1.
  
  If the policies are enumerated via IDSP method then legacy method is
  used, if not the new method is used to update policy support.
  
  Signed-off-by: Srinivas Pandruvada 
  Signed-off-by: Rafael J. Wysocki 

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


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

[Kernel-packages] [Bug 1966098] Re: linux-azure: arm64 network performance improvement

[Tim Gardner]

Patches submitted: https://lists.ubuntu.com/archives/kernel-
team/2022-March/128873.html

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

Title:
  linux-azure: arm64 network performance improvement

Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-azure source package in Impish:
  In Progress
Status in linux-azure source package in Jammy:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  The Microsoft validation team found the issue on arm64 Hyperv where
  server throughput was reduced by < 50%.

  [Fix]

  https://lore.kernel.org/lkml/1647533563-2170-1-git-send-email-
  mikel...@microsoft.com/T/#t

  [Where things could go wrong]

  Network performance could get worse, or data could be corrupted.

  [Other Info]

  SF: #00310705

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


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

[Kernel-packages] [Bug 1962578] Re: [UBUNTU 20.04] Fix SIGP processing on KVM/s390

[Frank Heimes]

Thank you Eric for the verifications!

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

Title:
  [UBUNTU 20.04] Fix SIGP processing on KVM/s390

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Impish:
  Fix Committed

Bug description:
  SRU Justification:
  ==

  [Impact]

  * The SIGP processing on KVM/s390x is incorrect and not fully conform to
    the 'Principles of Operations', the IBM Z architecture definition
    and documentation.

  * KVM: SIGP RESTART is reporting a CPU state 'stopped' after SIGP RESTART
    was issued, while it should report a 'busy' condition until the CPU is
    really started.

  * The fix for this consists of three patches:
    812de04661c4 "KVM: s390: Clarify SIGP orders versus STOP/RESTART"
    435d17955519 "KVM: s390: Add a routine for setting userspace CPU state"
    4563bcad46bf "KVM: s390: Simplify SIGP Set Arch handling"
    whereas 812de04661c4 already landed via upstream stable,
    hence only two are left and need to be cherry-picked:

  [Fix]

  * 67cf68b6a5ccac8bc7dfef0a220b59af4c83fd2c 67cf68b6a5cc "KVM: s390:
  Add a routine for setting userspace CPU state"

  * 8eeba194a32e0f50329354a696baaa2e3d9accc5 8eeba194a32e "KVM: s390:
  Simplify SIGP Set Arch handling"

  [Test Case]

  * Install an LPAR on IBM Z (z13+) or LinuxONE (Emperor / Rockhopper)
    with Ubuntu Server 20.04 using kernel standard kernel 5.4.

  * Setup this LPAR as QEMU/KVM host and a focal VM as guest.

  * The test itself is the following unit test:
    https://lore.kernel.org/r/20220303210425.1693486-1-far...@linux.ibm.com/

  * The test and verification will be done by the IBM Z team.

  [Where problems could occur]

  * A broken patch could harm KVM ioctl on s390x or the (virtual) CPU
    state control in general.

  * The SIGP handing (on s390x) can become broken, which could lead to
    incorrect (virtual) CPU states.

  * In worst case KVM can become broken on s390x entirely.

  * The modified code is all s390x specific QEMU/KVM code,
    no common code is touched.

  [Other]

  * The two remaining patches are upstream since 5.16,
    the first one already landed in 5.4 via upstream stable bug LP#1959701
    and in 5.13 via upstream stable bug LP#1960861.

  * The patches already landed in jammy (master-next) based on LP#1959735,
    hence only SRU to impish and focal is needed.

  * This patches got discussed here:
    https://lore.kernel.org/all/20211008203112.1979843-2-far...@linux.ibm.com/

  * This not only fixes the SIGP processing, but is also important in terms of
    long term maintainability.

  __

  Description:
     KVM: SIGP RESTART is reporting a CPU state 'stopped' after SIGP RESTART 
was issued, while it should report a 'busy' condition until the CPU is really 
started.

   The patches to fix this have already been picked for jammy/master-
  next:

  812de04661c4 "KVM: s390: Clarify SIGP orders versus STOP/RESTART"
  435d17955519 "KVM: s390: Add a routine for setting userspace CPU state"
  4563bcad46bf "KVM: s390: Simplify SIGP Set Arch handling"

   For Ubuntu 20.04 the focal/master-next already contains:
  d74b0d2d38d3 KVM: s390: Clarify SIGP orders versus STOP/RESTART

   so we additionally need the following two upstream commits in focal
  67cf68b6a5cc KVM: s390: Add a routine for setting userspace CPU state
  8eeba194a32e KVM: s390: Simplify SIGP Set Arch handling

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1962578/+subscriptions


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

[Kernel-packages] [Bug 1961996] Re: Webcams no longer have correct names

[Dave Musicant]

This has now been fixed with kernel 5.13.0-37.

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

Title:
  Webcams no longer have correct names

Status in linux-signed-hwe-5.13 package in Ubuntu:
  New

Bug description:
  I've got two webcams: one of them is built in to my Lenovo T14s
  (running Ubuntu 20.04.4), and the other is an external USB device.
  They used to have obvious names: one was called something like
  "Integrated Camera C" and the other was called something like
  "HuddleCamHD". Strangely, they have both been renamed to be "Video
  Capture 4", which means I can't easily distinguish between them when
  switching cameras in tools such as Zoom or OBS Studio. Here's some
  output showing this:

  $ v4l2-ctl --list-devices  
  Video Capture 4 (usb-:00:14.0-5.2.3):
  /dev/video2
  /dev/video3

  Video Capture 4 (usb-:00:14.0-8):
  /dev/video0
  /dev/video1

  Likewise, I'm seeing precisely the same issue on my desktop computer,
  which is also running Ubuntu 20.04.04:

  Video Capture 4 (usb-:00:14.0-3.4.3):
  /dev/video0
  /dev/video1

  I'm running kernel version 5.13.0-30. This error first occurs with
  kernel version 5.13.0-28. If I boot with an earlier version, it
  detects the webcam names just fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 23 07:09:46 2022
  InstallationDate: Installed on 2020-05-08 (655 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1961996/+subscriptions


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

[Kernel-packages] [Bug 1965968] Re: post jammy update, black/flickering screen on boot

[Joe Barnett]

based on previous comment no longer testing with i915.enable_psr=0, but
here's what i've narrowed it down to:

v5.13.19: works
v5.14.0rc2: black screen

looks like the v5.14.0rc1 build failed so can't test that?

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

Title:
  post jammy update, black/flickering screen on boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After initial jammy upgrade things were working fine, but after a
  recent update the machine boots to a blank screen.  There are
  occasional purplish flickers that seem to correspond with keypresses,
  but even blindly typing the encrypted disk password doesn't appear to
  advance the boot process to gdm.

  Plugging in an external monitor does fix the issue and allow boot to
  proceed, but obviously doesn't help if not near an external monitor.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: plymouth 0.9.5+git20211018-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Tue Mar 22 09:22:26 2022
  DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
  InstallationDate: Installed on 2019-08-17 (948 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  MachineType: Dell Inc. XPS 15 9575
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic 
root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic 
root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7
  SourcePackage: plymouth
  TextPlymouth: 
/usr/share/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth
  UpgradeStatus: Upgraded to jammy on 2022-03-18 (3 days ago)
  dmi.bios.date: 03/25/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.1
  dmi.board.name: 0N338G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1966107] [NEW] Tourchpad not working

[Tania Machado]

Public bug reported:

Touchpad not working ~/devices

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-105-generic 5.4.0-105.119
ProcVersionSignature: Ubuntu 5.4.0-105.119-generic 5.4.174
Uname: Linux 5.4.0-105-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tygomes26   2407 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 23 16:50:05 2022
HibernationDevice: RESUME=UUID=a7628af0-e7f9-4692-a926-32fc0d5c138e
InstallationDate: Installed on 2019-09-16 (919 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 003: ID 13d3:56c1 IMC Networks USB2.0 HD UVC WebCam
 Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X530FN_S530FN
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-105-generic 
root=UUID=c205ef0b-8571-494f-933e-ac1fe9f40f2e ro recovery nomodeset 
dis_ucode_ldr
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-105-generic N/A
 linux-backports-modules-5.4.0-105-generic  N/A
 linux-firmware 1.187.11
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/30/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X530FN.305
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X530FN
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX530FN.305:bd05/30/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX530FN_S530FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX530FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: VivoBook
dmi.product.name: VivoBook_ASUSLaptop X530FN_S530FN
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug focal

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

Title:
  Tourchpad not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad not working ~/devices

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-105-generic 5.4.0-105.119
  ProcVersionSignature: Ubuntu 5.4.0-105.119-generic 5.4.174
  Uname: Linux 5.4.0-105-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tygomes26   2407 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 16:50:05 2022
  HibernationDevice: RESUME=UUID=a7628af0-e7f9-4692-a926-32fc0d5c138e
  InstallationDate: Installed on 2019-09-16 (919 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 13d3:56c1 IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X530FN_S530FN
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-105-generic 
root=UUID=c205ef0b-8571-494f-933e-ac1fe9f40f2e ro recovery nomodeset 
dis_ucode_ldr
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-105-generic N/A
   linux-backports-modules-5.4.0-105-generic  N/A
   linux-firmware 1.187.11
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X530FN.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X530FN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX530FN.305:bd05/30/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX530FN_S530FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX530FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X530FN_S530FN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Tourchpad not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad not working ~/devices

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-105-generic 5.4.0-105.119
  ProcVersionSignature: Ubuntu 5.4.0-105.119-generic 5.4.174
  Uname: Linux 5.4.0-105-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tygomes26   2407 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 16:50:05 2022
  HibernationDevice: RESUME=UUID=a7628af0-e7f9-4692-a926-32fc0d5c138e
  InstallationDate: Installed on 2019-09-16 (919 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 13d3:56c1 IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X530FN_S530FN
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-105-generic 
root=UUID=c205ef0b-8571-494f-933e-ac1fe9f40f2e ro recovery nomodeset 
dis_ucode_ldr
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-105-generic N/A
   linux-backports-modules-5.4.0-105-generic  N/A
   linux-firmware 1.187.11
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X530FN.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X530FN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX530FN.305:bd05/30/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX530FN_S530FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX530FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X530FN_S530FN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 1966107] Re: Touchpad not working

[Simon Déziel]

** Summary changed:

- Tourchpad not working
+ Touchpad not working

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

Title:
  Touchpad not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad not working ~/devices

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-105-generic 5.4.0-105.119
  ProcVersionSignature: Ubuntu 5.4.0-105.119-generic 5.4.174
  Uname: Linux 5.4.0-105-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tygomes26   2407 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 16:50:05 2022
  HibernationDevice: RESUME=UUID=a7628af0-e7f9-4692-a926-32fc0d5c138e
  InstallationDate: Installed on 2019-09-16 (919 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 13d3:56c1 IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X530FN_S530FN
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-105-generic 
root=UUID=c205ef0b-8571-494f-933e-ac1fe9f40f2e ro recovery nomodeset 
dis_ucode_ldr
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-105-generic N/A
   linux-backports-modules-5.4.0-105-generic  N/A
   linux-firmware 1.187.11
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X530FN.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X530FN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX530FN.305:bd05/30/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX530FN_S530FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX530FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X530FN_S530FN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 1966118] [NEW] Focal update: v5.4.180 upstream stable release

[Kamal Mostafa]

Public bug reported:

SRU Justification

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

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

integrity: check the return value of audit_log_start()
ima: Remove ima_policy file before directory
ima: Allow template selection with ima_template[_fmt]= after ima_hash=
ima: Do not print policy rule with inactive LSM labels
mmc: sdhci-of-esdhc: Check for error num after setting mask
net: phy: marvell: Fix RGMII Tx/Rx delays setting in 88e1121-compatible PHYs
net: phy: marvell: Fix MDI-x polarity setting in 88e1118-compatible PHYs
NFS: Fix initialisation of nfs_client cl_flags field
NFSD: Clamp WRITE offsets
NFSD: Fix offset type in I/O trace points
NFSv4 only print the label when its queried
nfs: nfs4clinet: check the return value of kstrdup()
NFSv4.1: Fix uninitialised variable in devicenotify
NFSv4 remove zero number of fs_locations entries error check
NFSv4 expose nfs_parse_server_name function
drm: panel-orientation-quirks: Add quirk for the 1Netbook OneXPlayer
net: sched: Clarify error message when qdisc kind is unknown
scsi: target: iscsi: Make sure the np under each tpg is unique
scsi: qedf: Fix refcount issue when LOGO is received during TMF
scsi: myrs: Fix crash in error case
PM: hibernate: Remove register_nosave_region_late()
usb: dwc2: gadget: don't try to disable ep0 in dwc2_hsotg_suspend
net: stmmac: dwmac-sun8i: use return val of readl_poll_timeout()
KVM: nVMX: eVMCS: Filter out VM_EXIT_SAVE_VMX_PREEMPTION_TIMER
riscv: fix build with binutils 2.38
ARM: dts: imx23-evk: Remove MX23_PAD_SSP1_DETECT from hog group
ARM: socfpga: fix missing RESET_CONTROLLER
nvme-tcp: fix bogus request completion when failing to send AER
ACPI/IORT: Check node revision for PMCG resources
PM: s2idle: ACPI: Fix wakeup interrupts handling
net: bridge: fix stale eth hdr pointer in br_dev_xmit
perf probe: Fix ppc64 'perf probe add events failed' case
ARM: dts: meson: Fix the UART compatible strings
staging: fbtft: Fix error path in fbtft_driver_module_init()
ARM: dts: imx6qdl-udoo: Properly describe the SD card detect
usb: f_fs: Fix use-after-free for epfile
misc: fastrpc: avoid double fput() on failed usercopy
ixgbevf: Require large buffers for build_skb on 82599VF
bonding: pair enable_port with slave_arr_updates
ipmr,ip6mr: acquire RTNL before calling ip[6]mr_free_table() on failure path
nfp: flower: fix ida_idx not being released
net: do not keep the dst cache when uncloning an skb dst and its metadata
net: fix a memleak when uncloning an skb dst and its metadata
veth: fix races around rq->rx_notify_masked
net: mdio: aspeed: Add missing MODULE_DEVICE_TABLE
tipc: rate limit warning for received illegal binding update
net: amd-xgbe: disable interrupts during pci removal
vt_ioctl: fix array_index_nospec in vt_setactivate
vt_ioctl: add array_index_nospec to VT_ACTIVATE
n_tty: wake up poll(POLLRDNORM) on receiving data
eeprom: ee1004: limit i2c reads to I2C_SMBUS_BLOCK_MAX
net: usb: ax88179_178a: Fix out-of-bounds accesses in RX fixup
usb: ulpi: Move of_node_put to ulpi_dev_release
usb: ulpi: Call of_node_put correctly
usb: dwc3: gadget: Prevent core from processing stale TRBs
usb: gadget: udc: renesas_usb3: Fix host to USB_ROLE_NONE transition
USB: gadget: validate interface OS descriptor requests
usb: gadget: rndis: check size of RNDIS_MSG_SET command
usb: gadget: f_uac2: Define specific wTerminalType
USB: serial: ftdi_sio: add support for Brainboxes US-159/235/320
USB: serial: option: add ZTE MF286D modem
USB: serial: ch341: add support for GW Instek USB2.0-Serial devices
USB: serial: cp210x: add NCR Retail IO box id
USB: serial: cp210x: add CPI Bulk Coin Recycler id
seccomp: Invalidate seccomp mode to catch death failures
hwmon: (dell-smm) Speed up setting of fan speed
scsi: lpfc: Remove NVMe support if kernel has NVME_FC disabled
perf: Fix list corruption in perf_cgroup_switch()
Linux 5.4.180
UBUNTU: upstream stable to v5.4.180

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

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


** Tags: kernel-stable-tracking-bug

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

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

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

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

[Kernel-packages] [Bug 1966066] Re: audio from external sound card is distorted

[Johan Mattsson]

Hi. I think this happens for me as well. I just want to add that I only
get audio from my left channel. Things sound good with other cards and
the same card on other operating systems.

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

Title:
  audio from external sound card is distorted

Status in linux-signed-hwe-5.13 package in Ubuntu:
  Confirmed

Bug description:
  The sound card is a Focusrite Scarlett 2i2.

  The sound is distorted everywhere.

  Sound via HDMI works.

  Seen others having the same problem:
  https://askubuntu.com/questions/138284/how-to-downgrade-a-package-via-
  apt-get

  ubuntu release: Ubuntu 20.04.4 LTS
  package name involved in bug: linux-image-5.13.0-37-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 12:56:02 2022
  InstallationDate: Installed on 2020-12-18 (459 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1966066/+subscriptions


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

[Kernel-packages] [Bug 1966098] Re: linux-azure: arm64 network performance improvement

[Tim Gardner]

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

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

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

Title:
  linux-azure: arm64 network performance improvement

Status in linux-azure package in Ubuntu:
  Fix Committed
Status in linux-azure source package in Impish:
  Fix Committed
Status in linux-azure source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  The Microsoft validation team found the issue on arm64 Hyperv where
  server throughput was reduced by < 50%.

  [Fix]

  https://lore.kernel.org/lkml/1647533563-2170-1-git-send-email-
  mikel...@microsoft.com/T/#t

  [Where things could go wrong]

  Network performance could get worse, or data could be corrupted.

  [Other Info]

  SF: #00310705

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


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

[Kernel-packages] [Bug 1955916] Re: Bluetooth dongle rtl8761b

[Ismael Ferreras]

This one seems like the same unregistered USB VID issue as in #1955351.
A patch was submitted by Helmut Grohne and accepted. The firmware seems
to also appear now on the linux-firmware repo.


Someone should submit this patch to sta...@vger.kernel.org so that it can get 
backported.

* https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955351
* https://github.com/bluez/bluetooth-next/commit/6dfbe29f
* 
https://patchwork.kernel.org/project/bluetooth/patch/yhpf0jdpcmrxz...@alf.mars/
* 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/WHENCE?id=fe3ec816766aaf2106f508bcab62f408a1fc0a0c#n4017

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

Title:
  Bluetooth dongle rtl8761b

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Package: linux-firmware
  Architecture: all
  Version: 1.187

  The device is recognized, hciconfig -a shows a device, no errors at
  all. It can scan do whatever. The only thing it doesn't do is find
  anything.

  hci0: Type: Primary  Bus: USB
BD Address: 00:E0:4C:19:xx:xx  ACL MTU: 1021:6  SCO MTU: 255:12
UP RUNNING 
RX bytes:1706 acl:0 sco:0 events:225 errors:0
TX bytes:6122 acl:0 sco:0 commands:201 errors:0
Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
Link policy: RSWITCH HOLD SNIFF PARK 
Link mode: SLAVE ACCEPT 
Name: 'hostname'
Class: 0x1c0104
Service Classes: Rendering, Capturing, Object Transfer
Device Class: Computer, Desktop workstation
HCI Version: 5.1 (0xa)  Revision: 0xb
LMP Version: 5.1 (0xa)  Subversion: 0x8761
Manufacturer: Realtek Semiconductor Corporation (93)

  #included on request
  Ubuntu 5.13.0-23.23~20.04.2-generic 5.13.19
  00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th 
Gen Core Processor Host Bridge/DRAM Registers [8086:191f] (rev 07)
Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v5/E3-1500 v5/6th 
Gen Core Processor Host Bridge/DRAM Registers [1458:5000]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

  00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th 
Gen Core Processor PCIe Controller (x16) [8086:1901] (rev 07) (prog-if 00 
[Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

  00:14.0 USB controller [0c03]: Intel Corporation 100 Series/C230 Series 
Chipset Family USB 3.0 xHCI Controller [8086:a12f] (rev 31) (prog-if 30 [XHCI])
Subsystem: Gigabyte Technology Co., Ltd 100 Series/C230 Series Chipset 
Family USB 3.0 xHCI Controller [1458:5007]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

  00:16.0 Communication controller [0780]: Intel Corporation 100 Series/C230 
Series Chipset Family MEI Controller #1 [8086:a13a] (rev 31)
Subsystem: Gigabyte Technology Co., Ltd 100 Series/C230 Series Chipset 
Family MEI Controller [1458:1c3a]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

  00:17.0 RAID bus controller [0104]: Intel Corporation SATA Controller [RAID 
mode] [8086:2822] (rev 31)
Subsystem: Gigabyte Technology Co., Ltd SATA Controller [RAID mode] 
[1458:b005]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: ahci
Kernel modules: ahci

  00:1b.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset 
Family PCI Express Root Port #17 [8086:a167] (rev f1) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

  00:1b.2 PCI bridge [0

[Kernel-packages] [Bug 1955351] Re: Add support for EDUP Bluetooth 5.1 USB

[Ismael Ferreras]

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

** This bug has been marked a duplicate of bug 1955916
   Bluetooth dongle rtl8761b

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

Title:
  Add support for EDUP Bluetooth 5.1 USB

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sorry, this is more of a feature request, but I didn't know where to
  send one, and just followed the instructions in a thread I found
  online!

  ---

  The EDUP Bluetooth dongle uses the Realtek RTL8761B chipset, and seems
  to work fine with the existing  RTL8761B driver after manually
  patching the kernel following this guide:
  https://askubuntu.com/questions/835084/bluetoothctl-cant-detect-
  device-but-hcitool-can

  Output of `hciconfig -a`

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:E0:4C:1A:58:04  ACL MTU: 1021:5  SCO MTU: 255:11
  UP RUNNING
  RX bytes:166020 acl:0 sco:0 events:2718 errors:0
  TX bytes:25153 acl:0 sco:0 commands:178 errors:0
  Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87
  Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
  Link policy: RSWITCH HOLD SNIFF PARK
  Link mode: SLAVE ACCEPT
  Name: 'ubuntu-Server'
  Class: 0x6c0104
  Service Classes: Rendering, Capturing, Audio, Telephony
  Device Class: Computer, Desktop workstation
  HCI Version: 5.1 (0xa)  Revision: 0xd99
  LMP Version: 5.1 (0xa)  Subversion: 0x646b
  Manufacturer: Realtek Semiconductor Corporation (93)

  Output of `usb-devices | awk '/8761/' RS=`

  T:  Bus=01 Lev=02 Prnt=02 Port=04 Cnt=02 Dev#=  4 Spd=12  MxCh= 0
  D:  Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=2550 ProdID=8761 Rev=02.00
  S:  Manufacturer=Realtek
  S:  Product=Bluetooth Radio
  S:  SerialNumber=00E04C239987
  C:  #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=500mA
  I:  If#=0x0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  I:  If#=0x1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb

  Kernel version: 5.13.0-22-generic

  Sorry, this is my first bug / feature report for Linux, and apologies
  if I've done something wrong 🙇‍♀️

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-22-generic 5.13.0-22.22
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.13.0-22-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2824 F pulseaudio
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: unknown
  Date: Sun Dec 19 15:07:04 2021
  HibernationDevice: RESUME=/dev/mapper/ubuntu--Server--vg-swap_1
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Hewlett-Packard HP Compaq Pro 6300 SFF
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-22-generic 
root=/dev/mapper/ubuntu--Server--vg-root ro
  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.13.0-22-generic N/A
   linux-backports-modules-5.13.0-22-generic  N/A
   linux-firmware 1.201.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-12-19 (0 days ago)
  dmi.bios.date: 04/10/2019
  dmi.bios.release: 3.8
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: K01 v03.08
  dmi.board.asset.tag: 2UA4071FM7
  dmi.board.name: 339A
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 2UA4071FM7
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v03.08:bd04/10/2019:br3.8:svnHewlett-Packard:pnHPCompaqPro6300SFF:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct4:cvr:skuE0E18UP#ABA:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP Compaq Pro 6300 SFF
  dmi.product.sku: E0E18UP#ABA
  dmi.sys.vendor: Hewlett-Packard

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


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

[Kernel-packages] [Bug 1966125] [NEW] Suspend (to ram) fails after upgrade from 5.13.0-35-generic to 5.13.0-37-generic

[Günter Neiß]

Public bug reported:

As stated in the summary, my PC can't suspend anymore after kernel upgrade.
When I click suspend from desktop:
- The screen gets blank
- (sometimes) Screen then shows up for a short time, then gets blank again
- Now PC ist "dead", no reaction an keyboard, mouse and so on.
- Even a CTR-ALT-DEL didn't show any reaction.
- There is still some activity (HD-Led flashing)
- The PC is "reachable" via network, but trying to ssh into it will not work 
(no response after entering password)
- I have to reboot, either by power the PC off by pressing the power button 
longer or by using "Magic SysRq" keyboard sequence

When I rollback (I use systemback) to Kernel 5.13.0-35-generic suspend
works!

#
Information needed as directed by 
https://wiki.ubuntu.com/DebuggingKernelSuspend)
#
=
$cat /proc/acpi/wakeup
Device  S-state   Status   Sysfs node
GPP0  S4*enabled   pci::00:01.1
GP12  S4*enabled   pci::00:07.1
GP13  S4*enabled   pci::00:08.1
XHC0  S4*enabled   pci::0e:00.3
GP30  S4*disabled
GP31  S4*disabled
PS2K  S3*disabled
GPP2  S4*disabled
GPP3  S4*disabled
GPP8  S4*enabled   pci::00:03.1
SWUS  S4*enabled   pci::0a:00.0
SWDS  S4*enabled   pci::0b:00.0
GPP1  S4*enabled   pci::00:01.2
=
sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"

... after power up again ...

dmesg | grep -e "Magic number" -e "hash matches"
[3.141067] PM:   Magic number: 0:247:389
[3.145394] PM:   hash matches drivers/base/power/main.c:982
[3.149741] thermal cooling_device4: hash matches
=
sudo su
echo freezer > /sys/power/pm_test
exit
sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"

... promt is back after a few seconds again ...

dmesg | grep -e "Magic number" -e "hash matches"
[3.142991] PM:   Magic number: 14:995:344
[3.147383] tty tty61: hash matches
[3.151721] acpi ACPI0007:06: hash matches
=
sudo su
echo devices > /sys/power/pm_test
exit
sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"

... after power up again ...

dmesg | grep -e "Magic number" -e "hash matches"
[3.141229] PM:   Magic number: 0:247:394
[3.145558] PM:   hash matches drivers/base/power/main.c:982
[3.149905] thermal cooling_device9: hash matches
=
sudo su
echo platform > /sys/power/pm_test
exit
sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"

... after power up again ...

dmesg | grep -e "Magic number" -e "hash matches"
[3.142816] PM:   Magic number: 0:247:394
[3.147180] PM:   hash matches drivers/base/power/main.c:982
[3.151573] thermal cooling_device9: hash matches
=
sudo su
echo processors > /sys/power/pm_test
exit
sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"

... after power up again ...

dmesg | grep -e "Magic number" -e "hash matches"
[3.141830] PM:   Magic number: 0:247:394
[3.146148] PM:   hash matches drivers/base/power/main.c:982
[3.150488] thermal cooling_device9: hash matches
=
sudo su
echo core > /sys/power/pm_test
exit
sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"

... after power up again ...

dmesg | grep -e "Magic number" -e "hash matches"
[3.140971] PM:   Magic number: 0:247:394
[3.145294] PM:   hash matches drivers/base/power/main.c:982
[3.149639] thermal cooling_device9: hash matches
=
sudo su
echo none > /sys/power/pm_test
exit
sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"

... after power up again ...

dmesg | grep -e "Magic number" -e "hash matches"
[3.143489] PM:   Magic number: 0:247:394
[3.147856] PM:   hash matches drivers/base/power/main.c:982
[3.152244] thermal cooling_device9: hash matches
=
$ sudo cat /sys/kernel/debug/suspend_stats 
success: 0
fail: 0
failed_freeze: 0
failed_prepare: 0
failed_suspend: 0
failed_suspend_late: 0
failed_suspend_noirq: 0
failed_resume: 0
failed_resume_early: 0
failed_resume_noirq: 0
failures:
  last_failed_dev:  

  last_failed_errno:0
0
  last_failed_step: 
=

#
System information:
#

=
lsb_release -rd
Description:Ubuntu 20.04.4 LTS
Release:20.04
=

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.

[Kernel-packages] [Bug 1942624] Re: NVME "can't change power state from D3Cold to D0 (config space inaccessible)"

[Heitor Alves de Siqueira]

Hi all,

This seems to be related to a regression introduced by the following commit:
* 7e4fdeafa61f ACPI: power: Turn off unused power resources unconditionally

The fix seems to indeed be the commit @sclarkson mentioned:
* bc2836859643 ACPI: PM: Do not turn off power resources in unknown state

Looking at our kernels, it seems the affected version window is between v5.12 
and v5.15. I've tagged the relevant packages in this bug, and have built a set 
of test kernels to validate the fixes. For the 5.13 kernels, we additionally 
require the commit below:
* 9b7ff25d129d ACPI: power: Refine turning off unused power resources

I'd greatly appreciate if anyone affected by this could give these test
kernels a try, as I don't have the appropriate hardware to test it
myself. I've uploaded packages for Focal-HWE/Impish (5.13) and Focal-OEM
(5.14) to a public PPA, but please consider these packages for testing
purposes only. If you can reproduce this bug on a different kernel,
please add a comment and I'll look into backporting the required patches
there as well.

Cheers,
Heitor

[0] https://launchpad.net/~halves/+archive/ubuntu/test-1942624

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

Title:
  NVME "can't change power state from D3Cold to D0 (config space
  inaccessible)"

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  In Progress
Status in linux source package in Impish:
  In Progress
Status in linux-oem-5.14 source package in Impish:
  Invalid

Bug description:
  Bug with kernels after version 5.11.0-18 on Lenovo Ideapad 330-15ICH.
  The NVME drive with my root partition cannot be mounted at boot with
  an error "can't change power state from D3Cold to D0 (config space
  inaccessible)". I'm willing to help find a root cause if I don't need
  to spent too many hours. All Ubuntu kernels after 5.11.0-18 exhibit
  this bug, but I could boot properly with the official linux kernel
  5.13.0. Thanks a lot for your help

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-18-generic 5.11.0-18.19
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  7503 F pulseaudio
   /dev/snd/pcmC0D0p:   chris  7503 F...m pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  3 18:46:35 2021
  InstallationDate: Installed on 2019-07-17 (779 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 5986:210e Acer, Inc EasyCamera
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 007: ID 1050:0407 Yubico.com Yubikey 4/5 OTP+U2F+CCID
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81FK
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic 
root=UUID=9d963312-3a16-428d-8efd-f1323c6528f1 ro quiet nosplash 
crashkernel=512M-:192M
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-18-generic N/A
   linux-backports-modules-5.11.0-18-generic  N/A
   linux-firmware 1.197.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to hirsute on 2021-06-03 (92 days ago)
  dmi.bios.date: 10/24/2018
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7ZCN29WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330-15ICH
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr7ZCN29WW:bd10/24/2018:br1.29:efr1.29:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH:
  dmi.product.family: ideapad 330-15ICH
  dmi.product.name: 81FK
  dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH
  dmi.product.version: Lenovo ideapad 330-15ICH
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1963555] Re: xhci: Fix command ring abort, write all 64 bits to CRCR register.

[Jonathan George]

This appears to be the resolution upstream:
https://lore.kernel.org/linux-usb/yay1eiy%2ff7ezp...@kroah.com/

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

Title:
  xhci: Fix command ring abort, write all 64 bits to CRCR register.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upstream mainline kernel includes patch v5.15-rc5-4-gff0e50d3564f.
  This patch was included in the Ubuntu kernel as 
Ubuntu-5.13.0-22.22-387-g0fc979747dec, available in Ubuntu kernels 5.13.0-23 
and up.

  The patch is incomplete, which causes an issue with some xHC controllers.
  An additional patch was made to the upstream mainline kernel, which fixes the 
issue that was introduced: v5.16-rc3-1-g09f736aa9547. This patch does not yet 
have a corresponding commit in the Ubuntu kernel repository for Ubuntu 21.10; 
and Ubuntu 22.04 will use the 5.15 kernel, which does also not include the 
second patch.

  Discussion of the first patch (already in Ubuntu kernel) can be found
  on the kernel.org mailing list:
  
https://lore.kernel.org/r/20211008092547.3996295-5-mathias.ny...@linux.intel.com

  Discussion of the second patch (not yet in Ubuntu kernel):
  
https://lore.kernel.org/all/20211126122340.1193239-2-mathias.ny...@linux.intel.com/

  Request to include upstream patch v5.16-rc3-1-g09f736aa9547 into the
  kernels for Ubuntu 21.10 (5.13 kernels) and Ubuntu 22.04 LTS (5.15
  kernels).

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-22-generic 5.13.0-22.22
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  amedee 4158 F pulseaudio
   /dev/snd/controlC3:  amedee 4158 F pulseaudio
   /dev/snd/controlC0:  amedee 4158 F pulseaudio
   /dev/snd/controlC1:  amedee 4158 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  3 22:23:43 2022
  HibernationDevice: RESUME=UUID=edec0bf3-448f-4e5c-a21a-ef9624572973
  InstallationDate: Installed on 2022-01-30 (32 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Z370 AORUS Gaming K3
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-22-generic N/A
   linux-backports-modules-5.13.0-22-generic  N/A
   linux-firmware 1.201.4
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/28/2019
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F15a
  dmi.board.asset.tag: Default string
  dmi.board.name: Z370 AORUS Gaming K3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF15a:bd11/28/2019:br5.12:svnGigabyteTechnologyCo.,Ltd.:pnZ370AORUSGamingK3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370AORUSGamingK3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z370 AORUS Gaming K3
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Kernel-packages] [Bug 1966066] Re: audio from external sound card is distorted

[Hampus Lundberg]

** Description changed:

  The sound card is a Focusrite Scarlett 2i2.
  
  The sound is distorted everywhere.
  
  Sound via HDMI works.
  
  Seen others having the same problem:
- https://askubuntu.com/questions/138284/how-to-downgrade-a-package-via-
- apt-get
+ (Edit because of previously wrong link here) 
https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card
  
  ubuntu release: Ubuntu 20.04.4 LTS
  package name involved in bug: linux-image-5.13.0-37-generic
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 12:56:02 2022
  InstallationDate: Installed on 2020-12-18 (459 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  audio from external sound card is distorted

Status in linux-signed-hwe-5.13 package in Ubuntu:
  Confirmed

Bug description:
  The sound card is a Focusrite Scarlett 2i2.

  The sound is distorted everywhere.

  Sound via HDMI works.

  Seen others having the same problem:
  (Edit because of previously wrong link here) 
https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card

  ubuntu release: Ubuntu 20.04.4 LTS
  package name involved in bug: linux-image-5.13.0-37-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 12:56:02 2022
  InstallationDate: Installed on 2020-12-18 (459 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1966066/+subscriptions


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

[Kernel-packages] [Bug 1966143] [NEW] Periodic glitch in LogiTech H390 headphone audio

[Michael Sharman]

Public bug reported:

When running kernel version 5.13.0-37-generic the audio output through
my Logitech H390 headphones has a periodic "glitch" every few seconds -
noticable in Google Meetings and Youtube - its very distracting, its not
exactly a scratch or pop; it's more like a really bad reception mobile
phone call "robot voice" noise but lasts only for a moment, then maybe
30 seconds later occurs again, seems to be regularly periodic.

The problem isn't present on 5.13.0-35-generic and doesn't effect my
external speaker audio output just the headphones so it's not a network
issue.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Thu Mar 24 10:26:12 2022
InstallationDate: Installed on 2018-02-17 (1495 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
SourcePackage: linux-signed-hwe-5.13
UpgradeStatus: Upgraded to focal on 2020-05-08 (684 days ago)

** Affects: linux-signed-hwe-5.13 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Description changed:

  When running kernel version 5.13.0-37-generic the audio output through
  my Logitech H390 headphones has a periodic "glitch" every few seconds -
  noticable in Google Meetings and Youtube - its very distracting, its not
- exactly a scratch or pop, not sure how to describe it.
+ exactly a scratch or pop; it's more like a really bad reception mobile
+ phone call "robot voice" noise but lasts only for a moment, then maybe
+ 30 seconds later occurs again, seems to be regularly peridoic.
  
  The problem isn't present on 5.13.0-35-generic and doesn't effect my
  sound card audio output just the headphones.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Thu Mar 24 10:26:12 2022
  InstallationDate: Installed on 2018-02-17 (1495 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: Upgraded to focal on 2020-05-08 (684 days ago)

** Description changed:

  When running kernel version 5.13.0-37-generic the audio output through
  my Logitech H390 headphones has a periodic "glitch" every few seconds -
  noticable in Google Meetings and Youtube - its very distracting, its not
  exactly a scratch or pop; it's more like a really bad reception mobile
  phone call "robot voice" noise but lasts only for a moment, then maybe
- 30 seconds later occurs again, seems to be regularly peridoic.
+ 30 seconds later occurs again, seems to be regularly periodic.
  
  The problem isn't present on 5.13.0-35-generic and doesn't effect my
- sound card audio output just the headphones.
+ external speaker audio output just the headphones so it's not a network
+ issue.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Thu Mar 24 10:26:12 2022
  InstallationDate: Installed on 2018-02-17 (1495 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: Upgraded to focal on 2020-05-08 (684 days ago)

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

Title:
  Periodic glitch in LogiTech H390 headphone audio

Status in linux-signed-hwe-5.13 package in Ubuntu:
  New

Bug description:
  When running kernel version 5.13.0-37-generic the audio output through
  my Logitech H390 headphones has a periodic "glitch" every few seconds
  - noticable in Google Meetings and Youtube - its very distracting, its
  not exactly a scratch or pop; it's more like a really bad reception
  mobile phone call "robot voice" noise but lasts only for a moment,
  then maybe 30 seconds later occurs again, seems to be regularly
  periodic.

  The problem isn't present on 5.13.0-35-generic and doesn't effect my
  external speaker audio output just the headphones so it's not a
  network issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-37

[Kernel-packages] [Bug 1948701] Re: Hard system lock under 5.* kernel on standard laptop

[Dirk Eddelbuettel]

It was a mirage. The system is still locking up, something that did not
happen with an older kernel, and also not with other systems booting off
USB.

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

Title:
  Hard system lock under 5.* kernel on standard laptop

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This issue appeared first under 21.04, and I (wrongly) suspected a bug
  in the window manager or graphics stack. I posted on askubuntu at

  https://askubuntu.com/questions/1346317/ubuntu-21-04-and-21-10-lock-
  hard-with-basic-gui-redrawing-using-standard-intel-g

  and even offered a bounty but no luck.  I then hopen 21.10 may solve
  it, but alas, no.

  At issue is a fairly immediate system lock as soon as I use Chrome or
  Slack and switch desktops.  It typically locks the machine with
  minutes of a reboot -- making it unuseable under GUI.

  On the other hand, I kept it running 'headless' (just ssh'ed in from
  byobu running on my desktop) for a month so I had some reason to
  believe the hard ware was not at fault.

  Now, more recently, I realized that I had not tried an older kernel,
  and indeed under 4.13.0-46-generic, still installed from an older
  relese, everything runs fine!

  I would be happy to help debug if you pointers or test builds.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-20-generic 5.13.0-20.20
  ProcVersionSignature: Ubuntu 4.13.0-46.51-generic 4.13.16
  Uname: Linux 4.13.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edd2005 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Mon Oct 25 13:04:38 2021
  HibernationDevice: RESUME=UUID=97ca6744-22ea-45bd-bf19-38197b40062c
  InstallationDate: Installed on 2016-08-08 (1904 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20FCCTO1WW
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-46-generic 
root=UUID=5f3d6606-96bb-422c-9918-62d7cf6850fb ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-46-generic N/A
   linux-backports-modules-4.13.0-46-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-10-14 (11 days ago)
  dmi.bios.date: 06/23/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET41W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FCCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FCCTO1WW:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FCCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 4th
  dmi.product.name: 20FCCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1963555] Re: xhci: Fix command ring abort, write all 64 bits to CRCR register.

[Amedee Van Gasse]

Well, yes, the message you linked does not contain any new information;
the two commits there (the one that introduced the bug and the one that
fixes it) are already mentioned here in the first message.

The intent of this bug report is to pull in the fixing bugfix from
upstream.

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

Title:
  xhci: Fix command ring abort, write all 64 bits to CRCR register.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upstream mainline kernel includes patch v5.15-rc5-4-gff0e50d3564f.
  This patch was included in the Ubuntu kernel as 
Ubuntu-5.13.0-22.22-387-g0fc979747dec, available in Ubuntu kernels 5.13.0-23 
and up.

  The patch is incomplete, which causes an issue with some xHC controllers.
  An additional patch was made to the upstream mainline kernel, which fixes the 
issue that was introduced: v5.16-rc3-1-g09f736aa9547. This patch does not yet 
have a corresponding commit in the Ubuntu kernel repository for Ubuntu 21.10; 
and Ubuntu 22.04 will use the 5.15 kernel, which does also not include the 
second patch.

  Discussion of the first patch (already in Ubuntu kernel) can be found
  on the kernel.org mailing list:
  
https://lore.kernel.org/r/20211008092547.3996295-5-mathias.ny...@linux.intel.com

  Discussion of the second patch (not yet in Ubuntu kernel):
  
https://lore.kernel.org/all/20211126122340.1193239-2-mathias.ny...@linux.intel.com/

  Request to include upstream patch v5.16-rc3-1-g09f736aa9547 into the
  kernels for Ubuntu 21.10 (5.13 kernels) and Ubuntu 22.04 LTS (5.15
  kernels).

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-22-generic 5.13.0-22.22
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  amedee 4158 F pulseaudio
   /dev/snd/controlC3:  amedee 4158 F pulseaudio
   /dev/snd/controlC0:  amedee 4158 F pulseaudio
   /dev/snd/controlC1:  amedee 4158 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  3 22:23:43 2022
  HibernationDevice: RESUME=UUID=edec0bf3-448f-4e5c-a21a-ef9624572973
  InstallationDate: Installed on 2022-01-30 (32 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Z370 AORUS Gaming K3
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-22-generic N/A
   linux-backports-modules-5.13.0-22-generic  N/A
   linux-firmware 1.201.4
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/28/2019
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F15a
  dmi.board.asset.tag: Default string
  dmi.board.name: Z370 AORUS Gaming K3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF15a:bd11/28/2019:br5.12:svnGigabyteTechnologyCo.,Ltd.:pnZ370AORUSGamingK3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370AORUSGamingK3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z370 AORUS Gaming K3
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Kernel-packages] [Bug 1963555] Re: xhci: Fix command ring abort, write all 64 bits to CRCR register.

[Amedee Van Gasse]

See also the kernel mailing list message from 26 November 2021:
https://lore.kernel.org/all/20211126122340.1193239-2-mathias.ny...@linux.intel.com/

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

Title:
  xhci: Fix command ring abort, write all 64 bits to CRCR register.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upstream mainline kernel includes patch v5.15-rc5-4-gff0e50d3564f.
  This patch was included in the Ubuntu kernel as 
Ubuntu-5.13.0-22.22-387-g0fc979747dec, available in Ubuntu kernels 5.13.0-23 
and up.

  The patch is incomplete, which causes an issue with some xHC controllers.
  An additional patch was made to the upstream mainline kernel, which fixes the 
issue that was introduced: v5.16-rc3-1-g09f736aa9547. This patch does not yet 
have a corresponding commit in the Ubuntu kernel repository for Ubuntu 21.10; 
and Ubuntu 22.04 will use the 5.15 kernel, which does also not include the 
second patch.

  Discussion of the first patch (already in Ubuntu kernel) can be found
  on the kernel.org mailing list:
  
https://lore.kernel.org/r/20211008092547.3996295-5-mathias.ny...@linux.intel.com

  Discussion of the second patch (not yet in Ubuntu kernel):
  
https://lore.kernel.org/all/20211126122340.1193239-2-mathias.ny...@linux.intel.com/

  Request to include upstream patch v5.16-rc3-1-g09f736aa9547 into the
  kernels for Ubuntu 21.10 (5.13 kernels) and Ubuntu 22.04 LTS (5.15
  kernels).

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-22-generic 5.13.0-22.22
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  amedee 4158 F pulseaudio
   /dev/snd/controlC3:  amedee 4158 F pulseaudio
   /dev/snd/controlC0:  amedee 4158 F pulseaudio
   /dev/snd/controlC1:  amedee 4158 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  3 22:23:43 2022
  HibernationDevice: RESUME=UUID=edec0bf3-448f-4e5c-a21a-ef9624572973
  InstallationDate: Installed on 2022-01-30 (32 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Z370 AORUS Gaming K3
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-22-generic N/A
   linux-backports-modules-5.13.0-22-generic  N/A
   linux-firmware 1.201.4
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/28/2019
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F15a
  dmi.board.asset.tag: Default string
  dmi.board.name: Z370 AORUS Gaming K3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF15a:bd11/28/2019:br5.12:svnGigabyteTechnologyCo.,Ltd.:pnZ370AORUSGamingK3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370AORUSGamingK3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z370 AORUS Gaming K3
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Kernel-packages] [Bug 1964440] Re: 5.15.0-22: No console displayed on EFI systems

[ChongMeng Eng]

Kernel 5.15.0-23 confirmed fix on my legion5Pro.

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

Title:
  5.15.0-22: No console displayed on EFI systems

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  DISCLAIMER:
  This is my second-ever bug report. Apologies in advance for any missing or 
inaccurate info. I am willing to troubleshoot and supply more/better info as 
needed.

  PROBLEM DESCRIPTION:
  After upgrading the kernel on my Ubuntu 22.04 Server test system from 
5.15.0-18 to 5.15.0-22, I see absolutely no console output on my display past 
the grub menu.

  I can give the system a few seconds to finish booting, log in blindly and 
watch the activity LEDs on e.g. the network interface as i run a ping or 
similar.
  I can also log in remotely via SSH, and/or use a serial console. So the 
system definitely does boot. But my actual display/screen shows no console 
output.

  ENVIRONMENT:

  (Output gathered via SSH while display was showing no output)

  testuser@testserver:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04
  Codename: jammy
  testuser@testserver:~$ uname -a
  Linux testserver 5.15.0-22-generic #22-Ubuntu SMP Tue Feb 8 10:16:30 UTC 2022 
x86_64 x86_64 x86_64 GNU/Linux

  This was initially discovered on an Ubuntu Server VM running in EFI mode on 
VirtualBox 6.1.32.
  System was installed with the daily 'jammy-live-server-amd64.iso' image from 
2022-03-07, fully upgraded as of 2022-03-10.
  Switching Graphics Controller in Virtualbox does not help, nor does 
'nomodeset' or 'noacpi'.
  I am able to reproduce the issue on real hardware and with different physical 
graphics cards.

  Similar symptoms can also be observed in Ubuntu Desktop (still using EFI) by 
attempting to switch to tty with CTRL + ALT + F[3-6], or by taking note of the 
missing plymouth screen during boot.
  Systems installed/booted in legacy BIOS mode (both Server and Desktop) do not 
appear to be affected.

  I have tried reinstalling on both virtual and hardware platforms, with
  same result before and after upgrading the kernel.

  HOW TO REPRODUCE - Ubuntu Server:
  - Boot existing Ubuntu Server EFI installation with 5.15.0-18 and observe 
console output
  - Set GRUB_TIMEOUT_STYLE=menu and GRUB_TIMEOUT=10 in /etc/default/grub (to 
enable rollback)
  - Run update-grub
  - Run sudo apt full-upgrade and watch linux version 5.15.0-22 get installed
  - Reboot and observe your display (no console output will be shown after grub)

  HOW TO REPRODUCE - Ubuntu Desktop:
  - Download Ubuntu 22.04 Desktop daily ISO
  - Write ISO to USB
  - Boot from USB in EFI mode
  - Install system
  - Run sudo apt full-upgrade and upgrade linux* to kernel 5.15.0-22
  - Reboot and observe missing plymouth screen during boot
  - Wait for graphical login screen to appear
  - Press CTRL + ALT + F[3-6] (screen will go black and/or freeze)
  - Press CTRL + ALT + F1 (screen will unfreeze and/or return to gdm greeter)

  WORKAROUNDS:
  If you still have 5.15.0-18 or earlier installed, select it in Grub.
  and/or install mainline kernel 5.16.11+ (for testing only - will not work if 
you have Secure Boot enabled).
  Alternatively, re-install/convert/boot your system to boot in legacy BIOS 
mode.

  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.15.0-22-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-10 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20220307)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=8fe50fbe-79d7-47a9-ad2f-ff36ddc1fe54 ro
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  RelatedPackageVersions:
   linu

[Kernel-packages] [Bug 1959728] Re: trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume

[Wei]

Same machine and same issues here. works fine in Windows.

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

Title:
  trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my X1 Yoga Titanium (which has a fancy new "Sensel" trackpad with
  haptic response to clicks), the trackpad stops working after a
  suspend/resume cycle, although the red trackpoint continues to work
  fine for controlling the pointer.  I believe this system is using S0i3
  for suspend, in case that's relevant.

  If I boot from power off, then the trackpad works fine in both the
  pre-boot BIOS and in Ubuntu 22.04 (prerelease), including haptic
  response to clicks.  After a suspend/resume cycle, the trackpad stops
  responding, although a lot of swiping/pressing will occasionally
  produce a button press event.  This state persists even if I reboot
  out of Linux (without a power cycle) - for example the trackpad no
  longer works for the pre-boot BIOS configuration screen, until a full
  power cycle (which fixes the trackpad).

  Possibly relevant, the trackpad seems to be this device to the kernel:

  [2.016917] input: SNSL0001:00 2C2F:0006 Mouse as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0001:00/0018:2C2F:0006.0001/input/input6
  [2.016964] input: SNSL0001:00 2C2F:0006 Touchpad as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0001:00/0018:2C2F:0006.0001/input/input7
  [2.017027] hid-generic 0018:2C2F:0006.0001: input,hidraw0: I2C HID v1.00 
Mouse [SNSL0001:00 2C2F:0006] on i2c-SNSL0001:00

  and the last kernel messages before suspend are:

  [  305.216189] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [  305.217435] printk: Suspending console(s) (use no_console_suspend to debug)
  [  305.274332] i2c_designware i2c_designware.0: i2c_dw_handle_tx_abort: lost 
arbitration
  [  306.030947] i2c_hid_acpi i2c-SNSL0001:00: failed to set a report to device.
  [  306.616463] ACPI: EC: interrupt blocked
  [  331.551118] ACPI: EC: interrupt unblocked

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bina   1543 F pipewire
bina   1544 F pipewire-media-
bina   1545 F pulseaudio
   /dev/snd/seq:bina   1543 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  1 14:54:14 2022
  InstallationDate: Installed on 2022-02-01 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
  MachineType: LENOVO 20QA000EUS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-18-generic N/A
   linux-backports-modules-5.15.0-18-generic  N/A
   linux-firmware 20220124.git0c6a7b3b-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2021
  dmi.bios.release: 1.18
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2MET53W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QA000EUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2MET53W(1.18):bd09/30/2021:br1.18:efr1.11:svnLENOVO:pn20QA000EUS:pvrThinkPadX1TitaniumGen1:rvnLENOVO:rn20QA000EUS:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20QA_BU_Think_FM_ThinkPadX1TitaniumGen1:
  dmi.product.family: ThinkPad X1 Titanium Gen 1
  dmi.product.name: 20QA000EUS
  dmi.product.sku: LENOVO_MT_20QA_BU_Think_FM_ThinkPad X1 Titanium Gen 1
  dmi.product.version: ThinkPad X1 Titanium Gen 1
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1965968] Re: post jammy update, black/flickering screen on boot

[Daniel van Vugt]

Ideally the flicker (PSR) should get a separate bug to the black screen
regression, but it's difficult to separate them when both are messing up
the same screen at the same time. So let's focus on just the black
screen here.


** Summary changed:

- post jammy update, black/flickering screen on boot
+ [Dell XPS 15 9575] Black screen on boot in kernels 5.14 and 5.15 (but 5.13.19 
works)

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

Title:
  [Dell XPS 15 9575] Black screen on boot in kernels 5.14 and 5.15 (but
  5.13.19 works)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After initial jammy upgrade things were working fine, but after a
  recent update the machine boots to a blank screen.  There are
  occasional purplish flickers that seem to correspond with keypresses,
  but even blindly typing the encrypted disk password doesn't appear to
  advance the boot process to gdm.

  Plugging in an external monitor does fix the issue and allow boot to
  proceed, but obviously doesn't help if not near an external monitor.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: plymouth 0.9.5+git20211018-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Tue Mar 22 09:22:26 2022
  DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
  InstallationDate: Installed on 2019-08-17 (948 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  MachineType: Dell Inc. XPS 15 9575
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic 
root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic 
root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7
  SourcePackage: plymouth
  TextPlymouth: 
/usr/share/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth
  UpgradeStatus: Upgraded to jammy on 2022-03-18 (3 days ago)
  dmi.bios.date: 03/25/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.1
  dmi.board.name: 0N338G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1965968] Re: [Dell XPS 15 9575] Black screen on boot in kernels 5.14 and 5.15 (but 5.13.19 works)

[Daniel van Vugt]

This feels like something the OEM team would have already fixed in an
oem kernel?

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

Title:
  [Dell XPS 15 9575] Black screen on boot in kernels 5.14 and 5.15 (but
  5.13.19 works)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After initial jammy upgrade things were working fine, but after a
  recent update the machine boots to a blank screen.  There are
  occasional purplish flickers that seem to correspond with keypresses,
  but even blindly typing the encrypted disk password doesn't appear to
  advance the boot process to gdm.

  Plugging in an external monitor does fix the issue and allow boot to
  proceed, but obviously doesn't help if not near an external monitor.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: plymouth 0.9.5+git20211018-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Tue Mar 22 09:22:26 2022
  DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
  InstallationDate: Installed on 2019-08-17 (948 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  MachineType: Dell Inc. XPS 15 9575
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic 
root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic 
root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7
  SourcePackage: plymouth
  TextPlymouth: 
/usr/share/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth
  UpgradeStatus: Upgraded to jammy on 2022-03-18 (3 days ago)
  dmi.bios.date: 03/25/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.1
  dmi.board.name: 0N338G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1962799] Re: Bad items from Powertop on oem kernel

[Bin Li]

** Changed in: oem-priority
   Status: New => Triaged

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

Title:
  Bad items from Powertop on oem kernel

Status in OEM Priority Project:
  Triaged
Status in linux-oem package in Ubuntu:
  New

Bug description:
  On Jaguar2, we found some items are bad from powertop, could we set
  them 'Good' by default from oem kernel, so that we could save more
  power consumption.

  System info
  
  "ThinkPad X1 Yoga Gen 7", "BIOS": "N3AET52W (1.17 ) 02/21/2022",
  CPU": "12th Gen Intel(R) Core(TM) i5-1235U", VGA: [8086:46a8],
  Kernel: 5.14.0-1024-oem

  Power Consumption
  ===
  The idle-screen-on-residency-check/cpu-low-power-idle/system-low-power-idle 
passed.
  Default value and the value after set all ‘Good’ in powertop
  ShortIdle: 5.5W, 5W
  LongIdle: 1.8W, 2W
  S2Idle: 0.6W, 0.6W

  Bad items
  ===
  * VM writeback timeout
  (echo ‘1500’ > /proc/sys/vm/dirty_writeback_centisecs)

  * Should we turn off the NMI watchdog for the OEM kernel? It
  prompt“NMI watchdog should be turned off”
  (/proc/sys/kernel/nmi_watchdog)

  * Runtime PM for I2C Adapter i2c-[2-10] (i915 gmbus tc[1-6]/dp[a-c])?
  By default these values are ‘on’, should we set it to ‘auto’? 
(/sys/bus/i2c/devices/i2c-2/device/power/control)

  * Runtime PM for PCI Device Intel Corporation Device 
[4601,46a8,461d,464f,51a4,51f0,5182,51ed,51ef,51fc]?
  Host bridge,VGA controller,Signal processing controller,System 
peripheral,Serial bus controller,Network Controller,ISA bridge,USB 
controller,RAM memory,Serial controller.
  (/sys/bus/pci/devices/:00:00.0/power/control)

  * Runtime PM for PCI Device MEDIATEK Corp. Device 4d75
  * Runtime PM for PCI Device Samsung Electronics Co Ltd Device a80a

  * Autosuspend for USB device USB Bridge [MCHP]?
  (/sys/bus/usb/devices/3-8/power/control)

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


-- 
Mailing list: https://launchpad.net/~kernel-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-oracle/5.13.0.1024.24)

[Ubuntu SRU Bot]

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

systemd/248.3-1ubuntu8.2 (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/impish/update_excuses.html#linux-meta-oracle

[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 1912052] Re: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 21.04 (not even wired, cable headset)

[Po-Hsu Lin]

** Changed in: linux (Ubuntu Bionic)
 Assignee: Po-Hsu Lin (cypressyew) => (unassigned)

** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => 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/1912052

Title:
  [Acer Spin 5 - SP513-54N] External headset microphone not working on
  Ubuntu 21.04 (not even wired, cable headset)

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  New
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed
Status in linux source package in Impish:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  Recently, external microphone has stopped working while using classic
  wired audio combo jack headset.

  Basics:

  1) Headset's microphone works fine both in MS Windows on the same machine and 
on older Xubuntu on another machine.
  2) Internal laptop mic works normally.
  3) Yes, I have mic unmuted in settings.

  I've followed whole step1 from this troubleshoot guide:
  https://help.ubuntu.com/community/SoundTroubleshootingProcedure

  Did not help.

  There are more information with screenshots here:
  https://askubuntu.com/questions/1305942/external-headset-microphone-
  not-working-on-ubuntu-20-10-not-even-wired-cable-h:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crysman2301 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 16 13:31:13 2021
  InstallationDate: Installed on 2020-06-19 (210 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-12-08 (38 days ago)
  dmi.bios.date: 07/17/2020
  dmi.bios.release: 1.5
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.05
  dmi.board.name: Caboom_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.05
  dmi.chassis.type: 31
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.05
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:br1.5:efr1.2:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05:
  dmi.product.family: Spin 5
  dmi.product.name: Spin SP513-54N
  dmi.product.sku: 
  dmi.product.version: V1.05
  dmi.sys.vendor: Acer

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


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

[Kernel-packages] [Bug 1966159] [NEW] package linux-libc-dev 5.4.0-105.119 failed to install/upgrade: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted

[Kavindu Zoysa]

Public bug reported:

This makes my laptop very slow.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-libc-dev 5.4.0-105.119
ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-34-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
AptOrdering:
 linux-libc-dev:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  kavindu1601 F pulseaudio
CasperMD5CheckResult: skip
Date: Tue Mar 22 23:39:37 2022
Dependencies:
 
DpkgTerminalLog:
 Preparing to unpack .../linux-libc-dev_5.4.0-105.119_amd64.deb ...
 Unpacking linux-libc-dev:amd64 (5.4.0-105.119) over (5.4.0-104.118) ...
 dpkg: error processing archive 
/var/cache/apt/archives/linux-libc-dev_5.4.0-105.119_amd64.deb (--unpack):
  unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation 
not permitted
DuplicateSignature:
 package:linux-libc-dev:5.4.0-105.119
 Unpacking linux-libc-dev:amd64 (5.4.0-105.119) over (5.4.0-104.118) ...
 dpkg: error processing archive 
/var/cache/apt/archives/linux-libc-dev_5.4.0-105.119_amd64.deb (--unpack):
  unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation 
not permitted
ErrorMessage: unable to open 
'/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted
InstallationDate: Installed on 2021-06-20 (276 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: LENOVO 20FBA07Y00
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=106efafd-9069-4bf9-b738-813dcacd8be7 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.
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13
SourcePackage: linux
Title: package linux-libc-dev 5.4.0-105.119 failed to install/upgrade: unable 
to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not 
permitted
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/08/2017
dmi.bios.release: 1.23
dmi.bios.vendor: LENOVO
dmi.bios.version: N1FET49W (1.23 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FBA07Y00
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.14
dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET49W(1.23):bd02/08/2017:br1.23:efr1.14:svnLENOVO:pn20FBA07Y00:pvrThinkPadX1Carbon4th:skuLENOVO_MT_20FB_BU_Think_FM_ThinkPadX1Carbon4th:rvnLENOVO:rn20FBA07Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 4th
dmi.product.name: 20FBA07Y00
dmi.product.sku: LENOVO_MT_20FB_BU_Think_FM_ThinkPad X1 Carbon 4th
dmi.product.version: ThinkPad X1 Carbon 4th
dmi.sys.vendor: LENOVO

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


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

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

Title:
  package linux-libc-dev 5.4.0-105.119 failed to install/upgrade: unable
  to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation
  not permitted

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This makes my laptop very slow.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-libc-dev 5.4.0-105.119
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  AptOrdering:
   linux-libc-dev:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kavindu1601 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Tue Mar 22 23:39:37 2022
  Dependencies:
   
  DpkgTerminalLog:
   Preparing to unpack .../linux-libc-dev_5.4.0-105.119_amd64.deb ...
   Unpacking linux-libc-dev:amd64 (5.4.0-105.119) over (5.4.0-104.118) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-libc-dev_5.4.0-105.119_amd64.deb (--unpack):
unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': 
Operation not permitted
  DuplicateSignature:
   package:linux-libc-dev:5.4.0-105.119
   Unpacking linux-libc-dev:amd64 (5.4.0-105.119) over (5.4.0-104.118) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-libc-dev_5.4.0-105.119_amd64.deb (--unpack):
unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': 
Operation not permitted
  ErrorMessage: unable to open 
'/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted
  InstallationDate: Installed on 2021-06-20 (2

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  package linux-libc-dev 5.4.0-105.119 failed to install/upgrade: unable
  to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation
  not permitted

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This makes my laptop very slow.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-libc-dev 5.4.0-105.119
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  AptOrdering:
   linux-libc-dev:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kavindu1601 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Tue Mar 22 23:39:37 2022
  Dependencies:
   
  DpkgTerminalLog:
   Preparing to unpack .../linux-libc-dev_5.4.0-105.119_amd64.deb ...
   Unpacking linux-libc-dev:amd64 (5.4.0-105.119) over (5.4.0-104.118) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-libc-dev_5.4.0-105.119_amd64.deb (--unpack):
unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': 
Operation not permitted
  DuplicateSignature:
   package:linux-libc-dev:5.4.0-105.119
   Unpacking linux-libc-dev:amd64 (5.4.0-105.119) over (5.4.0-104.118) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-libc-dev_5.4.0-105.119_amd64.deb (--unpack):
unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': 
Operation not permitted
  ErrorMessage: unable to open 
'/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted
  InstallationDate: Installed on 2021-06-20 (276 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 20FBA07Y00
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=106efafd-9069-4bf9-b738-813dcacd8be7 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.
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13
  SourcePackage: linux
  Title: package linux-libc-dev 5.4.0-105.119 failed to install/upgrade: unable 
to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not 
permitted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/08/2017
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET49W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FBA07Y00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.14
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET49W(1.23):bd02/08/2017:br1.23:efr1.14:svnLENOVO:pn20FBA07Y00:pvrThinkPadX1Carbon4th:skuLENOVO_MT_20FB_BU_Think_FM_ThinkPadX1Carbon4th:rvnLENOVO:rn20FBA07Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 4th
  dmi.product.name: 20FBA07Y00
  dmi.product.sku: LENOVO_MT_20FB_BU_Think_FM_ThinkPad X1 Carbon 4th
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1963555] Re: xhci: Fix command ring abort, write all 64 bits to CRCR register.

[Jonathan George]

You referenced the original report, patch, and promotion to Linux Next for 
review. The new information is that the resolution for the issue you referenced 
was reviewed and promoted by Greg KH from Linux Next to his queue for Linus 
https://lore.kernel.org/all/yayq%2fxdb%2fphss7%...@kroah.com/ in the production 
kernel back on December 5, 2021. BTW it was accepted into Linus's mainline 
queue with commit 
https://lore.kernel.org/all/163872600645.987.7156724710444619664.pr-tracker-...@kernel.org/
 later that day.
Interestingly Greg mentioned merging these changes into the stable queue. If he 
actually did so (I didn't notice where) it might help to make sure that 21.10 
and 22.04 are immediately rebased to include the mainline included patches.

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

Title:
  xhci: Fix command ring abort, write all 64 bits to CRCR register.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upstream mainline kernel includes patch v5.15-rc5-4-gff0e50d3564f.
  This patch was included in the Ubuntu kernel as 
Ubuntu-5.13.0-22.22-387-g0fc979747dec, available in Ubuntu kernels 5.13.0-23 
and up.

  The patch is incomplete, which causes an issue with some xHC controllers.
  An additional patch was made to the upstream mainline kernel, which fixes the 
issue that was introduced: v5.16-rc3-1-g09f736aa9547. This patch does not yet 
have a corresponding commit in the Ubuntu kernel repository for Ubuntu 21.10; 
and Ubuntu 22.04 will use the 5.15 kernel, which does also not include the 
second patch.

  Discussion of the first patch (already in Ubuntu kernel) can be found
  on the kernel.org mailing list:
  
https://lore.kernel.org/r/20211008092547.3996295-5-mathias.ny...@linux.intel.com

  Discussion of the second patch (not yet in Ubuntu kernel):
  
https://lore.kernel.org/all/20211126122340.1193239-2-mathias.ny...@linux.intel.com/

  Request to include upstream patch v5.16-rc3-1-g09f736aa9547 into the
  kernels for Ubuntu 21.10 (5.13 kernels) and Ubuntu 22.04 LTS (5.15
  kernels).

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-22-generic 5.13.0-22.22
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  amedee 4158 F pulseaudio
   /dev/snd/controlC3:  amedee 4158 F pulseaudio
   /dev/snd/controlC0:  amedee 4158 F pulseaudio
   /dev/snd/controlC1:  amedee 4158 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  3 22:23:43 2022
  HibernationDevice: RESUME=UUID=edec0bf3-448f-4e5c-a21a-ef9624572973
  InstallationDate: Installed on 2022-01-30 (32 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Z370 AORUS Gaming K3
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-22-generic N/A
   linux-backports-modules-5.13.0-22-generic  N/A
   linux-firmware 1.201.4
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/28/2019
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F15a
  dmi.board.asset.tag: Default string
  dmi.board.name: Z370 AORUS Gaming K3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF15a:bd11/28/2019:br5.12:svnGigabyteTechnologyCo.,Ltd.:pnZ370AORUSGamingK3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370AORUSGamingK3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z370 AORUS Gaming K3
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Kernel-packages] [Bug 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support

[Muralidharan]

Hi Vicamo,

Please let us know once you have further updates on ADL FM350 integration on 
ADL-P RVP or other OEM devices.
Please do let us know if you need any help from our side.

Thanks and Best Regards,
Murali

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

Title:
  Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] 
(rev 01)
  Subsystem: Hewlett-Packard Company Device [103c:8914]

  
https://lore.kernel.org/linux-wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:
   
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-07-13 (119 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Intel Corporation Alder Lake Client Platform
  Package: linux-firmware 1.187.20+staging.31
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem 
root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 
automatic-oem-config quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14
  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.14.0-9007-oem N/A
   linux-backports-modules-5.14.0-9007-oem  N/A
   linux-firmware   1.187.20+staging.31
  Tags:  focal
  Uname: Linux 5.14.0-9007-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/23/2021
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: AlderLake-M LP5 RVP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 0.1
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002:
  dmi.product.family: Alder Lake Client System
  dmi.product.name: Alder Lake Client Platform
  dmi.product.sku: 01010002
  dmi.product.version: 0.1
  dmi.sys.vendor: Intel Corporation

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


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

[Kernel-packages] [Bug 1966066] Re: audio from external sound card is distorted

[Steve]

I can confirm the same distorted sound issue with the same external
audio device: Focusrite Scarlett 2i2

5.13.0-37

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

Title:
  audio from external sound card is distorted

Status in linux-signed-hwe-5.13 package in Ubuntu:
  Confirmed

Bug description:
  The sound card is a Focusrite Scarlett 2i2.

  The sound is distorted everywhere.

  Sound via HDMI works.

  Seen others having the same problem:
  (Edit because of previously wrong link here) 
https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card

  ubuntu release: Ubuntu 20.04.4 LTS
  package name involved in bug: linux-image-5.13.0-37-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 12:56:02 2022
  InstallationDate: Installed on 2020-12-18 (459 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1966066/+subscriptions


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

[Kernel-packages] [Bug 1965740] Re: BlueZ 5.64 release

[Daniel van Vugt]

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

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

Title:
  BlueZ 5.64 release

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  http://www.bluez.org/release-of-bluez-5-64/

  At least for 22.10, but maybe for 22.04 too.

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


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