[Kernel-packages] [Bug 1976125] ProcEnviron.txt

[Sugihwaras]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1976125/+attachment/5593502/+files/ProcEnviron.txt

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

Title:
  The webcam image displayed has problems

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  i try open cheese webcam but image displayed has problems. i try
  another webcam app like Guvcview can display image normally

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  Uname: Linux 5.17.9-xanmod1 x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 28 03:16:15 2022
  InstallationDate: Installed on 2022-05-27 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220524)
  MachineType: Dell Inc. Inspiron 3442
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2020
  dmi.bios.release: 65.16
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0T57PC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A16
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/02/2020:br65.16:svnDellInc.:pnInspiron3442:pvrNotSpecified:rvnDellInc.:rn0T57PC:rvrA16:cvnDellInc.:ct8:cvrNotSpecified:sku0651:
  dmi.product.name: Inspiron 3442
  dmi.product.sku: 0651
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-27 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220524)
  NonfreeKernelModules: wl
  Package: linux (not installed)
  Tags:  jammy wayland-session
  Uname: Linux 5.17.9-xanmod1 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-27 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220524)
  NonfreeKernelModules: wl
  Package: linux (not installed)
  Tags:  jammy wayland-session
  Uname: Linux 5.18.0-051800-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Kernel-packages] [Bug 1976125] Re: The webcam image displayed has problems

[Sugihwaras]

apport information

** Description changed:

  i try open cheese webcam but image displayed has problems. i try another
  webcam app like Guvcview can display image normally
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  Uname: Linux 5.17.9-xanmod1 x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 28 03:16:15 2022
  InstallationDate: Installed on 2022-05-27 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220524)
  MachineType: Dell Inc. Inspiron 3442
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2020
  dmi.bios.release: 65.16
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0T57PC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A16
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/02/2020:br65.16:svnDellInc.:pnInspiron3442:pvrNotSpecified:rvnDellInc.:rn0T57PC:rvrA16:cvnDellInc.:ct8:cvrNotSpecified:sku0651:
  dmi.product.name: Inspiron 3442
  dmi.product.sku: 0651
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-27 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220524)
  NonfreeKernelModules: wl
  Package: linux (not installed)
  Tags:  jammy wayland-session
  Uname: Linux 5.17.9-xanmod1 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.1
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2022-05-27 (0 days ago)
+ InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220524)
+ NonfreeKernelModules: wl
+ Package: linux (not installed)
+ Tags:  jammy wayland-session
+ Uname: Linux 5.18.0-051800-generic x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  The webcam image displayed has problems

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  i try open cheese webcam but image displayed has problems. i try
  another webcam app like Guvcview can display image normally

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  Uname: Linux 5.17.9-xanmod1 x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 28 03:16:15 2022
  InstallationDate: Installed on 2022-05-27 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220524)
  MachineType: Dell Inc. Inspiron 3442
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2020
  dmi.bios.release: 65.16
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0T57PC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A16
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/02/2020:br65.16:svnDellInc.:pnInspiron3442:pvrNotSpecified:rvnDellInc.:rn0T57PC:rvrA16:cvnDellInc.:ct8:cvrNotSpecified:sku0651:
  dmi.product.name: Inspiron 3442
  dmi.product.sku: 0651
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-27 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220524)
  NonfreeKernelModules: wl
  Package: linux (not installed)
  Tags:  jammy wayland-session
  Uname: Linux 5.17.9-xanmod1 x86_64
  UnreportableReason: The running kernel is not 

[Kernel-packages] [Bug 1965075] Re: arm64 suport

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
gcp-5.15/5.15.0-1005.8~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal' 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-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1965075

Title:
  arm64 suport

Status in linux-gcp package in Ubuntu:
  Fix Released
Status in linux-gcp source package in Bionic:
  New
Status in linux-gcp source package in Focal:
  New
Status in linux-gcp source package in Jammy:
  Fix Released

Bug description:
  
  [Impact]
  No support for arm64 currently

  [Fix]
  Add arm64 support, including hardware support patches

  [Test]
  Confirm that it boots on desired arm64 hardware, as well as VMs

  [Regression Potential]
  This was never working on arm64 so there should be no risk of regression.
  The requested changes included some refactorings of early memory 
initialization code (all arches) so this presents a small risk. The changes 
were tested on arm64 as well amd64.

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


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

