date:20230410

You have been subscribed to a public bug:

When logged into a desktop session, I created a new user account and
then tried to "switch to" it. A new gnome session started for that user
(test1), but after a few seconds, gnome-shell appears to have crashed.
This only seems to happen on the first attempt to "switch to" a new
user.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87
Uname: Linux 5.15.0-69-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.gpu2: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.gpu3: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file.
.proc.driver.nvidia.gpus..08.00.0: Error: path was not a regular file.
.proc.driver.nvidia.gpus..0e.00.0: Error: path was not a regular file.
.proc.driver.nvidia.gpus..0f.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  525.89.02  Wed Feb  1 23:23:25 
UTC 2023
 GCC version:
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Wed Apr  5 17:23:28 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
MachineType: NVIDIA DGX Station
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic 
root=UUID=88df95a6-4fd9-475a-8b59-ad14df1ada5a ro
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/27/2018
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0406
dmi.board.asset.tag: Default string
dmi.board.name: X99-E-10G WS
dmi.board.vendor: EMPTY
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: EMPTY
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0406:bd08/27/2018:br5.11:svnNVIDIA:pnDGXStation:pvrSystemVersion:rvnEMPTY:rnX99-E-10GWS:rvrRev1.xx:cvnEMPTY:ct3:cvrDefaultstring:sku920-22587-2510-000:
dmi.product.family: DGX
dmi.product.name: DGX Station
dmi.product.sku: 920-22587-2510-000
dmi.product.version: System Version
dmi.sys.vendor: NVIDIA
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug crash jammy ubuntu uec-images
-- 
gnome-shell crashes after "switching to" a new user from an existing login
https://bugs.launchpad.net/bugs/2015386
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to nvidia-graphics-drivers-525 in Ubuntu.

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

[Kernel-packages] [Bug 2006453] Re: Fix selftests/ftracetests/Meta-selftests

This bug is awaiting verification that the linux-oem-6.1/6.1.0-1009.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 removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-oem-6.1 verification-needed-jammy

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

Title:
  Fix selftests/ftracetests/Meta-selftests

Status in ubuntu-kernel-tests:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem-6.1 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-6.1 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [SRU Justification]

  == Impact ==
  This subtest checks for bashisms in the test scripts of ftracetests. A recent 
stable change added such a case. This is harmless but causes the Meta-selftests 
to fail. The offending commit is "selftests/ftrace: event_triggers: wait longer 
for test_event_enable" which adds:
  +   if [ "$e" == $val ]; then

  == Fix ==
  Replace the test with
  +   if [ "$e" = $val ]; then

  == Testcase ==
  Running the kernel selftests/ftracetest (done in ADT and RT) should no longer 
show "Meta-selftests" as FAILed.

  == Regression Potential ==
  This affects only the selftest suite and only ftrace subtests. Any change 
would only be observable there.

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


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

[Kernel-packages] [Bug 2009024] Re: Fail to output sound to external monitor which connects via docking station

This bug is awaiting verification that the linux-oem-6.1/6.1.0-1009.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 removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-oem-6.1 verification-needed-jammy

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

Title:
  Fail to output sound to external monitor which connects via docking
  station

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

Bug description:
  [Impact]
  No sound output from the external monitor which connect via some docking 
station. It only happens when user boot the system with docking station 
connected. Re-plug the docking station can fix this issue. Or plug the docking 
station later won't trigger this problem.

  [Fix]
  Turn on the CONFIG_SND_HDA_INTEL_HDMI_SILENT in kernel config. It will start 
sending an "audio keepalive" to the monitor as soon as it is connected.

  [Test]
  Connect the external monitor to the Atomic Type-C Dock (HD22Q) and boot the 
system with the dock connected. Play sound via HDMI/DP port and check if 
there's any audio output from the external monitor.

  [Where problems could occur]
  It sends the "audio keepalive"(silent stream) to the monitor when connected. 
Doesn't affect original workflow of the audio system.

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


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

[Kernel-packages] [Bug 2009164] Re: Fix screen that remains blank forever after it gets locked

This bug is awaiting verification that the linux-oem-6.1/6.1.0-1009.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: kernel-spammed-jammy-linux-oem-6.1 verification-needed-jammy

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

Title:
  Fix screen that remains blank forever after it gets locked

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

Bug description:
  [Impact]
  Once screen is locked under gnome-shell, the screen never wakes up and
  remains in blank forever.

  [Fix]
  "drm/i915: Create resized LUTs for ivb+ split gamma mode" makes gamma
  LUT operations in atomic context, so userspace can no longer misuse libdrm.

  "drm/i915: Rework legacy LUT handling" starts to use the reworked gamma
  LUT.

  Pull the whole series and series they depends upon to properly support
  gamma LUT.

  [Test]
  The easier way to reproduce the issue is to
  1) Login under Wayland
  2) Logout and login under X
  3) Go back to wayland
  4) Super + L to screenlock

  With the LUT reworked series applied, screen can always come back
  alive.

  [Where problems could occur]
  Regression can happen on refactoring patches with "no functional change
  intended", let alone overhauls like this one.

  So only OEM-6.1 and Unstable are targeted to contain the potential
  regression.

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


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

[Kernel-packages] [Bug 2009642] Re: mt7921: add support of MTFG table

This bug is awaiting verification that the linux-oem-6.1/6.1.0-1009.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 removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-oem-6.1 verification-needed-jammy

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

Title:
  mt7921: add support of MTFG table

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Released
Status in linux-firmware source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  Add ACPI MTFG table support of Mediatek MT7922 Wi-Fi driver
  to enable 6G power enhance feature.

  [Fix]
  Add MTFG table in driver and update firmware to support it.
  Lunar already got the firmware, so SRU for Jammy only.
  Kernel commit is a new feature and it requests more than 10 unrelated
  commits when backport to 5.15 and 5.19, so SRU for 6.0+ kernel version.

  [Test]
  Verified WiFi on 2.4/5GHz only because of no 6G environment.

  [Where problems could occur]
  Low risk.
  It may cause issues on mt76 driver.

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


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

[Kernel-packages] [Bug 2011379] Re: Speaker / Audio/Mic mute LED don't work on a HP platform

This bug is awaiting verification that the linux-oem-6.1/6.1.0-1009.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: kernel-spammed-jammy-linux-oem-6.1 verification-needed-jammy

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

Title:
  Speaker / Audio/Mic mute LED don't work on a HP platform

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

Bug description:
  [Impact]
  The speaker / audio/mic mute LEDs don't work on a HP platform.

  [Fix]
  This is HP platform needs ALC245_FIXUP_CS35L41_SPI_2_HP_GPIO_LED quirk to
  make mic-mute/audio-mute/speaker working.

  [Test]
  After applying the fix, the speaker / audio/mic mute LEDs are working.

  [Where problems could occur]
  It's low risk as it's specific ID for HP new machines. If the HP ships other 
machines using same SSID, then these functions may not work on those machines.

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


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

[Kernel-packages] [Bug 2011389] Re: vmd may fail to create sysfs entry while `pci_rescan_bus()` called in some other drivers like wwan

This bug is awaiting verification that the linux-oem-6.1/6.1.0-1009.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: kernel-spammed-jammy-linux-oem-6.1 verification-needed-jammy

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

Title:
  vmd may fail to create sysfs entry while `pci_rescan_bus()` called in
  some other drivers like wwan

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  In Progress
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  With wwan t7xx driver patched, vmd may fail the probe process because
  it does not lock properly.

  [Fix]

  https://lore.kernel.org/linux-
  pci/20230313173733.1815277-1-vicamo.y...@canonical.com/T/#u

  [Test Case]

  Verify on platforms with FM350 wwan module with prebuilt oem-6.1 or
  above kernels. No vmd probe error should be found in dmesg.

  [Where problems could occur]

  This is the way it should have been done.

  [Other Info]

  This is not reproducible with v6.0 or older kernels, so only Lunar and
  oem-6.1 are nominated for fix. OEM-6.0 patch goes to Gerrit instead.

  == original bug report ==

  vmd may fail to create sysfs entry while `pci_rescan_bus()` called in
  some other drivers like wwan.

  This happens after bug 2002089 re-added pci rescan feature back to
  wwan t7xx driver to support firmware updates via devlink. t7xx may
  call `pci_rescan_bus()` with proper locks, but vmd doesn't.

  sysfs: cannot create duplicate filename '/devices/.../resource0'
  Call Trace:
   
   sysfs_warn_dup.cold+0x17/0x34
   sysfs_add_bin_file_mode_ns+0xc0/0xf0
   sysfs_create_bin_file+0x6d/0xb0
   pci_create_attr+0x117/0x260
   pci_create_resource_files+0x6b/0x150
   pci_create_sysfs_dev_files+0x18/0x30
   pci_bus_add_device+0x30/0x80
   pci_bus_add_devices+0x31/0x80
   pci_bus_add_devices+0x5b/0x80
   vmd_enable_domain.constprop.0+0x6b7/0x880 [vmd]
   vmd_probe+0x16d/0x193 [vmd]

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


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

[Kernel-packages] [Bug 2011768] Re: Fix NVME storage with RAID ON disappeared under Dell factory WINPE environment

This bug is awaiting verification that the linux-oem-6.1/6.1.0-1009.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: kernel-spammed-jammy-linux-oem-6.1 verification-needed-jammy

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

Title:
  Fix NVME storage with RAID ON disappeared under Dell factory WINPE
  environment

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

Bug description:
  [Impact]
  NVME storage disappeared under Dell factory WINPE environment with RAID ON 
mode when this WINPE boot entry touched by efibootmgr

  [Fix]
  Reset the VMD msi remapping during shutdown.

  [Test Case]
  1. Install Ubuntu
  2. Then, system will reboot to WINPE to do some cleanup work.
  3. in WINPE, the NVME storage could be listed.

  [Where problems could occur]
  Low, the issue may be observed on VMD MSI remapping.

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


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

[Kernel-packages] [Bug 2011407] Re: Jammy update: v6.1.16 upstream stable release

This bug is awaiting verification that the linux-oem-6.1/6.1.0-1009.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: kernel-spammed-jammy-linux-oem-6.1 verification-needed-jammy

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

Title:
  Jammy update: v6.1.16 upstream stable release

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

Bug description:
  SRU Justification

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

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

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


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

[Kernel-packages] [Bug 2012019] Re: Fix E-star testing failure with RTK 8852BE

This bug is awaiting verification that the linux-oem-6.1/6.1.0-1009.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: kernel-spammed-jammy-linux-oem-6.1 verification-needed-jammy

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

Title:
  Fix E-star testing failure with RTK 8852BE

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

Bug description:
  [Impact]
  E-star testing failure on machine with RTK 8852BE configuration.

  [Fix]
  1. Enable CLKREQ to reduce power consumption.
  2. release RX standby timer of beamformee to save power

  [Test Case]
  1. Prepare one system with RTK 8852BE WLAN/BT.
  2. Run E-star testing.
  3. The result must meet PASS criteria.

  [Where problems could occur]
  Low, may face the performance issue during throughput verification.

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


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

[Kernel-packages] [Bug 2012846] Re: Fix spurious wakeup from S5 when TBT dock is plugged

This bug is awaiting verification that the linux-oem-6.1/6.1.0-1009.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: kernel-spammed-jammy-linux-oem-6.1 verification-needed-jammy

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

Title:
  Fix spurious wakeup from S5 when TBT dock is plugged

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  When TBT dock is plugged, system wakes up immediately after shutdown.

  [Fix]
  "ACPICA: Events: Support fixed PCIe wake event" to properly support fixed 
PCIe wake event.
  Opposite to other ACPI events, the PCIe wake event gets enabled during boot 
up and gets disabled on S states like S5 shutdown.

  [Test]
  The spurious wake up is no longer observed when 

  [Where problems could occur]
  I did some quick tests and didn't see any negative impact.
  However, since ACPI fixed PCIe event now is enabled when system is running, 
events like runtime PCIe D3cold wake can be affected.

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


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

[Kernel-packages] [Bug 2013114] Re: The panel get blank for too long after disconnecting dock with monitors

This bug is awaiting verification that the linux-oem-6.1/6.1.0-1009.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: kernel-spammed-jammy-linux-oem-6.1 verification-needed-jammy

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

Title:
  The panel get blank for too long after disconnecting dock with
  monitors

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  Connect 2 or more external monitors via type-C docking station, the dp-mst 
function is working correctly. However, after unplugging the docking station, 
the internal display seems to freeze for more than 5 seconds to get back with 
normal display.

  [Fix]
  Intel release a fix to abort the DP AUX transfer on a disconnected TC port. 
It prevent the DP to stuck in a unexpected long retry.

  [Test]
  Connect external monitors to the type-C port on the system. Make sure 
external monitor display OK then unplug the dock. The internal panel should not 
stay in blank for more than 10 seconds.

  [Where problems could occur]
  The long AUX transfer timeout and retry are meaningless on a disconnected 
sink. Should be no risk for regression.

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


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

[Kernel-packages] [Bug 2015833] Re: ubuntu_bpf/test_verifier failed on B-KVM (bounds check after 32-bit right shift with 64-bit input FAIL)

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

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

** Changed in: linux-kvm (Ubuntu)
   Status: New => Fix Released

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

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

Title:
  ubuntu_bpf/test_verifier failed on B-KVM (bounds check after 32-bit
  right shift with 64-bit input FAIL)

Status in ubuntu-kernel-tests:
  New
Status in linux-kvm package in Ubuntu:
  Fix Released
Status in linux-kvm source package in Bionic:
  Confirmed

Bug description:
  This is not a regression, we don't test ubuntu_bpf on KVM kernels
  until we have openstack added recently.

  Test failed with:
  #435/u bounds check after 32-bit right shift with 64-bit input FAIL
  Unexpected error message!
  0: (7a) *(u64 *)(r10 -8) = 0
  1: (bf) r2 = r10
  2: (07) r2 += -8
  3: (18) r1 = 0x0
  5: (85) call bpf_map_lookup_elem#1
  6: (15) if r0 == 0x0 goto pc+6
   R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R10=fp0
  7: (b7) r1 = 2
  8: (67) r1 <<= 31
  9: (74) (u32) r1 >>= (u32) 31
  10: (14) (u32) r1 -= (u32) 2
  11: (0f) r0 += r1
  math between map_value pointer and 4294967294 is not allowed
  #435/p bounds check after 32-bit right shift with 64-bit input FAIL
  Unexpected error message!
  0: (7a) *(u64 *)(r10 -8) = 0
  1: (bf) r2 = r10
  2: (07) r2 += -8
  3: (18) r1 = 0x9fe6065f4c00
  5: (85) call bpf_map_lookup_elem#1
  6: (15) if r0 == 0x0 goto pc+6
   R0=map_value(id=0,off=0,ks=8,vs=8,imm=0) R10=fp0
  7: (b7) r1 = 2
  8: (67) r1 <<= 31
  9: (74) (u32) r1 >>= (u32) 31
  10: (14) (u32) r1 -= (u32) 2
  11: (0f) r0 += r1
  math between map_value pointer and 4294967294 is not allowed

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


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

