[Kernel-packages] [Bug 1954369] Re: Fix runtime power management on USB controller with XHCI_RESET_ON_RESUME flag
Verify on WMVD5-DVT2-A1, BIOS 0.4.7. Bluetooth can get scan result in gnome-control-center. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1954369 Title: Fix runtime power management on USB controller with XHCI_RESET_ON_RESUME flag Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] xHCI driver's runtime resume routine tries to reset USB controller with XHCI_RESET_ON_RESUME flag. That causes USB devices connect to the xHCI fail to work. [Fix] Disable runtime power management regardless of CONFIG_USB_DEFAULT_PERSIST option. [Test] USB devices which connect to the xHCI controller can work normally. [Where problems could occur] USB_DEFAULT_PERSIST is a config for system-wide PM to speed up resume time, so it shouldn't be applied to runtime PM at first place. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954369/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954646] Re: [SRU][I/J/OEM-5.13/OEM-5.14] Fix pci port lost when hotplug dock
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1954646 Title: [SRU][I/J/OEM-5.13/OEM-5.14] Fix pci port lost when hotplug dock Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: In Progress Bug description: [Impact] On Intel Maple Ridge, when hotplug TBT4 dock, PCIe bus show error "severity=Uncorrected (Non-Fatal)", and failed to probe. [Fix] Re-enable PCIe port LTR after reset or hotplug, and probe it properly. [Test] Verified on HW with TBT4 dock. it works fine. Also tested Tiger Lake-LP Thunderbolt 4, tbt4 dock works fine. Tested on AMD Cezanne, PCIe works fine, it doesn't support thunderbolt. [Where problems could occur] PCI bus may break. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954818] Re: Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish, and 470 in Focal
This bug was fixed in the package nvidia-graphics-drivers-495 -
495.46-0ubuntu2
---
nvidia-graphics-drivers-495 (495.46-0ubuntu2) jammy; urgency=medium
* debian/additional_runtimepm_ids:
- Add the following IDs:
1FBC 249C 249D 24B6 24B7 24B8 25A0 25B8
-- Alberto Milone Thu, 16 Dec 2021
15:40:14 +0100
** Changed in: nvidia-graphics-drivers-495 (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/1954818
Title:
Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish,
and 470 in Focal
Status in nvidia-graphics-drivers-470 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-495 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
Invalid
Status in nvidia-graphics-drivers-495 source package in Bionic:
Fix Committed
Status in nvidia-graphics-drivers-470 source package in Focal:
Fix Committed
Status in nvidia-graphics-drivers-495 source package in Focal:
Fix Committed
Status in nvidia-graphics-drivers-470 source package in Hirsute:
Invalid
Status in nvidia-graphics-drivers-495 source package in Hirsute:
Fix Committed
Status in nvidia-graphics-drivers-470 source package in Impish:
Invalid
Status in nvidia-graphics-drivers-495 source package in Impish:
Fix Committed
Bug description:
[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvements.
See the changelog entry below for a full list of changes and bugs.
[Test Case]
The following development and SRU process was followed:
https://wiki.ubuntu.com/NVidiaUpdates
Certification test suite must pass on a range of hardware:
https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu
The QA team that executed the tests will be in charge of attaching the
artifacts and console output of the appropriate run to the bug. nVidia
maintainers team members will not mark ‘verification-done’ until this
has happened.
[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned system level tests are attached to this bug.
[Discussion]
[Changelog]
== 470 (focal only) ==
nvidia-graphics-drivers-470 (470.86-0ubuntu0.20.04.2) focal;
urgency=medium
* debian/{nvidia_supported|pm-aliases-gen}:
- Drop the following IDs in favour of the 495 series (LP: #1954818):
1fbc, 249c, 249d, 24b6, 24b7, 24b8,
25a0, 25b8.
== 495 (bionic, focal, hirsute, impish) ==
nvidia-graphics-drivers-495 (495.46-0ubuntu*)
[ Daniel van Vugt ]
* debian/templates/libnvidia-extra-flavour.links.in:
- Move nvidia-drm_gbm.so into the gbm/ library subdirectory
which is where Mesa searches for it.
[ Alberto Milone ]
* debian/additional_card_ids,
debian/additional_runtimepm_ids:
- Add the following IDs:
1FBC 249C 249D 24B6 24B7 24B8 25A0 25B8
* New upstream release (LP: #1954818):
- Added support for the GBM API. This adds the new symlink
nvidia-drm_gbm.so pointing to the file libnvidia-
allocator.so.VERSION to implement a GBM backend driver usable
with the GBM loader from the Mesa project version 21.2 and
above, as well as the files libnvidia-egl-gbm.so.1.1.0 and
15_nvidia_gbm.json, which implement EGL support for the GBM
platform (EGL_KHR_platform_gbm).
- Add indicator for Resizable BAR support on compatible systems.
- Fixed a bug that could cause the X server to crash when
starting a new server generation on PRIME configurations.
- Removed support for NvIFROpenGL. This functionality was
deprecated in the 470.xx driver release.
- Removed libnvidia-cbl.so from the driver package. This
functionality is now provided by other driver libraries.
- Changed the minimum required Linux kernel version from 2.6.32
to 3.10.
- Updated nvidia.ko to load even if no supported NVIDIA GPUs are
present when an NVIDIA NVSwitch device is detected in the
system. Previously, nvidia.ko would fail to load into the
kernel if no supported GPUs were present.
- Fixed a bug in the Vulkan driver where unused input attributes
to a vertex shader would corrupt the interpolation qualifiers
for the shader.
- Fixed a bug in the Vulkan driver where individual components of
barycentric inputs could not be read.
- Added support for the VK_KHR_present_id extension.
- Added support for the VK_KHR_present_wait extension.
- Added support for the
VK_KHR_shader_subgroup_uniform_control_flow extension.
- Fixed a bug where VK_NVX_binary_import was advertised as
supported on unsupported
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oem-5.14/5.14.0.1012.12)
All autopkgtests for the newly accepted linux-meta-oem-5.14 (5.14.0.1012.12) for focal have finished running. The following regressions have been reported in tests triggered by the package: virtualbox-hwe/6.1.26-dfsg-3~ubuntu1.20.04.2 (amd64) virtualbox/6.1.26-dfsg-3~ubuntu1.20.04.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-oem-5.14 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953208] Re: Fix bogus HDMI audio interface
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1012.12 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1953208 Title: Fix bogus HDMI audio interface Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: [Impact] Bogus HDMI audio can be selected as output, without any HDMI monitor connected. [Fix] Consider 0 SAD as invalid ELD - no SAD means no audio. [Test] With the patch applied, no bogus HDMI audio can be found in GNOME's setting app. [Where problems could occur] Basically none. No SAD means no PCM - so it has never worked before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1953208/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954369] Re: Fix runtime power management on USB controller with XHCI_RESET_ON_RESUME flag
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1012.12 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1954369 Title: Fix runtime power management on USB controller with XHCI_RESET_ON_RESUME flag Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] xHCI driver's runtime resume routine tries to reset USB controller with XHCI_RESET_ON_RESUME flag. That causes USB devices connect to the xHCI fail to work. [Fix] Disable runtime power management regardless of CONFIG_USB_DEFAULT_PERSIST option. [Test] USB devices which connect to the xHCI controller can work normally. [Where problems could occur] USB_DEFAULT_PERSIST is a config for system-wide PM to speed up resume time, so it shouldn't be applied to runtime PM at first place. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954369/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954728] Re: Fix No Screen after login to Desktop on sku with 3840x2400 panel
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1012.12 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1954728 Title: Fix No Screen after login to Desktop on sku with 3840x2400 panel Status in HWE Next: New Status in OEM Priority Project: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: New Bug description: [Impact] Got kernel report CPU pipe A FIFO underrun: soft,transcoder kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun: soft,transcoder, [Fix] Fix has been landed on linux-next, 4fe7907f3775(drm/i915/display/adlp: Disable underrun recovery). Defeature the underrun feature for intel display gen13+. [Test Case] 1. change resolution to 3840x2400 2. monitor works well and doesn't black out. [Where problems could occur] low To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954773] Re: New fix for jack detection after resume on CS8409 sound driver
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1012.12
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1954773
Title:
New fix for jack detection after resume on CS8409 sound driver
Status in HWE Next:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-oem-5.14 package in Ubuntu:
New
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.14 source package in Focal:
In Progress
Status in linux source package in Impish:
Fix Committed
Status in linux-oem-5.14 source package in Impish:
Invalid
Bug description:
[SRU Justification]
[Impact]
On some platforms with Cirrus CS8409 audio codec, the external headset will
fail to be detected after system resume.
[Fix]
Cirrus released a new fix commit 65cc4ad62a9e ('ALSA: hda/cs8409: Set PMSG_ON
earlier inside cs8409 driver'). It sets the power_state to ON before the
unsolicited event arrives to make sure the jack detection can be invoked after
resume.
[Test]
Plug-in an external headset in front headset port, suspend/resume the system
then check whether the headset function works as expected.
[Where problem could occur]
Low. It only affect the platforms with Cirrus codec CS8409 which used to have
problem.
== Original Bug Description ==
[Summary] System can't detect external headset after suspend
[Steps to reproduce]
1. install manifest and boot into OS
2. plug-in an external headset in front headset port
3. un-plug external headset
4. suspend system
5. resume system from suspend
6. plug-in an external headset
[Expected result]
System could detect external headset after suspend
[Actual result]
System can't detect external headset after suspend
[Failure rate]
3/3
[Additional information]
CID: 202110-29567
SKU: DLPV-SFF-DVT-C1
Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-davos-adl+X152
system-manufacturer: Dell Inc.
system-product-name: Vostro 3710
bios-version: 0.13.73
CPU: 12th Gen Intel(R) Core(TM) i7-12700 (20x)
GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device
[8086:4680] (rev 0c)
kernel-version: 5.13.0-1019-oem
[Stage]
Issue reported and logs collected right after it happened
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1954773/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954930] Re: AMD: Suspend not working when some cores are disabled through cpufreq
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1012.12
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1954930
Title:
AMD: Suspend not working when some cores are disabled through cpufreq
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.14 source package in Focal:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Status in linux-oem-5.14 source package in Impish:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux-oem-5.14 source package in Jammy:
Invalid
Bug description:
[SRU Justification]
[Impact]
Detailed in https://gitlab.freedesktop.org/drm/amd/-/issues/1708, taking
some cpu cores offline using cpufreq gadgets or via sysfs may hang the
system.
[Fix]
In v5.16-rc1 commit d6b88ce2eb9d ("ACPI: processor idle: Allow playing
dead in C3 state") fixes this issue.
[Test Case]
As stated in aforementioned bug url, setup cpufreq extention to take
down a few cpu cores, and trigger system suspend. There are ~50% chances
that networking/input/... would hang and the user can only reboot by
sysrq keys.
[Where problems could occur]
According to the patch discussion thread in
https://lore.kernel.org/linux-acpi/20210922133116.102-1-richard.g...@amd.com/,
the limitation to allow enter_dead in no more than ACPI_STATE_C2 might
not have a practical meaning, but simply C2 was the deepest supported
then.
[Other Info]
While this is currently only available in v5.16-rc1 and affects AMD
Cezanne/Barcelo, oem-5.14/impish and jammy are nominated.
== original bug report ==
https://gitlab.freedesktop.org/drm/amd/-/issues/1708
Reproduce steps:
1. Install cpufeq gnome extension
(https://extensions.gnome.org/extension/1082/cpufreq/)
2. Click on the cpu freq extention in the top bar
3. Slide the "cores online" from 16 to 3
4. close lid of laptop
Expected result: the laptop goes into suspend
Actual result: the laptop stay on but screen is now always black and keyboard
input is ignored
Fix committed to v5.16-rc1:
https://github.com/torvalds/linux/commit/d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ubuntu 1188 F pulseaudio
/dev/snd/controlC2: ubuntu 1188 F pulseaudio
/dev/snd/controlC0: ubuntu 1188 F pulseaudio
CasperMD5CheckResult: skip
Dependencies:
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X152
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2021-09-09 (97 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
IwConfig:
lono wireless extensions.
enp1s0f0 no wireless extensions.
Lsusb:
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: AMD Celadon-CZN
Package: linux-firmware 1.187.23+staging.38 [origin:
LP-PPA-canonical-hwe-team-linux-firmware-staging]
PackageArchitecture: all
ProcFB: 0 amdgpu
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9011-oem
root=UUID=668f30b7-78ec-472e-9916-c9b1cbdbbbc6 ro automatic-oem-config
no_console_suspend
ProcVersionSignature: Ubuntu 5.14.0-9011.11+staging.37-oem 5.14.20
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.14.0-9011-oem N/A
linux-backports-modules-5.14.0-9011-oem N/A
linux-firmware 1.187.23+staging.38
[Kernel-packages] [Bug 1938104] Re: shiftfs module is not built because CONFIG_SHIFT_FS is not set
This bug is awaiting verification that the linux-oem-5.13/5.13.0-1023.28 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1938104 Title: shiftfs module is not built because CONFIG_SHIFT_FS is not set Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.13 source package in Focal: New Bug description: Shiftfs is built and included in all other ubuntu kernels that I know of and if I'm not mistaken is sponsored by ubuntu mostly for use with LXD containers, which is my use case. It also included in the linux- oem-5.10. Is there a reason shiftfs is not included in the 5.13 oem release? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.13/+bug/1938104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954646] Re: [SRU][I/J/OEM-5.13/OEM-5.14] Fix pci port lost when hotplug dock
This bug is awaiting verification that the linux-oem-5.13/5.13.0-1023.28 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1954646 Title: [SRU][I/J/OEM-5.13/OEM-5.14] Fix pci port lost when hotplug dock Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: In Progress Bug description: [Impact] On Intel Maple Ridge, when hotplug TBT4 dock, PCIe bus show error "severity=Uncorrected (Non-Fatal)", and failed to probe. [Fix] Re-enable PCIe port LTR after reset or hotplug, and probe it properly. [Test] Verified on HW with TBT4 dock. it works fine. Also tested Tiger Lake-LP Thunderbolt 4, tbt4 dock works fine. Tested on AMD Cezanne, PCIe works fine, it doesn't support thunderbolt. [Where problems could occur] PCI bus may break. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955278] [NEW] /tmp/apt-dpkg-install-VaNlgQ/10-libnvidia-gl-460_460.91.03-0ubuntu0.20.04.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1)
Public bug reported: ı am trying install nvidia drivers but it gives this error ** Affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1955278 Title: /tmp/apt-dpkg-install-VaNlgQ/10-libnvidia- gl-460_460.91.03-0ubuntu0.20.04.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: ı am trying install nvidia drivers but it gives this error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1955278/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955277] [NEW] Hirsute update: upstream stable patchset 2021-12-17
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 2021-12-17 Ported from the following upstream stable releases: v5.10.82, v5.15.5 from git://git.kernel.org/ arm64: zynqmp: Do not duplicate flash partition label property arm64: zynqmp: Fix serial compatible string ARM: dts: sunxi: Fix OPPs node name arm64: dts: allwinner: h5: Fix GPU thermal zone node name arm64: dts: allwinner: a100: Fix thermal zone node name staging: wfx: ensure IRQ is ready before enabling it ARM: dts: NSP: Fix mpcore, mmc node names scsi: lpfc: Fix list_add() corruption in lpfc_drain_txq() arm64: dts: rockchip: Disable CDN DP on Pinebook Pro arm64: dts: hisilicon: fix arm,sp805 compatible string RDMA/bnxt_re: Check if the vlan is valid before reporting bus: ti-sysc: Add quirk handling for reinit on context lost bus: ti-sysc: Use context lost quirk for otg usb: musb: tusb6010: check return value after calling platform_get_resource() usb: typec: tipd: Remove WARN_ON in tps6598x_block_read ARM: dts: ux500: Skomer regulator fixes staging: rtl8723bs: remove possible deadlock when disconnect (v2) ARM: BCM53016: Specify switch ports for Meraki MR32 arm64: dts: qcom: msm8998: Fix CPU/L2 idle state latency and residency arm64: dts: qcom: ipq6018: Fix qcom,controlled-remotely property arm64: dts: freescale: fix arm,sp805 compatible string ASoC: SOF: Intel: hda-dai: fix potential locking issue clk: imx: imx6ul: Move csi_sel mux to correct base register ASoC: nau8824: Add DMI quirk mechanism for active-high jack-detect scsi: advansys: Fix kernel pointer leak ALSA: intel-dsp-config: add quirk for APL/GLK/TGL devices based on ES8336 codec firmware_loader: fix pre-allocated buf built-in firmware use ARM: dts: omap: fix gpmc,mux-add-data type usb: host: ohci-tmio: check return value after calling platform_get_resource() ARM: dts: ls1021a: move thermal-zones node out of soc/ ARM: dts: ls1021a-tsn: use generic "jedec,spi-nor" compatible for flash ALSA: ISA: not for M68K tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc MIPS: sni: Fix the build scsi: scsi_debug: Fix out-of-bound read in resp_readcap16() scsi: scsi_debug: Fix out-of-bound read in resp_report_tgtpgs() scsi: target: Fix ordered tag handling scsi: target: Fix alua_tg_pt_gps_count tracking iio: imu: st_lsm6dsx: Avoid potential array overflow in st_lsm6dsx_set_odr() powerpc/5200: dts: fix memory node unit name ARM: dts: qcom: fix memory and mdio nodes naming for RB3011 ALSA: gus: fix null pointer dereference on pointer block powerpc/dcr: Use cmplwi instead of 3-argument cmpli powerpc/8xx: Fix Oops with STRICT_KERNEL_RWX without DEBUG_RODATA_TEST sh: check return code of request_irq maple: fix wrong return value of maple_bus_init(). f2fs: fix up f2fs_lookup tracepoints f2fs: fix to use WHINT_MODE sh: fix kconfig unmet dependency warning for FRAME_POINTER sh: math-emu: drop unused functions sh: define __BIG_ENDIAN for math-emu f2fs: compress: disallow disabling compress on non-empty compressed file f2fs: fix incorrect return value in f2fs_sanity_check_ckpt() clk: ingenic: Fix bugs with divided dividers clk/ast2600: Fix soc revision for AHB clk: qcom: gcc-msm8996: Drop (again) gcc_aggre1_pnoc_ahb_clk mips: BCM63XX: ensure that CPU_SUPPORTS_32BIT_KERNEL is set sched/core: Mitigate race cpus_share_cache()/update_top_cache_domain() perf/x86/vlbr: Add c->flags to vlbr event constraints blkcg: Remove extra blkcg_bio_issue_init tracing/histogram: Do not copy the fixed-size char array field over the field size perf bpf: Avoid memory leak from perf_env__insert_btf() perf bench futex: Fix memory leak of perf_cpu_map__new() perf tests: Remove bash construct from record+zstd_comp_decomp.sh drm/nouveau: hdmigv100.c: fix corrupted HDMI Vendor InfoFrame tcp: Fix uninitialized access in skb frags array for Rx 0cp. tracing: Add length protection to histogram string copies net: ipa: disable HOLB drop when updating timer net: bnx2x: fix variable dereferenced before check bnxt_en: reject indirect blk offload when hw-tc-offload is off tipc: only accept encrypted MSG_CRYPTO msgs net: reduce indentation level in sk_clone_lock() sock: fix /proc/net/sockstat underflow in sk_clone_lock() net/smc: Make sure the link_id is unique iavf: Fix return of set the new channel count iavf: check for null in iavf_fix_features iavf: free q_vectors before queues in iavf_disable_vf iavf: Fix failure to exit out from last all-multicast mode iavf: prevent accidental free of filter structure iavf: validate pointers iavf: Fix for the
[Kernel-packages] [Bug 1955180] Re: Impish update: upstream stable patchset 2021-12-17
** 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 2021-12-17 + + Ported from the following upstream stable releases: + v5.10.82, v5.15.5 + from git://git.kernel.org/ arm64: zynqmp: Do not duplicate flash partition label property arm64: zynqmp: Fix serial compatible string ARM: dts: sunxi: Fix OPPs node name arm64: dts: allwinner: h5: Fix GPU thermal zone node name arm64: dts: allwinner: a100: Fix thermal zone node name staging: wfx: ensure IRQ is ready before enabling it ARM: dts: NSP: Fix mpcore, mmc node names scsi: lpfc: Fix list_add() corruption in lpfc_drain_txq() arm64: dts: rockchip: Disable CDN DP on Pinebook Pro arm64: dts: hisilicon: fix arm,sp805 compatible string RDMA/bnxt_re: Check if the vlan is valid before reporting bus: ti-sysc: Add quirk handling for reinit on context lost bus: ti-sysc: Use context lost quirk for otg usb: musb: tusb6010: check return value after calling platform_get_resource() usb: typec: tipd: Remove WARN_ON in tps6598x_block_read ARM: dts: ux500: Skomer regulator fixes staging: rtl8723bs: remove possible deadlock when disconnect (v2) ARM: BCM53016: Specify switch ports for Meraki MR32 arm64: dts: qcom: msm8998: Fix CPU/L2 idle state latency and residency arm64: dts: qcom: ipq6018: Fix qcom,controlled-remotely property arm64: dts: freescale: fix arm,sp805 compatible string ASoC: SOF: Intel: hda-dai: fix potential locking issue clk: imx: imx6ul: Move csi_sel mux to correct base register ASoC: nau8824: Add DMI quirk mechanism for active-high jack-detect scsi: advansys: Fix kernel pointer leak ALSA: intel-dsp-config: add quirk for APL/GLK/TGL devices based on ES8336 codec firmware_loader: fix pre-allocated buf built-in firmware use ARM: dts: omap: fix gpmc,mux-add-data type usb: host: ohci-tmio: check return value after calling platform_get_resource() ARM: dts: ls1021a: move thermal-zones node out of soc/ ARM: dts: ls1021a-tsn: use generic "jedec,spi-nor" compatible for flash ALSA: ISA: not for M68K tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc MIPS: sni: Fix the build scsi: scsi_debug: Fix out-of-bound read in resp_readcap16() scsi: scsi_debug: Fix out-of-bound read in resp_report_tgtpgs() scsi: target: Fix ordered tag handling scsi: target: Fix alua_tg_pt_gps_count tracking iio: imu: st_lsm6dsx: Avoid potential array overflow in st_lsm6dsx_set_odr() powerpc/5200: dts: fix memory node unit name ARM: dts: qcom: fix memory and mdio nodes naming for RB3011 ALSA: gus: fix null pointer dereference on pointer block powerpc/dcr: Use cmplwi instead of 3-argument cmpli powerpc/8xx: Fix Oops with STRICT_KERNEL_RWX without DEBUG_RODATA_TEST sh: check return code of request_irq maple: fix wrong return value of maple_bus_init(). f2fs: fix up f2fs_lookup tracepoints f2fs: fix to use WHINT_MODE sh: fix kconfig unmet dependency warning for FRAME_POINTER sh: math-emu: drop unused functions sh: define __BIG_ENDIAN for math-emu f2fs: compress: disallow disabling compress on non-empty compressed file f2fs: fix incorrect return value in f2fs_sanity_check_ckpt() clk: ingenic: Fix bugs with divided dividers clk/ast2600: Fix soc revision for AHB clk: qcom: gcc-msm8996: Drop (again) gcc_aggre1_pnoc_ahb_clk mips: BCM63XX: ensure that CPU_SUPPORTS_32BIT_KERNEL is set sched/core: Mitigate race cpus_share_cache()/update_top_cache_domain() perf/x86/vlbr: Add c->flags to vlbr event constraints blkcg: Remove extra blkcg_bio_issue_init tracing/histogram: Do not copy the fixed-size char array field over the field size perf bpf: Avoid memory leak from perf_env__insert_btf() perf bench futex: Fix memory leak of perf_cpu_map__new() perf tests: Remove bash construct from record+zstd_comp_decomp.sh drm/nouveau: hdmigv100.c: fix corrupted HDMI Vendor InfoFrame tcp: Fix uninitialized access in skb frags array for Rx 0cp. tracing: Add length protection to histogram string copies net: ipa: disable HOLB drop when updating timer net: bnx2x: fix variable dereferenced before check bnxt_en: reject indirect blk offload when hw-tc-offload is off tipc: only accept encrypted MSG_CRYPTO msgs sock: fix /proc/net/sockstat underflow in sk_clone_lock() net/smc: Make sure the link_id is unique iavf: Fix return of set the new channel count iavf: check for null in iavf_fix_features iavf: free q_vectors before queues in iavf_disable_vf iavf: Fix
[Kernel-packages] [Bug 1955180] Re: Impish update: upstream stable patchset 2021-12-17
** 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 2021-12-17 + from git://git.kernel.org/ -upstream stable patchset 2021-12-17 -from git://git.kernel.org/ + arm64: zynqmp: Do not duplicate flash partition label property + arm64: zynqmp: Fix serial compatible string + ARM: dts: sunxi: Fix OPPs node name + arm64: dts: allwinner: h5: Fix GPU thermal zone node name + arm64: dts: allwinner: a100: Fix thermal zone node name + staging: wfx: ensure IRQ is ready before enabling it + ARM: dts: NSP: Fix mpcore, mmc node names + scsi: lpfc: Fix list_add() corruption in lpfc_drain_txq() + arm64: dts: rockchip: Disable CDN DP on Pinebook Pro + arm64: dts: hisilicon: fix arm,sp805 compatible string + RDMA/bnxt_re: Check if the vlan is valid before reporting + bus: ti-sysc: Add quirk handling for reinit on context lost + bus: ti-sysc: Use context lost quirk for otg + usb: musb: tusb6010: check return value after calling platform_get_resource() + usb: typec: tipd: Remove WARN_ON in tps6598x_block_read + ARM: dts: ux500: Skomer regulator fixes + staging: rtl8723bs: remove possible deadlock when disconnect (v2) + ARM: BCM53016: Specify switch ports for Meraki MR32 + arm64: dts: qcom: msm8998: Fix CPU/L2 idle state latency and residency + arm64: dts: qcom: ipq6018: Fix qcom,controlled-remotely property + arm64: dts: freescale: fix arm,sp805 compatible string + ASoC: SOF: Intel: hda-dai: fix potential locking issue + clk: imx: imx6ul: Move csi_sel mux to correct base register + ASoC: nau8824: Add DMI quirk mechanism for active-high jack-detect + scsi: advansys: Fix kernel pointer leak + ALSA: intel-dsp-config: add quirk for APL/GLK/TGL devices based on ES8336 codec + firmware_loader: fix pre-allocated buf built-in firmware use + ARM: dts: omap: fix gpmc,mux-add-data type + usb: host: ohci-tmio: check return value after calling platform_get_resource() + ARM: dts: ls1021a: move thermal-zones node out of soc/ + ARM: dts: ls1021a-tsn: use generic "jedec,spi-nor" compatible for flash + ALSA: ISA: not for M68K + tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc + MIPS: sni: Fix the build + scsi: scsi_debug: Fix out-of-bound read in resp_readcap16() + scsi: scsi_debug: Fix out-of-bound read in resp_report_tgtpgs() + scsi: target: Fix ordered tag handling + scsi: target: Fix alua_tg_pt_gps_count tracking + iio: imu: st_lsm6dsx: Avoid potential array overflow in st_lsm6dsx_set_odr() + powerpc/5200: dts: fix memory node unit name + ARM: dts: qcom: fix memory and mdio nodes naming for RB3011 + ALSA: gus: fix null pointer dereference on pointer block + powerpc/dcr: Use cmplwi instead of 3-argument cmpli + powerpc/8xx: Fix Oops with STRICT_KERNEL_RWX without DEBUG_RODATA_TEST + sh: check return code of request_irq + maple: fix wrong return value of maple_bus_init(). + f2fs: fix up f2fs_lookup tracepoints + f2fs: fix to use WHINT_MODE + sh: fix kconfig unmet dependency warning for FRAME_POINTER + sh: math-emu: drop unused functions + sh: define __BIG_ENDIAN for math-emu + f2fs: compress: disallow disabling compress on non-empty compressed file + f2fs: fix incorrect return value in f2fs_sanity_check_ckpt() + clk: ingenic: Fix bugs with divided dividers + clk/ast2600: Fix soc revision for AHB + clk: qcom: gcc-msm8996: Drop (again) gcc_aggre1_pnoc_ahb_clk + mips: BCM63XX: ensure that CPU_SUPPORTS_32BIT_KERNEL is set + sched/core: Mitigate race cpus_share_cache()/update_top_cache_domain() + perf/x86/vlbr: Add c->flags to vlbr event constraints + blkcg: Remove extra blkcg_bio_issue_init + tracing/histogram: Do not copy the fixed-size char array field over the field size + perf bpf: Avoid memory leak from perf_env__insert_btf() + perf bench futex: Fix memory leak of perf_cpu_map__new() + perf tests: Remove bash construct from record+zstd_comp_decomp.sh + drm/nouveau: hdmigv100.c: fix corrupted HDMI Vendor InfoFrame + tcp: Fix uninitialized access in skb frags array for Rx 0cp. + tracing: Add length protection to histogram string copies + net: ipa: disable HOLB drop when updating timer
[Kernel-packages] [Bug 1955180] Re: Impish update: upstream stable patchset 2021-12-17
** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1955180 Title: Impish update: upstream stable patchset 2021-12-17 Status in linux package in Ubuntu: Invalid Status in linux source package in Impish: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-12-17 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955180/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955180] [NEW] Impish update: upstream stable patchset 2021-12-17
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 2021-12-17 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Impish) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Impish) 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/1955180 Title: Impish update: upstream stable patchset 2021-12-17 Status in linux package in Ubuntu: Invalid Status in linux source package in Impish: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-12-17 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955180/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951873] Re: Enable arm64 nitro enclaves
** Changed in: linux-aws (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-aws (Ubuntu Hirsute) Status: In Progress => Fix Committed -- 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/1951873 Title: Enable arm64 nitro enclaves Status in linux-aws package in Ubuntu: In Progress Status in linux-aws source package in Focal: Fix Committed Status in linux-aws source package in Hirsute: Fix Committed Status in linux-aws source package in Impish: In Progress Status in linux-aws source package in Jammy: In Progress Bug description: SRU Justification [Impact] Enable arm64 support for Nitro Enclaves [Test Plan] Boot an AWS arm64 instance. Test for the existence of enclaves. See https://github.com/aws/aws-nitro-enclaves-cli/blob/main/docs/ubuntu_20.04_how_to_install_nitro_cli_from_github_sources.md [Where things could go wrong] Its possible this could affect amd64 enclave support. [Other Info] SF: #00323459 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1951873/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950666] Re: system crash when removing ipmi_msghandler module
** Changed in: linux (Ubuntu Focal) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Hirsute) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Impish) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950666 Title: system crash when removing ipmi_msghandler module Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: In Progress Bug description: [IMPACT] Commit 3b9a907223d7 (ipmi: fix sleep-in-atomic in free_user at cleanup SRCU user->release_barrier) pushes the removal of an ipmi_user into the system's workqueue. Whenever an ipmi_user struct is about to be removed it is scheduled as a work on the system's workqueue to guarantee the free operation won't be executed in atomic context. When the work is executed the free_user_work() function is invoked which frees the ipmi_user. When ipmi_msghandler module is removed in cleanup_ipmi() function, there is no check if there are any pending works to be executed. Therefore, there is a potential race condition : An ipmi_user is scheduled for removal and shortly after to remove the ipmi_msghandler module. If the scheduled work delays execution for any reason and the module is removed first, then when the work is executed the pages of free_user_work() are gone and the system crashes with the following : BUG: unable to handle page fault for address: c05c3450 #PF: supervisor instruction fetch in kernel mode #PF: error_code(0x0010) - not-present page PGD 635420e067 P4D 635420e067 PUD 6354210067 PMD 4711e51067 PTE 0 Oops: 0010 [#1] SMP PTI CPU: 19 PID: 29646 Comm: kworker/19:1 Kdump: loaded Not tainted 5.4.0-77-generic #86~18.04.1-Ubuntu Hardware name: Ciara Technologies ORION RS610-G4-DTH4S/MR91-FS1-Y9, BIOS F29 05/23/2019 Workqueue: events 0xc05c3450 RIP: 0010:0xc05c3450 Code: Bad RIP value. RSP: 0018:b721333c3e88 EFLAGS: 00010286 RAX: c05c3450 RBX: 92a95f56a740 RCX: b7221cfd14e8 RDX: 0001 RSI: 92616040d4b0 RDI: b7221cf404e0 RBP: b721333c3ec0 R08: 73746e657665 R09: 8080808080808080 R10: b721333c3de0 R11: fefefefefefefeff R12: 92a95f570700 R13: 92a0a40ece40 R14: b7221cf404e0 R15: 092a95f57070 FS: () GS:92a95f54() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: c05c3426 CR3: 0081e9bfc005 CR4: 007606e0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 PKRU: 5554 Call Trace: ? process_one_work+0x20f/0x400 worker_thread+0x34/0x410 kthread+0x121/0x140 ? process_one_work+0x400/0x400 ? kthread_park+0x90/0x90 ret_from_fork+0x35/0x40 Modules linked in: xt_REDIRECT xt_owner ipt_rpfilter xt_CT xt_multiport xt_set ip_set_hash_ip veth xt_statistic ipt_REJECT ... megaraid_sas ahci libahci wmi [last unloaded: ipmi_msghandler] CR2: c05c3450 [TEST CASE] The user who reported the issue can reproduce reliably by stopping the ipmi related services and then removing the ipmi modules. I could reproduce the issue only when turning the normal 'work' to delayed work. [WHERE PROBLEMS COULD OCCUR] The fixing patch creates a dedicated workqueue for the remove_work struct of ipmi_user when loading the ipmi_msghandler modules and destroys the workqueue when removing the module. Therefore any potential problems would occur during these two operations or when scheduling works on the dedicated workqueue. [OTHER] Upstream patches : 1d49eb91e86e (ipmi: Move remove_work to dedicated workqueue) 5a3ba99b62d8 (ipmi: msghandler: Make symbol 'remove_work_wq' static) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950666/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954930] Re: AMD: Suspend not working when some cores are disabled through cpufreq
** Changed in: linux (Ubuntu Impish)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1954930
Title:
AMD: Suspend not working when some cores are disabled through cpufreq
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.14 source package in Focal:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Status in linux-oem-5.14 source package in Impish:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux-oem-5.14 source package in Jammy:
Invalid
Bug description:
[SRU Justification]
[Impact]
Detailed in https://gitlab.freedesktop.org/drm/amd/-/issues/1708, taking
some cpu cores offline using cpufreq gadgets or via sysfs may hang the
system.
[Fix]
In v5.16-rc1 commit d6b88ce2eb9d ("ACPI: processor idle: Allow playing
dead in C3 state") fixes this issue.
[Test Case]
As stated in aforementioned bug url, setup cpufreq extention to take
down a few cpu cores, and trigger system suspend. There are ~50% chances
that networking/input/... would hang and the user can only reboot by
sysrq keys.
[Where problems could occur]
According to the patch discussion thread in
https://lore.kernel.org/linux-acpi/20210922133116.102-1-richard.g...@amd.com/,
the limitation to allow enter_dead in no more than ACPI_STATE_C2 might
not have a practical meaning, but simply C2 was the deepest supported
then.
[Other Info]
While this is currently only available in v5.16-rc1 and affects AMD
Cezanne/Barcelo, oem-5.14/impish and jammy are nominated.
== original bug report ==
https://gitlab.freedesktop.org/drm/amd/-/issues/1708
Reproduce steps:
1. Install cpufeq gnome extension
(https://extensions.gnome.org/extension/1082/cpufreq/)
2. Click on the cpu freq extention in the top bar
3. Slide the "cores online" from 16 to 3
4. close lid of laptop
Expected result: the laptop goes into suspend
Actual result: the laptop stay on but screen is now always black and keyboard
input is ignored
Fix committed to v5.16-rc1:
https://github.com/torvalds/linux/commit/d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ubuntu 1188 F pulseaudio
/dev/snd/controlC2: ubuntu 1188 F pulseaudio
/dev/snd/controlC0: ubuntu 1188 F pulseaudio
CasperMD5CheckResult: skip
Dependencies:
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X152
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2021-09-09 (97 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
IwConfig:
lono wireless extensions.
enp1s0f0 no wireless extensions.
Lsusb:
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: AMD Celadon-CZN
Package: linux-firmware 1.187.23+staging.38 [origin:
LP-PPA-canonical-hwe-team-linux-firmware-staging]
PackageArchitecture: all
ProcFB: 0 amdgpu
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9011-oem
root=UUID=668f30b7-78ec-472e-9916-c9b1cbdbbbc6 ro automatic-oem-config
no_console_suspend
ProcVersionSignature: Ubuntu 5.14.0-9011.11+staging.37-oem 5.14.20
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.14.0-9011-oem N/A
linux-backports-modules-5.14.0-9011-oem N/A
linux-firmware 1.187.23+staging.38
RfKill:
Tags: third-party-packages focal
Uname: Linux 5.14.0-9011-oem x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any
third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 06/30/2021
dmi.bios.release: 19.1
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: RLD1005B_AB
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Celadon-CZN
[Kernel-packages] [Bug 1954926] Re: Focal: CIFS stable updates
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1954926 Title: Focal: CIFS stable updates Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux-azure source package in Focal: In Progress Bug description: SRU Justification [Impact] Backport several stable updates to v5.4 Azure [Test Case] Microsoft tested [Where things could go wrong] Samba connections could fail [Other Info] SF: #00324495 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954926/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955174] [NEW] Unkillable process pegging CPU
Public bug reported: The following very simple bash script results in an unkillable process topping the CPU. ``` #!/bin/bash while true; do echo -n "." if echo "hw-tc-offload: off [fixed]" 2>&1 | grep 'x-checksumming' ; then echo "should never get here" fi done ``` I can reproduce the issue by starting a few (8) concurrent executions and wait a few minutes. The system used is: ``` > cat /etc/os-release PRETTY_NAME="Ubuntu 21.10" NAME="Ubuntu" VERSION_ID="21.10" VERSION="21.10 (Impish Indri)" VERSION_CODENAME=impish ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=impish ``` With kernel: ``` > uname -a Linux ubuntu 5.13.0-1011-raspi #13-Ubuntu SMP PREEMPT Fri Nov 19 18:40:23 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux ``` The issue reported over at [1] and it seems to not be present on debian [2]. At the time the issue is triggered top shows the script using one of the CPUs: ``` top - 16:39:24 up 21 min, 10 users, load average: 1.86, 3.00, 3.52 Tasks: 194 total, 3 running, 191 sleeping, 0 stopped, 0 zombie %Cpu(s): 11.1 us, 32.1 sy, 0.0 ni, 56.8 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 7808.5 total, 5194.8 free,873.9 used, 1739.7 buff/cache MiB Swap: 0.0 total, 0.0 free, 0.0 used. 6682.4 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 78617 ubuntu20 08836408 0 R 99.7 0.0 9:09.02 repro.sh ``` The stack of the CPU as reported by sysrq with the "l" option: ``` [ 876.197594] sysrq: Show backtrace of all active CPUs [ 876.202717] sysrq: CPU1: [ 876.202724] Call trace: [ 876.202727] dump_backtrace+0x0/0x1ec [ 876.202738] show_stack+0x24/0x30 [ 876.202743] showacpu+0x84/0x94 [ 876.202751] flush_smp_call_function_queue+0xd8/0x260 [ 876.202757] generic_smp_call_function_single_interrupt+0x20/0x2c [ 876.202762] do_handle_IPI+0x1d8/0x310 [ 876.202769] ipi_handler+0x28/0x40 [ 876.202774] handle_percpu_devid_irq+0x94/0x270 [ 876.202780] __handle_domain_irq+0x88/0xec [ 876.202787] gic_handle_irq+0x5c/0xf0 [ 876.202791] el1_irq+0xc0/0x15c [ 876.202795] schedule_tail+0x12c/0x1fc [ 876.202802] ret_from_fork+0x4/0x3c ``` The stack of the stuck: ``` > cat /proc/78617/stack [<0>] __switch_to+0x138/0x190 [<0>] exit_to_kernel_mode+0x28/0x80 ``` This is causing MicroK8s to fail after a few days. Thank you for your help. [1] https://github.com/ubuntu/microk8s/issues/2280#issuecomment-866912974 [2] https://github.com/ubuntu/microk8s/issues/2280#issuecomment-931306599 ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1955174 Title: Unkillable process pegging CPU Status in linux-raspi package in Ubuntu: New Bug description: The following very simple bash script results in an unkillable process topping the CPU. ``` #!/bin/bash while true; do echo -n "." if echo "hw-tc-offload: off [fixed]" 2>&1 | grep 'x-checksumming' ; then echo "should never get here" fi done ``` I can reproduce the issue by starting a few (8) concurrent executions and wait a few minutes. The system used is: ``` > cat /etc/os-release PRETTY_NAME="Ubuntu 21.10" NAME="Ubuntu" VERSION_ID="21.10" VERSION="21.10 (Impish Indri)" VERSION_CODENAME=impish ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=impish ``` With kernel: ``` > uname -a Linux ubuntu 5.13.0-1011-raspi #13-Ubuntu SMP PREEMPT Fri Nov 19 18:40:23 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux ``` The issue reported over at [1] and it seems to not be present on debian [2]. At the time the issue is triggered top shows the script using one of the CPUs: ``` top - 16:39:24 up 21 min, 10 users, load average: 1.86, 3.00, 3.52 Tasks: 194 total, 3 running, 191 sleeping, 0 stopped, 0 zombie %Cpu(s): 11.1 us, 32.1 sy, 0.0 ni, 56.8 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 7808.5 total, 5194.8 free,873.9 used, 1739.7 buff/cache MiB Swap: 0.0 total, 0.0 free, 0.0 used. 6682.4 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-hwe-5.11/5.11.0.44.48~20.04.22)
All autopkgtests for the newly accepted linux-meta-hwe-5.11 (5.11.0.44.48~20.04.22) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 (amd64) systemd/245.4-4ubuntu3.13 (amd64, s390x, ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-hwe-5.11 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950584] Re: cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and offline
Thank you for verifying, Colin! :)
--
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/1950584
Title:
cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and
offline
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
"Commit a365ab6b9dfb ("cpufreq: intel_pstate: Implement the
->adjust_perf() callback") caused intel_pstate to use nonzero HWP
desired values in certain usage scenarios, but it did not prevent
them from being leaked into the confugirations in which HWP desired
is expected to be 0"
I believe I'm seeing this issue on my laptop during suspend/resume.
The upstream fix is:
[Fix]
commit dbea75fe18f60e364de6d994fc938a24ba249d81
Author: Rafael J. Wysocki
Date: Wed Nov 3 19:43:47 2021 +0100
cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and offline
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: cking 2316 F pulseaudio
/dev/snd/pcmC1D0c: cking 2316 F...m pulseaudio
/dev/snd/controlC0: cking 2316 F pulseaudio
/dev/snd/pcmC0D0p: cking 2316 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2021-06-07 (156 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210607)
MachineType: LENOVO 20L5CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
RelatedPackageVersions:
linux-restricted-modules-5.13.0-20-generic N/A
linux-backports-modules-5.13.0-20-generic N/A
linux-firmware 1.202
Tags: jammy
Uname: Linux 5.13.0-20-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
vboxusers
_MarkForUpload: True
dmi.bios.date: 01/11/2020
dmi.bios.release: 1.30
dmi.bios.vendor: LENOVO
dmi.bios.version: N24ET55W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.20
dmi.modalias:
dmi:bvnLENOVO:bvrN24ET55W(1.30):bd01/11/2020:br1.30:efr1.20:svnLENOVO:pn20L5CTO1WW:pvrThinkPadT480:skuLENOVO_MT_20L5_BU_Think_FM_ThinkPadT480:rvnLENOVO:rn20L5CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T480
dmi.product.name: 20L5CTO1WW
dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
dmi.product.version: ThinkPad T480
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950584/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955167] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1955167 Title: Bluetooth scan Status in linux package in Ubuntu: Confirmed Bug description: Hello guys. I could not make it on my own. So help me. https://askubuntu.com/questions/1370663/bluetooth-scan-doesnt-detect-any-device-on-ubuntu-21-10 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-22-generic 5.13.0-22.22 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sms 720 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Dec 17 23:15:10 2021 InstallationDate: Installed on 2021-12-01 (16 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: ASUSTeK Computer Inc. K42F ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=053d2aa5-a579-4374-9656-2be8fa3d2a5d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2010 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 400 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K42F dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr400:bd01/29/2010:br4.6:svnASUSTeKComputerInc.:pnK42F:pvr1.0:rvnASUSTeKComputerInc.:rnK42F:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: K42F dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955167/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955167] [NEW] Bluetooth scan
Public bug reported: Hello guys. I could not make it on my own. So help me. https://askubuntu.com/questions/1370663/bluetooth-scan-doesnt-detect-any-device-on-ubuntu-21-10 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-22-generic 5.13.0-22.22 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sms 720 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Dec 17 23:15:10 2021 InstallationDate: Installed on 2021-12-01 (16 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: ASUSTeK Computer Inc. K42F ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=053d2aa5-a579-4374-9656-2be8fa3d2a5d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2010 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 400 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K42F dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr400:bd01/29/2010:br4.6:svnASUSTeKComputerInc.:pnK42F:pvr1.0:rvnASUSTeKComputerInc.:rnK42F:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: K42F dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1955167 Title: Bluetooth scan Status in linux package in Ubuntu: Confirmed Bug description: Hello guys. I could not make it on my own. So help me. https://askubuntu.com/questions/1370663/bluetooth-scan-doesnt-detect-any-device-on-ubuntu-21-10 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-22-generic 5.13.0-22.22 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sms 720 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Dec 17 23:15:10 2021 InstallationDate: Installed on 2021-12-01 (16 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: ASUSTeK Computer Inc. K42F ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=053d2aa5-a579-4374-9656-2be8fa3d2a5d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2010 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 400 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K42F dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr400:bd01/29/2010:br4.6:svnASUSTeKComputerInc.:pnK42F:pvr1.0:rvnASUSTeKComputerInc.:rnK42F:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: K42F dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955167/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931001] Re: Soft lockup due to interrupt storm from smbus
** Summary changed: - kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! + Soft lockup due to interrupt storm from smbus -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1931001 Title: Soft lockup due to interrupt storm from smbus Status in Linux: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-hwe-5.11 package in Ubuntu: Confirmed Status in linux-hwe-5.13 package in Ubuntu: Confirmed Status in Fedora: Confirmed Bug description: Ubuntu 20.04 LTS and Ubuntu 21.04 occasionally boots with very bad performance and very unresponsive to user input on Lenovo laptop Lenovo 300e 2nd Gen 81M9 (LENOVO_MT_81M9_BU_idea_FM_300e 2nd G). When this happens you can read this kind of messages on journal: --- root@alumne-1-58:~# journalctl | grep "BUG: soft" may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 22 09:33:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [prometheus-node:4220] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [swapper/1:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:02:15 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 21s! [swapper/0:0] jun 05 08:22:58 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [swapper/2:0] jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [lxd:3975] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [swapper/2:0] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [irq/138-iwlwifi:1044] jun 05 08:27:38 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [irq/138-iwlwifi:1044] jun 05 08:28:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:29:46 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] root@alumne-1-58:~# --- Usually if you reboot everything works fine but it's very annoying when happens. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1931001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955161] [NEW] Jammy update: v5.15.9 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.9 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1955161 Title: Jammy update: v5.15.9 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.9 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955161/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954818] Please test proposed package
Hello Alberto, or anyone else affected,
Accepted nvidia-graphics-drivers-495 into focal-proposed. The package
will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-495/495.46-0ubuntu0.20.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: nvidia-graphics-drivers-495 (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Tags added: verification-needed-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/1954818
Title:
Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish,
and 470 in Focal
Status in nvidia-graphics-drivers-470 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-495 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-470 source package in Bionic:
Invalid
Status in nvidia-graphics-drivers-495 source package in Bionic:
Fix Committed
Status in nvidia-graphics-drivers-470 source package in Focal:
Fix Committed
Status in nvidia-graphics-drivers-495 source package in Focal:
Fix Committed
Status in nvidia-graphics-drivers-470 source package in Hirsute:
Invalid
Status in nvidia-graphics-drivers-495 source package in Hirsute:
Fix Committed
Status in nvidia-graphics-drivers-470 source package in Impish:
Invalid
Status in nvidia-graphics-drivers-495 source package in Impish:
Fix Committed
Bug description:
[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvements.
See the changelog entry below for a full list of changes and bugs.
[Test Case]
The following development and SRU process was followed:
https://wiki.ubuntu.com/NVidiaUpdates
Certification test suite must pass on a range of hardware:
https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu
The QA team that executed the tests will be in charge of attaching the
artifacts and console output of the appropriate run to the bug. nVidia
maintainers team members will not mark ‘verification-done’ until this
has happened.
[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned system level tests are attached to this bug.
[Discussion]
[Changelog]
== 470 (focal only) ==
nvidia-graphics-drivers-470 (470.86-0ubuntu0.20.04.2) focal;
urgency=medium
* debian/{nvidia_supported|pm-aliases-gen}:
- Drop the following IDs in favour of the 495 series (LP: #1954818):
1fbc, 249c, 249d, 24b6, 24b7, 24b8,
25a0, 25b8.
== 495 (bionic, focal, hirsute, impish) ==
nvidia-graphics-drivers-495 (495.46-0ubuntu*)
[ Daniel van Vugt ]
* debian/templates/libnvidia-extra-flavour.links.in:
- Move nvidia-drm_gbm.so into the gbm/ library subdirectory
which is where Mesa searches for it.
[ Alberto Milone ]
* debian/additional_card_ids,
debian/additional_runtimepm_ids:
- Add the following IDs:
1FBC 249C 249D 24B6 24B7 24B8 25A0 25B8
* New upstream release (LP: #1954818):
- Added support for the GBM API. This adds the new symlink
nvidia-drm_gbm.so pointing to the file libnvidia-
allocator.so.VERSION to implement a GBM backend driver usable
with the GBM loader from the Mesa project version 21.2 and
above, as well as the files libnvidia-egl-gbm.so.1.1.0 and
15_nvidia_gbm.json, which implement EGL support for the GBM
platform (EGL_KHR_platform_gbm).
- Add indicator for Resizable BAR support on compatible systems.
- Fixed a bug that could cause the X server to crash when
starting a new server generation on PRIME configurations.
- Removed support for NvIFROpenGL. This functionality was
deprecated in the 470.xx driver release.
- Removed libnvidia-cbl.so from
[Kernel-packages] [Bug 1954818] Please test proposed package
Hello Alberto, or anyone else affected,
Accepted nvidia-graphics-drivers-495 into bionic-proposed. The package
will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-495/495.46-0ubuntu0.18.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/1954818
Title:
Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish,
and 470 in Focal
Status in nvidia-graphics-drivers-470 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-495 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-470 source package in Bionic:
Invalid
Status in nvidia-graphics-drivers-495 source package in Bionic:
Fix Committed
Status in nvidia-graphics-drivers-470 source package in Focal:
Fix Committed
Status in nvidia-graphics-drivers-495 source package in Focal:
Fix Committed
Status in nvidia-graphics-drivers-470 source package in Hirsute:
Invalid
Status in nvidia-graphics-drivers-495 source package in Hirsute:
Fix Committed
Status in nvidia-graphics-drivers-470 source package in Impish:
Invalid
Status in nvidia-graphics-drivers-495 source package in Impish:
Fix Committed
Bug description:
[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvements.
See the changelog entry below for a full list of changes and bugs.
[Test Case]
The following development and SRU process was followed:
https://wiki.ubuntu.com/NVidiaUpdates
Certification test suite must pass on a range of hardware:
https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu
The QA team that executed the tests will be in charge of attaching the
artifacts and console output of the appropriate run to the bug. nVidia
maintainers team members will not mark ‘verification-done’ until this
has happened.
[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned system level tests are attached to this bug.
[Discussion]
[Changelog]
== 470 (focal only) ==
nvidia-graphics-drivers-470 (470.86-0ubuntu0.20.04.2) focal;
urgency=medium
* debian/{nvidia_supported|pm-aliases-gen}:
- Drop the following IDs in favour of the 495 series (LP: #1954818):
1fbc, 249c, 249d, 24b6, 24b7, 24b8,
25a0, 25b8.
== 495 (bionic, focal, hirsute, impish) ==
nvidia-graphics-drivers-495 (495.46-0ubuntu*)
[ Daniel van Vugt ]
* debian/templates/libnvidia-extra-flavour.links.in:
- Move nvidia-drm_gbm.so into the gbm/ library subdirectory
which is where Mesa searches for it.
[ Alberto Milone ]
* debian/additional_card_ids,
debian/additional_runtimepm_ids:
- Add the following IDs:
1FBC 249C 249D 24B6 24B7 24B8 25A0 25B8
* New upstream release (LP: #1954818):
- Added support for the GBM API. This adds the new symlink
nvidia-drm_gbm.so pointing to the file libnvidia-
allocator.so.VERSION to implement a GBM backend driver usable
with the GBM loader from the Mesa project version 21.2 and
above, as well as the files libnvidia-egl-gbm.so.1.1.0 and
15_nvidia_gbm.json, which implement EGL support for the GBM
platform (EGL_KHR_platform_gbm).
- Add indicator for Resizable BAR support on compatible systems.
- Fixed a bug that could cause the X server to crash when
starting a new server generation on PRIME configurations.
- Removed support for NvIFROpenGL. This functionality was
deprecated in the 470.xx driver release.
- Removed libnvidia-cbl.so from the driver package. This
functionality is now provided by other driver libraries.
- Changed the minimum required Linux kernel
[Kernel-packages] [Bug 1954818] Re: Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish, and 470 in Focal
Hello Alberto, or anyone else affected,
Accepted nvidia-graphics-drivers-495 into hirsute-proposed. The package
will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-495/495.46-0ubuntu0.21.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. In either case, without details of your
testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: nvidia-graphics-drivers-495 (Ubuntu Hirsute)
Status: In Progress => Fix Committed
** Tags added: verification-needed-hirsute
** Changed in: nvidia-graphics-drivers-495 (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/1954818
Title:
Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish,
and 470 in Focal
Status in nvidia-graphics-drivers-470 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-495 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-470 source package in Bionic:
Invalid
Status in nvidia-graphics-drivers-495 source package in Bionic:
Fix Committed
Status in nvidia-graphics-drivers-470 source package in Focal:
Fix Committed
Status in nvidia-graphics-drivers-495 source package in Focal:
Fix Committed
Status in nvidia-graphics-drivers-470 source package in Hirsute:
Invalid
Status in nvidia-graphics-drivers-495 source package in Hirsute:
Fix Committed
Status in nvidia-graphics-drivers-470 source package in Impish:
Invalid
Status in nvidia-graphics-drivers-495 source package in Impish:
Fix Committed
Bug description:
[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvements.
See the changelog entry below for a full list of changes and bugs.
[Test Case]
The following development and SRU process was followed:
https://wiki.ubuntu.com/NVidiaUpdates
Certification test suite must pass on a range of hardware:
https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu
The QA team that executed the tests will be in charge of attaching the
artifacts and console output of the appropriate run to the bug. nVidia
maintainers team members will not mark ‘verification-done’ until this
has happened.
[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned system level tests are attached to this bug.
[Discussion]
[Changelog]
== 470 (focal only) ==
nvidia-graphics-drivers-470 (470.86-0ubuntu0.20.04.2) focal;
urgency=medium
* debian/{nvidia_supported|pm-aliases-gen}:
- Drop the following IDs in favour of the 495 series (LP: #1954818):
1fbc, 249c, 249d, 24b6, 24b7, 24b8,
25a0, 25b8.
== 495 (bionic, focal, hirsute, impish) ==
nvidia-graphics-drivers-495 (495.46-0ubuntu*)
[ Daniel van Vugt ]
* debian/templates/libnvidia-extra-flavour.links.in:
- Move nvidia-drm_gbm.so into the gbm/ library subdirectory
which is where Mesa searches for it.
[ Alberto Milone ]
* debian/additional_card_ids,
debian/additional_runtimepm_ids:
- Add the following IDs:
1FBC 249C 249D 24B6 24B7 24B8 25A0 25B8
* New upstream release (LP: #1954818):
- Added support for the GBM API. This adds the new symlink
nvidia-drm_gbm.so pointing to the file libnvidia-
allocator.so.VERSION to implement a GBM backend driver usable
with the GBM loader from the Mesa project version 21.2 and
above, as well as the files libnvidia-egl-gbm.so.1.1.0 and
15_nvidia_gbm.json, which implement EGL support for the GBM
platform (EGL_KHR_platform_gbm).
- Add indicator for Resizable BAR support on compatible systems.
- Fixed a bug that could cause the X server to crash when
starting a new server generation on PRIME configurations.
- Removed support for
[Kernel-packages] [Bug 1953671] Re: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion
I've just updated with the logs from: apport-collect 1953671 Please note: these are gathered when using the 5.13.0-21-generic kernel. However, VMWare Fusion requires at least 5.14, so I have been running v5.14.21-051421-generic day-to-day, and only switched to 5.13.0-21 in order to report these diagnostics. Both v5.15.8 and v5.16-rc5 both hang, so v5.14.21-051421 remains the only kernel I can use at the moment. -- 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/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion Status in linux package in Ubuntu: Confirmed Bug description: I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro per: https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech- preview-now-available.html I am successfully using the 5.14 kernel series (currently 5.14.21-051421-generic) but note this is now EOL. However whenever I try to upgrade to either the 5.15 or 5.16 series my VM hangs at boot time after: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DIB from configuration table EFI stub: Exiting boot services... I see the same "hang" for both 5.15.7 and 5.16-rc4. FYI this has also been reported by others who note that the problem appears to be specific to Ubuntu: https://communities.vmware.com/t5/Fusion-for-Apple-Silicon- Tech/Anyone-have-any-luck-with-Ubuntu-5-15-kernels/m-p/2880362 Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't provide the output from: cat /proc/version However I attach the output from lspci. Please let me know what other information I can provide to help diagnose this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (26 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) Package: linux-image-generic 5.13.0.21.32 [origin: unknown] PackageArchitecture: arm64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash Tags: jammy uec-images third-party-packages Uname: Linux 5.14.21-051421-generic aarch64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: Upgraded to jammy on 2021-11-15 (23 days ago) UserGroups: N/A _MarkForUpload: True --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Dec 17 11:38 seq crw-rw+ 1 root audio 116, 33 Dec 17 11:38 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.13.0-21-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:myitcv 1543 F pipewire CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (34 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: VMware, Inc. VBSA Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=7378d8ea-883e-47b8-b5ab-a92790860f9c ro ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.202 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.13.0-21-generic aarch64 UpgradeStatus: Upgraded to jammy on 2021-11-15 (31 days ago) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/31/2020 dmi.bios.release: 0.0 dmi.bios.vendor: VMware dmi.bios.version: VEFI dmi.board.name: VBSA dmi.board.vendor: VMware dmi.board.version: 1 dmi.chassis.type: 1 dmi.chassis.vendor: VMware dmi.chassis.version: VBSA dmi.ec.firmware.release: 0.0 dmi.modalias:
[Kernel-packages] [Bug 1953671] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1953671/+attachment/5548296/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion Status in linux package in Ubuntu: Confirmed Bug description: I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro per: https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech- preview-now-available.html I am successfully using the 5.14 kernel series (currently 5.14.21-051421-generic) but note this is now EOL. However whenever I try to upgrade to either the 5.15 or 5.16 series my VM hangs at boot time after: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DIB from configuration table EFI stub: Exiting boot services... I see the same "hang" for both 5.15.7 and 5.16-rc4. FYI this has also been reported by others who note that the problem appears to be specific to Ubuntu: https://communities.vmware.com/t5/Fusion-for-Apple-Silicon- Tech/Anyone-have-any-luck-with-Ubuntu-5-15-kernels/m-p/2880362 Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't provide the output from: cat /proc/version However I attach the output from lspci. Please let me know what other information I can provide to help diagnose this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (26 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) Package: linux-image-generic 5.13.0.21.32 [origin: unknown] PackageArchitecture: arm64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash Tags: jammy uec-images third-party-packages Uname: Linux 5.14.21-051421-generic aarch64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: Upgraded to jammy on 2021-11-15 (23 days ago) UserGroups: N/A _MarkForUpload: True --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Dec 17 11:38 seq crw-rw+ 1 root audio 116, 33 Dec 17 11:38 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.13.0-21-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:myitcv 1543 F pipewire CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (34 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: VMware, Inc. VBSA Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=7378d8ea-883e-47b8-b5ab-a92790860f9c ro ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.202 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.13.0-21-generic aarch64 UpgradeStatus: Upgraded to jammy on 2021-11-15 (31 days ago) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/31/2020 dmi.bios.release: 0.0 dmi.bios.vendor: VMware dmi.bios.version: VEFI dmi.board.name: VBSA dmi.board.vendor: VMware dmi.board.version: 1 dmi.chassis.type: 1 dmi.chassis.vendor: VMware dmi.chassis.version: VBSA dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnVMware:bvrVEFI:bd12/31/2020:br0.0:efr0.0:svnVMware,Inc.:pnVBSA:pvr1:rvnVMware:rnVBSA:rvr1:cvnVMware:ct1:cvrVBSA:sku0001: dmi.product.family: VMware dmi.product.name: VBSA dmi.product.sku: 0001 dmi.product.version: 1 dmi.sys.vendor: VMware, Inc. To manage notifications
[Kernel-packages] [Bug 1953671] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1953671/+attachment/5548290/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion Status in linux package in Ubuntu: Confirmed Bug description: I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro per: https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech- preview-now-available.html I am successfully using the 5.14 kernel series (currently 5.14.21-051421-generic) but note this is now EOL. However whenever I try to upgrade to either the 5.15 or 5.16 series my VM hangs at boot time after: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DIB from configuration table EFI stub: Exiting boot services... I see the same "hang" for both 5.15.7 and 5.16-rc4. FYI this has also been reported by others who note that the problem appears to be specific to Ubuntu: https://communities.vmware.com/t5/Fusion-for-Apple-Silicon- Tech/Anyone-have-any-luck-with-Ubuntu-5-15-kernels/m-p/2880362 Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't provide the output from: cat /proc/version However I attach the output from lspci. Please let me know what other information I can provide to help diagnose this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (26 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) Package: linux-image-generic 5.13.0.21.32 [origin: unknown] PackageArchitecture: arm64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash Tags: jammy uec-images third-party-packages Uname: Linux 5.14.21-051421-generic aarch64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: Upgraded to jammy on 2021-11-15 (23 days ago) UserGroups: N/A _MarkForUpload: True --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Dec 17 11:38 seq crw-rw+ 1 root audio 116, 33 Dec 17 11:38 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.13.0-21-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:myitcv 1543 F pipewire CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (34 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: VMware, Inc. VBSA Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=7378d8ea-883e-47b8-b5ab-a92790860f9c ro ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.202 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.13.0-21-generic aarch64 UpgradeStatus: Upgraded to jammy on 2021-11-15 (31 days ago) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/31/2020 dmi.bios.release: 0.0 dmi.bios.vendor: VMware dmi.bios.version: VEFI dmi.board.name: VBSA dmi.board.vendor: VMware dmi.board.version: 1 dmi.chassis.type: 1 dmi.chassis.vendor: VMware dmi.chassis.version: VBSA dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnVMware:bvrVEFI:bd12/31/2020:br0.0:efr0.0:svnVMware,Inc.:pnVBSA:pvr1:rvnVMware:rnVBSA:rvr1:cvnVMware:ct1:cvrVBSA:sku0001: dmi.product.family: VMware dmi.product.name: VBSA dmi.product.sku: 0001 dmi.product.version: 1 dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1953671] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1953671/+attachment/5548295/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion Status in linux package in Ubuntu: Confirmed Bug description: I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro per: https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech- preview-now-available.html I am successfully using the 5.14 kernel series (currently 5.14.21-051421-generic) but note this is now EOL. However whenever I try to upgrade to either the 5.15 or 5.16 series my VM hangs at boot time after: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DIB from configuration table EFI stub: Exiting boot services... I see the same "hang" for both 5.15.7 and 5.16-rc4. FYI this has also been reported by others who note that the problem appears to be specific to Ubuntu: https://communities.vmware.com/t5/Fusion-for-Apple-Silicon- Tech/Anyone-have-any-luck-with-Ubuntu-5-15-kernels/m-p/2880362 Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't provide the output from: cat /proc/version However I attach the output from lspci. Please let me know what other information I can provide to help diagnose this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (26 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) Package: linux-image-generic 5.13.0.21.32 [origin: unknown] PackageArchitecture: arm64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash Tags: jammy uec-images third-party-packages Uname: Linux 5.14.21-051421-generic aarch64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: Upgraded to jammy on 2021-11-15 (23 days ago) UserGroups: N/A _MarkForUpload: True --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Dec 17 11:38 seq crw-rw+ 1 root audio 116, 33 Dec 17 11:38 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.13.0-21-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:myitcv 1543 F pipewire CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (34 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: VMware, Inc. VBSA Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=7378d8ea-883e-47b8-b5ab-a92790860f9c ro ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.202 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.13.0-21-generic aarch64 UpgradeStatus: Upgraded to jammy on 2021-11-15 (31 days ago) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/31/2020 dmi.bios.release: 0.0 dmi.bios.vendor: VMware dmi.bios.version: VEFI dmi.board.name: VBSA dmi.board.vendor: VMware dmi.board.version: 1 dmi.chassis.type: 1 dmi.chassis.vendor: VMware dmi.chassis.version: VBSA dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnVMware:bvrVEFI:bd12/31/2020:br0.0:efr0.0:svnVMware,Inc.:pnVBSA:pvr1:rvnVMware:rnVBSA:rvr1:cvnVMware:ct1:cvrVBSA:sku0001: dmi.product.family: VMware dmi.product.name: VBSA dmi.product.sku: 0001 dmi.product.version: 1 dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go
[Kernel-packages] [Bug 1953671] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1953671/+attachment/5548299/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion Status in linux package in Ubuntu: Confirmed Bug description: I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro per: https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech- preview-now-available.html I am successfully using the 5.14 kernel series (currently 5.14.21-051421-generic) but note this is now EOL. However whenever I try to upgrade to either the 5.15 or 5.16 series my VM hangs at boot time after: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DIB from configuration table EFI stub: Exiting boot services... I see the same "hang" for both 5.15.7 and 5.16-rc4. FYI this has also been reported by others who note that the problem appears to be specific to Ubuntu: https://communities.vmware.com/t5/Fusion-for-Apple-Silicon- Tech/Anyone-have-any-luck-with-Ubuntu-5-15-kernels/m-p/2880362 Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't provide the output from: cat /proc/version However I attach the output from lspci. Please let me know what other information I can provide to help diagnose this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (26 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) Package: linux-image-generic 5.13.0.21.32 [origin: unknown] PackageArchitecture: arm64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash Tags: jammy uec-images third-party-packages Uname: Linux 5.14.21-051421-generic aarch64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: Upgraded to jammy on 2021-11-15 (23 days ago) UserGroups: N/A _MarkForUpload: True --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Dec 17 11:38 seq crw-rw+ 1 root audio 116, 33 Dec 17 11:38 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.13.0-21-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:myitcv 1543 F pipewire CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (34 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: VMware, Inc. VBSA Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=7378d8ea-883e-47b8-b5ab-a92790860f9c ro ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.202 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.13.0-21-generic aarch64 UpgradeStatus: Upgraded to jammy on 2021-11-15 (31 days ago) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/31/2020 dmi.bios.release: 0.0 dmi.bios.vendor: VMware dmi.bios.version: VEFI dmi.board.name: VBSA dmi.board.vendor: VMware dmi.board.version: 1 dmi.chassis.type: 1 dmi.chassis.vendor: VMware dmi.chassis.version: VBSA dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnVMware:bvrVEFI:bd12/31/2020:br0.0:efr0.0:svnVMware,Inc.:pnVBSA:pvr1:rvnVMware:rnVBSA:rvr1:cvnVMware:ct1:cvrVBSA:sku0001: dmi.product.family: VMware dmi.product.name: VBSA dmi.product.sku: 0001 dmi.product.version: 1 dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1953671] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1953671/+attachment/5548297/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion Status in linux package in Ubuntu: Confirmed Bug description: I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro per: https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech- preview-now-available.html I am successfully using the 5.14 kernel series (currently 5.14.21-051421-generic) but note this is now EOL. However whenever I try to upgrade to either the 5.15 or 5.16 series my VM hangs at boot time after: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DIB from configuration table EFI stub: Exiting boot services... I see the same "hang" for both 5.15.7 and 5.16-rc4. FYI this has also been reported by others who note that the problem appears to be specific to Ubuntu: https://communities.vmware.com/t5/Fusion-for-Apple-Silicon- Tech/Anyone-have-any-luck-with-Ubuntu-5-15-kernels/m-p/2880362 Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't provide the output from: cat /proc/version However I attach the output from lspci. Please let me know what other information I can provide to help diagnose this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (26 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) Package: linux-image-generic 5.13.0.21.32 [origin: unknown] PackageArchitecture: arm64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash Tags: jammy uec-images third-party-packages Uname: Linux 5.14.21-051421-generic aarch64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: Upgraded to jammy on 2021-11-15 (23 days ago) UserGroups: N/A _MarkForUpload: True --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Dec 17 11:38 seq crw-rw+ 1 root audio 116, 33 Dec 17 11:38 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.13.0-21-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:myitcv 1543 F pipewire CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (34 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: VMware, Inc. VBSA Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=7378d8ea-883e-47b8-b5ab-a92790860f9c ro ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.202 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.13.0-21-generic aarch64 UpgradeStatus: Upgraded to jammy on 2021-11-15 (31 days ago) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/31/2020 dmi.bios.release: 0.0 dmi.bios.vendor: VMware dmi.bios.version: VEFI dmi.board.name: VBSA dmi.board.vendor: VMware dmi.board.version: 1 dmi.chassis.type: 1 dmi.chassis.vendor: VMware dmi.chassis.version: VBSA dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnVMware:bvrVEFI:bd12/31/2020:br0.0:efr0.0:svnVMware,Inc.:pnVBSA:pvr1:rvnVMware:rnVBSA:rvr1:cvnVMware:ct1:cvrVBSA:sku0001: dmi.product.family: VMware dmi.product.name: VBSA dmi.product.sku: 0001 dmi.product.version: 1 dmi.sys.vendor: VMware, Inc. To manage notifications about this
[Kernel-packages] [Bug 1953671] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1953671/+attachment/5548293/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion Status in linux package in Ubuntu: Confirmed Bug description: I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro per: https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech- preview-now-available.html I am successfully using the 5.14 kernel series (currently 5.14.21-051421-generic) but note this is now EOL. However whenever I try to upgrade to either the 5.15 or 5.16 series my VM hangs at boot time after: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DIB from configuration table EFI stub: Exiting boot services... I see the same "hang" for both 5.15.7 and 5.16-rc4. FYI this has also been reported by others who note that the problem appears to be specific to Ubuntu: https://communities.vmware.com/t5/Fusion-for-Apple-Silicon- Tech/Anyone-have-any-luck-with-Ubuntu-5-15-kernels/m-p/2880362 Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't provide the output from: cat /proc/version However I attach the output from lspci. Please let me know what other information I can provide to help diagnose this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (26 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) Package: linux-image-generic 5.13.0.21.32 [origin: unknown] PackageArchitecture: arm64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash Tags: jammy uec-images third-party-packages Uname: Linux 5.14.21-051421-generic aarch64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: Upgraded to jammy on 2021-11-15 (23 days ago) UserGroups: N/A _MarkForUpload: True --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Dec 17 11:38 seq crw-rw+ 1 root audio 116, 33 Dec 17 11:38 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.13.0-21-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:myitcv 1543 F pipewire CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (34 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: VMware, Inc. VBSA Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=7378d8ea-883e-47b8-b5ab-a92790860f9c ro ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.202 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.13.0-21-generic aarch64 UpgradeStatus: Upgraded to jammy on 2021-11-15 (31 days ago) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/31/2020 dmi.bios.release: 0.0 dmi.bios.vendor: VMware dmi.bios.version: VEFI dmi.board.name: VBSA dmi.board.vendor: VMware dmi.board.version: 1 dmi.chassis.type: 1 dmi.chassis.vendor: VMware dmi.chassis.version: VBSA dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnVMware:bvrVEFI:bd12/31/2020:br0.0:efr0.0:svnVMware,Inc.:pnVBSA:pvr1:rvnVMware:rnVBSA:rvr1:cvnVMware:ct1:cvrVBSA:sku0001: dmi.product.family: VMware dmi.product.name: VBSA dmi.product.sku: 0001 dmi.product.version: 1 dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1953671] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1953671/+attachment/5548300/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion Status in linux package in Ubuntu: Confirmed Bug description: I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro per: https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech- preview-now-available.html I am successfully using the 5.14 kernel series (currently 5.14.21-051421-generic) but note this is now EOL. However whenever I try to upgrade to either the 5.15 or 5.16 series my VM hangs at boot time after: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DIB from configuration table EFI stub: Exiting boot services... I see the same "hang" for both 5.15.7 and 5.16-rc4. FYI this has also been reported by others who note that the problem appears to be specific to Ubuntu: https://communities.vmware.com/t5/Fusion-for-Apple-Silicon- Tech/Anyone-have-any-luck-with-Ubuntu-5-15-kernels/m-p/2880362 Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't provide the output from: cat /proc/version However I attach the output from lspci. Please let me know what other information I can provide to help diagnose this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (26 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) Package: linux-image-generic 5.13.0.21.32 [origin: unknown] PackageArchitecture: arm64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash Tags: jammy uec-images third-party-packages Uname: Linux 5.14.21-051421-generic aarch64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: Upgraded to jammy on 2021-11-15 (23 days ago) UserGroups: N/A _MarkForUpload: True --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Dec 17 11:38 seq crw-rw+ 1 root audio 116, 33 Dec 17 11:38 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.13.0-21-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:myitcv 1543 F pipewire CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (34 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: VMware, Inc. VBSA Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=7378d8ea-883e-47b8-b5ab-a92790860f9c ro ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.202 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.13.0-21-generic aarch64 UpgradeStatus: Upgraded to jammy on 2021-11-15 (31 days ago) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/31/2020 dmi.bios.release: 0.0 dmi.bios.vendor: VMware dmi.bios.version: VEFI dmi.board.name: VBSA dmi.board.vendor: VMware dmi.board.version: 1 dmi.chassis.type: 1 dmi.chassis.vendor: VMware dmi.chassis.version: VBSA dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnVMware:bvrVEFI:bd12/31/2020:br0.0:efr0.0:svnVMware,Inc.:pnVBSA:pvr1:rvnVMware:rnVBSA:rvr1:cvnVMware:ct1:cvrVBSA:sku0001: dmi.product.family: VMware dmi.product.name: VBSA dmi.product.sku: 0001 dmi.product.version: 1 dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go
[Kernel-packages] [Bug 1953671] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1953671/+attachment/5548294/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion Status in linux package in Ubuntu: Confirmed Bug description: I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro per: https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech- preview-now-available.html I am successfully using the 5.14 kernel series (currently 5.14.21-051421-generic) but note this is now EOL. However whenever I try to upgrade to either the 5.15 or 5.16 series my VM hangs at boot time after: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DIB from configuration table EFI stub: Exiting boot services... I see the same "hang" for both 5.15.7 and 5.16-rc4. FYI this has also been reported by others who note that the problem appears to be specific to Ubuntu: https://communities.vmware.com/t5/Fusion-for-Apple-Silicon- Tech/Anyone-have-any-luck-with-Ubuntu-5-15-kernels/m-p/2880362 Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't provide the output from: cat /proc/version However I attach the output from lspci. Please let me know what other information I can provide to help diagnose this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (26 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) Package: linux-image-generic 5.13.0.21.32 [origin: unknown] PackageArchitecture: arm64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash Tags: jammy uec-images third-party-packages Uname: Linux 5.14.21-051421-generic aarch64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: Upgraded to jammy on 2021-11-15 (23 days ago) UserGroups: N/A _MarkForUpload: True --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Dec 17 11:38 seq crw-rw+ 1 root audio 116, 33 Dec 17 11:38 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.13.0-21-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:myitcv 1543 F pipewire CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (34 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: VMware, Inc. VBSA Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=7378d8ea-883e-47b8-b5ab-a92790860f9c ro ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.202 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.13.0-21-generic aarch64 UpgradeStatus: Upgraded to jammy on 2021-11-15 (31 days ago) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/31/2020 dmi.bios.release: 0.0 dmi.bios.vendor: VMware dmi.bios.version: VEFI dmi.board.name: VBSA dmi.board.vendor: VMware dmi.board.version: 1 dmi.chassis.type: 1 dmi.chassis.vendor: VMware dmi.chassis.version: VBSA dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnVMware:bvrVEFI:bd12/31/2020:br0.0:efr0.0:svnVMware,Inc.:pnVBSA:pvr1:rvnVMware:rnVBSA:rvr1:cvnVMware:ct1:cvrVBSA:sku0001: dmi.product.family: VMware dmi.product.name: VBSA dmi.product.sku: 0001 dmi.product.version: 1 dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1953671] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1953671/+attachment/5548292/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion Status in linux package in Ubuntu: Confirmed Bug description: I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro per: https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech- preview-now-available.html I am successfully using the 5.14 kernel series (currently 5.14.21-051421-generic) but note this is now EOL. However whenever I try to upgrade to either the 5.15 or 5.16 series my VM hangs at boot time after: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DIB from configuration table EFI stub: Exiting boot services... I see the same "hang" for both 5.15.7 and 5.16-rc4. FYI this has also been reported by others who note that the problem appears to be specific to Ubuntu: https://communities.vmware.com/t5/Fusion-for-Apple-Silicon- Tech/Anyone-have-any-luck-with-Ubuntu-5-15-kernels/m-p/2880362 Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't provide the output from: cat /proc/version However I attach the output from lspci. Please let me know what other information I can provide to help diagnose this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (26 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) Package: linux-image-generic 5.13.0.21.32 [origin: unknown] PackageArchitecture: arm64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash Tags: jammy uec-images third-party-packages Uname: Linux 5.14.21-051421-generic aarch64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: Upgraded to jammy on 2021-11-15 (23 days ago) UserGroups: N/A _MarkForUpload: True --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Dec 17 11:38 seq crw-rw+ 1 root audio 116, 33 Dec 17 11:38 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.13.0-21-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:myitcv 1543 F pipewire CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (34 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: VMware, Inc. VBSA Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=7378d8ea-883e-47b8-b5ab-a92790860f9c ro ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.202 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.13.0-21-generic aarch64 UpgradeStatus: Upgraded to jammy on 2021-11-15 (31 days ago) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/31/2020 dmi.bios.release: 0.0 dmi.bios.vendor: VMware dmi.bios.version: VEFI dmi.board.name: VBSA dmi.board.vendor: VMware dmi.board.version: 1 dmi.chassis.type: 1 dmi.chassis.vendor: VMware dmi.chassis.version: VBSA dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnVMware:bvrVEFI:bd12/31/2020:br0.0:efr0.0:svnVMware,Inc.:pnVBSA:pvr1:rvnVMware:rnVBSA:rvr1:cvnVMware:ct1:cvrVBSA:sku0001: dmi.product.family: VMware dmi.product.name: VBSA dmi.product.sku: 0001 dmi.product.version: 1 dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1953671] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1953671/+attachment/5548298/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion Status in linux package in Ubuntu: Confirmed Bug description: I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro per: https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech- preview-now-available.html I am successfully using the 5.14 kernel series (currently 5.14.21-051421-generic) but note this is now EOL. However whenever I try to upgrade to either the 5.15 or 5.16 series my VM hangs at boot time after: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DIB from configuration table EFI stub: Exiting boot services... I see the same "hang" for both 5.15.7 and 5.16-rc4. FYI this has also been reported by others who note that the problem appears to be specific to Ubuntu: https://communities.vmware.com/t5/Fusion-for-Apple-Silicon- Tech/Anyone-have-any-luck-with-Ubuntu-5-15-kernels/m-p/2880362 Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't provide the output from: cat /proc/version However I attach the output from lspci. Please let me know what other information I can provide to help diagnose this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (26 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) Package: linux-image-generic 5.13.0.21.32 [origin: unknown] PackageArchitecture: arm64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash Tags: jammy uec-images third-party-packages Uname: Linux 5.14.21-051421-generic aarch64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: Upgraded to jammy on 2021-11-15 (23 days ago) UserGroups: N/A _MarkForUpload: True --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Dec 17 11:38 seq crw-rw+ 1 root audio 116, 33 Dec 17 11:38 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.13.0-21-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:myitcv 1543 F pipewire CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (34 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: VMware, Inc. VBSA Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=7378d8ea-883e-47b8-b5ab-a92790860f9c ro ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.202 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.13.0-21-generic aarch64 UpgradeStatus: Upgraded to jammy on 2021-11-15 (31 days ago) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/31/2020 dmi.bios.release: 0.0 dmi.bios.vendor: VMware dmi.bios.version: VEFI dmi.board.name: VBSA dmi.board.vendor: VMware dmi.board.version: 1 dmi.chassis.type: 1 dmi.chassis.vendor: VMware dmi.chassis.version: VBSA dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnVMware:bvrVEFI:bd12/31/2020:br0.0:efr0.0:svnVMware,Inc.:pnVBSA:pvr1:rvnVMware:rnVBSA:rvr1:cvnVMware:ct1:cvrVBSA:sku0001: dmi.product.family: VMware dmi.product.name: VBSA dmi.product.sku: 0001 dmi.product.version: 1 dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go
[Kernel-packages] [Bug 1953671] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1953671/+attachment/5548291/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion Status in linux package in Ubuntu: Confirmed Bug description: I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro per: https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech- preview-now-available.html I am successfully using the 5.14 kernel series (currently 5.14.21-051421-generic) but note this is now EOL. However whenever I try to upgrade to either the 5.15 or 5.16 series my VM hangs at boot time after: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DIB from configuration table EFI stub: Exiting boot services... I see the same "hang" for both 5.15.7 and 5.16-rc4. FYI this has also been reported by others who note that the problem appears to be specific to Ubuntu: https://communities.vmware.com/t5/Fusion-for-Apple-Silicon- Tech/Anyone-have-any-luck-with-Ubuntu-5-15-kernels/m-p/2880362 Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't provide the output from: cat /proc/version However I attach the output from lspci. Please let me know what other information I can provide to help diagnose this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (26 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) Package: linux-image-generic 5.13.0.21.32 [origin: unknown] PackageArchitecture: arm64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash Tags: jammy uec-images third-party-packages Uname: Linux 5.14.21-051421-generic aarch64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: Upgraded to jammy on 2021-11-15 (23 days ago) UserGroups: N/A _MarkForUpload: True --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Dec 17 11:38 seq crw-rw+ 1 root audio 116, 33 Dec 17 11:38 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.13.0-21-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:myitcv 1543 F pipewire CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (34 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: VMware, Inc. VBSA Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=7378d8ea-883e-47b8-b5ab-a92790860f9c ro ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.202 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.13.0-21-generic aarch64 UpgradeStatus: Upgraded to jammy on 2021-11-15 (31 days ago) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/31/2020 dmi.bios.release: 0.0 dmi.bios.vendor: VMware dmi.bios.version: VEFI dmi.board.name: VBSA dmi.board.vendor: VMware dmi.board.version: 1 dmi.chassis.type: 1 dmi.chassis.vendor: VMware dmi.chassis.version: VBSA dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnVMware:bvrVEFI:bd12/31/2020:br0.0:efr0.0:svnVMware,Inc.:pnVBSA:pvr1:rvnVMware:rnVBSA:rvr1:cvnVMware:ct1:cvrVBSA:sku0001: dmi.product.family: VMware dmi.product.name: VBSA dmi.product.sku: 0001 dmi.product.version: 1 dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1954818] Re: Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish, and 470 in Focal
Hello Alberto, or anyone else affected,
Accepted nvidia-graphics-drivers-495 into impish-proposed. The package
will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-495/495.46-0ubuntu0.21.10.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
impish to verification-done-impish. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-impish. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: nvidia-graphics-drivers-495 (Ubuntu Impish)
Status: In Progress => Fix Committed
** Tags added: verification-needed-impish
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/1954818
Title:
Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish,
and 470 in Focal
Status in nvidia-graphics-drivers-470 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-495 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-470 source package in Bionic:
Invalid
Status in nvidia-graphics-drivers-495 source package in Bionic:
In Progress
Status in nvidia-graphics-drivers-470 source package in Focal:
Fix Committed
Status in nvidia-graphics-drivers-495 source package in Focal:
In Progress
Status in nvidia-graphics-drivers-470 source package in Hirsute:
Invalid
Status in nvidia-graphics-drivers-495 source package in Hirsute:
In Progress
Status in nvidia-graphics-drivers-470 source package in Impish:
Invalid
Status in nvidia-graphics-drivers-495 source package in Impish:
Fix Committed
Bug description:
[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvements.
See the changelog entry below for a full list of changes and bugs.
[Test Case]
The following development and SRU process was followed:
https://wiki.ubuntu.com/NVidiaUpdates
Certification test suite must pass on a range of hardware:
https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu
The QA team that executed the tests will be in charge of attaching the
artifacts and console output of the appropriate run to the bug. nVidia
maintainers team members will not mark ‘verification-done’ until this
has happened.
[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned system level tests are attached to this bug.
[Discussion]
[Changelog]
== 470 (focal only) ==
nvidia-graphics-drivers-470 (470.86-0ubuntu0.20.04.2) focal;
urgency=medium
* debian/{nvidia_supported|pm-aliases-gen}:
- Drop the following IDs in favour of the 495 series (LP: #1954818):
1fbc, 249c, 249d, 24b6, 24b7, 24b8,
25a0, 25b8.
== 495 (bionic, focal, hirsute, impish) ==
nvidia-graphics-drivers-495 (495.46-0ubuntu*)
[ Daniel van Vugt ]
* debian/templates/libnvidia-extra-flavour.links.in:
- Move nvidia-drm_gbm.so into the gbm/ library subdirectory
which is where Mesa searches for it.
[ Alberto Milone ]
* debian/additional_card_ids,
debian/additional_runtimepm_ids:
- Add the following IDs:
1FBC 249C 249D 24B6 24B7 24B8 25A0 25B8
* New upstream release (LP: #1954818):
- Added support for the GBM API. This adds the new symlink
nvidia-drm_gbm.so pointing to the file libnvidia-
allocator.so.VERSION to implement a GBM backend driver usable
with the GBM loader from the Mesa project version 21.2 and
above, as well as the files libnvidia-egl-gbm.so.1.1.0 and
15_nvidia_gbm.json, which implement EGL support for the GBM
platform (EGL_KHR_platform_gbm).
- Add indicator for Resizable BAR support on compatible systems.
- Fixed a bug that could cause the X server to crash when
starting a new server generation on PRIME configurations.
- Removed support for NvIFROpenGL. This functionality was
deprecated in the 470.xx driver release.
- Removed libnvidia-cbl.so from
[Kernel-packages] [Bug 1953671] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1953671/+attachment/5548288/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion Status in linux package in Ubuntu: Confirmed Bug description: I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro per: https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech- preview-now-available.html I am successfully using the 5.14 kernel series (currently 5.14.21-051421-generic) but note this is now EOL. However whenever I try to upgrade to either the 5.15 or 5.16 series my VM hangs at boot time after: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DIB from configuration table EFI stub: Exiting boot services... I see the same "hang" for both 5.15.7 and 5.16-rc4. FYI this has also been reported by others who note that the problem appears to be specific to Ubuntu: https://communities.vmware.com/t5/Fusion-for-Apple-Silicon- Tech/Anyone-have-any-luck-with-Ubuntu-5-15-kernels/m-p/2880362 Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't provide the output from: cat /proc/version However I attach the output from lspci. Please let me know what other information I can provide to help diagnose this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (26 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) Package: linux-image-generic 5.13.0.21.32 [origin: unknown] PackageArchitecture: arm64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash Tags: jammy uec-images third-party-packages Uname: Linux 5.14.21-051421-generic aarch64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: Upgraded to jammy on 2021-11-15 (23 days ago) UserGroups: N/A _MarkForUpload: True --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Dec 17 11:38 seq crw-rw+ 1 root audio 116, 33 Dec 17 11:38 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.13.0-21-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:myitcv 1543 F pipewire CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (34 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: VMware, Inc. VBSA Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=7378d8ea-883e-47b8-b5ab-a92790860f9c ro ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.202 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.13.0-21-generic aarch64 UpgradeStatus: Upgraded to jammy on 2021-11-15 (31 days ago) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/31/2020 dmi.bios.release: 0.0 dmi.bios.vendor: VMware dmi.bios.version: VEFI dmi.board.name: VBSA dmi.board.vendor: VMware dmi.board.version: 1 dmi.chassis.type: 1 dmi.chassis.vendor: VMware dmi.chassis.version: VBSA dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnVMware:bvrVEFI:bd12/31/2020:br0.0:efr0.0:svnVMware,Inc.:pnVBSA:pvr1:rvnVMware:rnVBSA:rvr1:cvnVMware:ct1:cvrVBSA:sku0001: dmi.product.family: VMware dmi.product.name: VBSA dmi.product.sku: 0001 dmi.product.version: 1 dmi.sys.vendor: VMware, Inc. To manage notifications about this bug
[Kernel-packages] [Bug 1953671] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1953671/+attachment/5548289/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion Status in linux package in Ubuntu: Confirmed Bug description: I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro per: https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech- preview-now-available.html I am successfully using the 5.14 kernel series (currently 5.14.21-051421-generic) but note this is now EOL. However whenever I try to upgrade to either the 5.15 or 5.16 series my VM hangs at boot time after: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DIB from configuration table EFI stub: Exiting boot services... I see the same "hang" for both 5.15.7 and 5.16-rc4. FYI this has also been reported by others who note that the problem appears to be specific to Ubuntu: https://communities.vmware.com/t5/Fusion-for-Apple-Silicon- Tech/Anyone-have-any-luck-with-Ubuntu-5-15-kernels/m-p/2880362 Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't provide the output from: cat /proc/version However I attach the output from lspci. Please let me know what other information I can provide to help diagnose this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (26 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) Package: linux-image-generic 5.13.0.21.32 [origin: unknown] PackageArchitecture: arm64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash Tags: jammy uec-images third-party-packages Uname: Linux 5.14.21-051421-generic aarch64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: Upgraded to jammy on 2021-11-15 (23 days ago) UserGroups: N/A _MarkForUpload: True --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Dec 17 11:38 seq crw-rw+ 1 root audio 116, 33 Dec 17 11:38 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.13.0-21-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:myitcv 1543 F pipewire CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (34 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: VMware, Inc. VBSA Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=7378d8ea-883e-47b8-b5ab-a92790860f9c ro ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.202 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.13.0-21-generic aarch64 UpgradeStatus: Upgraded to jammy on 2021-11-15 (31 days ago) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/31/2020 dmi.bios.release: 0.0 dmi.bios.vendor: VMware dmi.bios.version: VEFI dmi.board.name: VBSA dmi.board.vendor: VMware dmi.board.version: 1 dmi.chassis.type: 1 dmi.chassis.vendor: VMware dmi.chassis.version: VBSA dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnVMware:bvrVEFI:bd12/31/2020:br0.0:efr0.0:svnVMware,Inc.:pnVBSA:pvr1:rvnVMware:rnVBSA:rvr1:cvnVMware:ct1:cvrVBSA:sku0001: dmi.product.family: VMware dmi.product.name: VBSA dmi.product.sku: 0001 dmi.product.version: 1 dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1953671] Re: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion
apport information ** Description changed: I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro per: https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech- preview-now-available.html I am successfully using the 5.14 kernel series (currently 5.14.21-051421-generic) but note this is now EOL. However whenever I try to upgrade to either the 5.15 or 5.16 series my VM hangs at boot time after: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DIB from configuration table EFI stub: Exiting boot services... I see the same "hang" for both 5.15.7 and 5.16-rc4. FYI this has also been reported by others who note that the problem appears to be specific to Ubuntu: https://communities.vmware.com/t5/Fusion-for-Apple-Silicon-Tech/Anyone- have-any-luck-with-Ubuntu-5-15-kernels/m-p/2880362 Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't provide the output from: cat /proc/version However I attach the output from lspci. Please let me know what other information I can provide to help diagnose this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (26 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) Package: linux-image-generic 5.13.0.21.32 [origin: unknown] PackageArchitecture: arm64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash Tags: jammy uec-images third-party-packages Uname: Linux 5.14.21-051421-generic aarch64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: Upgraded to jammy on 2021-11-15 (23 days ago) UserGroups: N/A _MarkForUpload: True + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw+ 1 root audio 116, 1 Dec 17 11:38 seq + crw-rw+ 1 root audio 116, 33 Dec 17 11:38 timer + AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.13.0-21-generic. + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu74 + Architecture: arm64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/seq:myitcv 1543 F pipewire + CasperMD5CheckResult: pass + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2021-11-12 (34 days ago) + InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + MachineType: VMware, Inc. VBSA + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + LANG=C.UTF-8 + SHELL=/bin/bash + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=7378d8ea-883e-47b8-b5ab-a92790860f9c ro + ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-5.13.0-21-generic N/A + linux-backports-modules-5.13.0-21-generic N/A + linux-firmware 1.202 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: jammy uec-images + Uname: Linux 5.13.0-21-generic aarch64 + UpgradeStatus: Upgraded to jammy on 2021-11-15 (31 days ago) + UserGroups: N/A + _MarkForUpload: True + acpidump: + + dmi.bios.date: 12/31/2020 + dmi.bios.release: 0.0 + dmi.bios.vendor: VMware + dmi.bios.version: VEFI + dmi.board.name: VBSA + dmi.board.vendor: VMware + dmi.board.version: 1 + dmi.chassis.type: 1 + dmi.chassis.vendor: VMware + dmi.chassis.version: VBSA + dmi.ec.firmware.release: 0.0 + dmi.modalias: dmi:bvnVMware:bvrVEFI:bd12/31/2020:br0.0:efr0.0:svnVMware,Inc.:pnVBSA:pvr1:rvnVMware:rnVBSA:rvr1:cvnVMware:ct1:cvrVBSA:sku0001: + dmi.product.family: VMware + dmi.product.name: VBSA + dmi.product.sku: 0001 + dmi.product.version: 1 + dmi.sys.vendor: VMware, Inc. ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1953671/+attachment/5548287/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion Status in linux package in Ubuntu: Confirmed Bug description: I am
[Kernel-packages] [Bug 1954818] Re: Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish, and 470 in Focal
** Description changed:
[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvements.
See the changelog entry below for a full list of changes and bugs.
[Test Case]
The following development and SRU process was followed:
https://wiki.ubuntu.com/NVidiaUpdates
Certification test suite must pass on a range of hardware:
https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu
The QA team that executed the tests will be in charge of attaching the
artifacts and console output of the appropriate run to the bug. nVidia
maintainers team members will not mark ‘verification-done’ until this
has happened.
[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned system level tests are attached to this bug.
[Discussion]
[Changelog]
== 470 (focal only) ==
nvidia-graphics-drivers-470 (470.86-0ubuntu0.20.04.2) focal;
urgency=medium
- * debian/{nvidia_supported|pm-aliases-gen}:
- - Drop the following IDs in favour of the 495 series (LP: #1954818):
- 1fbc, 249c, 249d, 24b6, 24b7, 24b8,
- 25a0, 25b8.
-
+ * debian/{nvidia_supported|pm-aliases-gen}:
+ - Drop the following IDs in favour of the 495 series (LP: #1954818):
+ 1fbc, 249c, 249d, 24b6, 24b7, 24b8,
+ 25a0, 25b8.
== 495 (bionic, focal, hirsute, impish) ==
nvidia-graphics-drivers-495 (495.46-0ubuntu*)
- * debian/additional_card_ids,
- debian/additional_runtimepm_ids:
- - Add the following IDs:
- 1FBC 249C 249D 24B6 24B7 24B8 25A0 25B8
- * New upstream release (LP: #1954818):
- - Added support for the GBM API. This adds the new symlink
- nvidia-drm_gbm.so pointing to the file libnvidia-
- allocator.so.VERSION to implement a GBM backend driver usable
- with the GBM loader from the Mesa project version 21.2 and
- above, as well as the files libnvidia-egl-gbm.so.1.1.0 and
- 15_nvidia_gbm.json, which implement EGL support for the GBM
- platform (EGL_KHR_platform_gbm).
- - Add indicator for Resizable BAR support on compatible systems.
- - Fixed a bug that could cause the X server to crash when
- starting a new server generation on PRIME configurations.
- - Removed support for NvIFROpenGL. This functionality was
- deprecated in the 470.xx driver release.
- - Removed libnvidia-cbl.so from the driver package. This
- functionality is now provided by other driver libraries.
- - Changed the minimum required Linux kernel version from 2.6.32
- to 3.10.
- - Updated nvidia.ko to load even if no supported NVIDIA GPUs are
- present when an NVIDIA NVSwitch device is detected in the
- system. Previously, nvidia.ko would fail to load into the
- kernel if no supported GPUs were present.
- - Fixed a bug in the Vulkan driver where unused input attributes
- to a vertex shader would corrupt the interpolation qualifiers
- for the shader.
- - Fixed a bug in the Vulkan driver where individual components of
- barycentric inputs could not be read.
- - Added support for the VK_KHR_present_id extension.
- - Added support for the VK_KHR_present_wait extension.
- - Added support for the
- VK_KHR_shader_subgroup_uniform_control_flow extension.
- - Fixed a bug where VK_NVX_binary_import was advertised as
- supported on unsupported platforms. This caused calls to
- vkCreateDevice to fail if applications attempted to enable
- VK_NVX_binary_import on such platforms.
- - Added a new command line option, "--no-peermem", to nvidia-
- installer. Selecting this option prevents the installation of
- the nvidia-peermem kernel module.
- - Fixed a regression which prevented DisplayPort and HDMI 2.1
- variable refresh rate (VRR) G-SYNC Compatible monitors from
- functioning correctly in variable refresh rate mode, resulting
- in issues such as flickering.
- - Fixed a bug that can cause a kernel crash in SLI Mosaic
- configurations.
- - Added support for the EGL_NV_robustness_video_memory_purge
- extension.
+ [ Daniel van Vugt ]
+ * debian/templates/libnvidia-extra-flavour.links.in:
+ - Move nvidia-drm_gbm.so into the gbm/ library subdirectory
+ which is where Mesa searches for it.
+
+ [ Alberto Milone ]
+ * debian/additional_card_ids,
+ debian/additional_runtimepm_ids:
+ - Add the following IDs:
+ 1FBC 249C 249D 24B6 24B7 24B8 25A0 25B8
+
+ * New upstream release (LP: #1954818):
+ - Added support for the GBM API. This adds the new symlink
+ nvidia-drm_gbm.so pointing to the file libnvidia-
+ allocator.so.VERSION to implement a GBM backend driver usable
+ with the GBM loader from the Mesa project version 21.2 and
+ above, as well as the files
[Kernel-packages] [Bug 1954818] Re: Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish, and 470 in Focal
Hello Alberto, or anyone else affected,
Accepted nvidia-graphics-drivers-470 into focal-proposed. The package
will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-470/470.86-0ubuntu0.20.04.2 in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: nvidia-graphics-drivers-470 (Ubuntu Focal)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/1954818
Title:
Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish,
and 470 in Focal
Status in nvidia-graphics-drivers-470 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-495 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-470 source package in Bionic:
Invalid
Status in nvidia-graphics-drivers-495 source package in Bionic:
In Progress
Status in nvidia-graphics-drivers-470 source package in Focal:
Fix Committed
Status in nvidia-graphics-drivers-495 source package in Focal:
In Progress
Status in nvidia-graphics-drivers-470 source package in Hirsute:
Invalid
Status in nvidia-graphics-drivers-495 source package in Hirsute:
In Progress
Status in nvidia-graphics-drivers-470 source package in Impish:
Invalid
Status in nvidia-graphics-drivers-495 source package in Impish:
In Progress
Bug description:
[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvements.
See the changelog entry below for a full list of changes and bugs.
[Test Case]
The following development and SRU process was followed:
https://wiki.ubuntu.com/NVidiaUpdates
Certification test suite must pass on a range of hardware:
https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu
The QA team that executed the tests will be in charge of attaching the
artifacts and console output of the appropriate run to the bug. nVidia
maintainers team members will not mark ‘verification-done’ until this
has happened.
[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned system level tests are attached to this bug.
[Discussion]
[Changelog]
== 470 (focal only) ==
nvidia-graphics-drivers-470 (470.86-0ubuntu0.20.04.2) focal;
urgency=medium
* debian/{nvidia_supported|pm-aliases-gen}:
- Drop the following IDs in favour of the 495 series (LP: #1954818):
1fbc, 249c, 249d, 24b6, 24b7, 24b8,
25a0, 25b8.
== 495 (bionic, focal, hirsute, impish) ==
nvidia-graphics-drivers-495 (495.46-0ubuntu*)
* debian/additional_card_ids,
debian/additional_runtimepm_ids:
- Add the following IDs:
1FBC 249C 249D 24B6 24B7 24B8 25A0 25B8
* New upstream release (LP: #1954818):
- Added support for the GBM API. This adds the new symlink
nvidia-drm_gbm.so pointing to the file libnvidia-
allocator.so.VERSION to implement a GBM backend driver usable
with the GBM loader from the Mesa project version 21.2 and
above, as well as the files libnvidia-egl-gbm.so.1.1.0 and
15_nvidia_gbm.json, which implement EGL support for the GBM
platform (EGL_KHR_platform_gbm).
- Add indicator for Resizable BAR support on compatible systems.
- Fixed a bug that could cause the X server to crash when
starting a new server generation on PRIME configurations.
- Removed support for NvIFROpenGL. This functionality was
deprecated in the 470.xx driver release.
- Removed libnvidia-cbl.so from the driver package. This
functionality is now provided by other driver libraries.
- Changed the minimum required Linux kernel version from 2.6.32
to 3.10.
- Updated nvidia.ko
[Kernel-packages] [Bug 1953249] Re: UVD firmware for AMD Southern Islands (GCN 1) GPUs is missing
** Changed in: linux-firmware (Ubuntu) Status: Confirmed => Fix Released -- 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/1953249 Title: UVD firmware for AMD Southern Islands (GCN 1) GPUs is missing Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Bug description: [ Impact ] AMD GPU not functional on Focal with HWE kernel. [ Test Case ] See original description below. [ Fix ] Cherry-pick relevant commit from upstream linux-firmware. [ Where Problems Could Occur ] Broken graphics with AMD GPUs. [ Original Description ] Release: up-to-date Focal LTS (20.04.3) Package-version: linux-firmware 1.187.20 Hardware model: [AMD/ATI] Chelsea LP [Radeon HD 7730M] With the latest kernel upgrade (5.4 --> 5.11, if I recall correctly), my laptop's discrete graphics stopped working. Looking at the logs, I found these messages: -- snippet -- kernel: [1.492908] [drm] amdgpu: dpm initialized kernel: [1.492932] [drm] AMDGPU Display Connectors kernel: [1.492951] amdgpu :01:00.0: Direct firmware load for amdgpu/verde_uvd.bin failed with error -2 kernel: [1.492954] amdgpu :01:00.0: amdgpu: amdgpu_uvd: Can't load firmware "amdgpu/verde_uvd.bin" kernel: [1.492957] [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* sw_init of IP block failed -2 kernel: [1.493196] amdgpu :01:00.0: amdgpu: amdgpu_device_ip_init failed kernel: [1.493198] amdgpu :01:00.0: amdgpu: Fatal error during GPU init kernel: [1.493200] amdgpu :01:00.0: amdgpu: amdgpu: finishing device. -- snippet -- In fact, file '/lib/firmware/amdgpu/verde_uvd.bin' was missing. Running '$ dpkg -L linux-firmware | sort' gives this: -- snippet -- /lib/firmware/amdgpu/vegam_uvd.bin /lib/firmware/amdgpu/vegam_vce.bin /lib/firmware/amdgpu/verde_ce.bin /lib/firmware/amdgpu/verde_k_smc.bin /lib/firmware/amdgpu/verde_mc.bin /lib/firmware/amdgpu/verde_me.bin /lib/firmware/amdgpu/verde_pfp.bin /lib/firmware/amdgpu/verde_rlc.bin /lib/firmware/amdgpu/verde_smc.bin /lib/firmware/amdgpu/yellow_carp_asd.bin /lib/firmware/amdgpu/yellow_carp_ce.bin -- snippet -- Copying the file from upstream (https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/tree/amdgpu/verde_uvd.bin) didn't work on my system, probably because I use UEFI and the module wasn't signed (error below): -- snippet -- kernel: [ 502.174932] amdgpu :01:00.0: amdgpu: amdgpu_uvd: Can't validate firmware "amdgpu/verde_uvd.bin" kernel: [ 502.174992] [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* sw_init of IP block failed -22 kernel: [ 502.175285] amdgpu :01:00.0: amdgpu: amdgpu_device_ip_init failed kernel: [ 502.175289] amdgpu :01:00.0: amdgpu: Fatal error during GPU init kernel: [ 502.175293] amdgpu :01:00.0: amdgpu: amdgpu: finishing device. -- snippet -- I can confirm that reverting kernel driver to 'radeonsi' makes the device usable again, but at the expense of Vulkan APIs (not supported by this driver). Could you, please, fix this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1953249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954300] Re: mt7921e: Failed to start WM firmware
** No longer affects: linux-oem-5.13 (Ubuntu Impish)
** No longer affects: linux-oem-5.13 (Ubuntu Jammy)
** No longer affects: linux-oem-5.13 (Ubuntu)
** No longer affects: linux-oem-5.14 (Ubuntu Impish)
** No longer affects: linux-oem-5.14 (Ubuntu Jammy)
** No longer affects: linux-oem-5.14 (Ubuntu)
** No longer affects: linux (Ubuntu Focal)
--
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/1954300
Title:
mt7921e: Failed to start WM firmware
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Focal:
Fix Committed
Status in linux-oem-5.13 source package in Focal:
Fix Released
Status in linux-oem-5.14 source package in Focal:
Fix Released
Status in linux source package in Impish:
Fix Committed
Status in linux-firmware source package in Impish:
Fix Committed
Status in linux source package in Jammy:
In Progress
Status in linux-firmware source package in Jammy:
Fix Released
Bug description:
[SRU Justification]
[Impact]
MT7921 might fail at device probe at boot:
mt7921e :03:00.0: WM Firmware Version: 01, Build Time:
20211014150922
IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
mt7921e :03:00.0: Message 8002 (seq 9) timeout
mt7921e :03:00.0: Failed to start WM firmware
mt7921e: probe of :03:00.0 failed with error -110
[Fix]
Kernel fixes:
* 995d948cf2e4 ("Bluetooth: btusb: Return error code when getting patch status
failed")
* 00c0ee9850b7 ("Bluetooth: btusb: Handle download_firmware failure cases")
And firmware:
* 948cad200e94 ("linux-firmware: update frimware for mediatek bluetooth chip
(MT7921)")
[Test Case]
Run checkbox reboot stress tests to try trigger this issue:
$ checkbox-cli run com.canonical.certification::stress/reboot
[Where problems could occur]
This imports fixes requiring both kernel driver and proprietary firmware
updates, the firmware part might cause instability or so.
== original bug report ==
Oct 25 22:40:10 u kernel: [ 6.194102] mt7921e :03:00.0: WM Firmware
Version: 01, Build Time: 20211014150922
Oct 25 22:40:11 u kernel: [ 7.948458] rfkill: input handler disabled
Oct 25 22:40:12 u kernel: [ 9.012741] r8169 :02:00.0 enp2s0: Link is Up -
1Gbps/Full - flow control rx/tx
Oct 25 22:40:12 u kernel: [ 9.012766] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0:
link becomes ready
Oct 25 22:40:13 u kernel: [ 9.174471] usb 1-2.4: device descriptor read/64,
error -110
Oct 25 22:40:13 u kernel: [ 9.250459] mt7921e :03:00.0: Message 8002
(seq 9) timeout
Oct 25 22:40:13 u kernel: [ 9.250470] mt7921e :03:00.0: Failed to start
WM firmware
Oct 25 22:40:13 u kernel: [ 9.250596] mt7921e: probe of :03:00.0 failed
with error -110
This takes following fixes to resolve completely:
* kernel patch:
*
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=995d948cf2e45834275f07afc1c9881a9902e73c
*
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=00c0ee9850b7b0cb7c40b8daba806ae2245e59d4
* firmware:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=948cad200e94d82d339207f8ac7b10f932bd627a
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1954300/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950720] Re: GSYNC bug regression in 495.44 Ubuntu 21.10
This problem persists on driver 495.46 from NVIDIA website which stated the same regression fix in the patch notes, there was no change in the flickering on G-SYNC mode change. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1950720 Title: GSYNC bug regression in 495.44 Ubuntu 21.10 Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-495 package in Ubuntu: Confirmed Bug description: Similar to bug https://launchpad.net/bugs/1950665, the GSYNC regression bug has returned in 495.44 on Ubuntu 21.10. I have tried the standard kernel and 5.14.1 and 5.14.17, but they are all experiencing the same bug again. Hardware is: - NVIDIA GeForce RTX 2080 Super - Dell 27" S2721DGF G-Sync Compatible monitor - High quality DisplayPort cable (This was replaced previously under suspicion) This issue happens at all refresh rates: 60 Hz, 120 Hz, 144 Hz and 165 Hz. Prior to upgrading to Ubuntu 21.10, I had upgraded to 495.44 on Ubuntu 21.04 and kernel 5.14.1, and this problem was not present. I then upgraded to Ubuntu 21.10, and the problem didn't seem to be present, but as of today I've noticed again. I'm not sure what the cause is, but I have tried full driver purges, returned to 470.82, went back to the standard kernel for 21.10 (5.13.0-21-generic), 5.14.1 and 5.14.17, and the problem continues to occur when any GPU accelerated application starts, in some cases when switching between applications (i.e. alt tabbing out of a game). A second or so of no signal occurs as it re-syncs. I am unsure if X11 has been updated in this time, I know there was work happening on GBM support, wondering if X11 has switched to using this instead of the EGL Streams direct approach that was used previously. Either-way, I'm still running X11 in all of these tests. Let me know if there are any tests you'd like me to try. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1950720/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930086] Re: [22.04 FEAT] gcc tunings for power9
now built in jammy-proposed ** Changed in: llvm-toolchain-13 (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930086 Title: [22.04 FEAT] gcc tunings for power9 Status in The Ubuntu-power-systems project: In Progress Status in gcc-11 package in Ubuntu: In Progress Status in linux package in Ubuntu: Incomplete Status in llvm-toolchain-13 package in Ubuntu: Fix Committed Bug description: This is an Ubuntu-power-systems 22.04 LTS feature bug to track changing the gcc configure options from --with-cpu=power8 to --with- cpu=power9. Prerequisites for this bug include power9 builder hardware in Canonical datacenter. I'm still learning my way around Debian/Ubuntu source so go easy on me if this isn't the correct branch: https://salsa.debian.org/toolchain- team/gcc/-/blob/gcc-10-debian/debian/rules2#L394 But we'll want to add some logic around line 394 to add --with- cpu=power9 for 22.04 and possibly --with-tune=? but I'll reverse mirror this bug and verify with our IBM Power toolchain architect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1930086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945565] Re: [SRU] Revert amdgpu/renoir firmware
doesn't look like anything left to do to the kernel here ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1945565 Title: [SRU] Revert amdgpu/renoir firmware Status in OEM Priority Project: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Won't Fix Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Invalid Bug description: [Impact] The USB-type-C port is useless when uplug the USB-type-C <-> DP/HDMI/VGA Dongle after the system resumed from S3. [Fix] Revert below change, this issue is gone. commit a543b9c1bfd12e60d962acd48108234481a8581f Author: Alex Deucher Date: Thu Jul 1 12:23:11 2021 +0800 amdgpu: update renoir firmware from 21.20 BugLink: https://bugs.launchpad.net/bugs/1934014 From internal git commit: 8b05e03570818d047d7ea0a7388c89c4192fd20b Signed-off-by: Alex Deucher Signed-off-by: Josh Boyer (backported from commit 56ef642160203f8be7e1334feca4a76852c74bc0) [khfeng: Squashed multiple updates into one commit] Signed-off-by: Kai-Heng Feng Signed-off-by: Timo Aaltonen [Test] Verify S3 on renoir's platforms. [Where problems could occur] Renoir based systems can't resume from s2idle. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1945565/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
I'm still having issues with this driver on Kernels later than 5.11 installed with Ubuntu Mainline - can it be the case that these drivers are not set for those? Here is a full dmesg output: [4.557452] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [4.557589] sof-audio-pci-intel-tgl :00:1f.3: SoundWire enabled on CannonLake+ platform, using SOF driver [4.557639] sof-audio-pci-intel-tgl :00:1f.3: enabling device ( -> 0002) [4.557935] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [4.558004] sof-audio-pci-intel-tgl :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.565246] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode [4.579175] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 4 [4.662581] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 1:6:1-53680 [4.662585] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:17:0 Kernel ABI 3:18:0 [4.701918] sof-audio-pci-intel-tgl :00:1f.3: Topology: ABI 3:17:0 Kernel ABI 3:18:0 [4.714224] sof-audio-pci-intel-tgl :00:1f.3: ASoC: physical link SDW3-Capture (id 4) not exist [4.714254] sof-audio-pci-intel-tgl :00:1f.3: ASoC: topology: could not load header: -22 [4.714331] sof-audio-pci-intel-tgl :00:1f.3: error: tplg component load failed -22 [4.714360] sof-audio-pci-intel-tgl :00:1f.3: error: failed to load DSP topology -22 [4.714383] sof-audio-pci-intel-tgl :00:1f.3: ASoC: error at snd_soc_component_probe on :00:1f.3: -22 [4.714424] sof_sdw sof_sdw: ASoC: failed to instantiate card -22 [4.720966] sof_sdw sof_sdw: snd_soc_register_card failed -22 [4.720985] sof_sdw: probe of sof_sdw failed with error -22 Anything I could do? -- 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/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in linux package in Ubuntu: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: This patch is for soundwire audio, and only ubuntu 5.11-generic and later kernels support soundwire audio driver, so this patch is not sent to groovy and focal kernels. For oem-5.10 and oem-5.13 kernels, since this bug is not from OEM project, it is not urgent to merge this patch to OEM kenrels, after the patch is in the hirsute and impish kernels, the oem kernels will have this patch when syncing with generic kernels. [Impact] On the Dell XPS 17 (9710) machine, the audio card is not detected when booting hirsute or impish kernels. So the audio doesn't work on this machine with ubuntu linux 21.04 or 21.10. [Fix] Backport a upstream patch, this will set the correct codec config for this machine: rt711 for headset, dual rt1308 for spks and rt715 for internal mic. [Test] Booting up with the patched kernel, the audio card is detected, test internal speaker and internal mic, all work well, plug a headset, the headphone and external mic work well too. [Where problems could occur] This change only applis to the Dell machines with the DMI_PRODUCT_SKU equals to "0A5D", if this could introduce the regression, it will make the audio (speaker, internal mic and headset) can't work anymore on the Dell machine with that PRODUCT_SKU, but this possibility is very low, and we tested the patch on the machine, so far no regression is found. No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install)
[Kernel-packages] [Bug 1955108] [NEW] package linux-headers-5.11.0-43-generic 5.11.0-43.47~20.04.2 failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-43-generic/include/config/te
Public bug reported: occurred during apt upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-headers-5.11.0-43-generic 5.11.0-43.47~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: linux-headers-5.11.0-43-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Dec 17 13:28:30 2021 DpkgTerminalLog: Preparing to unpack .../linux-headers-5.11.0-43-generic_5.11.0-43.47~20.04.2_amd64.deb ... Unpacking linux-headers-5.11.0-43-generic (5.11.0-43.47~20.04.2) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/linux-headers-5.11.0-43-generic_5.11.0-43.47~20.04.2_amd64.deb (--unpack): unable to open '/usr/src/linux-headers-5.11.0-43-generic/include/config/textsearch/fsm.h.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-5.11.0-43-generic/include/config/textsearch/fsm.h.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-09-24 (83 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-hwe-5.11 Title: package linux-headers-5.11.0-43-generic 5.11.0-43.47~20.04.2 failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-43-generic/include/config/textsearch/fsm.h.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1955108 Title: package linux-headers-5.11.0-43-generic 5.11.0-43.47~20.04.2 failed to install/upgrade: unable to open '/usr/src/linux- headers-5.11.0-43-generic/include/config/textsearch/fsm.h.dpkg-new': Operation not permitted Status in linux-hwe-5.11 package in Ubuntu: New Bug description: occurred during apt upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-headers-5.11.0-43-generic 5.11.0-43.47~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: linux-headers-5.11.0-43-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Dec 17 13:28:30 2021 DpkgTerminalLog: Preparing to unpack .../linux-headers-5.11.0-43-generic_5.11.0-43.47~20.04.2_amd64.deb ... Unpacking linux-headers-5.11.0-43-generic (5.11.0-43.47~20.04.2) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/linux-headers-5.11.0-43-generic_5.11.0-43.47~20.04.2_amd64.deb (--unpack): unable to open '/usr/src/linux-headers-5.11.0-43-generic/include/config/textsearch/fsm.h.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-5.11.0-43-generic/include/config/textsearch/fsm.h.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-09-24 (83 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-hwe-5.11 Title: package linux-headers-5.11.0-43-generic 5.11.0-43.47~20.04.2 failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-43-generic/include/config/textsearch/fsm.h.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1955108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