[Kernel-packages] [Bug 1942215] Re: OOPs on boot: invalid opcode: 0000 [#1] SMP NOPTI

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1006.8~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1942215

Title:
  OOPs on boot: invalid opcode:  [#1] SMP NOPTI

Status in Linux:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Impish:
  Incomplete

Bug description:
  Using latest Impish kernel 5.13.0-15.15 from ckt/bootstrap PPA, upon
  boot on vought we get this:

  ...
  [   11.502916] invalid opcode:  [#1] SMP NOPTI
  [   11.504249] CPU: 95 PID: 1472 Comm: systemd-udevd Not tainted 
5.13.0-15-generic #15-Ubuntu
  [   11.505734] Hardware name: Intel Corporation S2600WFD/S2600WFD, BIOS 
SE5C620.86B.0D.01.0395.022720191340 02/27/2019
  [   11.507260] RIP: 0010:acpi_ds_exec_end_op+0x187/0x774
  [   11.508771] Code: 77 28 48 8b 04 c5 00 9b ea 91 48 89 df ff d0 0f 1f 00 41 
89 c4 e9 8f 00 00 00 0f b6 43 0d 8d 50 ff 48 63 d2 48 83 fa 09 76 02 <0f> 0b 83 
c0 6c 0f b7 7b 0a 48 89 da 48 98 48 8d 34 c3 e8 c0 3c 01
  [   11.511898] RSP: 0018:aaeca1a776e0 EFLAGS: 00010286
  [   11.513428] RAX:  RBX: 8f08a7573800 RCX: 
0040
  [   11.514972] RDX:  RSI: 91ea9980 RDI: 
02cb
  [   11.516100] RBP: aaeca1a77710 R08:  R09: 
8f08a8c84af0
  [   11.517479] R10:  R11: 0003 R12: 

  [   11.518985] R13: 8f08a8c84af0 R14:  R15: 

  [   11.520425] FS:  7f7fb403ed00() GS:8f348d5c() 
knlGS:
  [   11.521931] CS:  0010 DS:  ES:  CR0: 80050033
  [   11.523424] CR2: 7f7fb38d1918 CR3: 000129b6a002 CR4: 
007706e0
  [   11.524924] DR0:  DR1:  DR2: 

  [   11.526221] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   11.527636] PKRU: 5554
  [   11.528820] Call Trace:
  [   11.529807]  acpi_ps_parse_loop+0x587/0x660
  [   11.531198]  acpi_ps_parse_aml+0x1af/0x552
  [   11.532595]  acpi_ps_execute_method+0x208/0x2ca
  [   11.533972]  acpi_ns_evaluate+0x34e/0x4f0
  [   11.535361]  acpi_evaluate_object+0x18e/0x3b4
  [   11.536736]  acpi_evaluate_dsm+0xb3/0x120
  [   11.537943]  ? acpi_evaluate_dsm+0xb3/0x120
  [   11.539214]  nfit_intel_shutdown_status+0xed/0x1b0 [nfit]
  [   11.540603]  acpi_nfit_add_dimm+0x3cb/0x670 [nfit]
  [   11.541990]  acpi_nfit_register_dimms+0x141/0x460 [nfit]
  [   11.543377]  acpi_nfit_init+0x54f/0x620 [nfit]
  [   11.544755]  acpi_nfit_add+0x192/0x1f0 [nfit]
  [   11.546116]  acpi_device_probe+0x49/0x170
  [   11.547431]  really_probe+0x245/0x4c0
  [   11.548749]  driver_probe_device+0xf0/0x160
  [   11.550064]  device_driver_attach+0xab/0xb0
  [   11.551387]  __driver_attach+0xb2/0x140
  [   11.552692]  ? device_driver_attach+0xb0/0xb0
  [   11.554001]  bus_for_each_dev+0x7e/0xc0
  [   11.555326]  driver_attach+0x1e/0x20
  [   11.556630]  bus_add_driver+0x135/0x1f0
  [   11.557917]  driver_register+0x95/0xf0
  [   11.559226]  acpi_bus_register_driver+0x39/0x50
  [   11.560139]  nfit_init+0x168/0x1000 [nfit]
  [   11.561230]  ? 0xc0649000
  [   11.562442]  do_one_initcall+0x46/0x1d0
  [   11.563701]  ? kmem_cache_alloc_trace+0x11c/0x240
  [   11.564846]  do_init_module+0x62/0x290
  [   11.565768]  load_module+0xaa6/0xb40
  [   11.566811]  __do_sys_finit_module+0xc2/0x120
  [   11.567825]  __x64_sys_finit_module+0x18/0x20
  [   11.568747]  do_syscall_64+0x61/0xb0
  [   11.569694]  ? syscall_exit_to_user_mode+0x27/0x50
  [   11.570680]  ? __x64_sys_mmap+0x33/0x40
  [   11.571606]  ? do_syscall_64+0x6e/0xb0
  [   11.572442]  ? asm_exc_page_fault+0x8/0x30
  [   11.573395]  entry_SYSCALL_64_after_hwframe+0x44/0xae
  [   11.574392] RIP: 0033:0x7f7fb45d670d
  [   11.575373] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d f3 66 0f 00 f7 d8 64 89 01 48
  [   11.577496] RSP: 002b:7ffe815a56d8 EFLAGS: 0246 ORIG_RAX: 
0139
  [   11.578573] RAX: ffda RBX: 5624b212e410 RCX: 
7f7fb45d670d
  [   11.579646] RDX:  RSI: 7f7fb47683fe RDI: 

[Kernel-packages] [Bug 1956982] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.4 for Ubuntu 22.04

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1006.8~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1956982

Title:
  Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.4 for Ubuntu 22.04

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Please integrate this customer critical/reported fix that was submitted as a 
stand along patch:
  Accepted 11/29/21:

  Applied to 5.16/scsi-fixes, thanks!

  [1/1] lpfc: Fix nonrecovery of remote ports following an unsolicited LOGO
https://git.kernel.org/mkp/scsi/c/0956ba63bd94

  As well as this latest set of bug fix patches accepted upstream
  12/6/2021:

  scsi: lpfc: Fix leaked lpfc_dmabuf mbox allocations with NPIV
commitf0d3919697492950f57a26a1093aee53880d669d
  scsi: lpfc: Change return code on I/Os received during link bounce
commit2e81b1a374da5d6024208c16c4a5224a70cafa64
  scsi: lpfc: Fix lpfc_force_rscn ndlp kref imbalance
commit7576d48c64f36f6fea9df2882f710a474fa35f40
  scsi: lpfc: Fix NPIV port deletion crash
commit8ed190a91950564775cbaae9e8e8083a69a8da23
  scsi: lpfc: Trigger SLI4 firmware dump before doing driver cleanup
commit7dd2e2a923173d637c272e483966be8e96a72b64
  scsi: lpfc: Adjust CMF total bytes and rxmonitor
commita6269f837045acb02904f31f05acde847ec8f8a7
  scsi: lpfc: Cap CMF read bytes to MBPI
commit05116ef9c4b444f7fdbb56f9e13c2ec941726639
  scsi: lpfc: Add additional debugfs support for CMF
commit6014a2468f0e49194f612b1f09f99eacee0a409a
  scsi: lpfc: Update lpfc version to 14.0.0.4
commit4437503bfbec2f02b41b2492520fe627715889a7


  Extended log info:

-cover-letter.patch

0001-lpfc-Fix-leaked-lpfc_dmabuf-mbox-allocations-with-np.patch
 commitf0d3919697492950f57a26a1093aee53880d669d
 lpfc: Fix memory leaked lpfc_dmabuf mbox allocations
 Fix leaked lpfc_dmabuf allocations in an mbox.
   svn: r82112
bz: 249968 250131

0002-lpfc-Change-return-code-on-ios-received-during-link-.patch
 commit2e81b1a374da5d6024208c16c4a5224a70cafa64
 lpfc: Group RPI_SUSPENDED error action with DID_REQUEUE
 Fix Medusa IO errors on Scope and Scale LIP test
   svn: r82348
bz: 247164 250466
 Fix Medusa IO errors on Scope and Scale LIP test - build
   svn: r82377
bz: 247164 250466

0003-lpfc-Fix-lpfc_force_rscn-ndlp-kref-imbalance.patch
 commit7576d48c64f36f6fea9df2882f710a474fa35f40
 lpfc: Fix lpfc_force_rscn ndlp kref imbalance
 Fix ndlp kref crash during lpfc_force_rscn
   svn: r82526
bz: 250692 250695

0004-lpfc-Fix-NPIV-port-deletion-crash.patch
 commit8ed190a91950564775cbaae9e8e8083a69a8da23
 lpfc: Fix NPIV port deletion crash
 Fix crash when deleting a large number of vports.
   svn: r82120
bz: 240671 250158
 Fix a log message formatting error introduced in svn r82120.
   svn: r82743
bz: 249968 250131

0005-lpfc-Trigger-SLI4-firmware-dump-before-doing-driver-.patch
 commit7dd2e2a923173d637c272e483966be8e96a72b64
 lpfc: Trigger SLI4 firmware dump immediately without delays
 Trigger SLI4 firmware dump immediately without delays
   svn: r82770
bz: 250111 251061

0006-lpfc-Adjust-CMF-total-bytes-and-rxmonitor.patch
 commita6269f837045acb02904f31f05acde847ec8f8a7
 lpfc: Adjust CMF total bytes and rxmonitor
 Adjust CMF total bytes and add to rxmonitor
   svn: r82429
bz: 250581 250587

0007-lpfc-Cap-CMF-read-bytes-to-MBPI.patch
 commit05116ef9c4b444f7fdbb56f9e13c2ec941726639
 lpfc: Cap CMF read bytes to MBPI
 Cap CMF read bytes to MBPI only for shortened timer intervals
   svn: r82483
bz: 250605 251274

0008-lpfc-Add-additional-debugfs-support-for-CMF.patch
 commit6014a2468f0e49194f612b1f09f99eacee0a409a
 lpfc: Add additional debugfs support for CMF
 Add debugfs support for CMF parameters
   svn: r82144
bz: 250206 250237
 Coverity: CID 19805 Fix memory illegal access
   svn: r82349
bz: 250454 250465

0009-lpfc-Update-lpfc-version-to-14.0.0.4.patch
  commit4437503bfbec2f02b41b2492520fe627715889a7

To manage notifications about this bug 

[Kernel-packages] [Bug 1948038] Re: disable CONFIG_KFENCE_STATIC_KEYS in linux 5.15

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1006.8~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1948038

Title:
  disable CONFIG_KFENCE_STATIC_KEYS in linux 5.15

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

Bug description:
  [Impact]

  KFENCE devs are changing CONFIG_KFENCE_STATIC_KEYS to be disabled by
  default, because it's introducing more problems than benefits:

  https://lore.kernel.org/all/20211019102524.2807208-2-el...@google.com/T/#u

  This also seems to trigger QEMU bugs during the systemd autopkgtest, like:
  https://bugs.launchpad.net/qemu/+bug/1920934

  [Test case]

  Run systemd autopkgtest.

  [Fix]

  Disable CONFIG_KFENCE_STATIC_KEYS.

  [Regression potential]

  We may experience an overall performance regression for not using
  static branches in the KFENCE code.

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


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

[Kernel-packages] [Bug 1956780] Re: 5.15 stuck at boot on c4.large

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1006.8~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1956780

Title:
  5.15 stuck at boot on c4.large

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

  c4.large instances are stuck at boot with kernel 5.15.0-15.15.

  [Test case]

  Simply deploy a c4.large instance and install the latest jammy kernel
  (5.15.0-15.15).

  [Fix]

  It looks like the offending commit is the following:

   02c70033b98b ("PCI/MSI: Mask MSI-X vectors only on success")

  Reverting the commit fixes the problem.

  [Regression potential]

  It looks like the commit was fixing a potential breakage with broken
  Marvell NVME devices, so we may see crashes in presence of these
  devices. However, reverting the commit we are simply restoring the
  previous behavior, so potential regressions should be limited to these
  broken devices.

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


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

[Kernel-packages] [Bug 1933179] Re: [22.04 FEAT] KVM: Enable storage key checking for intercepted instruction handled by userspace

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1006.8~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1933179

Title:
  [22.04 FEAT] KVM: Enable storage key checking for intercepted
  instruction handled by userspace

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

Bug description:
  KVM uses lazy storage key enablement as Linux does no longer make use of the 
storage keys. When the guest enters keyed mode, then KVM will save/restore the 
key during paging, provide change/reference tracking for guest and host and for 
all interpreted instructions will do key protection.
  If an instruction is intercepted and passed along to userspace (like QEMU) no 
storage key protection is checked, though. This is in violation of the 
architecture and it can result in misbehaving guests that rely on key 
protection for all instructions.
  This item will improve the MEMOP ioctl to also add key checking. In case of a 
key protection the right fault is injected in the guest.

  Value: Interoperability

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


-- 
Mailing list: https://launchpad.net/~kernel-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-azure/5.15.0.1008.9)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-azure (5.15.0.1008.9) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

digimend-dkms/10-4 (arm64)
snapd/2.55.3+22.04ubuntu1 (amd64)
oss4/4.2-build2010-5ubuntu9 (amd64)


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/jammy/update_excuses.html#linux-meta-azure

[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 1947557] Re: kernel panic: NULL pointer dereference in wb_timer_f()

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1006.8~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1947557

Title:
  kernel panic: NULL pointer dereference in wb_timer_f()

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Impish:
  Confirmed

Bug description:
  [Impact]

  It is possible to trigger a kernel panic with the latest impish kernel
  running systemd autopkgtest using --enable-kvm with the test instances
  created by systemd during the autotest. The panic happens in the host,
  not in the guest VM executed by systemd.

  [Test case]

  Add --enable-kvm to the options in test/testdata/test-functions
  (systemd), run `sudo autopkgtest . -- null`, wait for the panic to
  happen.

  [Fix]

  https://lore.kernel.org/lkml/YW6N2qXpBU3oc50q@arighi-desktop/T/#u

  [Regression potential]

  The fix is addressing a race in the block layer (in the buffered write
  throttling code - block/blk-wbt.c) between a disk being released and
  the timer callback that periodically checks if the latency for a
  specific block device has been exceeded. If the fix is not correct we
  may still have a race in this code, that can still show potential
  kernel panics in the block layer subsystem.

  [Original bug report]

  I can trigger the following kernel panic with the latest impish kernel
  5.13.0-19-generic, running systemd autopkgtest using --enable-kvm for
  the instances created by systemd to run the autotest:

  [  119.987108] BUG: kernel NULL pointer dereference, address: 0098
  [  119.987617] #PF: supervisor read access in kernel mode
  [  119.987971] #PF: error_code(0x) - not-present page
  [  119.988325] PGD 7c4a4067 P4D 7c4a4067 PUD 7bf63067 PMD 0
  [  119.988697] Oops:  [#1] SMP NOPTI
  [  119.988959] CPU: 1 PID: 9353 Comm: cloud-init Not tainted 
5.15-rc5+arighi-aws #rc5+arighi
  [  119.989520] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 
1.14.0-2 04/01/2014
  [  119.990055] RIP: 0010:wb_timer_fn+0x44/0x3c0
  [  119.990376] Code: 41 8b 9c 24 98 00 00 00 41 8b 94 24 b8 00 00 00 41 8b 84 
24 d8 00 00 00 4d 8b 74 24 28 01 d3 01 c3 49 8b 44 24 60 48 8b 40 78 <4c> 8b b8 
98 00 00 00 4d 85 f6 0f 84 c4 00 00 00 49 83 7c 24 30 00
  [  119.991578] RSP: :b5f580957da8 EFLAGS: 00010246
  [  119.991937] RAX:  RBX:  RCX: 
0004
  [  119.992412] RDX:  RSI:  RDI: 
88f476d7f780
  [  119.992895] RBP: b5f580957dd0 R08:  R09: 

  [  119.993371] R10: 0004 R11: 0002 R12: 
88f476c84500
  [  119.993847] R13: 88f4434390c0 R14:  R15: 
88f4bdc98c00
  [  119.994323] FS:  7fb90bcd9c00() GS:88f4bdc8() 
knlGS:
  [  119.994952] CS:  0010 DS:  ES:  CR0: 80050033
  [  119.995380] CR2: 0098 CR3: 7c0d6000 CR4: 
06e0
  [  119.995906] Call Trace:
  [  119.996130]  ? blk_stat_free_callback_rcu+0x30/0x30
  [  119.996505]  blk_stat_timer_fn+0x138/0x140
  [  119.996830]  call_timer_fn+0x2b/0x100
  [  119.997136]  __run_timers.part.0+0x1d1/0x240
  [  119.997470]  ? kvm_clock_get_cycles+0x11/0x20
  [  119.997826]  ? ktime_get+0x3e/0xa0
  [  119.998110]  ? native_apic_msr_write+0x2c/0x30
  [  119.998456]  ? lapic_next_event+0x20/0x30
  [  119.998779]  ? clockevents_program_event+0x94/0xf0
  [  119.999150]  run_timer_softirq+0x2a/0x50
  [  119.999465]  __do_softirq+0xcb/0x26f
  [  119.999764]  irq_exit_rcu+0x8c/0xb0
  [  120.57]  sysvec_apic_timer_interrupt+0x43/0x90
  [  120.000429]  ? asm_sysvec_apic_timer_interrupt+0xa/0x20
  [  120.000836]  asm_sysvec_apic_timer_interrupt+0x12/0x20
  [  120.001226] RIP: 0033:0x501969
  [  120.001486] Code: 8d 54 e5 00 4d 8b a2 80 02 00 00 4d 89 ba 88 02 00 00 4d 
39 f4 75 0f e9 84 00 00 00 0f 1f 44 00 00 4c 39 f2 74 7a 49 8b 14 24 <4d> 89 e7 
49 89 d4 49 81 7f 18 e0 33 8f 00 75 e7 48 85 d2 74 e7 49
  [  120.002793] RSP: 002b:7ffc407d68b0 EFLAGS: 0206
  [  120.003196] RAX: 008eaa20 RBX: 7ffc407d6930 RCX: 

  [  120.003711] RDX: 00d2d940 RSI: 7fb90b9522c0 RDI: 
0001
  [  120.004224] RBP: 7ffc407d6940 R08: 

[Kernel-packages] [Bug 1959610] Re: ubuntu_kernel_selftests / ftrace:ftracetest do_softirq failure on Jammy realtime

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1006.8~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1959610

Title:
  ubuntu_kernel_selftests / ftrace:ftracetest do_softirq failure on
  Jammy realtime

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  * ubuntu_kernel_selftests / ftrace:ftracetest fails on realtime
  kernel.

  * ftrace:ftracetest which reports: "echo: I/O error". This is caused
  by using "do_softirq" in test which does not exist on preempt RT
  kernel.

  [Fix]

  * Use other function.
  * Upstream commit 6fec1ab67f8d ("selftests/ftrace: Do not trace do_softirq 
because of PREEMPT_RT")

  [Test Plan]

  * Run the test on regular (base) and realtime kernel.

  [Where problems could occur]

  * Only ftracetest tests.

  [Other info]

  Failure is reported for step 32 in Jenkins job:

  23:48:45 DEBUG| [stdout] # selftests: ftrace: ftracetest
  23:48:45 DEBUG| [stdout] # === Ftrace unit tests ===
  23:48:45 DEBUG| [stdout] # [1] Basic trace file check [PASS]
  23:48:49 DEBUG| [stdout] # [2] Basic test for tracers [PASS]
  23:48:49 DEBUG| [stdout] # [3] Basic trace clock test [PASS]
  23:48:49 DEBUG| [stdout] # [4] Basic event tracing check  [PASS]
  23:48:50 DEBUG| [stdout] # [5] Change the ringbuffer size [PASS]
  23:48:50 DEBUG| [stdout] # [6] Snapshot and tracing setting   [PASS]
  23:48:50 DEBUG| [stdout] # [7] trace_pipe and trace_marker[PASS]
  23:49:38 DEBUG| [stdout] # [8] Test ftrace direct functions against tracers   
[PASS]
  23:49:57 DEBUG| [stdout] # [9] Test ftrace direct functions against kprobes   
[PASS]
  23:49:57 DEBUG| [stdout] # [10] Generic dynamic event - add/remove eprobe 
events  [PASS]
  23:49:57 DEBUG| [stdout] # [11] Generic dynamic event - add/remove kprobe 
events  [PASS]
  23:49:57 DEBUG| [stdout] # [12] Generic dynamic event - add/remove synthetic 
events   [PASS]
  23:49:57 DEBUG| [stdout] # [13] Generic dynamic event - selective clear 
(compatibility)   [PASS]
  23:49:58 DEBUG| [stdout] # [14] Generic dynamic event - generic clear event   
[PASS]
  23:49:58 DEBUG| [stdout] # [15] Generic dynamic event - check if duplicate 
events are caught  [PASS]
  23:49:58 DEBUG| [stdout] # [16] event tracing - enable/disable with event 
level files [PASS]
  23:49:58 DEBUG| [stdout] # [17] event tracing - restricts events based on pid 
notrace filtering   [PASS]
  23:49:59 DEBUG| [stdout] # [18] event tracing - restricts events based on pid 
[PASS]
  23:49:59 DEBUG| [stdout] # [19] event tracing - enable/disable with subsystem 
level files [PASS]
  23:50:00 DEBUG| [stdout] # [20] event tracing - enable/disable with top level 
files   [PASS]
  23:50:01 DEBUG| [stdout] # [21] Test trace_printk from module [PASS]
  23:50:04 DEBUG| [stdout] # [22] ftrace - function graph filters with stack 
tracer [PASS]
  23:50:05 DEBUG| [stdout] # [23] ftrace - function graph filters   [PASS]
  23:50:06 DEBUG| [stdout] # [24] ftrace - function pid notrace filters [PASS]
  23:50:06 DEBUG| [stdout] # [25] ftrace - function pid filters [PASS]
  23:50:08 DEBUG| [stdout] # [26] ftrace - stacktrace filter command[PASS]
  23:50:08 DEBUG| [stdout] # [27] ftrace - function trace with cpumask  [PASS]
  23:50:12 DEBUG| [stdout] # [28] ftrace - test for function event triggers 
[PASS]
  23:50:13 DEBUG| [stdout] # [29] ftrace - function trace on module [PASS]
  23:50:16 DEBUG| [stdout] # [30] ftrace - function profiling   [PASS]
  23:50:21 DEBUG| [stdout] # [31] ftrace - function profiler with function 
tracing  [PASS]
  23:50:22 DEBUG| [stdout] # [32] ftrace - test reading of set_ftrace_filter
[FAIL]
  23:50:24 DEBUG| [stdout] # [33] ftrace - test for function traceon/off 
triggers   [PASS]
  23:50:24 DEBUG| [stdout] # [34] ftrace - test tracing error log support   
[PASS]
  23:50:28 DEBUG| [stdout] # [35] Test creation and deletion of trace instances 
while setting an event  [PASS]
  23:50:29 DEBUG| [stdout] # [36] Test creation and deletion of trace instances 
[PASS]
  23:50:30 DEBUG| [stdout] # [37] Kprobe dynamic event - adding and removing
[PASS]
  23:50:30 DEBUG| [stdout] # [38] 

[Kernel-packages] [Bug 1853152] Re: [22.04 FEAT] In-kernel crypto: SIMD implementation of chacha20

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1006.8~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1853152

Title:
  [22.04 FEAT] In-kernel crypto: SIMD implementation of chacha20

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

Bug description:
  Recent kernel releases provide support for the chacha20 cipher and among 
others use it to compute pseudo random numbers for /dev/urandom.
  Chacha20 is a type of algorithm that can be accelerated using SIMD 
instructions. The goal of this item is to use z System SIMD instruction to 
implement chacha20.

  Will be made available earliest for kernel >=5.6. Mean, request for
  integration if backport is possible for 20.04

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


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

[Kernel-packages] [Bug 1953192] Re: Enable Landlock by default

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1006.8~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1953192

Title:
  Enable Landlock by default

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  The Landlock security feature is built in Ubuntu kernel since 5.13
  which is great!  However, it is not enough to enable the
  CONFIG_SECURITY_LANDLOCK option as described in the related help. The
  CONFIG_LSM option needs to be prepended by "landlock," to make
  Landlock system calls available without modifying the kernel boot
  arguments.

  Could you please update the CONFIG_LSM variable accordingly?

  Regards,
   Mickaël

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


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

[Kernel-packages] [Bug 1951440] Re: Enable CONFIG_INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON on jammy 5.15

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1006.8~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1951440

Title:
  Enable CONFIG_INTEL_IOMMU_DEFAULT_ON and
  CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON on jammy 5.15

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

Bug description:
  Starting with the following commit, upstream kernel is enabling Intel
  IOMMU related options by default:

   792fb43ce2c9 ("iommu/vt-d: Enable Intel IOMMU scalable mode by
  default")

  We should follow upstream direction enabling
  CONFIG_INTEL_IOMMU_DEFAULT_ON and
  CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON.

  A downside is that this change may introduce boot regressions on old
  systems (especially those with buggy firmware).

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


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

[Kernel-packages] [Bug 1959977] Re: [22.04 FEAT] KVM: Enable GISA support for Secure Execution guests

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1006.8~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1959977

Title:
  [22.04 FEAT] KVM: Enable GISA support for Secure Execution guests

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

Bug description:
  KVM: Enable GISA support for Secure Execution guests

  Description:
  The initial Secure Execution support doesn't contain guest interrupt support 
via GISA. Consequently the GISA support is fenced by QEMU for guests running in 
Secure Execution mode. For crypto passthrough support it is necessary to allow 
interrupts to be injected for better performance.

  Category: kernel
  Request Type: Kernel - Enhancement from IBM
  Upstream Acceptance: In Progress

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


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

[Kernel-packages] [Bug 1958004] Re: intel_iommu breaks Intel IPU6 camera: isys port open ready failed -16

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1006.8~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' 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-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1958004

Title:
  intel_iommu breaks Intel IPU6 camera: isys port open ready failed -16

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

Bug description:
  [SRU Justfication]

  
  [Impact]

  Intel iommu was turned on by default in mainline build v5.15.5 or jammy
  -generic kernel 5.15.0-12.12. This would breaks IPU6.

  [ 6.681241] intel-ipu6 intel-ipu: IPU driver version 1.0
  [ 7.056166] DMAR: DRHD: handling fault status reg 2
  [ 7.056169] DMAR: [DMA Read NO_PASID] Request device [00:05.0] fault
  addr 0x11b1d4000 [fault reason 0x06] PTE Read access is not set
  [ 7.056421] DMAR: DRHD: handling fault status reg 2
  [ 7.056422] DMAR: [DMA Read NO_PASID] Request device [00:05.0] fault
  addr 0x3fff000 [fault reason 0x06] PTE Read access is not set
  [ 7.056456] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8
  [ 7.056637] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0
  [ 7.056652] DMAR: DRHD: handling fault status reg 2
  [ 7.056653] DMAR: [DMA Read NO_PASID] Request device [00:05.0] fault
  addr 0x3fff000 [fault reason 0x06] PTE Read access is not set
  [ 7.056882] DMAR: DRHD: handling fault status reg 2
  [ 8.197149] intel-ipu6-isys intel-ipu6-isys0: isys port open ready
  failed -16
  [ 8.197157] intel-ipu6-isys intel-ipu6-isys0: Device close failure: -16
  [ 10.201677] intel-ipu6-isys intel-ipu6-isys0: Device release time out
  -16
  [ 10.240523] intel-ipu6-isys intel-ipu6-isys0: Clearing old context

  [Fix]

  Use IOMMU passthrough mode for IPU6 as it has its own iommu hardware.

  [Test Case]

  Apply the fix and kernel should print a new info line:

Passthrough IOMMU for integrated Intel IPU

  and IPU6 camera should continue to work without intel_iommu=off
  work-around.

  [Where problems could occur]

  No. That's what it should have been done.

  [Other Info]

  This only affects kernel >= 5.15, so only Jammy is nominated.

  Intel IPU6 driver has been proposed for Jammy for hwe-5.15 migration in
  bug 1955383
  (https://lists.ubuntu.com/archives/kernel-team/2021-December/126749.html).
  The port for 5.17 unstable would be filed soon. Still under discussion.

  While there is no plan for Intel to upstream Intel IPU6 driver before
  kernel camera API is out, these extra prerequisite patches will only be
  staged in a separate patches folder in the upstream repository.

  == original bug description ==

  Intel iommu was turned on by default in mainline build v5.15.5 or
  jammy -generic kernel 5.15.0-12.12. This would breaks IPU6 leaving
  error messages:

  [6.681241] intel-ipu6 intel-ipu: IPU driver version 1.0
  [7.056166] DMAR: DRHD: handling fault status reg 2
  [7.056169] DMAR: [DMA Read NO_PASID] Request device [00:05.0] fault addr 
0x11b1d4000 [fault reason 0x06] PTE Read access is not set
  [7.056421] DMAR: DRHD: handling fault status reg 2
  [7.056422] DMAR: [DMA Read NO_PASID] Request device [00:05.0] fault addr 
0x3fff000 [fault reason 0x06] PTE Read access is not set
  [7.056456] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8
  [7.056637] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0
  [7.056652] DMAR: DRHD: handling fault status reg 2
  [7.056653] DMAR: [DMA Read NO_PASID] Request device [00:05.0] fault addr 
0x3fff000 [fault reason 0x06] PTE Read access is not set
  [7.056882] DMAR: DRHD: handling fault status reg 2
  [8.197149] intel-ipu6-isys intel-ipu6-isys0: isys port open ready failed 
-16
  [8.197157] intel-ipu6-isys intel-ipu6-isys0: Device close failure: -16
  [   10.201677] intel-ipu6-isys intel-ipu6-isys0: Device release time out -16
  [   10.240523] intel-ipu6-isys intel-ipu6-isys0: Clearing old context
  ...

  This can be worked-around with intel_iommu=off.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
 

[Kernel-packages] [Bug 1959890] Re: [22.04 FEAT] Deactivitate CONFIG_QETH_OSX kernel config option

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1006.8~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1959890

Title:
  [22.04 FEAT] Deactivitate  CONFIG_QETH_OSX kernel config option

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

Bug description:
  Deactivitate CONFIG_QETH_OSX by dropping this kernel config option

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


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

[Kernel-packages] [Bug 1959735] Re: [22.04 FEAT] KVM: Improve SIGP architectural compliance

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1006.8~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1959735

Title:
  [22.04 FEAT] KVM: Improve SIGP architectural compliance

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

Bug description:
  Linux as a guest operating system often doesn't have as stringent
  requirements to architectural compliance as traditional operating
  systems that rely on it. Specifically, KVM implements the SIGP RESTART
  in a non-compliant way, as it reports a CPU state to be stopped after
  SIGP RESTART was issued, while it should report a busy condition until
  the CPU is really started. This feature covers the necessary
  fixes/improvements to KVM SIGP processing.

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


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

[Kernel-packages] [Bug 1960361] Re: hwmon: k10temp updates for AMD Genoa in 22.04

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1006.8~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1960361

Title:
  hwmon: k10temp updates for AMD Genoa in 22.04

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

Bug description:
  Patch pull request to include additional support for AMD Genoa in
  22.04

  f707bcb5d1cb 5.17 hwmon: (k10temp) Remove unused definitions
  3cf90efa1367 5.17 hwmon: (k10temp) Add support for AMD Family 19h Models 
10h-1Fh and A0h-AFh
  8bb050cd5cf4 5.17 hwmon: (k10temp) Support up to 12 CCDs on AMD Family of 
processors

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


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

[Kernel-packages] [Bug 1960298] Re: Forward-port drm/i915 commits from oem-5.14 for Alder Lake S & P

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1006.8~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1960298

Title:
  Forward-port drm/i915 commits from oem-5.14 for Alder Lake S & P

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Hi

  These commits add the missing commits from oem-5.14 to fix known issues for 
Alder Lake (ADL) S & P.
  The final patch enables loading i915 on them without require_force_probe 
option.

  The original bug reports are:

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929027
  https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1940504
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954728
  https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945438

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


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

[Kernel-packages] [Bug 1960362] Re: EDAC update for AMD Genoa support in 22.04

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1006.8~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1960362

Title:
  EDAC update for AMD Genoa support in 22.04

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

Bug description:
  EDAC updates for AMD Genoa support for 22.04 as requested by AMD

  f957112423905.17EDAC: Add RDDR5 and LRDDR5 memory types
  e2be5955a8865.17EDAC/amd64: Add support for AMD Family 19h Models 
10h-1Fh and A0h-AFh

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


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

[Kernel-packages] [Bug 1960580] Re: [22.04 FEAT] [KRN1918] Long kernel command line on s390x

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1006.8~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1960580

Title:
  [22.04 FEAT] [KRN1918] Long kernel command line on s390x

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

Bug description:
  Feature: Long kernel command line

  Description:
  Allow to handle command lines with a length of up to 4096 bytes by kernel. It 
happened in the past that our supported command line size of 896 bytes was 
sometimes too short - while x86, powerpc, and arm each support 2048 bytes.

  This requires:
  - an ABI interface to the kernel image, so that tools can figure out if the 
kernel supports large command lines (might be a feature bitmap at a fixed 
location)
  - zipl, genprotimg, qemu, kexec-tools and  changes (depending on the kernel 
side implementation)
  - in-kernel ipl support changes (IPL from reader)

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


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

[Kernel-packages] [Bug 1960771] Re: Use EC GPE for s2idle wakeup on AMD platforms

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1006.8~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' 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-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1960771

Title:
  Use EC GPE for s2idle wakeup on AMD platforms

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

Bug description:
  [Impact]
  Opening lid doesn't wakeup some AMD platforms from s2idle.

  [Fix]
  Use EC GPE for lid events to wakeup the laptops.

  [Test]
  Close and only the lid. The affected laptop now can be woken up by lid.

  [Where problems could occur]
  The original issue was later fixed by "pinctrl: amd: Fix wakeups when
  IRQ is shared with SCI". However, EC GPE is prone to cause spurious
  wakeup, so we still need to keep an eye on the regression reports.

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


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

[Kernel-packages] [Bug 1962185] Re: Add ConnectX7 support and bug fixes to Jammy

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1006.8~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1962185

Title:
  Add ConnectX7 support and bug fixes  to Jammy

Status in linux package in Ubuntu:
  Fix Released
Status in rdma-core package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  Add support for NDR (next data rate) in IB MAD.
  This speed is supported From ConnectX7 onwards.
  And in addition user space support for NDR was extended.

  [Test Case]
  TBD

  [Regression Potential]
  TBD

  [Other Info]

  Feature patchset: (kernel v5.17-rc1)
  fbdb0ba7051e IB/mlx5: Expose NDR speed through MAD

  userspace (upstream rdma-core v39):
  eb7a7fb3 ibdiags: Extend support of NDR rates
  f6c49e79 verbs: Extend support of NDR rates
  49c2d6e7 pyverbs: Extend support of NDR rates

  This list might not be full as i haven't ported the patches to Jammy
  yet.

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


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

[Kernel-packages] [Bug 1976135] [NEW] Jammy update: v5.15.37 upstream stable release

[Kamal Mostafa]

Public bug reported:

SRU Justification

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

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

floppy: disable FDRAWCMD by default
UBUNTU: [Config] updateconfigs for BLK_DEV_FD_RAWCMD
bpf: Introduce composable reg, ret and arg types.
bpf: Replace ARG_XXX_OR_NULL with ARG_XXX | PTR_MAYBE_NULL
bpf: Replace RET_XXX_OR_NULL with RET_XXX | PTR_MAYBE_NULL
bpf: Replace PTR_TO_XXX_OR_NULL with PTR_TO_XXX | PTR_MAYBE_NULL
bpf: Introduce MEM_RDONLY flag
bpf: Convert PTR_TO_MEM_OR_NULL to composable types.
bpf: Make per_cpu_ptr return rdonly PTR_TO_MEM.
bpf: Add MEM_RDONLY for helper args that are pointers to rdonly mem.
bpf/selftests: Test PTR_TO_RDONLY_MEM
bpf: Fix crash due to out of bounds access into reg2btf_ids.
spi: cadence-quadspi: fix write completion support
ARM: dts: socfpga: change qspi to "intel,socfpga-qspi"
mm: kfence: fix objcgs vector allocation
gup: Turn fault_in_pages_{readable,writeable} into fault_in_{readable,writeable}
iov_iter: Turn iov_iter_fault_in_readable into fault_in_iov_iter_readable
iov_iter: Introduce fault_in_iov_iter_writeable
gfs2: Add wrapper for iomap_file_buffered_write
gfs2: Clean up function may_grant
gfs2: Introduce flag for glock holder auto-demotion
gfs2: Move the inode glock locking to gfs2_file_buffered_write
gfs2: Eliminate ip->i_gh
gfs2: Fix mmap + page fault deadlocks for buffered I/O
iomap: Fix iomap_dio_rw return value for user copies
iomap: Support partial direct I/O on user copy failures
iomap: Add done_before argument to iomap_dio_rw
gup: Introduce FOLL_NOFAULT flag to disable page faults
iov_iter: Introduce nofault flag to disable page faults
gfs2: Fix mmap + page fault deadlocks for direct I/O
btrfs: fix deadlock due to page faults during direct IO reads and writes
btrfs: fallback to blocking mode when doing async dio over multiple extents
mm: gup: make fault_in_safe_writeable() use fixup_user_fault()
selftests/bpf: Add test for reg2btf_ids out of bounds access
Linux 5.15.37
UBUNTU: upstream stable to v5.15.37

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

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


** Tags: kernel-stable-tracking-bug

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

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

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

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    v5.15.37 upstream stable release
+    from git://git.kernel.org/
  
-v5.15.37 upstream stable release
-from git://git.kernel.org/
+ floppy: disable FDRAWCMD by default
+ UBUNTU: [Config] updateconfigs for BLK_DEV_FD_RAWCMD
+ bpf: Introduce composable reg, ret and arg types.
+ bpf: Replace ARG_XXX_OR_NULL with ARG_XXX | PTR_MAYBE_NULL
+ bpf: Replace RET_XXX_OR_NULL with RET_XXX | PTR_MAYBE_NULL
+ bpf: Replace PTR_TO_XXX_OR_NULL with PTR_TO_XXX | PTR_MAYBE_NULL
+ bpf: Introduce MEM_RDONLY flag
+ bpf: Convert PTR_TO_MEM_OR_NULL to composable types.
+ bpf: Make per_cpu_ptr return rdonly PTR_TO_MEM.
+ bpf: Add MEM_RDONLY for helper args that are pointers to rdonly mem.
+ bpf/selftests: Test PTR_TO_RDONLY_MEM
+ bpf: Fix crash due to out of bounds access into reg2btf_ids.
+ spi: cadence-quadspi: fix write completion support
+ ARM: dts: socfpga: change qspi to "intel,socfpga-qspi"
+ mm: kfence: fix objcgs vector allocation
+ gup: Turn fault_in_pages_{readable,writeable} into 
fault_in_{readable,writeable}
+ iov_iter: Turn iov_iter_fault_in_readable into fault_in_iov_iter_readable
+ iov_iter: Introduce 

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oracle-5.13/5.13.0.1030.35~20.04.1)

[Ubuntu SRU Bot]

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

linux-oracle-5.13/5.13.0-1030.35~20.04.1 (amd64)


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-oracle-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 1976125] ProcEnviron.txt

[Sugihwaras]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1976125/+attachment/5593486/+files/ProcEnviron.txt

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

Title:
  The webcam image displayed has problems

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  i try open cheese webcam but image displayed has problems. i try
  another webcam app like Guvcview can display image normally

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  Uname: Linux 5.17.9-xanmod1 x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 28 03:16:15 2022
  InstallationDate: Installed on 2022-05-27 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220524)
  MachineType: Dell Inc. Inspiron 3442
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2020
  dmi.bios.release: 65.16
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0T57PC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A16
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/02/2020:br65.16:svnDellInc.:pnInspiron3442:pvrNotSpecified:rvnDellInc.:rn0T57PC:rvrA16:cvnDellInc.:ct8:cvrNotSpecified:sku0651:
  dmi.product.name: Inspiron 3442
  dmi.product.sku: 0651
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-27 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220524)
  NonfreeKernelModules: wl
  Package: linux (not installed)
  Tags:  jammy wayland-session
  Uname: Linux 5.17.9-xanmod1 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Kernel-packages] [Bug 1976125] Re: The webcam image displayed has problems

[Sugihwaras]

apport information

** Tags added: apport-collected

** Description changed:

  i try open cheese webcam but image displayed has problems. i try another
  webcam app like Guvcview can display image normally
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  Uname: Linux 5.17.9-xanmod1 x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 28 03:16:15 2022
  InstallationDate: Installed on 2022-05-27 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220524)
  MachineType: Dell Inc. Inspiron 3442
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2020
  dmi.bios.release: 65.16
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0T57PC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A16
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/02/2020:br65.16:svnDellInc.:pnInspiron3442:pvrNotSpecified:rvnDellInc.:rn0T57PC:rvrA16:cvnDellInc.:ct8:cvrNotSpecified:sku0651:
  dmi.product.name: Inspiron 3442
  dmi.product.sku: 0651
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.1
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2022-05-27 (0 days ago)
+ InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220524)
+ NonfreeKernelModules: wl
+ Package: linux (not installed)
+ Tags:  jammy wayland-session
+ Uname: Linux 5.17.9-xanmod1 x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  The webcam image displayed has problems

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  i try open cheese webcam but image displayed has problems. i try
  another webcam app like Guvcview can display image normally

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  Uname: Linux 5.17.9-xanmod1 x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 28 03:16:15 2022
  InstallationDate: Installed on 2022-05-27 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220524)
  MachineType: Dell Inc. Inspiron 3442
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2020
  dmi.bios.release: 65.16
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0T57PC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A16
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/02/2020:br65.16:svnDellInc.:pnInspiron3442:pvrNotSpecified:rvnDellInc.:rn0T57PC:rvrA16:cvnDellInc.:ct8:cvrNotSpecified:sku0651:
  dmi.product.name: Inspiron 3442
  dmi.product.sku: 0651
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-27 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220524)
  NonfreeKernelModules: wl
  Package: linux (not installed)
  Tags:  jammy wayland-session
  Uname: Linux 5.17.9-xanmod1 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Kernel-packages] [Bug 1971144] Re: Black screen after login when using CKLau-64HUA KVM switch