[Kernel-packages] [Bug 2015836] Re: package linux-image-unsigned-6.2.0-19-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11

2023-04-10 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-unsigned-6.2.0-19-generic (not installed) failed
  to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with
  return code 11

Status in dkms package in Ubuntu:
  New

Bug description:
  Cannot log in (no keyboard input on login screen) with 6.2.0-19 but
  can with 6.2.0.18.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-image-unsigned-6.2.0-19-generic (not installed)
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  larry  2836 F wireplumber
   /dev/snd/controlC1:  larry  2836 F wireplumber
   /dev/snd/controlC0:  larry  2836 F wireplumber
   /dev/snd/seq:larry  2833 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Mon Apr 10 11:45:59 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  InstallationDate: Installed on 2022-02-12 (422 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic 
root=UUID=c085ea94-9283-4cd6-b9a2-bbedfd2aa112 ro quiet splash 
usbcore.autosuspend=1 nvidia.NVreg_RegistryDwords=EnableBrightnessControl=1 
vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0
  SourcePackage: dkms
  Title: package linux-image-unsigned-6.2.0-19-generic (not installed) failed 
to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return 
code 11
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/19/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4022
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING X570-PLUS (WI-FI)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4022:bd10/19/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


-- 
Mailing list: https://launchpad.net/~kernel-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-restricted-modules-lowlatency-hwe-5.15/5.15.0-70.77~20.04.1)

2023-04-10 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted 
linux-restricted-modules-lowlatency-hwe-5.15 (5.15.0-70.77~20.04.1) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)


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-restricted-modules-lowlatency-
hwe-5.15

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging 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 2006712] Re: Doesn't start on i5-13600K

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

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

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

Title:
  Doesn't start on i5-13600K

Status in linux package in Ubuntu:
  Expired

Bug description:
  When installed the new kernel (5.15.0-60) the OS doesn't boot at all (all I 
see is the MSI logo). 
  Booting into recovery returns the message that 'there's no memory (RAM?)'.

  
  Hardware:
  - CPU: i5-13600K
  - Motherboard: PRO Z690-A DDR4
  - SSD: 2nd slot WD Green
  - RAM: 32GB of fresh DDR4 3600Mhz
  - GPU: Nvidia 1660 (with Optimus drivers)

  Note I: I've updated the BIOS on the motherboard, so the CPU is supported.
  Note II: The whole spec is new apart from GPU.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  1394 F pulseaudio
   /dev/snd/controlC2:  chris  1394 F pulseaudio
   /dev/snd/pcmC2D0p:   chris  1394 F...m pulseaudio
   /dev/snd/controlC1:  chris  1394 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 21.1
  InstallationDate: Installed on 2023-01-16 (23 days ago)
  InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7D25
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=07fa5762-37a1-487f-b739-4f27238d542b ro recovery nomodeset 
dis_ucode_ldr
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-58-generic N/A
   linux-backports-modules-5.15.0-58-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  RfKill:
   
  Tags:  vera
  Uname: Linux 5.15.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/31/2022
  dmi.bios.release: 5.27
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 1.80
  dmi.board.asset.tag: Default string
  dmi.board.name: PRO Z690-A DDR4(MS-7D25)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.80:bd08/31/2022:br5.27:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D25:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ690-ADDR4(MS-7D25):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7D25
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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


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

[Kernel-packages] [Bug 2015836] [NEW] package linux-image-unsigned-6.2.0-19-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11

2023-04-10 Thread LarryBuza

Public bug reported:

