[Kernel-packages] [Bug 1956467] Re: powerlight stays on after shutdown

[Willos]

Same for me :

ACER Aspire A315-21
AMD® A9-9420 radeon r5, 5 compute cores 2c+3g × 2
AMD® Stoney
Ubuntu 20.04.3 LTS
kernel 5.11.0.41 to 46

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

Title:
  powerlight stays on after shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After kernel upgrade from 5.11.0.40 to versions 5.11.0.41, 5.11.0.43,
  5.11.0.44 power-button light fails to switch off, after shutdown.

  shutdown can be triggered from command line or via desktop menu,
  result is the same. After rebooting from 5.11.0.40 normal
  functionality is restored.

  systemd appears to complete shutdown looking at the logs (see
  attached)

  Switching to suspend mode (sleep) functions as expected (power light blinks) 
and stays permanently on after wake-up.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  christian   1896 F pulseaudio
   /dev/snd/controlC0:  christian   1896 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-06 (609 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81MT
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-40-generic N/A
   linux-backports-modules-5.11.0-40-generic  N/A
   linux-firmware 1.187.24
  Tags:  focal
  Uname: Linux 5.11.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/09/2019
  dmi.bios.release: 2.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8ZCN23WW(V2.02)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo V145-15AST
  dmi.ec.firmware.release: 2.23
  dmi.modalias: 
dmi:bvnLENOVO:bvr8ZCN23WW(V2.02):bd05/09/2019:br2.23:efr2.23:svnLENOVO:pn81MT:pvrLenovoV145-15AST:skuLENOVO_MT_81MT_BU_idea_FM_V145-15AST:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoV145-15AST:
  dmi.product.family: V145-15AST
  dmi.product.name: 81MT
  dmi.product.sku: LENOVO_MT_81MT_BU_idea_FM_V145-15AST
  dmi.product.version: Lenovo V145-15AST
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1954773] Re: New fix for jack detection after resume on CS8409 sound driver

[Chris Chiu]

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

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

Title:
  New fix for jack detection after resume on CS8409 sound driver

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

Bug description:
  [SRU Justification]

  [Impact]
  On some platforms with Cirrus CS8409 audio codec, the external headset will 
fail to be detected after system resume.

  [Fix]
  Cirrus released a new fix commit 65cc4ad62a9e ('ALSA: hda/cs8409: Set PMSG_ON 
earlier inside cs8409 driver'). It sets the power_state to ON before the 
unsolicited event arrives to make sure the jack detection can be invoked after 
resume.

  [Test]
  Plug-in an external headset in front headset port, suspend/resume the system 
then check whether the headset function works as expected.

  [Where problem could occur]
  Low. It only affect the platforms with Cirrus codec CS8409 which used to have 
problem.

  == Original Bug Description ==

  [Summary] System can't detect external headset after suspend

  [Steps to reproduce]
  1. install manifest and boot into OS
  2. plug-in an external headset in front headset port
  3. un-plug external headset
  4. suspend system
  5. resume system from suspend
  6. plug-in an external headset

  [Expected result]
  System could detect external headset after suspend

  [Actual result]
  System can't detect external headset after suspend

  [Failure rate]
  3/3

  [Additional information]
  CID: 202110-29567
  SKU: DLPV-SFF-DVT-C1
  Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-davos-adl+X152
  system-manufacturer: Dell Inc.
  system-product-name: Vostro 3710
  bios-version: 0.13.73
  CPU: 12th Gen Intel(R) Core(TM) i7-12700 (20x)
  GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:4680] (rev 0c)
  kernel-version: 5.13.0-1019-oem

  [Stage]
  Issue reported and logs collected right after it happened

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


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

[Kernel-packages] [Bug 1949063] Re: Add F81966 watchdog support

[AceLan Kao]

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

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

Title:
  Add F81966 watchdog support

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.11 package in Ubuntu:
  Invalid
Status in linux-hwe-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-hwe-5.11 source package in Focal:
  Fix Released
Status in linux-hwe-5.13 source package in Focal:
  Fix Released
Status in linux source package in Hirsute:
  Fix Released
Status in linux-hwe-5.11 source package in Hirsute:
  Invalid
Status in linux-hwe-5.13 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  Fix Committed
Status in linux-hwe-5.11 source package in Impish:
  Invalid
Status in linux-hwe-5.13 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-hwe-5.11 source package in Jammy:
  Invalid
Status in linux-hwe-5.13 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  f71808e_wdt watchdog driver can't recognize F81966 chip.

  [Fix]
  AAEON provides a patch to add the ID.
  https://www.spinics.net/lists/kernel/msg4147351.html

  [Test]
  Testing was done on the Aaeon SSE-OPTI

  [Where problems could occur]
  Simply adding one ID, should not introduce any regressions.

  [Misc]
  This patch is for ODM project and need this to be included as soon as 
possible, so we submit this patch as a sauce patch before upstream merges it.
  BTW, Jammy already included this commit when the patch was submitted for the 
SRU the first time.

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


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

[Kernel-packages] [Bug 1958774] Re: Blackscreen after suspending and closing LID

[Chuyang Chen]

** Description changed:

  These bugs occur after I upgrade the linux-generic package from 5.11
  (not sure) to 5.13 today. After that, I have met two similar bugs:
  
  1. Every time I suspend my computer and re-activate it, I will get a black 
screen with a bleaking cursor.
  2. Every time I close my laptop's LID and reopen it, I will get an empty 
black screen (without anything).
  
  These bugs really trouble me. It will be very helpful if you fix it.