[Stapel]

This has now been fixed. After installing the latest updates, I tried
the setup with the KVM switch again, and it worked.

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

Title:
  Black screen after login when using CKLau-64HUA KVM switch

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

Bug description:
  After I log in from the login screen, I just get a black screen. To
  get a GUI, I then press "CTL+Alt+F4", to get a console login, and then
  do "sudo startx". I have tried both options from the bottom right
  corner for logging in.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  Date: Mon May  2 14:01:43 2022
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl/6.30.223.271+bdcom, 5.13.0-22-generic, x86_64: installed
   bcmwl/6.30.223.271+bdcom, 5.13.0-40-generic, x86_64: installed
   bcmwl/6.30.223.271+bdcom, 5.15.0-27-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller 
[106b:0141]
  InstallationDate: Installed on 2020-11-28 (520 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Apple Inc. Macmini7,1
  ProcEnviron:
   LANGUAGE=en_ZA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=278bd098-563c-4e88-85c7-d0dd2d492987 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-04-29 (3 days ago)
  dmi.bios.date: 09/16/2021
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 432.40.8.0.1
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-35C5E08120C7EEAF
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Macmini7,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-35C5E08120C7EEAF
  dmi.modalias: 
dmi:bvnAppleInc.:bvr432.40.8.0.1:bd09/16/2021:br0.1:svnAppleInc.:pnMacmini7,1:pvr1.0:rvnAppleInc.:rnMac-35C5E08120C7EEAF:rvrMacmini7,1:cvnAppleInc.:ct10:cvrMac-35C5E08120C7EEAF:skuSystemSKU#:
  dmi.product.family: Mac
  dmi.product.name: Macmini7,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

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

[Ubuntu Kernel Bot]

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

apport-collect 1976125

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

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

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

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

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

Title:
  The webcam image displayed has problems

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  i try open cheese webcam but image displayed has problems. i try
  another webcam app like Guvcview can display image normally

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  Uname: Linux 5.17.9-xanmod1 x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 28 03:16:15 2022
  InstallationDate: Installed on 2022-05-27 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220524)
  MachineType: Dell Inc. Inspiron 3442
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2020
  dmi.bios.release: 65.16
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0T57PC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A16
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/02/2020:br65.16:svnDellInc.:pnInspiron3442:pvrNotSpecified:rvnDellInc.:rn0T57PC:rvrA16:cvnDellInc.:ct8:cvrNotSpecified:sku0651:
  dmi.product.name: Inspiron 3442
  dmi.product.sku: 0651
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1976125] [NEW] The webcam image displayed has problems

[Sugihwaras]

Public bug reported:

i try open cheese webcam but image displayed has problems. i try another
webcam app like Guvcview can display image normally

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: cheese 41.1-1build1
Uname: Linux 5.17.9-xanmod1 x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat May 28 03:16:15 2022
InstallationDate: Installed on 2022-05-27 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220524)
MachineType: Dell Inc. Inspiron 3442
RelatedPackageVersions:
 cheese41.1-1build1
 cheese-common 41.1-1build1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/02/2020
dmi.bios.release: 65.16
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 0T57PC
dmi.board.vendor: Dell Inc.
dmi.board.version: A16
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/02/2020:br65.16:svnDellInc.:pnInspiron3442:pvrNotSpecified:rvnDellInc.:rn0T57PC:rvrA16:cvnDellInc.:ct8:cvrNotSpecified:sku0651:
dmi.product.name: Inspiron 3442
dmi.product.sku: 0651
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug gstreamer-error jammy wayland-session

** Attachment added: "display image like this"
   
https://bugs.launchpad.net/bugs/1976125/+attachment/5593477/+files/Screenshot%20from%202022-05-28%2003-18-04.png

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

Title:
  The webcam image displayed has problems

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  i try open cheese webcam but image displayed has problems. i try
  another webcam app like Guvcview can display image normally

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  Uname: Linux 5.17.9-xanmod1 x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 28 03:16:15 2022
  InstallationDate: Installed on 2022-05-27 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220524)
  MachineType: Dell Inc. Inspiron 3442
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2020
  dmi.bios.release: 65.16
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0T57PC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A16
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/02/2020:br65.16:svnDellInc.:pnInspiron3442:pvrNotSpecified:rvnDellInc.:rn0T57PC:rvrA16:cvnDellInc.:ct8:cvrNotSpecified:sku0651:
  dmi.product.name: Inspiron 3442
  dmi.product.sku: 0651
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1970468] Re: linux-azure: Patch Set for ARM64 Images 20.04 and 18.04

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-azure/5.4.0-1081.84
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-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1970468

Title:
  linux-azure: Patch Set for ARM64 Images 20.04 and 18.04

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

Bug description:
  SRU Justification

  [Impact]

  Microsoft has asked to have the following patches included in
  impish/linux-azure and focal/linux-azure:

  commit eaa03d34535872d29004cb5cf77dc9dec1ba9a25 Drivers: hv: vmbus: Replace 
smp_store_mb() with virt_store_mb()
  commit b3d6dd09ff00fdcf4f7c0cb54700ffd5dd343502 Drivers: hv: balloon: Support 
status report for larger page sizes
  commit be5802795cf8d0b881745fa9ba7790293b382280 Drivers: hv: balloon: Disable 
balloon and hot-add accordingly

  [Test Case]

  Microsoft tested

  [Where things could go wrong]

  Hyper-v ballooning could fail.

  [Other Info]

  SF: #00333989

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


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

[Kernel-packages] [Bug 1972662] Re: [Azure] PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-azure/5.4.0-1081.84
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-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1972662

Title:
  [Azure] PCI: hv: Do not set PCI_COMMAND_MEMORY to reduce VM boot time

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

Bug description:
  SRU Justification

  [Impact]

  A VM on Azure can have 14 GPUs, and each GPU may have a huge MMIO BAR,
  e.g. 128 GB. Currently the boot time of such a VM can be 4+ minutes, and
  most of the time is used by the host to unmap/map the vBAR from/to pBAR
  when the VM clears and sets the PCI_COMMAND_MEMORY bit: each unmap/map
  operation for a 128GB BAR needs about 1.8 seconds, and the pci-hyperv
  driver and the Linux PCI subsystem flip the PCI_COMMAND_MEMORY bit
  eight times (see pci_setup_device() -> pci_read_bases() and
  pci_std_update_resource()), increasing the boot time by 1.8 * 8 = 14.4
  seconds per GPU, i.e. 14.4 * 14 = 201.6 seconds in total.

  Fix the slowness by not turning on the PCI_COMMAND_MEMORY in pci-hyperv.c,
  so the bit stays in the off state before the PCI device driver calls
  pci_enable_device(): when the bit is off, pci_read_bases() and
  pci_std_update_resource() don't cause Hyper-V to unmap/map the vBARs.
  With this change, the boot time of such a VM is reduced by
  1.8 * (8-1) * 14 = 176.4 seconds.

  [Test Case]

  Microsoft tested

  [Where things could go wrong]

  PCI BAR setup could fail or be incorrect.

  [Other Info]

  SF: #00336342

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


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

[Kernel-packages] [Bug 1973758] Re: Azure: Mellanox VF NIC crashes when removed

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-azure/5.4.0-1081.84
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-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1973758

Title:
  Azure:  Mellanox VF NIC crashes when removed

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

Bug description:
  SRU Justification

  [Impact]

  The 5.4.0-1075-azure and newer kernels are broken in that the VM can
  easily panic when the Mellanox VF NIC is removed and added due to
  Azure host servicing events or the below manual "unbind/bind" test
  (here the GUID can be different in different VMs):

  for i in `seq 1 1000`;
  do
  cd /sys/bus/vmbus/drivers/hv_pci;
  echo abdc2107-402e-4704-8c88-c2b850696c3c > unbind;
  echo abdc2107-402e-4704-8c88-c2b850696c3c > bind;
  done

  A sample panic call-trace is:
  [ 107.359954] kernel BUG at 