Cannot log in (no keyboard input on login screen) with 6.2.0-19 but can
with 6.2.0.18.

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-image-unsigned-6.2.0-19-generic (not installed)
ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
Uname: Linux 6.2.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  larry  2836 F wireplumber
 /dev/snd/controlC1:  larry  2836 F wireplumber
 /dev/snd/controlC0:  larry  2836 F wireplumber
 /dev/snd/seq:larry  2833 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Mon Apr 10 11:45:59 2023
ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
InstallationDate: Installed on 2022-02-12 (422 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: System manufacturer System Product Name
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic 
root=UUID=c085ea94-9283-4cd6-b9a2-bbedfd2aa112 ro quiet splash 
usbcore.autosuspend=1 nvidia.NVreg_RegistryDwords=EnableBrightnessControl=1 
vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.21ubuntu1
 apt  2.6.0
SourcePackage: dkms
Title: package linux-image-unsigned-6.2.0-19-generic (not installed) failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/19/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4022
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING X570-PLUS (WI-FI)
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4022:bd10/19/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-package lunar

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

Title:
  package linux-image-unsigned-6.2.0-19-generic (not installed) failed
  to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with
  return code 11

Status in dkms package in Ubuntu:
  New

Bug description:
  Cannot log in (no keyboard input on login screen) with 6.2.0-19 but
  can with 6.2.0.18.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-image-unsigned-6.2.0-19-generic (not installed)
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  larry  2836 F wireplumber
   /dev/snd/controlC1:  larry  2836 F wireplumber
   /dev/snd/controlC0:  larry  2836 F wireplumber
   /dev/snd/seq:larry  2833 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Mon Apr 10 11:45:59 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  InstallationDate: Installed on 2022-02-12 (422 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic 
root=UUID=c085ea94-9283-4cd6-b9a2-bbedfd2aa112 ro quiet splash 
usbcore.autosuspend=1 nvidia.NVreg_RegistryDwords=EnableBrightnessControl=1 
vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0
  SourcePackage: dkms
  Title: package linux-image-unsigned-6.2.0-19-generic (not installed) failed 
to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return 
code 11
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/19/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4022
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING X570-PLUS (WI-FI)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.

[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM

2023-04-10 Thread Marcos Bernardo Jr

Same problem...
I have an Aspire A515-57 and i am running into the same issue :/
I have tried replicating the steps from #19, but didn't manage to fix it. 
Probably due to my lack of experience using Linux. Mine is the 0408:4033

BTW could any of you gentlemen do a more detailed step-by-step or video
for the layman such as myself?

Thanks in advance!

BR
Marcos

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

Title:
  UVC  Quanta 0408:4035  camera PROBLEM

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing',
  USB 0408:4035.

  The camera is reported to have problems by many users:  
  https://linux-hardware.org/?id=usb:0408-4035
  The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera 
is “recongized” but fails installation.

  My console commands report similar info to other users: 
  
https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58

  
  PROPOSED SOLUTION 
  I got in contact with laurent.pinch...@ideasonboard.com   and with 
riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And  
me...@vger.kernel.org mailinglist.

  Laurent proposed me a fix and I modified the 5,15 uvc_driver.c
  version, and loaded it on github

  https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User-
  Facing-0x0408-0x4035-/blob/main/uvc_driver.c

  I offered to test the fix, so I tried to compile the module with the
  new source.

  COMPILING PROBLEMS
  I’m running **Ubuntu 22.04.1 LTS, with kernel 
  giuliano@Astra2A:/usr/src$ cat /proc/version_signature
  Ubuntu 5.15.0-56.62-generic 5.15.64

  BUT  the linux-source that I found installed seems to be different
  tgiuliano@Astra2A:/usr/src$ ls -al linux-so*
  lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> 
linux-source-5.15.0/linux-source-5.15.0.tar.bz2

  I expanded  the tar file, configured the IDE and compiled without error  any 
errors… 
  I manually copied the uvcvideo.ko in 
  /lib/modules/5.15.0-56-
  sudo cp…...

  then tryed to intall the new uvcvideo.ko module
  sudo rmmod uvcvideo && sudo modprobe uvcvideo

  BUT… IT FAILS
  giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo
  modprobe: ERROR: could not insert 'uvcvideo': Exec format error

  and dmesg shows
  [25961.151982] usbcore: registered new interface driver uvcvideo
  [26323.125534] usbcore: deregistering interface driver uvcvideo
  [26323.189294] uvcvideo: disagrees about version of symbol module_layout


  These are the TWO modinfo from the old and new uvcvideo modules
  https://pastebin.com/tSj8Exm6
  Basically
  OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions 
  NEW module: vermagic: 5.15.64 SMP mod_unload modversions


  -kindly ASK

  HOW can FORCE the uvcdriver.c to match mi kernel version ?
  Have I got OTHER ways to make the kernel module I’m compiling, match my 
running system ?

  I would like to test the module so to confirm the patch and let it
  enter the kernel main stream...

  
  BR
  Giuliano

  PS
  btw…. to allow Eclipse to compile the kernel, I had to pass this commands
  scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_TRUSTED_KEYS

  hope that this does not affect the module layout & checking
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  giuliano   2142 F pulseaudio
   /dev/snd/pcmC1D0p:   giuliano   2142 F...m pulseaudio
   /dev/snd/controlC0:  giuliano   2142 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-03 (66 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Acer Nitro AN517-55
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic 
root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-57-generic N/A
   linux-backports-modules-5.15.0-57-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  Tags:  jammy
  Uname: Linux 5.15.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/20/

[Kernel-packages] [Bug 1848004] Re: test_maps from ubuntu_bpf failed with sockmap creation on B/D-KVM

** Tags added: sru-20230320

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

Title:
  test_maps from ubuntu_bpf failed with sockmap creation on B/D-KVM

Status in ubuntu-kernel-tests:
  Triaged
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux-kvm source package in Bionic:
  Confirmed
Status in linux-kvm source package in Disco:
  Won't Fix

Bug description:
  Test test_maps test from ubuntu_bpf failed with Disco KVM kernel
  (5.0.0-1019-kvm)

   Running './test_maps'
   Failed to create sockmap -1

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-1019-kvm 5.0.0-1019.20
  ProcVersionSignature: User Name 5.0.0-1019.20-kvm 5.0.21
  Uname: Linux 5.0.0-1019-kvm x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  Date: Mon Oct 14 11:49:26 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1987507] Autopkgtest regression report (linux-restricted-modules-hwe-5.15/5.15.0-70.77~20.04.1)

2023-04-10 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-restricted-modules-hwe-5.15 
(5.15.0-70.77~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)


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-restricted-modules-hwe-5.15

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

Thank you!

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

Title:
  Migrate oem-20.04 to hwe-5.15

Status in linux-meta-hwe-5.15 package in Ubuntu:
  Invalid
Status in linux-restricted-modules-hwe-5.15 package in Ubuntu:
  Invalid
Status in linux-meta-hwe-5.15 source package in Focal:
  New
Status in linux-restricted-modules-hwe-5.15 source package in Focal:
  New

Bug description:
  [Impact]
  Migrate oem-5.14 to hwe-5.15 now that there should be no functional 
regressions left anymore.

  [Test case]
  Update a machine with oem-5.14 metapackages to the proposed ones, and verify 
that all packages (including nvidia etc) migrate properly.

  [Where things could go wrong]
  In theory we might miss a package to transition, but at this point this is 
unlikely.

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


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

[Kernel-packages] [Bug 1991130] Autopkgtest regression report (linux-restricted-modules-hwe-5.15/5.15.0-70.77~20.04.1)

2023-04-10 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-restricted-modules-hwe-5.15 
(5.15.0-70.77~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)


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-restricted-modules-hwe-5.15

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

Thank you!

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

Title:
  Add lrm autogenerated transitional independent of variants

Status in linux-restricted-modules package in Ubuntu:
  New
Status in linux-restricted-modules-hwe-5.15 package in Ubuntu:
  Invalid
Status in linux-restricted-modules source package in Focal:
  Invalid
Status in linux-restricted-modules-hwe-5.15 source package in Focal:
  In Progress

Bug description:
  [Impact]

  The kernel lrm packages have a mechanism to auto-generate transitional
  packages by adding a line to 'debian/package.config' in the following
  format

  transitional   

  Example:

  transitional 450-oem-20.04 450-generic amd64

  When being processed by 'debian/scripts/gen-rules.lrm' the
  autogenerated contents are added to 'debian/control.d/transitionals-
  local'. However, this file is not included in the final
  'debian/control' for packages which does not contain the default
  variant '--' (see debian/rules.in). This is intentional to prevent
  unwanted transitionals.

  However, there are some cases where we want to transition packages to
  kernels which are not the default variant in a series (e.g. hwe
  kernels).

  [Fix]

  The proposed fix is to add a new command "migrate", which does exactly
  what "transitional" does but adding the content to
  'debian/control.d/migrate-local' which would get added to the final
  'debian/control' independently of the source's variants.

  [Test Case]

  Add "migrate" entries to 'debian/package.config' and check whether
  they get added to 'debian/control' even for non default variant
  packages.

  [Where problems could occur]

  If not used correctly, unwanted transitionals could be generated
  causing issues to the archive. However, this is a new command and
  should not impact any of the previously set transitionals and it needs
  to be explicitly used.

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


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

[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74

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

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

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


** Tags added: kernel-spammed-kinetic-linux-kvm

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

Title:
  NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74

Status in linux package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-aws source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux-aws source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-aws source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-aws source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux-aws source package in Lunar:
  Invalid

Bug description:
  After updating on the kernel 
  5.4.0-144.161 at Ubuntu 18 and 
  5.15.0-67.74 at Ubuntu 20, 
  we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our 
NFS servers.

  All clients are extremely slow when it comes to access to the NFS
  resources.

  Restart and use older kernel, fixed the problem.
  Ubuntu 18 5.4.0-139-generic
  Ubuntu 20 5.15.0-60-Generic
  I don't have a NFS problem with this kernel.

  Problem came with the last releas on March 3rd, 2023
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mär  4 15:00 seq
   crw-rw 1 root audio 116, 33 Mär  4 15:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic 
root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto 
elevator=noop
  ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-67-generic N/A
   linux-backports-modules-5.15.0-67-generic  N/A
   linux-firmware 1.187.36
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal
  Uname: Linux 5.15.0-67-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mär  4 15:03 seq
   crw-rw 1 root audio 116, 33 Mär  4 15:03 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.28
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMwa

[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74

2023-04-10 Thread ChengEn, Du

Hi @krglosse,

We have opened a bug to address the performance issue related to NFS.
You can find more details about the bug at this link: 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015827.

We have also sent a proposal to upstream for their consideration, but 
unfortunately, we have not received a response yet.
As a result, we may need to send a patch directly and await upstream's feedback 
and judgement.

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

Title:
  NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74

Status in linux package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-aws source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux-aws source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-aws source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-aws source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux-aws source package in Lunar:
  Invalid

Bug description:
  After updating on the kernel 
  5.4.0-144.161 at Ubuntu 18 and 
  5.15.0-67.74 at Ubuntu 20, 
  we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our 
NFS servers.

  All clients are extremely slow when it comes to access to the NFS
  resources.

  Restart and use older kernel, fixed the problem.
  Ubuntu 18 5.4.0-139-generic
  Ubuntu 20 5.15.0-60-Generic
  I don't have a NFS problem with this kernel.

  Problem came with the last releas on March 3rd, 2023
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mär  4 15:00 seq
   crw-rw 1 root audio 116, 33 Mär  4 15:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic 
root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto 
elevator=noop
  ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-67-generic N/A
   linux-backports-modules-5.15.0-67-generic  N/A
   linux-firmware 1.187.36
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal
  Uname: Linux 5.15.0-67-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mär  4 15:03 seq
   crw-rw 1 root audio 116, 33 Mär  4 15:03 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.28
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic 
root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto 
elevator=noop
  ProcV

[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74

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

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

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


** Tags added: kernel-spammed-jammy-linux-gke

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

Title:
  NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74

Status in linux package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-aws source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux-aws source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-aws source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-aws source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux-aws source package in Lunar:
  Invalid

Bug description:
  After updating on the kernel 
  5.4.0-144.161 at Ubuntu 18 and 
  5.15.0-67.74 at Ubuntu 20, 
  we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our 
NFS servers.

  All clients are extremely slow when it comes to access to the NFS
  resources.

  Restart and use older kernel, fixed the problem.
  Ubuntu 18 5.4.0-139-generic
  Ubuntu 20 5.15.0-60-Generic
  I don't have a NFS problem with this kernel.

  Problem came with the last releas on March 3rd, 2023
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mär  4 15:00 seq
   crw-rw 1 root audio 116, 33 Mär  4 15:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic 
root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto 
elevator=noop
  ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-67-generic N/A
   linux-backports-modules-5.15.0-67-generic  N/A
   linux-firmware 1.187.36
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal
  Uname: Linux 5.15.0-67-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mär  4 15:03 seq
   crw-rw 1 root audio 116, 33 Mär  4 15:03 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.28
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual

[Kernel-packages] [Bug 2013209] Re: expoline.o is packaged unconditionally for s390x

This bug is awaiting verification that the linux-
hwe-5.15/5.15.0-70.77~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: kernel-spammed-focal-linux-hwe-5.15 verification-needed-focal

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

Title:
  expoline.o is packaged unconditionally for s390x

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-hwe-5.15 package in Ubuntu:
  New
Status in linux-hwe-5.15 source package in Focal:
  In Progress
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed

Bug description:
  https://bugs.launchpad.net/bugs/1639924 enabled CONFIG_EXPOLINE_EXTERN
  for s390x in Jammy. While this works as expected on Jammy, it won't
  work on some derivatives of it: for example focal:hwe-5.15. On Focal,
  this config can't be enabled due to the GCC version it comes with.
  CONFIG_EXPOLINE_EXTERN requires >= 110200 while Focal comes with
  90400.

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


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

[Kernel-packages] [Bug 2013537] Re: Focal can't enable EXPOLINE_EXTERN due to GCC version requirement

This bug is awaiting verification that the linux-
hwe-5.15/5.15.0-70.77~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: kernel-spammed-focal-linux-hwe-5.15 verification-needed-focal

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

Title:
  Focal can't enable EXPOLINE_EXTERN due to GCC version requirement

Status in linux-hwe-5.15 package in Ubuntu:
  New
Status in linux-hwe-5.15 source package in Focal:
  In Progress

Bug description:
  https://bugs.launchpad.net/bugs/1639924 enabled CONFIG_EXPOLINE_EXTERN
  for s390x in Jammy. While doing so, it also defined an associated
  annotation check to enforce it on s390x. On Focal, this config can't
  be enabled due to the GCC version it comes with.
  CONFIG_EXPOLINE_EXTERN requires >= 110200 while Focal comes with
  90400.

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


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

[Kernel-packages] [Bug 2015827] Re: NFS performance issue while clearing the file access cache upon login

2023-04-10 Thread ChengEn, Du

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => ChengEn, Du (chengendu)

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

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

Title:
  NFS performance issue while clearing the file access cache upon login

Status in linux package in Ubuntu:
  In Progress

Bug description:
  The performance issue that has been observed may be attributed to an increase 
in NFS ACCESS operations, possibly due to a new mechanism introduced in the 
Linux 6.2-rc3 NFS client side.
  This mechanism clears the access cache as soon as the cache timestamp becomes 
older than the user's login time,
  with the primary objective of preventing the NFS client's access cache from 
becoming stale due to any changes made to the user's group membership on the 
server after the user has already logged in on the client.

  It's worth noting that POSIX only refreshes the user's supplementary group 
information upon login.
  Upstream has taken into consideration that users may reasonably expect the 
access cache to be cleared when they log out and log back in again, with all 
behavior returning to normal after the replacement.

  The performance overhead can be particularly noticeable when applications or 
users switch to other privileged users via commands such as "su" to operate on 
NFS-mounted folders.
  In such cases, the privileged user's login time will be renewed, and NFS 
ACCESS operations will need to be re-sent, potentially leading to performance 
degradation.

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


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

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

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

apport-collect 2015827

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

Title:
  NFS performance issue while clearing the file access cache upon login

Status in linux package in Ubuntu:
  In Progress

Bug description:
  The performance issue that has been observed may be attributed to an increase 
in NFS ACCESS operations, possibly due to a new mechanism introduced in the 
Linux 6.2-rc3 NFS client side.
  This mechanism clears the access cache as soon as the cache timestamp becomes 
older than the user's login time,
  with the primary objective of preventing the NFS client's access cache from 
becoming stale due to any changes made to the user's group membership on the 
server after the user has already logged in on the client.

  It's worth noting that POSIX only refreshes the user's supplementary group 
information upon login.
  Upstream has taken into consideration that users may reasonably expect the 
access cache to be cleared when they log out and log back in again, with all 
behavior returning to normal after the replacement.

  The performance overhead can be particularly noticeable when applications or 
users switch to other privileged users via commands such as "su" to operate on 
NFS-mounted folders.
  In such cases, the privileged user's login time will be renewed, and NFS 
ACCESS operations will need to be re-sent, potentially leading to performance 
degradation.

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


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

[Kernel-packages] [Bug 2015827] [NEW] NFS performance issue while clearing the file access cache upon login

2023-04-10 Thread ChengEn, Du

Public bug reported:

The performance issue that has been observed may be attributed to an increase 
in NFS ACCESS operations, possibly due to a new mechanism introduced in the 
Linux 6.2-rc3 NFS client side.
This mechanism clears the access cache as soon as the cache timestamp becomes 
older than the user's login time,
with the primary objective of preventing the NFS client's access cache from 
becoming stale due to any changes made to the user's group membership on the 
server after the user has already logged in on the client.

It's worth noting that POSIX only refreshes the user's supplementary group 
information upon login.
Upstream has taken into consideration that users may reasonably expect the 
access cache to be cleared when they log out and log back in again, with all 
behavior returning to normal after the replacement.

The performance overhead can be particularly noticeable when applications or 
users switch to other privileged users via commands such as "su" to operate on 
NFS-mounted folders.
In such cases, the privileged user's login time will be renewed, and NFS ACCESS 
operations will need to be re-sent, potentially leading to performance 
degradation.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: ChengEn, Du (chengendu)
 Status: In Progress

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

Title:
  NFS performance issue while clearing the file access cache upon login

Status in linux package in Ubuntu:
  In Progress

Bug description:
  The performance issue that has been observed may be attributed to an increase 
in NFS ACCESS operations, possibly due to a new mechanism introduced in the 
Linux 6.2-rc3 NFS client side.
  This mechanism clears the access cache as soon as the cache timestamp becomes 
older than the user's login time,
  with the primary objective of preventing the NFS client's access cache from 
becoming stale due to any changes made to the user's group membership on the 
server after the user has already logged in on the client.

  It's worth noting that POSIX only refreshes the user's supplementary group 
information upon login.
  Upstream has taken into consideration that users may reasonably expect the 
access cache to be cleared when they log out and log back in again, with all 
behavior returning to normal after the replacement.

  The performance overhead can be particularly noticeable when applications or 
users switch to other privileged users via commands such as "su" to operate on 
NFS-mounted folders.
  In such cases, the privileged user's login time will be renewed, and NFS 
ACCESS operations will need to be re-sent, potentially leading to performance 
degradation.

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


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

[Kernel-packages] [Bug 2012335] Re: Ubuntu 22.04 raise abnormal NIC MSI-X requests with larger CPU cores (256)

2023-04-10 Thread Luke Nowakowski-Krijger

hey @xijunli ! Could you please test that the driver now works as
expected? I have placed the files here
https://kernel.ubuntu.com/~lukenow/lp2012335/ , but you should only need
to install the modules. Let me know if that works for you

Thanks, 
- Luke

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

Title:
  Ubuntu 22.04 raise abnormal NIC MSI-X requests with larger CPU cores
  (256)

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

Bug description:
  System Configuration
  OS: Ubuntu 22.04 LTS
  Kernel: 5.15.0-25-generic
  CPUs: 256
  NIC: Intel E810 NIC with 512 MSIx vectors each function

  
  Errors
  Not enough device MSI-X vectors, requested = 260, available = 253

  
  Findings
  (1) the current ice kernel driver (ice_main.c) will pre-allocate all 
required number of msix (even it's not enough for big core CPUs)
  (2) the commit 
https://github.com/torvalds/linux/commit/ce4626131112e1d0066a890371e14d8091323f99
 has improved this logic, and it seems merged into kernel version from v6.1

  
  So for supporting the new CPUs with more than 252 vCPUs, will Ubuntu kernel 
backport above patch to the current kernel (v5.15) ?

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


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

[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74

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

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

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


** Tags added: kernel-spammed-kinetic-linux-allwinner

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

Title:
  NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74

Status in linux package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-aws source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux-aws source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-aws source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-aws source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux-aws source package in Lunar:
  Invalid

Bug description:
  After updating on the kernel 
  5.4.0-144.161 at Ubuntu 18 and 
  5.15.0-67.74 at Ubuntu 20, 
  we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our 
NFS servers.

  All clients are extremely slow when it comes to access to the NFS
  resources.

  Restart and use older kernel, fixed the problem.
  Ubuntu 18 5.4.0-139-generic
  Ubuntu 20 5.15.0-60-Generic
  I don't have a NFS problem with this kernel.

  Problem came with the last releas on March 3rd, 2023
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mär  4 15:00 seq
   crw-rw 1 root audio 116, 33 Mär  4 15:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic 
root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto 
elevator=noop
  ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-67-generic N/A
   linux-backports-modules-5.15.0-67-generic  N/A
   linux-firmware 1.187.36
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal
  Uname: Linux 5.15.0-67-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mär  4 15:03 seq
   crw-rw 1 root audio 116, 33 Mär  4 15:03 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.28
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMw

[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74

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

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

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


** Tags added: kernel-spammed-kinetic-linux-starfive

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

Title:
  NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74

Status in linux package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-aws source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux-aws source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-aws source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-aws source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux-aws source package in Lunar:
  Invalid

Bug description:
  After updating on the kernel 
  5.4.0-144.161 at Ubuntu 18 and 
  5.15.0-67.74 at Ubuntu 20, 
  we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our 
NFS servers.

  All clients are extremely slow when it comes to access to the NFS
  resources.

  Restart and use older kernel, fixed the problem.
  Ubuntu 18 5.4.0-139-generic
  Ubuntu 20 5.15.0-60-Generic
  I don't have a NFS problem with this kernel.

  Problem came with the last releas on March 3rd, 2023
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mär  4 15:00 seq
   crw-rw 1 root audio 116, 33 Mär  4 15:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic 
root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto 
elevator=noop
  ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-67-generic N/A
   linux-backports-modules-5.15.0-67-generic  N/A
   linux-firmware 1.187.36
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal
  Uname: Linux 5.15.0-67-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mär  4 15:03 seq
   crw-rw 1 root audio 116, 33 Mär  4 15:03 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.28
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware,

[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74

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

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

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


** Tags removed: verification-done-kinetic
** Tags added: kernel-spammed-kinetic-linux-riscv verification-needed-kinetic

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

Title:
  NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74

Status in linux package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-aws source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux-aws source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-aws source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-aws source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux-aws source package in Lunar:
  Invalid

Bug description:
  After updating on the kernel 
  5.4.0-144.161 at Ubuntu 18 and 
  5.15.0-67.74 at Ubuntu 20, 
  we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our 
NFS servers.

  All clients are extremely slow when it comes to access to the NFS
  resources.

  Restart and use older kernel, fixed the problem.
  Ubuntu 18 5.4.0-139-generic
  Ubuntu 20 5.15.0-60-Generic
  I don't have a NFS problem with this kernel.

  Problem came with the last releas on March 3rd, 2023
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mär  4 15:00 seq
   crw-rw 1 root audio 116, 33 Mär  4 15:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic 
root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto 
elevator=noop
  ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-67-generic N/A
   linux-backports-modules-5.15.0-67-generic  N/A
   linux-firmware 1.187.36
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal
  Uname: Linux 5.15.0-67-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mär  4 15:03 seq
   crw-rw 1 root audio 116, 33 Mär  4 15:03 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.28
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error:

[Kernel-packages] [Bug 2015812] Re: Kinetic update: upstream stable patchset 2023-04-10

2023-04-10 Thread Kamal Mostafa

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

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

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

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

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    upstream stable patchset 2023-04-10
+    from git://git.kernel.org/
  
-upstream stable patchset 2023-04-10
-from git://git.kernel.org/
+ drm/etnaviv: don't truncate physical page address
+ wifi: rtl8xxxu: gen2: Turn on the rate control
+ drm/edid: Fix minimum bpc supported with DSC1.2 for HDMI sink
+ clk: mxl: Switch from direct readl/writel based IO to regmap based IO
+ clk: mxl: Remove redundant spinlocks
+ clk: mxl: Add option to override gate clks
+ clk: mxl: Fix a clk entry by adding relevant flags
+ powerpc: dts: t208x: Mark MAC1 and MAC2 as 10G
+ clk: mxl: syscon_node_to_regmap() returns error pointers
+ random: always mix cycle counter in add_latent_entropy()
+ KVM: x86: Fail emulation during EMULTYPE_SKIP on any exception
+ KVM: SVM: Skip WRMSR fastpath on VM-Exit if next RIP isn't valid
+ can: kvaser_usb: hydra: help gcc-13 to figure out cmd_len
+ powerpc: dts: t208x: Disable 10G on MAC1 and MAC2
+ powerpc/vmlinux.lds: Ensure STRICT_ALIGN_SIZE is at least page aligned
+ powerpc/64s/radix: Fix RWX mapping with relocated kernel
+ uaccess: Add speculation barrier to copy_from_user()
+ wifi: mwifiex: Add missing compatible string for SD8787
+ audit: update the mailing list in MAINTAINERS
+ ext4: Fix function prototype mismatch for ext4_feat_ktype
+ Revert "net/sched: taprio: make qdisc_leaf() see the per-netdev-queue pfifo 
child qdiscs"
+ bpf: add missing header file include
+ wifi: ath11k: fix warning in dma_free_coherent() of memory chunks while 
recovery
+ sched/psi: Stop relying on timer_pending() for poll_work rescheduling
+ docs: perf: Fix PMU instance name of hisi-pcie-pmu
+ randstruct: disable Clang 15 support
+ UBUNTU: Upstream stable to v5.15.96, v6.1.14
+ ionic: refactor use of ionic_rx_fill()
+ Fix XFRM-I support for nested ESP tunnels
+ arm64: dts: rockchip: drop unused LED mode property from rk3328-roc-cc
+ ARM: dts: rockchip: add power-domains property to dp node on rk3288
+ HID: elecom: add support for TrackBall 056E:011C
+ ACPI: NFIT: fix a potential deadlock during NFIT teardown
+ btrfs: send: limit number of clones and allocated memory size
+ ASoC: rt715-sdca: fix clock stop prepare timeout issue
+ IB/hfi1: Assign npages earlier
+ neigh: make sure used and confirmed times are valid
+ HID: core: Fix deadloop in hid_apply_multiplier.
+ x86/cpu: Add Lunar Lake M
+ bpf: bpf_fib_lookup should not return neigh in NUD_FAILED state
+ net: Remove WARN_ON_ONCE(sk->sk_forward_alloc) from sk_stream_kill_queues().
+ vc_screen: don't clobber return value in vcs_read
+ scripts/tags.sh: fix incompatibility with PCRE2
+ usb: dwc3: pci: add support for the Intel Meteor Lake-M
+ USB: serial: option: add support for VW/Skoda "Carstick LTE"
+ usb: gadget: u_serial: Add null pointer check in gserial_resume
+ USB: core: Don't hold device lock while reading the "descriptors" sysfs file
+ UBUNTU: Upstream stable to v5.15.97, v6.1.15

** Description changed:

  SRU Justification
  
  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:
  
     upstream stable patchset 2023-04-10
+ 
+ Ported from the following upstream stable releases:
+ v5.15.96, v6.1.14
+ v5.15.97, v6.1.15
+ 
     from git://git.kernel.org/
  
  drm/etnaviv: don't truncate physical page address
  wifi: rtl8xxxu: gen2:

[Kernel-packages] [Bug 2015812] [NEW] Kinetic update: upstream stable patchset 2023-04-10

2023-04-10 Thread Kamal Mostafa

Public bug reported:


SRU Justification

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

   upstream stable patchset 2023-04-10
   from git://git.kernel.org/

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

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


** Tags: kernel-stable-tracking-bug

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

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

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

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

Title:
  Kinetic update: upstream stable patchset 2023-04-10

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

Bug description:
  
  SRU Justification

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

 upstream stable patchset 2023-04-10
 from git://git.kernel.org/

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


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

[Kernel-packages] [Bug 2004132] Re: btrfs/154: rename fails with EOVERFLOW when calculating item size during item key collision

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

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

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


** Tags removed: verification-done-bionic
** Tags added: kernel-spammed-bionic-linux-snapdragon verification-needed-bionic

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

Title:
  btrfs/154: rename fails with EOVERFLOW when calculating item size
  during item key collision

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

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

  [Impact]

  xfstests btrfs/154 fails on both Bionic and Focal, leading to a kernel
  oops and the btrfs volume being forced readonly.

  In btrfs, item key collision is allowed for some item types, namely
  dir item and inode references. When inserting items into the btree,
  there are two objects, the btrfs_item and the item data. These objects
  must fit within the btree nodesize.

  When a hash collision occurs, and we call btrfs_search_slot() to place
  the objects in the tree, when btrfs_search_slot() reaches the leaf
  node, a check is performed to see if we need to split the leaf. The
  check is incorrect, returning that we need to split the leaf, since it
  thinks that both btrfs_item and the item data need to be inserted,
  when in reality, the item can be merged with the existing one and no
  new btrfs_item will be inserted.

  split_leaf() will return EOVERFLOW from following code:

    if (extend && data_size + btrfs_item_size_nr(l, slot) +
    sizeof(struct btrfs_item) > BTRFS_LEAF_DATA_SIZE(fs_info))
    return -EOVERFLOW;

  In the rename case, btrfs_check_dir_item_collision() is called early
  stages of treewalking, and correctly calculates the needed size,
  taking into account that a hash collision has occurred.

    data_size = sizeof(*di) + name_len;
    if (data_size + btrfs_item_size_nr(leaf, slot) +
    sizeof(struct btrfs_item) > BTRFS_LEAF_DATA_SIZE(root->fs_info))

  The two sizes reported from btrfs_check_dir_item_collision() and
  btrfs_search_slot() are different, and rename fails due to
  split_leaf() returning -EOVERFLOW, leading to transaction abort and
  forcing the volume readonly.

  Kernel oops:

  BTRFS: Transaction aborted (error -75)
  WARNING: CPU: 0 PID: 2921 at 
/build/linux-fTmV3T/linux-4.15.0/fs/btrfs/inode.c:10217 
btrfs_rename+0xcf1/0xdf0 [btrfs]
  CPU: 0 PID: 2921 Comm: python3 Not tainted 4.15.0-202-generic #213-Ubuntu
  RIP: 0010:btrfs_rename+0xcf1/0xdf0 [btrfs]
  RSP: 0018:9e6f4183fd20 EFLAGS: 00010282
  RAX:  RBX: 91a493f27b98 RCX: 0006
  RDX: 0007 RSI: 0096 RDI: 91a4bfc1b4d0
  RBP: 9e6f4183fdc0 R08: 02b4 R09: 0004
  R10:  R11: 0001 R12: 0236
  R13: 91a493f56518 R14: 91a4b6b57b40 R15: 91a493f27b98
  FS:  7f6041081740() GS:91a4bfc0() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 7f6040fe84c8 CR3: 00015c8ca005 CR4: 00760ef0
  PKRU: 5554
  Call Trace:
   btrfs_rename2+0x1d/0x30 [btrfs]
   vfs_rename+0x46e/0x960
   SyS_rename+0x362/0x3c0
   do_syscall_64+0x73/0x130
   entry_SYSCALL_64_after_hwframe+0x41/0xa6
  Code: 0f ba a8 d0 cd 00 00 02 72 2b 41 83 f8 fb 0f 84 d9 00 00 00 44 89 c6 48 
c7 c7 68 43 4b c0 44 89 55 80 44 89 45 98 e8 8f 5c a6 d0 <0f> 0b 44 8b 45 98 44 
8b 55 80 44 89 55 80 44 89 c1 44 89 45 98
  ---[ end trace 9c6b87a19f4436f3 ]---
  BTRFS: error (device vdd) in btrfs_rename:10217: errno=-75 unknown
  BTRFS info (device vdd): forced readonly

  [Testcase]

  Start a fresh Bionic or Focal VM.

  Attach two scratch disks, I used standard virtio disks with 3gb of
  storage each. These disks are /dev/vdc and /dev/vdd.

  Compile xfstests:

  $ sudo apt-get install acl attr automake bc dbench dump e2fsprogs fio gawk \
  gcc git indent libacl1-dev libaio-dev libcap-dev libgdbm-dev libtool \
  libtool-bin  libuuid1 lvm2 make psmisc python3 quota sed \
  uuid-dev uuid-runtime xfsprogs linux-headers-$(uname -r) sqlite3 make
  $ sudo apt-get install  f2fs-tools ocfs2-tools udftools xfsdump \
  xfslibs-dev
  $ git clone git://git.kernel.org/pub/scm/f

[Kernel-packages] [Bug 1922406]

2023-04-10 Thread eddik98

Additional logs:

- Before executing above mv command:
[   18.502463] Intel(R) Wireless WiFi driver for Linux
[   18.502891] iwlwifi 0004:41:00.0: enabling device ( -> 0002)
[   18.543590] iwlwifi 0004:41:00.0: api flags index 2 larger than supported by 
driver
[   18.543628] iwlwifi 0004:41:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 
93.8.63.28
[   18.544154] iwlwifi 0004:41:00.0: loaded firmware version 59.601f3a66.0 
ty-a0-gf-a0-59.ucode op_mode iwlmvm
[   18.552252] iwlwifi 0004:41:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, 
REV=0x420
[   18.631147] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   18.728168] iwlwifi 0004:41:00.0: loaded PNVM version 0x881c99e1
[   19.001708] iwlwifi 0004:41:00.0: Timeout waiting for PNVM load!
[   19.001730] iwlwifi 0004:41:00.0: Failed to start RT ucode: -110
[   19.001740] iwlwifi 0004:41:00.0: iwl_trans_send_cmd bad state = 0
[   19.014020] iwlwifi 0004:41:00.0: Failed to run INIT ucode: -110
[   19.026420] iwlwifi 0004:41:00.0: retry init count 0
[   19.028901] iwlwifi 0004:41:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, 
REV=0x420
[   19.081044] Process accounting resumed
[   19.479068] iwlwifi 0004:41:00.0: Timeout waiting for PNVM load!
[   19.479114] iwlwifi 0004:41:00.0: Failed to start RT ucode: -110
[   19.479137] iwlwifi 0004:41:00.0: iwl_trans_send_cmd bad state = 0
[   19.491411] iwlwifi 0004:41:00.0: Failed to run INIT ucode: -110
[   19.504714] iwlwifi 0004:41:00.0: retry init count 1
[   19.958375] iwlwifi 0004:41:00.0: Timeout waiting for PNVM load!
[   19.958420] iwlwifi 0004:41:00.0: Failed to start RT ucode: -110
[   19.958445] iwlwifi 0004:41:00.0: iwl_trans_send_cmd bad state = 0
[   19.971024] iwlwifi 0004:41:00.0: Failed to run INIT ucode: -110
[   19.983452] iwlwifi 0004:41:00.0: retry init count 2

- After executing above mv command:
[   18.750383] iwlwifi 0004:41:00.0: enabling device ( -> 0002)
[   18.765745] iwlwifi 0004:41:00.0: api flags index 2 larger than supported by 
driver
[   18.765774] iwlwifi 0004:41:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 
93.8.63.28
[   18.766197] iwlwifi 0004:41:00.0: loaded firmware version 59.601f3a66.0 
ty-a0-gf-a0-59.ucode op_mode iwlmvm
[   18.777427] iwlwifi 0004:41:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, 
REV=0x420
[   18.896842] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   19.033116] iwlwifi 0004:41:00.0: base HW address: 04:cf:4b:21:24:e2
[   19.047555] thermal thermal_zone7: power_allocator: sustainable_power will 
be estimated
[   19.047621] thermal thermal_zone7: failed to read out thermal zone (-61)
[   19.055209] iwlwifi 0004:41:00.0 wlP4p65s0: renamed from wlan0

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

Title:
  Intel AX210 Wi-Fi card does not work since updating to 1.196

Status in Linux:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Fix Released

Bug description:
  Running 21.04, updated daily.

  Since updating the linux-firmware package yesterday, the Wireless card
  does not work with current kernel (5.11.0-13).

  The error message is as follows:

  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Timeout waiting 
for PNVM load!
  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Failed to start 
RT ucode: -110
  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: 
iwl_trans_send_cmd bad state = 1

  It **does** work with 5.11.0-11 (previous version)

  Distro: Ubuntu 21.04 (Hirsute Hippo)
  Machine:   Type: Laptop System: LENOVO product: 82C5 v: Lenovo V15-IIL
Mobo: LENOVO model: LNVNB161216 v: SDK0J40700 WIN UEFI: LENOVO v: DKCN51WW 
date: 12/23/2020
  CPU:   Info: Dual Core model: Intel Core i3-1005G1 bits: 64 type: MT MCP 
L2 cache: 4 MiB

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


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

[Kernel-packages] [Bug 1922406]

2023-04-10 Thread eddik98

Hello, I have the same problem, with a lot of linux-firmware versions.
I have found this issue also with 
linux-firmware-20220329.git681281e4-0ubuntu3.12.

After upgrading linux-firmware lib, I always have to use this command
`sudo mv /usr/lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm
/usr/lib/firmware/iwlwifi-ty-a0-gf-a0.bak`
(https://askubuntu.com/questions/1360175/intel-wifi-6-ax210-wifi-not-
working-after-update), and after this command, Wi-Fi module works.

I have the same logs as other users have above.

- linux-firmware-20220329.git681281e4-0ubuntu3.12
- Linux version 5.10.110-rockchip-rk3588 (aarch64-linux-gnu-gcc (Ubuntu 
9.4.0-1ubuntu1~20.04.1) 9.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1 SMP 
Wed Mar 29 08:28:12 BST 2023

00:34:55 kernel: iwlwifi 0004:41:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, 
REV=0x420
00:34:55 kernel: iwlwifi 0004:41:00.0: Failed to run INIT ucode: -110
00:34:55 kernel: iwlwifi 0004:41:00.0: iwl_trans_send_cmd bad state = 0
00:34:54 kernel: iwlwifi 0004:41:00.0: loaded PNVM version 0x881c99e1

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

Title:
  Intel AX210 Wi-Fi card does not work since updating to 1.196

Status in Linux:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Fix Released

Bug description:
  Running 21.04, updated daily.

  Since updating the linux-firmware package yesterday, the Wireless card
  does not work with current kernel (5.11.0-13).

  The error message is as follows:

  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Timeout waiting 
for PNVM load!
  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Failed to start 
RT ucode: -110
  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: 
iwl_trans_send_cmd bad state = 1

  It **does** work with 5.11.0-11 (previous version)

  Distro: Ubuntu 21.04 (Hirsute Hippo)
  Machine:   Type: Laptop System: LENOVO product: 82C5 v: Lenovo V15-IIL
Mobo: LENOVO model: LNVNB161216 v: SDK0J40700 WIN UEFI: LENOVO v: DKCN51WW 
date: 12/23/2020
  CPU:   Info: Dual Core model: Intel Core i3-1005G1 bits: 64 type: MT MCP 
L2 cache: 4 MiB

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


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

[Kernel-packages] [Bug 2015794] Re: Ubuntu 23.04-beta failed to boot on HP x2 Detachable 10 with Intel Atom Cherry Trail x5-Z8350

2023-04-10 Thread Lorca

System is not booting so I'm not able to run the script.

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

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

Title:
  Ubuntu 23.04-beta failed to boot on HP x2 Detachable 10 with Intel
  Atom Cherry Trail x5-Z8350

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Regression started from linux kernel 6.2

  [57.794591] atomisp-isp2 :00:03.0: atomisp: Error -2 while requesting 
firmware shisp_2401a0_v21.bin
  ^ this line was present in dmesg on the old kernels too

  [57.851197] atomisp-isp2 :00:03.0: IUNIT power-off timeout.
  [57.853085] atomisp-isp2 :00:03.0: Failed to switch off ISP
  [84.174915] watchdog: BUG: soft lockup - CPU#3 stuck for 26s! [systemd-udevd: 
1089]

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


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

[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74

2023-04-10 Thread Kodie

Hi ChengEn, Du,

Do we have another issue opened to address the NFS mechanism and the
performance impacts it has on the kernel? We cannot move to the new
kernel currently because of these issues so I just want to make sure we
are continuing to push a solution forward. Thank you!

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

Title:
  NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74

Status in linux package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-aws source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux-aws source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-aws source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-aws source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux-aws source package in Lunar:
  Invalid

Bug description:
  After updating on the kernel 
  5.4.0-144.161 at Ubuntu 18 and 
  5.15.0-67.74 at Ubuntu 20, 
  we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our 
NFS servers.

  All clients are extremely slow when it comes to access to the NFS
  resources.

  Restart and use older kernel, fixed the problem.
  Ubuntu 18 5.4.0-139-generic
  Ubuntu 20 5.15.0-60-Generic
  I don't have a NFS problem with this kernel.

  Problem came with the last releas on March 3rd, 2023
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mär  4 15:00 seq
   crw-rw 1 root audio 116, 33 Mär  4 15:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic 
root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto 
elevator=noop
  ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-67-generic N/A
   linux-backports-modules-5.15.0-67-generic  N/A
   linux-firmware 1.187.36
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal
  Uname: Linux 5.15.0-67-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mär  4 15:03 seq
   crw-rw 1 root audio 116, 33 Mär  4 15:03 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.28
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic 
root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto 
elevator=noop
  ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-43-generic N/A
   linux

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

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

apport-collect 2015794

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

Title:
  Ubuntu 23.04-beta failed to boot on HP x2 Detachable 10 with Intel
  Atom Cherry Trail x5-Z8350

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Regression started from linux kernel 6.2

  [57.794591] atomisp-isp2 :00:03.0: atomisp: Error -2 while requesting 
firmware shisp_2401a0_v21.bin
  ^ this line was present in dmesg on the old kernels too

  [57.851197] atomisp-isp2 :00:03.0: IUNIT power-off timeout.
  [57.853085] atomisp-isp2 :00:03.0: Failed to switch off ISP
  [84.174915] watchdog: BUG: soft lockup - CPU#3 stuck for 26s! [systemd-udevd: 
1089]

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


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

[Kernel-packages] [Bug 2015794] [NEW] Ubuntu 23.04-beta failed to boot on HP x2 Detachable 10 with Intel Atom Cherry Trail x5-Z8350

2023-04-10 Thread Lorca

Public bug reported:

Regression started from linux kernel 6.2

[57.794591] atomisp-isp2 :00:03.0: atomisp: Error -2 while requesting 
firmware shisp_2401a0_v21.bin
^ this line was present in dmesg on the old kernels too

[57.851197] atomisp-isp2 :00:03.0: IUNIT power-off timeout.
[57.853085] atomisp-isp2 :00:03.0: Failed to switch off ISP
[84.174915] watchdog: BUG: soft lockup - CPU#3 stuck for 26s! [systemd-udevd: 
1089]

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

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

Title:
  Ubuntu 23.04-beta failed to boot on HP x2 Detachable 10 with Intel
  Atom Cherry Trail x5-Z8350

Status in linux package in Ubuntu:
  New

Bug description:
  Regression started from linux kernel 6.2

  [57.794591] atomisp-isp2 :00:03.0: atomisp: Error -2 while requesting 
firmware shisp_2401a0_v21.bin
  ^ this line was present in dmesg on the old kernels too

  [57.851197] atomisp-isp2 :00:03.0: IUNIT power-off timeout.
  [57.853085] atomisp-isp2 :00:03.0: Failed to switch off ISP
  [84.174915] watchdog: BUG: soft lockup - CPU#3 stuck for 26s! [systemd-udevd: 
1089]

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


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

[Kernel-packages] [Bug 2015776] Re: 5.17.0-1029-oem-headers incompatible with third party DKMS modules

2023-04-10 Thread Bartłomiej Żogała

The proposed fix is to include those above two symlink in linux-headers
package for compatibility

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

Title:
  5.17.0-1029-oem-headers incompatible with third party DKMS modules

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

Bug description:
  The VMWare kernel modules required to use VMWare Workstation(the specific 
version is 16.2.5 build-20904516) used to work in past by 3rd party script 
automatically compiling modules with DKMS. Since some time it's broken due to 
the DKMS triggered scripts looking for files:
  `/lib/modules/5.17.0-1029-oem/build/include/stddef.h`
  `/lib/modules/5.17.0-1029-oem/build/include/stdarg.h`
  while the files are present in
  `/lib/modules/5.17.0-1029-oem/build/include/linux/`
  directory

  The workaround is to create two symlinks:
  `sudo ln -s linux/stddef.h`
  `sudo ln -s linux/stdarg.h`
  `
  but this causes manual action  required after each kernel breaking the DKMS 
system.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.17.0-1029-oem 5.17.0-1029.30
  ProcVersionSignature: Ubuntu 5.17.0-1029.30-oem 5.17.15
  Uname: Linux 5.17.0-1029-oem x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 10 18:22:50 2023
  InstallationDate: Installed on 2015-05-08 (2894 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-oem-5.17
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2015776] [NEW] 5.17.0-1029-oem-headers incompatible with third party DKMS modules

2023-04-10 Thread Bartłomiej Żogała

Public bug reported:

The VMWare kernel modules required to use VMWare Workstation(the specific 
version is 16.2.5 build-20904516) used to work in past by 3rd party script 
automatically compiling modules with DKMS. Since some time it's broken due to 
the DKMS triggered scripts looking for files:
`/lib/modules/5.17.0-1029-oem/build/include/stddef.h`
`/lib/modules/5.17.0-1029-oem/build/include/stdarg.h`
while the files are present in
`/lib/modules/5.17.0-1029-oem/build/include/linux/`
directory

The workaround is to create two symlinks:
`sudo ln -s linux/stddef.h`
`sudo ln -s linux/stdarg.h`
`
but this causes manual action  required after each kernel breaking the DKMS 
system.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.17.0-1029-oem 5.17.0-1029.30
ProcVersionSignature: Ubuntu 5.17.0-1029.30-oem 5.17.15
Uname: Linux 5.17.0-1029-oem x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 10 18:22:50 2023
InstallationDate: Installed on 2015-05-08 (2894 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-oem-5.17
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-oem-5.17 (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug jammy

** Changed in: linux-signed-oem-5.17 (Ubuntu)
   Status: New => Confirmed

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

Title:
  5.17.0-1029-oem-headers incompatible with third party DKMS modules

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

Bug description:
  The VMWare kernel modules required to use VMWare Workstation(the specific 
version is 16.2.5 build-20904516) used to work in past by 3rd party script 
automatically compiling modules with DKMS. Since some time it's broken due to 
the DKMS triggered scripts looking for files:
  `/lib/modules/5.17.0-1029-oem/build/include/stddef.h`
  `/lib/modules/5.17.0-1029-oem/build/include/stdarg.h`
  while the files are present in
  `/lib/modules/5.17.0-1029-oem/build/include/linux/`
  directory

  The workaround is to create two symlinks:
  `sudo ln -s linux/stddef.h`
  `sudo ln -s linux/stdarg.h`
  `
  but this causes manual action  required after each kernel breaking the DKMS 
system.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.17.0-1029-oem 5.17.0-1029.30
  ProcVersionSignature: Ubuntu 5.17.0-1029.30-oem 5.17.15
  Uname: Linux 5.17.0-1029-oem x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 10 18:22:50 2023
  InstallationDate: Installed on 2015-05-08 (2894 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-oem-5.17
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2012366] Re: NMI: IOCK error on HP MicroServer Gen8 after Focal -> Jammy upgrade

2023-04-10 Thread dv

Just updated to:

5.19.0-38-generic #39~22.04.1-Ubuntu

The same issue persists.

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

Title:
  NMI: IOCK error on HP MicroServer Gen8 after Focal -> Jammy upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After distro upgrade to new LTS "22" from 20 the HP microserver shows
  a critical NMI event in ILO

  Unrecoverable System Error (NMI) has occurred.  System Firmware will
  log additional details in a separate IML entry if possible

  no hp modules are loaded except hpilo:

  lsmod |grep hp
  hpilo  24576  0

  Despite the server is flashing "red" the System is functional. A few
  minutes after boot the kernel shows 4-5 of these kernel panics (see
  full log) but continue to run ok, the NMI flag in ILO appears
  simultaneously to this kernel error. this issue was not present before
  the distro-upgrade.

  [  739.516183] NMI: IOCK error (debug interrupt?) for reason 61 on CPU 0.
  [  739.516190] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.0-67-generic 
#74-Ubuntu
  [  739.516194] Hardware name: HP ProLiant MicroServer Gen8, BIOS J06 
04/04/2019
  [  739.516196] RIP: 0010:mwait_idle_with_hints.constprop.0+0x4f/0xa0

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-67-generic 5.15.0-67.74
  ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85
  Uname: Linux 5.15.0-67-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 23:54 seq
   crw-rw 1 root audio 116, 33 Mar 20 23:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: pass
  Date: Tue Mar 21 09:20:20 2023
  InstallationDate: Installed on 2022-02-16 (397 days ago)
  InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210824)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: HP ProLiant MicroServer Gen8
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgag200drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic 
root=UUID=ce9a2e21-54ae-4461-8086-c62bbcaa1481 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-67-generic N/A
   linux-backports-modules-5.15.0-67-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2023-03-20 (0 days ago)
  dmi.bios.date: 04/04/2019
  dmi.bios.vendor: HP
  dmi.bios.version: J06
  dmi.chassis.type: 7
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 2.82
  dmi.modalias: 
dmi:bvnHP:bvrJ06:bd04/04/2019:efr2.82:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:sku712317-421:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant MicroServer Gen8
  dmi.product.sku: 712317-421
  dmi.sys.vendor: HP

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


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

[Kernel-packages] [Bug 2009910] Re: After updrade (apt), my bluetooth headset microphone doesn't works

2023-04-10 Thread Nick Rosbrook

** Package changed: ubuntu-release-upgrader (Ubuntu) => bluez (Ubuntu)

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

Title:
  After updrade (apt), my bluetooth headset microphone doesn't works

Status in bluez package in Ubuntu:
  New

Bug description:
  Stop working after that upgrade.

  Start-Date: 2023-03-09  19:39:40
  Commandline: packagekit role='update-packages'
  Requested-By: kea (1000)
  Upgrade: udev:amd64 (251.4-1ubuntu7, 251.4-1ubuntu7.1), 
xscreensaver-screensaver-bsod:amd64 (6.02+dfsg1-2ubuntu1, 
6.02+dfsg1-2ubuntu1.2), google-chrome-stable:amd64 (110.0.5481.177-1, 
111.0.5563.64-1), systemd-timesyncd:amd64 (251.4-1ubuntu7, 251.4-1ubuntu7.1), 
xscreensaver-gl-extra:amd64 (6.02+dfsg1-2ubuntu1, 6.02+dfsg1-2ubuntu1.2), 
libpam-systemd:amd64 (251.4-1ubuntu7, 251.4-1ubuntu7.1), 
libyaml-snake-java:amd64 (1.29-1, 1.29-1ubuntu0.22.10.1), libsystemd0:amd64 
(251.4-1ubuntu7, 251.4-1ubuntu7.1), libsystemd0:i386 (251.4-1ubuntu7, 
251.4-1ubuntu7.1), xscreensaver-gl:amd64 (6.02+dfsg1-2ubuntu1, 
6.02+dfsg1-2ubuntu1.2), libnss-systemd:amd64 (251.4-1ubuntu7, 
251.4-1ubuntu7.1), libudev-dev:amd64 (251.4-1ubuntu7, 251.4-1ubuntu7.1), 
systemd:amd64 (251.4-1ubuntu7, 251.4-1ubuntu7.1), libudev1:amd64 
(251.4-1ubuntu7, 251.4-1ubuntu7.1), libudev1:i386 (251.4-1ubuntu7, 
251.4-1ubuntu7.1), xscreensaver:amd64 (6.02+dfsg1-2ubuntu1, 
6.02+dfsg1-2ubuntu1.2), systemd-resolved:amd64 (251.4-1ubuntu7, 251
 .4-1ubuntu7.1), xscreensaver-data:amd64 (6.02+dfsg1-2ubuntu1, 
6.02+dfsg1-2ubuntu1.2), libsystemd-shared:amd64 (251.4-1ubuntu7, 
251.4-1ubuntu7.1), systemd-sysv:amd64 (251.4-1ubuntu7, 251.4-1ubuntu7.1), 
xscreensaver-data-extra:amd64 (6.02+dfsg1-2ubuntu1, 6.02+dfsg1-2ubuntu1.2), 
signal-desktop:amd64 (6.8.0, 6.9.0)
  End-Date: 2023-03-09  19:40:21

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: ubuntu-release-upgrader-core 1:22.10.8
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Thu Mar  9 21:58:06 2023
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to kinetic on 2023-02-10 (27 days ago)
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting

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


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

[Kernel-packages] [Bug 2009910] [NEW] After updrade (apt), my bluetooth headset microphone doesn't works

You have been subscribed to a public bug:

Stop working after that upgrade.

Start-Date: 2023-03-09  19:39:40
Commandline: packagekit role='update-packages'
Requested-By: kea (1000)
Upgrade: udev:amd64 (251.4-1ubuntu7, 251.4-1ubuntu7.1), 
xscreensaver-screensaver-bsod:amd64 (6.02+dfsg1-2ubuntu1, 
6.02+dfsg1-2ubuntu1.2), google-chrome-stable:amd64 (110.0.5481.177-1, 
111.0.5563.64-1), systemd-timesyncd:amd64 (251.4-1ubuntu7, 251.4-1ubuntu7.1), 
xscreensaver-gl-extra:amd64 (6.02+dfsg1-2ubuntu1, 6.02+dfsg1-2ubuntu1.2), 
libpam-systemd:amd64 (251.4-1ubuntu7, 251.4-1ubuntu7.1), 
libyaml-snake-java:amd64 (1.29-1, 1.29-1ubuntu0.22.10.1), libsystemd0:amd64 
(251.4-1ubuntu7, 251.4-1ubuntu7.1), libsystemd0:i386 (251.4-1ubuntu7, 
251.4-1ubuntu7.1), xscreensaver-gl:amd64 (6.02+dfsg1-2ubuntu1, 
6.02+dfsg1-2ubuntu1.2), libnss-systemd:amd64 (251.4-1ubuntu7, 
251.4-1ubuntu7.1), libudev-dev:amd64 (251.4-1ubuntu7, 251.4-1ubuntu7.1), 
systemd:amd64 (251.4-1ubuntu7, 251.4-1ubuntu7.1), libudev1:amd64 
(251.4-1ubuntu7, 251.4-1ubuntu7.1), libudev1:i386 (251.4-1ubuntu7, 
251.4-1ubuntu7.1), xscreensaver:amd64 (6.02+dfsg1-2ubuntu1, 
6.02+dfsg1-2ubuntu1.2), systemd-resolved:amd64 (251.4-1ubuntu7, 251.4
 -1ubuntu7.1), xscreensaver-data:amd64 (6.02+dfsg1-2ubuntu1, 
6.02+dfsg1-2ubuntu1.2), libsystemd-shared:amd64 (251.4-1ubuntu7, 
251.4-1ubuntu7.1), systemd-sysv:amd64 (251.4-1ubuntu7, 251.4-1ubuntu7.1), 
xscreensaver-data-extra:amd64 (6.02+dfsg1-2ubuntu1, 6.02+dfsg1-2ubuntu1.2), 
signal-desktop:amd64 (6.8.0, 6.9.0)
End-Date: 2023-03-09  19:40:21

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: ubuntu-release-upgrader-core 1:22.10.8
ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
Uname: Linux 5.19.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CrashDB: ubuntu
CurrentDesktop: KDE
Date: Thu Mar  9 21:58:06 2023
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to kinetic on 2023-02-10 (27 days ago)
VarLogDistupgradeXorgFixuplog:
 INFO:root:/usr/bin/do-release-upgrade running
 INFO:root:No xorg.conf, exiting

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


** Tags: amd64 apport-bug dist-upgrade kinetic
-- 
After updrade (apt), my bluetooth headset microphone doesn't works
https://bugs.launchpad.net/bugs/2009910
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to bluez in Ubuntu.

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

[Kernel-packages] [Bug 2015765] Re: autopkgtests fail with "EE: Missing modules"

2023-04-10 Thread Mauricio Faria de Oliveira

Apparently, the check for (non-ignored) modules might be inexact? as both 
'mstflint_access' and 'nvidia-fs' are in the linux-modules-*-nvidia deb package.
(Note: this is just a su-guess-tion :) I haven't looked at it.)

$ dpkg-deb -c linux-modules-5.15.0-1017-nvidia_5.15.0-1017.17_amd64.deb | grep 
-i mstflint.access
drwxr-xr-x root/root 0 2023-02-01 00:00 
./lib/modules/5.15.0-1017-nvidia/kernel/mstflint_access/
-rw-r--r-- root/root 46409 2023-02-01 00:00 
./lib/modules/5.15.0-1017-nvidia/kernel/mstflint_access/mstflint_access.ko

$ dpkg-deb -c linux-modules-5.15.0-1018-nvidia_5.15.0-1018.18_amd64.deb | grep 
-i mstflint.access
drwxr-xr-x root/root 0 2023-03-06 17:20 
./lib/modules/5.15.0-1018-nvidia/kernel/mstflint_access/
-rw-r--r-- root/root 46409 2023-03-06 17:20 
./lib/modules/5.15.0-1018-nvidia/kernel/mstflint_access/mstflint_access.ko

$ dpkg-deb -c linux-modules-5.15.0-1017-nvidia_5.15.0-1017.17_amd64.deb | grep 
-i nvidia.fs
drwxr-xr-x root/root 0 2023-02-01 00:00 
./lib/modules/5.15.0-1017-nvidia/kernel/nvidia-fs/
-rw-r--r-- root/root219921 2023-02-01 00:00 
./lib/modules/5.15.0-1017-nvidia/kernel/nvidia-fs/nvidia-fs.ko

$ dpkg-deb -c linux-modules-5.15.0-1018-nvidia_5.15.0-1018.18_amd64.deb | grep 
-i nvidia.fs
drwxr-xr-x root/root 0 2023-03-06 17:20 
./lib/modules/5.15.0-1018-nvidia/kernel/nvidia-fs/
-rw-r--r-- root/root219921 2023-03-06 17:20 
./lib/modules/5.15.0-1018-nvidia/kernel/nvidia-fs/nvidia-fs.ko


** Tags added: update-excuse-jammy

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

Title:
  autopkgtests fail with "EE: Missing modules"

Status in linux-nvidia package in Ubuntu:
  New

Bug description:
  II: Checking modules for nvidia...
  read 12 modules.
 reading new modules...read 6315 modules.
 reading old modules...
MISS: icp (ignored)
MISS: mstflint_access
MISS: nvidia-fs
MISS: spl (ignored)
MISS: v4l2loopback (ignored)
MISS: zavl (ignored)
MISS: zcommon (ignored)
MISS: zfs (ignored)
MISS: zlua (ignored)
MISS: znvpair (ignored)
MISS: zunicode (ignored)
MISS: zzstd (ignored)
NEW: 8250
  ...
NEW: zswap
read 6017 modules : new(310)  missing(12)
  EE: Missing modules
  make: *** [debian/rules.d/4-checks.mk:10: module-check-nvidia] Error 1
  dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2
  autopkgtest [01:49:45]: test rebuild: ---]
  autopkgtest [01:49:45]: test rebuild:  - - - - - - - - - - results - - - - - 
- - - - -
  rebuild  FAIL non-zero exit status 2

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


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

[Kernel-packages] [Bug 2015765] [NEW] autopkgtests fail with "EE: Missing modules"

2023-04-10 Thread Mauricio Faria de Oliveira

Public bug reported:

II: Checking modules for nvidia...
read 12 modules.
   reading new modules...read 6315 modules.
   reading old modules...
  MISS: icp (ignored)
  MISS: mstflint_access
  MISS: nvidia-fs
  MISS: spl (ignored)
  MISS: v4l2loopback (ignored)
  MISS: zavl (ignored)
  MISS: zcommon (ignored)
  MISS: zfs (ignored)
  MISS: zlua (ignored)
  MISS: znvpair (ignored)
  MISS: zunicode (ignored)
  MISS: zzstd (ignored)
  NEW: 8250
...
  NEW: zswap
  read 6017 modules : new(310)  missing(12)
EE: Missing modules
make: *** [debian/rules.d/4-checks.mk:10: module-check-nvidia] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit 
status 2
autopkgtest [01:49:45]: test rebuild: ---]
autopkgtest [01:49:45]: test rebuild:  - - - - - - - - - - results - - - - - - 
- - - -
rebuild  FAIL non-zero exit status 2

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


** Tags: update-excuse-jammy

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

Title:
  autopkgtests fail with "EE: Missing modules"

Status in linux-nvidia package in Ubuntu:
  New

Bug description:
  II: Checking modules for nvidia...
  read 12 modules.
 reading new modules...read 6315 modules.
 reading old modules...
MISS: icp (ignored)
MISS: mstflint_access
MISS: nvidia-fs
MISS: spl (ignored)
MISS: v4l2loopback (ignored)
MISS: zavl (ignored)
MISS: zcommon (ignored)
MISS: zfs (ignored)
MISS: zlua (ignored)
MISS: znvpair (ignored)
MISS: zunicode (ignored)
MISS: zzstd (ignored)
NEW: 8250
  ...
NEW: zswap
read 6017 modules : new(310)  missing(12)
  EE: Missing modules
  make: *** [debian/rules.d/4-checks.mk:10: module-check-nvidia] Error 1
  dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2
  autopkgtest [01:49:45]: test rebuild: ---]
  autopkgtest [01:49:45]: test rebuild:  - - - - - - - - - - results - - - - - 
- - - - -
  rebuild  FAIL non-zero exit status 2

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


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

[Kernel-packages] [Bug 2015755] [NEW] Pull-request to address mgbe ethernet driver on AGX Orin

2023-04-10 Thread Brad Figg

Public bug reported:

[Impact]
This patch set is intended to address 
https://bugs.launchpad.net/riverside/+bug/2011636

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

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

Title:
  Pull-request to address mgbe ethernet driver on AGX Orin

Status in linux-nvidia package in Ubuntu:
  New

Bug description:
  [Impact]
  This patch set is intended to address 
https://bugs.launchpad.net/riverside/+bug/2011636

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


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

[Kernel-packages] [Bug 2007369] Re: Intel AX210 wifi card "Failed to run INIT ucode: -110" after linux-firmware upgraded to 20220329.git681281e4-0ubuntu3.10

2023-04-10 Thread Eduard

Hello, I have the same problem, with a lot of linux-firmware versions. 
I have found this issue also with 
linux-firmware-20220329.git681281e4-0ubuntu3.12.

After upgrading linux-firmware lib, I always have to use this command
`sudo mv /usr/lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm
/usr/lib/firmware/iwlwifi-ty-a0-gf-a0.bak`
(https://askubuntu.com/questions/1360175/intel-wifi-6-ax210-wifi-not-
working-after-update), and after this command, Wi-Fi module works.

I have the same logs as other users have above.

- linux-firmware-20220329.git681281e4-0ubuntu3.12
- Linux version 5.10.110-rockchip-rk3588 (aarch64-linux-gnu-gcc (Ubuntu 
9.4.0-1ubuntu1~20.04.1) 9.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1 SMP 
Wed Mar 29 08:28:12 BST 2023


00:34:55 kernel: iwlwifi 0004:41:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, 
REV=0x420
00:34:55 kernel: iwlwifi 0004:41:00.0: Failed to run INIT ucode: -110
00:34:55 kernel: iwlwifi 0004:41:00.0: iwl_trans_send_cmd bad state = 0
00:34:54 kernel: iwlwifi 0004:41:00.0: loaded PNVM version 0x881c99e1

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

Title:
  Intel AX210 wifi card "Failed to run INIT ucode: -110" after linux-
  firmware upgraded to 20220329.git681281e4-0ubuntu3.10

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  Xubuntu 22.04.1 LTS running 5.15.0-60-generic kernel.
  On last 'dist-upgrade' following packages get upgraded (according to 
/var/log/apt/history.log):

  gir1.2-javascriptcoregtk-4.0:amd64 (2.38.3-0ubuntu0.22.04.1, 
2.38.4-0ubuntu0.22.04.1), gir1.2-webkit2-4.0:amd64 (2.38.3-0ubuntu0.22.04.1, 
2.38.4-0ubuntu0.22.04.1), libjavascriptcoregtk-4.0-18:amd64 
(2.38.3-0ubuntu0.22.04.1, 2.38.4-0ubuntu0.22.04.1), linux-firmware:amd64 
(20220329.git681281e4-0ubuntu3.9, 20220329.git681281e4-0ubuntu3.10), 
libwebkit2gtk-4.0-37:amd64 (2.38.3-0ubuntu0.22.04.1, 2.38.4-0ubuntu0.22.04.1)
  End-Date: 2023-02-14  00:02:47

  One of this was linux-firmware package. I 'lost' my wifi connectivity.

  dmesg|grep iwlwifi shows:

  [   10.678853] iwlwifi :01:00.0: enabling device ( -> 0002)
  [   10.691307] iwlwifi :01:00.0: api flags index 2 larger than supported 
by driver
  [   10.691325] iwlwifi :01:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 
0.63.2.2
  [   10.691602] iwlwifi :01:00.0: loaded firmware version 66.f1c864e0.0 
ty-a0-gf-a0-66.ucode op_mode iwlmvm
  [   10.840186] iwlwifi :01:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, 
REV=0x420
  [   11.852608] iwlwifi :01:00.0: SecBoot CPU1 Status: 0x7663, CPU2 
Status: 0xb03
  [   11.852635] iwlwifi :01:00.0: UMAC PC: 0x8047f600
  [   11.852656] iwlwifi :01:00.0: LMAC PC: 0x0
  [   11.852659] iwlwifi :01:00.0: WRT: Collecting data: ini trigger 13 
fired (delay=0ms).
  [   11.852866] iwlwifi :01:00.0: Loaded firmware version: 66.f1c864e0.0 
ty-a0-gf-a0-66.ucode
  [   11.852870] iwlwifi :01:00.0: 0x | ADVANCED_SYSASSERT  
  [   11.852874] iwlwifi :01:00.0: 0x | trm_hw_status0
  [   11.852876] iwlwifi :01:00.0: 0x | trm_hw_status1
  [   11.852878] iwlwifi :01:00.0: 0x | branchlink2
  [   11.852881] iwlwifi :01:00.0: 0x | interruptlink1
  [   11.852883] iwlwifi :01:00.0: 0x | interruptlink2
  [   11.852885] iwlwifi :01:00.0: 0x | data1
  [   11.852887] iwlwifi :01:00.0: 0x | data2
  [   11.852890] iwlwifi :01:00.0: 0x | data3
  [   11.852892] iwlwifi :01:00.0: 0x | beacon time
  [   11.852894] iwlwifi :01:00.0: 0x | tsf low
  [   11.852896] iwlwifi :01:00.0: 0x | tsf hi
  [   11.852898] iwlwifi :01:00.0: 0x | time gp1
  [   11.852901] iwlwifi :01:00.0: 0x | time gp2
  [   11.852903] iwlwifi :01:00.0: 0x | uCode revision type
  [   11.852906] iwlwifi :01:00.0: 0x | uCode version major
  [   11.852908] iwlwifi :01:00.0: 0x | uCode version minor
  [   11.852910] iwlwifi :01:00.0: 0x | hw version
  [   11.852913] iwlwifi :01:00.0: 0x | board version
  [   11.852915] iwlwifi :01:00.0: 0x | hcmd
  [   11.852918] iwlwifi :01:00.0: 0x | isr0
  [   11.852920] iwlwifi :01:00.0: 0x | isr1
  [   11.852922] iwlwifi :01:00.0: 0x | isr2
  [   11.852924] iwlwifi :01:00.0: 0x | isr3
  [   11.852926] iwlwifi :01:00.0: 0x | isr4
  [   11.852928] iwlwifi :01:00.0: 0x | last cmd Id
  [   11.852930] iwlwifi :01:00.0: 0x | wait_event
  [   11.852933] iwlwifi :01:00.0: 0x | l2p_control
  [   11.852935] iwlwifi :01:00.0: 0x | l2p_duration
  [   11.852937] iwlwifi :01:00.0: 0x | l2p_mhvalid
  [   11.852940] iwlwifi :01:00.0: 0x | l2p_addr_match
  [   11.852942] iwlwifi :01:00.0: 0x

[Kernel-packages] [Bug 1988364] Re: Missing the A2DP profile and defaults to low quality

2023-04-10 Thread Rafael K.

I just removed my WF-1000XM4 from my device list and paired them again.
Now I have "High Fidelity Playback (A2DP Sink, codec LDAC)" and it was selected 
by default.

I have no idea what changed. bluez is still 5.64 since 2022-08-28. Maybe
it's related to the blueman update from 2.3.4 to 2.3.5 on 2023-01-19 or
some pipewire update on 2023-01-12.

These are my current bluez related packages:
bluez-alsa-utils/jammy 3.0.0-2 amd64
bluez-btsco/jammy 1:0.50-0ubuntu7 amd64
bluez-cups/jammy,now 5.64-0ubuntu1 amd64 [installed]
bluez-firmware/jammy,jammy 1.2-7 all
bluez-hcidump/jammy 5.64-0ubuntu1 amd64
bluez-hcidump/jammy 5.64-0ubuntu1 i386
bluez-meshd/jammy 5.64-0ubuntu1 amd64
bluez-meshd/jammy 5.64-0ubuntu1 i386
bluez-obexd/jammy,now 5.64-0ubuntu1 amd64 [installed]
bluez-obexd/jammy 5.64-0ubuntu1 i386
bluez-tests/jammy 5.64-0ubuntu1 amd64
bluez-tests/jammy 5.64-0ubuntu1 i386
bluez-tools/jammy,now 2.0~20170911.0.7cb788c-4 amd64 [installed]
bluez/jammy,now 5.64-0ubuntu1 amd64 [installed]
bluez/jammy 5.64-0ubuntu1 i386
libasound2-plugin-bluez/jammy 3.0.0-2 amd64
libkf5bluezqt-data/jammy,jammy 5.92.0-0ubuntu1 all
libkf5bluezqt-dev/jammy 5.92.0-0ubuntu1 amd64
libkf5bluezqt-doc/jammy,jammy 5.92.0-0ubuntu1 all
libkf5bluezqt6/jammy 5.92.0-0ubuntu1 amd64
python3-bluez/jammy 0.23-4build1 amd64
qml-module-org-kde-bluezqt/jammy 5.92.0-0ubuntu1 amd64

So it seems it's somehow unrelated to bluez 5.65

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

Title:
  Missing the A2DP profile and defaults to low quality

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Jammy:
  In Progress
Status in bluez source package in Kinetic:
  Fix Released
Status in bluez source package in Lunar:
  Fix Released

Bug description:
  [ Impact ]

  Sony WH-1000XM4 missing the A2DP profile and defaults to low quality.
  Probably other headphone types would be affected too.

  https://github.com/bluez/bluez/issues/313

  [ Test Plan ]

  No verifiable test case yet. Will ask the community for testing, and
  if it fails then consider reverting the fix.

  [ Where problems could occur ]

  The fix touches Bluetooth audio logic (only). So anything relating to
  Bluetooth audio (A2DP) is the main risk. A secondary risk is the rest
  of bluetoothd which could suffer side effects.

  [ Other Info ]

  None provided.

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


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

[Kernel-packages] [Bug 2007001] Re: Blank console display with aarch64 kernel 5.19.0-31

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

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

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

Title:
  Blank console display with aarch64 kernel 5.19.0-31

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

Bug description:
  Upgraded the kernel on 22.10 aarch64 (running in a VM on VMware Fusion
  13.0.1 on Apple Silicon_ from 5.19.0-29 to 5.19.0-31. After the
  upgrade and after rebooting the VM no text or graphical console
  appears on the VM.

  The VM is running and can be accessed through SSH.

  Rebooting the VM with kernel 5.19.0-29 - everything is working as
  expected. Text and graphical consoles now display properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-31-generic 5.19.0-31.32
  ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17
  Uname: Linux 5.19.0-31-generic aarch64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: arm64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Sat Feb 11 13:04:22 2023
  InstallationDate: Installed on 2022-09-11 (153 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha arm64 (20220911)
  IwConfig:
   lono wireless extensions.
   
   ens160no wireless extensions.
  MachineType: VMware, Inc. VMware20,1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic 
root=UUID=5e9795ee-63e3-4df1-93e9-c36cd88c726c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-31-generic N/A
   linux-backports-modules-5.19.0-31-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2022
  dmi.bios.vendor: VMware, Inc.
  dmi.bios.version: VMW201.00V.20904234.BA64.2212051119
  dmi.board.name: VBSA
  dmi.board.vendor: VMware, Inc.
  dmi.board.version: 1
  dmi.chassis.type: 1
  dmi.chassis.vendor: VMware, Inc.
  dmi.chassis.version: VMware20,1
  dmi.modalias: 
dmi:bvnVMware,Inc.:bvrVMW201.00V.20904234.BA64.2212051119:bd12/05/2022:svnVMware,Inc.:pnVMware20,1:pvr1:rvnVMware,Inc.:rnVBSA:rvr1:cvnVMware,Inc.:ct1:cvrVMware20,1:sku0001:
  dmi.product.family: VMware
  dmi.product.name: VMware20,1
  dmi.product.sku: 0001
  dmi.product.version: 1
  dmi.sys.vendor: VMware, Inc.

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


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

[Kernel-packages] [Bug 1987829] Re: LG Gram 12gen high CPU use when USB-C/TB is in use

2023-04-10 Thread Pixel

Hello everyone,

I have been following this thread for a while now, but have not yet seen
others report the same thing I am experiencing. I am using an LG Gram
14Z90Q-G.AA76B and have experienced high CPU usage from kworker threads
on every distro I have tried (Fedora, ArchLinux, VanillaOS, Ubuntu).
>From my experience, there is a somewhat reliable way to temporarily stop
the high CPU usage. I don't dualboot windows, so I cannot test the
suggestion of booting from windows to linux. Rather, I have noticed the
following pattern:

1. Plug In USB-C cable (charging/HDMI)
2. Run "top" to verify that 3 kworker threads appear with high CPU usage. The 
fan will eventually kick in
3. Suspend the laptop (close the lid, press power button, press Fn+s, or 
manually suspend) and wait for the fan to completely turn off. Optionally 
unplug and plug in USB-C cable (sometimes helps).
4. Wake device from sleep.
5. Run "top" again, kworkers will be gone

Now this does not work 100% of the time, as sometimes after waking from
sleep the device still keeps the kworker threads up and running, but
eventually after doing this they disappear until the next reboot. This
workaround gets the job done for me, as long as I don't have to reboot
often.

Will share these findings on the bugzilla site as well.

Hope it helps

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

Title:
  LG Gram 12gen high CPU use when USB-C/TB is in use

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

Bug description:
  LG Gram laptop 17Z90Q with a Core i7-1260P CPU.

  Whenever an external monitor is connected to USB-C/Thunderbolt 4,
  average load goes above 3.0 and the machine is getting very hot.

  Output from top -H shows a lot of kworker CPU usage:

  top - 11:45:06 up 33 min,  2 users,  load average: 3,30, 3,08, 2,79
  Threads: 1442 total,   2 running, 1440 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0,1 us,  3,7 sy,  0,0 ni, 96,1 id,  0,0 wa,  0,0 hi,  0,1 si,  0,0 
st
  MiB Mem :  15684,6 total,   8510,2 free,   2580,8 used,   4593,6 buff/cache
  MiB Swap:   3815,0 total,   3815,0 free,  0,0 used.  11326,9 avail Mem 

  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ WCHAN  
COMMAND
 7766 root  20   0   0  0  0 R  19,8   0,0   0:56.05 
worker_th+ kworker/0:2-events
  196 root  20   0   0  0  0 D  15,8   0,0   1:18.12 
ec_guard   kworker/u32:2+USBC000:00-con0
10237 root  20   0   0  0  0 I  12,9   0,0   0:26.44 
worker_th+ kworker/0:0-events
 1027 root  20   0   0  0  0 I   6,6   0,0   0:43.30 
worker_th+ kworker/1:3-events
10971 root  20   0   0  0  0 I   4,0   0,0   0:00.20 
worker_th+ kworker/15:0-events
  175 root  20   0   0  0  0 I   2,3   0,0   0:03.24 
worker_th+ kworker/11:1-events
 2410 root  20   0   0  0  0 I   1,7   0,0   0:05.49 
worker_th+ kworker/9:3-events

  Perf shows a lot of time spent inside
  handle_irq_event/acpi_ev_gpe_detect/acpi_hw_gpe_read.

  Additionally, kernel log is getting spammed with these lines every 4
  seconds (but also without any USB-C device attached):

  [  223.514304] ACPI Error: No handler for Region [XIN1] (f2ad4f1f) 
[UserDefinedRegion] (20210730/evregion-130)
  [  223.514323] ACPI Error: Region UserDefinedRegion (ID=143) has no handler 
(20210730/exfldio-261)

  [  223.514337] 
 Initialized Local Variables for Method [_TMP]:
  [  223.514339]   Local0: 21495082Integer 
0034

  [  223.514349] No Arguments are initialized for method [_TMP]

  [  223.514354] ACPI Error: Aborting method
  \_SB.PC00.LPCB.LGEC.SEN2._TMP due to previous error (AE_NOT_EXIST)
  (20210730/psparse-529)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-46-generic 5.15.0-46.49
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  me 1678 F pulseaudio
   /dev/snd/controlC1:  me 1678 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Fri Aug 26 11:57:05 2022
  InstallationDate: Installed on 2022-08-25 (1 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LG Electronics 17Z90Q-G.AA78N
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=e2f96916-a67c-432e-b687-730071271216 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A

[Kernel-packages] [Bug 2000778] Re: pmtu.sh in net from ubunut_kernel_selftests crash SUT with K-5.19

I just noticed that we have this hint for Lunar as well, I will revert
the bug status to incomplete to verify it.

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

** Changed in: linux (Ubuntu)
   Status: Invalid => 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/2000778

Title:
  pmtu.sh in net from ubunut_kernel_selftests crash SUT with K-5.19

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

Bug description:
  Issue found with Kinetic 5.19.0-27.28 and 5.19.0-28.29 in this cycle 
(20221114) on these SUTs
   * P9 baltar
   * ARM64 kuzzle
   * ARM64 howzit-kernel

  This should not be considered as a regression as the net test cannot
  be built in 5.19.0-24.25

  
  Test log:
  
ubuntu@baltar:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$
 sudo ./pmtu.sh
  TEST: ipv4: PMTU exceptions [ OK ]
  TEST: ipv4: PMTU exceptions - nexthop objects   [ OK ]
  TEST: ipv6: PMTU exceptions [ OK ]
  TEST: ipv6: PMTU exceptions - nexthop objects   [ OK ]
  TEST: ICMPv4 with DSCP and ECN: PMTU exceptions [ OK ]
  TEST: ICMPv4 with DSCP and ECN: PMTU exceptions - nexthop objects   [ OK ]
  'socat' command not found; skipping tests
  TEST: UDPv4 with DSCP and ECN: PMTU exceptions  [SKIP]
  TEST: IPv4 over vxlan4: PMTU exceptions [ OK ]
  TEST: IPv4 over vxlan4: PMTU exceptions - nexthop objects   [ OK ]
  TEST: IPv6 over vxlan4: PMTU exceptions [ OK ]
  TEST: IPv6 over vxlan4: PMTU exceptions - nexthop objects   [ OK ]
  TEST: IPv4 over vxlan6: PMTU exceptions [ OK ]
  TEST: IPv4 over vxlan6: PMTU exceptions - nexthop objects   [ OK ]
  TEST: IPv6 over vxlan6: PMTU exceptions [ OK ]
  TEST: IPv6 over vxlan6: PMTU exceptions - nexthop objects   [ OK ]
  TEST: IPv4 over geneve4: PMTU exceptions[ OK ]
  TEST: IPv4 over geneve4: PMTU exceptions - nexthop objects  [ OK ]
  TEST: IPv6 over geneve4: PMTU exceptions[ OK ]
  TEST: IPv6 over geneve4: PMTU exceptions - nexthop objects  [ OK ]
  TEST: IPv4 over geneve6: PMTU exceptions[ OK ]
  TEST: IPv4 over geneve6: PMTU exceptions - nexthop objects  [ OK ]
  TEST: IPv6 over geneve6: PMTU exceptions[ OK ]
  TEST: IPv6 over geneve6: PMTU exceptions - nexthop objects  [ OK ]
  TEST: IPv4, bridged vxlan4: PMTU exceptions [ OK ]
  TEST: IPv4, bridged vxlan4: PMTU exceptions - nexthop objects   [ OK ]
  TEST: IPv6, bridged vxlan4: PMTU exceptions [ OK ]
  TEST: IPv6, bridged vxlan4: PMTU exceptions - nexthop objects   [ OK ]
  TEST: IPv4, bridged vxlan6: PMTU exceptions [ OK ]
  TEST: IPv4, bridged vxlan6: PMTU exceptions - nexthop objects   [ OK ]
  TEST: IPv6, bridged vxlan6: PMTU exceptions [ OK ]
  TEST: IPv6, bridged vxlan6: PMTU exceptions - nexthop objects   [ OK ]
  TEST: IPv4, bridged geneve4: PMTU exceptions[ OK ]
  TEST: IPv4, bridged geneve4: PMTU exceptions - nexthop objects  [ OK ]
  TEST: IPv6, bridged geneve4: PMTU exceptions[ OK ]
  TEST: IPv6, bridged geneve4: PMTU exceptions - nexthop objects  [ OK ]
  TEST: IPv4, bridged geneve6: PMTU exceptions[ OK ]
  TEST: IPv4, bridged geneve6: PMTU exceptions - nexthop objects  [ OK ]
  TEST: IPv6, bridged geneve6: PMTU exceptions[ OK ]
  TEST: IPv6, bridged geneve6: PMTU exceptions - nexthop objects  [ OK ]
ovs_bridge not supported
  TEST: IPv4, OVS vxlan4: PMTU exceptions [SKIP]
ovs_bridge not supported
  TEST: IPv6, OVS vxlan4: PMTU exceptions [SKIP]
ovs_bridge not supported
  TEST: IPv4, OVS vxlan6: PMTU exceptions [SKIP]
ovs_bridge not supported
  TEST: IPv6, OVS vxlan6: PMTU exceptions [SKIP]
ovs_bridge not supported
  TEST: IPv4, OVS geneve4: PMTU exceptions[SKIP]
ovs_bridge not supported
  TEST: IPv6, OVS geneve4: PMTU exceptions[SKIP]
ovs_bridge not supported
  TEST: IPv4, OVS geneve6: PMTU exceptions[SKIP]
ovs_bridge not supported
  TEST: IPv6, OVS geneve6: PMTU exceptions[SKIP]
  TEST: IPv4 over fou4: PMTU exceptions

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

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

apport-collect 2015741

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

Title:
  memfd:run_fuse_test.sh in ubuntu_kernel_selftests crash L-6.2 ARM64

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

Bug description:
  Issue found on 6.2.0-20.20 ARM64 instances.

  Looks like the memfd:run_fuse_test.sh will never finish properly and
  the whole test will be interrupted abnormally.

  Test log:
   Running 'make run_tests -C memfd TEST_PROGS=run_fuse_test.sh 
TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
   make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd'
   TAP version 13
   1..1
   # selftests: memfd: run_fuse_test.sh
  sut-test TEST SYSTEM FAILURE DETECTED Test results file 
'/home/maas/workspace/lunar-linux-generic-arm64-6.2.0-dazzle-ubuntu_kernel_selftests/kernel-results.xml'
 not found.

  This issue can be found since 6.2.0-19.19

  6.2.0-18.18 works fine:
   Running 'make run_tests -C memfd TEST_PROGS=run_fuse_test.sh 
TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
   make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd'
   TAP version 13
   1..1
   # selftests: memfd: run_fuse_test.sh
   # opening: ./mnt/memfd
   # fuse: DONE
   ok 1 selftests: memfd: run_fuse_test.sh
   make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd'
  GOODubuntu_kernel_selftests.memfd:run_fuse_test.sh
ubuntu_kernel_selftests.memfd:run_fuse_test.shtimestamp=1679321878
localtime=Mar 20 14:17:58completed successfully

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


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

[Kernel-packages] [Bug 2015741] [NEW] memfd:run_fuse_test.sh in ubuntu_kernel_selftests crash L-6.2 ARM64

Public bug reported:

Issue found on 6.2.0-20.20 ARM64 instances.

Looks like the memfd:run_fuse_test.sh will never finish properly and the
whole test will be interrupted abnormally.

Test log:
 Running 'make run_tests -C memfd TEST_PROGS=run_fuse_test.sh TEST_GEN_PROGS='' 
TEST_CUSTOM_PROGS='''
 make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd'
 TAP version 13
 1..1
 # selftests: memfd: run_fuse_test.sh
sut-test TEST SYSTEM FAILURE DETECTED Test results file 
'/home/maas/workspace/lunar-linux-generic-arm64-6.2.0-dazzle-ubuntu_kernel_selftests/kernel-results.xml'
 not found.

This issue can be found since 6.2.0-19.19

6.2.0-18.18 works fine:
 Running 'make run_tests -C memfd TEST_PROGS=run_fuse_test.sh TEST_GEN_PROGS='' 
TEST_CUSTOM_PROGS='''
 make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd'
 TAP version 13
 1..1
 # selftests: memfd: run_fuse_test.sh
 # opening: ./mnt/memfd
 # fuse: DONE
 ok 1 selftests: memfd: run_fuse_test.sh
 make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd'
GOODubuntu_kernel_selftests.memfd:run_fuse_test.sh
ubuntu_kernel_selftests.memfd:run_fuse_test.shtimestamp=1679321878
localtime=Mar 20 14:17:58completed successfully

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

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


** Tags: 6.2 arm64 lunar ubuntu-kernel-selftests

** Tags added: 6.2 arm64 lunar ubuntu-kernel-selftests

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

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

Title:
  memfd:run_fuse_test.sh in ubuntu_kernel_selftests crash L-6.2 ARM64

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

Bug description:
  Issue found on 6.2.0-20.20 ARM64 instances.

  Looks like the memfd:run_fuse_test.sh will never finish properly and
  the whole test will be interrupted abnormally.

  Test log:
   Running 'make run_tests -C memfd TEST_PROGS=run_fuse_test.sh 
TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
   make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd'
   TAP version 13
   1..1
   # selftests: memfd: run_fuse_test.sh
  sut-test TEST SYSTEM FAILURE DETECTED Test results file 
'/home/maas/workspace/lunar-linux-generic-arm64-6.2.0-dazzle-ubuntu_kernel_selftests/kernel-results.xml'
 not found.

  This issue can be found since 6.2.0-19.19

  6.2.0-18.18 works fine:
   Running 'make run_tests -C memfd TEST_PROGS=run_fuse_test.sh 
TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
   make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd'
   TAP version 13
   1..1
   # selftests: memfd: run_fuse_test.sh
   # opening: ./mnt/memfd
   # fuse: DONE
   ok 1 selftests: memfd: run_fuse_test.sh
   make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd'
  GOODubuntu_kernel_selftests.memfd:run_fuse_test.sh
ubuntu_kernel_selftests.memfd:run_fuse_test.shtimestamp=1679321878
localtime=Mar 20 14:17:58completed successfully

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


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

[Kernel-packages] [Bug 2009243] Re: kernel 5.19.0-35 clobbers Creative S/B AE-7 Sound Card

2023-04-10 Thread Oscaruzzo

It still happens with 5.19.0-38-generic. alsa-info says:

!!Soundcards recognised by ALSA
!!-

0 [NVidia ]: HDA-Intel - HDA NVidia
HDA NVidia at 0xa308 irq 17

!!PCI Soundcards installed in the system
!!--

01:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:228e] (rev a1)
Subsystem: ASUSTeK Computer Inc. Device [1043:881d]
03:00.0 Audio device [0403]: Creative Labs Sound Core3D [Sound Blaster Recon3D
/ Z-Series] [1102:0012] (rev 01)
Subsystem: Creative Labs Sound Core3D [Sound Blaster Recon3D /
Z-Series] [1102:0191]

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

Title:
kernel 5.19.0-35 clobbers Creative S/B AE-7 Sound Card

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

Bug description:
2023-03-03
Attempted install of kernel 5.19.0-35 using the Linux Mint package installer
LM 21.1 Vera, release 21.1).
Clobbered my Sound Blaster AE-7.
Could not even locate the device using Sound manager utility on Linux Mint
Panel (the enumerated device showed up as the embedded sound chip on the mobo
which I had previously disabled in the UEFI setup).
Uninstalled kernel and reverted back to 5.19.0-32 using Timeshift restore
feature which worked fine before the update to 5.19.0-35.
Tried again to install 5.19.0-35 the same way, just to be sure.
The SB AE-7 got clobbered again.
So restored back to 5.19.0-32 generic one more time, using Timeshift. SB AE-7
works fine now with this lower version kernel.
Current hardware config:

Asus Prime Z790-P wifi mobo.
Intel Core i3-13100 processor (with Intel UHD 730 graphics).
Corsair Vengeance DDR5 32gb (2x16) ram, 5200Mhz.
3 x Nvme SSD.
Boot drive is Western Digital Black SN770 500gb.
Asus Nvidia RTX-3050 PCIe graphics card.
Creative Labs Sound Blaster AE-7 audio card (PCIe).
On-board audio chip (Realtek 7.1 Surround Sound High Definition Audio) is
disabled in UEFI.
UEFI is AMI/BIOS, revision 0812.
Linux Mint 21.1 is running on barebones hardware, no VM involved.
No other O/S's are installed on the machine.
-
Running sudo lspci -vnvn > lspci-vnvn.log
gave the following error message...
pcilib: sysfs_read_vpd: read failed: No such device
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: mikey 4106 F wireplumber
/dev/snd/controlC0: mikey 4106 F wireplumber
/dev/snd/seq:mikey 4105 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 21.1
InstallationDate: Installed on 2023-01-31 (32 days ago)
InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217
MachineType: ASUS System Product Name
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic
root=UUID=854c280c-7c5c-494d-a304-db66cf592baf ro quiet splash
ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.19.0-32-generic N/A
linux-backports-modules-5.19.0-32-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.10
Tags: vera
Uname: Linux 5.19.0-32-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 02/24/2023
dmi.bios.release: 8.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0812
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z790-P WIFI
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0812:bd02/24/2023:br8.12:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ790-PWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS

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

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

[Kernel-packages] [Bug 2000778] Re: pmtu.sh in net from ubunut_kernel_selftests crash SUT with K-5.19

Checked with K-5.19, K-lowlatency-5.19, J-hwe-5.19 and J-hwe-
lowlatency-5.19. This issue does not exist anymore, therefore I am
closing this bug.

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

** Changed in: linux (Ubuntu Kinetic)
   Status: Incomplete => Fix Released

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

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

Title:
  pmtu.sh in net from ubunut_kernel_selftests crash SUT with K-5.19

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

Bug description:
  Issue found with Kinetic 5.19.0-27.28 and 5.19.0-28.29 in this cycle 
(20221114) on these SUTs
   * P9 baltar
   * ARM64 kuzzle
   * ARM64 howzit-kernel

  This should not be considered as a regression as the net test cannot
  be built in 5.19.0-24.25

  
  Test log:
  
ubuntu@baltar:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$
 sudo ./pmtu.sh
  TEST: ipv4: PMTU exceptions [ OK ]
  TEST: ipv4: PMTU exceptions - nexthop objects   [ OK ]
  TEST: ipv6: PMTU exceptions [ OK ]
  TEST: ipv6: PMTU exceptions - nexthop objects   [ OK ]
  TEST: ICMPv4 with DSCP and ECN: PMTU exceptions [ OK ]
  TEST: ICMPv4 with DSCP and ECN: PMTU exceptions - nexthop objects   [ OK ]
  'socat' command not found; skipping tests
  TEST: UDPv4 with DSCP and ECN: PMTU exceptions  [SKIP]
  TEST: IPv4 over vxlan4: PMTU exceptions [ OK ]
  TEST: IPv4 over vxlan4: PMTU exceptions - nexthop objects   [ OK ]
  TEST: IPv6 over vxlan4: PMTU exceptions [ OK ]
  TEST: IPv6 over vxlan4: PMTU exceptions - nexthop objects   [ OK ]
  TEST: IPv4 over vxlan6: PMTU exceptions [ OK ]
  TEST: IPv4 over vxlan6: PMTU exceptions - nexthop objects   [ OK ]
  TEST: IPv6 over vxlan6: PMTU exceptions [ OK ]
  TEST: IPv6 over vxlan6: PMTU exceptions - nexthop objects   [ OK ]
  TEST: IPv4 over geneve4: PMTU exceptions[ OK ]
  TEST: IPv4 over geneve4: PMTU exceptions - nexthop objects  [ OK ]
  TEST: IPv6 over geneve4: PMTU exceptions[ OK ]
  TEST: IPv6 over geneve4: PMTU exceptions - nexthop objects  [ OK ]
  TEST: IPv4 over geneve6: PMTU exceptions[ OK ]
  TEST: IPv4 over geneve6: PMTU exceptions - nexthop objects  [ OK ]
  TEST: IPv6 over geneve6: PMTU exceptions[ OK ]
  TEST: IPv6 over geneve6: PMTU exceptions - nexthop objects  [ OK ]
  TEST: IPv4, bridged vxlan4: PMTU exceptions [ OK ]
  TEST: IPv4, bridged vxlan4: PMTU exceptions - nexthop objects   [ OK ]
  TEST: IPv6, bridged vxlan4: PMTU exceptions [ OK ]
  TEST: IPv6, bridged vxlan4: PMTU exceptions - nexthop objects   [ OK ]
  TEST: IPv4, bridged vxlan6: PMTU exceptions [ OK ]
  TEST: IPv4, bridged vxlan6: PMTU exceptions - nexthop objects   [ OK ]
  TEST: IPv6, bridged vxlan6: PMTU exceptions [ OK ]
  TEST: IPv6, bridged vxlan6: PMTU exceptions - nexthop objects   [ OK ]
  TEST: IPv4, bridged geneve4: PMTU exceptions[ OK ]
  TEST: IPv4, bridged geneve4: PMTU exceptions - nexthop objects  [ OK ]
  TEST: IPv6, bridged geneve4: PMTU exceptions[ OK ]
  TEST: IPv6, bridged geneve4: PMTU exceptions - nexthop objects  [ OK ]
  TEST: IPv4, bridged geneve6: PMTU exceptions[ OK ]
  TEST: IPv4, bridged geneve6: PMTU exceptions - nexthop objects  [ OK ]
  TEST: IPv6, bridged geneve6: PMTU exceptions[ OK ]
  TEST: IPv6, bridged geneve6: PMTU exceptions - nexthop objects  [ OK ]
ovs_bridge not supported
  TEST: IPv4, OVS vxlan4: PMTU exceptions [SKIP]
ovs_bridge not supported
  TEST: IPv6, OVS vxlan4: PMTU exceptions [SKIP]
ovs_bridge not supported
  TEST: IPv4, OVS vxlan6: PMTU exceptions [SKIP]
ovs_bridge not supported
  TEST: IPv6, OVS vxlan6: PMTU exceptions [SKIP]
ovs_bridge not supported
  TEST: IPv4, OVS geneve4: PMTU exceptions[SKIP]
ovs_bridge not supported
  TEST: IPv6, OVS geneve4: PMTU exceptions[SKIP]
ovs_bridge not supported
  TEST: IPv4, OVS geneve6: PMTU exceptions[SKIP]
ovs_bridge not supported
  TEST: IPv6, OVS

[Kernel-packages] [Bug 1978980] Re: [amdgpu] Wrong external screen resolution after wake up from sleep

2023-04-10 Thread Francisco R. Santos

I see that if I disable "Automatic screen lock", it does not happen any
more, even if the screen goes blank for a long time.

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

Title:
  [amdgpu] Wrong external screen resolution after wake up from sleep

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  After the Ubuntu distro upgrade (upgrade from LTS 20.04 to LTS 22.04,
  running KDE) I started experiencing a problem with external screen
  resolution after the wake up from sleep. The monitor resolution is
  small (1280x768) and doesn't respect the setting prior the sleep
  (1920x1200).

  After the wake up from sleep:

  ```
  > xrandr
  HDMI-A-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x 
axis y axis) 535mm x 339mm
 1280x768  59.94* 
 # a list of lower resolutions
  ```

  There is an error when trying to change the setting to the highest
  resolution supported by the monitor (which is not included in the
  above list).

  ```
  > xrandr --output DisplayPort-1 --mode 1920x1200
  xrandr: cannot find mode 1920x1200
  ```

  After the turn off and turn on of the external monitor, the resolution
  is somehow added to the xrandr list:

  ```
  > xrandr
  HDMI-A-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x 
axis y axis) 535mm x 339mm
 1920x1200 59.95 +
 # a list of resolutions
 1280x768  59.94* 
 # a list of lower resolutions
  ```

  Now it is possible to change the resolution:

  ```
  > xrandr --output DisplayPort-1 --mode 1920x1200
  # no output, the resolution was successfully changed
  ```   

  After the change, the resolution is successfully changed and xrandr
  gives proper output:

  ```
  > xrandr
  HDMI-A-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-1 connected primary 1920x1200+0+0 (normal left inverted right x 
axis y axis) 535mm x 339mm
 1920x1200 59.95*+
 # a list of lower resolutions
  ```

  The problem is not present on fresh start. However, it is consistently
  present after the wake up from sleep.

  What can cause the problem and how may I fix it?

  Running AMD based laptop (Ryzen 7 3700U with integrated graphics), the
  external monitor is connected via USB-C. There are no problems with
  laptop screen resolution, only external monitor is affected.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
  Uname: Linux 5.15.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Thu Jun 16 18:12:05 2022
  DistUpgraded: 2022-05-08 07:52:25,560 DEBUG icon theme changed, re-reading
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15d8] (rev c1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2019-08-21 (1030 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20NE000BMC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic 
root=UUID=0fff4104-4909-4124-b8b0-8430281f24be ro open splash iommu=soft 
vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-05-08 (39 days ago)
  dmi.bios.date: 01/26/2022
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R11ET44W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NE000BMC
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.24
  dmi.modalias: 
dmi:bvnLENOVO:bvrR11ET44W(1.24):bd01/26/2022:br1.24:efr1.24:svnLENOVO:pn20NE000BMC:pvrThinkPadE495:rvnLENOVO:rn20NE000BMC:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20NE_BU_Think_FM_ThinkPadE495:
  dmi.product.family: ThinkPad E495
  dmi.product.name: 20NE000BMC
  dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495
  dmi.product.versio

[Kernel-packages] [Bug 2000778] Re: pmtu.sh in net from ubunut_kernel_selftests crash SUT with K-5.19