+ 
+ UPDATE: After I upgrade the "core" package using "snap refresh", the
+ first bug has been fixed. However, the second bug related to laptop
+ devices is still there.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-generic 5.13.0.27.37
  ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nomanous   5648 F pulseaudio
   /dev/snd/controlC1:  nomanous   5648 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 23 23:02:24 2022
  InstallationDate: Installed on 2021-06-29 (208 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: HASEE Computer NH5x_7xDCx_DDx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=018344b7-14eb-4d4a-b012-cf2577a7bc6a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.201.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-10-15 (100 days ago)
  dmi.bios.date: 04/18/2020
  dmi.bios.release: 7.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.03THZX
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH5x_7xDCx_DDx
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.1
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.03THZX:bd04/18/2020:br7.3:efr7.1:svnHASEEComputer:pnNH5x_7xDCx_DDx:pvrNotApplicable:rvnNotebook:rnNH5x_7xDCx_DDx:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: NH5x_7xDCx_DDx
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer

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

Title:
  Blackscreen after suspending and closing LID

Status in linux package in Ubuntu:
  New

Bug description:
  These bugs occur after I upgrade the linux-generic package from 5.11
  (not sure) to 5.13 today. After that, I have met two similar bugs:

  1. Every time I suspend my computer and re-activate it, I will get a black 
screen with a bleaking cursor.
  2. Every time I close my laptop's LID and reopen it, I will get an empty 
black screen (without anything).

  These bugs really trouble me. It will be very helpful if you fix it.

  UPDATE: After I upgrade the "core" package using "snap refresh", the
  first bug has been fixed. However, the second bug related to laptop
  devices is still there.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-generic 5.13.0.27.37
  ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nomanous   5648 F pulseaudio
   /dev/snd/controlC1:  nomanous   5648 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 23 23:02:24 2022
  InstallationDate: Installed on 2021-06-29 (208 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: HASEE Computer NH5x_7xDCx_DDx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=018344b7-14eb-4d4a-b012-cf2577a7bc6a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.201.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-10-15 (100 days ago)
  dmi.bios.date: 04/18/2020
  dmi.bios.release: 7.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.03THZX
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH5x_7xDCx_DDx
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  

[Kernel-packages] [Bug 1958914] Re: AMD GPU driver not loading.

[Juerg Haefliger]

Probably missing firmware. Can you run 'apport-collect 1958914'?

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

Title:
  AMD GPU driver not loading.

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

Bug description:
  The video driver for my AMD GPU does not seem to be loading properly
  with kernel 5.13. The GUI loads but is stuck with a low resolution.

  Output of 'lspci -v' command seems to show that no graphics driver is
  in use. I expect 'amdgpu' to be the selected driver for my GPU.

  Everything works correctly if I restart the system and select the
  previous kernel version (5.11.0-44).

  Additional info:
  I have linux-generic-hwe-20.04 meta package installed (currently at version 
5.13.0.27.29~20.04.13)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 24 19:02:21 2022
  InstallationDate: Installed on 2021-11-17 (68 days ago)
  InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210824)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  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/1958914/+subscriptions


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

[Kernel-packages] [Bug 1957753] Re: net/mlx5e: EPERM on vlan 0 programming

[Po-Hsu Lin]

** Description changed:

- [Impact] 
+ [Impact]
  There is an issue with hypervisor host side mlx5 driver operation on 
Bluefield devices in kernels <=5.16
  
  Copied from patch description:
  When using libvirt to passthrough VF to VM it will always set the VF vlan
  to 0 even if user didn’t request it, this will cause libvirt to fail to
  boot in case the PF isn't eswitch owner.
  
  Example of such case is the DPU host PF which isn't eswitch manager, so
- any attempt to passthrough VF of it using libvirt will fail. 
+ any attempt to passthrough VF of it using libvirt will fail.
  
  [Fix]
  * 7846665d net/mlx5e: Unblock setting vid 0 for VF in case PF isn't
-  eswitch manager
+  eswitch manager
  
  This patch can be cherry-picked into Impish and newer kernels, but it
  requires some backport work on F/H due to they're missing commit
  b55b3538 that split the legacy code out.
  
  [Test]
  Test kernels can be found here:
  F: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/F/
  H: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/H/
  I: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/I/
  J: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/J/
  
  Kernels tested by Dmitrii Shcherbakov with positive feedback.
  
  [Where problems could occur]
- If this patch is erroneous, it might cause issue to this mlx5 driver.
- 
+ If this patch is erroneous, it might cause issue to this mlx5 driver with 
certain operations (passing vlan 0).
  
  [Original Bug Description]
  There is an issue with hypervisor host side mlx5 driver operation on 
Bluefield devices in kernels <=5.16 that was recently fixed in master with a 
one-liner:
  
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37
  
  It would be good to have this fix in Focal+ kernels.
  
  This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux-
  bluefield since it's used at the DPU side whereas the issue in question
  affects the hypervisor side.

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

Title:
  net/mlx5e: EPERM on vlan 0 programming

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in linux source package in Hirsute:
  Confirmed
Status in linux source package in Impish:
  Confirmed
Status in linux source package in Jammy:
  Confirmed

Bug description:
  [Impact]
  There is an issue with hypervisor host side mlx5 driver operation on 
Bluefield devices in kernels <=5.16

  Copied from patch description:
  When using libvirt to passthrough VF to VM it will always set the VF vlan
  to 0 even if user didn’t request it, this will cause libvirt to fail to
  boot in case the PF isn't eswitch owner.

  Example of such case is the DPU host PF which isn't eswitch manager, so
  any attempt to passthrough VF of it using libvirt will fail.

  [Fix]
  * 7846665d net/mlx5e: Unblock setting vid 0 for VF in case PF isn't
   eswitch manager

  This patch can be cherry-picked into Impish and newer kernels, but it
  requires some backport work on F/H due to they're missing commit
  b55b3538 that split the legacy code out.

  [Test]
  Test kernels can be found here:
  F: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/F/
  H: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/H/
  I: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/I/
  J: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/J/

  Kernels tested by Dmitrii Shcherbakov with positive feedback.

  [Where problems could occur]
  If this patch is erroneous, it might cause issue to this mlx5 driver with 
certain operations (passing vlan 0).

  [Original Bug Description]
  There is an issue with hypervisor host side mlx5 driver operation on 
Bluefield devices in kernels <=5.16 that was recently fixed in master with a 
one-liner:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37

  It would be good to have this fix in Focal+ kernels.

  This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux-
  bluefield since it's used at the DPU side whereas the issue in
  question affects the hypervisor side.

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


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

[Kernel-packages] [Bug 1953334] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part

[Frank Heimes]

Hello Kelsey, sorry for the delay, I've noticed this verification request, but 
for verifying this another package based on LP#1953338 is needed, which became 
just available since yesterday.
Now with having both, a verification will be done soon-ish ...

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

Title:
  [UBUNTU 20.04] KVM hardware diagnose data improvements for guest
  kernel - kernel part

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
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:
  In Progress

Bug description:
  SRU Justification:
  ==

  [Impact]

  * Hardware diagnose data (diag 318) of KVM guest kernel cannot be
  handled.

  * A fix is needed to enhance problem determination of guest kernel
  under KVM using DIAG 0x318 instruction execution.

  * The s390x diagnose 318 instruction sets the control program name
  code (CPNC) and control program version code (CPVC) to provide useful
  information regarding the OS during debugging.

  * The CPNC is explicitly set to 4 to indicate a Linux/KVM environment.

  [Fix]

  * In general the following 4 commits are needed:

  * 3fd8417f2c728d810a3b26d7e2008012ffb7fd01 3fd8417f2c72 "KVM: s390: add debug 
statement for diag 318 CPNC data"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545726/+files/0004-KVM-s390-add-debug-statement-for-diag-318-CPNC-data.patch

  * 6cbf1e960fa52e4c63a6dfa4cda8736375b34ccc 6cbf1e960fa5 "KVM: s390: remove 
diag318 reset code"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545725/+files/0003-KVM-s390-remove-diag318-reset-code.patch

  * 23a60f834406c8e3805328b630d09d5546b460c1 23a60f834406 "s390/kvm: diagnose 
0x318 sync and reset"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545724/+files/0002-s390-kvm-diagnose-0x318-sync-and-reset.patch

  * a23816f3cdcbffe5dc6e8c331914b3f51b87c2f3 a23816f3cdcb "s390/setup: diag 
318: refactor struct"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545723/+files/0001-s390-setup-diag-318-refactor-struct.patch

  * For jammy, hirsute and impish only the first commit is needed, the
  others are already in.

  * For focal all 4 commits are needed, but since they do not apply
  cleanly on focal, the attached backports need to be used instead.

  [Test Case]

  * Setup an IBM Z or LinuxONE LPAR with Ubuntu Server as KVM host.

  * And setup an Ubuntu KVM virtual on top.

  * It can then be observed if the CPNC (diag318 data) has been
  successfully set by looking at the s390dbf messages for the KVM guest.

  * The CPNC will always be 4 (denotes Linux environment).

  * Another way to test this is by running the sync_regs_test under
  tools/testing/selftests/kvm/s390x/sync_regs_test.   Just running the
  kernel self test suite can trigger this.

  [Where problems could occur]

  * The approach here is to provide additional debug and diagnose
  information on top.

  * Hence even if the diag318 changes are broken, the existing
  functionality shouldn't be harmed.

  * The changes themselves are relatively discernible and mostly
  introduce new structures.

  * However, with the functional changes broken code could be introduced
  (e.g. due to erroneous pointer arithmetic for example) that does not
  compile or causes crashes. But this is what the test builds are for
  (https://launchpad.net/~fheimes/+archive/ubuntu/lp1953334).

  * On top the diag318 diagnose data might not properly provided - maybe
  empty or wrong. Again that is what the test builds and the
  verification later is targeted at.

  * Since diag318 is s390x specific, all the modifications touch s390x
  code only. (in arch/s390/kvm/ kvm-s390.c and vsie.c,
  arch/s390/kernel/setup.c, arch/s390/include/asm/ kvm_host.h, kvm.h and
  diag.h). At least no other other architecture will be affected.

  * Well, there is one tiny bit of a common code change, but it's just a
  new define statement in include/uapi/linux/kvm.h ('#define
  KVM_CAP_S390_DIAG318 186').

  [Other]

  * Request was to add the patches to focal / 20.04, but to avoid
  potential regressions on upgrades, the patches need to be added to
  jammy, impish and hirsute, too.

  * As mentioned above, Jammy, Hirsute and Impish includes almost
  everything needed, except 3fd8417f2c72 "KVM: s390: add debug statement
  for diag 318 CPNC data".

  * Hence the SRU is for Focal, Jammy, Hirsute and Impish, but less
  invasive for Jammy, Hirsute and Impish, also because commit
  3fd8417f2c72 can be cleanly cherry-picked form there.

  * LP#1953338 is related to this bug and covers the qemu/KVM bits.
  __

[Kernel-packages] [Bug 1958850] Re: USB port lost function after unplugging usb drive

[koba]

@Timo, 5.14-oem-1020 is ok, the regression is with 5.14-oem-1021.
im bisecting.

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

Title:
  USB port lost function after unplugging usb drive

Status in OEM Priority Project:
  New
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Incomplete

Bug description:
  Test the proposed 5.14 oem kernel, and get a failure symptom.

  Unplug a usb drive from WD19TB docking and a BUG reported in kernel,
  then the other embedded usb port can't detect usb drive anymore after
  a while.

  kernel: usb 5-2.3.3: USB disconnect, device number 5
  kernel: BUG: kernel NULL pointer dereference, address: 0030
  kernel: #PF: supervisor read access in kernel mode
  kernel: #PF: error_code(0x) - not-present page
  kernel: PGD 0 P4D 0
  kernel: Oops:  [#1] SMP NOPTI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  2205 F pulseaudio
   /dev/snd/controlC0:  u  2205 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-04-29 (270 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. Precision 5750
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem 
root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-1021-oem N/A
   linux-backports-modules-5.14.0-1021-oem  N/A
   linux-firmware   1.201.3
  Tags:  impish
  Uname: Linux 5.14.0-1021-oem x86_64
  UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990:
  dmi.product.family: Precision
  dmi.product.name: Precision 5750
  dmi.product.sku: 0990
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-hwe-5.13/5.13.0.28.31~20.04.15)

[Ubuntu SRU Bot]

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

nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 (amd64)
systemd/245.4-4ubuntu3.15 (amd64, s390x, ppc64el)


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

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

[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 1958850] Re: USB port lost function after unplugging usb drive

[Timo Aaltonen]

could be a regression due to patches from bug 1950974, although there
are also >1100 patches from stable@

are you able to bisect?

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

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

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

** Tags added: block-proposed

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

Title:
  USB port lost function after unplugging usb drive

Status in OEM Priority Project:
  New
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Incomplete

Bug description:
  Test the proposed 5.14 oem kernel, and get a failure symptom.

  Unplug a usb drive from WD19TB docking and a BUG reported in kernel,
  then the other embedded usb port can't detect usb drive anymore after
  a while.

  kernel: usb 5-2.3.3: USB disconnect, device number 5
  kernel: BUG: kernel NULL pointer dereference, address: 0030
  kernel: #PF: supervisor read access in kernel mode
  kernel: #PF: error_code(0x) - not-present page
  kernel: PGD 0 P4D 0
  kernel: Oops:  [#1] SMP NOPTI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  2205 F pulseaudio
   /dev/snd/controlC0:  u  2205 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-04-29 (270 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. Precision 5750
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem 
root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-1021-oem N/A
   linux-backports-modules-5.14.0-1021-oem  N/A
   linux-firmware   1.201.3
  Tags:  impish
  Uname: Linux 5.14.0-1021-oem x86_64
  UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990:
  dmi.product.family: Precision
  dmi.product.name: Precision 5750
  dmi.product.sku: 0990
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1896420] Re: seccomp_bpf in seccomp from ubuntu_kernel_selftests failed to build on B-5.4

[Po-Hsu Lin]

END GOODubuntu_kernel_selftests.seccomp-build

Verified with 5.4.0-97.110~18.04.1 on node fili.

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

** Changed in: ubuntu-kernel-tests
   Status: New => Fix Released

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

Title:
  seccomp_bpf in seccomp from ubuntu_kernel_selftests failed to build on
  B-5.4

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  Test fails to build in selftests/seccomp/seccomp_bpf.c with
  'error: storage size of ‘md’ isn’t known' due to the type
  struct seccomp_metadata not being defined for B/5.4 kernels.

  [Test case]

  Test successfully builds and test cases pass both on Bionic/5.4 and on
  Focal

  [Fixes]

  Unconditionally define struct seccomp_metadata.
  Remove linux/ptrace.h where a definition of seccomp_metadata is already being
  defined in Focal.

  [Potential regression]

  There could be future build failures if glibc headers get updated to
  include definitions of struct seccomp_metadata or if linux/ptrace.h gets 
updated
  to include needed definitions.

  ---
  Issue found on 5.4.0-48.52~18.04.1

  Test build failed with:
   gcc -Wl,-no-as-needed -Wall seccomp_bpf.c -lpthread -o seccomp_bpf
   seccomp_bpf.c: In function ‘get_metadata’:
   seccomp_bpf.c:3028:26: error: storage size of ‘md’ isn’t known
   struct seccomp_metadata md;
   ^~
   seccomp_bpf.c:3028:26: warning: unused variable ‘md’ [-Wunused-variable] 
   Makefile:12: recipe for target 'seccomp_bpf' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1896420/+subscriptions


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

[Kernel-packages] [Bug 1957753] Re: net/mlx5e: EPERM on vlan 0 programming

[Po-Hsu Lin]

** Description changed:

- There is an issue with hypervisor host side mlx5 driver operation on
- Bluefield devices in kernels <=5.16 that was recently fixed in master
- with a one-liner:
+ [Impact] 
+ There is an issue with hypervisor host side mlx5 driver operation on 
Bluefield devices in kernels <=5.16
+ 
+ Copied from patch description:
+ When using libvirt to passthrough VF to VM it will always set the VF vlan
+ to 0 even if user didn’t request it, this will cause libvirt to fail to
+ boot in case the PF isn't eswitch owner.
+ 
+ Example of such case is the DPU host PF which isn't eswitch manager, so
+ any attempt to passthrough VF of it using libvirt will fail. 
+ 
+ [Fix]
+ * 7846665d net/mlx5e: Unblock setting vid 0 for VF in case PF isn't
+  eswitch manager
+ 
+ This patch can be cherry-picked into Impish and newer kernels, but it
+ requires some backport work on F/H due to they're missing commit
+ b55b3538 that split the legacy code out.
+ 
+ [Test]
+ Test kernels can be found here:
+ F: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/F/
+ H: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/H/
+ I: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/I/
+ J: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/J/
+ 
+ Kernels tested by Dmitrii Shcherbakov with positive feedback.
+ 
+ [Where problems could occur]
+ If this patch is erroneous, it might cause issue to this mlx5 driver.
+ 
+ 
+ [Original Bug Description]
+ There is an issue with hypervisor host side mlx5 driver operation on 
Bluefield devices in kernels <=5.16 that was recently fixed in master with a 
one-liner:
  
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37
  
  It would be good to have this fix in Focal+ kernels.
  
  This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux-
  bluefield since it's used at the DPU side whereas the issue in question
  affects the hypervisor side.

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

Title:
  net/mlx5e: EPERM on vlan 0 programming

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in linux source package in Hirsute:
  Confirmed
Status in linux source package in Impish:
  Confirmed
Status in linux source package in Jammy:
  Confirmed

Bug description:
  [Impact] 
  There is an issue with hypervisor host side mlx5 driver operation on 
Bluefield devices in kernels <=5.16

  Copied from patch description:
  When using libvirt to passthrough VF to VM it will always set the VF vlan
  to 0 even if user didn’t request it, this will cause libvirt to fail to
  boot in case the PF isn't eswitch owner.

  Example of such case is the DPU host PF which isn't eswitch manager, so
  any attempt to passthrough VF of it using libvirt will fail. 

  [Fix]
  * 7846665d net/mlx5e: Unblock setting vid 0 for VF in case PF isn't
   eswitch manager

  This patch can be cherry-picked into Impish and newer kernels, but it
  requires some backport work on F/H due to they're missing commit
  b55b3538 that split the legacy code out.

  [Test]
  Test kernels can be found here:
  F: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/F/
  H: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/H/
  I: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/I/
  J: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/J/

  Kernels tested by Dmitrii Shcherbakov with positive feedback.

  [Where problems could occur]
  If this patch is erroneous, it might cause issue to this mlx5 driver.

  
  [Original Bug Description]
  There is an issue with hypervisor host side mlx5 driver operation on 
Bluefield devices in kernels <=5.16 that was recently fixed in master with a 
one-liner:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37

  It would be good to have this fix in Focal+ kernels.

  This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux-
  bluefield since it's used at the DPU side whereas the issue in
  question affects the hypervisor side.

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


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

[Kernel-packages] [Bug 1952217] Re: bluetoothd coredumps from double free on connection of headset

[Launchpad Bug Tracker]

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

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

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

Title:
  bluetoothd coredumps from double free on connection of headset

Status in bluez package in Ubuntu:
  Expired

Bug description:
  Problem:

  Since the security updates on 2021-11-23 connecting my headset causes
  bluetoothd to crash, which drops all the other connections.

  Expected:

  Headset connects and works as it has done previously.

  
  ❯ lsb_release -rd
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  ❯ apt-cache policy bluez
  bluez:
Installed: 5.53-0ubuntu3.4
Candidate: 5.53-0ubuntu3.4

  
  Headset is a Sony WH-1000XM3. I have ppa:berglh/pulseaudio-a2dp installed for 
the LDAC codecs for this headset.

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


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

[Kernel-packages] [Bug 1952375] Re: Blutooth headset not taking

[Launchpad Bug Tracker]

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

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

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

Title:
  Blutooth headset not taking

Status in bluez package in Ubuntu:
  Expired

Bug description:
  Blutooth Headset problem

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: bluez 5.60-0ubuntu2.1
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 26 01:09:24 2021
  InstallationDate: Installed on 2020-07-22 (491 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04f2:b64f Chicony Electronics Co., Ltd HD User Facing
   Bus 001 Device 003: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire A515-54
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic 
root=UUID=c9b8ebcf-747e-454e-8dfb-68b609629c3a ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to impish on 2021-10-15 (41 days ago)
  dmi.bios.date: 08/01/2019
  dmi.bios.release: 1.11
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Doc_WC
  dmi.board.vendor: CML
  dmi.board.version: V1.11
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd08/01/2019:br1.11:efr1.6:svnAcer:pnAspireA515-54:pvrV1.11:rvnCML:rnDoc_WC:rvrV1.11:cvnChassisManufacturer:ct10:cvrChassisVersion:sku:
  dmi.product.family: Aspire 5
  dmi.product.name: Aspire A515-54
  dmi.product.sku: 
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 84:FD:D1:EA:D2:2D  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:151467 acl:66 sco:0 events:20824 errors:0
TX bytes:13788724 acl:20413 sco:0 commands:299 errors:0

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


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

[Kernel-packages] [Bug 1958620] Re: Flickering white/black screen once KMS comes up

[Chris Halse Rogers]

There is no scanout hardware connected to the AMD GPU, so if there is
any involvement by amdgpu it is purely by making i915 misbehave.

This is also not a GNOME bug - the display corrupts as soon as the KMS
driver is loaded, which, since I've got an encrypted rootfs, is early in
the initramfs. The same behaviour is observed regardless of the kernel
commandline options, too, so it's not plymouth doing something weird, or
vthandoff. It also happens with break=mount.

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

Title:
  Flickering white/black screen once KMS comes up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This looks like a regression from the 5.13.0-20-generic kernel to the
  5.15.0-17-generic kernel. The display works fine under efifb, but as
  soon as the DRM drivers are loaded and KMS kicks in the display is
  replaced by black with flickering white (apparently when what would be
  on the output changes).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  7134 F pipewire-media-
   /dev/snd/seq:chris  7133 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 21 17:07:08 2022
  InstallationDate: Installed on 2021-06-26 (208 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
  MachineType: Dell Inc. XPS 15 9575
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash
  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-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.204
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago)
  dmi.bios.date: 07/07/2019
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  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/1958620/+subscriptions


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

[Kernel-packages] [Bug 1953334] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part

[Kelsey Skunberg]

Hi Frank, may you please verify this bug is resolved on the
focal/hirsute/impish kernels in -proposed? Appreciate your help!

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

Title:
  [UBUNTU 20.04] KVM hardware diagnose data improvements for guest
  kernel - kernel part

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
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:
  In Progress

Bug description:
  SRU Justification:
  ==

  [Impact]

  * Hardware diagnose data (diag 318) of KVM guest kernel cannot be
  handled.

  * A fix is needed to enhance problem determination of guest kernel
  under KVM using DIAG 0x318 instruction execution.

  * The s390x diagnose 318 instruction sets the control program name
  code (CPNC) and control program version code (CPVC) to provide useful
  information regarding the OS during debugging.

  * The CPNC is explicitly set to 4 to indicate a Linux/KVM environment.

  [Fix]

  * In general the following 4 commits are needed:

  * 3fd8417f2c728d810a3b26d7e2008012ffb7fd01 3fd8417f2c72 "KVM: s390: add debug 
statement for diag 318 CPNC data"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545726/+files/0004-KVM-s390-add-debug-statement-for-diag-318-CPNC-data.patch

  * 6cbf1e960fa52e4c63a6dfa4cda8736375b34ccc 6cbf1e960fa5 "KVM: s390: remove 
diag318 reset code"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545725/+files/0003-KVM-s390-remove-diag318-reset-code.patch

  * 23a60f834406c8e3805328b630d09d5546b460c1 23a60f834406 "s390/kvm: diagnose 
0x318 sync and reset"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545724/+files/0002-s390-kvm-diagnose-0x318-sync-and-reset.patch

  * a23816f3cdcbffe5dc6e8c331914b3f51b87c2f3 a23816f3cdcb "s390/setup: diag 
318: refactor struct"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545723/+files/0001-s390-setup-diag-318-refactor-struct.patch

  * For jammy, hirsute and impish only the first commit is needed, the
  others are already in.

  * For focal all 4 commits are needed, but since they do not apply
  cleanly on focal, the attached backports need to be used instead.

  [Test Case]

  * Setup an IBM Z or LinuxONE LPAR with Ubuntu Server as KVM host.

  * And setup an Ubuntu KVM virtual on top.

  * It can then be observed if the CPNC (diag318 data) has been
  successfully set by looking at the s390dbf messages for the KVM guest.

  * The CPNC will always be 4 (denotes Linux environment).

  * Another way to test this is by running the sync_regs_test under
  tools/testing/selftests/kvm/s390x/sync_regs_test.   Just running the
  kernel self test suite can trigger this.

  [Where problems could occur]

  * The approach here is to provide additional debug and diagnose
  information on top.

  * Hence even if the diag318 changes are broken, the existing
  functionality shouldn't be harmed.

  * The changes themselves are relatively discernible and mostly
  introduce new structures.

  * However, with the functional changes broken code could be introduced
  (e.g. due to erroneous pointer arithmetic for example) that does not
  compile or causes crashes. But this is what the test builds are for
  (https://launchpad.net/~fheimes/+archive/ubuntu/lp1953334).

  * On top the diag318 diagnose data might not properly provided - maybe
  empty or wrong. Again that is what the test builds and the
  verification later is targeted at.

  * Since diag318 is s390x specific, all the modifications touch s390x
  code only. (in arch/s390/kvm/ kvm-s390.c and vsie.c,
  arch/s390/kernel/setup.c, arch/s390/include/asm/ kvm_host.h, kvm.h and
  diag.h). At least no other other architecture will be affected.

  * Well, there is one tiny bit of a common code change, but it's just a
  new define statement in include/uapi/linux/kvm.h ('#define
  KVM_CAP_S390_DIAG318 186').

  [Other]

  * Request was to add the patches to focal / 20.04, but to avoid
  potential regressions on upgrades, the patches need to be added to
  jammy, impish and hirsute, too.

  * As mentioned above, Jammy, Hirsute and Impish includes almost
  everything needed, except 3fd8417f2c72 "KVM: s390: add debug statement
  for diag 318 CPNC data".

  * Hence the SRU is for Focal, Jammy, Hirsute and Impish, but less
  invasive for Jammy, Hirsute and Impish, also because commit
  3fd8417f2c72 can be cleanly cherry-picked form there.

  * LP#1953338 is related to this bug and covers the qemu/KVM bits.
  __

  Hardware diagnose data (diag 318) of KVM guest kernel cannot be handled.
  Fix needed to enhance problem determination of guest 

[Kernel-packages] [Bug 1954773] Re: New fix for jack detection after resume on CS8409 sound driver

[Kelsey Skunberg]

Hi Chris, may you please verify if this bug is resolved for the impish
kernel in -proposed too? Thank you!

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

Title:
  New fix for jack detection after resume on CS8409 sound driver

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

Bug description:
  [SRU Justification]

  [Impact]
  On some platforms with Cirrus CS8409 audio codec, the external headset will 
fail to be detected after system resume.

  [Fix]
  Cirrus released a new fix commit 65cc4ad62a9e ('ALSA: hda/cs8409: Set PMSG_ON 
earlier inside cs8409 driver'). It sets the power_state to ON before the 
unsolicited event arrives to make sure the jack detection can be invoked after 
resume.

  [Test]
  Plug-in an external headset in front headset port, suspend/resume the system 
then check whether the headset function works as expected.

  [Where problem could occur]
  Low. It only affect the platforms with Cirrus codec CS8409 which used to have 
problem.

  == Original Bug Description ==

  [Summary] System can't detect external headset after suspend

  [Steps to reproduce]
  1. install manifest and boot into OS
  2. plug-in an external headset in front headset port
  3. un-plug external headset
  4. suspend system
  5. resume system from suspend
  6. plug-in an external headset

  [Expected result]
  System could detect external headset after suspend

  [Actual result]
  System can't detect external headset after suspend

  [Failure rate]
  3/3

  [Additional information]
  CID: 202110-29567
  SKU: DLPV-SFF-DVT-C1
  Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-davos-adl+X152
  system-manufacturer: Dell Inc.
  system-product-name: Vostro 3710
  bios-version: 0.13.73
  CPU: 12th Gen Intel(R) Core(TM) i7-12700 (20x)
  GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:4680] (rev 0c)
  kernel-version: 5.13.0-1019-oem

  [Stage]
  Issue reported and logs collected right after it happened

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


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

[Kernel-packages] [Bug 1945461] Re: Integrated TSN controller (stmmac/i225) driver support

[Anthony Wong]

** Summary changed:

- Integrated TSN controller
+ Integrated TSN controller (stmmac/i225) driver support

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

Title:
  Integrated TSN controller (stmmac/i225) driver support

Status in HWE Next:
  Fix Released
Status in linux-intel-5.13 package in Ubuntu:
  Invalid
Status in linux-intel-5.13 source package in Focal:
  Fix Released

Bug description:
  Tracking bug, please don't triage.

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


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

[Kernel-packages] [Bug 1957753] Re: net/mlx5e: EPERM on vlan 0 programming

[Po-Hsu Lin]

Awesome!
I will send the SRU request out, thanks for testing!

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

Title:
  net/mlx5e: EPERM on vlan 0 programming

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in linux source package in Hirsute:
  Confirmed
Status in linux source package in Impish:
  Confirmed
Status in linux source package in Jammy:
  Confirmed

Bug description:
  There is an issue with hypervisor host side mlx5 driver operation on
  Bluefield devices in kernels <=5.16 that was recently fixed in master
  with a one-liner:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37

  It would be good to have this fix in Focal+ kernels.

  This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux-
  bluefield since it's used at the DPU side whereas the issue in
  question affects the hypervisor side.

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


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

[Kernel-packages] [Bug 1958620] Re: Flickering white/black screen once KMS comes up

[Daniel van Vugt]

Interesting dual GPU setup. In theory GNOME should be using the primary
GPU (Intel) only.

One exception to that would be if you have a monitor plugged into one of
the AMD GPU ports, in which case scanout would be via AMD but the
rendering still on Intel.

Can we be sure amdgpu is not involved at all here?

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

Title:
  Flickering white/black screen once KMS comes up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This looks like a regression from the 5.13.0-20-generic kernel to the
  5.15.0-17-generic kernel. The display works fine under efifb, but as
  soon as the DRM drivers are loaded and KMS kicks in the display is
  replaced by black with flickering white (apparently when what would be
  on the output changes).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  7134 F pipewire-media-
   /dev/snd/seq:chris  7133 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 21 17:07:08 2022
  InstallationDate: Installed on 2021-06-26 (208 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
  MachineType: Dell Inc. XPS 15 9575
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash
  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-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.204
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago)
  dmi.bios.date: 07/07/2019
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  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/1958620/+subscriptions


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

[Kernel-packages] [Bug 1924298] Re: accept returns duplicate endpoints under load

[Seth Arnold]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Public Security to Public

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

Title:
  accept returns duplicate endpoints under load

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

Bug description:
  When accepting client connections under load, duplicate endpoints may
  be returned. These endpoints will have different (usually sequential)
  file descriptors but will refer to the same connection (same server
  IP, same server port, same client IP, same client port). Both copies
  of the endpoint appear to be functional.

  Reproduction requires:
  - compilation of the attached server.c program
  - wrk (https://github.com/wg/wrk) to generate load

  The steps to reproduce are:
  - run 'server' application in one console window
  - run 'for i in {1..50}; do /opt/wrk/wrk -t 2 -c 1000 -d 5s --latency 
--timeout 1s http://localhost:/post; done' in a second console window
  - run the same command in a third window to generate concurrent load

  You may need to run additional instance of the wrk command in multiple
  windows to trigger the issue.

  When the problem occurs the server executable will exit and print some 
debugging info. e.g.:
  accerror = 1950892, counter = 10683, port = 59892, clientfd = 233, lastClient 
= 232

  This indicates that the sockets with file descriptors 233 and 232 are
  duplicates.

  The issue has been reproduced on fully patched versions of Ubuntu
  20.04 and 18.04. Other versions have not been tested.

  This issue was originally observed in Java and was reported against the 
Spring Framework:
  https://github.com/spring-projects/spring-framework/issues/26434

  Investigation from the Spring team and the Apache Tomcat team identified that 
it appeared to be a JDK issue:
  https://bugs.openjdk.java.net/browse/JDK-8263243

  Further research from the JDK team determined that the issue was at
  the OS level. Hence this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-71-generic 5.4.0-71.79
  ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101
  Uname: Linux 5.4.0-71-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 15 12:52:53 2021
  HibernationDevice: RESUME=UUID=f5a46e09-d99b-4475-8ab6-2cd70da8418d
  InstallationDate: Installed on 2017-02-02 (1532 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   lono wireless extensions.
   
   docker0   no wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-71-generic 
root=/dev/mapper/ubuntu--vg-root ro text
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-71-generic N/A
   linux-backports-modules-5.4.0-71-generic  N/A
   linux-firmware1.187.10
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-09-07 (219 days ago)
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22
  dmi.board.asset.tag: Default string
  dmi.board.name: X99-SLI-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.:bvrF22:bd06/13/2016:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  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/linux/+bug/1924298/+subscriptions


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

[Kernel-packages] [Bug 1958412] Re: [amdgpu] at startup and shutdown screen gets white noise

[Daniel van Vugt]

I agree this bug is not well described. It could do with better wording.
But keeping bug 1958591 open separately is probably not helpful.

** Summary changed:

- [amdgpu] at startup and shutdown screen gets white noise
+ [amdgpu] Flickering/noise on screen started in kernel 5.13

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

Title:
  [amdgpu] Flickering/noise on screen started in kernel 5.13

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

Bug description:
  After the kernel release 5.13.0-27-generic was installed today, the
  startup and shutdown processes finish with white noise screens.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Jan 19 16:17:35 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:164c] (rev c2) (prog-if 
00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:18b2]
  InstallationDate: Installed on 2022-01-19 (0 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop TP420UA_TM420UA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=c4ec4ae8-c14c-4c0b-9922-9142270cef97 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/06/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: TP420UA.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP420UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.2
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrTP420UA.302:bd09/06/2021:br5.19:efr3.2:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopTP420UA_TM420UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP420UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:
  dmi.product.family: VivoBook Flip
  dmi.product.name: VivoBook_ASUSLaptop TP420UA_TM420UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Kernel-packages] [Bug 1958890] Re: [amdgpu] the screen is flickering after waking up from sleep

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1958412, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1958412
   [amdgpu] Flickering/noise on screen started in kernel 5.13

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

Title:
  [amdgpu] the screen is flickering after waking up from sleep

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

Bug description:
  the screen is flcikering after waking up from sleep

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 24 23:04:53 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: amdgpu, 5.6.0.15-1098277: added
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:164c] (rev c1) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3f95]
  InstallationDate: Installed on 2022-01-11 (12 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: LENOVO 82KT
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=7e63c3e2-afff-4841-8da3-9dad122a8352 ro nouveau.modeset=0 quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 07/23/2021
  dmi.bios.release: 1.40
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLCN40WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55726WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 3 14ALC6
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLCN40WW:bd07/23/2021:br1.40:efr1.40:svnLENOVO:pn82KT:pvrIdeaPad314ALC6:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55726WIN:cvnLENOVO:ct10:cvrIdeaPad314ALC6:skuLENOVO_MT_82KT_BU_idea_FM_IdeaPad314ALC6:
  dmi.product.family: IdeaPad 3 14ALC6
  dmi.product.name: 82KT
  dmi.product.sku: LENOVO_MT_82KT_BU_idea_FM_IdeaPad 3 14ALC6
  dmi.product.version: IdeaPad 3 14ALC6
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Kernel-packages] [Bug 1958850] Re: USB port lost function after unplugging usb drive

[Kai-Chuan Hsieh]

** Tags added: somerville

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

Title:
  USB port lost function after unplugging usb drive

Status in OEM Priority Project:
  New
Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  Test the proposed 5.14 oem kernel, and get a failure symptom.

  Unplug a usb drive from WD19TB docking and a BUG reported in kernel,
  then the other embedded usb port can't detect usb drive anymore after
  a while.

  kernel: usb 5-2.3.3: USB disconnect, device number 5
  kernel: BUG: kernel NULL pointer dereference, address: 0030
  kernel: #PF: supervisor read access in kernel mode
  kernel: #PF: error_code(0x) - not-present page
  kernel: PGD 0 P4D 0
  kernel: Oops:  [#1] SMP NOPTI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  2205 F pulseaudio
   /dev/snd/controlC0:  u  2205 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-04-29 (270 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. Precision 5750
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem 
root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-1021-oem N/A
   linux-backports-modules-5.14.0-1021-oem  N/A
   linux-firmware   1.201.3
  Tags:  impish
  Uname: Linux 5.14.0-1021-oem x86_64
  UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990:
  dmi.product.family: Precision
  dmi.product.name: Precision 5750
  dmi.product.sku: 0990
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1958890] Re: Xorg freeze

[Daniel van Vugt]

** Tags added: amdgpu

** Package changed: xorg (Ubuntu) => linux-hwe-5.13 (Ubuntu)

** Summary changed:

- Xorg freeze
+ [amdgpu] the screen is flickering after waking up from sleep

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

Title:
  [amdgpu] the screen is flickering after waking up from sleep

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

Bug description:
  the screen is flcikering after waking up from sleep

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 24 23:04:53 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: amdgpu, 5.6.0.15-1098277: added
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:164c] (rev c1) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3f95]
  InstallationDate: Installed on 2022-01-11 (12 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: LENOVO 82KT
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=7e63c3e2-afff-4841-8da3-9dad122a8352 ro nouveau.modeset=0 quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 07/23/2021
  dmi.bios.release: 1.40
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLCN40WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55726WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 3 14ALC6
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLCN40WW:bd07/23/2021:br1.40:efr1.40:svnLENOVO:pn82KT:pvrIdeaPad314ALC6:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55726WIN:cvnLENOVO:ct10:cvrIdeaPad314ALC6:skuLENOVO_MT_82KT_BU_idea_FM_IdeaPad314ALC6:
  dmi.product.family: IdeaPad 3 14ALC6
  dmi.product.name: 82KT
  dmi.product.sku: LENOVO_MT_82KT_BU_idea_FM_IdeaPad 3 14ALC6
  dmi.product.version: IdeaPad 3 14ALC6
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Kernel-packages] [Bug 1958890] [NEW] Xorg freeze

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

the screen is flcikering after waking up from sleep

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 24 23:04:53 2022
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: amdgpu, 5.6.0.15-1098277: added
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a day
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Since before I upgraded
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:164c] (rev c1) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo Device [17aa:3f95]
InstallationDate: Installed on 2022-01-11 (12 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
MachineType: LENOVO 82KT
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=7e63c3e2-afff-4841-8da3-9dad122a8352 ro nouveau.modeset=0 quiet 
splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLogOld:
 
dmi.bios.date: 07/23/2021
dmi.bios.release: 1.40
dmi.bios.vendor: LENOVO
dmi.bios.version: GLCN40WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0Q55726WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad 3 14ALC6
dmi.ec.firmware.release: 1.40
dmi.modalias: 
dmi:bvnLENOVO:bvrGLCN40WW:bd07/23/2021:br1.40:efr1.40:svnLENOVO:pn82KT:pvrIdeaPad314ALC6:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55726WIN:cvnLENOVO:ct10:cvrIdeaPad314ALC6:skuLENOVO_MT_82KT_BU_idea_FM_IdeaPad314ALC6:
dmi.product.family: IdeaPad 3 14ALC6
dmi.product.name: 82KT
dmi.product.sku: LENOVO_MT_82KT_BU_idea_FM_IdeaPad 3 14ALC6
dmi.product.version: IdeaPad 3 14ALC6
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.105-3~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 amdgpu apport-bug focal freeze ubuntu
-- 
Xorg freeze
https://bugs.launchpad.net/bugs/1958890
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-hwe-5.13 in Ubuntu.

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

[Kernel-packages] [Bug 1958787] Re: CRASH - [drm:amd gpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

[Seth Arnold]

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

** Information type changed from Private Security to Public

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

Title:
  CRASH - [drm:amd gpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
  parser -125!

Status in linux package in Ubuntu:
  New

Bug description:
  While watching a video form hard drive with vlc i got this complete crash of 
my machine!
  I wasn't able to do anything in the GUI with keyboard and/or mouse , all 
input where gone

  Going to TTY1 and killing vlc did not change anything.
  I had to reboot hard.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: vlc 3.0.16-1
  ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sun Jan 23 20:31:02 2022
  InstallationDate: Installed on 2020-12-28 (391 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: vlc
  UpgradeStatus: Upgraded to impish on 2021-11-28 (56 days ago)

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


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

[Kernel-packages] [Bug 1958933] [NEW] HDMI sound not available in driver amdgpu in linux kernel version >=5.11

[RNZ]

Public bug reported:

After upgrade kernel 5.8 -> 5.11 (and 5.13) - HDMI sound not available
with driver amdgpu and RX 5700 XT

Bug: https://gitlab.freedesktop.org/drm/amd/-/issues/1536
Regression confirmation: 
https://gitlab.freedesktop.org/drm/amd/-/issues/1536#note_1060547

```
$ xrandr | grep ' connected'
DisplayPort-0 connected 2560x1440+0+0 (normal left inverted right x axis y 
axis) 698mm x 393mm

$ cat /sys/class/drm/card0-DP-1/edid | edid-decode | egrep 'Display Product 
Name|Manufacturer|DTD'
Manufacturer: IVM
DTD 1:  2560x1440   59.951 Hz  16:988.787 kHz 241.500 MHz (698 mm x 393 
mm)
Display Product Name: 'PL3270Q'
DTD 2:  1920x1080   60.000 Hz  16:967.500 kHz 148.500 MHz (698 mm x 393 
mm)
DTD 3:  1920x1080i  60.000 Hz  16:933.750 kHz  74.250 MHz (698 mm x 393 
mm)
DTD 4:  1280x72060.000 Hz  16:945.000 kHz  74.250 MHz (698 mm x 393 
mm)
DTD 5:   720x48059.940 Hz   3:231.469 kHz  27.000 MHz (698 mm x 393 
mm)

$ cat /sys/class/drm/card0-DP-1/edid | edid-decode | grep -A6 Audio
  Audio Data Block:
Linear PCM:
  Max channels: 2
  Supported sample rates (kHz): 48 44.1 32
  Supported sample sizes (bits): 24 20 16
  Speaker Allocation Data Block:
FL/FR - Front Left/Right

$ pactl list cards short
40  
alsa_card.usb-Creative_Technology_Ltd._VF0700_Live__Cam_Chat_HD_3C120119-02 
alsa
47  bluez_card.00_16_94_3F_BB_C7module-bluez5-device.c
```


ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-27-generic 5.13.0-27.29
ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19
Uname: Linux 5.13.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  rnz5186 F pipewire-media-
 /dev/snd/seq:rnz5185 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Tue Jan 25 02:18:01 2022
InstallationDate: Installed on 2015-05-01 (2460 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-27-generic 
root=UUID=e4e7aa28-c520-4902-86a3-0de1cf7fc9da ro acpi_enforce_resources=lax 
amd_iommu=on iommu=pt iommu=1
RelatedPackageVersions:
 linux-restricted-modules-5.13.0-27-generic N/A
 linux-backports-modules-5.13.0-27-generic  N/A
 linux-firmware 1.201.3
SourcePackage: linux
UpgradeStatus: Upgraded to impish on 2021-11-19 (66 days ago)
dmi.bios.date: 10/14/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F36e
dmi.board.asset.tag: Default string
dmi.board.name: X570 AORUS ELITE
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36e:bd10/14/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: X570 MB
dmi.product.name: X570 AORUS ELITE
dmi.product.sku: Default string
dmi.product.version: -CF
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2015-10-26T22:19:16.074320

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


** Tags: amd64 apport-bug impish

** Description changed:

  After upgrade kernel 5.8 -> 5.11 (and 5.13) - HDMI sound not available
  with driver amdgpu and RX 5700 XT
  
  Bug: https://gitlab.freedesktop.org/drm/amd/-/issues/1536
  Regression confirmation: 
https://gitlab.freedesktop.org/drm/amd/-/issues/1536#note_1060547
  
  ```
  $ xrandr | grep ' connected'
  DisplayPort-0 connected 2560x1440+0+0 (normal left inverted right x axis y 
axis) 698mm x 393mm
  
  $ cat /sys/class/drm/card0-DP-1/edid | edid-decode | egrep 'Display Product 
Name|Manufacturer|DTD'
- Manufacturer: IVM
- DTD 1:  2560x1440   59.951 Hz  16:988.787 kHz 241.500 MHz (698 mm x 
393 mm)
- Display Product Name: 'PL3270Q'
- DTD 2:  1920x1080   60.000 Hz  16:967.500 kHz 148.500 MHz (698 mm x 
393 mm)
- DTD 3:  1920x1080i  60.000 Hz  16:933.750 kHz  74.250 MHz (698 mm x 
393 mm)
- DTD 4:  1280x72060.000 Hz  16:945.000 kHz  74.250 MHz (698 mm x 
393 mm)
- DTD 5:   720x48059.940 Hz   3:231.469 kHz  27.000 MHz (698 mm x 
393 mm)
+ Manufacturer: IVM
+ DTD 1:  2560x1440   59.951 Hz  16:988.787 kHz 241.500 MHz (698 mm x 
393 mm)
+  

[Kernel-packages] [Bug 1686099] Re: connection flood to port 445 on mounting cifs volume under kernel

[Casper]

Has this bug been fixed in Ubuntu 18.04?
I seem to have the same issue (kernel 4.15.0-34).

I do not have any SMB drives mounted, yet old connections from several
months ago are open and still flooding 445:

> sudo netstat -tnp | grep 445
tcp0  0 x.x.x.x:54508a.a.a.a:445 ESTABLISHED -
tcp0  0 x.x.x.x:60350b.b.b.b:445 ESTABLISHED -
tcp0  0 x.x.x.x:56534c.c.c.c:445 ESTABLISHED -

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

Title:
  connection flood to port 445 on mounting cifs volume under kernel

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  This is identical to the bug reported on the Debian kernel list, only
  I'm running 4.4.0, not 4.[89].0

  After about 15 mintues, the cifsd daemon starts flooding echo requests
  on port 445 to the windows server causing a constant 1MB/s load
  (around 10,000 packets per second) that eventually leads to system
  instability that forces a reboot to correct.  This is repeatable and
  as far as I know started about a week ago (possibly with the
  installation of 4.4.0-75).

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856843

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


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

[Kernel-packages] [Bug 1958918] Re: dependency on crda obsolete according to Debian

[Bug Watch Updater]

** Changed in: crda (Debian)
   Status: Unknown => Fix Released

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

Title:
  dependency on crda obsolete according to Debian

Status in crda package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in crda source package in Jammy:
  New
Status in linux source package in Jammy:
  New
Status in crda package in Debian:
  Fix Released

Bug description:
  Debian has just removed the crda package from the archive, stating
  that it is obsolete with current kernels:

https://bugs.debian.org/1003903

  We need someone to determine if this is accurate for Ubuntu as well,
  and if so, update the kernel packaging to not depend on crda anymore
  so it can be removed.

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


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

[Kernel-packages] [Bug 1947568] Re: cannot promote clone: "not a cloned filesystem"

[Some Guy On The Net]

https://bugs.launchpad.net/ubuntu/+source/zfs-
linux/+bug/1947568/comments/1

This is my exact issue as well, elbit using a focal based distro -
Zorin:

$ lsb_release -a
No LSB modules are available.
Distributor ID: Zorin
Description:Zorin OS 16
Release:16
Codename:   focal

$ uname -r
5.13.0-27-generic

$ apt-cache policy zfsutils-linux
zfsutils-linux:
  Installed: 0.8.3-1ubuntu12.13
  Candidate: 0.8.3-1ubuntu12.13
  Version table:
 *** 0.8.3-1ubuntu12.13 500
500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 0.8.3-1ubuntu12.9 500
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
 0.8.3-1ubuntu12 500
500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages

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

Title:
  cannot promote clone: "not a cloned filesystem"

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  I have a zvol containing a Windows image for a virtual machine.  After
  restarting the system a node under /dev/zvol/... was not created for
  the virtual disk and no amount of prompting by `udevadm trigger`
  helped.  Instead I created a snapshot from the most recent hourly
  backup:

  # zfs clone rpool/vm/windows/windows10/hda@hourly07 
rpool/vm/windows/windows10/hda-new
  # zfs promote rpool/vm/windows/windows10/hda-new
  cannot promote 'rpool/vm/windows/windows10/hda-new': not a cloned filesystem
  (didn't work here but carried on assuming something can be sorted later)
  # zfs rename rpool/vm/windows/windows10/hda rpool/vm/windows/windows10/hda-old
  # zfs rename rpool/vm/windows/windows10/hda-new rpool/vm/windows/windows10/hda

  Entries in /dev appeared and I could start the virtual machine.
  Trying to promote the clone gives 'not a cloned filesystem' message.
  I later renamed the old zvol and tried to cleanup:

  # zfs rename rpool/vm/windows/windows10/hda-old rpool/to-be-deleted
  #  zfs destroy rpool/to-be-deleted@hourly07
  cannot destroy 'rpool/to-be-deleted@hourly07': snapshot has dependent clones
  use '-R' to destroy the following datasets:
  rpool/vm/windows/windows10/hda@hourly09
  rpool/vm/windows/windows10/hda@hourly10
  rpool/vm/windows/windows10/hda
  # zfs promote rpool/vm/windows/windows10/hda
  cannot promote 'rpool/vm/windows/windows10/hda': not a cloned filesystem

  # zfs get origin rpool/vm/windows/windows10/hda
  NAMEPROPERTY  VALUE SOURCE
  rpool/vm/windows/windows10/hda  originrpool/to-be-deleted@hourly07  -

  # zfs get clones rpool/to-be-deleted@hourly07
  NAME  PROPERTY  VALUE   SOURCE
  rpool/to-be-deleted@hourly07  clonesrpool/vm/windows/windows10/hda  -

  The dependency between seems to be as expected.  This small test fails
  in the same way:

  # zfs create -V1G rpool/vm/test
  # zfs snapshot rpool/vm/test@test2
  # zfs clone rpool/vm/test@test2 rpool/vm/test3
  # zfs promote rpool/vm/test3
  cannot promote 'rpool/vm/test3': not a cloned filesystem
  # zfs get origin rpool/vm/test3
  NAMEPROPERTY  VALUESOURCE
  rpool/vm/test3  originrpool/vm/test@test2  -
  # zfs get clones rpool/vm/test@test2
  NAME PROPERTY  VALUE   SOURCE
  rpool/vm/test@test2  clonesrpool/vm/test3  -

  All the zpool members are ONLINE and no errors are reported.

  # lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.3 LTS
  Release:20.04
  Codename:   focal

  # uname -r
  5.11.0-37-generic

  # modinfo zfs | grep -i version
  version:2.0.2-1ubuntu5.1
  srcversion: F267DF7B3FFB43AFE76257D
  vermagic:   5.11.0-37-generic SMP mod_unload modversions

  # apt-cache policy zfsutils-linux
  zfsutils-linux:
Installed: 0.8.3-1ubuntu12.12
Candidate: 0.8.3-1ubuntu12.13
Version table:
   0.8.3-1ubuntu12.13 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
   *** 0.8.3-1ubuntu12.12 100
  100 /var/lib/dpkg/status
   0.8.3-1ubuntu12.9 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   0.8.3-1ubuntu12 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

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


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

[Kernel-packages] [Bug 1957753] Re: net/mlx5e: EPERM on vlan 0 programming

[Dmitrii Shcherbakov]

And, finally, the Jammy kernel:

$ uname -r
5.15.0-17-generic

$ sudo ip link set enp130s0f0 vf 2 vlan 0 ; echo $?
0

$ sudo ip link set enp130s0f0 vf 2 vlan 1 ; echo $?
RTNETLINK answers: Operation not permitted
2


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

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

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

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

Title:
  net/mlx5e: EPERM on vlan 0 programming

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in linux source package in Hirsute:
  Confirmed
Status in linux source package in Impish:
  Confirmed
Status in linux source package in Jammy:
  Confirmed

Bug description:
  There is an issue with hypervisor host side mlx5 driver operation on
  Bluefield devices in kernels <=5.16 that was recently fixed in master
  with a one-liner:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37

  It would be good to have this fix in Focal+ kernels.

  This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux-
  bluefield since it's used at the DPU side whereas the issue in
  question affects the hypervisor side.

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


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

[Kernel-packages] [Bug 1958724] Re: System Shutdown and resume hangs since Kernel linux-image-5.13.0-23-generic

[Brian Clark]

I've confirmed that by rolling back to a prior kernel
(5.11.0-46-generic), the system shuts down normally.

Temp work around I used was to

>sudo vi /etc/default/grub

GRUB_DEFAULT=0
#GRUB_TIMEOUT_STYLE=hidden <-- comment this line
GRUB_TIMEOUT=10 <-- change this line to a value between 5 and 10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""

>sudo update-grub

This allows me to see the GRUB boot menu and then select "Advanced
options for Ubuntu" and then the kernel I want to boot

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

Title:
  System Shutdown and resume hangs since Kernel linux-
  image-5.13.0-23-generic

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

Bug description:
  Hi,

  on my Medion E14304 Ubuntu was working fine until Kernel 5.13.0.21.
  Since Version 5.13.0.23 System Shutdown and resume hangs. The System
  does not stop also after a long time.

  The last messages in recovery mode on the root console are:

  Reached target Power-off
  ... systemd-udevd[295]: ... Worker [311] processing SEQNUM=3047 is taking time
  Waiting for process systemd-udevd, systemd-udevd 

  Perhaps my attached dmesg and lsmod helps. All messages are in one file.
   
  Thank you very much.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 22 16:59:05 2022
  InstallationDate: Installed on 2021-12-25 (27 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  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/1958724/+subscriptions


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

[Kernel-packages] [Bug 1956518] Re: linux-firmware 1.187.24 may crash USB ports

[Alan H]

I'm seeing something that seems similar, but with 1.187.25, i think.
Is this related? https://ubuntuforums.org/showthread.php?t=2471244

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

Title:
  linux-firmware 1.187.24 may crash USB ports

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04
  5.4.0-92-generic

  linux-firmware:
Instalados: 1.187.24
Candidato:  1.187.24
Tabla de versión:
   *** 1.187.24 500
  500 http://es.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://es.archive.ubuntu.com/ubuntu focal-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1.187 500
  500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://es.archive.ubuntu.com/ubuntu focal/main i386 Packages

  linux-firmware 1.187.24 upgrade disabled all mainboard USB ports.
  USB keyboard and mouse stopped working on the next reboot after upgrade.
  I disconnected an USB bluetooth key from a back USB port, rebooted, and 
everything restored to normality.
  My personal conclusion: there is a bug in the bluetooth firmware update that 
may cause a general USB crash when an USB bluetooth key is connected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alvaro 2225 F pulseaudio
   /dev/snd/controlC0:  alvaro 2225 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Dependencies:
   
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=fd59aa5f-2c5c-44c8-9fd3-36c7b5ec516a
  InstallationDate: Installed on 2014-10-25 (2634 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  IwConfig:
   lono wireless extensions.
   
   enp7s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. B365M H
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-firmware 1.187.24
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-92-generic 
root=UUID=ff070320-7281-484d-a5d3-4a42ed9ed075 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-92-generic N/A
   linux-backports-modules-5.4.0-92-generic  N/A
   linux-firmware1.187.24
  RfKill:
   2: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-92-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-27 (623 days ago)
  UserGroups: adm boinc cdrom dip lpadmin netdev plugdev render sambashare sudo 
video
  _MarkForUpload: True
  dmi.bios.date: 08/18/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4b
  dmi.board.asset.tag: Default string
  dmi.board.name: B365M H
  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.:bvrF4b:bd08/18/2020:svnGigabyteTechnologyCo.,Ltd.:pnB365MH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B365M H
  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-firmware/+bug/1956518/+subscriptions


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

[Kernel-packages] [Bug 1954757] Re: Missing overlays/README

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-raspi/5.4.0-1051.57
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-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1954757

Title:
  Missing overlays/README

Status in linux-raspi package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  Invalid
Status in linux-raspi source package in Focal:
  Fix Committed
Status in linux-raspi source package in Hirsute:
  Fix Committed
Status in linux-raspi source package in Impish:
  Fix Committed

Bug description:
  [ Impact ]

  overlays/README is used by the 'dtoverlay' command to display info on
  available overlays and params.

  [ Test Case ]

  $ apt install libraspberrypi-bin
  $ dtoverlay -h uart0
  * Help file not found

  With the README present:
  $ dtoverlay -h uart0
  Name:   uart0

  Info:   Change the pin usage of uart0

  Usage:  dtoverlay=uart0,=

  Params: txd0_pinGPIO pin for TXD0 (14, 32 or 36 -
  default 14)

  rxd0_pinGPIO pin for RXD0 (15, 33 or 37 -
  default 15)

  pin_funcAlternative pin function - 4(Alt0) for 14&15,
  7(Alt3) for 32&33, 6(Alt2) for 36&37

  [ Where Problems Could Occur ]

  The output of the `dtoverlay` could be wrong but it's only
  informational so should have no negative impact.

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


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

[Kernel-packages] [Bug 1948807] Re: Boot time from snap in 20/stable increases boot time on 3.5 seconds

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-raspi/5.4.0-1051.57
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-raspi-5.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1948807

Title:
  Boot time from snap in 20/stable increases boot time on 3.5 seconds

Status in linux-raspi package in Ubuntu:
  Invalid
Status in linux-raspi-5.4 package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi-5.4 source package in Bionic:
  Fix Committed
Status in linux-raspi2 source package in Bionic:
  Fix Committed
Status in linux-raspi source package in Focal:
  Fix Committed
Status in linux-raspi source package in Hirsute:
  Fix Committed
Status in linux-raspi source package in Impish:
  Fix Committed

Bug description:
  [ Impact ]

  I am seeing what looks as a regression in pi-kernel snap for UC20:
  there are around 3.5 additional seconds spent in boot time. In the
  image from cdimage (2021-06-30), I see:

  [1.856540] random: crng init done
  [1.871798] loop: module loaded

  (see https://paste.ubuntu.com/p/CkfWXY5Vgf/)
  while if I build an image from latest snaps in the 20/stable channel, I get:

  [1.855481] random: crng init done
  [5.349491] loop: module loaded

  (see https://paste.ubuntu.com/p/CNt42gdDcZ/)
  The pi-kernel snap revision is 353.

  [ Test Case ]

  $ sudo dmesg | grep -B1 -A1 'loop: module'
  [0.791122] cacheinfo: Unable to detect cache hierarchy for CPU 0
  [4.903386] loop: module loaded
  [4.906092] spi-bcm2835 fe204000.spi: could not get clk: -517

  [ Fix ]

  Set CONFIG_BLK_DEV_LOOP_MIN_COUNT to the default value (8).

  [ Where Problems Could Occur ]

  Loop devices need to be created on-demand if more than 8 are required.
  If that fails, user space will fail.

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


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

[Kernel-packages] [Bug 1957753] Re: net/mlx5e: EPERM on vlan 0 programming

[Dmitrii Shcherbakov]

Impish kernel looks good:

$ uname -r
5.13.0-28-generic

$ sudo ip link set enp130s0f0 vf 2 vlan 1 ; echo $?
RTNETLINK answers: Operation not permitted
2

$ sudo ip link set enp130s0f0 vf 2 vlan 0 ; echo $?
0

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

Title:
  net/mlx5e: EPERM on vlan 0 programming

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Incomplete
Status in linux source package in Hirsute:
  New
Status in linux source package in Impish:
  Incomplete
Status in linux source package in Jammy:
  Incomplete

Bug description:
  There is an issue with hypervisor host side mlx5 driver operation on
  Bluefield devices in kernels <=5.16 that was recently fixed in master
  with a one-liner:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37

  It would be good to have this fix in Focal+ kernels.

  This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux-
  bluefield since it's used at the DPU side whereas the issue in
  question affects the hypervisor side.

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


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

[Kernel-packages] [Bug 1958918] Re: dependency on crda obsolete according to Debian

[Steve Langasek]

** Bug watch added: Debian Bug tracker #1003903
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003903

** Also affects: crda (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003903
   Importance: Unknown
   Status: Unknown

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

Title:
  dependency on crda obsolete according to Debian

Status in crda package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in crda source package in Jammy:
  New
Status in linux source package in Jammy:
  New
Status in crda package in Debian:
  Unknown

Bug description:
  Debian has just removed the crda package from the archive, stating
  that it is obsolete with current kernels:

https://bugs.debian.org/1003903

  We need someone to determine if this is accurate for Ubuntu as well,
  and if so, update the kernel packaging to not depend on crda anymore
  so it can be removed.

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


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

[Kernel-packages] [Bug 1923104] Re: Include Infiniband Peer Memory interface

[Ian May]

Tested on Focal 5.4.0-97.110, confirmed inbox peer memory interface is
working.

** 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1923104

Title:
  Include Infiniband Peer Memory interface

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

Bug description:
  The peer_memory_client scheme allows a driver to register with the ib_umem 
system that it has the ability to understand user virtual address ranges that 
are not compatible with get_user_pages(). For instance VMAs created with 
io_remap_pfn_range(), or other driver special VMA.
  
  For ranges the interface understands it can provide a DMA mapped sg_table for 
use by the ib_umem, allowing user virtual ranges that cannot be supported by 
get_user_pages() to be used as umems for RDMA.
  
  This is designed to preserve the kABI, no functions or structures are 
changed, only new symbols are added:

   ib_register_peer_memory_client
   ib_unregister_peer_memory_client
   ib_umem_activate_invalidation_notifier
   ib_umem_get_peer

  And a bitfield in struct ib_umem uses more bits.

  This interface is compatible with the two out of tree GPU drivers:
   
https://github.com/RadeonOpenCompute/ROCK-Kernel-Driver/blob/master/drivers/gpu/drm/amd/amdkfd/kfd_peerdirect.c
   https://github.com/Mellanox/nv_peer_memory/blob/master/nv_peer_mem.c

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


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

[Kernel-packages] [Bug 1958917] Re: dependency on crda obsolete according to Debian

[Steve Langasek]

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

** This bug has been marked a duplicate of bug 1958918
   dependency on crda obsolete according to Debian

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

Title:
  dependency on crda obsolete according to Debian

Status in linux package in Ubuntu:
  New

Bug description:
  Debian has just removed the crda package from the archive, stating
  that it is obsolete with current kernels:

https://bugs.debian.org/1003903

  We need someone to determine if this is accurate for Ubuntu as well,
  and if so, update the kernel packaging to not depend on crda anymore
  so it can be removed.

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


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

[Kernel-packages] [Bug 1958918] Re: dependency on crda obsolete according to Debian

[Andy Whitcroft]

Looks very much that since 4.15 we can and have been loading the
regulatory.db via the firmware interface.  Once confirmed we should be
able to drop the dependency on crda|wireless-crda and replace it with
wireless-regdb.

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Andy Whitcroft (apw)

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

Title:
  dependency on crda obsolete according to Debian

Status in crda package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in crda source package in Jammy:
  New
Status in linux source package in Jammy:
  New
Status in crda package in Debian:
  Unknown

Bug description:
  Debian has just removed the crda package from the archive, stating
  that it is obsolete with current kernels:

https://bugs.debian.org/1003903

  We need someone to determine if this is accurate for Ubuntu as well,
  and if so, update the kernel packaging to not depend on crda anymore
  so it can be removed.

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


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

[Kernel-packages] [Bug 1958917] [NEW] dependency on crda obsolete according to Debian

[Steve Langasek]

Public bug reported:

Debian has just removed the crda package from the archive, stating that
it is obsolete with current kernels:

  https://bugs.debian.org/1003903

We need someone to determine if this is accurate for Ubuntu as well, and
if so, update the kernel packaging to not depend on crda anymore so it
can be removed.

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

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

Title:
  dependency on crda obsolete according to Debian

Status in linux package in Ubuntu:
  New

Bug description:
  Debian has just removed the crda package from the archive, stating
  that it is obsolete with current kernels:

https://bugs.debian.org/1003903

  We need someone to determine if this is accurate for Ubuntu as well,
  and if so, update the kernel packaging to not depend on crda anymore
  so it can be removed.

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


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

[Kernel-packages] [Bug 1958918] [NEW] dependency on crda obsolete according to Debian

[Steve Langasek]

Public bug reported:

Debian has just removed the crda package from the archive, stating that
it is obsolete with current kernels:

  https://bugs.debian.org/1003903

We need someone to determine if this is accurate for Ubuntu as well, and
if so, update the kernel packaging to not depend on crda anymore so it
can be removed.

** Affects: crda (Ubuntu)
 Importance: High
 Status: New

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

** Affects: crda (Ubuntu Jammy)
 Importance: High
 Status: New

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

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

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

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

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

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

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

Title:
  dependency on crda obsolete according to Debian

Status in crda package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in crda source package in Jammy:
  New
Status in linux source package in Jammy:
  New

Bug description:
  Debian has just removed the crda package from the archive, stating
  that it is obsolete with current kernels:

https://bugs.debian.org/1003903

  We need someone to determine if this is accurate for Ubuntu as well,
  and if so, update the kernel packaging to not depend on crda anymore
  so it can be removed.

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


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

[Kernel-packages] [Bug 1958778] Re: [amdgpu] Laptop not waking up from suspend

[Aaron Kriegman]

Yes, bug 1958591 is the exact same bug, except that if my computer
suspends without my monitor plugged in then the screen is black instead
of noisy when I try to wake it up.

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

Title:
  [amdgpu] Laptop not waking up from suspend

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

Bug description:
  Starting today my laptop will not wake up from suspend no matter what
  I try. After closing my laptop or leaving it alone for a while, the
  screen goes black like normal, but then no matter how much I mash the
  keyboard, touch the mouse, press the power button etc. the screen will
  not turn on. The power light is still on when this happens, so the
  computer is on. I've had to resort to holding the power button to
  restart every time.

  The behavior only changed (and got even weirder) when I plugged my
  monitor into my laptop. Things worked normally until my laptop went
  into standby. This time the monitor woke up as normal, and my laptop
  screen became filled with colorful static. I'm able to use the
  computer as normal on the monitor, which is how I'm filing this
  report.

  I should note that I installed routine updates yesterday through
  Software Updater, which is likely what triggered these issues. I also
  had a possibly related bug yesterday (after updating) where my
  laptop's fan stopped working. I restarted once and the fan still
  wouldn't turn on. I switched to my Windows partition and the fan
  started working. Then when I switched back to my Ubuntu partition the
  fan was working normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 23 17:11:50 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Renoir [17aa:3f1a]
  InstallationDate: Installed on 2021-08-04 (171 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 81X2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=464df196-22f9-4ea4-989d-dda2cb0a5ec5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2020
  dmi.bios.release: 1.31
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EECN31WW
  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: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad Flex 5 14ARE05
  dmi.ec.firmware.release: 1.20
  dmi.modalias: 
dmi:bvnLENOVO:bvrEECN31WW:bd12/18/2020:br1.31:efr1.20:svnLENOVO:pn81X2:pvrIdeaPadFlex514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrIdeaPadFlex514ARE05:skuLENOVO_MT_81X2_BU_idea_FM_IdeaPadFlex514ARE05:
  dmi.product.family: IdeaPad Flex 5 14ARE05
  dmi.product.name: 81X2
  dmi.product.sku: LENOVO_MT_81X2_BU_idea_FM_IdeaPad Flex 5 14ARE05
  dmi.product.version: IdeaPad Flex 5 14ARE05
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Kernel-packages] [Bug 1924298] Re: accept returns duplicate endpoints under load

[Brooke Hedrick]

We are seeing this error on Windows Server 2019

Jan 21, 2022 10:30:21 AM org.apache.tomcat.util.net.AprEndpoint setSocketOptions
SEVERE: Error allocating socket processor
java.io.IOException: Duplicate accept detected. This is a known OS bug. Please 
consider reporting that you are affected: 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924298
at 
org.apache.tomcat.util.net.AprEndpoint.setSocketOptions(AprEndpoint.java:811)
at 
org.apache.tomcat.util.net.AprEndpoint.setSocketOptions(AprEndpoint.java:83)
at org.apache.tomcat.util.net.Acceptor.run(Acceptor.java:149)
at java.base/java.lang.Thread.run(Thread.java:829)


Adoptium JDK jdk-11.0.13+8 64bit
Apache Tomcat 9.0.56
tomcat-native-1.2.31
openssl-1.1.1l
apr-1.7.0
apr-util-1.6.1

2022-01-21 09:58:59 Apache Commons Daemon procrun stdout initialized.
Jan 21, 2022 9:59:01 AM org.apache.catalina.core.AprLifecycleListener 
lifecycleEvent
INFO: Loaded Apache Tomcat Native library [1.2.31] using APR version [1.7.0].
Jan 21, 2022 9:59:01 AM org.apache.catalina.core.AprLifecycleListener 
lifecycleEvent
INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], 
random [true], UDS [true].
Jan 21, 2022 9:59:01 AM org.apache.catalina.core.AprLifecycleListener 
lifecycleEvent
INFO: APR/OpenSSL configuration: useAprConnector [false], useOpenSSL [true]
Jan 21, 2022 9:59:01 AM org.apache.catalina.core.AprLifecycleListener 
initializeSSL
INFO: OpenSSL successfully initialized [OpenSSL 1.1.1l  24 Aug 2021]
Jan 21, 2022 9:59:01 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-apr-0.0.0.0-x"]
Jan 21, 2022 9:59:01 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["https-openssl-apr-0.0.0.0-x"]
Jan 21, 2022 9:59:01 AM org.apache.tomcat.util.net.openssl.OpenSSLUtil 
getKeyManagers
Jan 21, 2022 9:59:01 AM org.apache.catalina.startup.Catalina load
INFO: Server initialization in [667] milliseconds
Jan 21, 2022 9:59:01 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service [Catalina]
Jan 21, 2022 9:59:01 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet engine: [Apache Tomcat/9.0.56]


AND We are seeing the error on Ubuntu 20.04.3 LTS

Jan 21, 2022 8:55:02 AM org.apache.tomcat.util.net.AprEndpoint setSocketOptions
SEVERE: Error allocating socket processor
java.io.IOException: Duplicate accept detected. This is a known OS bug. Please 
consider reporting that you are affected: 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924298
at 
org.apache.tomcat.util.net.AprEndpoint.setSocketOptions(AprEndpoint.java:811)
at 
org.apache.tomcat.util.net.AprEndpoint.setSocketOptions(AprEndpoint.java:83)
at org.apache.tomcat.util.net.Acceptor.run(Acceptor.java:149)
at java.base/java.lang.Thread.run(Thread.java:829)

Jan 21, 2022 7:08:11 AM org.apache.catalina.core.AprLifecycleListener 
lifecycleEvent
INFO: Loaded Apache Tomcat Native library [1.2.31] using APR version [1.7.0].
Jan 21, 2022 7:08:11 AM org.apache.catalina.core.AprLifecycleListener 
lifecycleEvent
INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], 
random [true], UDS [true].
Jan 21, 2022 7:08:11 AM org.apache.catalina.core.AprLifecycleListener 
lifecycleEvent
INFO: APR/OpenSSL configuration: useAprConnector [false], useOpenSSL [true]
Jan 21, 2022 7:08:11 AM org.apache.catalina.core.AprLifecycleListener 
initializeSSL
INFO: OpenSSL successfully initialized [OpenSSL 1.1.1l  24 Aug 2021]
Jan 21, 2022 7:08:11 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-apr-0.0.0.0-x"]
Jan 21, 2022 7:08:11 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["https-openssl-apr-0.0.0.0-x"]
Jan 21, 2022 7:08:11 AM org.apache.catalina.startup.Catalina load
INFO: Server initialization in [463] milliseconds
Jan 21, 2022 7:08:11 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service [Catalina]
Jan 21, 2022 7:08:11 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet engine: [Apache Tomcat/9.0.56]


We do NOT see this issue logged, by Tomcat, on the same Windows or Linux
O/S versions with

DIFF AdoptOpenJDK 11.0.10+9 64bit
DIFF Apache Tomcat 9.0.43
DIFF tomcat-native-1.2.26
DIFF openssl-1.1.1i
SAME apr-1.7.0
SAME apr-util-1.6.1

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

Title:
  accept returns duplicate endpoints under load

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

Bug description:
  When accepting client connections under load, duplicate endpoints may
  be returned. These endpoints will have different (usually sequential)
  file descriptors but will refer to the same connection (same server
  IP, same server port, same client IP, same 

[Kernel-packages] [Bug 1947455] Re: sub sub domain names not properly resolved

[Sergio Durigan Junior]

Thank you for taking the time to file a bug report.

Unfortunately I didn't understand the problem very well.  It seems to me
that this could be a local configuration issue, although you mentioned
that this was working before Impish.  Also, I noticed that you marked
the bug as Invalid for bind9.  Since it is extremely unlikely that this
is a Linux kernel bug, I will go ahead and mark the Linux kernel and the
Ubuntu tasks as Invalid as well.

If you are still experiencing a problem, feel free to explain what is
happening.  A reproducer would also go a long way here.

Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete description of the problem, explain why you
believe this is a bug in Ubuntu rather than a problem specific to your
system, and then change the bug status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

** Changed in: ubuntu
   Status: New => Invalid

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

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

Title:
  sub sub domain names not properly resolved

Status in Ubuntu:
  Invalid
Status in bind9 package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  I have a local lan with a libvirt server and on that a vpn
  I have a wildcard sub domain at freedns.afraid.org (sub.hostname.com)
  that has a kvm and vpn sub sub domain names. (sub.sub.hostname.com)

  If i ping the sub sub hostname outside my local lan i get my external IP 
address.
  but also if i ping from within my local lan network
  dig and nslookup do a resolve to my local ip.
  But ping and applications like openvpn and libvirt cant connect to the local 
application.

  I worked around it by registering two sub domains at
  freedns.afraid.org those are resolved correctly to the local IP
  address.

  No logs due to privacy.

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


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

[Kernel-packages] [Bug 1958914] [NEW] AMD GPU driver not loading.

[James Paton-Smith]

Public bug reported:

The video driver for my AMD GPU does not seem to be loading properly
with kernel 5.13. The GUI loads but is stuck with a low resolution.

Output of 'lspci -v' command seems to show that no graphics driver is in
use. I expect 'amdgpu' to be the selected driver for my GPU.

Everything works correctly if I restart the system and select the
previous kernel version (5.11.0-44).

Additional info:
I have linux-generic-hwe-20.04 meta package installed (currently at version 
5.13.0.27.29~20.04.13)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 24 19:02:21 2022
InstallationDate: Installed on 2021-11-17 (68 days ago)
InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210824)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
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 uec-images

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

Title:
  AMD GPU driver not loading.

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

Bug description:
  The video driver for my AMD GPU does not seem to be loading properly
  with kernel 5.13. The GUI loads but is stuck with a low resolution.

  Output of 'lspci -v' command seems to show that no graphics driver is
  in use. I expect 'amdgpu' to be the selected driver for my GPU.

  Everything works correctly if I restart the system and select the
  previous kernel version (5.11.0-44).

  Additional info:
  I have linux-generic-hwe-20.04 meta package installed (currently at version 
5.13.0.27.29~20.04.13)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 24 19:02:21 2022
  InstallationDate: Installed on 2021-11-17 (68 days ago)
  InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210824)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  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/1958914/+subscriptions


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

[Kernel-packages] [Bug 1772624] Re: Broadcom BCM4356 wifi chipset firmware is not working

[Hiroki Matsuura]

I opened new bug (Bug #1958911).

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

Title:
  Broadcom BCM4356 wifi chipset firmware is not working

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  After upgrading to Ubuntu 18.04 I got an issue with the wifi chipset
  (Broadcom BCM4356) not initializing properly.

  Here is the error I got when loading the driver brcmfmac:

  ```
  [ 8189.092819] brcmfmac: brcmf_fw_map_chip_to_name: using 
brcm/brcmfmac4356-pcie.bin for chip 0x004356(17238) rev 0x02
  [ 8189.093100] brcmfmac :04:00.0: Direct firmware load for 
brcm/brcmfmac4356-pcie.txt failed with error -2
  [ 8191.568544] brcmfmac: brcmf_msgbuf_query_dcmd: Timeout on response for 
query command
  [ 8191.568562] brcmfmac: brcmf_c_preinit_dcmds: Retreiving cur_etheraddr 
failed, -5
  [ 8191.568570] brcmfmac: brcmf_bus_started: failed: -5
  [ 8191.568588] brcmfmac: brcmf_pcie_attach_bus: dongle is not responding
  ```

  As seen here https://answers.launchpad.net/ubuntu/+question/668329, I
  reverted to the previous linux-firmware version and then the wifi
  chipset is working:

  Previous firmware package: https://packages.ubuntu.com/artful-
  updates/linux-firmware

  ```
  [10087.698214] brcmfmac: brcmf_fw_map_chip_to_name: using 
brcm/brcmfmac4356-pcie.bin for chip 0x004356(17238) rev 0x02
  [10087.698634] brcmfmac :04:00.0: Direct firmware load for 
brcm/brcmfmac4356-pcie.txt failed with error -2
  [10088.104176] brcmfmac :04:00.0: Direct firmware load for 
brcm/brcmfmac4356-pcie.clm_blob failed with error -2
  [10088.104186] brcmfmac: brcmf_c_process_clm_blob: no clm_blob 
available(err=-2), device may have limited channels available
  [10088.105170] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 
22 2015 06:16:41 version 7.35.180.119 (r594535) FWID 01-1a5c4016
  [10088.179872] brcmfmac :04:00.0 wlp4s0: renamed from wlan0
  ```

  The problem seems to have been reported to the linux-wireless mailing
  list but no fix has been committed apparently :
  https://www.spinics.net/lists/linux-wireless/msg168687.html

  System information:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  linux-image-4.15.0-20-generic:
Installé : 4.15.0-20.21
Candidat : 4.15.0-20.21
   Table de version :
   *** 4.15.0-20.21 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  linux-firmware:
Installé : 1.173
Candidat : 1.173
   Table de version :
   *** 1.173 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://fr.archive.ubuntu.com/ubuntu bionic/main i386 Packages
  100 /var/lib/dpkg/status

  
  Regards,
  Jean Pierre.

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


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

[Kernel-packages] [Bug 1958679] Re: after suspend losing screen

[go4heartbeat]

I just ran the following command in the terminal for data that maybe could help 
you:
apport-collect 1958679

Before that, I restarted my notebook with the problem kernel 5.13.0-27,
which blocks the screen with white and black bars after suspending it.

But now I can no longer use the suspend command without errors, so after a 
waiting period I will switch off my notebook to protect it.
I have no idea if it will help if I give you this grace period for data 
exchange.

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

Title:
  after suspend losing screen

Status in linux-hwe-5.13 package in Ubuntu:
  Incomplete

Bug description:
  After wake up after suspending my notebook I lost my screen with white
  and black bars on it!

  Technic:
  with the newest Kernel für Ubuntu 20.04:
  Ubuntu 20.04 mit Kernel 5.13.0-27-generic

  Notebook Sony Vaio with graphics driver:
  X.Org-X-Server (Nouveau)

  Now, with the older kernel (second kernel)
  uname -r
  5.11.0-46-generic
  all be alright

  So I currently have no problems, but I would like to point out
  problems with the kernel 5.13.0-27-generic and suspend.

  Thank you!

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


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

[Kernel-packages] [Bug 1958898] [NEW] Focal update: v5.4.170 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.170 upstream stable release
   from git://git.kernel.org/

HID: asus: Add depends on USB_HID to HID_ASUS Kconfig option
tee: handle lookup of shm with reference count 0
Input: i8042 - add deferred probe support
Input: i8042 - enable deferred probe quirk for ASUS UM325UA
tomoyo: Check exceeded quota early in tomoyo_domain_quota_is_ok().
platform/x86: apple-gmux: use resource_size() with res
memblock: fix memblock_phys_alloc() section mismatch error
recordmcount.pl: fix typo in s390 mcount regex
selinux: initialize proto variable in selinux_ip_postroute_compat()
scsi: lpfc: Terminate string in lpfc_debugfs_nvmeio_trc_write()
net/mlx5: DR, Fix NULL vs IS_ERR checking in dr_domain_init_resources
udp: using datalen to cap ipv6 udp max gso segments
selftests: Calculate udpgso segment count without header adjustment
sctp: use call_rcu to free endpoint
net: usb: pegasus: Do not drop long Ethernet frames
net: lantiq_xrx200: fix statistics of received bytes
NFC: st21nfca: Fix memory leak in device probe and remove
ionic: Initialize the 'lif->dbid_inuse' bitmap
net/mlx5e: Fix wrong features assignment in case of error
selftests/net: udpgso_bench_tx: fix dst ip argument
net/ncsi: check for error return from call to nla_put_u32
fsl/fman: Fix missing put_device() call in fman_port_probe
i2c: validate user data in compat ioctl
nfc: uapi: use kernel size_t to fix user-space builds
uapi: fix linux/nfc.h userspace compilation errors
xhci: Fresco FL1100 controller should not have BROKEN_MSI quirk set.
usb: gadget: f_fs: Clear ffs_eventfd in ffs_data_clear.
usb: mtu3: add memory barrier before set GPD's HWO
usb: mtu3: fix list_head check warning
usb: mtu3: set interval of FS intr and isoc endpoint
binder: fix async_free_space accounting for empty parcels
scsi: vmw_pvscsi: Set residual data length conditionally
Input: appletouch - initialize work before device registration
Input: spaceball - fix parsing of movement data packets
net: fix use-after-free in tw_timer_handler
perf script: Fix CPU filtering of a script's switch events
Linux 5.4.170
UBUNTU: upstream stable to v5.4.170

** 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
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    v5.4.170 upstream stable release
+    from git://git.kernel.org/
  
-v5.4.170 upstream stable release
-from git://git.kernel.org/
+ HID: asus: Add depends on USB_HID to HID_ASUS Kconfig option
+ tee: handle lookup of shm with reference count 0
+ Input: i8042 - add deferred probe support
+ Input: i8042 - enable deferred probe quirk for ASUS UM325UA
+ tomoyo: Check exceeded quota early in tomoyo_domain_quota_is_ok().
+ platform/x86: apple-gmux: use resource_size() with res
+ memblock: fix memblock_phys_alloc() section mismatch error
+ recordmcount.pl: fix typo in s390 mcount regex
+ selinux: initialize proto variable in selinux_ip_postroute_compat()
+ scsi: lpfc: Terminate string in lpfc_debugfs_nvmeio_trc_write()
+ net/mlx5: DR, Fix NULL vs IS_ERR checking in dr_domain_init_resources
+ udp: using datalen to cap ipv6 udp max gso segments
+ selftests: Calculate udpgso segment count without header adjustment
+ sctp: use call_rcu to free endpoint
+ net: usb: pegasus: Do not drop long 

[Kernel-packages] [Bug 1954646] Re: [SRU][I/J/OEM-5.13/OEM-5.14] Fix pci port lost when hotplug dock

[Timo Aaltonen]

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

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

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

Title:
  [SRU][I/J/OEM-5.13/OEM-5.14] Fix pci port lost when hotplug dock

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Fix Committed
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  On Intel Maple Ridge, when hotplug TBT4 dock, PCIe bus  show error 
"severity=Uncorrected (Non-Fatal)",
  and failed to probe.

  [Fix]
  Re-enable PCIe port LTR after reset or hotplug, and probe it properly.

  [Test]
  Verified on HW with TBT4 dock. it works fine.
  Also tested Tiger Lake-LP Thunderbolt 4, tbt4 dock works fine.
  Tested on AMD Cezanne, PCIe works fine, it doesn't support thunderbolt.

  [Where problems could occur]
  PCI bus may break.

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


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

[Kernel-packages] [Bug 1946686] Re: Fix zfs_get_data access to files with wrong generation causing panics

[Dimitri John Ledkov]

For focal this appears to be required and fixes things for people
https://github.com/openzfs/zfs/issues/10642

I will rerun regression suites on focal with latest kernel, and if that
passes, will mark this as verification done.

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

Title:
  Fix zfs_get_data access to files with wrong generation causing panics

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Focal:
  Fix Committed
Status in zfs-linux source package in Hirsute:
  Fix Released
Status in zfs-linux source package in Impish:
  Fix Released

Bug description:
  == SRU Focal/Hirsute ==

  [Impact]

  ZFS: Fix a panic while acquiring a lock.

  If TX_WRITE is create on a file, and the file is later deleted and a new
  directory is created on the same object id, it is possible that when
  zil_commit happens, zfs_get_data will be called on the new directory.
  This may result in panic as it tries to do range lock. 

  Upstream ZFS bug #10593, #11682, upstream fix:

  commit 296a4a369bc1078a694f88570972330985b3b1b8
  Author: Chunwei Chen 
  Date: Fri Mar 19 22:53:31 2021 -0700

  Fix zfs_get_data access to files with wrong generation

  This patch fixes this issue by record the generation number during
  zfs_log_write, so zfs_get_data can check if the object is valid.

  The fix is already in Ubuntu ZFS 2.0.6 in Impish. The fix is a
  relatively simple backport with only minor backporting effort required
  in moving some of the module specific upstream changes into the pre-
  renamed module specific os specific parts of the ZFS module.

  [Test Plan]

  This is difficult to reproduce, see
  https://github.com/openzfs/zfs/issues/10593

  The fix has been tested with the complete ubuntu autotest ZFS
  regression tests that exercise ZFS core functionality (smoke tests),
  file system POSIX compliance (fs tests), extra XFS tests and every
  mount option with stress-ng file I/O stress tests.

  [Where problems could occur]

  This fix could regress the ZIL (ZFS intent log) commit writes since it
  modifies this code to now checks for generation numbers. Testing with
  ZFS autotests with intent logs have not found any regressions, but
  there is a risk that the ZIL functionality is affected. This could
  lead to corruption.

  --

  As mentioned at https://answers.launchpad.net/ubuntu/+source/zfs-
  linux/+question/696659, the following pull request fixes a panic
  acquiring a lock: https://github.com/openzfs/zfs/pull/11682

  This fix does not appear to be a part of the latest Ubuntu 20.04
  release:

  zfsutils-linux:
    Installed: 0.8.3-1ubuntu12.12
    Candidate: 0.8.3-1ubuntu12.12
    Version table:
   *** 0.8.3-1ubuntu12.12 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   0.8.3-1ubuntu12.9 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   0.8.3-1ubuntu12 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Of note is this issue where the bug is reported against the Ubuntu
  0.8.3 packages: https://github.com/openzfs/zfs/issues/10642

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


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

[Kernel-packages] [Bug 1946686] Re: Fix zfs_get_data access to files with wrong generation causing panics

[Dimitri John Ledkov]

riscv64 ftbfs is not a regression, as we don't build it in updates
either.

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

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

Title:
  Fix zfs_get_data access to files with wrong generation causing panics

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Focal:
  Fix Committed
Status in zfs-linux source package in Hirsute:
  Fix Released
Status in zfs-linux source package in Impish:
  Fix Released

Bug description:
  == SRU Focal/Hirsute ==

  [Impact]

  ZFS: Fix a panic while acquiring a lock.

  If TX_WRITE is create on a file, and the file is later deleted and a new
  directory is created on the same object id, it is possible that when
  zil_commit happens, zfs_get_data will be called on the new directory.
  This may result in panic as it tries to do range lock. 

  Upstream ZFS bug #10593, #11682, upstream fix:

  commit 296a4a369bc1078a694f88570972330985b3b1b8
  Author: Chunwei Chen 
  Date: Fri Mar 19 22:53:31 2021 -0700

  Fix zfs_get_data access to files with wrong generation

  This patch fixes this issue by record the generation number during
  zfs_log_write, so zfs_get_data can check if the object is valid.

  The fix is already in Ubuntu ZFS 2.0.6 in Impish. The fix is a
  relatively simple backport with only minor backporting effort required
  in moving some of the module specific upstream changes into the pre-
  renamed module specific os specific parts of the ZFS module.

  [Test Plan]

  This is difficult to reproduce, see
  https://github.com/openzfs/zfs/issues/10593

  The fix has been tested with the complete ubuntu autotest ZFS
  regression tests that exercise ZFS core functionality (smoke tests),
  file system POSIX compliance (fs tests), extra XFS tests and every
  mount option with stress-ng file I/O stress tests.

  [Where problems could occur]

  This fix could regress the ZIL (ZFS intent log) commit writes since it
  modifies this code to now checks for generation numbers. Testing with
  ZFS autotests with intent logs have not found any regressions, but
  there is a risk that the ZIL functionality is affected. This could
  lead to corruption.

  --

  As mentioned at https://answers.launchpad.net/ubuntu/+source/zfs-
  linux/+question/696659, the following pull request fixes a panic
  acquiring a lock: https://github.com/openzfs/zfs/pull/11682

  This fix does not appear to be a part of the latest Ubuntu 20.04
  release:

  zfsutils-linux:
    Installed: 0.8.3-1ubuntu12.12
    Candidate: 0.8.3-1ubuntu12.12
    Version table:
   *** 0.8.3-1ubuntu12.12 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   0.8.3-1ubuntu12.9 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   0.8.3-1ubuntu12 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Of note is this issue where the bug is reported against the Ubuntu
  0.8.3 packages: https://github.com/openzfs/zfs/issues/10642

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


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

[Kernel-packages] [Bug 1958724] Re: System Shutdown and resume hangs since Kernel linux-image-5.13.0-23-generic

[Brian Clark]

I believe I'm having the same issue as well.  Have tried both GUI and
terminal commands.

Ubuntu 20.04.3
Uname: 5.13.0-27-generic

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

Title:
  System Shutdown and resume hangs since Kernel linux-
  image-5.13.0-23-generic

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

Bug description:
  Hi,

  on my Medion E14304 Ubuntu was working fine until Kernel 5.13.0.21.
  Since Version 5.13.0.23 System Shutdown and resume hangs. The System
  does not stop also after a long time.

  The last messages in recovery mode on the root console are:

  Reached target Power-off
  ... systemd-udevd[295]: ... Worker [311] processing SEQNUM=3047 is taking time
  Waiting for process systemd-udevd, systemd-udevd 

  Perhaps my attached dmesg and lsmod helps. All messages are in one file.
   
  Thank you very much.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 22 16:59:05 2022
  InstallationDate: Installed on 2021-12-25 (27 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  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/1958724/+subscriptions


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

[Kernel-packages] [Bug 1958412] Re: [amdgpu] at startup and shutdown screen gets white noise

[James Ferguson]

Please also note that while this bug is mostly cosmetic (?), the
probably-related bug https://bugs.launchpad.net/ubuntu/+source/linux-
hwe-5.13/+bug/1958591 is more critical and renders the display and
therefore often the computer unusable.

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

Title:
  [amdgpu] at startup and shutdown screen gets white noise

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

Bug description:
  After the kernel release 5.13.0-27-generic was installed today, the
  startup and shutdown processes finish with white noise screens.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Jan 19 16:17:35 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:164c] (rev c2) (prog-if 
00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:18b2]
  InstallationDate: Installed on 2022-01-19 (0 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop TP420UA_TM420UA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=c4ec4ae8-c14c-4c0b-9922-9142270cef97 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/06/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: TP420UA.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP420UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.2
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrTP420UA.302:bd09/06/2021:br5.19:efr3.2:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopTP420UA_TM420UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP420UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:
  dmi.product.family: VivoBook Flip
  dmi.product.name: VivoBook_ASUSLaptop TP420UA_TM420UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Kernel-packages] [Bug 1954746] Re: ASIX AX88179 compatible USB adapter not working

[Arno]

I tried putting Ubuntu in suspend mode and wake it up again after
reading
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939638/comments/11.

This seams to make the situation work again. After bringing the network
interface up again and requesting a fresh IP from the DHCP server I'm
able to use the USB network adapter again.

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

Title:
  ASIX AX88179 compatible USB adapter not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upon inserting the USB device errors can be found in dmesg. (see
  below)

  
  The current result:
  USB adapter is no longer working

  The expected result:
  USB adapter should work properly

  Please also note that this is my first bug report here.

  
  [ 5667.499655] ax88179_178a 2-1.3:2.0 eth0: unregister 'ax88179_178a' 
usb-:00:14.0-1.3, ASIX AX88179 USB 3.0 Gigabit Ethernet
  [ 5667.541257] ax88179_178a 2-1.3:2.0 eth0 (unregistered): Failed to write 
reg index 0x0002: -19
  [ 5667.541264] ax88179_178a 2-1.3:2.0 eth0 (unregistered): Failed to write 
reg index 0x0001: -19
  [ 5667.541268] ax88179_178a 2-1.3:2.0 eth0 (unregistered): Failed to write 
reg index 0x0002: -19
  [ 5667.541445] ax88179_178a 2-1.3:2.1 eth1: unregister 'ax88179_178a' 
usb-:00:14.0-1.3, ASIX AX88179 USB 3.0 Gigabit Ethernet
  [ 5667.585338] ax88179_178a 2-1.3:2.1 eth1 (unregistered): Failed to write 
reg index 0x0002: -19
  [ 5667.585345] ax88179_178a 2-1.3:2.1 eth1 (unregistered): Failed to write 
reg index 0x0001: -19
  [ 5667.585350] ax88179_178a 2-1.3:2.1 eth1 (unregistered): Failed to write 
reg index 0x0002: -19
  [ 5668.066721] usb 2-1.3: new SuperSpeed Gen 1 USB device number 4 using 
xhci_hcd
  [ 5668.237190] usb 2-1.3: New USB device found, idVendor=0b95, 
idProduct=1790, bcdDevice= 2.00
  [ 5668.237196] usb 2-1.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [ 5668.237199] usb 2-1.3: Product: AX88179A
  [ 5668.237203] usb 2-1.3: Manufacturer: ASIX
  [ 5668.237205] usb 2-1.3: SerialNumber: 000CFBDD
  [ 5668.915280] ax88179_178a 2-1.3:1.0 (unnamed net_device) (uninitialized): 
Failed to read reg index 0x0040: -32
  [ 5669.227298] ax88179_178a 2-1.3:1.0 eth0: register 'ax88179_178a' at 
usb-:00:14.0-1.3, ASIX AX88179 USB 3.0 Gigabit Ethernet, f8:e4:3b:0c:fb:dd
  [ 5669.285419] ax88179_178a 2-1.3:1.0 enxf8e43b0cfbdd: renamed from eth0

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-91-generic 5.4.0-91.102
  ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151
  Uname: Linux 5.4.0-91-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arno   1964 F pulseaudio
   /dev/snd/controlC1:  arno   1964 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 14 08:14:34 2021
  HibernationDevice: RESUME=UUID=67bde916-af41-4b15-bcb4-599116d67df7
  InstallationDate: Installed on 2018-05-18 (1306 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. XPS 15 9560
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-91-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nouveau.runpm=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-91-generic N/A
   linux-backports-modules-5.4.0-91-generic  N/A
   linux-firmware1.187.20
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-11-21 (387 days ago)
  dmi.bios.date: 05/25/2021
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.23.1
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.23.1:bd05/25/2021:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1958879] [NEW] nvidia-kernel-source-470 470.86-0ubuntu0.21.10.1: nvidia kernel module failed to build

[Manuel Piñar Molina]

Public bug reported:

I can't configure nvidia rtx3080 in my laptop msi

ProblemType: Package
DistroRelease: Ubuntu 21.10
Package: nvidia-kernel-source-470 470.86-0ubuntu0.21.10.1
Uname: Linux 5.14.15-051415-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: unknown
DKMSKernelVersion: 5.13.0-28-generic
Date: Mon Jan 24 15:36:45 2022
Dependencies:
 
PackageVersion: 470.86-0ubuntu0.21.10.1
Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 
3.9.4-1ubuntu1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.20.9ubuntu2.1
 apt  2.3.9
SourcePackage: nvidia-graphics-drivers-470
Title: nvidia-kernel-source-470 470.86-0ubuntu0.21.10.1: nvidia kernel module 
failed to build
UpgradeStatus: Upgraded to impish on 2021-11-01 (83 days ago)

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


** Tags: amd64 apport-package impish

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

Title:
  nvidia-kernel-source-470 470.86-0ubuntu0.21.10.1: nvidia kernel module
  failed to build

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  I can't configure nvidia rtx3080 in my laptop msi

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: nvidia-kernel-source-470 470.86-0ubuntu0.21.10.1
  Uname: Linux 5.14.15-051415-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DKMSKernelVersion: 5.13.0-28-generic
  Date: Mon Jan 24 15:36:45 2022
  Dependencies:
   
  PackageVersion: 470.86-0ubuntu0.21.10.1
  Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 
3.9.4-1ubuntu1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu2.1
   apt  2.3.9
  SourcePackage: nvidia-graphics-drivers-470
  Title: nvidia-kernel-source-470 470.86-0ubuntu0.21.10.1: nvidia kernel module 
failed to build
  UpgradeStatus: Upgraded to impish on 2021-11-01 (83 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1958879/+subscriptions


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

[Kernel-packages] [Bug 1924298] Re: accept returns duplicate endpoints under load

[Chen]

Amazon Linux is affected as well.

Operating System: Amazon Linux 2
Kernel: Linux 4.14.256-197.484.amzn2.aarch64
Architecture: arm64

openjdk version "17" 2021-09-14
OpenJDK Runtime Environment Temurin-17+35 (build 17+35)
OpenJDK 64-Bit Server VM Temurin-17+35 (build 17+35, mixed mode, sharing)

Tomcat 9.0.56

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

Title:
  accept returns duplicate endpoints under load

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

Bug description:
  When accepting client connections under load, duplicate endpoints may
  be returned. These endpoints will have different (usually sequential)
  file descriptors but will refer to the same connection (same server
  IP, same server port, same client IP, same client port). Both copies
  of the endpoint appear to be functional.

  Reproduction requires:
  - compilation of the attached server.c program
  - wrk (https://github.com/wg/wrk) to generate load

  The steps to reproduce are:
  - run 'server' application in one console window
  - run 'for i in {1..50}; do /opt/wrk/wrk -t 2 -c 1000 -d 5s --latency 
--timeout 1s http://localhost:/post; done' in a second console window
  - run the same command in a third window to generate concurrent load

  You may need to run additional instance of the wrk command in multiple
  windows to trigger the issue.

  When the problem occurs the server executable will exit and print some 
debugging info. e.g.:
  accerror = 1950892, counter = 10683, port = 59892, clientfd = 233, lastClient 
= 232

  This indicates that the sockets with file descriptors 233 and 232 are
  duplicates.

  The issue has been reproduced on fully patched versions of Ubuntu
  20.04 and 18.04. Other versions have not been tested.

  This issue was originally observed in Java and was reported against the 
Spring Framework:
  https://github.com/spring-projects/spring-framework/issues/26434

  Investigation from the Spring team and the Apache Tomcat team identified that 
it appeared to be a JDK issue:
  https://bugs.openjdk.java.net/browse/JDK-8263243

  Further research from the JDK team determined that the issue was at
  the OS level. Hence this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-71-generic 5.4.0-71.79
  ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101
  Uname: Linux 5.4.0-71-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 15 12:52:53 2021
  HibernationDevice: RESUME=UUID=f5a46e09-d99b-4475-8ab6-2cd70da8418d
  InstallationDate: Installed on 2017-02-02 (1532 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   lono wireless extensions.
   
   docker0   no wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-71-generic 
root=/dev/mapper/ubuntu--vg-root ro text
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-71-generic N/A
   linux-backports-modules-5.4.0-71-generic  N/A
   linux-firmware1.187.10
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-09-07 (219 days ago)
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22
  dmi.board.asset.tag: Default string
  dmi.board.name: X99-SLI-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.:bvrF22:bd06/13/2016:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  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/linux/+bug/1924298/+subscriptions


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

[Kernel-packages] [Bug 1945461] Re: Integrated TSN controller

[Anthony Wong]

** Summary changed:

- Integrated TSN controller for sprint 2
+ Integrated TSN controller

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

Title:
  Integrated TSN controller

Status in HWE Next:
  Fix Released
Status in linux-intel-5.13 package in Ubuntu:
  Invalid
Status in linux-intel-5.13 source package in Focal:
  Fix Released

Bug description:
  Tracking bug, please don't triage.

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


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

[Kernel-packages] [Bug 1933301] Re: [uacc-0623] hisi_sec2 fail to alloc uacce

[Stefan Bader]

** Changed in: linux (Ubuntu Jammy)
   Status: Incomplete => Fix Committed

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

Title:
  [uacc-0623] hisi_sec2  fail to alloc uacce

Status in kunpeng920:
  Fix Committed
Status in kunpeng920 ubuntu-20.04-hwe series:
  Fix Committed
Status in kunpeng920 ubuntu-21.10 series:
  Fix Committed
Status in kunpeng920 ubuntu-22.04 series:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Impish:
  In Progress
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification
  =

  [Impact]
  * Users with HiSilicon Security Engine (SEC) version 2 controller fail to 
allocate Uacce.

  [Fix]
  * upstream 183b60e005975d3c84c22199ca64a9221e620fb6 crypto: hisilicon/qm - 
modify the uacce mode check

  [Test Plan]
  * Deploy Ubuntu Focal with HWE 5.13 kernel to a Kunpeng920 chip with 
HiSilicon Security Engine (SEC) version 2 controller
  * Boot the system
  * 'dmesg | grep "fail to alloc uacce"' and you will see complains from 
hisi_sec2. For example: [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc 
uacce (-22)

  [Where problems could occur]
  * The regression can be considered as low, since it is HiSilicon crypto 
system specific

  == Original Bug Description ==

  [Bug Description]

  ubuntu 20.04.2 boot system and fail to alloc uacce (-22)

  [Steps to Reproduce]
  1) boot ubuntu 20.04.2 system
  2) dmesg | grep fail

  [Actual Results]
  [   27.86] cma: cma_alloc: alloc failed, req-size: 4 pages, ret: -12
  [   27.006515] hisi_sec2 :b6:00.0: Failed to enable PASID
  [   27.012043] hisi_sec2 :b6:00.0: Adding to iommu group 45
  [   27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22)

  [Expected Results]
  no fail
  [Reproducibility]
  100%

  [Additional information]
  (Firmware version, kernel version, affected hardware, etc. if required):

  [Resolution]
  this following patches will solve this bug.

  commit f8408d2b79b834f79b6c578817e84f74a85d2190
  Author: Kai Ye 
  Date:   Tue Jan 5 14:16:42 2021 +0800

  crypto: hisilicon - add ZIP device using mode parameter

  Add 'uacce_mode' parameter for ZIP, which can be set as 0(default) or 1.
  '0' means ZIP is only registered to kernel crypto, and '1' means it's
  registered to both kernel crypto and UACCE.

  Signed-off-by: Kai Ye 
  Reviewed-by: Zhou Wang 
  Reviewed-by: Zaibo Xu 
  Signed-off-by: Herbert Xu 

  commit bedd04e4aa1434d2f0f038e15bb6c48ac36876e1
  Author: Kai Ye 
  Date:   Tue Jan 5 14:16:43 2021 +0800

  crypto: hisilicon/hpre - register HPRE device to uacce

  commit 34932a6033be3c0088935c334e4dc5ad43dcb0cc
  Author: Kai Ye 
  Date:   Tue Jan 5 14:16:44 2021 +0800

  crypto: hisilicon/sec - register SEC device to uacce

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


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

[Kernel-packages] [Bug 1957753] Re: net/mlx5e: EPERM on vlan 0 programming

[Dmitrii Shcherbakov]

Hirsute kernel looks good as well:

$ uname -r
5.11.0-50-generic

$ sudo ip link set enp130s0f0 vf 2 vlan 1 ; echo $?
RTNETLINK answers: Operation not permitted
2

$ sudo ip link set enp130s0f0 vf 2 vlan 0 ; echo $?
0

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

Title:
  net/mlx5e: EPERM on vlan 0 programming

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Incomplete
Status in linux source package in Hirsute:
  New
Status in linux source package in Impish:
  Incomplete
Status in linux source package in Jammy:
  Incomplete

Bug description:
  There is an issue with hypervisor host side mlx5 driver operation on
  Bluefield devices in kernels <=5.16 that was recently fixed in master
  with a one-liner:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37

  It would be good to have this fix in Focal+ kernels.

  This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux-
  bluefield since it's used at the DPU side whereas the issue in
  question affects the hypervisor side.

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


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

[Kernel-packages] [Bug 1957753] Re: net/mlx5e: EPERM on vlan 0 programming

[Dmitrii Shcherbakov]

Focal:

$ uname -r
5.4.0-97-generic

$ sudo ip link set enp130s0f0 vf 2 vlan 1
RTNETLINK answers: Operation not permitted

$ sudo ip link set enp130s0f0 vf 2 vlan 0 ; echo $?
0

Looks good - vlan 0 programming doesn't result in EPERM as expected
contrary to non-zero vlans.

Will try others as well. It would be good to backport it to currently
released versions above Focal (for production, we are mostly looking for
Focal GA + HWE kernels but it keeping it fixed consistently seems like
the right approach).

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

Title:
  net/mlx5e: EPERM on vlan 0 programming

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Incomplete
Status in linux source package in Hirsute:
  New
Status in linux source package in Impish:
  Incomplete
Status in linux source package in Jammy:
  Incomplete

Bug description:
  There is an issue with hypervisor host side mlx5 driver operation on
  Bluefield devices in kernels <=5.16 that was recently fixed in master
  with a one-liner:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37

  It would be good to have this fix in Focal+ kernels.

  This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux-
  bluefield since it's used at the DPU side whereas the issue in
  question affects the hypervisor side.

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


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

[Kernel-packages] [Bug 1958252] Re: Support networking XDP

[Tim Gardner]

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

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

Title:
  Support networking XDP

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-5.11 package in Ubuntu:
  Invalid
Status in linux-azure source package in Focal:
  In Progress
Status in linux-azure-5.11 source package in Focal:
  New
Status in linux-azure source package in Hirsute:
  Won't Fix
Status in linux-azure-5.11 source package in Hirsute:
  Invalid
Status in linux-azure source package in Impish:
  Fix Committed
Status in linux-azure-5.11 source package in Impish:
  Invalid

Bug description:
  SRU Justification

  [Impact]

  Enable XDP support in Azure tuned kernels.

  [Test Plan]

  Microsoft tested.

  [Where things could go wrong]

  Network performance could be impacted or base functionality could
  fail.

  [Other Info]

  SF: #00324494

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


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

[Kernel-packages] [Bug 1875015] Re: Displaylink is extremely slow

[Mathew Hodson]

** Bug watch removed: gitlab.gnome.org/GNOME/mutter/-/issues #2005
   https://gitlab.gnome.org/GNOME/mutter/-/issues/2005

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

Title:
  Displaylink is extremely slow

Status in Nouveau Xorg driver:
  Unknown
Status in OEM Priority Project:
  New
Status in xf86-video-amd:
  Unknown
Status in X.Org X server:
  Unknown
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  In Progress
Status in xserver-xorg-video-nouveau package in Ubuntu:
  In Progress
Status in xorg-server source package in Focal:
  Fix Released
Status in xorg-server source package in Hirsute:
  Won't Fix
Status in xorg-server source package in Impish:
  Fix Released

Bug description:
  Using ubuntu 20.04 on displaylink docking with external monitor is
  totally slow, unusable. The GUI responds very slow, if you click, the
  command of the click goes on after about 3 seconds... if you type, all
  the letters are with the same lag, so it is totally unusable.

  Was using displaylink without any problem on 19.10 until yesterday, when I 
upgraded to 20.04. 
  It is terrific.

  If i plug out the usb for the displaylink docking station, than the
  speed is back, and the system is ok, if I connect it to the docking
  station again, everything extremely slow again.

  Please investigate this asap, as it is unusable on displaylink docking
  stations.

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


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

[Kernel-packages] [Bug 1958850] Re: USB port lost function after unplugging usb drive

[Kai-Chuan Hsieh]

** Summary changed:

- USB port lost function after unplugging usb drive from WD19TB dock
+ USB port lost function after unplugging usb drive

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

Title:
  USB port lost function after unplugging usb drive

Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  Test the proposed 5.14 oem kernel, and get a failure symptom.

  Unplug a usb drive from WD19TB docking and a BUG reported in kernel,
  then the other embedded usb port can't detect usb drive anymore after
  a while.

  kernel: usb 5-2.3.3: USB disconnect, device number 5
  kernel: BUG: kernel NULL pointer dereference, address: 0030
  kernel: #PF: supervisor read access in kernel mode
  kernel: #PF: error_code(0x) - not-present page
  kernel: PGD 0 P4D 0
  kernel: Oops:  [#1] SMP NOPTI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  2205 F pulseaudio
   /dev/snd/controlC0:  u  2205 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-04-29 (270 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. Precision 5750
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem 
root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-1021-oem N/A
   linux-backports-modules-5.14.0-1021-oem  N/A
   linux-firmware   1.201.3
  Tags:  impish
  Uname: Linux 5.14.0-1021-oem x86_64
  UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990:
  dmi.product.family: Precision
  dmi.product.name: Precision 5750
  dmi.product.sku: 0990
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1958855] Re: sound

[Igor]

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

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

Title:
  sound

Status in linux-hwe-5.11 package in Ubuntu:
  New

Bug description:
  Hello. My laptop started having sound problems starting with cores older than 
5.11.43.
  The sound has become very wheezing and wheezing stops when you turn on video 
or music. But when nothing is lost, the sound on the speakers begins to make a 
wheeze very much. This is not on the core of the 5.11.43.

  [code]
  System:Kernel: 5.11.0-43-generic x86_64 bits: 64 compiler: N/A Desktop: 
Xfce 4.14.2 
 tk: Gtk 3.24.13 wm: xfwm4 dm: LightDM Distro: Linux Mint 20.1 
Ulyssa 
 base: Ubuntu 20.04 focal 
  Machine:   Type: Laptop System: Acer product: Aspire A515-44 v: V1.09 serial: 
 
 Mobo: RO model: Calla_RN v: V1.09 serial:  UEFI: INSYDE v: 
1.09 
 date: 08/05/2020 
  Battery:   ID-1: BAT1 charge: 40.9 Wh condition: 40.9/47.8 Wh (86%) volts: 
12.3/11.2 
 model: LGC AP18C8K serial:  status: Full 
  CPU:   Topology: 6-Core model: AMD Ryzen 5 4500U with Radeon Graphics 
bits: 64 type: MCP 
 arch: Zen rev: 1 L2 cache: 3072 KiB 
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 28447 
 Speed: 1394 MHz min/max: 1400/2375 MHz Core speeds (MHz): 1: 1339 
2: 1557 3: 1274 
 4: 3984 5: 1772 6: 1773 
  Graphics:  Device-1: AMD Renoir vendor: Acer Incorporated ALI driver: amdgpu 
v: kernel 
 bus ID: 05:00.0 chip ID: 1002:1636 
 Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati 
 unloaded: fbdev,modesetting,radeon,vesa resolution: 1600x900~60Hz 
 OpenGL: renderer: AMD RENOIR (DRM 3.40.0 5.11.0-43-generic LLVM 
12.0.0) 
 v: 4.6 Mesa 21.0.3 direct render: Yes 
  Audio: Device-1: AMD vendor: Acer Incorporated ALI driver: snd_hda_intel 
v: kernel 
 bus ID: 05:00.1 chip ID: 1002:1637 
 Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor 
 vendor: Acer Incorporated ALI driver: N/A bus ID: 05:00.5 chip ID: 
1022:15e2 
 Device-3: AMD Family 17h HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel 
 v: kernel bus ID: 05:00.6 chip ID: 1022:15e3 
 Sound Server: ALSA v: k5.11.0-43-generic 
  Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
 vendor: Acer Incorporated ALI driver: r8169 v: kernel port: 2000 
bus ID: 03:00.0 
 chip ID: 10ec:8168 
 IF: enp3s0 state: up speed: 100 Mbps duplex: full mac:  
 Device-2: Qualcomm Atheros QCA6174 802.11ac Wireless Network 
Adapter vendor: Lite-On 
 driver: ath10k_pci v: kernel port: 2000 bus ID: 04:00.0 chip ID: 
168c:003e 
 IF: wlp4s0 state: down mac:  
 IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A 
  Drives:Local Storage: total: 2.14 TiB used: 1.68 TiB (78.6%) 
 ID-1: /dev/nvme0n1 vendor: SK Hynix model: HFM256GDJTNI-82A0A 
size: 238.47 GiB 
 speed: 31.6 Gb/s lanes: 4 serial:  
 ID-2: /dev/sda type: USB vendor: Seagate model: ST2000LM007-1R8174 
size: 1.82 TiB 
 serial:  
 ID-3: /dev/sdb type: USB vendor: Transcend model: JetFlash 
Transcend 64GB 
 size: 59.84 GiB serial:  
 ID-4: /dev/sdc type: USB vendor: KingMAX model: USB2.0 FlashDisk 
size: 30.27 GiB 
 serial:  
  Partition: ID-1: / size: 231.54 GiB used: 55.93 GiB (24.2%) fs: ext4 dev: 
/dev/dm-1 
 ID-2: /boot size: 704.5 MiB used: 123.9 MiB (17.6%) fs: ext4 dev: 
/dev/nvme0n1p2 
 ID-3: swap-1 size: 976.0 MiB used: 3.5 MiB (0.4%) fs: swap dev: 
/dev/dm-2 
  USB:   Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002 
 Device-1: 1-3:2 info: Lite-On type: Bluetooth driver: btusb rev: 
2.0 chip ID: 04ca:3016 
 Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003 
 Device-2: 2-2:2 info: ASMedia Name: ASM1051E SATA 6Gb/s bridge 
ASM1053E SATA 6Gb/s 
 bridge ASM1153 SATA 3Gb/s bridge ASM1153E SATA 6Gb/s bridge 
 type: Mass Storage driver: usb-storage rev: 3.0 chip ID: 174c:55aa 
 Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002 
 Hub: 3-3:2 info: Genesys Logic 4-port hub ports: 4 rev: 2.0 chip 
ID: 05e3:0610 
 Device-3: 3-3.1:4 info: Transcend Information JetFlash type: Mass 
Storage 
 driver: usb-storage rev: 2.0 chip ID: 8564:1000 
 Device-4: 3-3.2:5 info: Kingmax Digital type: Mass Storage driver: 
usb-storage rev: 2.0 
 chip ID: 1687:3257 
 Device-5: 

[Kernel-packages] [Bug 1958853] [NEW] package nvidia-dkms-470 (not installed) failed to install/upgrade: 已安装 nvidia-dkms-470 软件包 post-installation 脚本 子进程返回错误状态 10

[shawntao]

Public bug reported:

update kernel to 5.15.6 and install the nvidia-dkms-495 or 470, the
error happen

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-dkms-470 (not installed)
Uname: Linux 5.12.0-051200-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Jan 24 15:13:04 2022
ErrorMessage: 已安装 nvidia-dkms-470 软件包 post-installation 脚本 子进程返回错误状态 10
InstallationDate: Installed on 2022-01-16 (7 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.1
 apt  2.0.6
SourcePackage: nvidia-graphics-drivers-470
Title: package nvidia-dkms-470 (not installed) failed to install/upgrade: 已安装 
nvidia-dkms-470 软件包 post-installation 脚本 子进程返回错误状态 10
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  package nvidia-dkms-470 (not installed) failed to install/upgrade: 已安装
  nvidia-dkms-470 软件包 post-installation 脚本 子进程返回错误状态 10

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  update kernel to 5.15.6 and install the nvidia-dkms-495 or 470, the
  error happen

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-dkms-470 (not installed)
  Uname: Linux 5.12.0-051200-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Jan 24 15:13:04 2022
  ErrorMessage: 已安装 nvidia-dkms-470 软件包 post-installation 脚本 子进程返回错误状态 10
  InstallationDate: Installed on 2022-01-16 (7 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.1
   apt  2.0.6
  SourcePackage: nvidia-graphics-drivers-470
  Title: package nvidia-dkms-470 (not installed) failed to install/upgrade: 已安装 
nvidia-dkms-470 软件包 post-installation 脚本 子进程返回错误状态 10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1958853/+subscriptions


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

[Kernel-packages] [Bug 1958854] [NEW] jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-01-24)

[Juerg Haefliger]

Public bug reported:


Upstream raspberrypi patchset 2022-01-24

  Ported from the following raspberrypi branch:
rpi-5.15.y
  from https://github.com/raspberrypi/linux.git

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

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

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

** Also affects: linux-raspi (Ubuntu Jammy)
   Importance: Undecided
   Status: Confirmed

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

Title:
  jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y
  (2022-01-24)

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

Bug description:
  
  Upstream raspberrypi patchset 2022-01-24

Ported from the following raspberrypi branch:
  rpi-5.15.y
from https://github.com/raspberrypi/linux.git

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


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

[Kernel-packages] [Bug 1958855] [NEW] sound

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hello. My laptop started having sound problems starting with cores older than 
5.11.43.
The sound has become very wheezing and wheezing stops when you turn on video or 
music. But when nothing is lost, the sound on the speakers begins to make a 
wheeze very much. This is not on the core of the 5.11.43.

[code]
System:Kernel: 5.11.0-43-generic x86_64 bits: 64 compiler: N/A Desktop: 
Xfce 4.14.2 
   tk: Gtk 3.24.13 wm: xfwm4 dm: LightDM Distro: Linux Mint 20.1 Ulyssa 
   base: Ubuntu 20.04 focal 
Machine:   Type: Laptop System: Acer product: Aspire A515-44 v: V1.09 serial: 
 
   Mobo: RO model: Calla_RN v: V1.09 serial:  UEFI: INSYDE v: 
1.09 
   date: 08/05/2020 
Battery:   ID-1: BAT1 charge: 40.9 Wh condition: 40.9/47.8 Wh (86%) volts: 
12.3/11.2 
   model: LGC AP18C8K serial:  status: Full 
CPU:   Topology: 6-Core model: AMD Ryzen 5 4500U with Radeon Graphics bits: 
64 type: MCP 
   arch: Zen rev: 1 L2 cache: 3072 KiB 
   flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 28447 
   Speed: 1394 MHz min/max: 1400/2375 MHz Core speeds (MHz): 1: 1339 2: 
1557 3: 1274 
   4: 3984 5: 1772 6: 1773 
Graphics:  Device-1: AMD Renoir vendor: Acer Incorporated ALI driver: amdgpu v: 
kernel 
   bus ID: 05:00.0 chip ID: 1002:1636 
   Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati 
   unloaded: fbdev,modesetting,radeon,vesa resolution: 1600x900~60Hz 
   OpenGL: renderer: AMD RENOIR (DRM 3.40.0 5.11.0-43-generic LLVM 
12.0.0) 
   v: 4.6 Mesa 21.0.3 direct render: Yes 
Audio: Device-1: AMD vendor: Acer Incorporated ALI driver: snd_hda_intel v: 
kernel 
   bus ID: 05:00.1 chip ID: 1002:1637 
   Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor 
   vendor: Acer Incorporated ALI driver: N/A bus ID: 05:00.5 chip ID: 
1022:15e2 
   Device-3: AMD Family 17h HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel 
   v: kernel bus ID: 05:00.6 chip ID: 1022:15e3 
   Sound Server: ALSA v: k5.11.0-43-generic 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
   vendor: Acer Incorporated ALI driver: r8169 v: kernel port: 2000 bus 
ID: 03:00.0 
   chip ID: 10ec:8168 
   IF: enp3s0 state: up speed: 100 Mbps duplex: full mac:  
   Device-2: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter 
vendor: Lite-On 
   driver: ath10k_pci v: kernel port: 2000 bus ID: 04:00.0 chip ID: 
168c:003e 
   IF: wlp4s0 state: down mac:  
   IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A 
Drives:Local Storage: total: 2.14 TiB used: 1.68 TiB (78.6%) 
   ID-1: /dev/nvme0n1 vendor: SK Hynix model: HFM256GDJTNI-82A0A size: 
238.47 GiB 
   speed: 31.6 Gb/s lanes: 4 serial:  
   ID-2: /dev/sda type: USB vendor: Seagate model: ST2000LM007-1R8174 
size: 1.82 TiB 
   serial:  
   ID-3: /dev/sdb type: USB vendor: Transcend model: JetFlash Transcend 
64GB 
   size: 59.84 GiB serial:  
   ID-4: /dev/sdc type: USB vendor: KingMAX model: USB2.0 FlashDisk 
size: 30.27 GiB 
   serial:  
Partition: ID-1: / size: 231.54 GiB used: 55.93 GiB (24.2%) fs: ext4 dev: 
/dev/dm-1 
   ID-2: /boot size: 704.5 MiB used: 123.9 MiB (17.6%) fs: ext4 dev: 
/dev/nvme0n1p2 
   ID-3: swap-1 size: 976.0 MiB used: 3.5 MiB (0.4%) fs: swap dev: 
/dev/dm-2 
USB:   Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip ID: 
1d6b:0002 
   Device-1: 1-3:2 info: Lite-On type: Bluetooth driver: btusb rev: 2.0 
chip ID: 04ca:3016 
   Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip ID: 
1d6b:0003 
   Device-2: 2-2:2 info: ASMedia Name: ASM1051E SATA 6Gb/s bridge 
ASM1053E SATA 6Gb/s 
   bridge ASM1153 SATA 3Gb/s bridge ASM1153E SATA 6Gb/s bridge 
   type: Mass Storage driver: usb-storage rev: 3.0 chip ID: 174c:55aa 
   Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip ID: 
1d6b:0002 
   Hub: 3-3:2 info: Genesys Logic 4-port hub ports: 4 rev: 2.0 chip ID: 
05e3:0610 
   Device-3: 3-3.1:4 info: Transcend Information JetFlash type: Mass 
Storage 
   driver: usb-storage rev: 2.0 chip ID: 8564:1000 
   Device-4: 3-3.2:5 info: Kingmax Digital type: Mass Storage driver: 
usb-storage rev: 2.0 
   chip ID: 1687:3257 
   Device-5: 3-3.3:9 info: SiGma Micro USB2.0 Hub type: Mouse driver: 
hid-generic,usbhid 
   rev: 1.1 chip ID: 1c4f:0034 
   Device-6: 3-3.4:7 info: China Resource Semico HD User Facing type: 
Keyboard,HID 
   driver: hid-generic,usbhid rev: 1.1 chip ID: 1a2c:2c27 
   Device-7: 3-4:3 info: Chicony HD User Facing type: Video driver: 
uvcvideo rev: 2.0 
   chip ID: 

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

[Kai-Chuan Hsieh]

apport information

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

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

Title:
  USB port lost function after unplugging usb drive from WD19TB dock

Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  Test the proposed 5.14 oem kernel, and get a failure symptom.

  Unplug a usb drive from WD19TB docking and a BUG reported in kernel,
  then the other embedded usb port can't detect usb drive anymore after
  a while.

  kernel: usb 5-2.3.3: USB disconnect, device number 5
  kernel: BUG: kernel NULL pointer dereference, address: 0030
  kernel: #PF: supervisor read access in kernel mode
  kernel: #PF: error_code(0x) - not-present page
  kernel: PGD 0 P4D 0
  kernel: Oops:  [#1] SMP NOPTI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  2205 F pulseaudio
   /dev/snd/controlC0:  u  2205 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-04-29 (270 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. Precision 5750
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem 
root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-1021-oem N/A
   linux-backports-modules-5.14.0-1021-oem  N/A
   linux-firmware   1.201.3
  Tags:  impish
  Uname: Linux 5.14.0-1021-oem x86_64
  UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990:
  dmi.product.family: Precision
  dmi.product.name: Precision 5750
  dmi.product.sku: 0990
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1958850] RfKill.txt

[Kai-Chuan Hsieh]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1958850/+attachment/5557005/+files/RfKill.txt

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

Title:
  USB port lost function after unplugging usb drive from WD19TB dock

Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  Test the proposed 5.14 oem kernel, and get a failure symptom.

  Unplug a usb drive from WD19TB docking and a BUG reported in kernel,
  then the other embedded usb port can't detect usb drive anymore after
  a while.

  kernel: usb 5-2.3.3: USB disconnect, device number 5
  kernel: BUG: kernel NULL pointer dereference, address: 0030
  kernel: #PF: supervisor read access in kernel mode
  kernel: #PF: error_code(0x) - not-present page
  kernel: PGD 0 P4D 0
  kernel: Oops:  [#1] SMP NOPTI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  2205 F pulseaudio
   /dev/snd/controlC0:  u  2205 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-04-29 (270 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. Precision 5750
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem 
root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-1021-oem N/A
   linux-backports-modules-5.14.0-1021-oem  N/A
   linux-firmware   1.201.3
  Tags:  impish
  Uname: Linux 5.14.0-1021-oem x86_64
  UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990:
  dmi.product.family: Precision
  dmi.product.name: Precision 5750
  dmi.product.sku: 0990
  dmi.sys.vendor: Dell Inc.

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


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

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

[Kai-Chuan Hsieh]

apport information

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

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

Title:
  USB port lost function after unplugging usb drive from WD19TB dock

Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  Test the proposed 5.14 oem kernel, and get a failure symptom.

  Unplug a usb drive from WD19TB docking and a BUG reported in kernel,
  then the other embedded usb port can't detect usb drive anymore after
  a while.

  kernel: usb 5-2.3.3: USB disconnect, device number 5
  kernel: BUG: kernel NULL pointer dereference, address: 0030
  kernel: #PF: supervisor read access in kernel mode
  kernel: #PF: error_code(0x) - not-present page
  kernel: PGD 0 P4D 0
  kernel: Oops:  [#1] SMP NOPTI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  2205 F pulseaudio
   /dev/snd/controlC0:  u  2205 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-04-29 (270 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. Precision 5750
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem 
root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-1021-oem N/A
   linux-backports-modules-5.14.0-1021-oem  N/A
   linux-firmware   1.201.3
  Tags:  impish
  Uname: Linux 5.14.0-1021-oem x86_64
  UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990:
  dmi.product.family: Precision
  dmi.product.name: Precision 5750
  dmi.product.sku: 0990
  dmi.sys.vendor: Dell Inc.

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


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

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

[Kai-Chuan Hsieh]

apport information

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

** Tags added: originate-from-1958840

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

Title:
  USB port lost function after unplugging usb drive from WD19TB dock

Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  Test the proposed 5.14 oem kernel, and get a failure symptom.

  Unplug a usb drive from WD19TB docking and a BUG reported in kernel,
  then the other embedded usb port can't detect usb drive anymore after
  a while.

  kernel: usb 5-2.3.3: USB disconnect, device number 5
  kernel: BUG: kernel NULL pointer dereference, address: 0030
  kernel: #PF: supervisor read access in kernel mode
  kernel: #PF: error_code(0x) - not-present page
  kernel: PGD 0 P4D 0
  kernel: Oops:  [#1] SMP NOPTI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  2205 F pulseaudio
   /dev/snd/controlC0:  u  2205 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-04-29 (270 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. Precision 5750
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem 
root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-1021-oem N/A
   linux-backports-modules-5.14.0-1021-oem  N/A
   linux-firmware   1.201.3
  Tags:  impish
  Uname: Linux 5.14.0-1021-oem x86_64
  UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990:
  dmi.product.family: Precision
  dmi.product.name: Precision 5750
  dmi.product.sku: 0990
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1958565] Re: Can not boot after updating kernel to linux-image-5.13.0-27-generic

[Sighil]

Having same issue on Dell inspiron 7415. Error saying unable to find
disk group. Works with 5.11

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

Title:
  Can not boot after updating kernel to linux-image-5.13.0-27-generic

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

Bug description:
  After auto-updating kernel to linux-image-5.13.0-27-generic I can not
  boot into Ubuntu 20.04. But using an older kernel the boot works fine.

  Laptop- Razor Blade 15 Advanced Model (2021)

  The boot fails and drops to initramfs. Ubuntu can not find any disk
  mounted. The problem is similar to this :
  https://askubuntu.com/questions/15515/disk-by-uuid-not-detected-
  initramfs-boot-failure

  Using older kernel works fine
  $ uname -a
  Linux rraj-Blade-15-Advanced-Model-Mid-2021-RZ09-0409 5.11.0-46-generic 
#51~20.04.1-Ubuntu SMP Fri Jan 7 06:51:40 UTC 2022 x86_64 x86_64 x86_64 
GNU/Linux

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


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

[Kernel-packages] [Bug 1958850] Lspci.txt

[Kai-Chuan Hsieh]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1958850/+attachment/5556993/+files/Lspci.txt

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

Title:
  USB port lost function after unplugging usb drive from WD19TB dock

Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  Test the proposed 5.14 oem kernel, and get a failure symptom.

  Unplug a usb drive from WD19TB docking and a BUG reported in kernel,
  then the other embedded usb port can't detect usb drive anymore after
  a while.

  kernel: usb 5-2.3.3: USB disconnect, device number 5
  kernel: BUG: kernel NULL pointer dereference, address: 0030
  kernel: #PF: supervisor read access in kernel mode
  kernel: #PF: error_code(0x) - not-present page
  kernel: PGD 0 P4D 0
  kernel: Oops:  [#1] SMP NOPTI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  2205 F pulseaudio
   /dev/snd/controlC0:  u  2205 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-04-29 (270 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. Precision 5750
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem 
root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-1021-oem N/A
   linux-backports-modules-5.14.0-1021-oem  N/A
   linux-firmware   1.201.3
  Tags:  impish
  Uname: Linux 5.14.0-1021-oem x86_64
  UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990:
  dmi.product.family: Precision
  dmi.product.name: Precision 5750
  dmi.product.sku: 0990
  dmi.sys.vendor: Dell Inc.

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


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

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

[Kai-Chuan Hsieh]

apport information

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

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

Title:
  USB port lost function after unplugging usb drive from WD19TB dock

Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  Test the proposed 5.14 oem kernel, and get a failure symptom.

  Unplug a usb drive from WD19TB docking and a BUG reported in kernel,
  then the other embedded usb port can't detect usb drive anymore after
  a while.

  kernel: usb 5-2.3.3: USB disconnect, device number 5
  kernel: BUG: kernel NULL pointer dereference, address: 0030
  kernel: #PF: supervisor read access in kernel mode
  kernel: #PF: error_code(0x) - not-present page
  kernel: PGD 0 P4D 0
  kernel: Oops:  [#1] SMP NOPTI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  2205 F pulseaudio
   /dev/snd/controlC0:  u  2205 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-04-29 (270 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. Precision 5750
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem 
root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-1021-oem N/A
   linux-backports-modules-5.14.0-1021-oem  N/A
   linux-firmware   1.201.3
  Tags:  impish
  Uname: Linux 5.14.0-1021-oem x86_64
  UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990:
  dmi.product.family: Precision
  dmi.product.name: Precision 5750
  dmi.product.sku: 0990
  dmi.sys.vendor: Dell Inc.

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


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

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

[Kai-Chuan Hsieh]

apport information

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

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

Title:
  USB port lost function after unplugging usb drive from WD19TB dock

Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  Test the proposed 5.14 oem kernel, and get a failure symptom.

  Unplug a usb drive from WD19TB docking and a BUG reported in kernel,
  then the other embedded usb port can't detect usb drive anymore after
  a while.

  kernel: usb 5-2.3.3: USB disconnect, device number 5
  kernel: BUG: kernel NULL pointer dereference, address: 0030
  kernel: #PF: supervisor read access in kernel mode
  kernel: #PF: error_code(0x) - not-present page
  kernel: PGD 0 P4D 0
  kernel: Oops:  [#1] SMP NOPTI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  2205 F pulseaudio
   /dev/snd/controlC0:  u  2205 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-04-29 (270 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. Precision 5750
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem 
root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-1021-oem N/A
   linux-backports-modules-5.14.0-1021-oem  N/A
   linux-firmware   1.201.3
  Tags:  impish
  Uname: Linux 5.14.0-1021-oem x86_64
  UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990:
  dmi.product.family: Precision
  dmi.product.name: Precision 5750
  dmi.product.sku: 0990
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1958850] PulseList.txt

[Kai-Chuan Hsieh]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1958850/+attachment/5557004/+files/PulseList.txt

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

Title:
  USB port lost function after unplugging usb drive from WD19TB dock

Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  Test the proposed 5.14 oem kernel, and get a failure symptom.

  Unplug a usb drive from WD19TB docking and a BUG reported in kernel,
  then the other embedded usb port can't detect usb drive anymore after
  a while.

  kernel: usb 5-2.3.3: USB disconnect, device number 5
  kernel: BUG: kernel NULL pointer dereference, address: 0030
  kernel: #PF: supervisor read access in kernel mode
  kernel: #PF: error_code(0x) - not-present page
  kernel: PGD 0 P4D 0
  kernel: Oops:  [#1] SMP NOPTI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  2205 F pulseaudio
   /dev/snd/controlC0:  u  2205 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-04-29 (270 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. Precision 5750
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem 
root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-1021-oem N/A
   linux-backports-modules-5.14.0-1021-oem  N/A
   linux-firmware   1.201.3
  Tags:  impish
  Uname: Linux 5.14.0-1021-oem x86_64
  UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990:
  dmi.product.family: Precision
  dmi.product.name: Precision 5750
  dmi.product.sku: 0990
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1958850] CurrentDmesg.txt

[Kai-Chuan Hsieh]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1958850/+attachment/5556991/+files/CurrentDmesg.txt

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

Title:
  USB port lost function after unplugging usb drive from WD19TB dock

Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  Test the proposed 5.14 oem kernel, and get a failure symptom.

  Unplug a usb drive from WD19TB docking and a BUG reported in kernel,
  then the other embedded usb port can't detect usb drive anymore after
  a while.

  kernel: usb 5-2.3.3: USB disconnect, device number 5
  kernel: BUG: kernel NULL pointer dereference, address: 0030
  kernel: #PF: supervisor read access in kernel mode
  kernel: #PF: error_code(0x) - not-present page
  kernel: PGD 0 P4D 0
  kernel: Oops:  [#1] SMP NOPTI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  2205 F pulseaudio
   /dev/snd/controlC0:  u  2205 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-04-29 (270 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. Precision 5750
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem 
root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-1021-oem N/A
   linux-backports-modules-5.14.0-1021-oem  N/A
   linux-firmware   1.201.3
  Tags:  impish
  Uname: Linux 5.14.0-1021-oem x86_64
  UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990:
  dmi.product.family: Precision
  dmi.product.name: Precision 5750
  dmi.product.sku: 0990
  dmi.sys.vendor: Dell Inc.

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


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

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

[Kai-Chuan Hsieh]

apport information

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

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

Title:
  USB port lost function after unplugging usb drive from WD19TB dock

Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  Test the proposed 5.14 oem kernel, and get a failure symptom.

  Unplug a usb drive from WD19TB docking and a BUG reported in kernel,
  then the other embedded usb port can't detect usb drive anymore after
  a while.

  kernel: usb 5-2.3.3: USB disconnect, device number 5
  kernel: BUG: kernel NULL pointer dereference, address: 0030
  kernel: #PF: supervisor read access in kernel mode
  kernel: #PF: error_code(0x) - not-present page
  kernel: PGD 0 P4D 0
  kernel: Oops:  [#1] SMP NOPTI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  2205 F pulseaudio
   /dev/snd/controlC0:  u  2205 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-04-29 (270 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. Precision 5750
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem 
root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-1021-oem N/A
   linux-backports-modules-5.14.0-1021-oem  N/A
   linux-firmware   1.201.3
  Tags:  impish
  Uname: Linux 5.14.0-1021-oem x86_64
  UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990:
  dmi.product.family: Precision
  dmi.product.name: Precision 5750
  dmi.product.sku: 0990
  dmi.sys.vendor: Dell Inc.

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


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

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

[Kai-Chuan Hsieh]

apport information

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

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

Title:
  USB port lost function after unplugging usb drive from WD19TB dock

Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  Test the proposed 5.14 oem kernel, and get a failure symptom.

  Unplug a usb drive from WD19TB docking and a BUG reported in kernel,
  then the other embedded usb port can't detect usb drive anymore after
  a while.

  kernel: usb 5-2.3.3: USB disconnect, device number 5
  kernel: BUG: kernel NULL pointer dereference, address: 0030
  kernel: #PF: supervisor read access in kernel mode
  kernel: #PF: error_code(0x) - not-present page
  kernel: PGD 0 P4D 0
  kernel: Oops:  [#1] SMP NOPTI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  2205 F pulseaudio
   /dev/snd/controlC0:  u  2205 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-04-29 (270 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. Precision 5750
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem 
root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-1021-oem N/A
   linux-backports-modules-5.14.0-1021-oem  N/A
   linux-firmware   1.201.3
  Tags:  impish
  Uname: Linux 5.14.0-1021-oem x86_64
  UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990:
  dmi.product.family: Precision
  dmi.product.name: Precision 5750
  dmi.product.sku: 0990
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1958850] Lsusb.txt

[Kai-Chuan Hsieh]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1958850/+attachment/5556995/+files/Lsusb.txt

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

Title:
  USB port lost function after unplugging usb drive from WD19TB dock

Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  Test the proposed 5.14 oem kernel, and get a failure symptom.

  Unplug a usb drive from WD19TB docking and a BUG reported in kernel,
  then the other embedded usb port can't detect usb drive anymore after
  a while.

  kernel: usb 5-2.3.3: USB disconnect, device number 5
  kernel: BUG: kernel NULL pointer dereference, address: 0030
  kernel: #PF: supervisor read access in kernel mode
  kernel: #PF: error_code(0x) - not-present page
  kernel: PGD 0 P4D 0
  kernel: Oops:  [#1] SMP NOPTI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  2205 F pulseaudio
   /dev/snd/controlC0:  u  2205 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-04-29 (270 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. Precision 5750
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem 
root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-1021-oem N/A
   linux-backports-modules-5.14.0-1021-oem  N/A
   linux-firmware   1.201.3
  Tags:  impish
  Uname: Linux 5.14.0-1021-oem x86_64
  UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990:
  dmi.product.family: Precision
  dmi.product.name: Precision 5750
  dmi.product.sku: 0990
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1958850] CRDA.txt

[Kai-Chuan Hsieh]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1958850/+attachment/5556990/+files/CRDA.txt

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

Title:
  USB port lost function after unplugging usb drive from WD19TB dock

Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  Test the proposed 5.14 oem kernel, and get a failure symptom.

  Unplug a usb drive from WD19TB docking and a BUG reported in kernel,
  then the other embedded usb port can't detect usb drive anymore after
  a while.

  kernel: usb 5-2.3.3: USB disconnect, device number 5
  kernel: BUG: kernel NULL pointer dereference, address: 0030
  kernel: #PF: supervisor read access in kernel mode
  kernel: #PF: error_code(0x) - not-present page
  kernel: PGD 0 P4D 0
  kernel: Oops:  [#1] SMP NOPTI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  2205 F pulseaudio
   /dev/snd/controlC0:  u  2205 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-04-29 (270 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. Precision 5750
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem 
root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-1021-oem N/A
   linux-backports-modules-5.14.0-1021-oem  N/A
   linux-firmware   1.201.3
  Tags:  impish
  Uname: Linux 5.14.0-1021-oem x86_64
  UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990:
  dmi.product.family: Precision
  dmi.product.name: Precision 5750
  dmi.product.sku: 0990
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1958850] Lsusb-t.txt

[Kai-Chuan Hsieh]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1958850/+attachment/5556996/+files/Lsusb-t.txt

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

Title:
  USB port lost function after unplugging usb drive from WD19TB dock

Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  Test the proposed 5.14 oem kernel, and get a failure symptom.

  Unplug a usb drive from WD19TB docking and a BUG reported in kernel,
  then the other embedded usb port can't detect usb drive anymore after
  a while.

  kernel: usb 5-2.3.3: USB disconnect, device number 5
  kernel: BUG: kernel NULL pointer dereference, address: 0030
  kernel: #PF: supervisor read access in kernel mode
  kernel: #PF: error_code(0x) - not-present page
  kernel: PGD 0 P4D 0
  kernel: Oops:  [#1] SMP NOPTI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  2205 F pulseaudio
   /dev/snd/controlC0:  u  2205 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-04-29 (270 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. Precision 5750
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem 
root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-1021-oem N/A
   linux-backports-modules-5.14.0-1021-oem  N/A
   linux-firmware   1.201.3
  Tags:  impish
  Uname: Linux 5.14.0-1021-oem x86_64
  UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990:
  dmi.product.family: Precision
  dmi.product.name: Precision 5750
  dmi.product.sku: 0990
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1958850] ProcEnviron.txt

[Kai-Chuan Hsieh]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1958850/+attachment/5557001/+files/ProcEnviron.txt

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

Title:
  USB port lost function after unplugging usb drive from WD19TB dock

Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  Test the proposed 5.14 oem kernel, and get a failure symptom.

  Unplug a usb drive from WD19TB docking and a BUG reported in kernel,
  then the other embedded usb port can't detect usb drive anymore after
  a while.

  kernel: usb 5-2.3.3: USB disconnect, device number 5
  kernel: BUG: kernel NULL pointer dereference, address: 0030
  kernel: #PF: supervisor read access in kernel mode
  kernel: #PF: error_code(0x) - not-present page
  kernel: PGD 0 P4D 0
  kernel: Oops:  [#1] SMP NOPTI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  2205 F pulseaudio
   /dev/snd/controlC0:  u  2205 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-04-29 (270 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. Precision 5750
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem 
root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-1021-oem N/A
   linux-backports-modules-5.14.0-1021-oem  N/A
   linux-firmware   1.201.3
  Tags:  impish
  Uname: Linux 5.14.0-1021-oem x86_64
  UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990:
  dmi.product.family: Precision
  dmi.product.name: Precision 5750
  dmi.product.sku: 0990
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1958850] Lsusb-v.txt

[Kai-Chuan Hsieh]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1958850/+attachment/5556997/+files/Lsusb-v.txt

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

Title:
  USB port lost function after unplugging usb drive from WD19TB dock

Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  Test the proposed 5.14 oem kernel, and get a failure symptom.

  Unplug a usb drive from WD19TB docking and a BUG reported in kernel,
  then the other embedded usb port can't detect usb drive anymore after
  a while.

  kernel: usb 5-2.3.3: USB disconnect, device number 5
  kernel: BUG: kernel NULL pointer dereference, address: 0030
  kernel: #PF: supervisor read access in kernel mode
  kernel: #PF: error_code(0x) - not-present page
  kernel: PGD 0 P4D 0
  kernel: Oops:  [#1] SMP NOPTI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  2205 F pulseaudio
   /dev/snd/controlC0:  u  2205 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-04-29 (270 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. Precision 5750
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem 
root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-1021-oem N/A
   linux-backports-modules-5.14.0-1021-oem  N/A
   linux-firmware   1.201.3
  Tags:  impish
  Uname: Linux 5.14.0-1021-oem x86_64
  UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990:
  dmi.product.family: Precision
  dmi.product.name: Precision 5750
  dmi.product.sku: 0990
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1958850] Lspci-vt.txt

[Kai-Chuan Hsieh]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1958850/+attachment/5556994/+files/Lspci-vt.txt

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

Title:
  USB port lost function after unplugging usb drive from WD19TB dock

Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  Test the proposed 5.14 oem kernel, and get a failure symptom.

  Unplug a usb drive from WD19TB docking and a BUG reported in kernel,
  then the other embedded usb port can't detect usb drive anymore after
  a while.

  kernel: usb 5-2.3.3: USB disconnect, device number 5
  kernel: BUG: kernel NULL pointer dereference, address: 0030
  kernel: #PF: supervisor read access in kernel mode
  kernel: #PF: error_code(0x) - not-present page
  kernel: PGD 0 P4D 0
  kernel: Oops:  [#1] SMP NOPTI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  2205 F pulseaudio
   /dev/snd/controlC0:  u  2205 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-04-29 (270 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. Precision 5750
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem 
root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-1021-oem N/A
   linux-backports-modules-5.14.0-1021-oem  N/A
   linux-firmware   1.201.3
  Tags:  impish
  Uname: Linux 5.14.0-1021-oem x86_64
  UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990:
  dmi.product.family: Precision
  dmi.product.name: Precision 5750
  dmi.product.sku: 0990
  dmi.sys.vendor: Dell Inc.

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


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

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

[Kai-Chuan Hsieh]

apport information

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

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

Title:
  USB port lost function after unplugging usb drive from WD19TB dock

Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  Test the proposed 5.14 oem kernel, and get a failure symptom.

  Unplug a usb drive from WD19TB docking and a BUG reported in kernel,
  then the other embedded usb port can't detect usb drive anymore after
  a while.

  kernel: usb 5-2.3.3: USB disconnect, device number 5
  kernel: BUG: kernel NULL pointer dereference, address: 0030
  kernel: #PF: supervisor read access in kernel mode
  kernel: #PF: error_code(0x) - not-present page
  kernel: PGD 0 P4D 0
  kernel: Oops:  [#1] SMP NOPTI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  2205 F pulseaudio
   /dev/snd/controlC0:  u  2205 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-04-29 (270 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. Precision 5750
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem 
root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-1021-oem N/A
   linux-backports-modules-5.14.0-1021-oem  N/A
   linux-firmware   1.201.3
  Tags:  impish
  Uname: Linux 5.14.0-1021-oem x86_64
  UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990:
  dmi.product.family: Precision
  dmi.product.name: Precision 5750
  dmi.product.sku: 0990
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1958850] IwConfig.txt

[Kai-Chuan Hsieh]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1958850/+attachment/5556992/+files/IwConfig.txt

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

Title:
  USB port lost function after unplugging usb drive from WD19TB dock

Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  Test the proposed 5.14 oem kernel, and get a failure symptom.

  Unplug a usb drive from WD19TB docking and a BUG reported in kernel,
  then the other embedded usb port can't detect usb drive anymore after
  a while.

  kernel: usb 5-2.3.3: USB disconnect, device number 5
  kernel: BUG: kernel NULL pointer dereference, address: 0030
  kernel: #PF: supervisor read access in kernel mode
  kernel: #PF: error_code(0x) - not-present page
  kernel: PGD 0 P4D 0
  kernel: Oops:  [#1] SMP NOPTI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  2205 F pulseaudio
   /dev/snd/controlC0:  u  2205 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-04-29 (270 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. Precision 5750
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem 
root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-1021-oem N/A
   linux-backports-modules-5.14.0-1021-oem  N/A
   linux-firmware   1.201.3
  Tags:  impish
  Uname: Linux 5.14.0-1021-oem x86_64
  UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990:
  dmi.product.family: Precision
  dmi.product.name: Precision 5750
  dmi.product.sku: 0990
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1958850] AlsaInfo.txt

[Kai-Chuan Hsieh]

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1958850/+attachment/5556989/+files/AlsaInfo.txt

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

Title:
  USB port lost function after unplugging usb drive from WD19TB dock

Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  Test the proposed 5.14 oem kernel, and get a failure symptom.

  Unplug a usb drive from WD19TB docking and a BUG reported in kernel,
  then the other embedded usb port can't detect usb drive anymore after
  a while.

  kernel: usb 5-2.3.3: USB disconnect, device number 5
  kernel: BUG: kernel NULL pointer dereference, address: 0030
  kernel: #PF: supervisor read access in kernel mode
  kernel: #PF: error_code(0x) - not-present page
  kernel: PGD 0 P4D 0
  kernel: Oops:  [#1] SMP NOPTI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  2205 F pulseaudio
   /dev/snd/controlC0:  u  2205 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-04-29 (270 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. Precision 5750
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem 
root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-1021-oem N/A
   linux-backports-modules-5.14.0-1021-oem  N/A
   linux-firmware   1.201.3
  Tags:  impish
  Uname: Linux 5.14.0-1021-oem x86_64
  UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990:
  dmi.product.family: Precision
  dmi.product.name: Precision 5750
  dmi.product.sku: 0990
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1958850] [NEW] USB port lost function after unplugging usb drive from WD19TB dock

[Kai-Chuan Hsieh]

Public bug reported:

Test the proposed 5.14 oem kernel, and get a failure symptom.

Unplug a usb drive from WD19TB docking and a BUG reported in kernel,
then the other embedded usb port can't detect usb drive anymore after a
while.

kernel: usb 5-2.3.3: USB disconnect, device number 5
kernel: BUG: kernel NULL pointer dereference, address: 0030
kernel: #PF: supervisor read access in kernel mode
kernel: #PF: error_code(0x) - not-present page
kernel: PGD 0 P4D 0
kernel: Oops:  [#1] SMP NOPTI
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  u  2205 F pulseaudio
 /dev/snd/controlC0:  u  2205 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2021-04-29 (270 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: Dell Inc. Precision 5750
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem 
root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21
RelatedPackageVersions:
 linux-restricted-modules-5.14.0-1021-oem N/A
 linux-backports-modules-5.14.0-1021-oem  N/A
 linux-firmware   1.201.3
Tags:  impish
Uname: Linux 5.14.0-1021-oem x86_64
UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago)
UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/18/2021
dmi.bios.release: 1.11
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.11.1
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990:
dmi.product.family: Precision
dmi.product.name: Precision 5750
dmi.product.sku: 0990
dmi.sys.vendor: Dell Inc.

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


** Tags: apport-collected impish oem-priority originate-from-1958840

** Attachment added: "kern.log"
   https://bugs.launchpad.net/bugs/1958850/+attachment/5556988/+files/kern.log

** Tags added: apport-collected impish

** Description changed:

  Test the proposed 5.14 oem kernel, and get a failure symptom.
  
  Unplug a usb drive from WD19TB docking and a BUG reported in kernel,
  then the other embedded usb port can't detect usb drive anymore after a
  while.
  
  kernel: usb 5-2.3.3: USB disconnect, device number 5
  kernel: BUG: kernel NULL pointer dereference, address: 0030
  kernel: #PF: supervisor read access in kernel mode
  kernel: #PF: error_code(0x) - not-present page
  kernel: PGD 0 P4D 0
  kernel: Oops:  [#1] SMP NOPTI
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu71
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  u  2205 F pulseaudio
+  /dev/snd/controlC0:  u  2205 F pulseaudio
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 21.10
+ InstallationDate: Installed on 2021-04-29 (270 days ago)
+ InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
+ MachineType: Dell Inc. Precision 5750
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem 
root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21
+ RelatedPackageVersions:
+  linux-restricted-modules-5.14.0-1021-oem N/A
+  linux-backports-modules-5.14.0-1021-oem  N/A
+  linux-firmware   1.201.3
+ Tags:  impish
+ Uname: Linux 5.14.0-1021-oem x86_64
+ UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago)
+ UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 11/18/2021
+ dmi.bios.release: 1.11
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 1.11.1
+ dmi.board.vendor: Dell Inc.
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990:
+ dmi.product.family: Precision
+ dmi.product.name: Precision 5750
+ dmi.product.sku: 0990
+ dmi.sys.vendor: Dell Inc.

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

Title:
  USB port lost function after unplugging usb drive from WD19TB dock

Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  Test the proposed 5.14 oem kernel, and get a failure symptom.

  Unplug 

[Kernel-packages] [Bug 1810239]

[biergaizi2009]

(In reply to Tom Li from comment #138)
> (In reply to sbingner from comment #136)
> > Also "Marvell Technology Group Ltd. 88SE9125 PCIe SATA 6.0 Gb/s controller
> > [...]
> > Is this sufficient or should I open a new bug?
> 
> I have the same hardware and was able to test and confirm the bug. I just
> submitted the patch to the Linux kernel maintainers. Hopefully it'll be
> accepted soon.
> 
> https://patchwork.kernel.org/project/linux-pci/patch/YZPA+gSsGWI6+xBP@work/

Patch for 88SE9125 has been merged into the upstream kernel since Linux
v5.17-rc1.

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e445375882883f69018aa669b67cbb37ec873406

Greg K.H. has also queued this patch for Linux 4.4, 4.9, 4.14, 5.4,
5.10, 5.15, 5.16. The patch should appear in the next stable kernel
release in each branch.

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

Title:
  amd_iommu conflict with  Marvell 88SE9230 SATA Controller

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Debian:
  Fix Released
Status in linux package in Fedora:
  Unknown

Bug description:
  Booting with kernel 4.18.0-13.14~18.04.1-generic shows errors:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/153

  WORKAROUND: Use kernel boot parameter:
  amd_iommu=off

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mythfe 1170 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=/dev/mythnew/swap
  InstallationDate: Installed on 2016-07-02 (913 days ago)
  InstallationMedia: Mythbuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.

   enp9s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. B450M S2H
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/mythnew-root ro verbose 
drm_kms_helper.edid_firmware=HDMI-A-3:edid/panasonic.edid
  ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.173.2
  RfKill:

  Tags:  bionic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-07-27 (158 days ago)
  UserGroups: adm cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 12/04/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2c
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M S2H
  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.:bvrF2c:bd12/04/2018:svnGigabyteTechnologyCo.,Ltd.:pnB450MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M S2H
  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/linux/+bug/1810239/+subscriptions


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

[Kernel-packages] [Bug 1942691] Re: linux-modules remove rpi_poe_fan module after reboot

[Pascal van Dam]

I will give a full example in thursday. The issue is still there.

In proza:

If I do not put the module in /etc/initramfs-tools/modules the module
will not be there after a reboot (e.g. remove from the filesystem).

And this is so for a lot of the other modules. I am booting from iSCSI
and even the NFS modules are gone. As far as I know this wasn't the case
in previous version.

Behaviour has been detected in:
  20.04, 21.04 and 21.10

Apologies for the delay

Kind regards,

   Pascal

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

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

Title:
  linux-modules remove rpi_poe_fan module after reboot

Status in linux-raspi package in Ubuntu:
  New

Bug description:
  When installing linux-modules-5.11.0-1016-raspi 5.11.0-1016.17 I do
  get the rpi_poe_fan module and can modprobe or insmod it. I can even
  find it under the relevant path in /lib/modules.

  After a reboot it appears that the module has been removed. Why?

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


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

[Kernel-packages] [Bug 1956177] Re: battery not detected by ACPI

[Patrick Walz]

** Attachment added: "DSDT.aml for BIOS Rev 1.10"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+attachment/5556980/+files/10_DSDT.aml

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

Title:
  battery not detected by ACPI

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with 
kernel 5.13.0-22-generic, there is an issue with the internal battery. When 
kernel boots up, ACPI isn't able to detect it correctly, see dmesg line:
  [0.528105] ACPI: battery: Slot [BAT1] (battery absent)

  But asking lshw for power devices, it says:
  *-battery 
 description: Lithium Ion Battery
 product: CP753347-01
 vendor: FUJITSU
 physical id: 1
 serial: 02A-Z201219003557Z
 slot: Internal Battery
 capacity: 45032mWh
 configuration: voltage=10,8V

  I've updated the BIOS to latest version 1.12 already, with no better result. 
What is the problem here, and how can I fix it?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thomas  945 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-12-31 (4 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic 
root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  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
  Tags:  impish
  Uname: Linux 5.13.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/22/2021
  dmi.bios.release: 1.12
  dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.bios.version: Version 1.12
  dmi.board.name: FJNBB6D
  dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.board.version: EQAB073106
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00:
  dmi.product.family: LIFEBOOK-FTS
  dmi.product.name: LIFEBOOK A3510
  dmi.product.sku: SK00
  dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED

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


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

[Kernel-packages] [Bug 1956177] Re: battery not detected by ACPI

[Patrick Walz]

** Attachment added: "DSDT.aml for BIOS Rev 1.12"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+attachment/5556981/+files/12_DSDT.aml

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

Title:
  battery not detected by ACPI

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with 
kernel 5.13.0-22-generic, there is an issue with the internal battery. When 
kernel boots up, ACPI isn't able to detect it correctly, see dmesg line:
  [0.528105] ACPI: battery: Slot [BAT1] (battery absent)

  But asking lshw for power devices, it says:
  *-battery 
 description: Lithium Ion Battery
 product: CP753347-01
 vendor: FUJITSU
 physical id: 1
 serial: 02A-Z201219003557Z
 slot: Internal Battery
 capacity: 45032mWh
 configuration: voltage=10,8V

  I've updated the BIOS to latest version 1.12 already, with no better result. 
What is the problem here, and how can I fix it?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thomas  945 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-12-31 (4 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic 
root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  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
  Tags:  impish
  Uname: Linux 5.13.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/22/2021
  dmi.bios.release: 1.12
  dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.bios.version: Version 1.12
  dmi.board.name: FJNBB6D
  dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.board.version: EQAB073106
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00:
  dmi.product.family: LIFEBOOK-FTS
  dmi.product.name: LIFEBOOK A3510
  dmi.product.sku: SK00
  dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED

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


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

[Kernel-packages] [Bug 1956177] Re: battery not detected by ACPI

[Patrick Walz]

I managed to rudimentarily fix it via DSDT. So far everything seems to be in 
working order.
I will attached three aml files for BIOS Revisions 1.09, 1.10, 1.12 and another 
required file 01_acpi.

One of the aml files needs to be copied into /boot (acording to your BIOS Rev.) 
and renamed into dsdt.aml, 01_acpi needs to be copied to /etc/grub.d/ 
Follow this with update-grub, reboot and the battery symbol should be there.

** Attachment added: "01_acpi"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+attachment/5556978/+files/01_acpi

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

Title:
  battery not detected by ACPI

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with 
kernel 5.13.0-22-generic, there is an issue with the internal battery. When 
kernel boots up, ACPI isn't able to detect it correctly, see dmesg line:
  [0.528105] ACPI: battery: Slot [BAT1] (battery absent)

  But asking lshw for power devices, it says:
  *-battery 
 description: Lithium Ion Battery
 product: CP753347-01
 vendor: FUJITSU
 physical id: 1
 serial: 02A-Z201219003557Z
 slot: Internal Battery
 capacity: 45032mWh
 configuration: voltage=10,8V

  I've updated the BIOS to latest version 1.12 already, with no better result. 
What is the problem here, and how can I fix it?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thomas  945 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-12-31 (4 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic 
root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  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
  Tags:  impish
  Uname: Linux 5.13.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/22/2021
  dmi.bios.release: 1.12
  dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.bios.version: Version 1.12
  dmi.board.name: FJNBB6D
  dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.board.version: EQAB073106
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00:
  dmi.product.family: LIFEBOOK-FTS
  dmi.product.name: LIFEBOOK A3510
  dmi.product.sku: SK00
  dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED

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


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

[Kernel-packages] [Bug 1956177] Re: battery not detected by ACPI

[Patrick Walz]

** Attachment added: "DSDT.aml for BIOS Rev 1.09"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+attachment/5556979/+files/09_DSDT.aml

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

Title:
  battery not detected by ACPI

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with 
kernel 5.13.0-22-generic, there is an issue with the internal battery. When 
kernel boots up, ACPI isn't able to detect it correctly, see dmesg line:
  [0.528105] ACPI: battery: Slot [BAT1] (battery absent)

  But asking lshw for power devices, it says:
  *-battery 
 description: Lithium Ion Battery
 product: CP753347-01
 vendor: FUJITSU
 physical id: 1
 serial: 02A-Z201219003557Z
 slot: Internal Battery
 capacity: 45032mWh
 configuration: voltage=10,8V

  I've updated the BIOS to latest version 1.12 already, with no better result. 
What is the problem here, and how can I fix it?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thomas  945 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-12-31 (4 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic 
root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  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
  Tags:  impish
  Uname: Linux 5.13.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/22/2021
  dmi.bios.release: 1.12
  dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.bios.version: Version 1.12
  dmi.board.name: FJNBB6D
  dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.board.version: EQAB073106
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00:
  dmi.product.family: LIFEBOOK-FTS
  dmi.product.name: LIFEBOOK A3510
  dmi.product.sku: SK00
  dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED

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


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

[Kernel-packages] [Bug 1942691] Re: linux-modules remove rpi_poe_fan module after reboot

[Juerg Haefliger]

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

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

Title:
  linux-modules remove rpi_poe_fan module after reboot

Status in linux-raspi package in Ubuntu:
  Invalid

Bug description:
  When installing linux-modules-5.11.0-1016-raspi 5.11.0-1016.17 I do
  get the rpi_poe_fan module and can modprobe or insmod it. I can even
  find it under the relevant path in /lib/modules.

  After a reboot it appears that the module has been removed. Why?

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


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

[Kernel-packages] [Bug 1956103] Re: Ubuntu Server image doesn't include common USB drivers / modules

[Juerg Haefliger]

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

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

Title:
  Ubuntu Server image doesn't include common USB drivers / modules

Status in linux-raspi package in Ubuntu:
  Invalid

Bug description:
  I tried using Ubuntu Server 21.10 (32 Bit) on a Raspberry Pi 3b but
  some common USB devices didn't work. On closer inspection the kernel
  modules were missing -

  Common USB serial adapters: ftdi_sio,pl2303
  Common USB modems including 3G Dongles: cdc_acm

  I understand the Ubuntu Server image is meant to be lightweight but I
  think these devices are common enough to include support for.

  Thanks!

  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu 21.10
  Release:  21.10

  root@ubuntu:~# lsmod
  Module  Size  Used by
  cmac   16384  3
  algif_hash 16384  1
  algif_skcipher 16384  1
  af_alg 28672  6 algif_hash,algif_skcipher
  bnep   32768  2
  hci_uart  135168  1
  btqca  28672  1 hci_uart
  btrtl  24576  1 hci_uart
  btbcm  16384  1 hci_uart
  btintel36864  1 hci_uart
  bluetooth 614400  29 btrtl,hci_uart,btintel,btqca,bnep,btbcm
  ecdh_generic   16384  2 bluetooth
  ecc40960  1 ecdh_generic
  dm_multipath   40960  0
  brcmfmac  389120  0
  brcmutil   24576  1 brcmfmac
  cfg80211  835584  1 brcmfmac
  bcm2835_isp32768  0
  bcm2835_codec  40960  0
  bcm2835_v4l2   45056  0
  v4l2_mem2mem   36864  1 bcm2835_codec
  bcm2835_mmal_vchiq 45056  3 bcm2835_isp,bcm2835_codec,bcm2835_v4l2
  videobuf2_vmalloc  20480  1 bcm2835_v4l2
  videobuf2_dma_contig24576  2 bcm2835_isp,bcm2835_codec
  videobuf2_memops   20480  2 videobuf2_dma_contig,videobuf2_vmalloc
  videobuf2_v4l2 32768  4 
bcm2835_isp,bcm2835_codec,bcm2835_v4l2,v4l2_mem2mem
  snd_bcm283532768  0
  videobuf2_common   69632  8 
bcm2835_isp,bcm2835_codec,videobuf2_dma_contig,videobuf2_vmalloc,videobuf2_memops,bcm2835_v4l2,v4l2_mem2mem,videobuf2_v4l2
  raspberrypi_hwmon  16384  0
  snd_pcm   118784  1 snd_bcm2835
  videodev  262144  6 
bcm2835_isp,bcm2835_codec,videobuf2_common,bcm2835_v4l2,v4l2_mem2mem,videobuf2_v4l2
  snd_timer  40960  1 snd_pcm
  mc 65536  6 
bcm2835_isp,bcm2835_codec,videobuf2_common,videodev,v4l2_mem2mem,videobuf2_v4l2
  snd90112  3 snd_timer,snd_bcm2835,snd_pcm
  vc_sm_cma  45056  2 bcm2835_isp,bcm2835_mmal_vchiq
  bcm2835_gpiomem16384  0
  uio_pdrv_genirq20480  0
  uio24576  1 uio_pdrv_genirq
  sch_fq_codel   20480  2
  drm   540672  0
  ip_tables  28672  0
  x_tables   36864  1 ip_tables
  autofs453248  2
  btrfs1527808  0
  blake2b_generic36864  0
  zstd_compress 172032  1 btrfs
  raid10 73728  0
  raid456   176128  0
  async_raid6_recov  24576  1 raid456
  async_memcpy   20480  2 raid456,async_raid6_recov
  async_pq   20480  2 raid456,async_raid6_recov
  async_xor  20480  3 async_pq,raid456,async_raid6_recov
  async_tx   20480  5 
async_xor,async_pq,raid456,async_memcpy,async_raid6_recov
  xor16384  2 async_xor,btrfs
  xor_neon   16384  1 xor
  raid6_pq  110592  4 async_pq,btrfs,raid456,async_raid6_recov
  libcrc32c  16384  2 btrfs,raid456
  raid1  53248  0
  raid0  24576  0
  multipath  20480  0
  linear 20480  0
  spidev 24576  0
  crc32_arm_ce   16384  2
  i2c_bcm283516384  0
  spi_bcm283528672  0
  phy_generic20480  0
  aes_arm_bs 24576  2
  crypto_simd16384  1 aes_arm_bs
  cryptd 24576  2 crypto_simd

  root@ubuntu:~# cat /etc/*release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=21.10
  DISTRIB_CODENAME=impish
  DISTRIB_DESCRIPTION="Ubuntu 21.10"
  PRETTY_NAME="Ubuntu 21.10"
  NAME="Ubuntu"
  VERSION_ID="21.10"
  VERSION="21.10 (Impish Indri)"
  VERSION_CODENAME=impish
  ID=ubuntu
  ID_LIKE=debian
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  UBUNTU_CODENAME=impish

  root@ubuntu:~# uname -a
  Linux ubuntu 5.13.0-1008-raspi #9-Ubuntu SMP PREEMPT Wed Sep 29 08:30:56 UTC 
2021 armv7l armv7l armv7l GNU/Linux

To manage notifications about this bug go 

[Kernel-packages] [Bug 1954680] Re: zcrypt DD: Toleration for new IBM Z Crypto Hardware - (Backport to Ubuntu 20.04)

[Frank Heimes]

Many thx Harald! (adjusting the tags now).

** 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1954680

Title:
  zcrypt DD: Toleration for new IBM Z Crypto Hardware - (Backport to
  Ubuntu 20.04)

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 Hirsute:
  Fix Committed
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * CEX8 hardware CryptoExpress adapter shall support quantum-safe crypto
 and therefore require nowadays message sizes > 12kB.

   * This change here is mainly required to support EP11 responses to admin 
requests at zNext
 which due to QS certificates can grow larger than 12kB.

   * It's to cover a minimal patch to provide toleration support for this 
feature
 which shall be back-ported to all distribution releases in service at zNext

   * This SRU requests belongs to the hardware enablement case.

  [Fix]

   * bd39654a2282 bd39654a2282c1a51c044575a6bc00d641d5dfd1 "s390/AP:
  support new dynamic AP bus size limit"

  [Test Plan]

   * An Ubuntu 20.04 (respectively 21.04) LPAR or z/VM guest is needed
 that has access to at least one online crypto domain.

   * Ideally using a CEX8 adapter (but can be too early to get one).

   * Then get the patched kernel installed (see PPA below).

   * And look for the /sys/devices/ap/cardxx/max_msg_size sysfs
  attributes.

   * On top IBM has some more in-depth zcrypt tests (see also
  LP#1933805).

  [Where problems could occur]

   * First of all the modification are limited to:
 the zcrypt driver ("/drivers/s390/crypto/ap_*.*" and
 "/drivers/s390/crypto/zcrypt_*.*")
 hence are s390x platform specific and crypto specific and
 should even affect CEX8 cards only.
 So in case anything fails, it's limited to s390x cryptography,
 which usually allows sw fall-backs.

   * The function signature of ap_queue_info and ap_test_queue got modified,
 which may lead to issues if called with the old signatures,
 but that would be identified by the test compile already.

   * Some minor new structures like 'info', 'ml' got introduced,
 but are properly declared and initialized.

   * The way ap_queue_info and ap_card_create get filled and used was changed,
 therefore in some code areas slightly different data might be expected,
 if not properly adapted to the new way.
 But a verification test will prove this.

   * The actual msg length is now handled based on bufsize rather than len
 and with that zq is calculated in a different way (using 
zcrypt_queue_alloc)
 which may cause some side effects if not properly (alloc)
 or not thoroughly done.
 
   * in _zcrypt_send_cprb and _zcrypt_send_ep11_cprb some additional 
calculations
 and checks (if-stmts) were introduced, but they look sane.

   * New code to identify older cards got added, since message sizes > 12kB
 are supported by CEX8 and higher only.
 The dispatcher responsible for choosing the right card and queue is aware
 of the individual card AP bus message limit.
 But already at the user space tools it should be ensured that the right
 card is used.

   * Nevertheless, the patch is not small, hence s390x hardware crypto
 zcrypt driver needs to be properly re-tested.
 
  [Other Info]
   
   * The above commit/patch is upstream accepted with 5.14.

   * Impish's Kernel 5.13 was already patched, based on LP#1933805.

   * With that there is already a certain level of testing that was done
 based on Impish (since the zcrypt driver is largely the same now with
 these cherry-picks).

   * Hence the SRU is only needed for Focal
 and Hirsute (just to avoid regressions on upgrades).
  __

  Toleration support for new IBM Z crypto hardware - Backport to focal
  (20.04)

  Patch from kernel 5.14:

  Summary: s390/AP: support new dynamic AP bus size limit
  Description: This patch provides support for new dynamic AP bus
   message limit with the existing zcrypt device driver
   and AP bus core code. There is support for a new
   field 'ml' from the TAPQ query which indicates the
   per card AP bus message size limit. This TAPQ
   improvement will come with an updated firmware and
   this patch exploits this new field and thus makes
   it possible to send/receive AP messages greater
   than the current limit of 12K.
  Upstream-ID: bd39654a2282c1a51c044575a6bc00d641d5dfd1

To manage notifications about this bug go to: