[Kernel-packages] [Bug 1978530] [NEW] [8086:7af0][8086:40c4] Missing support for Intel AX204 NGW wireless card
Public bug reported:
commit ac4790dcd0ff ("iwlwifi: pcie: add support for MS devices").
*
https://patchwork.kernel.org/project/linux-wireless/patch/iwlwifi.20220129105618.a82ca9207ace.I38aa0acfb7846b179027b6f87f5f88f8e4177f63@changeid/
*
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ac4790dcd0ffede2085a54ab12a4b70a48789215
** Affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-oem-5.17 (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux-firmware (Ubuntu Jammy)
Importance: Undecided
Status: New
** Affects: linux-oem-5.17 (Ubuntu Jammy)
Importance: High
Assignee: You-Sheng Yang (vicamo)
Status: In Progress
** Affects: linux-firmware (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Affects: linux-oem-5.17 (Ubuntu Kinetic)
Importance: Undecided
Status: Invalid
** Also affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.17 (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.17 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Description changed:
- TBD.
+ commit ac4790dcd0ff ("iwlwifi: pcie: add support for MS devices").
+
+ *
https://patchwork.kernel.org/project/linux-wireless/patch/iwlwifi.20220129105618.a82ca9207ace.I38aa0acfb7846b179027b6f87f5f88f8e4177f63@changeid/
+ *
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ac4790dcd0ffede2085a54ab12a4b70a48789215
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1978530
Title:
[8086:7af0][8086:40c4] Missing support for Intel AX204 NGW wireless
card
Status in linux-firmware package in Ubuntu:
New
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux-firmware source package in Jammy:
New
Status in linux-oem-5.17 source package in Jammy:
In Progress
Status in linux-firmware source package in Kinetic:
New
Status in linux-oem-5.17 source package in Kinetic:
Invalid
Bug description:
commit ac4790dcd0ff ("iwlwifi: pcie: add support for MS devices").
*
https://patchwork.kernel.org/project/linux-wireless/patch/iwlwifi.20220129105618.a82ca9207ace.I38aa0acfb7846b179027b6f87f5f88f8e4177f63@changeid/
*
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ac4790dcd0ffede2085a54ab12a4b70a48789215
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1978530/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978530] Re: [8086:7af0][8086:40c4] Missing support for Intel AX204 NGW wireless card
Commit ac4790dcd0ff landed in v5.18-rc1, so this affects only oem-5.17
kernel in jammy.
While it's corresponding firmware, iwlwifi-so-a0-mr-a0-*, is not yet
available in either
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git or
https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-
firmware.git, it affects linux-firmware in both kinetic and jammy.
** Changed in: linux-oem-5.17 (Ubuntu Kinetic)
Status: New => Invalid
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
--
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/1978530
Title:
[8086:7af0][8086:40c4] Missing support for Intel AX204 NGW wireless
card
Status in linux-firmware package in Ubuntu:
New
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux-firmware source package in Jammy:
New
Status in linux-oem-5.17 source package in Jammy:
In Progress
Status in linux-firmware source package in Kinetic:
New
Status in linux-oem-5.17 source package in Kinetic:
Invalid
Bug description:
commit ac4790dcd0ff ("iwlwifi: pcie: add support for MS devices").
*
https://patchwork.kernel.org/project/linux-wireless/patch/iwlwifi.20220129105618.a82ca9207ace.I38aa0acfb7846b179027b6f87f5f88f8e4177f63@changeid/
*
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ac4790dcd0ffede2085a54ab12a4b70a48789215
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1978530/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967274] Re: Screen sometimes can't update [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
Thank you Daniel!
I have added the bug information here:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1978534
--
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/1967274
Title:
Screen sometimes can't update [Failed to post KMS update: CRTC
property (GAMMA_LUT) not found]
Status in Mutter:
Fix Released
Status in OEM Priority Project:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in mutter package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in mutter source package in Jammy:
Fix Released
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
==
SRU Justification
[Impact]
The backlight power won't come back after the meta + l to turn off the
display on ADL machines.
[Fix]
Below series of commits from v5.17 fix this issue
1c7ab5affa5e drm/i915/xelpd: Add Pipe Color Lut caps to platform config
17815f624a90 drm/i915/xelpd: Enable Pipe Degamma
e83c18cffaed drm/i915/xelpd: Enable Pipe color support for D13 platform
[Test]
Verified on at least 2 different machines, the backlight is on after the
screen dimmed with touchpad movement or key stroke.
[Where problems could occcur]
The patches only affect ADL-P and up.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1920774] Re: v5.11 kernel seems to sometimes hang on unmatched board
** Changed in: linux-riscv (Ubuntu) Status: Expired => Incomplete ** Changed in: linux-riscv (Ubuntu) Importance: Undecided => Low ** Changed in: linux-riscv (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1920774 Title: v5.11 kernel seems to sometimes hang on unmatched board Status in linux-riscv package in Ubuntu: Incomplete Bug description: v5.11 kernel seems to sometimes hang on unmatched board To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1920774/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978530] Re: [8086:7af0][8086:40c4] Missing support for Intel AX204 NGW wireless card
Proposed kernel fix included in experimental kernel starting from
version 5.17.0-9008.8+exp.23 in https://launchpad.net/~canonical-hwe-
team/+archive/ubuntu/intermediate-kernel
--
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/1978530
Title:
[8086:7af0][8086:40c4] Missing support for Intel AX204 NGW wireless
card
Status in linux-firmware package in Ubuntu:
New
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux-firmware source package in Jammy:
New
Status in linux-oem-5.17 source package in Jammy:
In Progress
Status in linux-firmware source package in Kinetic:
New
Status in linux-oem-5.17 source package in Kinetic:
Invalid
Bug description:
commit ac4790dcd0ff ("iwlwifi: pcie: add support for MS devices").
*
https://patchwork.kernel.org/project/linux-wireless/patch/iwlwifi.20220129105618.a82ca9207ace.I38aa0acfb7846b179027b6f87f5f88f8e4177f63@changeid/
*
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ac4790dcd0ffede2085a54ab12a4b70a48789215
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1978530/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978539] [NEW] nvidia-dkms-470 fails to build with kernel 5.19
Public bug reported: [Impact] nvidia-dkms-470 fails to build on kinetic with the new (upcoming) kernel 5.19. [Test case] sudo apt install nvidia-dkms-470 [Fix] Change driver to support the new 5.19 ABI. [Regression potential] We may see build issues / regressions in kernels >= 5.19, since the fix are only affecting kernels >= 5.19. ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-470 (Ubuntu Kinetic) Importance: Undecided Status: New ** Tags: patch ** Also affects: nvidia-graphics-drivers-470 (Ubuntu Kinetic) Importance: Undecided Status: New -- 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/1978539 Title: nvidia-dkms-470 fails to build with kernel 5.19 Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in nvidia-graphics-drivers-470 source package in Kinetic: New Bug description: [Impact] nvidia-dkms-470 fails to build on kinetic with the new (upcoming) kernel 5.19. [Test case] sudo apt install nvidia-dkms-470 [Fix] Change driver to support the new 5.19 ABI. [Regression potential] We may see build issues / regressions in kernels >= 5.19, since the fix are only affecting kernels >= 5.19. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1978539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978539] Re: nvidia-dkms-470 fails to build with kernel 5.19
debdiff in attach fixes all the build failures with kernels >= 5.19. ** Patch added: "support-linux-5.19-nvidia-470.debdiff" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1978539/+attachment/5597189/+files/support-linux-5.19-nvidia-470.debdiff -- 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/1978539 Title: nvidia-dkms-470 fails to build with kernel 5.19 Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in nvidia-graphics-drivers-470 source package in Kinetic: New Bug description: [Impact] nvidia-dkms-470 fails to build on kinetic with the new (upcoming) kernel 5.19. [Test case] sudo apt install nvidia-dkms-470 [Fix] Change driver to support the new 5.19 ABI. [Regression potential] We may see build issues / regressions in kernels >= 5.19, since the fix are only affecting kernels >= 5.19. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1978539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978539] Re: nvidia-dkms-470 fails to build with kernel 5.19
** Tags added: patch -- 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/1978539 Title: nvidia-dkms-470 fails to build with kernel 5.19 Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in nvidia-graphics-drivers-470 source package in Kinetic: New Bug description: [Impact] nvidia-dkms-470 fails to build on kinetic with the new (upcoming) kernel 5.19. [Test case] sudo apt install nvidia-dkms-470 [Fix] Change driver to support the new 5.19 ABI. [Regression potential] We may see build issues / regressions in kernels >= 5.19, since the fix are only affecting kernels >= 5.19. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1978539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973434] Re: massive performance issues since 22.04 upgrade
For what it is worth, I am experiencing what seems like the exact same issues as Henning, on a Thinkpad T470s after upgrading from 21.10 to 22.04. I am pretty confident there were no problems at all with 21.10, now my whole system and especially things like videos running in chrome gets extremely lagging after the system has been running for a few hours. I tend to do daily reboots just to have the system in a useable state. I am on 5.15.0-37-generic and have also applied the IOMMU fix without any noticeable effects. A workaround is strongly needed. Please instruct me if there is any information I can provide from my side/any things to try out. -- 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/1973434 Title: massive performance issues since 22.04 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Hi, After upgrading to 22.04 i had to fight with massive performance issues. Browsers appeared to hang every other minute, youtube videos being laggy and hang in between, applications in a virtualbox VM where slow and also hanging every other minute to a level of not being useable. On a pretty recent and powerful system just 2 years old. I noticed CPU jumps in top, but also somehow thought it could be a graphics issue so invested some time installing nvidia drivers properly. Also I wondered if it might be the lowlatency kernel I normally use because I do audio stuff, and switched to generic. But nothing helped. ThenI had the idea it could be a kernel/scheduler issue because the system wasn't always slow, but it appeared certain things kept hanging when other processed had a lot of cpu for a few seconds. So I got a recent mainline kernel, configured it with my last running config from 21.10 before the update, made the debs and installed them, and now can tell that a mainline kernel 5.17.7 with all the dkms modules that i had before which got compiled automatically at installation brings back a "normal" performance. I can browse the web, run multiple youtube vids at once, even in another browser, have thunderbird running, and a virtualbox machine open with another browser for some web app testing and everything runs fine and smooth, no lagging. Not sure yet what the real reason is - either the kernel version, or a patch in the ubuntu version, or the 22.04 kernel config so far, or some configuration made in 21.10 that isn't good with 22.04 and it's kernel anymore. I will go ahead tomorrow and see if I can build a vanilla kernel with the config from the ubuntu 22.04 kernel and "make oldconfig", then I will be able to tell if only the config is making the difference. Please let me know of there is anything I should test to further analyze this issue, or any ideas I can try to solve it without having to run a mainline manually installed kernel. Thanks. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.30.33 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: henning6198 F pulseaudio /dev/snd/controlC1: henning6198 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 14 23:02:38 2022 InstallationDate: Installed on 2020-04-12 (761 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QV00CEGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=/dev/mapper/vgubuntu-root ro RelatedPackageVersions: linux-restricted-modules-5.15.0-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago) dmi.bios.date: 12/06/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET55W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QV00CEGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 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.23 dmi.modalias: dmi:bvnLENOVO:bvrN2OET55W(1.42):bd12/06/2021:br1.42:efr1.23:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QV00CEGE dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO To manag
[Kernel-packages] [Bug 1978380] Re: External monitor not detected
hello. But what about Windows 10? It works perfectly on Windows with HDMI port in switchable graphics mode? -- 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/1978380 Title: External monitor not detected Status in linux package in Ubuntu: Invalid Bug description: Hello. I have a laptop Lenovo Legion Y540-15IRH (81SX00EVRA) with Hybrid graphics. OS: 20.04.4 LTS and Windows 10 in dual boot. BIOS is set to Switchable Graphics, meaning Hybrid. NVidia PRIME profile is set to Intel (power saving). So the problem is that on Ubuntu system doesn't detect an external monitor through HDMI port. When PRIME profile was set to NVidia best Performance - it was able to detect the external monitor. But as I am not playing games anymore - I don't want to use power-consuming and noisy discrete RTX 2060. So I switched to integrated Intel UHD Graphics 630. What should I do in order OS to detect an external monitor? Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 11 14:41:50 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.13.0-44-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.13.0-48-generic, x86_64: installed nvidia, 470.129.06, 5.13.0-44-generic, x86_64: installed nvidia, 470.129.06, 5.13.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:3ffd] NVIDIA Corporation TU106M [GeForce RTX 2060 Mobile] [10de:1f11] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU106M [GeForce RTX 2060 Mobile] [17aa:3ffd] InstallationDate: Installed on 2020-10-21 (597 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 81SX ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-48-generic root=UUID=96af554d-dedb-4846-b7ca-651771269b4c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2022 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y540-15IRH dmi.ec.firmware.release: 1.44 dmi.modalias: dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81SX:pvrLegionY540-15IRH:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegionY540-15IRH:skuLENOVO_MT_81SX_BU_idea_FM_LegionY540-15IRH: dmi.product.family: Legion Y540-15IRH dmi.product.name: 81SX dmi.product.sku: LENOVO_MT_81SX_BU_idea_FM_Legion Y540-15IRH dmi.product.version: Legion Y540-15IRH dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978380/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978380] Re: External monitor not detected
It's unlikely the HDMI port is hardware-switchable independently from the GPU. What Windows would be doing is keeping the Nvidia driver always-enabled so you can always use the HDMI port, but just preferring that GPU rendering be done on Intel when in integrated mode. That's actually what GNOME does by default so you don't need to "switch" anything. -- 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/1978380 Title: External monitor not detected Status in linux package in Ubuntu: Invalid Bug description: Hello. I have a laptop Lenovo Legion Y540-15IRH (81SX00EVRA) with Hybrid graphics. OS: 20.04.4 LTS and Windows 10 in dual boot. BIOS is set to Switchable Graphics, meaning Hybrid. NVidia PRIME profile is set to Intel (power saving). So the problem is that on Ubuntu system doesn't detect an external monitor through HDMI port. When PRIME profile was set to NVidia best Performance - it was able to detect the external monitor. But as I am not playing games anymore - I don't want to use power-consuming and noisy discrete RTX 2060. So I switched to integrated Intel UHD Graphics 630. What should I do in order OS to detect an external monitor? Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 11 14:41:50 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.13.0-44-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.13.0-48-generic, x86_64: installed nvidia, 470.129.06, 5.13.0-44-generic, x86_64: installed nvidia, 470.129.06, 5.13.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:3ffd] NVIDIA Corporation TU106M [GeForce RTX 2060 Mobile] [10de:1f11] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU106M [GeForce RTX 2060 Mobile] [17aa:3ffd] InstallationDate: Installed on 2020-10-21 (597 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 81SX ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-48-generic root=UUID=96af554d-dedb-4846-b7ca-651771269b4c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2022 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y540-15IRH dmi.ec.firmware.release: 1.44 dmi.modalias: dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81SX:pvrLegionY540-15IRH:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegionY540-15IRH:skuLENOVO_MT_81SX_BU_idea_FM_LegionY540-15IRH: dmi.product.family: Legion Y540-15IRH dmi.product.name: 81SX dmi.product.sku: LENOVO_MT_81SX_BU_idea_FM_Legion Y540-15IRH dmi.product.version: Legion Y540-15IRH dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978380/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1966066] Re: audio from external sound card is distorted
Hi Anas Ghrab,
Does this issue exist with older Jammy 5.15 kernel?
For Jammy 5.15, this patch should already landed in:
https://launchpad.net/ubuntu/+source/linux/5.15.0-14.14
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1966066
Title:
audio from external sound card is distorted
Status in linux package in Ubuntu:
Fix Committed
Status in linux-signed-hwe-5.13 package in Ubuntu:
Invalid
Status in linux source package in Impish:
Fix Released
Status in linux-signed-hwe-5.13 source package in Impish:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux-signed-hwe-5.13 source package in Jammy:
Invalid
Bug description:
[Impact]
Commit d215f63d49da ("ALSA: usb-audio: Check available frames for the
next packet size") landed in 5.13.0-35 introduced regression to USB
audio device.
It's because this patch introduced the available frame size check, but
the conversion forgot to initialize the temporary variable properly.
A workaround is to modify /etc/pulse/daemon.conf, set the
default-sample-rate to 48000, uncomment it by removing the semicolon
at the beginning of the line. And restart pulseaudio with:
systemctl --user restart pulseaudio.service
[Fix]
* 23939115 ALSA: usb-audio: Fix packet size calculation regression
This patch can be cherry-picked into Impish kernel, and it's already in
the master-next branch of Jammy tree.
[Test]
Test kernels built with 5.13.0-37 + this patch, can be found in:
* Focal-5.13 -
https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/focal/
* Impish-5.13 -
https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/impish/
Both kernels were tested by affected users and they're working as
expected.
[Where problems could occur]
If this patch is incorrect, it might affect USB audio devices.
[Original Bug Report]
The sound card is a Focusrite Scarlett 2i2.
The sound is distorted everywhere.
Sound via HDMI works.
Seen others having the same problem:
(Edit because of previously wrong link here)
https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card
ubuntu release: Ubuntu 20.04.4 LTS
package name involved in bug: linux-image-5.13.0-37-generic
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 23 12:56:02 2022
InstallationDate: Installed on 2020-12-18 (459 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: linux-signed-hwe-5.13
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966066/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978539] Re: nvidia-dkms-470 fails to build with kernel 5.19
same fixes for nvidia-dkms-510. ** Patch added: "support-linux-5.19-nvidia-510.debdiff" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1978539/+attachment/5597215/+files/support-linux-5.19-nvidia-510.debdiff -- 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/1978539 Title: nvidia-dkms-470 fails to build with kernel 5.19 Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in nvidia-graphics-drivers-470 source package in Kinetic: New Bug description: [Impact] nvidia-dkms-470 fails to build on kinetic with the new (upcoming) kernel 5.19. [Test case] sudo apt install nvidia-dkms-470 [Fix] Change driver to support the new 5.19 ABI. [Regression potential] We may see build issues / regressions in kernels >= 5.19, since the fix are only affecting kernels >= 5.19. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1978539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978380] Re: External monitor not detected
So using USB-C adapter or the Mini DisplayPort instead of HDMI will go the trick ? -- 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/1978380 Title: External monitor not detected Status in linux package in Ubuntu: Invalid Bug description: Hello. I have a laptop Lenovo Legion Y540-15IRH (81SX00EVRA) with Hybrid graphics. OS: 20.04.4 LTS and Windows 10 in dual boot. BIOS is set to Switchable Graphics, meaning Hybrid. NVidia PRIME profile is set to Intel (power saving). So the problem is that on Ubuntu system doesn't detect an external monitor through HDMI port. When PRIME profile was set to NVidia best Performance - it was able to detect the external monitor. But as I am not playing games anymore - I don't want to use power-consuming and noisy discrete RTX 2060. So I switched to integrated Intel UHD Graphics 630. What should I do in order OS to detect an external monitor? Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 11 14:41:50 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.13.0-44-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.13.0-48-generic, x86_64: installed nvidia, 470.129.06, 5.13.0-44-generic, x86_64: installed nvidia, 470.129.06, 5.13.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:3ffd] NVIDIA Corporation TU106M [GeForce RTX 2060 Mobile] [10de:1f11] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU106M [GeForce RTX 2060 Mobile] [17aa:3ffd] InstallationDate: Installed on 2020-10-21 (597 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 81SX ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-48-generic root=UUID=96af554d-dedb-4846-b7ca-651771269b4c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2022 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y540-15IRH dmi.ec.firmware.release: 1.44 dmi.modalias: dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81SX:pvrLegionY540-15IRH:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegionY540-15IRH:skuLENOVO_MT_81SX_BU_idea_FM_LegionY540-15IRH: dmi.product.family: Legion Y540-15IRH dmi.product.name: 81SX dmi.product.sku: LENOVO_MT_81SX_BU_idea_FM_Legion Y540-15IRH dmi.product.version: Legion Y540-15IRH dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978380/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968681] Re: rdpru in ubuntu_kvm_unit_tests failed on B-4.15 node riccioli with FAIL: RDPRU raises #UD
** Description changed: [Impact] rdpru test in ubuntu_kvm_unit_tests is to check if the RDPRU instruction can be intercepted by the Hypervisor. RDPRU is one of the new instruction set extensions of AMD "Zen 2" CPUs that is for reading a processor register that is typically limited to privilege level zero. RDPRU allows for reading select registers at any privilege level. With Linux 5.5, the RDPRU presence will be advertised by the CPU features. Without this patchset, the rdpru test will fail on our AMD Zen 2 system "riccioli" [Fix] - * 9d40b85b x86/cpufeatures: Add feature bit RDPRU on AMD * 0cb8410b kvm: svm: Intercept RDPRU - We have these patches in newer releases already, only Bionic 4.15 - require this fix. And they can be cherry-picked without any conflict. + We have this patch in newer releases already, only Bionic 4.15 require + this fix. And it can be cherry-picked without any conflict. [Test] With the patched kernel, this rdpru test will pass on the target AMD Zen 2 system. And the rdpru flag will be available in cpuinfo: flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 invpcid_single hw_pstate ssbd ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr rdpru arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold v_vmsave_vmload vgif umip pku ospke vaes vpclmulqdq rdpid overflow_recov succor smca bugs : sysret_ss_attrs spectre_v1 spectre_v2 spec_store_bypass $ sudo ./rdpru BUILD_HEAD=16647354 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.syc17ecDpN -smp 1 -cpu max # -initrd /tmp/tmp.poLG53JqrJ enabling apic PASS: RDPRU raises #UD SUMMARY: 1 tests PASS rdpru (1 tests) [Where problems could occur] - This patchset will add a new feature bit RDPRU, the impact should be small as it's still up to user-space for making use of it. + This patchset will add a new feature bit RDPRU, the impact should be small as it's still up to user-space for making use of it. [Original Bug Report] Issue found on B-ibm-gt-4.15.0-1116.127 This can be reproduced with B-4.15.0-175 as well. This failure is only visible on this node. Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/rdpru' BUILD_HEAD=16647354 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.qGIR5tvTw1 -smp 1 -cpu max # -initrd /tmp/tmp.8JuYRCFRUi enabling apic FAIL: RDPRU raises #UD SUMMARY: 1 tests, 1 unexpected failures FAIL rdpru (1 tests, 1 unexpected failures) -- 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/1968681 Title: rdpru in ubuntu_kvm_unit_tests failed on B-4.15 node riccioli with FAIL: RDPRU raises #UD Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Confirmed Bug description: [Impact] rdpru test in ubuntu_kvm_unit_tests is to check if the RDPRU instruction can be intercepted by the Hypervisor. RDPRU is one of the new instruction set extensions of AMD "Zen 2" CPUs that is for reading a processor register that is typically limited to privilege level zero. RDPRU allows for reading select registers at any privilege level. With Linux 5.5, the RDPRU presence will be advertised by the CPU features. Without this patchset, the rdpru test will fail on our AMD Zen 2 system "riccioli" [Fix] * 0cb8410b kvm: svm: Intercept RDPRU We have this patch in newer releases already, only Bionic 4.15 require this fix. And it can be cherry-picked without any conflict. [Test] With the patched kernel, this rdpru test will pass on the target AMD Zen 2 system. And the rdpru flag will be available in cpuinfo: flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rd
[Kernel-packages] [Bug 1978565] [NEW] package nvidia-dkms-465 465.19.01-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-465 package post-installation script subprocess returned error exit st
Public bug reported: cant install cuda toolkit 11.3 to ubuntu 20.04 LTS 64 bit with NVIDIA GTX2080ti card. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-465 465.19.01-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-48-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 AptOrdering: nvidia-modprobe:amd64: Install libxnvctrl0:amd64: Install nvidia-settings:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 14 15:21:18 2022 ErrorMessage: installed nvidia-dkms-465 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2022-06-09 (4 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.8 SourcePackage: nvidia-graphics-drivers-465 Title: package nvidia-dkms-465 465.19.01-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-465 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-465 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-465 in Ubuntu. https://bugs.launchpad.net/bugs/1978565 Title: package nvidia-dkms-465 465.19.01-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-465 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-465 package in Ubuntu: New Bug description: cant install cuda toolkit 11.3 to ubuntu 20.04 LTS 64 bit with NVIDIA GTX2080ti card. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-465 465.19.01-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-48-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 AptOrdering: nvidia-modprobe:amd64: Install libxnvctrl0:amd64: Install nvidia-settings:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 14 15:21:18 2022 ErrorMessage: installed nvidia-dkms-465 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2022-06-09 (4 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.8 SourcePackage: nvidia-graphics-drivers-465 Title: package nvidia-dkms-465 465.19.01-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-465 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-465/+bug/1978565/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948626] Re: [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010
Michael, Step 4 holds good for this because this particular feature talks about CDC client(includes nvme-stas and libnvme). Step 1,2,3 should be a good sanity tests, just that it is unrelated to the patches this bug requests. -- 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/1948626 Title: [SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010 Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: [Impact] NVMe-oF suffers from a well-known discovery problem that fundamentally limits the size of realistic deployments. To address this discovery problem, the FMDS working group (within nvme.org) is working on two proposals that will allow NVMe-oF to be managed via a “network centric” provisioning process instead of an “end-node centric” one. TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP Network and will prevent an end-user from needing to manually configure the IP Address of Discovery Controllers. TP-8010 (this launchpad): will define the concept of a Centralized Discovery Controller (CDC) and will allow end-users to manage connectivity from a single point of management on an IP Fabric by IP Fabric basis. Here is code that implements TP8009 and TP8010: https://github.com/martin-belanger/nvme-stas/ which now got pulled into upstream - https://github.com/linux-nvme/nvme-stas [Fix] 1. Update kernel with TP8010 kernel patches: a. https://git.infradead.org/git/nvme.git/commit/647b2e01fb2d3394090ed11d1b5238157c52f907 b. https://git.infradead.org/git/nvme.git/commit/de87c02ea9b4d93d1114b912b621ead81f6738e0 c. nvme: add CNTRLTYPE definitions for 'identify controller https://lore.kernel.org/all/66fc4f03-ed5c-4727-ba94-c23daf7d6...@oracle.com/ [Test Case] 1. Test NVMe/TCP initiator support with the kernel 2. Create nvme 3. Connect and mount the luns 4. Complile and test libnvme and nvme-stas packages from github [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/nvme_tcp_patches_2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978475] Re: Docker container ports cannot be allocated
I'm currently on a conference so I won't be able to look into this further until Thursday. I should be able to provide more information by the end of the week. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1978475 Title: Docker container ports cannot be allocated Status in linux-aws-5.13 package in Ubuntu: Confirmed Bug description: This is a follow-up bug to https://bugs.launchpad.net/ubuntu/+source/linux-aws-5.13/+bug/1977919 I can confirm that the problem is indeed not fully fixed. @electricdaemon said: > Test kernel posted fixes crash but has another bug with unkillable stuck defunct docker-proxy service causing more issues. Bug is not solved. Tested on Linux AWS Lightsail instance. What I'm seeing is that docker-compose stacks either don't start at all or only start partially. In both cases the affected containers cannot start due to their host port being already allocated. I can say with absolute certainty that the ports on the host are dedicated to container applications and no other service is actually bound to the affected port numbers. # uname -a Linux ip-10-0-69-193 5.13.0-1029-aws #32~20.04.1-Ubuntu SMP Thu Jun 9 13:03:13 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux # apt-cache policy docker containerd docker: Installed: (none) Candidate: 1.5-2 Version table: 1.5-2 500 500 http://eu-central-1.ec2.archive.ubuntu.com/ubuntu focal/universe amd64 Packages containerd: Installed: (none) Candidate: 1.5.9-0ubuntu1~20.04.4 Version table: 1.5.9-0ubuntu1~20.04.4 500 500 http://eu-central-1.ec2.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 1.3.3-0ubuntu2 500 500 http://eu-central-1.ec2.archive.ubuntu.com/ubuntu focal/main amd64 Packages # docker-compose --version docker-compose version 1.29.2, build 5becea4c root@ip-10-0-69-193:/opt/myapp8/myappserv/int# docker-compose up -d Creating network "myappserv-int_default" with the default driver Creating myapp-migrator-int ... done Creating myapp-dealer-int ... Creating myapp-offer-int... Creating myapp-customer-int ... Creating myapp-customer-int ... error Creating myapp-dealer-int ... done Creating myapp-offer-int... done : port is already allocated ERROR: for customer Cannot start service customer: driver failed programming external connectivity on endpoint myapp8-customer-int (fe4112364528b0e7d192c793929c579e8a81af715118c8f83ad7e65e7397f3be): Bind for 0.0.0.0:9001 failed: port is already allocated ERROR: Encountered errors while bringing up the project. root@ip-10-0-69-193:/opt/myapp8/myappserv/int# docker-compose down Stopping myapp8-offer-int ... done Stopping myapp8-dealer-int ... done Removing myapp8-customer-int ... done Removing myapp8-offer-int... done Removing myapp8-dealer-int ... done Removing myapp8-migrator-int ... done Removing network myappserv-int_default root@ip-10-0-69-193:/opt/myapp8/myappserv/int# docker-compose up -d Creating network "myappserv-int_default" with the default driver Creating myapp8-migrator-int ... done Creating myapp8-offer-int... Creating myapp8-customer-int ... Creating myapp8-customer-int ... error WARNING: Host is already in use by another container Creating myapp8-offer-int... done ERROR: for myapp8-customer-int Cannot start service customer: driver failed programming external connectivity on endpoint myapp8-customer-int (72fc08854cd278e63cd3234e7fb03c08cb045efdcfb9e42075a1250d893645d5): Bind for 0.0.0.0:9001 failed Creating myapp8-dealer-int ... done ERROR: for customer Cannot start service customer: driver failed programming external connectivity on endpoint myapp8-customer-int (72fc08854cd278e63cd3234e7fb03c08cb045efdcfb9e42075a1250d893645d5): Bind for 0.0.0.0:9001 failed: port is already allocated ERROR: Encountered errors while bringing up the project. # docker-compose config services: customer: container_name: myapp8-customer-int depends_on: migrator: condition: service_completed_successfully image: reg.mydomain.tld/myapp8/customer:430d4ca ports: - published: 9001 target: 9001 restart: always dealer: container_name: myapp8-dealer-int depends_on: migrator: condition: service_completed_successfully image: reg.mydomain.tld/myapp8/dealer:430d4ca ports: - published: 9002 target: 9002 restart: always migrator: container_name: myapp8-migrator-int image: reg.mydomain.tld/myapp8/migrator:430d4ca offer: container_name: myapp8-offer-int depends_on: migrator: condition: service_completed_successf
[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added)
The bug exists on 5.15.35, 5.16.20, 5.17.5, 5.15.36. -- 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/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel paramater intel_idle.max_cstate=4 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1975509] Re: Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal, Impish, Jammy, and Kinetic
** Changed in: fabric-manager-510 (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: fabric-manager-510 (Ubuntu Focal) Status: New => Fix Committed ** Changed in: fabric-manager-510 (Ubuntu Impish) Status: New => Fix Committed ** Changed in: fabric-manager-510 (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: fabric-manager-510 (Ubuntu Kinetic) Status: New => Fix Committed ** Changed in: libnvidia-nscq-510 (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: libnvidia-nscq-510 (Ubuntu Focal) Status: New => Fix Committed ** Changed in: libnvidia-nscq-510 (Ubuntu Impish) Status: New => Fix Committed ** Changed in: libnvidia-nscq-510 (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: libnvidia-nscq-510 (Ubuntu Kinetic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1975509 Title: Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal, Impish, Jammy, and Kinetic Status in fabric-manager-510 package in Ubuntu: Fix Committed Status in libnvidia-nscq-510 package in Ubuntu: Fix Committed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510-server package in Ubuntu: Fix Committed Status in fabric-manager-510 source package in Bionic: Fix Committed Status in libnvidia-nscq-510 source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Bionic: Confirmed Status in nvidia-graphics-drivers-510-server source package in Bionic: Fix Released Status in fabric-manager-510 source package in Focal: Fix Committed Status in libnvidia-nscq-510 source package in Focal: Fix Committed Status in linux-restricted-modules source package in Focal: Confirmed Status in nvidia-graphics-drivers-510-server source package in Focal: Fix Released Status in fabric-manager-510 source package in Impish: Fix Committed Status in libnvidia-nscq-510 source package in Impish: Fix Committed Status in linux-restricted-modules source package in Impish: Confirmed Status in nvidia-graphics-drivers-510-server source package in Impish: Fix Released Status in fabric-manager-510 source package in Jammy: Fix Committed Status in libnvidia-nscq-510 source package in Jammy: Fix Committed Status in linux-restricted-modules source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510-server source package in Jammy: Fix Released Status in fabric-manager-510 source package in Kinetic: Fix Committed Status in libnvidia-nscq-510 source package in Kinetic: Fix Committed Status in linux-restricted-modules source package in Kinetic: Confirmed Status in nvidia-graphics-drivers-510-server source package in Kinetic: 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] === 510 kinetic/jammy/impish/focal/bionic === * New upstream release (LP: #1975509): - When calculating the address of grid barrier allocated for a CUDA stream, there was an off-by-one error. The address calculation is corrected in thisrelease. - An issue that caused an AC cycle test to fail with "AssertionError: NVLink links with inappropriate status found" is resolved. - An issue that caused NX 11 to become nonresponsive during a graphics operation is resolved. - Linking issues were observed when using libnvfm.so. Now and other depend tools use dynamic linking with libstdc++ and libgcc. - An intermittent error CUDA_ERROR_NVLINK_UNCORRECTABLE caused by some non-fatal nvlink interrupts is resolved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-510/+bug/1975509/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973434] Re: massive performance issues since 22.04 upgrade
@uengberg: in my research for another bug/problem (https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/1977660 - I did not yet document it there) i found out that power profile behaviour is strange and actually i realized that the settings available in gnome *do* have a short term effect on Kernel parameters, but keep jumping back to the other setting. Then I connected this finding mentally with the finding i made here, namely that performance is better in lxde then in gnome, and I tried to see whats happening if I completely remove the power-profile-daemon, because I though it is probably bad when a Kernel or the Thinkpad firmware cannot properly set power profiles and keepy jumping back and forth... Wile this is only how I imagine these things working with my less than incomplete knowledge, I can says than Video playback in gnome works quite nicely after having removed the dysfunctional power-profile-daemon package. You might try to see if that helps you too. BTW in my case video(and accompanying audio) is/was problematic in all browsers i tested - in firefox, chrome and chromium, as well as in Zoom App(which I guess is likely an electron app). I had no chance to test is zoom works now too. I still dont know if this all just is a symptomatic remedy or really the root cause, though. Just as much I dont know if this really is a Kernel, a thinkpad Firmware/ACPI, or another low level library problem. @mruffel: are there any cpu/performance tests suites we could run to make all this more measurable instead of having to say "oh run a bunch of Youtube videos and/or zoom calls and see if it starts stuttering after a while"? The thing not working properly could be video playback, but it could also just be some scheduling issue and a system that cant cope well with single processes creating short term CPU spikes, as gnome-shell does and as in Video Playback the RDD Process appears to cause. -- 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/1973434 Title: massive performance issues since 22.04 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Hi, After upgrading to 22.04 i had to fight with massive performance issues. Browsers appeared to hang every other minute, youtube videos being laggy and hang in between, applications in a virtualbox VM where slow and also hanging every other minute to a level of not being useable. On a pretty recent and powerful system just 2 years old. I noticed CPU jumps in top, but also somehow thought it could be a graphics issue so invested some time installing nvidia drivers properly. Also I wondered if it might be the lowlatency kernel I normally use because I do audio stuff, and switched to generic. But nothing helped. ThenI had the idea it could be a kernel/scheduler issue because the system wasn't always slow, but it appeared certain things kept hanging when other processed had a lot of cpu for a few seconds. So I got a recent mainline kernel, configured it with my last running config from 21.10 before the update, made the debs and installed them, and now can tell that a mainline kernel 5.17.7 with all the dkms modules that i had before which got compiled automatically at installation brings back a "normal" performance. I can browse the web, run multiple youtube vids at once, even in another browser, have thunderbird running, and a virtualbox machine open with another browser for some web app testing and everything runs fine and smooth, no lagging. Not sure yet what the real reason is - either the kernel version, or a patch in the ubuntu version, or the 22.04 kernel config so far, or some configuration made in 21.10 that isn't good with 22.04 and it's kernel anymore. I will go ahead tomorrow and see if I can build a vanilla kernel with the config from the ubuntu 22.04 kernel and "make oldconfig", then I will be able to tell if only the config is making the difference. Please let me know of there is anything I should test to further analyze this issue, or any ideas I can try to solve it without having to run a mainline manually installed kernel. Thanks. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.30.33 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: henning6198 F pulseaudio /dev/snd/controlC1: henning6198 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 14 23:02:38 2022 InstallationDate: Installed on 2020-04-12 (761 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType:
[Kernel-packages] [Bug 1978347] Re: horrible IO degradation with encrypted zfs root on kernels past 5.15.0-27
I can confirm 100% repro of this bug, on several systems. Data for a Xeon Silver 4215R on Supermicro X11SPi-TF. The only change between 5.15.0-37-generic and 5.15.0-27-generic is booting the same machine with a different kernel. Write to encrypted ramdisk: - 5.15.0-37-generic: 186 MB/s - 5.15.0-27-generic: 1.2 GB/s (6.5x faster) Read from encrypted RAIDz1 on 8 x ST16000NM000J, arc cache cold: - 5.15.0-37-generic: 61.1 MB/s - 5.15.0-27-generic: 490 MB/s (8x faster) It only appears to affect ZFS when encryption is enabled: Write to unencrypted ramdisk: - 5.15.0-37-generic: 1.6 GB/s - 5.15.0-27-generic: 1.6 GB/s (identical) I am getting very similar data on Xeon E3-1240 v6 / Supermicro X11SSM-F and EPYC 7282 / Supermicro H12SSL-i I am attaching a test script and output from "apport-cli --save 5.15.0-37-generic.apport -p linux --file-bug" Methodology below: # uname -a Linux aero 5.15.0-37-generic #39-Ubuntu SMP Wed Jun 1 19:16:45 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux # Create encrypted ZFS to ramdisk using the the attached "zfs-test.sh enc" Write speed to encrypted ramdisk: # dd if=/dev/zero of=/tmp/mount/zero bs=1M dd: error writing '/tmp/mount/zero': No space left on device 7432+0 records in 7431+0 records out 7792885760 bytes (7.8 GB, 7.3 GiB) copied, 41.9707 s, 186 MB/s # Create unencrypted ZFS to ramdisk using the the attached "zfs-test.sh" Write speed to unencrypted ramdisk: # dd if=/dev/zero of=/tmp/mount/zero bs=1M dd: error writing '/tmp/mount/zero': No space left on device 7439+0 records in 7438+0 records out 7799308288 bytes (7.8 GB, 7.3 GiB) copied, 4.93472 s, 1.6 GB/s Read speed from encrypted RAIDz1 on 8 x ST16000NM000J, arc cache cold: # dd if=/storage/kits/ubuntu-20.04.1-desktop-amd64.iso of=/dev/null bs=1M 2656+0 records in 2656+0 records out 2785017856 bytes (2.8 GB, 2.6 GiB) copied, 45.6045 s, 61.1 MB/s # uname -a Linux aero 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux # Create encrypted ZFS to ramdisk using the the attached "zfs-test.sh enc" Write speed to encrypted ramdisk: # dd if=/dev/zero of=/tmp/mount/zero bs=1M dd: error writing '/tmp/mount/zero': No space left on device 7433+0 records in 7432+0 records out 7793016832 bytes (7.8 GB, 7.3 GiB) copied, 6.28478 s, 1.2 GB/s # Create unencrypted ZFS to ramdisk using the the attached "zfs-test.sh" Write speed to unencrypted ramdisk: # dd if=/dev/zero of=/tmp/mount/zero bs=1M dd: error writing '/tmp/mount/zero': No space left on device 7439+0 records in 7438+0 records out 7799308288 bytes (7.8 GB, 7.3 GiB) copied, 4.76863 s, 1.6 GB/s Read speed from encrypted RAIDz1 on 8 x ST16000NM000J, arc cache cold: # dd if=/storage/kits/ubuntu-20.04.1-desktop-amd64.iso of=/dev/null bs=1M 2656+0 records in 2656+0 records out 2785017856 bytes (2.8 GB, 2.6 GiB) copied, 5.68203 s, 490 MB/s -- 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/1978347 Title: horrible IO degradation with encrypted zfs root on kernels past 5.15.0-27 Status in linux package in Ubuntu: Confirmed Bug description: IO on encrypted zfs root has fallen off a cliff in kernel versions after 5.15.0-27 (the degradation is observed since version 5.15.0-30, also seen on -33 and -37, -25 and -27 work like a charm). Heavy usage almost hangs a new laptop (building large singularity images or synthetic testing with dd). I have confirmed that things are working as expected on a default + upgraded Ubuntu 22.04 desktop LVM+LUKS installation using another NVMe SSD on the same laptop. There seems to be a regression when using the native zfs encryption (did aes-ni acceleration get turned off?) How to reproduce: - install ubuntu 22.04 desktop from iso, don't install web updates, check use zfs and encryption - sudo apt update && apt install dstat htop - create a dataset with compression disabled so that dd actually writes things to disk * sudo zfs create rpool/dummy * sudo zfs set compress=off rpool/dummy * sudo chown -R myusername. /dummy - start dstat and htop in the background (show kernel threads in the htop config) - dd if=/dev/zero of=/dummy/bigfile bs=1M count=16384 - sudo apt upgradeand reboot on the latest kernel, repeat Expected: some cpu load, dstat reports write speeds about as much as the SSD can sustain (2.9-3GiB/s with a 2TiB Samsung 970 EVO Plus for a 16GiB write test, 1.4GiB/s for a few seconds then 800MiB/s sustained for whatever WD 512GiB model I had laying around). Observed on versions -30 and later: 700% or more system cpu load, mostly in z_wr_iss threads, writes top at around 150-180MiB/s, the system becomes somewhat unresponsive. Reads are also not good but I have not benchmarked. Booting the system and launching apps seems about normal due to the low IO load. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package
[Kernel-packages] [Bug 1978347] Re: horrible IO degradation with encrypted zfs root on kernels past 5.15.0-27
Output from "apport-cli --save 5.15.0-37-generic.apport -p linux --file- bug" ** Attachment added: "5.15.0-37-generic.apport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978347/+attachment/5597248/+files/5.15.0-37-generic.apport -- 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/1978347 Title: horrible IO degradation with encrypted zfs root on kernels past 5.15.0-27 Status in linux package in Ubuntu: Confirmed Bug description: IO on encrypted zfs root has fallen off a cliff in kernel versions after 5.15.0-27 (the degradation is observed since version 5.15.0-30, also seen on -33 and -37, -25 and -27 work like a charm). Heavy usage almost hangs a new laptop (building large singularity images or synthetic testing with dd). I have confirmed that things are working as expected on a default + upgraded Ubuntu 22.04 desktop LVM+LUKS installation using another NVMe SSD on the same laptop. There seems to be a regression when using the native zfs encryption (did aes-ni acceleration get turned off?) How to reproduce: - install ubuntu 22.04 desktop from iso, don't install web updates, check use zfs and encryption - sudo apt update && apt install dstat htop - create a dataset with compression disabled so that dd actually writes things to disk * sudo zfs create rpool/dummy * sudo zfs set compress=off rpool/dummy * sudo chown -R myusername. /dummy - start dstat and htop in the background (show kernel threads in the htop config) - dd if=/dev/zero of=/dummy/bigfile bs=1M count=16384 - sudo apt upgradeand reboot on the latest kernel, repeat Expected: some cpu load, dstat reports write speeds about as much as the SSD can sustain (2.9-3GiB/s with a 2TiB Samsung 970 EVO Plus for a 16GiB write test, 1.4GiB/s for a few seconds then 800MiB/s sustained for whatever WD 512GiB model I had laying around). Observed on versions -30 and later: 700% or more system cpu load, mostly in z_wr_iss threads, writes top at around 150-180MiB/s, the system becomes somewhat unresponsive. Reads are also not good but I have not benchmarked. Booting the system and launching apps seems about normal due to the low IO load. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-37-generic 5.15.0-37.39 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laperlej 4100 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 10 15:52:12 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2022-05-10 (31 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: HP HP EliteBook 850 G8 Notebook PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rgwvzq@/vmlinuz-5.15.0-37-generic root=ZFS=rpool/ROOT/ubuntu_rgwvzq ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.15.0-37-generic N/A linux-backports-modules-5.15.0-37-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/11/2022 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: T76 Ver. 01.08.00 dmi.board.name: 8846 dmi.board.vendor: HP dmi.board.version: KBC Version 30.37.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 48.55 dmi.modalias: dmi:bvnHP:bvrT76Ver.01.08.00:bd01/11/2022:br8.0:efr48.55:svnHP:pnHPEliteBook850G8NotebookPC:pvr:rvnHP:rn8846:rvrKBCVersion30.37.00:cvnHP:ct10:cvr:sku4V1S3UP#ABL: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G8 Notebook PC dmi.product.sku: 4V1S3UP#ABL dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978347] Re: horrible IO degradation with encrypted zfs root on kernels past 5.15.0-27
Test script "zfs-test.sh" - "zfs-test.sh enc" creates a 2x8 GB ZFS mirror pool, backed by two files in tmpfs, followed by a ZFS encrypted filesystem using the default aes-256-gcm - "zfs-test.sh" creates a 2x8 GB ZFS mirror pool, backed by two files in tmpfs, followed by a ZFS unencrypted filesystem ** Attachment added: "zfs-test.sh" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978347/+attachment/5597249/+files/zfs-test.sh -- 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/1978347 Title: horrible IO degradation with encrypted zfs root on kernels past 5.15.0-27 Status in linux package in Ubuntu: Confirmed Bug description: IO on encrypted zfs root has fallen off a cliff in kernel versions after 5.15.0-27 (the degradation is observed since version 5.15.0-30, also seen on -33 and -37, -25 and -27 work like a charm). Heavy usage almost hangs a new laptop (building large singularity images or synthetic testing with dd). I have confirmed that things are working as expected on a default + upgraded Ubuntu 22.04 desktop LVM+LUKS installation using another NVMe SSD on the same laptop. There seems to be a regression when using the native zfs encryption (did aes-ni acceleration get turned off?) How to reproduce: - install ubuntu 22.04 desktop from iso, don't install web updates, check use zfs and encryption - sudo apt update && apt install dstat htop - create a dataset with compression disabled so that dd actually writes things to disk * sudo zfs create rpool/dummy * sudo zfs set compress=off rpool/dummy * sudo chown -R myusername. /dummy - start dstat and htop in the background (show kernel threads in the htop config) - dd if=/dev/zero of=/dummy/bigfile bs=1M count=16384 - sudo apt upgradeand reboot on the latest kernel, repeat Expected: some cpu load, dstat reports write speeds about as much as the SSD can sustain (2.9-3GiB/s with a 2TiB Samsung 970 EVO Plus for a 16GiB write test, 1.4GiB/s for a few seconds then 800MiB/s sustained for whatever WD 512GiB model I had laying around). Observed on versions -30 and later: 700% or more system cpu load, mostly in z_wr_iss threads, writes top at around 150-180MiB/s, the system becomes somewhat unresponsive. Reads are also not good but I have not benchmarked. Booting the system and launching apps seems about normal due to the low IO load. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-37-generic 5.15.0-37.39 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laperlej 4100 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 10 15:52:12 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2022-05-10 (31 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: HP HP EliteBook 850 G8 Notebook PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rgwvzq@/vmlinuz-5.15.0-37-generic root=ZFS=rpool/ROOT/ubuntu_rgwvzq ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.15.0-37-generic N/A linux-backports-modules-5.15.0-37-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/11/2022 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: T76 Ver. 01.08.00 dmi.board.name: 8846 dmi.board.vendor: HP dmi.board.version: KBC Version 30.37.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 48.55 dmi.modalias: dmi:bvnHP:bvrT76Ver.01.08.00:bd01/11/2022:br8.0:efr48.55:svnHP:pnHPEliteBook850G8NotebookPC:pvr:rvnHP:rn8846:rvrKBCVersion30.37.00:cvnHP:ct10:cvr:sku4V1S3UP#ABL: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G8 Notebook PC dmi.product.sku: 4V1S3UP#ABL dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978347] Re: horrible IO degradation with encrypted zfs root on kernels past 5.15.0-27
For more context, openssl using aes-256-cbc (not aes-256-gcm, which is unsupported by default) appears to behave identically between the two kernels, and faster than when disabling aes-ni, therefore aes-ni appears to be enabled in both. # uname -a Linux aero 5.15.0-37-generic #39-Ubuntu SMP Wed Jun 1 19:16:45 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux # openssl speed aes-256-cbc Doing aes-256-cbc for 3s on 16 size blocks: 186683511 aes-256-cbc's in 3.00s Doing aes-256-cbc for 3s on 64 size blocks: 50188595 aes-256-cbc's in 3.00s Doing aes-256-cbc for 3s on 256 size blocks: 12770138 aes-256-cbc's in 3.00s Doing aes-256-cbc for 3s on 1024 size blocks: 3204571 aes-256-cbc's in 3.00s Doing aes-256-cbc for 3s on 8192 size blocks: 400190 aes-256-cbc's in 3.00s Doing aes-256-cbc for 3s on 16384 size blocks: 199936 aes-256-cbc's in 3.00s version: 3.0.2 built on: Thu May 5 08:04:52 2022 UTC options: bn(64,64) compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -Wa,--noexecstack -g -O2 -ffile-prefix-map=/build/openssl-Ke3YUO/openssl-3.0.2=. -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -DOPENSSL_TLS_SECURITY_LEVEL=2 -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_BUILDING_OPENSSL -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 CPUINFO: OPENSSL_ia32cap=0x7ffef3eb:0x818d39ef7eb The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes256 bytes 1024 bytes 8192 bytes 16384 bytes aes-256-cbc 995645.39k 1070690.03k 1089718.44k 1093826.90k 1092785.49k 1091917.14k # uname -a Linux aero 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux # openssl speed aes-256-cbc Doing aes-256-cbc for 3s on 16 size blocks: 186867669 aes-256-cbc's in 3.00s Doing aes-256-cbc for 3s on 64 size blocks: 50246758 aes-256-cbc's in 3.00s Doing aes-256-cbc for 3s on 256 size blocks: 12765344 aes-256-cbc's in 3.00s Doing aes-256-cbc for 3s on 1024 size blocks: 3204376 aes-256-cbc's in 3.00s Doing aes-256-cbc for 3s on 8192 size blocks: 399400 aes-256-cbc's in 3.00s Doing aes-256-cbc for 3s on 16384 size blocks: 200109 aes-256-cbc's in 3.00s version: 3.0.2 built on: Thu May 5 08:04:52 2022 UTC options: bn(64,64) compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -Wa,--noexecstack -g -O2 -ffile-prefix-map=/build/openssl-Ke3YUO/openssl-3.0.2=. -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -DOPENSSL_TLS_SECURITY_LEVEL=2 -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_BUILDING_OPENSSL -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 CPUINFO: OPENSSL_ia32cap=0x7ffef3eb:0x818d39ef7eb The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes256 bytes 1024 bytes 8192 bytes 16384 bytes aes-256-cbc 996627.57k 1071930.84k 1089309.35k 1093760.34k 1090628.27k 1092861.95k # OPENSSL_ia32cap= openssl speed aes-256-cbc Doing aes-256-cbc for 3s on 16 size blocks: 20600986 aes-256-cbc's in 3.00s Doing aes-256-cbc for 3s on 64 size blocks: 5866219 aes-256-cbc's in 3.00s Doing aes-256-cbc for 3s on 256 size blocks: 1517023 aes-256-cbc's in 3.00s Doing aes-256-cbc for 3s on 1024 size blocks: 885706 aes-256-cbc's in 3.00s Doing aes-256-cbc for 3s on 8192 size blocks: 112410 aes-256-cbc's in 3.00s Doing aes-256-cbc for 3s on 16384 size blocks: 56135 aes-256-cbc's in 3.00s version: 3.0.2 built on: Thu May 5 08:04:52 2022 UTC options: bn(64,64) compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -Wa,--noexecstack -g -O2 -ffile-prefix-map=/build/openssl-Ke3YUO/openssl-3.0.2=. -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -DOPENSSL_TLS_SECURITY_LEVEL=2 -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_BUILDING_OPENSSL -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 CPUINFO: OPENSSL_ia32cap=0x400:0x0 env: The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes256 bytes 1024 bytes 8192 bytes 16384 bytes aes-256-cbc 109871.93k 125146.01k 129452.63k 302320.98k 306954.24k 306571.95k -- 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/1978347 Title: horrible IO degradation with encrypted zfs root on kernels past 5.15.0-27 Status in linux package in Ubuntu: Confirmed Bug description: IO on encrypted zfs root has fallen off a cliff in kernel versions after 5.15.0-27 (the degradation is observed since version 5.15.0-30, also seen on -33 and -37, -25 and -27 work like a charm). Heavy usage almost hangs a new laptop (building large singularity images or synthetic testing with dd). I have confirmed that things are working as expected on a default + upgraded Ubuntu 22.04 desk
[Kernel-packages] [Bug 1978333] Re: Remove "ata_piix.prefer_ms_hyperv=0" parameter
** Changed in: makedumpfile (Ubuntu Kinetic) Assignee: (unassigned) => Heather Lemon (hypothetical-lemon) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1978333 Title: Remove "ata_piix.prefer_ms_hyperv=0" parameter Status in kdump-tools package in Ubuntu: Fix Committed Status in makedumpfile package in Ubuntu: New Status in kdump-tools source package in Bionic: Invalid Status in makedumpfile source package in Bionic: New Status in kdump-tools source package in Focal: Invalid Status in makedumpfile source package in Focal: New Status in kdump-tools source package in Impish: New Status in makedumpfile source package in Impish: New Status in kdump-tools source package in Jammy: New Status in makedumpfile source package in Jammy: New Status in kdump-tools source package in Kinetic: Fix Committed Status in makedumpfile source package in Kinetic: New Bug description: Back-porting a fix from upstream to remove "ata_piix.prefer_ms_hyperv=0" parameter. target series - Kinetic-> Bionic upstream patch https://salsa.debian.org/debian/kdump- tools/-/commit/b1bac9396ddbbce3817c34be3161630698e4a503 *Note: There are two source packages needed changes, kdump-tools for Impish -> Kinetic and makedumpfile for series Focal -> Bionic Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/1978333/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1975509] Re: Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal, Impish, Jammy, and Kinetic
Testing of nvidia-fabricmanager-510 and libnvidia-nscq-510 has been successfully performed again against the packages in -proposed. These are good to release from a testing perspective. ** Tags removed: verification-needed verification-needed-bionic verification-needed-focal verification-needed-impish verification-needed-jammy ** Tags added: verification-done verification-done-bionic verification-done-focal verification-done-impish verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1975509 Title: Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal, Impish, Jammy, and Kinetic Status in fabric-manager-510 package in Ubuntu: Fix Committed Status in libnvidia-nscq-510 package in Ubuntu: Fix Committed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510-server package in Ubuntu: Fix Committed Status in fabric-manager-510 source package in Bionic: Fix Committed Status in libnvidia-nscq-510 source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Bionic: Confirmed Status in nvidia-graphics-drivers-510-server source package in Bionic: Fix Released Status in fabric-manager-510 source package in Focal: Fix Committed Status in libnvidia-nscq-510 source package in Focal: Fix Committed Status in linux-restricted-modules source package in Focal: Confirmed Status in nvidia-graphics-drivers-510-server source package in Focal: Fix Released Status in fabric-manager-510 source package in Impish: Fix Committed Status in libnvidia-nscq-510 source package in Impish: Fix Committed Status in linux-restricted-modules source package in Impish: Confirmed Status in nvidia-graphics-drivers-510-server source package in Impish: Fix Released Status in fabric-manager-510 source package in Jammy: Fix Committed Status in libnvidia-nscq-510 source package in Jammy: Fix Committed Status in linux-restricted-modules source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510-server source package in Jammy: Fix Released Status in fabric-manager-510 source package in Kinetic: Fix Committed Status in libnvidia-nscq-510 source package in Kinetic: Fix Committed Status in linux-restricted-modules source package in Kinetic: Confirmed Status in nvidia-graphics-drivers-510-server source package in Kinetic: 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] === 510 kinetic/jammy/impish/focal/bionic === * New upstream release (LP: #1975509): - When calculating the address of grid barrier allocated for a CUDA stream, there was an off-by-one error. The address calculation is corrected in thisrelease. - An issue that caused an AC cycle test to fail with "AssertionError: NVLink links with inappropriate status found" is resolved. - An issue that caused NX 11 to become nonresponsive during a graphics operation is resolved. - Linking issues were observed when using libnvfm.so. Now and other depend tools use dynamic linking with libstdc++ and libgcc. - An intermittent error CUDA_ERROR_NVLINK_UNCORRECTABLE caused by some non-fatal nvlink interrupts is resolved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-510/+bug/1975509/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978333] Re: Remove "ata_piix.prefer_ms_hyperv=0" parameter
For I/J/K in makedumpfile, it seems the default rules used does not have the parameter ata_piix.prefer_ms_hyperv=0 There is also a changelog entry about removing the parameter: * ppc64el: Remove ata_piix.prefer_ms_hyperv=0 from crashkernel cmdline (link to changelog) https://salsa.debian.org/search?group_id=2&project_id=57654&repository_ref=master&scope=blobs&search=883899 I will mark these as invalid ** Changed in: makedumpfile (Ubuntu Kinetic) Status: New => Invalid ** Changed in: makedumpfile (Ubuntu Jammy) Status: New => Invalid ** Changed in: makedumpfile (Ubuntu Impish) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. Matching subscriptions: Maintainer https://bugs.launchpad.net/bugs/1978333 Title: Remove "ata_piix.prefer_ms_hyperv=0" parameter Status in kdump-tools package in Ubuntu: Fix Committed Status in makedumpfile package in Ubuntu: Invalid Status in kdump-tools source package in Bionic: Invalid Status in makedumpfile source package in Bionic: New Status in kdump-tools source package in Focal: Invalid Status in makedumpfile source package in Focal: New Status in kdump-tools source package in Impish: New Status in makedumpfile source package in Impish: Invalid Status in kdump-tools source package in Jammy: New Status in makedumpfile source package in Jammy: Invalid Status in kdump-tools source package in Kinetic: Fix Committed Status in makedumpfile source package in Kinetic: Invalid Bug description: Back-porting a fix from upstream to remove "ata_piix.prefer_ms_hyperv=0" parameter. target series - Kinetic-> Bionic upstream patch https://salsa.debian.org/debian/kdump- tools/-/commit/b1bac9396ddbbce3817c34be3161630698e4a503 *Note: There are two source packages needed changes, kdump-tools for Impish -> Kinetic and makedumpfile for series Focal -> Bionic Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/1978333/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978333] Re: Remove "ata_piix.prefer_ms_hyperv=0" parameter
FYI to build the debian/rules I executed in makedumpfile (I/J/K) debuild -us -uc -b -rfakeroot ** Tags added: verification-needed-bionic verification-needed-focal verification-needed-impish verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1978333 Title: Remove "ata_piix.prefer_ms_hyperv=0" parameter Status in kdump-tools package in Ubuntu: Fix Committed Status in makedumpfile package in Ubuntu: Invalid Status in kdump-tools source package in Bionic: Invalid Status in makedumpfile source package in Bionic: New Status in kdump-tools source package in Focal: Invalid Status in makedumpfile source package in Focal: New Status in kdump-tools source package in Impish: New Status in makedumpfile source package in Impish: Invalid Status in kdump-tools source package in Jammy: New Status in makedumpfile source package in Jammy: Invalid Status in kdump-tools source package in Kinetic: Fix Committed Status in makedumpfile source package in Kinetic: Invalid Bug description: Back-porting a fix from upstream to remove "ata_piix.prefer_ms_hyperv=0" parameter. target series - Kinetic-> Bionic upstream patch https://salsa.debian.org/debian/kdump- tools/-/commit/b1bac9396ddbbce3817c34be3161630698e4a503 *Note: There are two source packages needed changes, kdump-tools for Impish -> Kinetic and makedumpfile for series Focal -> Bionic Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/1978333/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978719] [NEW] Ubuntu 5.4.0-117.132-generic 5.4.189 has BUG: kernel NULL pointer dereference, address: 0000000000000034
Public bug reported:
The 5.4.0 series of the Ubuntu kernel has missed a patch which resolves
a null dereference:
[104602.951260] BUG: kernel NULL pointer dereference, address: 0034
[104602.951263] #PF: supervisor write access in kernel mode
[104602.951264] #PF: error_code(0x0002) - not-present page
[104602.951266] PGD 0 P4D 0
[104602.951269] Oops: 0002 [#1] SMP PTI
[104602.951272] CPU: 6 PID: 176572 Comm: ThreadPoolForeg Kdump: loaded Tainted:
P OE 5.4.0-117-generic #132-Ubuntu
[104602.951273] Hardware name: System manufacturer System Product Name/P8P67
LE, BIOS 3801 09/12/2013
[104602.951278] RIP: 0010:unlink_anon_vmas+0x3e/0x1b0
[104602.951280] Code: 54 53 48 83 ec 08 48 8b 47 78 48 89 7d d0 48 8b 30 49 39
c5 0f 84 5e 01 00 00 4c 8d 78 f0 4c 8d 66 f0 31 db eb 21 49 8b 46 38 <83> 68 34
01 49 8b 44 24 10 49 8d 54 24 10 4d 89 e7 48 83 e8 10 49
[104602.951281] RSP: 0018:c00908703bd8 EFLAGS: 00010246
[104602.951283] RAX: RBX: RCX:
[104602.951284] RDX: RSI: 99e8e5815c48 RDI:
[104602.951286] RBP: c00908703c08 R08: 0001 R09:
ae665f00
[104602.951287] R10: 99eb808bd6c0 R11: 0001 R12:
99eb0fda27b8
[104602.951288] R13: 99eb0fda27c8 R14: 99e8e5815c08 R15:
99e7ee7af6c0
[104602.951290] FS: () GS:99eb8eb8()
knlGS:
[104602.951291] CS: 0010 DS: ES: CR0: 80050033
[104602.951293] CR2: 0034 CR3: 00037ae0a005 CR4:
000606e0
[104602.951294] Call Trace:
[104602.951299] free_pgtables+0x93/0xf0
[104602.951301] exit_mmap+0xc7/0x1b0
[104602.951304] mmput+0x5d/0x130
[104602.951306] do_exit+0x31a/0xaf0
[104602.951309] do_group_exit+0x47/0xb0
[104602.951312] get_signal+0x169/0x890
[104602.951315] do_signal+0x34/0x6c0
[104602.951318] ? _copy_from_user+0x3e/0x60
[104602.951321] ? __x64_sys_futex+0x13f/0x170
[104602.951324] exit_to_usermode_loop+0xbf/0x160
[104602.951327] do_syscall_64+0x163/0x190
[104602.951330] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[104602.951332] RIP: 0033:0x7f58d1db27d1
[104602.951335] Code: Bad RIP value.
[104602.951336] RSP: 002b:7f58c6987370 EFLAGS: 0246 ORIG_RAX:
00ca
[104602.951338] RAX: fdfc RBX: 7f58c69875e8 RCX:
7f58d1db27d1
[104602.951339] RDX: RSI: 0089 RDI:
7f58c6987600
[104602.951340] RBP: 7f58c69875d8 R08: R09:
[104602.951341] R10: 7f58c6987460 R11: 0246 R12:
7f58c69875fc
[104602.951343] R13: 7f58c69875b0 R14: 7f58c6987600 R15:
7f58c69873c0
The patch was posted back in 2021 the linux kernel mailing lists:
https://lore.kernel.org/linux-mm/20210224200449.hkU5GTEiH%25akpm@linux-
foundation.org/
The defect is:
Date: Wed, 24 Feb 2021 12:04:49 -0800 [thread overview]
Message-ID: <20210224200449.hku5gteih%a...@linux-foundation.org> (raw)
In-Reply-To: <20210224115824.1e289a6895087f10c41dd...@linux-foundation.org>
From: Li Xinhai
Subject: mm: rmap: explicitly reset vma->anon_vma in unlink_anon_vmas()
In case the vma will continue to be used after unlink its relevant
anon_vma, we need to reset the vma->anon_vma pointer to NULL. So, later
when fault happen within this vma again, a new anon_vma will be prepared.
By this way, the vma will only be checked for reverse mapping of pages
which been fault in after the unlink_anon_vmas call.
Currently, the mremap with MREMAP_DONTUNMAP scenario will continue use the
vma after moved its page table entries to a new vma. For other scenarios,
the vma itself will be freed after call unlink_anon_vmas.
Link: https://lkml.kernel.org/r/20210119075126.3513154-1-lixinhai@gmail.com
Signed-off-by: Li Xinhai
Cc: Andrea Arcangeli
Cc: Brian Geffon
Cc: Kirill A. Shutemov
Cc: Lokesh Gidra
Cc: Minchan Kim
Cc: Vlastimil Babka
Signed-off-by: Andrew Morton
---
mm/rmap.c |9 -
1 file changed, 8 insertions(+), 1 deletion(-)
--- a/mm/rmap.c~mm-rmap-explicitly-reset-vma-anon_vma-in-unlink_anon_vmas
+++ a/mm/rmap.c
@@ -413,8 +413,15 @@ void unlink_anon_vmas(struct vm_area_str
list_del(&avc->same_vma);
anon_vma_chain_free(avc);
}
- if (vma->anon_vma)
+ if (vma->anon_vma) {
vma->anon_vma->degree--;
+
+ /*
+* vma would still be needed after unlink, and anon_vma will be
prepared
+* when handle fault.
+*/
+ vma->anon_vma = NULL;
+ }
unlock_anon_vma_root(root);
/*
The Linux 5.4 package that Ubuntu is currently running on the latest kernel has
the following code:
if (vma->anon_vma)
vma->anon_vma->degree--;
unlock_anon_vma_root(root);
This is the 3rd time I've encountered the crash.
root@lazarus:/var/crash/202206141315# lsb_release
[Kernel-packages] [Bug 1978719] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1978719 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1978719 Title: Ubuntu 5.4.0-117.132-generic 5.4.189 has BUG: kernel NULL pointer dereference, address: 0034 Status in linux package in Ubuntu: Incomplete Bug description: The 5.4.0 series of the Ubuntu kernel has missed a patch which resolves a null dereference: [104602.951260] BUG: kernel NULL pointer dereference, address: 0034 [104602.951263] #PF: supervisor write access in kernel mode [104602.951264] #PF: error_code(0x0002) - not-present page [104602.951266] PGD 0 P4D 0 [104602.951269] Oops: 0002 [#1] SMP PTI [104602.951272] CPU: 6 PID: 176572 Comm: ThreadPoolForeg Kdump: loaded Tainted: P OE 5.4.0-117-generic #132-Ubuntu [104602.951273] Hardware name: System manufacturer System Product Name/P8P67 LE, BIOS 3801 09/12/2013 [104602.951278] RIP: 0010:unlink_anon_vmas+0x3e/0x1b0 [104602.951280] Code: 54 53 48 83 ec 08 48 8b 47 78 48 89 7d d0 48 8b 30 49 39 c5 0f 84 5e 01 00 00 4c 8d 78 f0 4c 8d 66 f0 31 db eb 21 49 8b 46 38 <83> 68 34 01 49 8b 44 24 10 49 8d 54 24 10 4d 89 e7 48 83 e8 10 49 [104602.951281] RSP: 0018:c00908703bd8 EFLAGS: 00010246 [104602.951283] RAX: RBX: RCX: [104602.951284] RDX: RSI: 99e8e5815c48 RDI: [104602.951286] RBP: c00908703c08 R08: 0001 R09: ae665f00 [104602.951287] R10: 99eb808bd6c0 R11: 0001 R12: 99eb0fda27b8 [104602.951288] R13: 99eb0fda27c8 R14: 99e8e5815c08 R15: 99e7ee7af6c0 [104602.951290] FS: () GS:99eb8eb8() knlGS: [104602.951291] CS: 0010 DS: ES: CR0: 80050033 [104602.951293] CR2: 0034 CR3: 00037ae0a005 CR4: 000606e0 [104602.951294] Call Trace: [104602.951299] free_pgtables+0x93/0xf0 [104602.951301] exit_mmap+0xc7/0x1b0 [104602.951304] mmput+0x5d/0x130 [104602.951306] do_exit+0x31a/0xaf0 [104602.951309] do_group_exit+0x47/0xb0 [104602.951312] get_signal+0x169/0x890 [104602.951315] do_signal+0x34/0x6c0 [104602.951318] ? _copy_from_user+0x3e/0x60 [104602.951321] ? __x64_sys_futex+0x13f/0x170 [104602.951324] exit_to_usermode_loop+0xbf/0x160 [104602.951327] do_syscall_64+0x163/0x190 [104602.951330] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [104602.951332] RIP: 0033:0x7f58d1db27d1 [104602.951335] Code: Bad RIP value. [104602.951336] RSP: 002b:7f58c6987370 EFLAGS: 0246 ORIG_RAX: 00ca [104602.951338] RAX: fdfc RBX: 7f58c69875e8 RCX: 7f58d1db27d1 [104602.951339] RDX: RSI: 0089 RDI: 7f58c6987600 [104602.951340] RBP: 7f58c69875d8 R08: R09: [104602.951341] R10: 7f58c6987460 R11: 0246 R12: 7f58c69875fc [104602.951343] R13: 7f58c69875b0 R14: 7f58c6987600 R15: 7f58c69873c0 The patch was posted back in 2021 the linux kernel mailing lists: https://lore.kernel.org/linux- mm/20210224200449.hku5gteih%25a...@linux-foundation.org/ The defect is: Date: Wed, 24 Feb 2021 12:04:49 -0800 [thread overview] Message-ID: <20210224200449.hku5gteih%a...@linux-foundation.org> (raw) In-Reply-To: <20210224115824.1e289a6895087f10c41dd...@linux-foundation.org> From: Li Xinhai Subject: mm: rmap: explicitly reset vma->anon_vma in unlink_anon_vmas() In case the vma will continue to be used after unlink its relevant anon_vma, we need to reset the vma->anon_vma pointer to NULL. So, later when fault happen within this vma again, a new anon_vma will be prepared. By this way, the vma will only be checked for reverse mapping of pages which been fault in after the unlink_anon_vmas call. Currently, the mremap with MREMAP_DONTUNMAP scenario will continue use the vma after moved its page table entries to a new vma. For other scenarios, the vma itself will be freed after call unlink_anon_vmas. Link: https://lkml.kernel.org/r/20210119075126.3513154-1-lixinhai@gmail.com Signed-off-by: Li Xinhai Cc: Andrea Arcangeli Cc: Brian Geffon Cc: Kirill A. Shutemov Cc: Lokesh Gidra Cc
[Kernel-packages] [Bug 1978145] Re: Request to back port vmci patches to Ubuntu kernel
Thanks a lot for the quick response, Tim!
We have completed our testing on x86 and it looks good from our
point of view. We are in the process of testing on arm64.
Will keep you posted on the progress.
Thanks,
Vishnu
--
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/1978145
Title:
Request to back port vmci patches to Ubuntu kernel
Status in linux package in Ubuntu:
Confirmed
Bug description:
The request is to bring vmci to TOT and back port the following patches into
Ubuntu kernels.
1. fac608138c6136126faadafa5554cc0bbabf3c44 ("VMCI: dma dg: whitespace
formatting change for vmci register defines")
2. e283a0e8b7ea83915e988ed059384af166b444c0 ("VMCI: dma dg: add MMIO access
to registers")
3. eed2298d936087a1c85e0fa6f7170028e4f4fded ("VMCI: dma dg: detect DMA
datagram capability")
4. 8cb520bea1470ca205980fbf030ed1f472f4af2f ("VMCI: dma dg: set OS page
size")
5. cc68f2177fcbfe2dbe5e9514789b96ba5995ec1e ("VMCI: dma dg: register dummy
IRQ handlers for DMA datagrams")
6. 5ee109828e73bbe4213c373988608d8f33e03d78 ("VMCI: dma dg: allocate send
and receive buffers for DMA datagrams")
7. 22aa5c7f323022477b70e044eb00e6bfea9498e8 ("VMCI: dma dg: add support for
DMA datagrams sends")
8. 463713eb6164b6577f8e91447c7745628215531b ("VMCI: dma dg: add support for
DMA datagrams receive")
9. 77e861619baea5a7c934e47fda74b03c0b072aec ("VMCI: Fix some error handling
paths in vmci_guest_probe_device()")
10. c8e9b30ccae605bf1dbeaf03971f9b83f70b928d ("VMCI: Release
notification_bitmap in error path")
11. 5df0e734b8c39598effe0f17e5bd8ff7748a0693 ("VMCI: Check exclusive_vectors
when freeing interrupt 1")
12. 1f7142915d304804a9bd952245fce92786b1b62f ("VMCI: Add support for ARM64")
13. ba03a9bbd17b149c373c0ea44017f35fc2cd0f28 ("VMCI: Release resource if the
work is already queued")
Thanks,
Vishnu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978145/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977753] Re: Azure 5.4: vDSO broken with 5.4.0-1075-azure
** Changed in: linux-azure (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/1977753
Title:
Azure 5.4: vDSO broken with 5.4.0-1075-azure
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Focal:
Fix Committed
Bug description:
SRU Justification
[Impact]
vDSO works with the 5.4.0-1074-azure kernel, but is broken in
5.4.0-1075-azure and newer due to this commit
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/+git/bionic/commit/?h=Ubuntu-azure-5.4-5.4.0-1075.78_18.04.1&id=5c899e1bcda02c755a5327353ed66f0768771644
Please revert the commit 5c899e1bcda02c755a5327353ed66f0768771644.
How to verify vDSO is working: "strace date 2>&1 | grep time" should not show
the time related syscalls, e.g. clock_gettime()
With 5.4.0-1075-azure and newer, I see the time related syscalls.
More info:
The buggy commit 5c899e1bcda02c755a5327353ed66f0768771644 was backported from
the mainline commit:
e4ab4658f1cf ("clocksource/drivers/hyper-v: Handle vDSO differences inline")
but due to the differences between the mainline kernel and the
5.4.0-107x-azure kernel, we actually should not simply remove
hv_set_clocksource_vdso().
FWIW, the mainline commit is actually buggy and is fixed by this later
mainline path:
commit 3486d2c9be652a31033363bdd50391b0c8a8fe21
Author: Vitaly Kuznetsov vkuzn...@redhat.com
Date: Thu May 13 09:32:46 2021 +0200
clocksource/drivers/hyper-v: Re-enable VDSO_CLOCKMODE_HVCLOCK on X86
Mohammed reports (https://bugzilla.kernel.org/show_bug.cgi?id=213029)
the commit e4ab4658f1cf ("clocksource/drivers/hyper-v: Handle vDSO
differences inline") broke vDSO on x86. The problem appears to be that
VDSO_CLOCKMODE_HVCLOCK is an enum value in 'enum vdso_clock_mode' and
'#ifdef VDSO_CLOCKMODE_HVCLOCK' branch evaluates to false (it is not
a define).
Use a dedicated HAVE_VDSO_CLOCKMODE_HVCLOCK define instead.
Fixes: e4ab4658f1cf ("clocksource/drivers/hyper-v: Handle vDSO differences
inline")
Reported-by: Mohammed Gamal mga...@redhat.com
Suggested-by: Thomas Gleixner t...@linutronix.de
Signed-off-by: Vitaly Kuznetsov vkuzn...@redhat.com
Signed-off-by: Thomas Gleixner t...@linutronix.de
Reviewed-by: Michael Kelley mikel...@microsoft.com
Link: https://lore.kernel.org/r/20210513073246.1715070-1-vkuzn...@redhat.com
PS, Ubunt 20.04’s 5.13.0-1026-azure is not affected.
After some discussion it was decided that the revert is the best
solution.
[Test Case]
strace date 2>&1 | grep time
also Microsoft tested
[Where things could go wrong]
vDSO entry point could stop working altogether
[Other Info]
SF: #00338309
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1977753/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978719] Re: Ubuntu 5.4.0-117.132-generic 5.4.189 has BUG: kernel NULL pointer dereference, address: 0000000000000034
Patch submitted for review: https://lists.ubuntu.com/archives/kernel- team/2022-June/130974.html ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => wyatt earp (wyatt-hackerforhire) -- 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/1978719 Title: Ubuntu 5.4.0-117.132-generic 5.4.189 has BUG: kernel NULL pointer dereference, address: 0034 Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Bug description: The 5.4.0 series of the Ubuntu kernel has missed a patch which resolves a null dereference: [104602.951260] BUG: kernel NULL pointer dereference, address: 0034 [104602.951263] #PF: supervisor write access in kernel mode [104602.951264] #PF: error_code(0x0002) - not-present page [104602.951266] PGD 0 P4D 0 [104602.951269] Oops: 0002 [#1] SMP PTI [104602.951272] CPU: 6 PID: 176572 Comm: ThreadPoolForeg Kdump: loaded Tainted: P OE 5.4.0-117-generic #132-Ubuntu [104602.951273] Hardware name: System manufacturer System Product Name/P8P67 LE, BIOS 3801 09/12/2013 [104602.951278] RIP: 0010:unlink_anon_vmas+0x3e/0x1b0 [104602.951280] Code: 54 53 48 83 ec 08 48 8b 47 78 48 89 7d d0 48 8b 30 49 39 c5 0f 84 5e 01 00 00 4c 8d 78 f0 4c 8d 66 f0 31 db eb 21 49 8b 46 38 <83> 68 34 01 49 8b 44 24 10 49 8d 54 24 10 4d 89 e7 48 83 e8 10 49 [104602.951281] RSP: 0018:c00908703bd8 EFLAGS: 00010246 [104602.951283] RAX: RBX: RCX: [104602.951284] RDX: RSI: 99e8e5815c48 RDI: [104602.951286] RBP: c00908703c08 R08: 0001 R09: ae665f00 [104602.951287] R10: 99eb808bd6c0 R11: 0001 R12: 99eb0fda27b8 [104602.951288] R13: 99eb0fda27c8 R14: 99e8e5815c08 R15: 99e7ee7af6c0 [104602.951290] FS: () GS:99eb8eb8() knlGS: [104602.951291] CS: 0010 DS: ES: CR0: 80050033 [104602.951293] CR2: 0034 CR3: 00037ae0a005 CR4: 000606e0 [104602.951294] Call Trace: [104602.951299] free_pgtables+0x93/0xf0 [104602.951301] exit_mmap+0xc7/0x1b0 [104602.951304] mmput+0x5d/0x130 [104602.951306] do_exit+0x31a/0xaf0 [104602.951309] do_group_exit+0x47/0xb0 [104602.951312] get_signal+0x169/0x890 [104602.951315] do_signal+0x34/0x6c0 [104602.951318] ? _copy_from_user+0x3e/0x60 [104602.951321] ? __x64_sys_futex+0x13f/0x170 [104602.951324] exit_to_usermode_loop+0xbf/0x160 [104602.951327] do_syscall_64+0x163/0x190 [104602.951330] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [104602.951332] RIP: 0033:0x7f58d1db27d1 [104602.951335] Code: Bad RIP value. [104602.951336] RSP: 002b:7f58c6987370 EFLAGS: 0246 ORIG_RAX: 00ca [104602.951338] RAX: fdfc RBX: 7f58c69875e8 RCX: 7f58d1db27d1 [104602.951339] RDX: RSI: 0089 RDI: 7f58c6987600 [104602.951340] RBP: 7f58c69875d8 R08: R09: [104602.951341] R10: 7f58c6987460 R11: 0246 R12: 7f58c69875fc [104602.951343] R13: 7f58c69875b0 R14: 7f58c6987600 R15: 7f58c69873c0 The patch was posted back in 2021 the linux kernel mailing lists: https://lore.kernel.org/linux- mm/20210224200449.hku5gteih%25a...@linux-foundation.org/ The defect is: Date: Wed, 24 Feb 2021 12:04:49 -0800 [thread overview] Message-ID: <20210224200449.hku5gteih%a...@linux-foundation.org> (raw) In-Reply-To: <20210224115824.1e289a6895087f10c41dd...@linux-foundation.org> From: Li Xinhai Subject: mm: rmap: explicitly reset vma->anon_vma in unlink_anon_vmas() In case the vma will continue to be used after unlink its relevant anon_vma, we need to reset the vma->anon_vma pointer to NULL. So, later when fault happen within this vma again, a new anon_vma will be prepared. By this way, the vma will only be checked for reverse mapping of pages which been fault in after the unlink_anon_vmas call. Currently, the mremap with MREMAP_DONTUNMAP scenario will continue use the vma after moved its page table entries to a new vma. For other scenarios, the vma itself will be freed after call unlink_anon_vmas. Link: https://lkml.kernel.org/r/20210119075126.3513154-1-lixinhai@gmail.com Signed-off-by: Li Xinhai Cc: Andrea Arcangeli Cc: Brian Geffon Cc: Kirill A. Shutemov Cc: Lokesh Gidra Cc: Minchan Kim Cc: Vlastimil Babka Signed-off-
[Kernel-packages] [Bug 1978347] Re: horrible IO degradation with encrypted zfs root on kernels past 5.15.0-27
** Also affects: zfs-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1978347 Title: horrible IO degradation with encrypted zfs root on kernels past 5.15.0-27 Status in linux package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: IO on encrypted zfs root has fallen off a cliff in kernel versions after 5.15.0-27 (the degradation is observed since version 5.15.0-30, also seen on -33 and -37, -25 and -27 work like a charm). Heavy usage almost hangs a new laptop (building large singularity images or synthetic testing with dd). I have confirmed that things are working as expected on a default + upgraded Ubuntu 22.04 desktop LVM+LUKS installation using another NVMe SSD on the same laptop. There seems to be a regression when using the native zfs encryption (did aes-ni acceleration get turned off?) How to reproduce: - install ubuntu 22.04 desktop from iso, don't install web updates, check use zfs and encryption - sudo apt update && apt install dstat htop - create a dataset with compression disabled so that dd actually writes things to disk * sudo zfs create rpool/dummy * sudo zfs set compress=off rpool/dummy * sudo chown -R myusername. /dummy - start dstat and htop in the background (show kernel threads in the htop config) - dd if=/dev/zero of=/dummy/bigfile bs=1M count=16384 - sudo apt upgradeand reboot on the latest kernel, repeat Expected: some cpu load, dstat reports write speeds about as much as the SSD can sustain (2.9-3GiB/s with a 2TiB Samsung 970 EVO Plus for a 16GiB write test, 1.4GiB/s for a few seconds then 800MiB/s sustained for whatever WD 512GiB model I had laying around). Observed on versions -30 and later: 700% or more system cpu load, mostly in z_wr_iss threads, writes top at around 150-180MiB/s, the system becomes somewhat unresponsive. Reads are also not good but I have not benchmarked. Booting the system and launching apps seems about normal due to the low IO load. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-37-generic 5.15.0-37.39 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laperlej 4100 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 10 15:52:12 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2022-05-10 (31 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: HP HP EliteBook 850 G8 Notebook PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rgwvzq@/vmlinuz-5.15.0-37-generic root=ZFS=rpool/ROOT/ubuntu_rgwvzq ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.15.0-37-generic N/A linux-backports-modules-5.15.0-37-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/11/2022 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: T76 Ver. 01.08.00 dmi.board.name: 8846 dmi.board.vendor: HP dmi.board.version: KBC Version 30.37.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 48.55 dmi.modalias: dmi:bvnHP:bvrT76Ver.01.08.00:bd01/11/2022:br8.0:efr48.55:svnHP:pnHPEliteBook850G8NotebookPC:pvr:rvnHP:rn8846:rvrKBCVersion30.37.00:cvnHP:ct10:cvr:sku4V1S3UP#ABL: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G8 Notebook PC dmi.product.sku: 4V1S3UP#ABL dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978145] Re: Request to back port vmci patches to Ubuntu kernel
Patches submitted: https://lists.ubuntu.com/archives/kernel-
team/2022-June/130976.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1978145
Title:
Request to back port vmci patches to Ubuntu kernel
Status in linux package in Ubuntu:
Confirmed
Bug description:
The request is to bring vmci to TOT and back port the following patches into
Ubuntu kernels.
1. fac608138c6136126faadafa5554cc0bbabf3c44 ("VMCI: dma dg: whitespace
formatting change for vmci register defines")
2. e283a0e8b7ea83915e988ed059384af166b444c0 ("VMCI: dma dg: add MMIO access
to registers")
3. eed2298d936087a1c85e0fa6f7170028e4f4fded ("VMCI: dma dg: detect DMA
datagram capability")
4. 8cb520bea1470ca205980fbf030ed1f472f4af2f ("VMCI: dma dg: set OS page
size")
5. cc68f2177fcbfe2dbe5e9514789b96ba5995ec1e ("VMCI: dma dg: register dummy
IRQ handlers for DMA datagrams")
6. 5ee109828e73bbe4213c373988608d8f33e03d78 ("VMCI: dma dg: allocate send
and receive buffers for DMA datagrams")
7. 22aa5c7f323022477b70e044eb00e6bfea9498e8 ("VMCI: dma dg: add support for
DMA datagrams sends")
8. 463713eb6164b6577f8e91447c7745628215531b ("VMCI: dma dg: add support for
DMA datagrams receive")
9. 77e861619baea5a7c934e47fda74b03c0b072aec ("VMCI: Fix some error handling
paths in vmci_guest_probe_device()")
10. c8e9b30ccae605bf1dbeaf03971f9b83f70b928d ("VMCI: Release
notification_bitmap in error path")
11. 5df0e734b8c39598effe0f17e5bd8ff7748a0693 ("VMCI: Check exclusive_vectors
when freeing interrupt 1")
12. 1f7142915d304804a9bd952245fce92786b1b62f ("VMCI: Add support for ARM64")
13. ba03a9bbd17b149c373c0ea44017f35fc2cd0f28 ("VMCI: Release resource if the
work is already queued")
Thanks,
Vishnu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978145/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added)
Are kernels from https://kernel.ubuntu.com/~kernel-ppa/mainline/ safe to try, as in, will I be able to boot afterwards if I have an LVM2 (LUKS?) encrypted root (Set up using the Ubuntu installer)? -- 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/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel paramater intel_idle.max_cstate=4 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978719] Re: Ubuntu 5.4.0-117.132-generic 5.4.189 has BUG: kernel NULL pointer dereference, address: 0000000000000034
Thank you for the prompt response!
--
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/1978719
Title:
Ubuntu 5.4.0-117.132-generic 5.4.189 has BUG: kernel NULL pointer
dereference, address: 0034
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
In Progress
Bug description:
The 5.4.0 series of the Ubuntu kernel has missed a patch which
resolves a null dereference:
[104602.951260] BUG: kernel NULL pointer dereference, address:
0034
[104602.951263] #PF: supervisor write access in kernel mode
[104602.951264] #PF: error_code(0x0002) - not-present page
[104602.951266] PGD 0 P4D 0
[104602.951269] Oops: 0002 [#1] SMP PTI
[104602.951272] CPU: 6 PID: 176572 Comm: ThreadPoolForeg Kdump: loaded
Tainted: P OE 5.4.0-117-generic #132-Ubuntu
[104602.951273] Hardware name: System manufacturer System Product Name/P8P67
LE, BIOS 3801 09/12/2013
[104602.951278] RIP: 0010:unlink_anon_vmas+0x3e/0x1b0
[104602.951280] Code: 54 53 48 83 ec 08 48 8b 47 78 48 89 7d d0 48 8b 30 49
39 c5 0f 84 5e 01 00 00 4c 8d 78 f0 4c 8d 66 f0 31 db eb 21 49 8b 46 38 <83> 68
34 01 49 8b 44 24 10 49 8d 54 24 10 4d 89 e7 48 83 e8 10 49
[104602.951281] RSP: 0018:c00908703bd8 EFLAGS: 00010246
[104602.951283] RAX: RBX: RCX:
[104602.951284] RDX: RSI: 99e8e5815c48 RDI:
[104602.951286] RBP: c00908703c08 R08: 0001 R09:
ae665f00
[104602.951287] R10: 99eb808bd6c0 R11: 0001 R12:
99eb0fda27b8
[104602.951288] R13: 99eb0fda27c8 R14: 99e8e5815c08 R15:
99e7ee7af6c0
[104602.951290] FS: () GS:99eb8eb8()
knlGS:
[104602.951291] CS: 0010 DS: ES: CR0: 80050033
[104602.951293] CR2: 0034 CR3: 00037ae0a005 CR4:
000606e0
[104602.951294] Call Trace:
[104602.951299] free_pgtables+0x93/0xf0
[104602.951301] exit_mmap+0xc7/0x1b0
[104602.951304] mmput+0x5d/0x130
[104602.951306] do_exit+0x31a/0xaf0
[104602.951309] do_group_exit+0x47/0xb0
[104602.951312] get_signal+0x169/0x890
[104602.951315] do_signal+0x34/0x6c0
[104602.951318] ? _copy_from_user+0x3e/0x60
[104602.951321] ? __x64_sys_futex+0x13f/0x170
[104602.951324] exit_to_usermode_loop+0xbf/0x160
[104602.951327] do_syscall_64+0x163/0x190
[104602.951330] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[104602.951332] RIP: 0033:0x7f58d1db27d1
[104602.951335] Code: Bad RIP value.
[104602.951336] RSP: 002b:7f58c6987370 EFLAGS: 0246 ORIG_RAX:
00ca
[104602.951338] RAX: fdfc RBX: 7f58c69875e8 RCX:
7f58d1db27d1
[104602.951339] RDX: RSI: 0089 RDI:
7f58c6987600
[104602.951340] RBP: 7f58c69875d8 R08: R09:
[104602.951341] R10: 7f58c6987460 R11: 0246 R12:
7f58c69875fc
[104602.951343] R13: 7f58c69875b0 R14: 7f58c6987600 R15:
7f58c69873c0
The patch was posted back in 2021 the linux kernel mailing lists:
https://lore.kernel.org/linux-
mm/20210224200449.hku5gteih%25a...@linux-foundation.org/
The defect is:
Date: Wed, 24 Feb 2021 12:04:49 -0800 [thread overview]
Message-ID: <20210224200449.hku5gteih%a...@linux-foundation.org> (raw)
In-Reply-To: <20210224115824.1e289a6895087f10c41dd...@linux-foundation.org>
From: Li Xinhai
Subject: mm: rmap: explicitly reset vma->anon_vma in unlink_anon_vmas()
In case the vma will continue to be used after unlink its relevant
anon_vma, we need to reset the vma->anon_vma pointer to NULL. So, later
when fault happen within this vma again, a new anon_vma will be prepared.
By this way, the vma will only be checked for reverse mapping of pages
which been fault in after the unlink_anon_vmas call.
Currently, the mremap with MREMAP_DONTUNMAP scenario will continue use the
vma after moved its page table entries to a new vma. For other scenarios,
the vma itself will be freed after call unlink_anon_vmas.
Link:
https://lkml.kernel.org/r/20210119075126.3513154-1-lixinhai@gmail.com
Signed-off-by: Li Xinhai
Cc: Andrea Arcangeli
Cc: Brian Geffon
Cc: Kirill A. Shutemov
Cc: Lokesh Gidra
Cc: Minchan Kim
Cc: Vlastimil Babka
Signed-off-by: Andrew Morton
---
mm/rmap.c |9 -
1 file changed, 8 insertions(+), 1 deletion(-)
--- a/mm/rmap.c~mm-rmap-explicitly-reset-vma-anon_vma-in-unlink_anon_vmas
+++ a/mm/rmap.c
@@ -413,8 +413,15 @@ void unlink_anon_vmas(struct vm_area_str
list_del(&avc->same_vma);
anon_vma_chain_free(avc);
}
- if (vma->anon_vma)
+ if (vma->anon_vma) {
vma->anon_vma->degree--;
+
[Kernel-packages] [Bug 1978745] [NEW] Need to delete existing APN profiles in Mobile broadband GUI to connect to cellular
Public bug reported: [Description] During initial setup, user needs to delete all the existing APN profiles listed in the Mobile broadband GUI and create a new one in order to connect to cellular [Expected results] If an APN profile of the current sim is already existing in the mobile broadband GUI, system should be able to connect to cellular by using the existing profile [Actual results] If an APN profile of the current sim being used is already existing in the mobile broadband GUI, the system fails to connect using the existing profile. [Steps to reproduce] 1. Create the APN profile for the sim card to be used. 2. Turn off the system and insert the sim card into the sim card slot. 3. Turn on the system and enter the password (if needed). Boot to OS. 4. Connect to cellular by selecting "Mobile broadband" under the system tray and selecting the name of the APN profile previously created. Notice that connection is unable to be established ==> PROBLEM [Workaround] Delete all existing APN profiles and create a new APN profile. Ubuntu release version: Ubuntu 20.04.4 LTS Kernel version: 5.15.0-33-generic (hwe-kernel) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-33-generic 5.15.0-33.34~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-33.34~20.04.1-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 15 10:03:28 2022 InstallationDate: Installed on 2022-06-01 (13 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1978745 Title: Need to delete existing APN profiles in Mobile broadband GUI to connect to cellular Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: [Description] During initial setup, user needs to delete all the existing APN profiles listed in the Mobile broadband GUI and create a new one in order to connect to cellular [Expected results] If an APN profile of the current sim is already existing in the mobile broadband GUI, system should be able to connect to cellular by using the existing profile [Actual results] If an APN profile of the current sim being used is already existing in the mobile broadband GUI, the system fails to connect using the existing profile. [Steps to reproduce] 1. Create the APN profile for the sim card to be used. 2. Turn off the system and insert the sim card into the sim card slot. 3. Turn on the system and enter the password (if needed). Boot to OS. 4. Connect to cellular by selecting "Mobile broadband" under the system tray and selecting the name of the APN profile previously created. Notice that connection is unable to be established ==> PROBLEM [Workaround] Delete all existing APN profiles and create a new APN profile. Ubuntu release version: Ubuntu 20.04.4 LTS Kernel version: 5.15.0-33-generic (hwe-kernel) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-33-generic 5.15.0-33.34~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-33.34~20.04.1-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 15 10:03:28 2022 InstallationDate: Installed on 2022-06-01 (13 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1978745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978751] [NEW] package linux-modules-nvidia-510-5.13.0-48-generic 5.13.0-48.54~20.04.1 failed to install/upgrade: installed linux-modules-nvidia-510-5.13.0-48-generic package po
Public bug reported: I tried to do sudo apt upgrade and got this error. I am very new to Ubuntu and don't know what information I should contain in this report. Sorry. It just popped up that I should submit a report. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-nvidia-510-5.13.0-48-generic 5.13.0-48.54~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 14 20:45:31 2022 ErrorMessage: installed linux-modules-nvidia-510-5.13.0-48-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-02-17 (117 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: linux-restricted-modules-hwe-5.13 Title: package linux-modules-nvidia-510-5.13.0-48-generic 5.13.0-48.54~20.04.1 failed to install/upgrade: installed linux-modules-nvidia-510-5.13.0-48-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-restricted-modules-hwe-5.13 (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-restricted-modules-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1978751 Title: package linux-modules-nvidia-510-5.13.0-48-generic 5.13.0-48.54~20.04.1 failed to install/upgrade: installed linux- modules-nvidia-510-5.13.0-48-generic package post-installation script subprocess returned error exit status 1 Status in linux-restricted-modules-hwe-5.13 package in Ubuntu: New Bug description: I tried to do sudo apt upgrade and got this error. I am very new to Ubuntu and don't know what information I should contain in this report. Sorry. It just popped up that I should submit a report. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-nvidia-510-5.13.0-48-generic 5.13.0-48.54~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 14 20:45:31 2022 ErrorMessage: installed linux-modules-nvidia-510-5.13.0-48-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-02-17 (117 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: linux-restricted-modules-hwe-5.13 Title: package linux-modules-nvidia-510-5.13.0-48-generic 5.13.0-48.54~20.04.1 failed to install/upgrade: installed linux-modules-nvidia-510-5.13.0-48-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.13/+bug/1978751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978380] Re: External monitor not detected
I don't know the internal wiring of the laptop so can't be totally sure. In 99% of laptops I have seen, the USB-C port is owned by the Intel chipset. So indeed if you connect a display cable to it that's USB-C at one end then that port should operate as a monitor wired directly to the Intel GPU. It's likely the Mini DisplayPort is also wired directly to the Intel GPU. But there's a chance the Nvidia GPU owns that port. It won't take long to find out with the right cables. -- 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/1978380 Title: External monitor not detected Status in linux package in Ubuntu: Invalid Bug description: Hello. I have a laptop Lenovo Legion Y540-15IRH (81SX00EVRA) with Hybrid graphics. OS: 20.04.4 LTS and Windows 10 in dual boot. BIOS is set to Switchable Graphics, meaning Hybrid. NVidia PRIME profile is set to Intel (power saving). So the problem is that on Ubuntu system doesn't detect an external monitor through HDMI port. When PRIME profile was set to NVidia best Performance - it was able to detect the external monitor. But as I am not playing games anymore - I don't want to use power-consuming and noisy discrete RTX 2060. So I switched to integrated Intel UHD Graphics 630. What should I do in order OS to detect an external monitor? Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 11 14:41:50 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.13.0-44-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.13.0-48-generic, x86_64: installed nvidia, 470.129.06, 5.13.0-44-generic, x86_64: installed nvidia, 470.129.06, 5.13.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:3ffd] NVIDIA Corporation TU106M [GeForce RTX 2060 Mobile] [10de:1f11] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU106M [GeForce RTX 2060 Mobile] [17aa:3ffd] InstallationDate: Installed on 2020-10-21 (597 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 81SX ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-48-generic root=UUID=96af554d-dedb-4846-b7ca-651771269b4c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2022 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y540-15IRH dmi.ec.firmware.release: 1.44 dmi.modalias: dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81SX:pvrLegionY540-15IRH:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegionY540-15IRH:skuLENOVO_MT_81SX_BU_idea_FM_LegionY540-15IRH: dmi.product.family: Legion Y540-15IRH dmi.product.name: 81SX dmi.product.sku: LENOVO_MT_81SX_BU_idea_FM_Legion Y540-15IRH dmi.product.version: Legion Y540-15IRH dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978380/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added)
> The bug exists on 5.15.35, 5.16.20, 5.17.5, 5.15.36. Then the range to search is between 5.17.5 (failing) and 5.18.2 (working). We need to find adjacent version numbers where one is failing and the next is working. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel paramater intel_idle.max_cstate=4 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978488] Re: LibreOffice Writer lags freezes high CPU 22.04 LTS
** Changed in: libreoffice (Ubuntu) Importance: Undecided => Medium -- 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/1978488 Title: LibreOffice Writer lags freezes high CPU 22.04 LTS Status in Ubuntu MATE: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: Upgraded to 22.04 LTS (20.04 no issues). Using Nvidia 4xx series driver. 48GB RAM, dual 1080ti gpu, i7 cpu. LibreOffice Writer constantly lags, losing function, freezes (does not crash) with any type of writer document (odt or xslx). New single page or existing multi-page documents, doesn't matter, same issue after a minute or two. Hates text selection, mouse-wheel scrolling is a tell- tale sign. New Writer windows opened during lag are black. CPU usage in htop is very high for soffice.bin, ~60 - 80%. Must pkill the soffice.bin and use file recover but lag freeze up will occur again soon after opening. I experience the issue with all three installation methods: snap, distro command-line install, or using the LibreOffice ppa "fresh". I've tried changing OpenCL settings, disabling all extensions, disable smooth scrolling, disabling java, have purged install/reinstall and limiting to single window. I have the Marco ppa installed (ppa:ubuntu- mate-dev/marco). Doesn't seem to matter or what mate-tweak option is selected. LO using Yaru or other theme; doesn't matter same effect. Terminal does not show me any helpful errors when Writer is called directly from command line, at least I can easily identify. Guessing this is upstream of MATE and a libreoffice thing; a few similar issues around the web but no good workaround. I can update my exact specs and kernel later as required. Thanks! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-03-27 (1174 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) Package: nvidia-graphics-drivers-510 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Tags: third-party-packages jammy Uname: Linux 5.15.0-37-generic x86_64 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 2022-06-03 (10 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1978488/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968311] Re: Jammy Jellyfish beta doesn't boot with zfs + encryption (Dell XPS 13)
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1968311 Title: Jammy Jellyfish beta doesn't boot with zfs + encryption (Dell XPS 13) Status in linux package in Ubuntu: Expired Bug description: I tried installing multiple times, with the Beta version and daily 2022-04-05. I was afraid it was driver related so I tried with and without installing 3rd party software. After unlocking the drive, I can watch what services are starting - it freezes right after "Started Thunderbolt system service." After a while it says "[drm] CPU pipe a FIFO underrun." It always freezes at the same point and never boots. Jammy Jellyfish installed on EXT4 booted just fine on the Dell XPS 13. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968311/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977703] [NEW] Ubuntu 18.04 is getting crashed on Dell Latitude 3420
You have been subscribed to a public bug: Ubuntu 18.04 is getting crashed on Dell Latitude 3420 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Ubuntu 18.04 is getting crashed on Dell Latitude 3420 https://bugs.launchpad.net/bugs/1977703 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977703] Re: Ubuntu 18.04 is getting crashed on Dell Latitude 3420
** Project changed: ubuntu-certification => linux ** Project changed: linux => linux (Ubuntu) -- 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/1977703 Title: Ubuntu 18.04 is getting crashed on Dell Latitude 3420 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04 is getting crashed on Dell Latitude 3420 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1977703/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977703] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1977703 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1977703 Title: Ubuntu 18.04 is getting crashed on Dell Latitude 3420 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04 is getting crashed on Dell Latitude 3420 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1977703/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977703] Re: Ubuntu 18.04 is getting crashed on Dell Latitude 3420
** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1977703 Title: Ubuntu 18.04 is getting crashed on Dell Latitude 3420 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04 is getting crashed on Dell Latitude 3420 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1977703/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978530] Re: [8086:7af0][8086:40c4] Missing support for Intel AX204 NGW wireless card
** Tags added: kern-3565
--
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/1978530
Title:
[8086:7af0][8086:40c4] Missing support for Intel AX204 NGW wireless
card
Status in linux-firmware package in Ubuntu:
New
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux-firmware source package in Jammy:
New
Status in linux-oem-5.17 source package in Jammy:
In Progress
Status in linux-firmware source package in Kinetic:
New
Status in linux-oem-5.17 source package in Kinetic:
Invalid
Bug description:
commit ac4790dcd0ff ("iwlwifi: pcie: add support for MS devices").
*
https://patchwork.kernel.org/project/linux-wireless/patch/iwlwifi.20220129105618.a82ca9207ace.I38aa0acfb7846b179027b6f87f5f88f8e4177f63@changeid/
*
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ac4790dcd0ffede2085a54ab12a4b70a48789215
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1978530/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
Does anyone know is it reproducible with ubuntu 22.04?
--
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/1775717
Title:
CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
Status in linux package in Ubuntu:
Confirmed
Bug description:
After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
GPU fans suddenly go full throttle. It doesn't seem to depend on
temperature, could happen when 32 °C reported, sometimes the laptop
can work for day or two without this issue, but eventually it happens.
The only way to stop fans is to power off the laptop, power on (fans
go 100% at this point again), power off during BIOS splash screen and
power on again. Seems to happen more often after waking up from a
sleep.
Things tried:
Upgrading BIOS to latest available on ASUS site to the date of
writing. No change.
asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
does not seem to control it and does not prevent going full throttle.
4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
issue.
Userspace fan control software (https://github.com/hirschmann/nbfc).
Can control speed of both fans to the point where they go full
throttle, after that has no effect on them.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: whale 3068 F pulseaudio
/dev/snd/controlC0: whale 3068 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
InstallationDate: Installed on 2014-10-20 (1333 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac
(20140722.2)
MachineType: ASUSTeK COMPUTER INC. G752VT
NonfreeKernelModules: nvidia_modeset nvidia wl
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash
acpi_backlight=vendor vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-23-generic N/A
linux-backports-modules-4.15.0-23-generic N/A
linux-firmware 1.173.1
Tags: bionic
Uname: Linux 4.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty
video
_MarkForUpload: True
dmi.bios.date: 06/29/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G752VT.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G752VT
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: G
dmi.product.name: G752VT
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/1775717/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978539] Re: nvidia-dkms-470 fails to build with kernel 5.19
same fixes for nvidia-dkms-470-server ** Patch added: "support-linux-5.19-nvidia-470-server.debdiff" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1978539/+attachment/5597370/+files/support-linux-5.19-nvidia-470-server.debdiff -- 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/1978539 Title: nvidia-dkms-470 fails to build with kernel 5.19 Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in nvidia-graphics-drivers-470 source package in Kinetic: New Bug description: [Impact] nvidia-dkms-470 fails to build on kinetic with the new (upcoming) kernel 5.19. [Test case] sudo apt install nvidia-dkms-470 [Fix] Change driver to support the new 5.19 ABI. [Regression potential] We may see build issues / regressions in kernels >= 5.19, since the fix are only affecting kernels >= 5.19. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1978539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1976567] [NEW] Desktop resolution was set incorrectly (1024x768) until I booted up the PC AFTER turning on the monitor
You have been subscribed to a public bug: Whenever I boot up my PC, I turn on the monitor as well. When this happens, the Intel Mesa graphics loads, and my screen ends up being small with large pixelated icons. The resolution was capped at 1024x768. Only after I reboot my PC multiple times without changing the display settings did the resolution increase to 1680x1050, the correct resolution. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 1 21:07:53 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0589] InstallationDate: Installed on 2022-05-22 (10 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Gateway DX4860 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=804dde02-f626-4837-9802-fcd2a3da1eeb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2011 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02-A1 dmi.board.name: IPISB-VR dmi.board.vendor: Gateway dmi.board.version: 1.01 dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:br4.6:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr:sku: dmi.product.family: Gateway Desktop dmi.product.name: DX4860 dmi.sys.vendor: Gateway version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: mutter (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug jammy resolution ubuntu wayland-session -- Desktop resolution was set incorrectly (1024x768) until I booted up the PC AFTER turning on the monitor https://bugs.launchpad.net/bugs/1976567 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1976567] Re: Desktop resolution was set incorrectly (1024x768) until I booted up the PC AFTER turning on the monitor
I just encountered the bug again. When I turned on the monitor the login screen is at 1024x768 and the system log shows it is using Wayland: Jun 15 14:03:49 nine gnome-shell[1225]: Running GNOME Shell (using mutter 42.1) as a Wayland display server Although the monitor was plugged in when the system booted, the kernel failed to get a working connection: Jun 15 14:03:50 nine kernel: i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful That's _after_ the login screen had started. So the bug is occurring when the kernel can detect a monitor (hence bug 1919400 doesn't happen) but can't establish a reliable display signal. For me, the fix was just to log in as usual. Then the correct screen resolution is detected and used. If the problem persists for you after logging in then it's a sign you probably need to replug or replace the monitor data cable. I don't see any real bug here unless it's the kernel failing to train when it shouldn't fail. ** Package changed: xorg-server (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => Opinion ** No longer affects: mutter (Ubuntu) ** Summary changed: - Desktop resolution was set incorrectly (1024x768) until I booted up the PC AFTER turning on the monitor + [i915] Desktop resolution was set incorrectly (1024x768) until I booted up the PC AFTER turning on the monitor -- 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/1976567 Title: [i915] Desktop resolution was set incorrectly (1024x768) until I booted up the PC AFTER turning on the monitor Status in linux package in Ubuntu: Opinion Bug description: Whenever I boot up my PC, I turn on the monitor as well. When this happens, the Intel Mesa graphics loads, and my screen ends up being small with large pixelated icons. The resolution was capped at 1024x768. Only after I reboot my PC multiple times without changing the display settings did the resolution increase to 1680x1050, the correct resolution. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 1 21:07:53 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0589] InstallationDate: Installed on 2022-05-22 (10 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Gateway DX4860 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=804dde02-f626-4837-9802-fcd2a3da1eeb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2011 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02-A1 dmi.board.name: IPISB-VR dmi.board.vendor: Gateway dmi.board.version: 1.01 dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:br4.6:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr:sku: dmi.product.family: Gateway Desktop dmi.product.name: DX4860 dmi.sys.vendor: Gateway version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976567/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978777] [NEW] [Intel 9560] wifi connection does not work properly
You have been subscribed to a public bug: I am not able to say much, since I don't know how to describe the problem. Yet I can mention that whenever I am trying to download the files like whatever is required to upgrade the software, the wifi connection does not work properly(Mobile Data, usually). I have checked if there is an error in the Wifi module by running the same, within Windows 11 updates, which worked normally as expected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 15 11:44:08 2022 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 470.103.01, 5.4.0-104-generic, x86_64: installed nvidia, 470.103.01, 5.4.0-107-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:85fc] NVIDIA Corporation Device [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:85fc] InstallationDate: Installed on 2020-10-26 (596 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b627 Chicony Electronics Co., Ltd Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 002: ID 3938:1032 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-107-generic root=UUID=aafecb7f-435a-43bb-a2ed-eabab507c6ad ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2021 dmi.bios.vendor: Insyde dmi.bios.version: F.50 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85FC dmi.board.vendor: HP dmi.board.version: 42.47 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.50:bd08/18/2021:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FC:rvr42.47:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx dmi.product.sku: 7LH02PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: linux-hwe-5.4 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- [Intel 9560] wifi connection does not work properly https://bugs.launchpad.net/bugs/1978777 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978777] Re: [Intel 9560] wifi connection does not work properly
** Summary changed: - NOt able to Install any updates + [Intel 9560] wifi connection does not work properly ** Package changed: xorg (Ubuntu) => linux-hwe-5.4 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1978777 Title: [Intel 9560] wifi connection does not work properly Status in linux-hwe-5.4 package in Ubuntu: New Bug description: I am not able to say much, since I don't know how to describe the problem. Yet I can mention that whenever I am trying to download the files like whatever is required to upgrade the software, the wifi connection does not work properly(Mobile Data, usually). I have checked if there is an error in the Wifi module by running the same, within Windows 11 updates, which worked normally as expected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 15 11:44:08 2022 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 470.103.01, 5.4.0-104-generic, x86_64: installed nvidia, 470.103.01, 5.4.0-107-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:85fc] NVIDIA Corporation Device [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:85fc] InstallationDate: Installed on 2020-10-26 (596 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b627 Chicony Electronics Co., Ltd Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 002: ID 3938:1032 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-107-generic root=UUID=aafecb7f-435a-43bb-a2ed-eabab507c6ad ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2021 dmi.bios.vendor: Insyde dmi.bios.version: F.50 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85FC dmi.board.vendor: HP dmi.board.version: 42.47 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.50:bd08/18/2021:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FC:rvr42.47:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx dmi.product.sku: 7LH02PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1978777/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