/build/linux-azure-5.4-4I3kFs/linux-azure-5.4-5.4.0/mm/slub.c:4020!
  [ 107.363858] invalid opcode:  [#1] SMP NOPTI
  [ 107.365870] CPU: 0 PID: 334 Comm: kworker/0:2 Not tainted 5.4.0-1077-azure 
#80~18.04.1-Ubuntu
  [ 107.369589] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090008 12/07/2018
  [ 107.373811] Workqueue: events vmbus_onmessage_work
  [ 107.375909] RIP: 0010:kfree+0x1d2/0x240
  …
  [ 107.413789] Call Trace:
  [ 107.414867] kobject_uevent_env+0x1b5/0x7e0
  [ 107.416747] kobject_uevent+0xb/0x10
  [ 107.418327] device_release_driver_internal+0x191/0x1c0
  [ 107.420653] device_release_driver+0x12/0x20
  [ 107.422523] bus_remove_device+0xe1/0x150
  [ 107.424279] device_del+0x167/0x380
  [ 107.425824] device_unregister+0x1a/0x60
  [ 107.427536] vmbus_device_unregister+0x27/0x50
  [ 107.429528] vmbus_onoffer_rescind+0x1d0/0x1f0
  [ 107.431474] vmbus_onmessage+0x2c/0x70
  [ 107.433104] vmbus_onmessage_work+0x22/0x30
  [ 107.434919] process_one_work+0x209/0x400
  [ 107.436661] worker_thread+0x34/0x40

  It turns out there is a bug in https://git.launchpad.net/~canonical-
  kernel/ubuntu/+source/linux-
  azure/+git/bionic/commit/?id=16a3c750a78d8, which misses the second
  hunk of the upstream patch
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=877b911a5ba0.

  Please apply the below patch to fix the issue:

  --- a/drivers/pci/controller/pci-hyperv.c
  +++ b/drivers/pci/controller/pci-hyperv.c
  @@ -3653,7 +3653,7 @@ static int hv_pci_remove(struct hv_device *hdev)

  hv_put_dom_num(hbus->bridge->domain_nr);

  - free_page((unsigned long)hbus);
  + kfree(hbus);
  return ret;
   }

  BTW, please apply this patch as well (Note: this patch is not really required 
as it's only for error handling path, which is usually unlikely):
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=42c3d41832ef4fcf60aaa6f748de01ad99572adf

  [Test Case]

  Microsoft tested

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


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

[Kernel-packages] [Bug 1975717] Re: [Azure] WARNING: CPU: 0 PID: 499 at include/linux/dma-mapping.h:555 netvsc_probe+0x3c9/0x3e0

[Ubuntu Kernel Bot]

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

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

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

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

Title:
  [Azure] WARNING: CPU: 0 PID: 499 at include/linux/dma-mapping.h:555
  netvsc_probe+0x3c9/0x3e0

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

Bug description:
  SRU Justification

  [Impact]

  When I hot-add a NIC to a Ubuntu 20.04 VM (“5.13.0-1023-azure 
#27~20.04.1-Ubuntu”), I get the the below call-trace.
  Please include the March-2022 fix: “Drivers: hv: vmbus: Fix initialization of 
device object in vmbus_device_register()” 
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3a5469582c241abca22500f36a9cb8e9331969cf)

  BTW, this call-trace should be harmless to a non-CVM VM.

  [ 364.275105] hv_utils: Heartbeat IC version 3.0
  [ 364.275137] hv_utils: KVP IC version 4.0
  [ 364.275146] hv_utils: Shutdown IC version 3.2
  [ 364.275153] hv_utils: TimeSync IC version 4.0
  [ 365.281376] [ cut here ]
  [ 365.281380] WARNING: CPU: 0 PID: 499 at include/linux/dma-mapping.h:555 
netvsc_probe+0x3c9/0x3e0 [hv_netvsc]
  [ 365.281392] Modules linked in: udf crc_itu_t iptable_mangle iptable_filter 
iptable_raw xt_LOG nf_log_syslog bpfilter nls_iso8859_1 dm_multipath 
scsi_dh_rdac scsi_dh_emc scsi_dh_alua kvm_intel kvm joydev hid_generic 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd 
cryptd serio_raw hv_netvsc pata_acpi hyperv_keyboard hid_hyperv hv_utils 
hv_balloon hyperv_fb hid sch_fq_codel ipmi_devintf drm ipmi_msghandler msr 
i2c_core ip_tables x_tables autofs4
  [ 365.281422] CPU: 0 PID: 499 Comm: kworker/0:3 Not tainted 5.13.0-1023-azure 
#27~20.04.1-Ubuntu
  [ 365.281424] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090008 12/07/2018
  [ 365.281427] Workqueue: hv_pri_chan vmbus_add_channel_work
  [ 365.281434] RIP: 0010:netvsc_probe+0x3c9/0x3e0 [hv_netvsc]
  [ 365.281440] Code: 37 c0 4c 89 e6 48 c7 c7 98 f2 37 c0 e8 70 b1 c4 da e9 e9 
fc ff ff 49 c7 84 24 88 0b 00 00 00 00 00 00 41 bf f4 ff ff ff eb b0 <0f> 0b e9 
19 fe ff ff 41 bf f4 ff ff ff e9 51 ff ff ff 0f 1f 44 00
  [ 365.281442] RSP: 0018:99270075bbd0 EFLAGS: 00010246
  [ 365.281444] RAX:  RBX: 890840b21000 RCX: 
0002
  [ 365.281446] RDX: 0002 RSI:  RDI: 
0002
  [ 365.281447] RBP: 99270075bbf8 R08:  R09: 

  [ 365.281448] R10: 9c74e820 R11: 0394 R12: 
890844dc6000
  [ 365.281449] R13: 0002 R14: 301d0800ae28 R15: 
000f
  [ 365.281451] FS: () GS:8909f7c0() 
knlGS:
  [ 365.281453] CS: 0010 DS:  ES:  CR0: 80050033
  [ 365.281454] CR2: 5619b3504d38 CR3: 0001091f8005 CR4: 
003706f0
  [ 365.281459] Call Trace:
  [ 365.281461] 
  [ 365.281465] vmbus_probe+0x67/0x80
  [ 365.281468] really_probe+0x1dc/0x440
  [ 365.281472] driver_probe_device+0xf0/0x160
  [ 365.281476] __device_attach_driver+0x79/0xe0
  [ 365.281479] ? driver_allows_async_probing+0x50/0x50
  [ 365.281482] bus_for_each_drv+0x84/0xd0
  [ 365.281485] __device_attach+0xed/0x170
  [ 365.281488] device_initial_probe+0x13/0x20
  [ 365.281491] bus_probe_device+0x8f/0xa0
  [ 365.281494] device_add+0x3f4/0x8e0
  [ 365.281496] ? hrtimer_init+0x2b/0x70
  [ 365.281501] device_register+0x1b/0x20
  [ 365.281503] vmbus_device_register+0x5e/0xe0
  [ 365.281505] vmbus_add_channel_work+0x12d/0x190
  [ 365.281507] process_one_work+0x21a/0x3b0
  [ 365.281511] worker_thread+0x4d/0x3e0
  [ 365.281515] ? process_one_work+0x3b0/0x3b0
  [ 365.281517] kthread+0x12b/0x150
  [ 365.281521] ? set_kthread_struct+0x40/0x40
  [ 365.281523] ret_from_fork+0x22/0x30
  [ 365.281528] 
  [ 365.281529] ---[ end trace 80a393e06f0ee58d ]---
  [ 365.514764] hv_balloon: Max. dynamic memory size: 8192 MB
  [ 367.937000] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

  [Test Case]

  Microsoft tested

  [Where things could go wrong]

  CVM VNIC instances may not initialize correctly.

  [Other Info]

  SF: #00337569

To manage notifications about 

[Kernel-packages] [Bug 1975717] Re: [Azure] WARNING: CPU: 0 PID: 499 at include/linux/dma-mapping.h:555 netvsc_probe+0x3c9/0x3e0

[Ubuntu Kernel Bot]

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

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

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


** Tags added: verification-needed-jammy

** Tags added: verification-needed-impish

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

Title:
  [Azure] WARNING: CPU: 0 PID: 499 at include/linux/dma-mapping.h:555
  netvsc_probe+0x3c9/0x3e0

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

Bug description:
  SRU Justification

  [Impact]

  When I hot-add a NIC to a Ubuntu 20.04 VM (“5.13.0-1023-azure 
#27~20.04.1-Ubuntu”), I get the the below call-trace.
  Please include the March-2022 fix: “Drivers: hv: vmbus: Fix initialization of 
device object in vmbus_device_register()” 
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3a5469582c241abca22500f36a9cb8e9331969cf)

  BTW, this call-trace should be harmless to a non-CVM VM.

  [ 364.275105] hv_utils: Heartbeat IC version 3.0
  [ 364.275137] hv_utils: KVP IC version 4.0
  [ 364.275146] hv_utils: Shutdown IC version 3.2
  [ 364.275153] hv_utils: TimeSync IC version 4.0
  [ 365.281376] [ cut here ]
  [ 365.281380] WARNING: CPU: 0 PID: 499 at include/linux/dma-mapping.h:555 
netvsc_probe+0x3c9/0x3e0 [hv_netvsc]
  [ 365.281392] Modules linked in: udf crc_itu_t iptable_mangle iptable_filter 
iptable_raw xt_LOG nf_log_syslog bpfilter nls_iso8859_1 dm_multipath 
scsi_dh_rdac scsi_dh_emc scsi_dh_alua kvm_intel kvm joydev hid_generic 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd 
cryptd serio_raw hv_netvsc pata_acpi hyperv_keyboard hid_hyperv hv_utils 
hv_balloon hyperv_fb hid sch_fq_codel ipmi_devintf drm ipmi_msghandler msr 
i2c_core ip_tables x_tables autofs4
  [ 365.281422] CPU: 0 PID: 499 Comm: kworker/0:3 Not tainted 5.13.0-1023-azure 
#27~20.04.1-Ubuntu
  [ 365.281424] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090008 12/07/2018
  [ 365.281427] Workqueue: hv_pri_chan vmbus_add_channel_work
  [ 365.281434] RIP: 0010:netvsc_probe+0x3c9/0x3e0 [hv_netvsc]
  [ 365.281440] Code: 37 c0 4c 89 e6 48 c7 c7 98 f2 37 c0 e8 70 b1 c4 da e9 e9 
fc ff ff 49 c7 84 24 88 0b 00 00 00 00 00 00 41 bf f4 ff ff ff eb b0 <0f> 0b e9 
19 fe ff ff 41 bf f4 ff ff ff e9 51 ff ff ff 0f 1f 44 00
  [ 365.281442] RSP: 0018:99270075bbd0 EFLAGS: 00010246
  [ 365.281444] RAX:  RBX: 890840b21000 RCX: 
0002
  [ 365.281446] RDX: 0002 RSI:  RDI: 
0002
  [ 365.281447] RBP: 99270075bbf8 R08:  R09: 

  [ 365.281448] R10: 9c74e820 R11: 0394 R12: 
890844dc6000
  [ 365.281449] R13: 0002 R14: 301d0800ae28 R15: 
000f
  [ 365.281451] FS: () GS:8909f7c0() 
knlGS:
  [ 365.281453] CS: 0010 DS:  ES:  CR0: 80050033
  [ 365.281454] CR2: 5619b3504d38 CR3: 0001091f8005 CR4: 
003706f0
  [ 365.281459] Call Trace:
  [ 365.281461] 
  [ 365.281465] vmbus_probe+0x67/0x80
  [ 365.281468] really_probe+0x1dc/0x440
  [ 365.281472] driver_probe_device+0xf0/0x160
  [ 365.281476] __device_attach_driver+0x79/0xe0
  [ 365.281479] ? driver_allows_async_probing+0x50/0x50
  [ 365.281482] bus_for_each_drv+0x84/0xd0
  [ 365.281485] __device_attach+0xed/0x170
  [ 365.281488] device_initial_probe+0x13/0x20
  [ 365.281491] bus_probe_device+0x8f/0xa0
  [ 365.281494] device_add+0x3f4/0x8e0
  [ 365.281496] ? hrtimer_init+0x2b/0x70
  [ 365.281501] device_register+0x1b/0x20
  [ 365.281503] vmbus_device_register+0x5e/0xe0
  [ 365.281505] vmbus_add_channel_work+0x12d/0x190
  [ 365.281507] process_one_work+0x21a/0x3b0
  [ 365.281511] worker_thread+0x4d/0x3e0
  [ 365.281515] ? process_one_work+0x3b0/0x3b0
  [ 365.281517] kthread+0x12b/0x150
  [ 365.281521] ? set_kthread_struct+0x40/0x40
  [ 365.281523] ret_from_fork+0x22/0x30
  [ 365.281528] 
  [ 365.281529] ---[ end trace 80a393e06f0ee58d ]---
  [ 365.514764] hv_balloon: Max. dynamic memory size: 8192 MB
  [ 367.937000] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

  [Test Case]

  Microsoft tested

  [Where things could go wrong]

  CVM VNIC instances may not 

[Kernel-packages] [Bug 1970586] Re: No sound support on Linux AWS/Azure kernels (but supported on GCP)

[Ubuntu Kernel Bot]

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

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

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


** Tags added: verification-needed-jammy

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

Title:
  No sound support on Linux AWS/Azure kernels (but supported on GCP)

Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-aws source package in Jammy:
  Fix Committed
Status in linux-azure source package in Jammy:
  In Progress

Bug description:
  In GCP images it is possible to create virtual MIDI devices and
  generally do stuff like audio routing, etc.

  At CircleCI, where we run many of our VMs on Ubuntu in GCP, several of
  our customers use this functionality to test audio equipment in their
  CI runs.

  Unfortunately they cannot run their tests on our AWS based VMs, as
  there is no sound support compiled into the kernel on the AWS kernel
  and images.

  See the package listings for the other kernels for, e.g. the loopback driver:
  ```
  linux-modules-extra-5.4.0-99-generic: 
/lib/modules/5.4.0-99-generic/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1031-oracle: 
/lib/modules/5.8.0-1031-oracle/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1032-gcp: 
/lib/modules/5.8.0-1032-gcp/kernel/sound/drivers/snd-aloop.ko
  ```

  We would love to be able to install the sound drivers (especially snd-
  aloop) with the linux-modules-extra-aws package, but currently cannot,
  and obviously do not want to start running our own kernels, as then we
  lose the immediacy of kernel patches provided upstream by Canonical.

  You can see the difference in the GCP:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/jammy/tree/debian.gcp/config/config.common.ubuntu#n6884

  and AWS kernel:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/tree/debian.aws/config/config.common.ubuntu

  again there. The reasoning for the removal appears to be in this commit from 
2016:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/commit/debian.aws/config/config.common.ubuntu?id=b5e310c4cc872c3fc7c7dd09ce67efb11eeaf07c

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


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

[Kernel-packages] [Bug 1969457] Re: /dev/zvol links not created for encrypted zvols, zfs-volume-wait Timed out waiting on zvol links

[Launchpad Bug Tracker]

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

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

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

Title:
  /dev/zvol links not created for encrypted zvols, zfs-volume-wait Timed
  out waiting on zvol links

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  Fresh installation of 20.04.4 with installer created zfs native encrypted root
  zfsutils-linux: 0.8.3-1ubuntu12.13

  On reboot, zvol /dev/zvol entries are not being created. This seems to
  effect different zvols each reboot.

  Example logs:
  ```
  -- A start job for unit zsys-gc.service has finished successfully.
  -- 
  -- The job identifier is 3139.
  Apr 19 06:43:49 monolith zvol_wait[74768]: cannot open 
'rpool/export/vault/block': dataset does not exist
  Apr 19 06:43:50 monolith zvol_wait[74786]: cannot open 
'rpool/export/vault/block': dataset does not exist
  Apr 19 06:43:51 monolith zvol_wait[74805]: cannot open 
'rpool/export/vault/block': dataset does not exist
  Apr 19 06:43:52 monolith zvol_wait[74823]: cannot open 
'rpool/export/vault/block': dataset does not exist
  Apr 19 06:43:53 monolith zvol_wait[74932]: cannot open 
'rpool/export/vault/block': dataset does not exist
  Apr 19 06:43:54 monolith zvol_wait[74950]: cannot open 
'rpool/export/vault/block': dataset does not exist
  Apr 19 06:43:55 monolith zvol_wait[74969]: cannot open 
'rpool/export/vault/block': dataset does not exist
  Apr 19 06:43:56 monolith zvol_wait[74987]: cannot open 
'rpool/export/vault/block': dataset does not exist
  Apr 19 06:43:57 monolith zvol_wait[75006]: cannot open 
'rpool/export/vault/block': dataset does not exist
  Apr 19 06:43:58 monolith zvol_wait[4440]: Still waiting on 1 zvol links ...
  Apr 19 06:43:58 monolith zvol_wait[4440]: No progress since last loop.
  Apr 19 06:43:58 monolith zvol_wait[4440]: Checking if any zvols were deleted.
  Apr 19 06:43:58 monolith zvol_wait[4440]: Remaining zvols:
  Apr 19 06:43:58 monolith zvol_wait[4440]: rpool/libvirt_zvols/kube-04-disk0
  Apr 19 06:43:58 monolith zvol_wait[4440]: Timed out waiting on zvol links
  Apr 19 06:43:58 monolith systemd[1]: zfs-volume-wait.service: Main process 
exited, code=exited, status=1/FAILURE
  -- Subject: Unit process exited
  -- Defined-By: systemd
  -- Support: http://www.ubuntu.com/support
  -- 
  -- An ExecStart= process belonging to unit zfs-volume-wait.service has exited.
  -- 
  -- The process' exit code is 'exited' and its exit status is 1.
  Apr 19 06:43:58 monolith systemd[1]: zfs-volume-wait.service: Failed with 
result 'exit-code'.
  -- Subject: Unit failed
  -- Defined-By: systemd
  -- Support: http://www.ubuntu.com/support
  -- 
  -- The unit zfs-volume-wait.service has entered the 'failed' state with 
result 'exit-code'.
  Apr 19 06:43:58 monolith systemd[1]: Failed to start Wait for ZFS Volume 
(zvol) links in /dev.
  -- Subject: A start job for unit zfs-volume-wait.service has failed
  -- Defined-By: systemd
  -- Support: http://www.ubuntu.com/support
  -- 
  -- A start job for unit zfs-volume-wait.service has finished with a failure.
  -- 
  -- The job identifier is 226 and the job result is failed.
  Apr 19 06:43:58 monolith systemd[1]: Dependency failed for ZFS volumes are 
ready.
  -- Subject: A start job for unit zfs-volumes.target has failed
  -- Defined-By: systemd
  -- Support: http://www.ubuntu.com/support
  -- 
  -- A start job for unit zfs-volumes.target has finished with a failure.
  ```
  I believe this is related to changes made here:
  https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1888405

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


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

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

etherdevice: Adjust ether_addr* prototypes to silence -Wstringop-overead
mm: page_alloc: fix building error on -Werror=array-compare
tracing: Dump stacktrace trigger to the corresponding instance
gfs2: assign rgrp glock before compute_bitstructs
tcp: fix race condition when creating child sockets from syncookies
tcp: Fix potential use-after-free due to double kfree()
ALSA: usb-audio: Clear MIDI port active flag after draining
ASoC: atmel: Remove system clock tree configuration for at91sam9g20ek
ASoC: msm8916-wcd-digital: Check failure for devm_snd_soc_register_component
dmaengine: imx-sdma: Fix error checking in sdma_event_remap
dmaengine: mediatek:Fix PM usage reference leak of 
mtk_uart_apdma_alloc_chan_resources
igc: Fix infinite loop in release_swfw_sync
igc: Fix BUG: scheduling while atomic
rxrpc: Restore removed timer deletion
net/smc: Fix sock leak when release after smc_shutdown()
net/packet: fix packet_sock xmit return value checking
net/sched: cls_u32: fix possible leak in u32_init_knode()
l3mdev: l3mdev_master_upper_ifindex_by_index_rcu should be using 
netdev_master_upper_dev_get_rcu
netlink: reset network and mac headers in netlink_dump()
selftests: mlxsw: vxlan_flooding: Prevent flooding of unwanted packets
ARM: vexpress/spc: Avoid negative array index when !SMP
reset: tegra-bpmp: Restore Handle errors in BPMP response
platform/x86: samsung-laptop: Fix an unsigned comparison which can never be 
negative
ALSA: usb-audio: Fix undefined behavior due to shift overflowing the constant
vxlan: fix error return code in vxlan_fdb_append
cifs: Check the IOCB_DIRECT flag, not O_DIRECT
mt76: Fix undefined behavior due to shift overflowing the constant
brcmfmac: sdio: Fix undefined behavior due to shift overflowing the constant
dpaa_eth: Fix missing of_node_put in dpaa_get_ts_info()
drm/msm/mdp5: check the return of kzalloc()
net: macb: Restart tx only if queue pointer is lagging
scsi: qedi: Fix failed disconnect handling
stat: fix inconsistency between struct stat and struct compat_stat
EDAC/synopsys: Read the error count from the correct register
oom_kill.c: futex: delay the OOM reaper to allow time for proper futex cleanup
ata: pata_marvell: Check the 'bmdma_addr' beforing reading
dma: at_xdmac: fix a missing check on list iterator
drm/panel/raspberrypi-touchscreen: Avoid NULL deref if not initialised
drm/panel/raspberrypi-touchscreen: Initialise the bridge in prepare
KVM: PPC: Fix TCE handling for VFIO
drm/vc4: Use pm_runtime_resume_and_get to fix pm_runtime_get_sync() usage
powerpc/perf: Fix power9 event alternatives
xtensa: patch_text: Fixup last cpu should be master
xtensa: fix a7 clobbering in coprocessor context load/store
openvswitch: fix OOB access in reserve_sfa_size()
ASoC: soc-dapm: fix two incorrect uses of list iterator
e1000e: Fix possible overflow in LTR decoding
ARC: entry: fix syscall_trace_exit argument
arm_pmu: Validate single/group leader events
ext4: fix symlink file size not match to file content
ext4: fix use-after-free in ext4_search_dir
ext4, doc: fix incorrect h_reserved size
ext4: fix overhead calculation to account for the reserved gdt blocks
ext4: force overhead calculation if the s_overhead_cluster makes no sense
jbd2: fix a potential race while discarding reserved buffers after an abort
spi: atmel-quadspi: Fix the buswidth adjustment between spi-mem and controller
staging: ion: Prevent incorrect reference counting behavour
block/compat_ioctl: fix range check in BLKGETSIZE
Linux 5.4.191
UBUNTU: upstream stable to v5.4.191

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

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

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

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

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

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu 

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  error during upgrade // bug report was suggested

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu version:
  Ubuntu 5.15.0-27.28-generic 5.15.30

  when running:
  sudo apt upgrade

  [..]

  /etc/grub.d/bin/grubcfg_proxy: error while loading shared libraries: 
libcrypto.s
  o.1.1: cannot open shared object file: No such file or directory
  run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 127
  dpkg: Fehler beim Bearbeiten des Paketes linux-image-5.13.0-40-generic 
(--remove
  ):
   »installiertes linux-image-5.13.0-40-generic-Skript des Paketes 
post-removal«-U
  nterprozess gab den Fehlerwert 1 zurück
  dpkg: Zu viele Fehler, Abbruch
  Fehler traten auf beim Bearbeiten von:
   linux-image-5.13.0-40-generic
  Bearbeitung wurde angehalten, da zu viele Fehler auftraten.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-33-generic 5.15.0-33.34
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  thorsten   1323 F pulseaudio
   /dev/snd/controlC0:  thorsten   1323 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 27 20:12:39 2022
  InstallationDate: Installed on 2020-06-05 (721 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=cd590fdd-0816-46d4-aa45-ee4c7c9789f5 ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/09/2020
  dmi.bios.release: 5.6
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: SYSKLi35.86A.0073.2020.0909.1625
  dmi.board.asset.tag: �=\�
  dmi.board.name: NUC6i5SYB
  dmi.board.vendor: Intel corporation
  dmi.board.version: H81131-503
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrSYSKLi35.86A.0073.2020.0909.1625:bd09/09/2020:br5.6:svn:pn:pvr:rvnIntelcorporation:rnNUC6i5SYB:rvrH81131-503:cvn:ct3:cvr:sku:

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


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

[Kernel-packages] [Bug 1976115] [NEW] error during upgrade // bug report was suggested

[Uthoru]

Public bug reported:

Ubuntu version:
Ubuntu 5.15.0-27.28-generic 5.15.30

when running:
sudo apt upgrade

[..]

/etc/grub.d/bin/grubcfg_proxy: error while loading shared libraries: libcrypto.s
o.1.1: cannot open shared object file: No such file or directory
run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 127
dpkg: Fehler beim Bearbeiten des Paketes linux-image-5.13.0-40-generic (--remove
):
 »installiertes linux-image-5.13.0-40-generic-Skript des Paketes post-removal«-U
nterprozess gab den Fehlerwert 1 zurück
dpkg: Zu viele Fehler, Abbruch
Fehler traten auf beim Bearbeiten von:
 linux-image-5.13.0-40-generic
Bearbeitung wurde angehalten, da zu viele Fehler auftraten.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-33-generic 5.15.0-33.34
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  thorsten   1323 F pulseaudio
 /dev/snd/controlC0:  thorsten   1323 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri May 27 20:12:39 2022
InstallationDate: Installed on 2020-06-05 (721 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=cd590fdd-0816-46d4-aa45-ee4c7c9789f5 ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-27-generic N/A
 linux-backports-modules-5.15.0-27-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/09/2020
dmi.bios.release: 5.6
dmi.bios.vendor: Intel Corp.
dmi.bios.version: SYSKLi35.86A.0073.2020.0909.1625
dmi.board.asset.tag: �=\�
dmi.board.name: NUC6i5SYB
dmi.board.vendor: Intel corporation
dmi.board.version: H81131-503
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrSYSKLi35.86A.0073.2020.0909.1625:bd09/09/2020:br5.6:svn:pn:pvr:rvnIntelcorporation:rnNUC6i5SYB:rvrH81131-503:cvn:ct3:cvr:sku:

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


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

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/bugs/1976115/+attachment/5593439/+files/lspci-vnvn.log

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

Title:
  error during upgrade // bug report was suggested

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu version:
  Ubuntu 5.15.0-27.28-generic 5.15.30

  when running:
  sudo apt upgrade

  [..]

  /etc/grub.d/bin/grubcfg_proxy: error while loading shared libraries: 
libcrypto.s
  o.1.1: cannot open shared object file: No such file or directory
  run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 127
  dpkg: Fehler beim Bearbeiten des Paketes linux-image-5.13.0-40-generic 
(--remove
  ):
   »installiertes linux-image-5.13.0-40-generic-Skript des Paketes 
post-removal«-U
  nterprozess gab den Fehlerwert 1 zurück
  dpkg: Zu viele Fehler, Abbruch
  Fehler traten auf beim Bearbeiten von:
   linux-image-5.13.0-40-generic
  Bearbeitung wurde angehalten, da zu viele Fehler auftraten.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-33-generic 5.15.0-33.34
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  thorsten   1323 F pulseaudio
   /dev/snd/controlC0:  thorsten   1323 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 27 20:12:39 2022
  InstallationDate: Installed on 2020-06-05 (721 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=cd590fdd-0816-46d4-aa45-ee4c7c9789f5 ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/09/2020
  dmi.bios.release: 5.6
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: 

[Kernel-packages] [Bug 1927808] Re: rtw88_8821ce causes freeze

[Pippo Franco]

I tested it and it won't give me freezes. But it seems to stop being
able to connect to my network after 24 hours. Even if I try to forget
and remake connection and reset router it will still can't connect.
(This happened even with Ubuntu 20.04, now I am on 22.04)

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

Title:
  rtw88_8821ce causes freeze

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.13 source package in Focal:
  Confirmed
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Confirmed
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Confirmed
Status in linux-oem-5.13 source package in Jammy:
  Invalid
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card.
  Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic 
kernel,and it works "well" for both WiFi and Bluetooth.
  However, this module (driver) causes frequent freezes, randomly but usually 
within a few minutes of running (thus very soon after boot): screen display 
remains frozen, no response to either keyboard or mouse input. All I can do is 
to hold the power button to power off, then reboot.

  After reboot, I do not see any crash reports, nor logs about the freeze.
  Please let me know if I should try to collect some info, and how.

  For now I use the DKMS module/driver from
    https://github.com/tomaspinho/rtl8821ce
  (having blacklisted rtw88_8821ce), and it seems to work perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-16-generic 5.11.0-16.17
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  psz1189 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  8 16:58:19 2021
  InstallationDate: Installed on 2021-04-23 (14 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera
   Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Protempo Ltd L116HTN6SPW
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-16-generic N/A
   linux-backports-modules-5.11.0-16-generic  N/A
   linux-firmware 1.197
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2020
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Notebook
  dmi.product.name: L116HTN6SPW
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Protempo Ltd

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


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

[Kernel-packages] [Bug 1912935] Re: battery drain while notebook off / shutdown

[Michael Rickmann]

Hello Kai-Heng, hello Martien,
thank you for your efforts. I am here on Manjaro affected by this bug. My 
hardware is the same as in the description of this bug. I compared (a) standard 
Manjaro 5.17.9 kernel, (b) same with Kei-Heng’s 
0001-PCI-Detach-PM-domain-on-shutdown.patch (#50), and (c) with the original 
patch published on lore.kernel.org (see #22 of this thread). Battery state was 
recorded after 10 – 11h shutdown from /sys/class/power_supply/BAT0/capacity. 
Power consumption during startup was neglected. Extrapolated 24h-power drain 
was for (a, standard) 14.4%, (b, 0001...patch) 14.9%, and (c original patch) 
2,4%.
Sorry for these results,
Regards Michael

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

Title:
  battery drain while notebook off / shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  my battery drains around 15 to 20 percent a day when shutdown on linux ubuntu.
  It is an HP notebook HP 15s-eq0355ng , Ryzen 5 3500U , Vega8 .

  Tested:

  - with ubuntu 20.04
  - Kernel 5.4, 5.8 (hwe) and the current mainline kernel 5.11 (rc4)
  - no usb devices are plugged in
  - no wake ob lan available
  - no USB power when off (checked with optical mouse)
  - no visible LEDs are on when shutdown

  I reinstalled window 10, when shutdown from windows there is no
  (visible) battery drain (or significantly lower).

  Linux is unusable on this device, if the battery drains in a short
  time to 0% percent. This cause battery damage ...

  ---

  Tested TLP with default settings and activated
  DEVICES_TO_DISABLE_ON_SHUTDOWN (bluetooth wifi wwan), same power
  consumption after shutdown.

  Same power consumption on 20.10 (Groovy Gorilla).

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  test953 F pulseaudio
   /dev/snd/controlC0:  test953 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-24 (0 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  MachineType: HP HP Laptop 15s-eq0xxx
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic 
root=UUID=17ad50f6-ec98-46b2-8c2e-c169f9baace8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-64-generic N/A
   linux-backports-modules-5.4.0-64-generic  N/A
   linux-firmware1.187.8
  Tags:  focal
  Uname: Linux 5.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.vendor: AMI
  dmi.bios.version: F.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86FD
  dmi.board.vendor: HP
  dmi.board.version: 99.40
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.30:bd11/18/2020:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.40:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15s-eq0xxx
  dmi.product.sku: 20T63EA#ABD
  dmi.sys.vendor: HP

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


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

[Kernel-packages] [Bug 1958770] Re: Aquantia GbE LAN driver causes UBSAN error during kernel boot

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-oem-5.14/5.14.0-1040.44
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-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1958770

Title:
  Aquantia GbE LAN driver causes UBSAN error during kernel boot

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.17 package in Ubuntu:
  Confirmed

Bug description:
  The undefined behaviour sanitiser picks up an array-index-out-of-
  bounds in the aquantia atlantic driver. The NIC is (I think) built
  into my gigabyte motherboard
  (https://www.gigabyte.com/uk/Motherboard/X399-AORUS-XTREME-
  rev-10/sp#sp). This wasn't an issue before I upgrading from 20.04 to
  22.04 (or at least dmesg didn't previously complain).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 23 13:02:10 2022
  InstallationDate: Installed on 2019-08-07 (899 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. X399 AORUS XTREME
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic 
root=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 ro quiet splash 
resume=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 resume_offset=34816 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-17-generic N/A
   linux-backports-modules-5.15.0-17-generic  N/A
   linux-firmware 1.204
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: X399 AORUS XTREME-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.:bvrF5:bd12/11/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSXTREME:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSXTREME-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X399 AORUS XTREME
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Kernel-packages] [Bug 1971417] Re: Fix REG_WAIT timeout for Yellow Carp

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-oem-5.14/5.14.0-1040.44
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-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1971417

Title:
  Fix REG_WAIT timeout for Yellow Carp

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

Bug description:
  [Impact]
  During hotplug built-in hdmi, the error message show up.
  #REG_WAIT timeout for yellow Carp

  [Fix]
  This tends to take miliseconds in certain scenarios and we'd rather not
  wait that long. Due to how this interacts with det size update and
  locking waiting should not be necessary as compbuf updates before
  unlock.

  Add a watch for config error instead as that is something we actually do
  care about.

  [Test Case]
  1. Plug and unplug hdmi
  2. cant get the error message in dmesg.

  [Where problems could occur]
  Low

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


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

[Kernel-packages] [Bug 1972815] Re: Headset mic with Cirrus logic codec doesn't work

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-oem-5.14/5.14.0-1040.44
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-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1972815

Title:
  Headset mic with Cirrus logic codec doesn't work

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

Bug description:
  [Impact]
  Headset mic doesn't be selected automatically after headset is plugged in.

  [Fix]
  Cirrus provides a fix for this issue
  
https://patchwork.kernel.org/project/alsa-devel/cover/20220504161236.2490532-1-sbind...@opensource.cirrus.com/

  [Test]
  Verified on the target platform, and confirmed these patches work.

  [Where problems could occur]
  These affect the mic detection on CS8409_BULLSEYE, CS8409_WARLOCK, 
CS8409_WARLOCK_MLK, CS8409_WARLOCK_MLK_DUAL_MIC, CS8409_CYBORG, and CS8409_ODIN 
platforms. Hard to tell if it introduce any regression, will keep an eye on it.

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


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

[Kernel-packages] [Bug 1974111] Re: Mute/mic LEDs no function on Elitebook 630

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-oem-5.14/5.14.0-1040.44
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-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1974111

Title:
  Mute/mic LEDs no function on Elitebook 630

Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.14 source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  The mic mute/audio mute LEDS are not work on HP EliteBook 630 G9 Notebook PC

  [Fix]
  It needs the specific quirk for the hardware layout.
  Thus, add the quirks to make it works.

  [Test]
  After applying the quirk, the audio/mic mute LEDs are working good.

  [Where problems could occur]
  If HP ships the different system boards design with the same subsystem ID of 
audio codec which is using different GPIO pins (different layout), then the 
quirk will not work (LEDs will not work when muting audio-output or microphone).

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


-- 
Mailing list: https://launchpad.net/~kernel-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

[Kevin Peter Gade]

Please find output of cat /proc/iomem attached.

** Attachment added: "output cat /proc/iomem"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+attachment/5593426/+files/iomem.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1887490] Re: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model

[Sven Kieske]

> I am not sure I would still call it a regression and it is certainly
an annoying, but it can be workarounded.

it worked before, now it doesn't without manual intervention, that's the
basic definition of a regression, no?

after all, there are _always_ workarounds for regressions, so I would
not consider it appropriate to call a regression not-a-regression
because there is some workaround available.

we are currently affected by this and need to figure out if the
workaround is even an acceptable solution, because in a cloud
environment you can't/don't want to manually patch libvirt xml for
dozens of machines.

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

Title:
  [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model

Status in libvirt package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Fix Released
Status in libvirt source package in Focal:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in qemu source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * CPU definitions are added to libvirt as these CPUs are known
     and added to qemu for execution.
     And due to that over time some are considered missing in
     former releases.

   * To really benefit from the new features of these chips
     they have to be known, therefore new type additions done by
     upstream should be backported if they generally apply and do
     not depend on SRU-critical changes.

   * This backports three upstream fixes that just add definitions
     (no control flow changes)

  [Test Case]

   * Check if it has an EPYC-Rome entry in
     /usr/share/libvirt/cpu_map/index.xml and the file included
     there exists.

   * Define a guest like:
     
   EPYC-Rome
     
     You can only "really" start this on a system with the
     matching HW. But even on others it will change from:
   error: internal error: Unknown CPU model EPYC-Rome
     to being unable to start for some features missing.

   * libvirt probes a system if a named cpu can be used, after the
     fix this should include EPYC-Rome
     $ virsh domcapabilities | grep EPYC
    EPYC-IBPB
    EPYC

  [Regression Potential]

   * Usually these type additions are safe unless they add control flow
     changes (e.g. to handle yet unknown types of registers or such) but
     that isn't the case here.
     A regression if any is to be expected on systems that are close to the
     newly added type(s). Those will after the update be detected as such
     if e.g. host-model is used. If then running on a mixed cluster of
     updated/non-updated systems migrations will only work if the target is
     updated as well.

  [Other Info]

   * This is the first build since glibc 2.32 arrived in groovy, hence we
     need to be careful of the fix done for bug 1892826.
 It has to be checked if the linking is fine after the rebuild.
 The workload still works in groovy despite 2.32 being present (I'd ahve 
 expected it doesn't), so we will keep the revert as-is for now.
 To be sure that adds two tests that shall be done:
     - check the linking to point to libtirpc instead of glibc
   $ eu-readelf -a /usr/lib/libvirt/libvirt_lxc | grep xdr_uint64 | grep 
GLOBAL
   Was pointing to glibc, does it still and if so does it work (see 
   below)?
     - run the autopkgtest cases as the LXC tests would trigger an issue if
   there is one

  

  ## Qemu SRU ##

  [Impact]

   * CPU definitions are added to qemu as these CPUs are known.
     And due to that over time are missing in former releases.

   * To really benefit from the new features of these chips
     they have to be known, therefore new type additions done by
     upstream should be backported if they generally apply and do
     not depend on SRU-critical changes.

   * This backports two upstream fixes that just add definitions (no
     control flow changes)

  [Test Case]

   * Probe qemu for the known CPU types (works on all HW)
     $ qemu-system-x86_64 -cpu ? | grep EPYC
     Focal without fix:
     x86 EPYC  (alias configured by machine type)
     x86 EPYC-IBPB (alias of EPYC-v2)
     x86 EPYC-v1   AMD EPYC Processor
     x86 EPYC-v2   AMD EPYC Processor (with IBPB)
     Focal with fix also adds:
     x86 EPYC-Rome (alias configured by machine type)
     x86 EPYC-Rome-v1  AMD EPYC-Rome Processor
     x86 EPYC-v3   AMD EPYC Processor

   * Given such HW is available start a KVM guest using those new types
     Since we don't have libvirt support (yet) do so directly in qemu
     commandline like (bootloader is enough)
     $ qemu-system-x86_64 -cpu EPYC-Rome -machine pc-q35-focal,accel=kvm 
-nographic
     $ qemu-system-x86_64 -cpu EPYC-v3 -machine 

[Kernel-packages] [Bug 1975494] Re: nvidia module cant load with 5.13.0-41-generic

[Ian Gordon]

I have the same problem. The nvidia drivers (version 470 in my case)
don't load after upgrading to 5.13.0-41-generic. Reverting to
5.13.0-39-generic fixes the problem.

I did notice that -41 has a lot of changes from the "stable" impish
kernel and that the modules loaded on my machine with -41 include lots
of wmi and i915 stuff:

i915 2400256  1
i2c_algo_bit   16384  1 i915
drm_kms_helper253952  1 i915
cec53248  2 drm_kms_helper,i915
drm   557056  3 drm_kms_helper,i915
video  53248  2 dell_wmi,i915
wmi32768  5 
dell_wmi_sysman,dell_wmi,wmi_bmof,dell_smbios,dell_wmi_descriptor

which the -39 modules does not load. Black listing these modules does
not fix the problem.

The 2 machines we are having issues with are

Dell Optiplex 7090 with a Nvidia GeForce RTX 3070

so I tried the 5.14.0-1038-oem kernel which fortunately fixes the
problem for me.

Regards,

Ian G.

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

Title:
  nvidia module cant load with 5.13.0-41-generic

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

Bug description:
  Hi,

  My system is working fine with 5.13.0-40-generic kernel and nvidia-
  driver-510...

  Switching to 5.13.0-41 is messing something up...

  Black screen after grub.

  No graphic at all (black screen).

  Further investigation show problems with the nvidia module :

  
  --
  nvidia :01:00.0: vgaarb: changed VGA decodes: 
olddecodes=none,decodes=none:owns=none
  NVRM: The NVIDIA GPU :01:00.0
  NVRM: (PCI ID: 10de:1cb3) installed in this system has
  NVRM: fallen off the bus and is not responding to commands.
  nvidia: probe of :01:00.0 failed with error -1
  NVRM: The NVIDIA probe routine failed for 1 device(s).
  NVRM: None of the NVIDIA devices were initialized.
  nvidia-nvlink: Unregistered the Nvlink Core, major device number 507
  --

  modules nvidia-* are present and installed :

  --
  dkms status
  nvidia, 510.73.05, 5.13.0-40-generic, x86_64: installed
  nvidia, 510.73.05, 5.13.0-41-generic, x86_64: installed
  --

  but they can't be modprobed :

  ---
  modprobe: ERROR: could not insert 'nvidia': No such device
  ---

  Reboot on the 5.13.0-40-generic solve the problem.

  We are numerous users here to have the same behaviour...

  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

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


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

[Kernel-packages] [Bug 1973620] Re: prevent kernel panic with overlayfs + shiftfs

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-
hwe-5.13/5.13.0-46.51~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal' 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1973620

Title:
  prevent kernel panic with overlayfs + shiftfs

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Impish:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Incomplete

Bug description:
  [Impact]

  The patch that we have recently re-introduced to properly support
  overlayfs on top of shiftfs can introduce potential kernel panics, for
  example:

  BUG: kernel NULL pointer dereference, address: 0008
  [  447.039738] #PF: supervisor read access in kernel mode
  [  447.040369] #PF: error_code(0x) - not-present page
  [  447.041002] PGD 0 P4D 0
  [  447.041325] Oops:  [#1] SMP NOPTI
  [  447.041798] CPU: 0 PID: 73766 Comm: sudo Not tainted 5.15.0-28-generic 
#29~20.04.1-Ubuntu
  [  447.042800] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 
Ubuntu-1.8.2-1ubuntu1+esm1 04/01/2014
  [  447.043979] RIP: 0010:aa_file_perm+0x3a/0x470
  [  447.044565] Code: 54 53 48 83 ec 68 48 89 7d 80 89 4d 8c 65 48 8b 04 
25 28 00 00 00 48 89 45 d0 31 c0 48 63 05 01 0a 19 01 48 03 82 c0 00 00 00 <4c> 
8b 68 08 f6 46 40 02 0f 85 d0 00 00 00 41 f6 45 40 02 0f 85 c5
  [  447.046837] RSP: 0018:aefe80a4bca8 EFLAGS: 00010246
  [  447.047481] RAX:  RBX: 96e4038abd01 RCX: 
0004
  [  447.048351] RDX: 96e4038abd00 RSI: 96e401215eb8 RDI: 
9c22a2ac
  [  447.049241] RBP: aefe80a4bd38 R08:  R09: 

  [  447.050121] R10:  R11:  R12: 
96e401215eb8
  [  447.051040] R13: 96e4038abd00 R14: 9c22a2ac R15: 
0004
  [  447.051942] FS:  7eff3c0f8c80() GS:96e45e40() 
knlGS:
  [  447.052981] CS:  0010 DS:  ES:  CR0: 80050033
  [  447.053696] CR2: 0008 CR3: 02be2000 CR4: 
003506f0
  [  447.054571] Call Trace:
  [  447.054883]  
  [  447.055154]  ? unlock_page_memcg+0x2f/0x40
  [  447.055668]  ? page_remove_rmap+0x4b/0x320
  [  447.056180]  common_file_perm+0x72/0x170
  [  447.056669]  apparmor_file_permission+0x1c/0x20
  [  447.057237]  security_file_permission+0x30/0x1a0
  [  447.057898]  rw_verify_area+0x35/0x60
  [  447.058392]  vfs_read+0x6d/0x1a0
  [  447.058842]  ksys_read+0xb1/0xe0
  [  447.059276]  __x64_sys_read+0x1a/0x20
  [  447.059732]  do_syscall_64+0x5c/0xc0
  [  447.060183]  ? __set_current_blocked+0x3b/0x60
  [  447.060738]  ? exit_to_user_mode_prepare+0x3d/0x1c0
  [  447.061434]  ? syscall_exit_to_user_mode+0x27/0x50
  [  447.062099]  ? do_syscall_64+0x69/0xc0
  [  447.062603]  ? irqentry_exit_to_user_mode+0x9/0x20
  [  447.063210]  ? irqentry_exit+0x19/0x30
  [  447.063678]  ? exc_page_fault+0x89/0x160
  [  447.064165]  ? asm_exc_page_fault+0x8/0x30
  [  447.064675]  entry_SYSCALL_64_after_hwframe+0x44/0xae
  [  447.065298] RIP: 0033:0x7eff3c2cb002

  [Test case]

  It is really easy to trigger this specific kernel panic running the
  lxc autopackage test.

  [Fix]

  This bug happens because we don't need to decrement anymore the
  refcount for the previous vm_file value in ovl_vm_prfile_set(). So the
  fix simply consists of removing the unnecessary fput().

  [Regression potential]

  This patch affects only overlayfs (only when AUFS is enabled), so we
  may see regressions in overlayfs in kernels that have AUFS enabled
  (focal hwe and cloud kernels).

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


-- 
Mailing list: https://launchpad.net/~kernel-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

[Kai-Heng Feng]

Thanks. Please attach `sudo cat /proc/iomem`.

-- 
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 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen

[msmalin]

I'm on a Dell Precision 3520 with Kubuntu 18.04, I have the same issue
with 4.15.0-177 and 4.15.0-180.  This also seems to disable my sound,
bluetooth, and wifi.  Currently booting 4.15.0-176.

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

Title:
  linux-image-4.15.0-177-generic freezes on the welcome screen

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

Bug description:
  After updating to linux-image-4.15.0-177-generic, my machine
  completely freezes on the Ubuntu Welcome screen, i.e. right after
  switching to GUI mode. The mouse pointer is frozen, the keyboard does
  not even respond to CAPS LOCK or NUM LOCK, pressing CTRL+ALT+F2 shows
  no reaction.

  I cannot work with my machine at this point and have to hard reset it.

  Selecting advanced boot options in grub and selecting the previous
  linux kernel 4.15.0-176 makes it work again. So this bad bug was
  introduced with the 4.15.0-177 kernel release.

  I tried removing the nvidia-driver-510 package, presumably making
  Ubuntu use the "nouveau" driver, and with that, I could use the
  welcome screen and log in, but the machine still froze shortly
  afterwards.

  So maybe this is some sort of interference with my GeForce 1080
  graphics card, but it is not specific to the driver used.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-177-generic:amd64 4.15.0-177.186
  ProcVersionSignature: Ubuntu 4.15.0-176.185-generic 4.15.18
  Uname: Linux 4.15.0-176-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 2082 F pulseaudio
   /dev/snd/controlC0:  robert 2082 F pulseaudio
   /dev/snd/controlC2:  robert 2082 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu May 12 13:36:28 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-10-29 (2386 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Supermicro Super Server
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-176-generic 
root=UUID=7c296e4d-0189-43a0-aef8-7d536b98a536 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-176-generic N/A
   linux-backports-modules-4.15.0-176-generic  N/A
   linux-firmware  1.173.21
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2019-07-29 (1017 days ago)
  dmi.bios.date: 09/18/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X11SAE
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd09/18/2020:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SAE:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Super Server
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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


-- 
Mailing list: https://launchpad.net/~kernel-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

[Kevin Peter Gade]

$ sudo acpidbg -b 'ex \_SB_.PCI0.LPCB.EC0_.BATL'
Evaluating \_SB_.PCI0.LPCB.EC0_.BATL
Evaluation of \_SB_.PCI0.LPCB.EC0_.BATL returned object 09af25b3, 
external buffer length 18
 [Integer] = 

$ sudo acpidbg -b 'ex \_SB_.PCI0.LPCB.EC0_.BATH'
Evaluating \_SB_.PCI0.LPCB.EC0_.BATH
Evaluation of \_SB_.PCI0.LPCB.EC0_.BATH returned object 3c0aee1f, 
external buffer length 18
 [Integer] = 

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

Re: [Kernel-packages] [Bug 1971933] Re: [Regression] Unable to wake laptop using trackpad input

[John Smith]

Thanks for trying Aaron,
Effort much appreciated.

Also, I think there is some miscommunication,
i.e. My laptop also wakes up with USB devices
(After configuration change in BIOS),

Problem is, my laptop used to wakeup on touchpad interaction as well (till
Ubuntu 21.10).
But after upgrading (to 22.04 jammy),

Touchpad wake is not working.

Does it work on your laptop or it never did ?
(Touchpad interaction to wakeup)

On Fri, May 27, 2022, 11:00 AM Aaron Rainbolt <1971...@bugs.launchpad.net>
wrote:

> Sadly, I have to correct myself - I thought I had replicated the issue,
> but it turns out my particular laptop doesn't use USB to attach the
> mousepad. I tried plugging a USB mouse into my system while running a
> "bad" kernel, and it was able to wake from suspend when I moved the
> mouse. Also, it appears my system is using s2idle. So sadly, I cannot
> reproduce the bug on my hardware after all.
>
> What I can do is leave a hint for the next person who goes to bisect the
> kernel. Due to a change in initrd compression, if you try to install a
> kernel that's too old onto Ubuntu Jammy or Kinetic, it won't be able to
> boot since it won't be able to mount the initrd image. To fix this, do
> "sudo nano /etc/initramfs-tools/initramfs.conf", and change the
> "COMPRESS" option to "gzip" (it will probably be set to "zstd" by
> default). That should get your older kernels booting, so you can
> actually have a fighting chance at bisecting the kernel.
>
> Sorry I couldn't do it myself on my hardware.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1971933
>
> Title:
>   [Regression] Unable to wake laptop using trackpad input
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   After upgrade to Ubuntu 22.04,
>   the dell laptop no longer wakes up using trackpad movement/interaction.
>
>   Wake-on trackpad-interaction used to work since Ubuntu Bionic, i.e.,
>   Working On:
>   Ubuntu 18.04, 18.10, 19.04, 19.10, 20.04, 20.10, 21.04, 21.10.
>
>   NOT Working on: Ubuntu 22.04, Ubuntu 22.10 (Kinetic - 2022-05-16 08:31
>   )
>
>   Just to clarify: Suspend and Resume are working, trackpad is functional
> before and after suspend,
>   But,
>   Trackpad trigger to wakeup from suspend is not working.
>
>   --
>
>   $ cat /proc/version_signature > version.log
>   => Ubuntu 5.15.0-27.28-generic 5.15.30
>
>   -
>
>   $ lsb_release -rd
>   =>
>   Description:Ubuntu 22.04 LTS
>   Release:22.04
>
>   -
>
>   $ apt-cache policy linux-image-generic
>   =>
>   linux-image-generic:
> Installed: 5.15.0.27.30
> Candidate: 5.15.0.27.30
> Version table:
>*** 5.15.0.27.30 500
>   500 http://mirror2.tuxinator.org/ubuntu jammy-updates/main
> amd64 Packages
>   500 http://mirror2.tuxinator.org/ubuntu jammy-security/main
> amd64 Packages
>   100 /var/lib/dpkg/status
>5.15.0.25.27 500
>   500 http://mirror2.tuxinator.org/ubuntu jammy/main amd64
> Packages
>
>   -
>
>   What I expected to happen:
>   Laptop wakes-up from suspend on touchpad interaction
>
>   -
>
>   What happened:
>   Laptop did not wakeup from suspend on touchpad interaction.
>
>   Laptop woke up on the press of power button.
>
>   ---
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 22.04
>   Package: linux-image-generic 5.15.0.27.30
>   ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
>   Uname: Linux 5.15.0-27-generic x86_64
>   NonfreeKernelModules: nvidia_modeset nvidia
>   ApportVersion: 2.20.11-0ubuntu82
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  monkey 5198 F wireplumber
>/dev/snd/controlC1:  monkey 5198 F wireplumber
>/dev/snd/seq:monkey 5195 F pipewire
>   CasperMD5CheckResult: unknown
>   CurrentDesktop: KDE
>   Date: Fri May  6 12:40:22 2022
>   InstallationDate: Installed on 2018-10-25 (1288 days ago)
>   InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
> (20181017.3)
>   Lsusb:
>Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra
>Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless
> interface
>Bus 001 Device 003: ID 0bda:568a Realtek Semiconductor Corp. Integrated
> Webcam
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   MachineType: Dell Inc. Inspiron 15 7000 Gaming
>   ProcFB: 0 i915drmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic
> root=UUID=e6745a81-1ffd-46f5-ae77-652fc77ba79a ro acpi_osi=!
> "acpi_osi=Windows 2013" quiet splash nvidia-drm.modeset=1 vga=0
> rdblacklist=nouveau nouveau.modeset=0 vt.handoff=7
>   PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
> PulseAudio daemon running, or not running as session daemon.
>  

[Kernel-packages] [Bug 1956177] Re: battery not detected by ACPI

[Kai-Heng Feng]

Thanks! Can you please also run

$ sudo acpidbg -b 'ex \_SB_.PCI0.LPCB.EC0_.BATL'

$ sudo acpidbg -b 'ex \_SB_.PCI0.LPCB.EC0_.BATH'

-- 
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 1973482] Re: kernel 4.15.0.177 break everything on Dell XPS 15 9570

[Luis Riveros]

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

Same problem with on Dell XPS 13 with Linux Ubuntu 18.04.6 LTS

Unfortunately the same issue with linux-image-4.15.0-180-generic.

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

Title:
  kernel 4.15.0.177 break everything on Dell XPS 15 9570

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  There are many issues including:

  - wireless card DISBLED / UNCLAIMED
  - no sound output device listed
  - strange electrical noise in the speakers when the cpu is under load
  - mounting /boot/efi hangs for 1m30
  - various services not starting (snap, etc)

  Rolling back to 4.15.0.176 fixes all the issues.

  Can you let me know which logs I could provide to help?

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-177-generic 4.15.0-177.186
  ProcVersionSignature: Ubuntu 4.15.0-177.186-generic 4.15.18
  Uname: Linux 4.15.0-177-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 16 00:39:58 2022
  InstallationDate: Installed on 2018-12-15 (1247 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig:
   virbr0no wireless extensions.
   
   lono wireless extensions.
   
   virbr0-nic  no wireless extensions.
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-177-generic 
root=UUID=d62d426c-0675-4dca-a5e1-6c8b79ed8056 ro acpi_rev_override=1 
nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 
nouveau.runpm=0 mem_sleep_default=deep noibrs noibpb nopti nospectre_v2 
nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off 
mitigations=off clocksource=hpet
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-177-generic N/A
   linux-backports-modules-4.15.0-177-generic  N/A
   linux-firmware  1.173.20
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2021
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.20.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.20.0:bd06/07/2021:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1975909] Re: le bluetooth ne suit pas le rythme (perte de connexion au smartphone, reste connecté, garde l'adresse IP assigné alors que inutilisable), le bluetooth c'est Titanic

[raspb]

bluetoothctl power off; #retour :: Changing power off succeeded
bluetoothctl power on; #retour Failed to set power on: org.bluez.Error.Busy
dmesg :: hci0: command 0x1003 tx timeout
dmesg :: hci0: command 0x1001 tx timeout
dmesg :: hci0: command 0x1009 tx timeout

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

Title:
  le bluetooth ne suit pas le rythme (perte de connexion au smartphone,
  reste connecté, garde l'adresse IP assigné alors que inutilisable), le
  bluetooth c'est Titanic  et petite anecdote c'est pareil sur raspberry
  pi OS ; )

Status in bluez package in Ubuntu:
  New

Bug description:
   Network Bluetooth 
  bluetoothctl system-alias Xorg #Changer de Nom
  bluetoothctl pairable on;
  bluetoothctl discoverable on;
  timeout 20s bluetoothctl scan on &
  bluetoothctl pair [Mac Address];
  apt -y install libdbus-1-3 libdbus-1-dev libglib2.0-dev python2 python-pip; 
#Ub
  pip2 install dbus-python; 
  bt-pan client -r [Mac Address];
  ((bt-pan est requis))

  apt -y install libdbus-1-3 libdbus-1-dev libglib2.0-dev python-dev; #Raspbian
  wget https://bootstrap.pypa.io/pip/2.7/get-pip.py; python2 get-pip.py; 
#Raspbian

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluez 5.64-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30
  Uname: Linux 5.15.0-1008-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Fri May 27 07:30:05 2022
  ImageMediaBuild: 20220419
  InterestingModules: bnep bluetooth
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb:
   Bus 001 Device 006: ID 248a:8367 Maxxter Telink Wireless Receiver
   Bus 001 Device 012: ID 1e0e:9001 Qualcomm / Option SimTech, Incorporated
   Bus 001 Device 011: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   SHELL=/bin/bash
   LANG=C.UTF-8
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 
smsc95xx.macaddr=B8:27:EB:F3:20:41 vc_mem.mem_base=0x1ec0 
vc_mem.mem_size=0x2000  console=ttyS0,115200 dwc_otg.lpm_enable=0 
console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:
   
  hciconfig:
   hci0:Type: Primary  Bus: UART
BD Address: B8:27:EB:59:8A:EB  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING 
RX bytes:865087 acl:5840 sco:0 events:4122 errors:0
TX bytes:1491451 acl:5973 sco:0 commands:314 errors:0

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


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

[Kernel-packages] [Bug 1975691] Re: Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests

[Po-Hsu Lin]

** Description changed:

  [Impact]
- test_vxlan_under_vrf.sh should not be failing anymore (except if it's a 
config related issue) with patches submitted for I-5.13 / F-oem-5.14 in bug 
1871015
+ test_vxlan_under_vrf.sh should not be failing anymore (unless it's a
+ kernel config related issue) with patches submitted for fixing this 
+ test in bug 1871015.
  
- We should remove the SAUCE patches that mark "vxlan_under_vrf" failure
- as expected failure to catch regressions in the future.
+ We should remove the SAUCE patches that mark "vxlan_under_vrf" test
+ failure as expected failure to catch regressions in the future.
  
  [Fix]
  Revert the following patches:
  * UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in non-default 
VRF an expected failure
  * UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail
  
  [Test]
- 
+ Tested with F/I/J/F-oem-5.14/J-oem-5.17.
  
  [Where problems could occur]
  Change limit to test cases, should not have any real impact to any
  kernel functions. We may see failures reported from this test in
  our SRU regression-testing report in the future, but it means we're
  doing the right thing.

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

Title:
  Remove SAUCE patches from test_vxlan_under_vrf.sh in net of
  ubuntu_kernel_selftests

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  In Progress
Status in linux-oem-5.14 source package in Focal:
  In Progress
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-oem-5.14 source package in Impish:
  Invalid
Status in linux-oem-5.17 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  In Progress
Status in linux-oem-5.14 source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  test_vxlan_under_vrf.sh should not be failing anymore (unless it's a
  kernel config related issue) with patches submitted for fixing this 
  test in bug 1871015.

  We should remove the SAUCE patches that mark "vxlan_under_vrf" test
  failure as expected failure to catch regressions in the future.

  [Fix]
  Revert the following patches:
  * UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in non-default 
VRF an expected failure
  * UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail

  [Test]
  Tested with F/I/J/F-oem-5.14/J-oem-5.17.

  [Where problems could occur]
  Change limit to test cases, should not have any real impact to any
  kernel functions. We may see failures reported from this test in
  our SRU regression-testing report in the future, but it means we're
  doing the right thing.

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


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

[Kernel-packages] [Bug 1975798] Re: [SRU][OEM-5.14/OEM-5.17/J][PATCH 0/1] Read the discovery registers for AMD_SFH

[Kleber Sacilotto de Souza]

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

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

Title:
  [SRU][OEM-5.14/OEM-5.17/J][PATCH 0/1] Read the discovery registers for
  AMD_SFH

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

Bug description:
  [Impact]
  Lenovo(Z13/Z16) advertises an orientation sensor connected to SFH.
  But actually it's not there.

  [Fix]
  Read reg of sensor discovery.

  [Test]
  Verified on hardware, it show failure and driver returned.

  [Where problems could occur]
  Low risk, it may break AMD SFH driver.

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


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

[Kernel-packages] [Bug 1975804] Re: [SRU][OEM-5.14/OEM-5.17/J][PATCH 0/2] Fix system hangs after s2idle on AMD A+A GPU

[Kleber Sacilotto de Souza]

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

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

Title:
  [SRU][OEM-5.14/OEM-5.17/J][PATCH 0/2] Fix system hangs after s2idle on
  AMD A+A GPU

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

Bug description:
  [Impact]
  System may hang after s2idle on AMD A+A GPU config due to the following
  commits:
  8b328c64c7082278c888927f00e526786eec2880 ("drm/amdgpu: don't use BACO
  for reset in S3") https://bugs.launchpad.net/bugs/1968475
  a26d80ba0d9e67ea11cbfc25618320163497d3fe ("drm/amd/pm: keep the BACO
  feature enabled for suspend") https://bugs.launchpad.net/bugs/1958371

  [Fix]
  Revert one commit and don't reset dGPU when s2idle

  [Test]
  Verified on AMD RMB, stress s2idle passed.

  [Where problems could occur]
  Low risk, it may break s2idle on AMD platform.

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


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

[Kernel-packages] [Bug 1918085] Re: Package linux-crashdump in 20.04 configures kernel cmdline crashkernel incorrectly causing lock-up on kernel dump

[Amos]

Also in 22.04

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

Title:
  Package linux-crashdump in 20.04 configures kernel cmdline crashkernel
  incorrectly causing lock-up on kernel dump

Status in linux-meta package in Ubuntu:
  Confirmed

Bug description:
  Package linux-crashdump in 20.04 configures kernel cmdline crashkernel
  incorrectly causing lock-up on kernel dump.

  It is very simple to replicate. I was testing using QEmu
  virtualisation software, where I had QEmu running a 20.04 install
  within another 20.04 install.

  Within the virtualisation install, simply install the package 
"linux-crashdump":
  $ sudo apt install linux-crashdump

  Answering Yes and Yes to the two questions asked:

   || Configuring kexec-tools ||
   |   |
   |   |
   | If you choose this option, a system reboot will trigger a restart into a  |
   | kernel loaded by kexec instead of going through the full system boot  |
   | loader process.   |
   |   |
   | Should kexec-tools handle reboots (sysvinit only)?|
   |   |
   |  |
   |   |
   |---|

   || Configuring kdump-tools ||
   |   |
   |   |
   | If you choose this option, the kdump-tools mechanism will be enabled.  A  |
   | reboot is still required in order to enable the crashkernel kernel|
   | parameter.|
   |   |
   | Should kdump-tools be enabled be default? |
   |   |
   |  |
   |   |
   |---|

  Check the kernel command-line Grub configured by package install:
  $ cat /proc/cmdline 
  BOOT_IMAGE=/vmlinuz-5.4.0-66-lowlatency root=/dev/mapper/rootlvm-rootpart ro 
crashkernel=512M-:192M

  As you can see "crashkernel=512M-:192M" is definitely a syntax error.

  Furthermore, when I test with this default configuration by forcing a crash:
  Enable dump then reboot testing with the following command:
  sudo sysctl -w kernel.sysrq=1
  Once this is done, you must become root, as just using sudo will not be 
sufficient. As the root user, you will have to issue the command echo c > 
/proc/sysrq-trigger.

  Once the "echo c > /proc/sysrq-trigger" command is issued as root, the
  virtual host being tested locks-up at 100% CPU indefinitely. Forcing
  shutdown and reboot shows no crash file in /var/crash folder however I
  can only see files "kexec_cmd" and "kdump_lock".

  To manually fix this issue I changed to "crashkernel=512M-:192M" to 
"crashkernel=384M-:512M" by editing (i.e. make the small number/larger number 
order correct):
  $ sudo vim /etc/default/grub.d/kdump-tools.cfg
  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT 
crashkernel=384M-:512M"

  After reboot and retest of the forced crash commands, the kdump works and all 
the needed files are present after self-reboot:
  $ ls /var/crash/
  202103081345  kdump_lock  kexec_cmd  
linux-image-5.4.0-66-lowlatency-202103081345.crash
  $ ls /var/crash/202103081345/
  dmesg.202103081345  dump.202103081345

  In summary the problem is that the default kernel command-line
  configured by default "crashkernel=512M-:192M" is faulty in some way
  or other and causes the kernel to lock-up at 100% CPU indefinitely
  when kdump is triggered.

  This can be manually fixed giving a workaround but future user will
  suffer until the default installation configuration is fixed.

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


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

[Kernel-packages] [Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])

[Kleber Sacilotto de Souza]

** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Changed in: linux (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-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1871015

Title:
  test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed
  (Check VM connectivity through VXLAN (underlay in the default VRF)
  [FAIL])

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-5.14 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.14 source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  Won't Fix
Status in linux-oem-5.14 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  Fix Committed
Status in linux-oem-5.14 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-5.14 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests
  will fail on 5.13 kernel with:

    # selftests: net: test_vxlan_under_vrf.sh
    # Checking HV connectivity [ OK ]
    # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]
    not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1

  Note that this test is not failing on F-oem-5.14 but it's better to
  have corresponding patches applied to reduce the maintenance cost
  in the future.

  [Fix]
  * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test
  * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case

  Only I-5.13 and F-oem-5.14 need these patches.

  First patch (e7e4785f):
    - Can be cherry-picked to Impish 5.13
    - Can be cherry-picked to F-oem-5.14.
  Second patch (b50d3b46):
    - Can be cherry-picked to Impish 5.13 (-C2 is required while
  applying it due to our SAUCE patches)
    - F-oem-5.14 has already got this one applied.

  The reason why we need the second patch is that after the first one
  got applied, we will see another failure, which we made it an expected
  failure (XFAIL) with SAUCE patches:
    Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL]

  [Test]
  With the patched test_vxlan_under_vrf.sh test, it can pass on Impish
  5.13 and F-oem-5.14 without any issue:
    Checking HV connectivity [ OK ]
    Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ]
    Check VM connectivity through VXLAN (underlay in a VRF) [ OK ]

  [Where problems could occur]
  Change limit to test cases, should not have any real impact to any
  kernel functions. But if these fixes are incorrect we will see
  failures in our regression-testing report. The worst scenario is
  getting false-negative results.

  v2: Update cover-letter content and target in patch title to make it
  easier to read.

  [Original Bug Report]
  Issue found with GCP 5.3.0-1017.18~18.04.1

   # selftests: net: test_vxlan_under_vrf.sh
   # Checking HV connectivity [ OK ]
   # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]
   not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1

  The failure is different from bug 1837348

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


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

[Kernel-packages] [Bug 1974017] Re: [UBUNTU 20.04] KVM nesting support leaks too much memory, might result in stalls during cleanup

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: In Progress => 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/1974017

Title:
  [UBUNTU 20.04] KVM nesting support leaks too much memory, might result
  in stalls during cleanup

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

Bug description:
  SRU Justification:
  ==

  [Impact]

   * If running KVM with nesting support (e.g. 'kvm.nested=1' on the kernel
 command line), the shadow page table code will produce too many entries
 in the shadow code.

   * The below mentioned upstream fix will prevent the entries from being
 piled up, by checking for existing entries at insert time.

   * This measurably reduces the list length and is faster than traversing
 the list at shutdown time only.

  [Fix]

   * a06afe8383080c630a7a528b8382fc6bb4925b61 a06afe838308
 "KVM: s390: vsie/gmap: reduce gmap_rmap overhead"

  [Test Plan]

   * A IBM zSystems or LinuxONE LPAR on a z13 or newer is needed.

   * Ubuntu focal, impish or jammy needs to be installed
 and the Ubuntu LPAR setup as (1st level) KVM host,
 allowing nested virtualization.

   * Now setup one (or more) KVM virtual machines,
 with similar Ubuntu releases,
 and define one or more of them again as (2nd level) KVM host.

   * Define several KVM virtual machines on this (2nd level) KVM host
 in a memory constraint fashion,
 so that a lot of memory mapping is caused.

   * Let such a system run for a while under load.

   * Now shutdown one (or more) 2nd level VMs and notice the
 time it takes.

   * With the patch in place this time should be considerably
 quicker than without.

   * The result is reduced mapping (gmap_rmap) overhead,
 less danger of leaking memory
 and a better responding system.

  [Where problems could occur]

   * In case wrong entries are freed up this will harm the virtual
 memory management and may even lead to crashes.

   * In case the pointer handling is not done properly,
 again crashes may occur.

   * But with net just five new lines the patch is pretty short, readable
 and the modifications traceable in arch/s390/mm/gmap.c only.

   * The changes are limited to s390/mm only,
 hence don't affect other architectures.

  [Other Info]
   
   * The commit was upstream accepted in v5.18-rc6.

   * Since the planned target kernel for kinetic is 5.19,
 the kinetic kernel does not need to be patched.

   * Hence the SRUs are for jammy, impish and focal.

  __

  KVM nesting support consumes too much memory

  When running KVM with nesting support (kvm.nested=1 on the kernel
  command line) the shadow page table code will produce too many entries
  in the shadow code.

  There is an upstream fix that will prevent the majority of the
  problem:

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

  The fix is needed for 20.04 and 22.04.

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


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

[Kernel-packages] [Bug 1974433] Re: [UBUNTU 20.04] CPU-MF: add extended counter set definitions for new IBM z16

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: In Progress => 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/1974433

Title:
  [UBUNTU 20.04] CPU-MF: add extended counter set definitions for new
  IBM z16

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

Bug description:
  SRU Justification:
  ==

  [Impact]

   * This is a hardware enablement SRU

   * and adds support for (new) IBM z16 counters

   * by exporting the extended counter set counters of the IBM z16 via
  sysfs.

  [Fix]

   * c9311de71635 c9311de71635d3eaa158df8516b9b99a92d60a0c
     "s390/cpumf: add new extended counter set for IBM z16"

  [Test Case]

   * Prepare an IBM z16 LPAR with Ubuntu 20.04, 21.10 or 22.04 (incl.
  this patch).

   * At LPARs activation profile, navigate to the Security page
     and within the counter facility options, select each counter set you want 
to use.
     (One may just select all for testing purposes.)

   * Use 'perf list' to determine if the new counters are listed.
     For comparing the new counters see:
     https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git\
     /commit/?id=c9311de71635d3eaa158df8516b9b99a92d60a0c

   * Use 'perf stat -e' to enable and make use of these counters.

  [What can go wrong]

   * Only new code is added by this commit - none is changed nor
  removed.

   * The new code may have syntactical errors,
     which would become visible during a test compile.

   * Initialization of the new struct cpumcf_z16_pmu_event_attr could be
  wrong.

   * The hex code for the counters could be wrong or mixed up,
     or the names might be wrong or mixed up,
     in which case one will get wrong or unexpected results.

   * The expansion of the case statement to determine the correct (z16) hardware
     might be wrong, using wrong case hex numbers.
     Which would lead to potentially counters,
     that may not match to the underlying hardware.

  [ Other info]

   * The commit will be upstream accepted with 5.18.
 (It's was brought upstream 'next-20220517'.)

   * Since the planned target kernel for kinetic is 5.19,
 this will be included.

   * Hence the SRU is for Focal, Impish and Jammy only.

  __

  For IBM z16 machine the extended counter set needs to be exported by the PMU 
device driver CPU MF. The upstream commit from linux-next is
  commit-id: c9311de71635 s390/cpumf: add new extended counter set for IBM z16

  The same patch will be imported into linux repo in the next merge
  window.

  Required patches are attached. They apply cleanly and compile without
  errors on focal (20.04) and jammy (22.04).

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


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

[Kernel-packages] [Bug 1974017] Re: [UBUNTU 20.04] KVM nesting support leaks too much memory, might result in stalls during cleanup

[Kleber Sacilotto de Souza]

** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

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

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

Title:
  [UBUNTU 20.04] KVM nesting support leaks too much memory, might result
  in stalls during cleanup

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Impish:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification:
  ==

  [Impact]

   * If running KVM with nesting support (e.g. 'kvm.nested=1' on the kernel
 command line), the shadow page table code will produce too many entries
 in the shadow code.

   * The below mentioned upstream fix will prevent the entries from being
 piled up, by checking for existing entries at insert time.

   * This measurably reduces the list length and is faster than traversing
 the list at shutdown time only.

  [Fix]

   * a06afe8383080c630a7a528b8382fc6bb4925b61 a06afe838308
 "KVM: s390: vsie/gmap: reduce gmap_rmap overhead"

  [Test Plan]

   * A IBM zSystems or LinuxONE LPAR on a z13 or newer is needed.

   * Ubuntu focal, impish or jammy needs to be installed
 and the Ubuntu LPAR setup as (1st level) KVM host,
 allowing nested virtualization.

   * Now setup one (or more) KVM virtual machines,
 with similar Ubuntu releases,
 and define one or more of them again as (2nd level) KVM host.

   * Define several KVM virtual machines on this (2nd level) KVM host
 in a memory constraint fashion,
 so that a lot of memory mapping is caused.

   * Let such a system run for a while under load.

   * Now shutdown one (or more) 2nd level VMs and notice the
 time it takes.

   * With the patch in place this time should be considerably
 quicker than without.

   * The result is reduced mapping (gmap_rmap) overhead,
 less danger of leaking memory
 and a better responding system.

  [Where problems could occur]

   * In case wrong entries are freed up this will harm the virtual
 memory management and may even lead to crashes.

   * In case the pointer handling is not done properly,
 again crashes may occur.

   * But with net just five new lines the patch is pretty short, readable
 and the modifications traceable in arch/s390/mm/gmap.c only.

   * The changes are limited to s390/mm only,
 hence don't affect other architectures.

  [Other Info]
   
   * The commit was upstream accepted in v5.18-rc6.

   * Since the planned target kernel for kinetic is 5.19,
 the kinetic kernel does not need to be patched.

   * Hence the SRUs are for jammy, impish and focal.

  __

  KVM nesting support consumes too much memory

  When running KVM with nesting support (kvm.nested=1 on the kernel
  command line) the shadow page table code will produce too many entries
  in the shadow code.

  There is an upstream fix that will prevent the majority of the
  problem:

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

  The fix is needed for 20.04 and 22.04.

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


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

[Kernel-packages] [Bug 1974433] Re: [UBUNTU 20.04] CPU-MF: add extended counter set definitions for new IBM z16

[Kleber Sacilotto de Souza]

** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

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

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

Title:
  [UBUNTU 20.04] CPU-MF: add extended counter set definitions for new
  IBM z16

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Impish:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification:
  ==

  [Impact]

   * This is a hardware enablement SRU

   * and adds support for (new) IBM z16 counters

   * by exporting the extended counter set counters of the IBM z16 via
  sysfs.

  [Fix]

   * c9311de71635 c9311de71635d3eaa158df8516b9b99a92d60a0c
     "s390/cpumf: add new extended counter set for IBM z16"

  [Test Case]

   * Prepare an IBM z16 LPAR with Ubuntu 20.04, 21.10 or 22.04 (incl.
  this patch).

   * At LPARs activation profile, navigate to the Security page
     and within the counter facility options, select each counter set you want 
to use.
     (One may just select all for testing purposes.)

   * Use 'perf list' to determine if the new counters are listed.
     For comparing the new counters see:
     https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git\
     /commit/?id=c9311de71635d3eaa158df8516b9b99a92d60a0c

   * Use 'perf stat -e' to enable and make use of these counters.

  [What can go wrong]

   * Only new code is added by this commit - none is changed nor
  removed.

   * The new code may have syntactical errors,
     which would become visible during a test compile.

   * Initialization of the new struct cpumcf_z16_pmu_event_attr could be
  wrong.

   * The hex code for the counters could be wrong or mixed up,
     or the names might be wrong or mixed up,
     in which case one will get wrong or unexpected results.

   * The expansion of the case statement to determine the correct (z16) hardware
     might be wrong, using wrong case hex numbers.
     Which would lead to potentially counters,
     that may not match to the underlying hardware.

  [ Other info]

   * The commit will be upstream accepted with 5.18.
 (It's was brought upstream 'next-20220517'.)

   * Since the planned target kernel for kinetic is 5.19,
 this will be included.

   * Hence the SRU is for Focal, Impish and Jammy only.

  __

  For IBM z16 machine the extended counter set needs to be exported by the PMU 
device driver CPU MF. The upstream commit from linux-next is
  commit-id: c9311de71635 s390/cpumf: add new extended counter set for IBM z16

  The same patch will be imported into linux repo in the next merge
  window.

  Required patches are attached. They apply cleanly and compile without
  errors on focal (20.04) and jammy (22.04).

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


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

[Kernel-packages] [Bug 1968096] Re: [UBUNTU 20.04] Null Pointer issue in nfs code running Ubuntu on IBM Z

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: In Progress => 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/1968096

Title:
  [UBUNTU 20.04] Null Pointer issue in nfs code running Ubuntu on IBM Z

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

Bug description:
  SRU Justification:
  ==

  [Impact]

  * The kernel crashed under load with a null pointer issue in nfs code:
  [556585.270959] Krnl Code:#:  illegal
    >0002:  illegal
     0004:  illegal
     0006:  illegal
     0008:  illegal
     000a:  illegal
     000c:  illegal
     000e:  illegal
  [556585.270967] Call Trace:
  [556585.270982] ([<03ff80d6fb1a>] rpcauth_lookup_credcache+0x5a/0x300 
[sunrpc])
  [556585.270993] [<03ff80e1182c>] nfs_ctx_key_to_expire+0xec/0x130 
[nfs]
  [556585.271004] [<03ff80e1189c>] nfs_key_timeout_notify+0x2c/0x70 
[nfs]
  [556585.271014] [<03ff80dfdf7e>] nfs_file_write+0x3e/0x320 [nfs]
  [556585.271016] [<0028165944a8>] new_sync_write+0x118/0x1b0
  [556585.271017] [<002816594ee0>] vfs_write+0xb0/0x1b0
  [556585.271019] [<002816596a1e>] ksys_pwrite64+0x7e/0xc0
  [556585.271021] [<002816bb26b2>] system_call+0x2a6/0x2c8

  * Several dumps were generated and shared with Canonical.

  * Analysis (done by kernel and SEG) point to refcount leaks fixed,
    that are already fixed in the following commit/fix:

  [Fix]

  * ca05cbae2a0468e5d78e9b4605936a8bf5da328b ca05cbae2a04 "NFS: Fix up
  nfs_ctx_key_to_expire()"

  [Test Case]

  * There is unfortunately no reproducer or trigger available for this
  issue.

  * It just happens now and then under higher load.

  * Patched test kernels (focal 5.4 and bionic 5.4-hwe) were created and
    ran for more than a week in a special staging environment (at IBM)
    without further crashes.

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

  [Where problems could occur]

  * The inode handling can become broken, in case the changes
    on the pointers are erroneous.

  * Problems with the authentication and/or the credentials could occur
    due to the modifications in put_rpccred, rpc_cred and rpc_auth.

  * The expiration of the cached credentials could be harmed as well,
    due to the changes in nfs_ctx_key_to_expire.

  * The different pointer arithmetic may cause further issues - wrong
    or null pointer references.

  * Positive is that the original commit was brought upstream by nfs
  experts.

  * A patched test kernel sustained day long runs under load in a staging
    and test environment.

  * The author of the upstream commit/patch is well known in the NFS
  area.

  [Other]

  * The Salesforce Case Number 00334334 is associated with this bug.

  * Commit ca05cbae2a04 was upstream accepted with 5.16-rc1.

  * But commit ca05cbae2a04 was unfortunately not tagged as stable,
    hence it was not picked automatically.

  * Since kinetic's (22.10) target kernel is 5.18,
    it will have the patch included,
    hence no dedicated PATCH request for kinetic.

  __

  State the component where the Bug is occurring:
    kernel

  Indicate the nature of the problem by answering the below questions:
  - Is this problem reproducible?   No
  No, steps unknown, but we have seen these before

  - Is the system sitting at a debugger (kdb, or xmon)?   No

  - Is the system hung? No
  No, dumped and rebooted

  - Are there any custom patches installed? Yes
  On base system level (CloudAppliance) we are still running with the zfpc_proc 
module loaded. But no recent changes in the module and is running absolutely 
stable in HA (same kernel and userspace, Ubuntu 20.04 LTS)

  - Is there any special hardware that may be relevant to this problem? 
Yes
  We are running with mlx (cloud network adapters) installed.

  - Is access information for the machine the problem was found on
  available? Yes

  - Is the bug occuring in a userspace application?   No

  - Was a stack trace produced? Yes
  This is what mention in first comment by @Boris Barth

  - Did the system produce an Oops message on the console?  Yes
  [556585.270902] illegal operation: 0001 ilc:1 [#10] SMP
  [556585.270905] Modules linked in: vhost_net macvtap macvlan tap 
rpcsec_gss_krb5 auth_rpcgss nfsv3 nfs_acl nfs lockd grace 

[Kernel-packages] [Bug 1968096] Re: [UBUNTU 20.04] Null Pointer issue in nfs code running Ubuntu on IBM Z

[Kleber Sacilotto de Souza]

** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

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

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

Title:
  [UBUNTU 20.04] Null Pointer issue in nfs code running Ubuntu on IBM Z

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

Bug description:
  SRU Justification:
  ==

  [Impact]

  * The kernel crashed under load with a null pointer issue in nfs code:
  [556585.270959] Krnl Code:#:  illegal
    >0002:  illegal
     0004:  illegal
     0006:  illegal
     0008:  illegal
     000a:  illegal
     000c:  illegal
     000e:  illegal
  [556585.270967] Call Trace:
  [556585.270982] ([<03ff80d6fb1a>] rpcauth_lookup_credcache+0x5a/0x300 
[sunrpc])
  [556585.270993] [<03ff80e1182c>] nfs_ctx_key_to_expire+0xec/0x130 
[nfs]
  [556585.271004] [<03ff80e1189c>] nfs_key_timeout_notify+0x2c/0x70 
[nfs]
  [556585.271014] [<03ff80dfdf7e>] nfs_file_write+0x3e/0x320 [nfs]
  [556585.271016] [<0028165944a8>] new_sync_write+0x118/0x1b0
  [556585.271017] [<002816594ee0>] vfs_write+0xb0/0x1b0
  [556585.271019] [<002816596a1e>] ksys_pwrite64+0x7e/0xc0
  [556585.271021] [<002816bb26b2>] system_call+0x2a6/0x2c8

  * Several dumps were generated and shared with Canonical.

  * Analysis (done by kernel and SEG) point to refcount leaks fixed,
    that are already fixed in the following commit/fix:

  [Fix]

  * ca05cbae2a0468e5d78e9b4605936a8bf5da328b ca05cbae2a04 "NFS: Fix up
  nfs_ctx_key_to_expire()"

  [Test Case]

  * There is unfortunately no reproducer or trigger available for this
  issue.

  * It just happens now and then under higher load.

  * Patched test kernels (focal 5.4 and bionic 5.4-hwe) were created and
    ran for more than a week in a special staging environment (at IBM)
    without further crashes.

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

  [Where problems could occur]

  * The inode handling can become broken, in case the changes
    on the pointers are erroneous.

  * Problems with the authentication and/or the credentials could occur
    due to the modifications in put_rpccred, rpc_cred and rpc_auth.

  * The expiration of the cached credentials could be harmed as well,
    due to the changes in nfs_ctx_key_to_expire.

  * The different pointer arithmetic may cause further issues - wrong
    or null pointer references.

  * Positive is that the original commit was brought upstream by nfs
  experts.

  * A patched test kernel sustained day long runs under load in a staging
    and test environment.

  * The author of the upstream commit/patch is well known in the NFS
  area.

  [Other]

  * The Salesforce Case Number 00334334 is associated with this bug.

  * Commit ca05cbae2a04 was upstream accepted with 5.16-rc1.

  * But commit ca05cbae2a04 was unfortunately not tagged as stable,
    hence it was not picked automatically.

  * Since kinetic's (22.10) target kernel is 5.18,
    it will have the patch included,
    hence no dedicated PATCH request for kinetic.

  __

  State the component where the Bug is occurring:
    kernel

  Indicate the nature of the problem by answering the below questions:
  - Is this problem reproducible?   No
  No, steps unknown, but we have seen these before

  - Is the system sitting at a debugger (kdb, or xmon)?   No

  - Is the system hung? No
  No, dumped and rebooted

  - Are there any custom patches installed? Yes
  On base system level (CloudAppliance) we are still running with the zfpc_proc 
module loaded. But no recent changes in the module and is running absolutely 
stable in HA (same kernel and userspace, Ubuntu 20.04 LTS)

  - Is there any special hardware that may be relevant to this problem? 
Yes
  We are running with mlx (cloud network adapters) installed.

  - Is access information for the machine the problem was found on
  available? Yes

  - Is the bug occuring in a userspace application?   No

  - Was a stack trace produced? Yes
  This is what mention in first comment by @Boris Barth

  - Did the system produce an Oops message on the console?  Yes
  [556585.270902] 

[Kernel-packages] [Bug 1971417] Re: Fix REG_WAIT timeout for Yellow Carp

[Kleber Sacilotto de Souza]

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

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

Title:
  Fix REG_WAIT timeout for Yellow Carp

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

Bug description:
  [Impact]
  During hotplug built-in hdmi, the error message show up.
  #REG_WAIT timeout for yellow Carp

  [Fix]
  This tends to take miliseconds in certain scenarios and we'd rather not
  wait that long. Due to how this interacts with det size update and
  locking waiting should not be necessary as compbuf updates before
  unlock.

  Add a watch for config error instead as that is something we actually do
  care about.

  [Test Case]
  1. Plug and unplug hdmi
  2. cant get the error message in dmesg.

  [Where problems could occur]
  Low

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


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

[Kernel-packages] [Bug 1969326] Re: Enable hotspot feature for Realtek 8821CE

[Kleber Sacilotto de Souza]

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

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

Title:
  Enable hotspot feature for Realtek 8821CE

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

Bug description:
  [Impact]
  The wifi hotspot doesn't work without the fix.

  [Fix]
  Realtek provides us the patches to add this feature which are still in 
linux-next.
  
https://patchwork.kernel.org/project/linux-wireless/cover/20220407095858.46807-1-pks...@realtek.com/
  ece31c93d4d6 rtw88: 8821c: fix debugfs rssi value
  f5207c122102 rtw88: do PHY calibration while starting AP
  f1c4dabfe68d rtw88: 8821c: Enable TX report for management frames
  f2217968ffda rtw88: Add update beacon flow for AP mode
  6723c0cde84f rtw88: fix incorrect frequency reported
  c1edc86472fc rtw88: add ieee80211:sta_rc_update ops

  Realtek provides us another series of patches for 5.14, and it
  contains 5 commits, we'd verified this series of patches.

  [Test]
  Verified on the Realtek 8821CE card.

  [Where problems could occur]
  The patches are introducing new interfaces, I think it only has minimal 
impact to the origin behaviors.

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


-- 
Mailing list: https://launchpad.net/~kernel-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

[Kevin Peter Gade]

Yes - Disabling Secureboot worked in order to get acpidbg working
(killed my touchpad mouse however that is another topic).

Output from both commands here:

$ sudo acpidbg -b 'ex \_SB_.PCI0.LPCB.EC0_.BATD'
Evaluating \_SB_.PCI0.LPCB.EC0_.BATD
Evaluation of \_SB_.PCI0.LPCB.EC0_.BATD returned object a3ce38e0, 
external buffer length 18
 [Integer] = 

$ sudo acpidbg -b 'ex \_SB_.BAT1._STA'
Evaluating \_SB_.BAT1._STA
Evaluation of \_SB_.BAT1._STA returned object cb8c88ff, external buffer 
length 18
 [Integer] = 000F

-- 
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 1971699] Re: disable Intel DMA remapping by default

[Kleber Sacilotto de Souza]

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

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

Title:
  disable Intel DMA remapping by default

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

Bug description:
  [Impact]

  It seems that enabling Intel IOMMU can cause some weird gfx problems, see for 
example:
  
   https://bugs.launchpad.net/bugs/1971146
   https://bugs.launchpad.net/bugs/1965882

  [Test case]

  We don't have any specific test case, only other bug reports that
  tracked down the origin of the issue as being introduced when
  CONFIG_INTEL_IOMMU_DEFAULT_ON has been enabled by default.

  [Fix]

  Revert "UBUNTU: [Config] enable Intel DMA remapping options by
  default"

  [Regression potential]

  DMA remapping device not present at boot by default, users that
  require this feature will need to specifically add intel_iommu=on to
  the kernel boot parameters to enable it.

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


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

[Kernel-packages] [Bug 1973620] Re: prevent kernel panic with overlayfs + shiftfs

[Kleber Sacilotto de Souza]

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

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

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

Title:
  prevent kernel panic with overlayfs + shiftfs

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Impish:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Incomplete

Bug description:
  [Impact]

  The patch that we have recently re-introduced to properly support
  overlayfs on top of shiftfs can introduce potential kernel panics, for
  example:

  BUG: kernel NULL pointer dereference, address: 0008
  [  447.039738] #PF: supervisor read access in kernel mode
  [  447.040369] #PF: error_code(0x) - not-present page
  [  447.041002] PGD 0 P4D 0
  [  447.041325] Oops:  [#1] SMP NOPTI
  [  447.041798] CPU: 0 PID: 73766 Comm: sudo Not tainted 5.15.0-28-generic 
#29~20.04.1-Ubuntu
  [  447.042800] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 
Ubuntu-1.8.2-1ubuntu1+esm1 04/01/2014
  [  447.043979] RIP: 0010:aa_file_perm+0x3a/0x470
  [  447.044565] Code: 54 53 48 83 ec 68 48 89 7d 80 89 4d 8c 65 48 8b 04 
25 28 00 00 00 48 89 45 d0 31 c0 48 63 05 01 0a 19 01 48 03 82 c0 00 00 00 <4c> 
8b 68 08 f6 46 40 02 0f 85 d0 00 00 00 41 f6 45 40 02 0f 85 c5
  [  447.046837] RSP: 0018:aefe80a4bca8 EFLAGS: 00010246
  [  447.047481] RAX:  RBX: 96e4038abd01 RCX: 
0004
  [  447.048351] RDX: 96e4038abd00 RSI: 96e401215eb8 RDI: 
9c22a2ac
  [  447.049241] RBP: aefe80a4bd38 R08:  R09: 

  [  447.050121] R10:  R11:  R12: 
96e401215eb8
  [  447.051040] R13: 96e4038abd00 R14: 9c22a2ac R15: 
0004
  [  447.051942] FS:  7eff3c0f8c80() GS:96e45e40() 
knlGS:
  [  447.052981] CS:  0010 DS:  ES:  CR0: 80050033
  [  447.053696] CR2: 0008 CR3: 02be2000 CR4: 
003506f0
  [  447.054571] Call Trace:
  [  447.054883]  
  [  447.055154]  ? unlock_page_memcg+0x2f/0x40
  [  447.055668]  ? page_remove_rmap+0x4b/0x320
  [  447.056180]  common_file_perm+0x72/0x170
  [  447.056669]  apparmor_file_permission+0x1c/0x20
  [  447.057237]  security_file_permission+0x30/0x1a0
  [  447.057898]  rw_verify_area+0x35/0x60
  [  447.058392]  vfs_read+0x6d/0x1a0
  [  447.058842]  ksys_read+0xb1/0xe0
  [  447.059276]  __x64_sys_read+0x1a/0x20
  [  447.059732]  do_syscall_64+0x5c/0xc0
  [  447.060183]  ? __set_current_blocked+0x3b/0x60
  [  447.060738]  ? exit_to_user_mode_prepare+0x3d/0x1c0
  [  447.061434]  ? syscall_exit_to_user_mode+0x27/0x50
  [  447.062099]  ? do_syscall_64+0x69/0xc0
  [  447.062603]  ? irqentry_exit_to_user_mode+0x9/0x20
  [  447.063210]  ? irqentry_exit+0x19/0x30
  [  447.063678]  ? exc_page_fault+0x89/0x160
  [  447.064165]  ? asm_exc_page_fault+0x8/0x30
  [  447.064675]  entry_SYSCALL_64_after_hwframe+0x44/0xae
  [  447.065298] RIP: 0033:0x7eff3c2cb002

  [Test case]

  It is really easy to trigger this specific kernel panic running the
  lxc autopackage test.

  [Fix]

  This bug happens because we don't need to decrement anymore the
  refcount for the previous vm_file value in ovl_vm_prfile_set(). So the
  fix simply consists of removing the unnecessary fput().

  [Regression potential]

  This patch affects only overlayfs (only when AUFS is enabled), so we
  may see regressions in overlayfs in kernels that have AUFS enabled
  (focal hwe and cloud kernels).

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


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

[Kernel-packages] [Bug 1975908] [NEW] Ayant migré de l'os raspberrypi OS à Ubuntu pour des problèmes similaire : le bluetooth ne suit pas le rythme (perte de connexion au smartphone, reste connecté,

[raspb]

Public bug reported:

https://bugs.launchpad.net/ubuntu/+source/bluez/+filebug/f53f77f8-dd8e-11ec-a167-40a8f03099c8?

Ayant migré de l'os raspberrypi OS à Ubuntu pour des problèmes similaire
:  le bluetooth ne suit pas le rythme (perte de connexion au smartphone,
reste connecté, garde l'adresse IP assigné alors que inutilisable),
c'est Titanic la wifi saute aléatoirement, le modem GSM officielle cablé
sur le hat usb officielle  (4 port) semble subir des crash (device
disconnected, connected,  dwc2_hc_chhltd_intr_dma: Channel 3 - ChHltd
set, but reason is + wwan0: Cannot change a running device +
dwc2_update_urb_state_abn(): trimming xfer length || hci0: killing
stalled connection 7e:c8:46:a6:57:22 +  hci0: link tx timeout ||


dependence

 Network Bluetooth 
bluetoothctl system-alias Xorg #Changer de Nom
bluetoothctl pairable on;
bluetoothctl discoverable on;
timeout 20s bluetoothctl scan on &
bluetoothctl pair [Mac Address];
apt -y install libdbus-1-3 libdbus-1-dev libglib2.0-dev python2 python-pip; #Ub
pip2 install dbus-python; 
bt-pan client -r [Mac Address];
((bt-pan est requis))

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-1008-raspi 5.15.0-1008.8
ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30
Uname: Linux 5.15.0-1008-raspi aarch64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: arm64
CasperMD5CheckResult: unknown
Date: Fri May 27 07:28:26 2022
ImageMediaBuild: 20220419
ProcEnviron:
 SHELL=/bin/bash
 LANG=C.UTF-8
 TERM=xterm-256color
 PATH=(custom, no user)
SourcePackage: linux-raspi
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug arm64 arm64-image jammy raspi-image uec-images

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

Title:
  Ayant migré de l'os raspberrypi OS à Ubuntu pour des problèmes
  similaire :  le bluetooth ne suit pas le rythme (perte de connexion au
  smartphone, reste connecté, garde l'adresse IP assigné alors que
  inutilisable), c'est Titanic la wifi saute aléatoirement, le modem GSM
  officielle cablé sur le hat usb officielle  (4 port) semble subir des
  crash (device disconnected, connected,  dwc2_hc_chhltd_intr_dma:
  Channel 3 - ChHltd set, but reason is + wwan0: Cannot change a running
  device + dwc2_update_urb_state_abn(): trimming xfer length || hci0:
  killing stalled connection 7e:c8:46:a6:57:22 +  hci0: link tx timeout
  ||

Status in linux-raspi package in Ubuntu:
  New

Bug description:
  
https://bugs.launchpad.net/ubuntu/+source/bluez/+filebug/f53f77f8-dd8e-11ec-a167-40a8f03099c8?

  Ayant migré de l'os raspberrypi OS à Ubuntu pour des problèmes
  similaire :  le bluetooth ne suit pas le rythme (perte de connexion au
  smartphone, reste connecté, garde l'adresse IP assigné alors que
  inutilisable), c'est Titanic la wifi saute aléatoirement, le modem GSM
  officielle cablé sur le hat usb officielle  (4 port) semble subir des
  crash (device disconnected, connected,  dwc2_hc_chhltd_intr_dma:
  Channel 3 - ChHltd set, but reason is + wwan0: Cannot change a running
  device + dwc2_update_urb_state_abn(): trimming xfer length || hci0:
  killing stalled connection 7e:c8:46:a6:57:22 +  hci0: link tx timeout
  ||

  
  dependence

   Network Bluetooth 
  bluetoothctl system-alias Xorg #Changer de Nom
  bluetoothctl pairable on;
  bluetoothctl discoverable on;
  timeout 20s bluetoothctl scan on &
  bluetoothctl pair [Mac Address];
  apt -y install libdbus-1-3 libdbus-1-dev libglib2.0-dev python2 python-pip; 
#Ub
  pip2 install dbus-python; 
  bt-pan client -r [Mac Address];
  ((bt-pan est requis))

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-1008-raspi 5.15.0-1008.8
  ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30
  Uname: Linux 5.15.0-1008-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Fri May 27 07:28:26 2022
  ImageMediaBuild: 20220419
  ProcEnviron:
   SHELL=/bin/bash
   LANG=C.UTF-8
   TERM=xterm-256color
   PATH=(custom, no user)
  SourcePackage: linux-raspi
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1975909] [NEW] le bluetooth ne suit pas le rythme (perte de connexion au smartphone, reste connecté, garde l'adresse IP assigné alors que inutilisable), le bluetooth c'est Titan

[raspb]

Public bug reported:

 Network Bluetooth 
bluetoothctl system-alias Xorg #Changer de Nom
bluetoothctl pairable on;
bluetoothctl discoverable on;
timeout 20s bluetoothctl scan on &
bluetoothctl pair [Mac Address];
apt -y install libdbus-1-3 libdbus-1-dev libglib2.0-dev python2 python-pip; #Ub
pip2 install dbus-python; 
bt-pan client -r [Mac Address];
((bt-pan est requis))

apt -y install libdbus-1-3 libdbus-1-dev libglib2.0-dev python-dev; #Raspbian
wget https://bootstrap.pypa.io/pip/2.7/get-pip.py; python2 get-pip.py; #Raspbian

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: bluez 5.64-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30
Uname: Linux 5.15.0-1008-raspi aarch64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: arm64
CasperMD5CheckResult: unknown
Date: Fri May 27 07:30:05 2022
ImageMediaBuild: 20220419
InterestingModules: bnep bluetooth
Lspci:
 
Lspci-vt: -[:00]-
Lsusb:
 Bus 001 Device 006: ID 248a:8367 Maxxter Telink Wireless Receiver
 Bus 001 Device 012: ID 1e0e:9001 Qualcomm / Option SimTech, Incorporated
 Bus 001 Device 011: ID 1a40:0101 Terminus Technology Inc. Hub
 Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ProcEnviron:
 SHELL=/bin/bash
 LANG=C.UTF-8
 TERM=xterm-256color
 PATH=(custom, no user)
ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 
smsc95xx.macaddr=B8:27:EB:F3:20:41 vc_mem.mem_base=0x1ec0 
vc_mem.mem_size=0x2000  console=ttyS0,115200 dwc_otg.lpm_enable=0 
console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
 
hciconfig:
 hci0:  Type: Primary  Bus: UART
BD Address: B8:27:EB:59:8A:EB  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING 
RX bytes:865087 acl:5840 sco:0 events:4122 errors:0
TX bytes:1491451 acl:5973 sco:0 commands:314 errors:0

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


** Tags: apport-bug arm64 arm64-image jammy raspi-image uec-images

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

Title:
  le bluetooth ne suit pas le rythme (perte de connexion au smartphone,
  reste connecté, garde l'adresse IP assigné alors que inutilisable), le
  bluetooth c'est Titanic  et petite anecdote c'est pareil sur raspberry
  pi OS ; )

Status in bluez package in Ubuntu:
  New

Bug description:
   Network Bluetooth 
  bluetoothctl system-alias Xorg #Changer de Nom
  bluetoothctl pairable on;
  bluetoothctl discoverable on;
  timeout 20s bluetoothctl scan on &
  bluetoothctl pair [Mac Address];
  apt -y install libdbus-1-3 libdbus-1-dev libglib2.0-dev python2 python-pip; 
#Ub
  pip2 install dbus-python; 
  bt-pan client -r [Mac Address];
  ((bt-pan est requis))

  apt -y install libdbus-1-3 libdbus-1-dev libglib2.0-dev python-dev; #Raspbian
  wget https://bootstrap.pypa.io/pip/2.7/get-pip.py; python2 get-pip.py; 
#Raspbian

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluez 5.64-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30
  Uname: Linux 5.15.0-1008-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Fri May 27 07:30:05 2022
  ImageMediaBuild: 20220419
  InterestingModules: bnep bluetooth
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb:
   Bus 001 Device 006: ID 248a:8367 Maxxter Telink Wireless Receiver
   Bus 001 Device 012: ID 1e0e:9001 Qualcomm / Option SimTech, Incorporated
   Bus 001 Device 011: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   SHELL=/bin/bash
   LANG=C.UTF-8
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 
smsc95xx.macaddr=B8:27:EB:F3:20:41 vc_mem.mem_base=0x1ec0 
vc_mem.mem_size=0x2000  console=ttyS0,115200 dwc_otg.lpm_enable=0 
console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:
   
  hciconfig:
   hci0:Type: Primary  Bus: UART
BD Address: B8:27:EB:59:8A:EB  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING 
RX bytes:865087 acl:5840 sco:0 events:4122 errors:0
TX bytes:1491451 acl:5973 sco:0 commands:314 errors:0

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1973839] Re: 5.15.0-30-generic : SSBD mitigation results in "unchecked MSR access error: WRMSR to 0x48 (tried to write 0x0000000000000004)" and flood of kernel traces in some cl

[Ian Wienand]

> Which cloud is in use and what the instance type is?

This was seen on OVH.  I don't think it's a public instance type.  I
have attached the cpuid of the affected guest
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973839/+attachment/5590542/+files/cpuid)
but unfortunately I don't details about what is happening behind KVM

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

Title:
  5.15.0-30-generic :  SSBD mitigation results in "unchecked MSR access
  error: WRMSR to 0x48 (tried to write 0x0004)" and flood of
  kernel traces in some cloud providers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When booting this in one of our clouds, we see an error early in the
  kernel output

kernel: unchecked MSR access error: WRMSR to 0x48 (tried to write
  0x0004) at rIP: 0xabc90af4
  (native_write_msr+0x4/0x20)

  and then an un-ending stream of "bare" tracebacks; which I think must
  be related

  [2.285717] kernel: Call Trace:
  [2.285722] kernel:  
  [2.285723] kernel:  ? speculation_ctrl_update+0x95/0x200
  [2.292001] kernel:  speculation_ctrl_update_current+0x1f/0x30
  [2.292011] kernel:  ssb_prctl_set+0x92/0xe0
  [2.292016] kernel:  arch_seccomp_spec_mitigate+0x62/0x70
  [2.292019] kernel:  seccomp_set_mode_filter+0x4de/0x530
  [2.292024] kernel:  do_seccomp+0x37/0x1f0
  [2.292026] kernel:  __x64_sys_seccomp+0x18/0x20
  [2.292028] kernel:  do_syscall_64+0x5c/0xc0
  [2.292035] kernel:  ? handle_mm_fault+0xd8/0x2c0
  [2.299617] kernel:  ? do_user_addr_fault+0x1e3/0x670
  [2.312878] kernel:  ? exit_to_user_mode_prepare+0x37/0xb0
  [2.312894] kernel:  ? irqentry_exit_to_user_mode+0x9/0x20
  [2.312905] kernel:  ? irqentry_exit+0x19/0x30
  [2.312907] kernel:  ? exc_page_fault+0x89/0x160
  [2.312909] kernel:  ? asm_exc_page_fault+0x8/0x30
  [2.312914] kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xae
  [2.312919] kernel: RIP: 0033:0x7fcffd6eaa3d
  [2.312924] kernel: Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e 
fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 
<48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48
  [2.312926] kernel: RSP: 002b:7ffe352e2938 EFLAGS: 0246 ORIG_RAX: 
013d
  [2.312930] kernel: RAX: ffda RBX: 557d99d0c0c0 RCX: 
7fcffd6eaa3d
  [2.319941] systemd[1]: Starting Load Kernel Module configfs...
  [2.320103] kernel: RDX: 557d99c01290 RSI:  RDI: 
0001
  [2.339938] kernel: RBP:  R08: 0001 R09: 
557d99c01290
  [2.339941] kernel: R10: 0001 R11: 0246 R12: 

  [2.339942] kernel: R13: 0001 R14: 557d99c01290 R15: 
0001
  [2.339947] kernel:  

  We never see any more warnings or context for the tracebacks, but they
  just keep coming over and over, filling up the logs.  This is with a
  jammy x86_64 system running 5.15.0-30-generic

  Unfortunately I don't exactly know what is behind it on the cloud
  side.

  There seem to be several bugs that are similar but not exactly the
  same

  https://bugzilla.redhat.com/show_bug.cgi?id=1808996
  https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921880

  The gist seems to be that 0x4 refers to SSBD mitigation and something
  about the combo of some versions of qemu and a Jammy guest kernel make
  the guest unhappy.  I will attach cpuid info for the guest.

  I installed the 5.17 kernel from the mainline repository, and this
  appears to go away.  I will attempt to bisect it to something more
  specific.

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


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

[Kernel-packages] [Bug 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen

[Jerome Pansanel]

It affects to:
Kubuntu 18.04, Dell Latitude 7490.
I could start by blacklisting the intel-lpss-pci module (in this case the mouse 
doesn't work) and loading it again after boot (the mouse works again fine).

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

Title:
  linux-image-4.15.0-177-generic freezes on the welcome screen

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

Bug description:
  After updating to linux-image-4.15.0-177-generic, my machine
  completely freezes on the Ubuntu Welcome screen, i.e. right after
  switching to GUI mode. The mouse pointer is frozen, the keyboard does
  not even respond to CAPS LOCK or NUM LOCK, pressing CTRL+ALT+F2 shows
  no reaction.

  I cannot work with my machine at this point and have to hard reset it.

  Selecting advanced boot options in grub and selecting the previous
  linux kernel 4.15.0-176 makes it work again. So this bad bug was
  introduced with the 4.15.0-177 kernel release.

  I tried removing the nvidia-driver-510 package, presumably making
  Ubuntu use the "nouveau" driver, and with that, I could use the
  welcome screen and log in, but the machine still froze shortly
  afterwards.

  So maybe this is some sort of interference with my GeForce 1080
  graphics card, but it is not specific to the driver used.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-177-generic:amd64 4.15.0-177.186
  ProcVersionSignature: Ubuntu 4.15.0-176.185-generic 4.15.18
  Uname: Linux 4.15.0-176-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 2082 F pulseaudio
   /dev/snd/controlC0:  robert 2082 F pulseaudio
   /dev/snd/controlC2:  robert 2082 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu May 12 13:36:28 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-10-29 (2386 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Supermicro Super Server
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-176-generic 
root=UUID=7c296e4d-0189-43a0-aef8-7d536b98a536 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-176-generic N/A
   linux-backports-modules-4.15.0-176-generic  N/A
   linux-firmware  1.173.21
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2019-07-29 (1017 days ago)
  dmi.bios.date: 09/18/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X11SAE
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd09/18/2020:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SAE:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Super Server
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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


-- 
Mailing list: https://launchpad.net/~kernel-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

[Kai-Heng Feng]

Right, I think Secureboot needs to be disabled in order to use acpidbg.

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

[Kevin Peter Gade]

Unfortunately I get an "Operation not permitted" error when running sudo
acpidbg -b 'ex \_SB_.BAT1._STA' as well.

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