[Kernel-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3037 https://gitlab.gnome.org/GNOME/mutter/-/issues/3037 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/3037 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland Status in Linux: New Status in Mutter: Unknown Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: In Progress Status in linux source package in Mantic: Confirmed Status in mutter source package in Mantic: In Progress Bug description: I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
Yes I was referring to the linux task. -- 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/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer Status in gdm: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in gdm3 source package in Jammy: In Progress Status in linux source package in Jammy: Won't Fix Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in gdm3 source package in Mantic: Fix Released Status in linux source package in Mantic: Confirmed Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Status in linux package in Fedora: Fix Released Bug description: [ Impact ] The fbdev subsystem has been deprecated for a long time. We should drop it in favour of using simpledrm with fbdev emulation layer. This requires Kernel config changes: FB_EFI=n FB_VESA=n fbcon will still require FB to be available, but will use the fbdev emulation layer When this stack is enabled, it changes boot timing such that some drivers may take a longer time to boot and GDM may hang in a black screen. This issue has been readily reproduced in Ubuntu and reported to upstream mutter. https://gitlab.gnome.org/GNOME/mutter/-/issues/2909 [ Test Plan ] * Ensure that a kernel with required kernel changes can boot to GDM using DRM driver (amdgpu, i915, or nouveau) [ Where Problems could occur ] * Race conditions could be exposed to DE environments * Software that expects to find DRM device at /dev/dri/card0 may have a problem. * Some older versions of NVIDIA driver might not work properly. [ Other Info ] * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
The kernel part yes. The bug fix in GDM to prepare for whenever the kernel part happens I would think not. -- 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/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer Status in gdm: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in gdm3 source package in Jammy: In Progress Status in linux source package in Jammy: Won't Fix Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in gdm3 source package in Mantic: Fix Released Status in linux source package in Mantic: Confirmed Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Status in linux package in Fedora: Fix Released Bug description: [ Impact ] The fbdev subsystem has been deprecated for a long time. We should drop it in favour of using simpledrm with fbdev emulation layer. This requires Kernel config changes: FB_EFI=n FB_VESA=n fbcon will still require FB to be available, but will use the fbdev emulation layer When this stack is enabled, it changes boot timing such that some drivers may take a longer time to boot and GDM may hang in a black screen. This issue has been readily reproduced in Ubuntu and reported to upstream mutter. https://gitlab.gnome.org/GNOME/mutter/-/issues/2909 [ Test Plan ] * Ensure that a kernel with required kernel changes can boot to GDM using DRM driver (amdgpu, i915, or nouveau) [ Where Problems could occur ] * Race conditions could be exposed to DE environments * Software that expects to find DRM device at /dev/dri/card0 may have a problem. * Some older versions of NVIDIA driver might not work properly. [ Other Info ] * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033735] Re: [mantic] New 6.5.0.2 kernel + Intel GPU = no HDMI
I don't think this is a bug. When the Nvidia GPU is disabled it is
expected that the ports wired to it will also be disabled.
** Changed in: linux (Ubuntu)
Status: Confirmed => Opinion
--
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/2033735
Title:
[mantic] New 6.5.0.2 kernel + Intel GPU = no HDMI
Status in linux package in Ubuntu:
Opinion
Bug description:
Hi,
Legion laptop with Nvidia.
- Nouveau : no hdmi
- Nvidia 535 dynamic graphics : no HDMI (screen not detected)
- Nvidia 535 discrete graphics : HDMI is detected
So I suppose this bug to be linked to Intel GPU.
All was ok with previous 6.3 kernel.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fthx 3395 F wireplumber
/dev/snd/controlC1: fthx 3395 F wireplumber
/dev/snd/seq:fthx 3390 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2021-09-15 (723 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
RelatedPackageVersions:
linux-restricted-modules-6.5.0-5-generic N/A
linux-backports-modules-6.5.0-5-generic N/A
linux-firmware 20230815.git0e048b06-0ubuntu1
Tags: mantic wayland-session
Uname: Linux 6.5.0-5-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-03-06 (186 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 07/10/2023
dmi.bios.release: 1.54
dmi.bios.vendor: LENOVO
dmi.bios.version: J2CN54WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76461 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion 5 Pro 16IAH7H
dmi.ec.firmware.release: 1.54
dmi.modalias:
dmi:bvnLENOVO:bvrJ2CN54WW:bd07/10/2023:br1.54:efr1.54:svnLENOVO:pn82RF:pvrLegion5Pro16IAH7H:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLegion5Pro16IAH7H:skuLENOVO_MT_82RF_BU_idea_FM_Legion5Pro16IAH7H:
dmi.product.family: Legion 5 Pro 16IAH7H
dmi.product.name: 82RF
dmi.product.sku: LENOVO_MT_82RF_BU_idea_FM_Legion 5 Pro 16IAH7H
dmi.product.version: Legion 5 Pro 16IAH7H
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033735/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036998] Re: Xorg freeze
** Tags added: amdgpu ** Summary changed: - Xorg freeze + [amdgpu] Oops in dm_helpers_dp_mst_send_payload_allocation+0x90/0xd0 [amdgpu] ** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu) ** Summary changed: - [amdgpu] Oops in dm_helpers_dp_mst_send_payload_allocation+0x90/0xd0 [amdgpu] + [amdgpu] Oops in dm_helpers_dp_mst_send_payload_allocation+0x90/0xd0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2036998 Title: [amdgpu] Oops in dm_helpers_dp_mst_send_payload_allocation+0x90/0xd0 Status in linux-hwe-6.2 package in Ubuntu: New Bug description: Amdgpu tends to freeze on resume with DP1.2 chained monitors waking up in random order. May have reported this earlier myself. Details to be filled later. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass Date: Thu Sep 21 20:20:00 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Very infrequently GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1462:3822] InstallationDate: Installed on 2022-04-27 (512 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-31-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2036998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037012] Re: package bluez 5.53-0ubuntu3.6 failed to install/upgrade: el subproceso instalado paquete bluez script post-installation devolvió el código de salida de error 1 [Fai
** Summary changed: - package bluez 5.53-0ubuntu3.6 failed to install/upgrade: el subproceso instalado paquete bluez script post-installation devolvió el código de salida de error 1 + package bluez 5.53-0ubuntu3.6 failed to install/upgrade: el subproceso instalado paquete bluez script post-installation devolvió el código de salida de error 1 [Failed to restart bluetooth.service: Unit bluetooth.service failed to load properly: File exists.] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037012 Title: package bluez 5.53-0ubuntu3.6 failed to install/upgrade: el subproceso instalado paquete bluez script post-installation devolvió el código de salida de error 1 [Failed to restart bluetooth.service: Unit bluetooth.service failed to load properly: File exists.] Status in bluez package in Ubuntu: New Bug description: no se está ejecutando el sevico Bluez ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.15.0-84.93~20.04.1-generic 5.15.116 Uname: Linux 5.15.0-84-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Sep 21 13:30:47 2023 ErrorMessage: el subproceso instalado paquete bluez script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2023-09-18 (2 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) InterestingModules: bluetooth MachineType: Hewlett-Packard HP Pavilion dv4 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=UUID=e02ac370-977e-4bed-840d-5a24e2e5b288 ro quiet splash vt.handoff=7 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: bluez Title: package bluez 5.53-0ubuntu3.6 failed to install/upgrade: el subproceso instalado paquete bluez script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 30F7 dmi.board.vendor: Compal dmi.board.version: 99.80 dmi.chassis.type: 10 dmi.chassis.vendor: Compal dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.22:bd10/17/2008:svnHewlett-Packard:pnHPPaviliondv4NotebookPC:pvrF.22:rvnCompal:rn30F7:rvr99.80:cvnCompal:ct10:cvrN/A:skuFR922UA#ABA: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion dv4 Notebook PC dmi.product.sku: FR922UA#ABA dmi.product.version: F.22 dmi.sys.vendor: Hewlett-Packard hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037012/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036998] [NEW] [amdgpu] Oops in dm_helpers_dp_mst_send_payload_allocation+0x90/0xd0 [amdgpu]
You have been subscribed to a public bug: Amdgpu tends to freeze on resume with DP1.2 chained monitors waking up in random order. May have reported this earlier myself. Details to be filled later. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass Date: Thu Sep 21 20:20:00 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Very infrequently GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1462:3822] InstallationDate: Installed on 2022-04-27 (512 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-31-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: linux-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 amdgpu apport-bug freeze jammy ubuntu -- [amdgpu] Oops in dm_helpers_dp_mst_send_payload_allocation+0x90/0xd0 [amdgpu] https://bugs.launchpad.net/bugs/2036998 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 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 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
This seems like a significant enhancement that will affect the graphics backends chosen by Plymouth and some desktop sessions, particularly virtual machines. Surely this needs a feature freeze exception? -- 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/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer Status in gdm: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in gdm3 source package in Jammy: In Progress Status in linux source package in Jammy: Won't Fix Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in gdm3 source package in Mantic: Fix Released Status in linux source package in Mantic: Confirmed Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Status in linux package in Fedora: Fix Released Bug description: [ Impact ] The fbdev subsystem has been deprecated for a long time. We should drop it in favour of using simpledrm with fbdev emulation layer. This requires Kernel config changes: FB_EFI=n FB_VESA=n fbcon will still require FB to be available, but will use the fbdev emulation layer When this stack is enabled, it changes boot timing such that some drivers may take a longer time to boot and GDM may hang in a black screen. This issue has been readily reproduced in Ubuntu and reported to upstream mutter. https://gitlab.gnome.org/GNOME/mutter/-/issues/2909 [ Test Plan ] * Ensure that a kernel with required kernel changes can boot to GDM using DRM driver (amdgpu, i915, or nouveau) [ Where Problems could occur ] * Race conditions could be exposed to DE environments * Software that expects to find DRM device at /dev/dri/card0 may have a problem. * Some older versions of NVIDIA driver might not work properly. [ Other Info ] * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025079] Re: [amdgpu] Multiple kernel errors and reboot
Vincent, please log your own bug by running: ubuntu-bug linux -- 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/2025079 Title: [amdgpu] Multiple kernel errors and reboot Status in linux package in Ubuntu: Confirmed Bug description: Preconditions: - Connect external monitor (not sure if necessary) - Have a Google Chrome o Microsoft Edge installed (did not test it with Chromium and Firefox) - Have access to at least 2 Gmail accounts to be able to use Meet (did not yet experience it with other videoconference systems) Steps to reproduce: - have a Google Meet call with someone else (does not reproduce when only I join the meeting) - click share the screen - select entire monitor - select external monitor - [new] press "Super" key to open Activities overview. Might need to rty it 2-3 times Symptomps: - Entire Wayland session freezes and after few stutters the entire system reboots Does not reproduce after uncommenting WaylandEnable=false in /etc/gdm3/custom.conf. Pretty certain that amdgpu is the culprit as never experienced this on Intel/Nvidia. Attached journal from the boot that ended in system crash. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 26 17:57:32 2023 InstallationDate: Installed on 2023-04-13 (74 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: mutter UpgradeStatus: Upgraded to lunar on 2023-04-21 (65 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-04-13 (145 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5415 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-32-generic N/A linux-backports-modules-6.2.0-32-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 Tags: lunar wayland-session Uname: Linux 6.2.0-32-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-21 (137 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/13/2023 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0WKFHK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.15.0 dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd02/13/2023:br1.15:svnDellInc.:pnInspiron5415:pvr1.15.0:rvnDellInc.:rn0WKFHK:rvrA00:cvnDellInc.:ct10:cvr1.15.0:sku0A77: dmi.product.family: Inspiron dmi.product.name: Inspiron 5415 dmi.product.sku: 0A77 dmi.product.version: 1.15.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025079/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036802] Re: HDMI not detected on HP Zbook Power 15 G9
It looks like the Intel GPU exists but is disabled. And that both the laptop screen and the external monitor are wired to the Nvidia GPU... unless you have more than one external monitor attached? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2036802 Title: HDMI not detected on HP Zbook Power 15 G9 Status in linux-hwe-6.2 package in Ubuntu: Incomplete Bug description: As discussed in this thread: https://gitlab.freedesktop.org/drm/intel/-/issues/8601#note_2092811 On my laptop, HP Zbook Power 15 G9 (i7-12800H), HDMI is not detected. According to the discussion a fix has been implemented in kernel v6.6-rc1. If it's possible for Ubuntu to implement some fix in the current LTS version that would be MUCH helpful and appreciated for me and all other ubuntu users on the same laptop. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.104.05 Sat Aug 19 01:15:15 UTC 2023 GCC version: gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 20 19:25:44 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: evdi/1.14.1, 6.2.0-32-generic, x86_64: installed evdi/1.14.1, 6.2.0-33-generic, x86_64: installed nvidia/535.104.05, 6.2.0-32-generic, x86_64: installed nvidia/535.104.05, 6.2.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:89c0] Subsystem: Hewlett-Packard Company Device [103c:89c1] InstallationDate: Installed on 2023-08-21 (29 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: HP HP ZBook Power 15.6 inch G9 Mobile Workstation PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic root=UUID=8a70988e-02bd-462a-b919-7e3ff4500355 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2023 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: U97 Ver. 01.08.00 dmi.board.name: 89C0 dmi.board.vendor: HP dmi.board.version: KBC Version 11.63.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 17.99 dmi.modalias: dmi:bvnHP:bvrU97Ver.01.08.00:bd06/26/2023:br8.0:efr17.99:svnHP:pnHPZBookPower15.6inchG9MobileWorkstationPC:pvr:rvnHP:rn89C0:rvrKBCVersion11.63.00:cvnHP:ct10:cvr:sku6B867EA#UUW: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Power 15.6 inch G9 Mobile Workstation PC dmi.product.sku: 6B867EA#UUW dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2036802/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031969] Re: Ubuntu 22.04.3 LTS stuck on power-off/reboot screen
This bug also affects other users, as described in: https://askubuntu.com/questions/1482315/ubuntu-22-04-03-lts-stuck-on-power-off-reboot-screen https://askubuntu.com/questions/1426205/ubuntu-22-04-stuck-at-shutdown Furthermore, this issue is not a duplicate of the following: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2031352 https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2029332 Also in Fedora with Kernel 6.1.X https://discussion.fedoraproject.org/t/shutdown-reboot-broken-in-f37-since-kernel-6-1-x/79944 ** Description changed: - Since update to version 23.04 I am facing several problems related to - system suspend and shutdown on a HP Envy 15 notebook (2016). The system - refuses to wake up from standby mode, especially if it has run for a - longer time. Screen is black, no response to keyboard or trackpad - actions, Power button led is on. The only way out of here is a long - press on power button. + Since I updated to version 23.04 I am facing several problems related to + system suspend and shutdown. The system refuses to wake up from standby + mode, especially if it has run for a longer time. Screen is black, no + response to keyboard or trackpad actions, Power button led is on. The + only way out of here is a long press on the power button. - Another problem with this and I think it's kind of related. If you want - to shut down the computer after a long runtime, the machine won't power - off. In the logs you can see the steps for shutting down the OS but in - the end the machine stays powered on. The power led is on, screen is - black, no response to keyboard or trackpad actions. System has to be - powered off by a long press on the power button. + Another issue with this, and I think it's related. If you want to shut + down the computer after a long runtime, the machine won't power off. In + the logs you can see the steps for shutting down the OS, but eventually + the machine stays powered on. The power lead is on, the screen is black, + no response to keyboard or trackpad actions. System has to be powered + off by a long press on the power button. Ubuntu 6.2.0-27.28-generic 6.2.15 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-27-generic 6.2.0-27.28 ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: tom2051 F wireplumber - /dev/snd/seq:tom2037 F pipewire + USERPID ACCESS COMMAND + /dev/snd/controlC0: tom2051 F wireplumber + /dev/snd/seq:tom2037 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Aug 19 16:01:07 2023 InstallationDate: Installed on 2018-07-01 (1875 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface - Bus 001 Device 002: ID 04f2:b56d Chicony Electronics Co., Ltd HP Wide Vision HD - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface + Bus 001 Device 002: ID 04f2:b56d Chicony Electronics Co., Ltd HP Wide Vision HD + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY Notebook ProcEnviron: - LANG=de_DE.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - TERM=xterm-256color - XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color + XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-27-generic root=UUID=1e8886f5-f232-49b1-af56-f83caee82bba ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: - linux-restricted-modules-6.2.0-27-generic N/A - linux-backports-modules-6.2.0-27-generic N/A - linux-firmware20230323.gitbcdcfbcf-0ubuntu1.5 + linux-restricted-modules-6.2.0-27-generic N/A + linux-backports-modules-6.2.0-27-generic N/A + linux-firmware20230323.gitbcdcfbcf-0ubuntu1.5 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-05-01 (109 days ago) dmi.bios.date: 11/10/2020 dmi.bios.release: 15.62 dmi.bios.vendor: Insyde dmi.bios.version: F.62 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81D2 dmi.board.vendor: HP dmi.board.version: KBC Version 87.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 87.21 dmi.modalias:
[Kernel-packages] [Bug 2031969] Re: Ubuntu 22.04.3 LTS stuck on power-off/reboot screen
I also have the same problem. After updating to Kernel 6.2 a few days ago, I have been experiencing issues with my system's shutdown and reboot functions. During these processes, the system becomes unresponsive and hangs on a black screen, which displays both the Dell and Ubuntu logos. This issue is inconsistent; it happens sporadically. Currently, the only workaround I've found to successfully shut down the system is to forcibly power off the machine by holding down the power button for 5 seconds. I've also tested a fresh installation of Ubuntu 22.04.3. I have a Dell Machine XPS 8930. And I do not use the "Nouveau driver" as described in a similar bug in: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2031352 I reported this bug at https://bugs.launchpad.net/ubuntu/+source/linux- hwe-6.2/+bug/2031352, but the bug was mistakenly changed to look like it is a bug with the Nouveau drivers. So the issue was not fixed. I have attached the last shutdown logs > journalctl -b -1 --since "1 hour ago" > shutdown.txt ** Attachment added: "shutdown.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031969/+attachment/5703374/+files/shutdown.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2031969 Title: Ubuntu 22.04.3 LTS stuck on power-off/reboot screen Status in linux package in Ubuntu: Confirmed Bug description: Since I updated to version 23.04 I am facing several problems related to system suspend and shutdown. The system refuses to wake up from standby mode, especially if it has run for a longer time. Screen is black, no response to keyboard or trackpad actions, Power button led is on. The only way out of here is a long press on the power button. Another issue with this, and I think it's related. If you want to shut down the computer after a long runtime, the machine won't power off. In the logs you can see the steps for shutting down the OS, but eventually the machine stays powered on. The power lead is on, the screen is black, no response to keyboard or trackpad actions. System has to be powered off by a long press on the power button. Ubuntu 6.2.0-27.28-generic 6.2.15 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-27-generic 6.2.0-27.28 ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom2051 F wireplumber /dev/snd/seq:tom2037 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Aug 19 16:01:07 2023 InstallationDate: Installed on 2018-07-01 (1875 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b56d Chicony Electronics Co., Ltd HP Wide Vision HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY Notebook ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-27-generic root=UUID=1e8886f5-f232-49b1-af56-f83caee82bba ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-27-generic N/A linux-backports-modules-6.2.0-27-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.5 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-05-01 (109 days ago) dmi.bios.date: 11/10/2020 dmi.bios.release: 15.62 dmi.bios.vendor: Insyde dmi.bios.version: F.62 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81D2 dmi.board.vendor: HP dmi.board.version: KBC Version 87.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 87.21 dmi.modalias: dmi:bvnInsyde:bvrF.62:bd11/10/2020:br15.62:efr87.21:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81D2:rvrKBCVersion87.21:cvnHP:ct10:cvrChassisVersion:skuZ6J78EA#ABD: dmi.product.family: 103C_5335KV dmi.product.name: HP ENVY Notebook dmi.product.sku: Z6J78EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1970066] Re: (Encrypted) ZFS breaks 22.04 installation
** Changed in: zfs-linux (Ubuntu Jammy) Milestone: ubuntu-22.04.3 => ubuntu-22.04.4 -- 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/1970066 Title: (Encrypted) ZFS breaks 22.04 installation Status in snapd package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Status in snapd source package in Jammy: Confirmed Status in zfs-linux source package in Jammy: Confirmed Bug description: On a freshly installed 22.04.0 amd64 Desktop with (encrypted) ZFS, removing the Firefox snap breaks: * the current gnome-shell session - it returns to gdm3 login prompt * snapd - all snaps are marked 'broken' * dpkg - dpkg status database is lost Reproducible on dedicated hardware and VMs. Not reproducible on a default (/ on ext4) installation. Video showing the whole process on a freshly installed system: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1970066/+attachment/5583102/+files/1970066.webm journalctl -b output: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1970066/+attachment/5583100/+files/1970066_journal.txt /proc/self/mountinfo: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1970066/+attachment/5583101/+files/1970066_mountinfo.txt Installation procedure: - Minimal installation - Tick 'download updates' - Tick 'install third party software' - Erase disk and use ZFS + encrypt - Require password to log in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1970066/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031969] Re: Ubuntu 22.04.3 LTS stuck on power-off/reboot screen
** Summary changed: - Ubuntu 23.04: Suspend & Power off + Ubuntu 22.04.3 LTS stuck on power-off/reboot screen -- 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/2031969 Title: Ubuntu 22.04.3 LTS stuck on power-off/reboot screen Status in linux package in Ubuntu: Confirmed Bug description: Since update to version 23.04 I am facing several problems related to system suspend and shutdown on a HP Envy 15 notebook (2016). The system refuses to wake up from standby mode, especially if it has run for a longer time. Screen is black, no response to keyboard or trackpad actions, Power button led is on. The only way out of here is a long press on power button. Another problem with this and I think it's kind of related. If you want to shut down the computer after a long runtime, the machine won't power off. In the logs you can see the steps for shutting down the OS but in the end the machine stays powered on. The power led is on, screen is black, no response to keyboard or trackpad actions. System has to be powered off by a long press on the power button. Ubuntu 6.2.0-27.28-generic 6.2.15 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-27-generic 6.2.0-27.28 ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom2051 F wireplumber /dev/snd/seq:tom2037 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Aug 19 16:01:07 2023 InstallationDate: Installed on 2018-07-01 (1875 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b56d Chicony Electronics Co., Ltd HP Wide Vision HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY Notebook ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-27-generic root=UUID=1e8886f5-f232-49b1-af56-f83caee82bba ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-27-generic N/A linux-backports-modules-6.2.0-27-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.5 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-05-01 (109 days ago) dmi.bios.date: 11/10/2020 dmi.bios.release: 15.62 dmi.bios.vendor: Insyde dmi.bios.version: F.62 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81D2 dmi.board.vendor: HP dmi.board.version: KBC Version 87.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 87.21 dmi.modalias: dmi:bvnInsyde:bvrF.62:bd11/10/2020:br15.62:efr87.21:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81D2:rvrKBCVersion87.21:cvnHP:ct10:cvrChassisVersion:skuZ6J78EA#ABD: dmi.product.family: 103C_5335KV dmi.product.name: HP ENVY Notebook dmi.product.sku: Z6J78EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970066] Re: (Encrypted) ZFS breaks 22.04 installation
** Changed in: zfs-linux (Ubuntu Jammy) Milestone: None => ubuntu-22.04.3 -- 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/1970066 Title: (Encrypted) ZFS breaks 22.04 installation Status in snapd package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Status in snapd source package in Jammy: Confirmed Status in zfs-linux source package in Jammy: Confirmed Bug description: On a freshly installed 22.04.0 amd64 Desktop with (encrypted) ZFS, removing the Firefox snap breaks: * the current gnome-shell session - it returns to gdm3 login prompt * snapd - all snaps are marked 'broken' * dpkg - dpkg status database is lost Reproducible on dedicated hardware and VMs. Not reproducible on a default (/ on ext4) installation. Video showing the whole process on a freshly installed system: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1970066/+attachment/5583102/+files/1970066.webm journalctl -b output: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1970066/+attachment/5583100/+files/1970066_journal.txt /proc/self/mountinfo: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1970066/+attachment/5583101/+files/1970066_mountinfo.txt Installation procedure: - Minimal installation - Tick 'download updates' - Tick 'install third party software' - Erase disk and use ZFS + encrypt - Require password to log in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1970066/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes
** Changed in: ubuntu-manual-tests Status: New => Triaged ** Changed in: ubuntu-manual-tests Importance: Undecided => High ** Changed in: ubuntu-manual-tests Assignee: (unassigned) => Tim Andersson (andersson123) -- 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/1993318 Title: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes Status in Ubuntu Manual Tests: Triaged Status in Release Notes for Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Status in ubiquity source package in Jammy: Fix Released Bug description: This is *probably* the wrong package, but it's the best I can figure for this, so here goes. Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM, 50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO. [Testcase] tl;dr encrypted-zfs, firstboot, `systemctl daemon-reload` must not unmount half of mountpoints, ie. /var/lib. Steps to reproduce: 1. Boot the Ubuntu desktop ISO. 2. Select "Install Ubuntu" and proceed with the installation process. 3. When you get to the "Installation type" screen, select "Advanced Options", and enable ZFS + Encryption. 4. Proceed with the rest of the installation as normal. 5. Reboot into the newly installed system. 6. Log in. 7. Run "sudo apt update" in a terminal. Expected result: The package database should be updated normally. Actual result: You are presented with the following errors at the end of the apt output: Reading package lists... Error! E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory) E: Could not open file - open (2: No such file or directory) E: Problem opening E: The package lists or status file could not be parsed or opened. Notes: Switching to a TTY will print a crash error message related to the same missing /var/lib/dpkg/status file. Running "sudo touch /var/lib/dpkg/status" will allow "sudo apt update" to function and fix the crashed process in the TTY. [End Testcase] Once you log in, you'll notice that Firefox is missing (bug #1993279), and you will likely be presented with a ton of error messages and other scary junk. At least one of those error messages was related to update-manager in my experience, and another one was from "check-new- release-gtk". ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 18 09:55:27 2022 InstallationDate: Installed on 2022-10-18 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1993318/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037014] [NEW] HDMI audio noisy
Public bug reported: After updating to the latest kernel ???-33, and setting the audio hardware to HDMI, playing any YouTube video is filled with noise. Rebooting to the previous kernel eliminated the noise. Please fix what the update broke. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Thu Sep 21 16:33:23 2023 InstallationDate: Installed on 2022-03-05 (565 days ago) InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2023-01-15 (249 days ago) ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2037014 Title: HDMI audio noisy Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: After updating to the latest kernel ???-33, and setting the audio hardware to HDMI, playing any YouTube video is filled with noise. Rebooting to the previous kernel eliminated the noise. Please fix what the update broke. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Thu Sep 21 16:33:23 2023 InstallationDate: Installed on 2022-03-05 (565 days ago) InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2023-01-15 (249 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2037014/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032535] Re: [Google_Puff] Screen blank crashes system
I went back to confirm the problem on other systems. Despite what I wrote before, Ubuntu 22.04.3 does crash when sleeping. My first post stands as correct. Also, I tried Debian 12 with gnome and wayland. That system does not crash - and it has a very similar look and feel to 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/2032535 Title: [Google_Puff] Screen blank crashes system Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 23.04 screen blank crashes system. Not a sleep problem, I can enter and resume from S2idle, S2ram. (Using command line or Power/Suspend GUI) However, when screen blanks, computer has a hard crash. Just rebooting with power button may not work (operating system not found error) I have to unplug the computer and plug it back in again to reboot properly. I would just turn off screen sleep, but when the S2ram suspend mode engages it often, but not always, crashes as well. I've tried live disks with other OS, and this is not a problem on Linux Mint 21.2, nor on Xubuntu 23.04.Windows 10 works too. I tried Ubuntu 22.04 and it also crashed - using either gnome or wayland. I'm happy to help debug, but I'm not a developer. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 21 15:11:21 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] InstallationDate: Installed on 2023-06-13 (69 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: Google Noibat ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-27-generic root=UUID=77b0ab13-596d-4e94-8648-e6aeda300b7a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2023 dmi.bios.release: 4.20 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.20.0 dmi.board.name: Noibat dmi.board.vendor: HP dmi.board.version: rev4 dmi.chassis.type: 3 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.20.0:bd05/15/2023:br4.20:efr0.0:svnGoogle:pnNoibat:pvrrev4:rvnHP:rnNoibat:rvrrev4:cvnGoogle:ct3:cvr:skusku83886080: dmi.product.family: Google_Puff dmi.product.name: Noibat dmi.product.sku: sku83886080 dmi.product.version: rev4 dmi.sys.vendor: Google version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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/2032535/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037012] [NEW] package bluez 5.53-0ubuntu3.6 failed to install/upgrade: el subproceso instalado paquete bluez script post-installation devolvió el código de salida de error 1
Public bug reported: no se está ejecutando el sevico Bluez ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.15.0-84.93~20.04.1-generic 5.15.116 Uname: Linux 5.15.0-84-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Sep 21 13:30:47 2023 ErrorMessage: el subproceso instalado paquete bluez script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2023-09-18 (2 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) InterestingModules: bluetooth MachineType: Hewlett-Packard HP Pavilion dv4 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=UUID=e02ac370-977e-4bed-840d-5a24e2e5b288 ro quiet splash vt.handoff=7 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: bluez Title: package bluez 5.53-0ubuntu3.6 failed to install/upgrade: el subproceso instalado paquete bluez script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 30F7 dmi.board.vendor: Compal dmi.board.version: 99.80 dmi.chassis.type: 10 dmi.chassis.vendor: Compal dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.22:bd10/17/2008:svnHewlett-Packard:pnHPPaviliondv4NotebookPC:pvrF.22:rvnCompal:rn30F7:rvr99.80:cvnCompal:ct10:cvrN/A:skuFR922UA#ABA: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion dv4 Notebook PC dmi.product.sku: FR922UA#ABA dmi.product.version: F.22 dmi.sys.vendor: Hewlett-Packard hciconfig: ** Affects: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037012 Title: package bluez 5.53-0ubuntu3.6 failed to install/upgrade: el subproceso instalado paquete bluez script post-installation devolvió el código de salida de error 1 Status in bluez package in Ubuntu: New Bug description: no se está ejecutando el sevico Bluez ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.15.0-84.93~20.04.1-generic 5.15.116 Uname: Linux 5.15.0-84-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Sep 21 13:30:47 2023 ErrorMessage: el subproceso instalado paquete bluez script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2023-09-18 (2 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) InterestingModules: bluetooth MachineType: Hewlett-Packard HP Pavilion dv4 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=UUID=e02ac370-977e-4bed-840d-5a24e2e5b288 ro quiet splash vt.handoff=7 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: bluez Title: package bluez 5.53-0ubuntu3.6 failed to install/upgrade: el subproceso instalado paquete bluez script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 30F7 dmi.board.vendor: Compal dmi.board.version: 99.80 dmi.chassis.type: 10 dmi.chassis.vendor: Compal dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.22:bd10/17/2008:svnHewlett-Packard:pnHPPaviliondv4NotebookPC:pvrF.22:rvnCompal:rn30F7:rvr99.80:cvnCompal:ct10:cvrN/A:skuFR922UA#ABA: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion dv4 Notebook PC dmi.product.sku: FR922UA#ABA dmi.product.version: F.22 dmi.sys.vendor: Hewlett-Packard hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037012/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964916] Re: [HP Omni 120-2110il AIO] Flickering white lines on screen
I reported the issue to intel/freedesktop and was fixed https://gitlab.freedesktop.org/drm/intel/-/issues/8895#note_2005508, I guess it will be included in the next kernel version. ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #8895 https://gitlab.freedesktop.org/drm/intel/-/issues/8895 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1964916 Title: [HP Omni 120-2110il AIO] Flickering white lines on screen Status in linux-hwe-5.11 package in Ubuntu: Confirmed Bug description: https://www.youtube.com/watch?v=GcAXAicoZqY this is the video of my error i am having this issue on all versions of ubuntu-- i have tried installing versions 20.04, 18.04.06, 12.04.. i have intel pentium g630 processor with intel graphics 2000 (Vram-256M). I used Windows 10 on my PC but i thought of switching to ubuntu when this problem arose.. The glitch shows up on ubuntu splash screen and remains there until i restart my pc with nomodeset parameter...i have reinstalled windows 10 but i want this issue to get fixed.. i need to use ubuntu ...pls ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 14:59:57 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:2ac5] InstallationDate: Installed on 2022-03-05 (9 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Hewlett-Packard 120-2110il ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=54d1c05e-a544-4510-8da7-87e1a7242e0f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/17/2011 dmi.bios.release: 4.6 dmi.bios.vendor: AMI dmi.bios.version: LEO_707 dmi.board.name: 2AC5 dmi.board.vendor: Quanta dmi.board.version: 101 dmi.chassis.asset.tag: 4CS2040B0F dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvrLEO_707:bd11/17/2011:br4.6:svnHewlett-Packard:pn120-2110il:pvr:rvnQuanta:rn2AC5:rvr101:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: 120-2110il dmi.product.sku: QF135AA#ACJ dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1964916/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000228] Please test proposed package
Hello ethan.hsieh, or anyone else affected, Accepted alsa-ucm-conf into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa-ucm- conf/1.2.6.3-1ubuntu1.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2000228 Title: [SRU] Add initial support for Mediatek Genio boards Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: Fix Committed Status in alsa-ucm-conf source package in Lunar: Fix Committed Bug description: [Impact] Add initial support for Mediatek Genio boards (mt8365-evk, mt8390-evk, and mt8395-evk) mt8365-evk: https://github.com/alsa-project/alsa-ucm-conf/commit/2f8027349c37044e15c694c6df4d62d622e20886 mt8390-evk (G700): (Still under review) https://github.com/alsa-project/alsa-ucm-conf/pull/321 mt8395-evk (G1200): (Still under review) https://github.com/alsa-project/alsa-ucm-conf/pull/322 [Where problems could occur] Audio function doesn't work on Mediatek Genio boards. mantic: mt8390-evk, and mt8395-evk lunar/jammy: mt8365-evk, mt8390-evk, and mt8395-evk [Test Case] Verify audio function on Mediatek Genio boards (mt8365-evk, mt8390-evk, and mt8395-evk). 1. Headset Jack Playback 2. Audio (Speaker) Jack Playback 3. HDMI Playback Play audio by following commands. $ speaker-test -D pulse -c 2 -r 48000 -f S16_LE -t wav [Regression Potential] Add initial support for Mediatek Genio boards. There should be no risk. mantic: mt8390-evk, and mt8395-evk lunar/jammy: mt8365-evk, mt8390-evk, and mt8395-evk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2000228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000228] Re: [SRU] Add initial support for Mediatek Genio boards
Hello ethan.hsieh, or anyone else affected, Accepted alsa-ucm-conf into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa-ucm- conf/1.2.6.3-1ubuntu9.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: alsa-ucm-conf (Ubuntu Lunar) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-lunar ** Changed in: alsa-ucm-conf (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2000228 Title: [SRU] Add initial support for Mediatek Genio boards Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: Fix Committed Status in alsa-ucm-conf source package in Lunar: Fix Committed Bug description: [Impact] Add initial support for Mediatek Genio boards (mt8365-evk, mt8390-evk, and mt8395-evk) mt8365-evk: https://github.com/alsa-project/alsa-ucm-conf/commit/2f8027349c37044e15c694c6df4d62d622e20886 mt8390-evk (G700): (Still under review) https://github.com/alsa-project/alsa-ucm-conf/pull/321 mt8395-evk (G1200): (Still under review) https://github.com/alsa-project/alsa-ucm-conf/pull/322 [Where problems could occur] Audio function doesn't work on Mediatek Genio boards. mantic: mt8390-evk, and mt8395-evk lunar/jammy: mt8365-evk, mt8390-evk, and mt8395-evk [Test Case] Verify audio function on Mediatek Genio boards (mt8365-evk, mt8390-evk, and mt8395-evk). 1. Headset Jack Playback 2. Audio (Speaker) Jack Playback 3. HDMI Playback Play audio by following commands. $ speaker-test -D pulse -c 2 -r 48000 -f S16_LE -t wav [Regression Potential] Add initial support for Mediatek Genio boards. There should be no risk. mantic: mt8390-evk, and mt8395-evk lunar/jammy: mt8365-evk, mt8390-evk, and mt8395-evk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2000228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978079] Re: EFI pstore not cleared on boot
This bug was fixed in the package linux-bluefield - 5.4.0-1070.76
---
linux-bluefield (5.4.0-1070.76) focal; urgency=medium
* focal/linux-bluefield: 5.4.0-1070.76 -proposed tracker (LP:
#2030986)
* EFI pstore not cleared on boot (LP: #1978079)
- [Config] bluefield: Enable CONFIG_EFI_VARS_PSTORE as build-in
- [Config] bluefield: Remove efi-pstore from modules list
* Focal update: v5.4.246 upstream stable release (LP: #2028981)
- [Config] bluefield: updateconfigs for SCSI_DPT_I2O
- SAUCE: xfrm: Check if_id in xfrm full offload
* rshim console truncates dmesg output due to tmfifo issue (LP: #2028197)
- SAUCE: mlxbf-tmfifo.c: Fix rhsim console w/ truncated dmesg output
* mlxbf-gige: Fix kernel panic after reboot (LP: #2030765)
- SAUCE: mlxbf-gige: Fix kernel panic after reboot (part 1/2)
- SAUCE: mlxbf-gige: Fix kernel panic after reboot (part 2/2)
[ Ubuntu: 5.4.0-162.179 ]
* focal/linux: 5.4.0-162.179 -proposed tracker (LP: #2031128)
* libgnutls report "trap invalid opcode" when trying to install packages over
https (LP: #2031093)
- [Config]: disable CONFIG_GDS_FORCE_MITIGATION
[ Ubuntu: 5.4.0-160.177 ]
* focal/linux: 5.4.0-160.177 -proposed tracker (LP: #2031017)
* Fix boot test warning for log_check "CPU: 0 PID: 0 at
arch/x86/kernel/fpu/xstate.c:878 get_xsave_addr+0x98/0xb0" (LP: #2031022)
- x86/pkeys: Revert a5eff7259790 ("x86/pkeys: Add PKRU value to
init_fpstate")
[ Ubuntu: 5.4.0-158.175 ]
* focal/linux: 5.4.0-158.175 -proposed tracker (LP: #2030466)
* CVE-2022-40982
- x86/mm: Initialize text poking earlier
- x86/mm: fix poking_init() for Xen PV guests
- x86/mm: Use mm_alloc() in poking_init()
- mm: Move mm_cachep initialization to mm_init()
- init: Provide arch_cpu_finalize_init()
- x86/cpu: Switch to arch_cpu_finalize_init()
- ARM: cpu: Switch to arch_cpu_finalize_init()
- sparc/cpu: Switch to arch_cpu_finalize_init()
- um/cpu: Switch to arch_cpu_finalize_init()
- init: Remove check_bugs() leftovers
- init: Invoke arch_cpu_finalize_init() earlier
- init, x86: Move mem_encrypt_init() into arch_cpu_finalize_init()
- x86/fpu: Remove cpuinfo argument from init functions
- x86/fpu: Mark init functions __init
- x86/fpu: Move FPU initialization into arch_cpu_finalize_init()
- x86/xen: Fix secondary processors' FPU initialization
- x86/speculation: Add Gather Data Sampling mitigation
- x86/speculation: Add force option to GDS mitigation
- x86/speculation: Add Kconfig option for GDS
- KVM: Add GDS_NO support to KVM
- Documentation/x86: Fix backwards on/off logic about YMM support
- [Config]: Enable CONFIG_ARCH_HAS_CPU_FINALIZE_INIT and
CONFIG_GDS_FORCE_MITIGATION
* CVE-2023-3609
- net/sched: cls_u32: Fix reference counter leak leading to overflow
* CVE-2023-20593
- x86/cpu/amd: Move the errata checking functionality up
- x86/cpu/amd: Add a Zenbleed fix
* CVE-2023-3611
- net/sched: sch_qfq: account for stab overhead in qfq_enqueue
* stacked overlay file system mounts that have chroot() called against them
appear to be getting locked (by the kernel most likely?) (LP: #2016398)
- SAUCE: overlayfs: fix reference count mismatch
* Focal update: v5.4.246 upstream stable release (LP: #2028981)
- RDMA/efa: Fix unsupported page sizes in device
- RDMA/bnxt_re: Enable SRIOV VF support on Broadcom's 57500 adapter series
- RDMA/bnxt_re: Refactor queue pair creation code
- RDMA/bnxt_re: Fix return value of bnxt_re_process_raw_qp_pkt_rx
- iommu/rockchip: Fix unwind goto issue
- iommu/amd: Don't block updates to GATag if guest mode is on
- dmaengine: pl330: rename _start to prevent build error
- net/mlx5: fw_tracer, Fix event handling
- netrom: fix info-leak in nr_write_internal()
- af_packet: Fix data-races of pkt_sk(sk)->num.
- amd-xgbe: fix the false linkup in xgbe_phy_status
- mtd: rawnand: ingenic: fix empty stub helper definitions
- af_packet: do not use READ_ONCE() in packet_bind()
- tcp: deny tcp_disconnect() when threads are waiting
- tcp: Return user_mss for TCP_MAXSEG in CLOSE/LISTEN state if user_mss set
- net/sched: sch_ingress: Only create under TC_H_INGRESS
- net/sched: sch_clsact: Only create under TC_H_CLSACT
- net/sched: Reserve TC_H_INGRESS (TC_H_CLSACT) for ingress (clsact) Qdiscs
- net/sched: Prohibit regrafting ingress or clsact Qdiscs
- net: sched: fix NULL pointer dereference in mq_attach
- ocfs2/dlm: move BITS_TO_BYTES() to bitops.h for wider use
- net/netlink: fix NETLINK_LIST_MEMBERSHIPS length report
- udp6: Fix race condition in udp6_sendmsg & connect
- net: dsa: mv88e6xxx: Increase wait after reset deactivation
- mtd: rawnand: marvell: ensure timing values are written
- mtd: rawnand: marvell: don't set the NAND frequency select
- watchdog: menz069_wdt: fix watchdog
[Kernel-packages] [Bug 2028197] Re: rshim console truncates dmesg output due to tmfifo issue
This bug was fixed in the package linux-bluefield - 5.4.0-1070.76
---
linux-bluefield (5.4.0-1070.76) focal; urgency=medium
* focal/linux-bluefield: 5.4.0-1070.76 -proposed tracker (LP:
#2030986)
* EFI pstore not cleared on boot (LP: #1978079)
- [Config] bluefield: Enable CONFIG_EFI_VARS_PSTORE as build-in
- [Config] bluefield: Remove efi-pstore from modules list
* Focal update: v5.4.246 upstream stable release (LP: #2028981)
- [Config] bluefield: updateconfigs for SCSI_DPT_I2O
- SAUCE: xfrm: Check if_id in xfrm full offload
* rshim console truncates dmesg output due to tmfifo issue (LP: #2028197)
- SAUCE: mlxbf-tmfifo.c: Fix rhsim console w/ truncated dmesg output
* mlxbf-gige: Fix kernel panic after reboot (LP: #2030765)
- SAUCE: mlxbf-gige: Fix kernel panic after reboot (part 1/2)
- SAUCE: mlxbf-gige: Fix kernel panic after reboot (part 2/2)
[ Ubuntu: 5.4.0-162.179 ]
* focal/linux: 5.4.0-162.179 -proposed tracker (LP: #2031128)
* libgnutls report "trap invalid opcode" when trying to install packages over
https (LP: #2031093)
- [Config]: disable CONFIG_GDS_FORCE_MITIGATION
[ Ubuntu: 5.4.0-160.177 ]
* focal/linux: 5.4.0-160.177 -proposed tracker (LP: #2031017)
* Fix boot test warning for log_check "CPU: 0 PID: 0 at
arch/x86/kernel/fpu/xstate.c:878 get_xsave_addr+0x98/0xb0" (LP: #2031022)
- x86/pkeys: Revert a5eff7259790 ("x86/pkeys: Add PKRU value to
init_fpstate")
[ Ubuntu: 5.4.0-158.175 ]
* focal/linux: 5.4.0-158.175 -proposed tracker (LP: #2030466)
* CVE-2022-40982
- x86/mm: Initialize text poking earlier
- x86/mm: fix poking_init() for Xen PV guests
- x86/mm: Use mm_alloc() in poking_init()
- mm: Move mm_cachep initialization to mm_init()
- init: Provide arch_cpu_finalize_init()
- x86/cpu: Switch to arch_cpu_finalize_init()
- ARM: cpu: Switch to arch_cpu_finalize_init()
- sparc/cpu: Switch to arch_cpu_finalize_init()
- um/cpu: Switch to arch_cpu_finalize_init()
- init: Remove check_bugs() leftovers
- init: Invoke arch_cpu_finalize_init() earlier
- init, x86: Move mem_encrypt_init() into arch_cpu_finalize_init()
- x86/fpu: Remove cpuinfo argument from init functions
- x86/fpu: Mark init functions __init
- x86/fpu: Move FPU initialization into arch_cpu_finalize_init()
- x86/xen: Fix secondary processors' FPU initialization
- x86/speculation: Add Gather Data Sampling mitigation
- x86/speculation: Add force option to GDS mitigation
- x86/speculation: Add Kconfig option for GDS
- KVM: Add GDS_NO support to KVM
- Documentation/x86: Fix backwards on/off logic about YMM support
- [Config]: Enable CONFIG_ARCH_HAS_CPU_FINALIZE_INIT and
CONFIG_GDS_FORCE_MITIGATION
* CVE-2023-3609
- net/sched: cls_u32: Fix reference counter leak leading to overflow
* CVE-2023-20593
- x86/cpu/amd: Move the errata checking functionality up
- x86/cpu/amd: Add a Zenbleed fix
* CVE-2023-3611
- net/sched: sch_qfq: account for stab overhead in qfq_enqueue
* stacked overlay file system mounts that have chroot() called against them
appear to be getting locked (by the kernel most likely?) (LP: #2016398)
- SAUCE: overlayfs: fix reference count mismatch
* Focal update: v5.4.246 upstream stable release (LP: #2028981)
- RDMA/efa: Fix unsupported page sizes in device
- RDMA/bnxt_re: Enable SRIOV VF support on Broadcom's 57500 adapter series
- RDMA/bnxt_re: Refactor queue pair creation code
- RDMA/bnxt_re: Fix return value of bnxt_re_process_raw_qp_pkt_rx
- iommu/rockchip: Fix unwind goto issue
- iommu/amd: Don't block updates to GATag if guest mode is on
- dmaengine: pl330: rename _start to prevent build error
- net/mlx5: fw_tracer, Fix event handling
- netrom: fix info-leak in nr_write_internal()
- af_packet: Fix data-races of pkt_sk(sk)->num.
- amd-xgbe: fix the false linkup in xgbe_phy_status
- mtd: rawnand: ingenic: fix empty stub helper definitions
- af_packet: do not use READ_ONCE() in packet_bind()
- tcp: deny tcp_disconnect() when threads are waiting
- tcp: Return user_mss for TCP_MAXSEG in CLOSE/LISTEN state if user_mss set
- net/sched: sch_ingress: Only create under TC_H_INGRESS
- net/sched: sch_clsact: Only create under TC_H_CLSACT
- net/sched: Reserve TC_H_INGRESS (TC_H_CLSACT) for ingress (clsact) Qdiscs
- net/sched: Prohibit regrafting ingress or clsact Qdiscs
- net: sched: fix NULL pointer dereference in mq_attach
- ocfs2/dlm: move BITS_TO_BYTES() to bitops.h for wider use
- net/netlink: fix NETLINK_LIST_MEMBERSHIPS length report
- udp6: Fix race condition in udp6_sendmsg & connect
- net: dsa: mv88e6xxx: Increase wait after reset deactivation
- mtd: rawnand: marvell: ensure timing values are written
- mtd: rawnand: marvell: don't set the NAND frequency select
- watchdog: menz069_wdt: fix watchdog
[Kernel-packages] [Bug 2030765] Re: mlxbf-gige: Fix kernel panic after reboot
This bug was fixed in the package linux-bluefield - 5.4.0-1070.76
---
linux-bluefield (5.4.0-1070.76) focal; urgency=medium
* focal/linux-bluefield: 5.4.0-1070.76 -proposed tracker (LP:
#2030986)
* EFI pstore not cleared on boot (LP: #1978079)
- [Config] bluefield: Enable CONFIG_EFI_VARS_PSTORE as build-in
- [Config] bluefield: Remove efi-pstore from modules list
* Focal update: v5.4.246 upstream stable release (LP: #2028981)
- [Config] bluefield: updateconfigs for SCSI_DPT_I2O
- SAUCE: xfrm: Check if_id in xfrm full offload
* rshim console truncates dmesg output due to tmfifo issue (LP: #2028197)
- SAUCE: mlxbf-tmfifo.c: Fix rhsim console w/ truncated dmesg output
* mlxbf-gige: Fix kernel panic after reboot (LP: #2030765)
- SAUCE: mlxbf-gige: Fix kernel panic after reboot (part 1/2)
- SAUCE: mlxbf-gige: Fix kernel panic after reboot (part 2/2)
[ Ubuntu: 5.4.0-162.179 ]
* focal/linux: 5.4.0-162.179 -proposed tracker (LP: #2031128)
* libgnutls report "trap invalid opcode" when trying to install packages over
https (LP: #2031093)
- [Config]: disable CONFIG_GDS_FORCE_MITIGATION
[ Ubuntu: 5.4.0-160.177 ]
* focal/linux: 5.4.0-160.177 -proposed tracker (LP: #2031017)
* Fix boot test warning for log_check "CPU: 0 PID: 0 at
arch/x86/kernel/fpu/xstate.c:878 get_xsave_addr+0x98/0xb0" (LP: #2031022)
- x86/pkeys: Revert a5eff7259790 ("x86/pkeys: Add PKRU value to
init_fpstate")
[ Ubuntu: 5.4.0-158.175 ]
* focal/linux: 5.4.0-158.175 -proposed tracker (LP: #2030466)
* CVE-2022-40982
- x86/mm: Initialize text poking earlier
- x86/mm: fix poking_init() for Xen PV guests
- x86/mm: Use mm_alloc() in poking_init()
- mm: Move mm_cachep initialization to mm_init()
- init: Provide arch_cpu_finalize_init()
- x86/cpu: Switch to arch_cpu_finalize_init()
- ARM: cpu: Switch to arch_cpu_finalize_init()
- sparc/cpu: Switch to arch_cpu_finalize_init()
- um/cpu: Switch to arch_cpu_finalize_init()
- init: Remove check_bugs() leftovers
- init: Invoke arch_cpu_finalize_init() earlier
- init, x86: Move mem_encrypt_init() into arch_cpu_finalize_init()
- x86/fpu: Remove cpuinfo argument from init functions
- x86/fpu: Mark init functions __init
- x86/fpu: Move FPU initialization into arch_cpu_finalize_init()
- x86/xen: Fix secondary processors' FPU initialization
- x86/speculation: Add Gather Data Sampling mitigation
- x86/speculation: Add force option to GDS mitigation
- x86/speculation: Add Kconfig option for GDS
- KVM: Add GDS_NO support to KVM
- Documentation/x86: Fix backwards on/off logic about YMM support
- [Config]: Enable CONFIG_ARCH_HAS_CPU_FINALIZE_INIT and
CONFIG_GDS_FORCE_MITIGATION
* CVE-2023-3609
- net/sched: cls_u32: Fix reference counter leak leading to overflow
* CVE-2023-20593
- x86/cpu/amd: Move the errata checking functionality up
- x86/cpu/amd: Add a Zenbleed fix
* CVE-2023-3611
- net/sched: sch_qfq: account for stab overhead in qfq_enqueue
* stacked overlay file system mounts that have chroot() called against them
appear to be getting locked (by the kernel most likely?) (LP: #2016398)
- SAUCE: overlayfs: fix reference count mismatch
* Focal update: v5.4.246 upstream stable release (LP: #2028981)
- RDMA/efa: Fix unsupported page sizes in device
- RDMA/bnxt_re: Enable SRIOV VF support on Broadcom's 57500 adapter series
- RDMA/bnxt_re: Refactor queue pair creation code
- RDMA/bnxt_re: Fix return value of bnxt_re_process_raw_qp_pkt_rx
- iommu/rockchip: Fix unwind goto issue
- iommu/amd: Don't block updates to GATag if guest mode is on
- dmaengine: pl330: rename _start to prevent build error
- net/mlx5: fw_tracer, Fix event handling
- netrom: fix info-leak in nr_write_internal()
- af_packet: Fix data-races of pkt_sk(sk)->num.
- amd-xgbe: fix the false linkup in xgbe_phy_status
- mtd: rawnand: ingenic: fix empty stub helper definitions
- af_packet: do not use READ_ONCE() in packet_bind()
- tcp: deny tcp_disconnect() when threads are waiting
- tcp: Return user_mss for TCP_MAXSEG in CLOSE/LISTEN state if user_mss set
- net/sched: sch_ingress: Only create under TC_H_INGRESS
- net/sched: sch_clsact: Only create under TC_H_CLSACT
- net/sched: Reserve TC_H_INGRESS (TC_H_CLSACT) for ingress (clsact) Qdiscs
- net/sched: Prohibit regrafting ingress or clsact Qdiscs
- net: sched: fix NULL pointer dereference in mq_attach
- ocfs2/dlm: move BITS_TO_BYTES() to bitops.h for wider use
- net/netlink: fix NETLINK_LIST_MEMBERSHIPS length report
- udp6: Fix race condition in udp6_sendmsg & connect
- net: dsa: mv88e6xxx: Increase wait after reset deactivation
- mtd: rawnand: marvell: ensure timing values are written
- mtd: rawnand: marvell: don't set the NAND frequency select
- watchdog: menz069_wdt: fix watchdog
[Kernel-packages] [Bug 2037005] Re: Lunar update: upstream stable patchset 2023-09-21
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + upstream stable patchset 2023-09-21 + from git://git.kernel.org/ -upstream stable patchset 2023-09-21 -from git://git.kernel.org/ + UBUNTU: Upstream stable to v6.1.41, v6.4.6 + io_uring: treat -EAGAIN for REQ_F_NOWAIT as final for io-wq + ALSA: hda/realtek - remove 3k pull low procedure + ALSA: hda/realtek: Add quirk for Clevo NS70AU + ALSA: hda/realtek: Enable Mute LED on HP Laptop 15s-eq2xxx + maple_tree: set the node limit when creating a new root node + maple_tree: fix node allocation testing on 32 bit + keys: Fix linking a duplicate key to a keyring's assoc_array + perf probe: Add test for regression introduced by switch to die_get_decl_file() + btrfs: fix warning when putting transaction with qgroups enabled after abort + fuse: revalidate: don't invalidate if interrupted + fuse: Apply flags2 only when userspace set the FUSE_INIT_EXT + btrfs: set_page_extent_mapped after read_folio in btrfs_cont_expand + btrfs: zoned: fix memory leak after finding block group with super blocks + fuse: ioctl: translate ENOSYS in outarg + btrfs: fix race between balance and cancel/pause + selftests: tc: set timeout to 15 minutes + selftests: tc: add 'ct' action kconfig dep + regmap: Drop initial version of maximum transfer length fixes + of: Preserve "of-display" device name for compatibility + regmap: Account for register length in SMBus I/O limits + arm64/fpsimd: Ensure SME storage is allocated after SVE VL changes + can: mcp251xfd: __mcp251xfd_chip_set_mode(): increase poll timeout + can: bcm: Fix UAF in bcm_proc_show() + can: gs_usb: gs_can_open(): improve error handling + selftests: tc: add ConnTrack procfs kconfig + dma-buf/dma-resv: Stop leaking on krealloc() failure + drm/amdgpu/vkms: relax timer deactivation by hrtimer_try_to_cancel + drm/amdgpu/pm: make gfxclock consistent for sienna cichlid + drm/amdgpu/pm: make mclk consistent for smu 13.0.7 + drm/client: Fix memory leak in drm_client_target_cloned + drm/client: Fix memory leak in drm_client_modeset_probe + drm/amd/display: only accept async flips for fast updates + drm/amd/display: Disable MPC split by default on special asic + drm/amd/display: check TG is non-null before checking if enabled + drm/amd/display: Keep PHY active for DP displays on DCN31 + ASoC: fsl_sai: Disable bit clock with transmitter + ASoC: fsl_sai: Revert "ASoC: fsl_sai: Enable MCTL_MCLK_EN bit for master mode" + ASoC: tegra: Fix ADX byte map + ASoC: rt5640: Fix sleep in atomic context + ASoC: cs42l51: fix driver to properly autoload with automatic module loading + ASoC: codecs: wcd938x: fix missing clsh ctrl error handling + ASoC: codecs: wcd-mbhc-v2: fix resource leaks on component remove + ASoC: qdsp6: audioreach: fix topology probe deferral + ASoC: tegra: Fix AMX byte map + ASoC: codecs: wcd938x: fix resource leaks on component remove + ASoC: codecs: wcd938x: fix missing mbhc init error handling + ASoC: codecs: wcd934x: fix resource leaks on component remove + ASoC: codecs: wcd938x: fix codec initialisation race + ASoC: codecs: wcd938x: fix soundwire initialisation race + ext4: correct inline offset when handling xattrs in inode body + drm/radeon: Fix integer overflow in radeon_cs_parser_init + ALSA: emu10k1: roll up loops in DSP setup code for Audigy + quota: Properly disable quotas when add_dquot_ref() fails + quota: fix warning in dqgrab() + HID: add quirk for 03f0:464a HP Elite Presenter Mouse + ovl: check type and offset of struct vfsmount in ovl_entry + udf: Fix uninitialized array access for some pathnames + fs: jfs: Fix UBSAN: array-index-out-of-bounds in dbAllocDmapLev + MIPS: dec: prom: Address -Warray-bounds warning + FS: JFS: Fix null-ptr-deref Read in txBegin + FS: JFS: Check for read-only mounted filesystem in txBegin + ACPI: video: Add backlight=native DMI quirk for Dell Studio 1569 + rcu-tasks: Avoid pr_info() with spin lock in cblist_init_generic() + rcu: Mark additional concurrent load from ->cpu_no_qs.b.exp + sched/fair: Don't balance task to its current running CPU + wifi: ath11k: fix
[Kernel-packages] [Bug 2000228] Re: [SRU] Add initial support for Mediatek Genio boards
** Also affects: alsa-ucm-conf (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: alsa-ucm-conf (Ubuntu Jammy) Assignee: (unassigned) => ethan.hsieh (ethan.hsieh) ** Changed in: alsa-ucm-conf (Ubuntu Lunar) Assignee: (unassigned) => ethan.hsieh (ethan.hsieh) ** Changed in: alsa-ucm-conf (Ubuntu Jammy) Status: New => In Progress ** Changed in: alsa-ucm-conf (Ubuntu Lunar) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2000228 Title: [SRU] Add initial support for Mediatek Genio boards Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: In Progress Status in alsa-ucm-conf source package in Lunar: In Progress Bug description: [Impact] Add initial support for Mediatek Genio boards (mt8365-evk, mt8390-evk, and mt8395-evk) mt8365-evk: https://github.com/alsa-project/alsa-ucm-conf/commit/2f8027349c37044e15c694c6df4d62d622e20886 mt8390-evk (G700): (Still under review) https://github.com/alsa-project/alsa-ucm-conf/pull/321 mt8395-evk (G1200): (Still under review) https://github.com/alsa-project/alsa-ucm-conf/pull/322 [Where problems could occur] Audio function doesn't work on Mediatek Genio boards. mantic: mt8390-evk, and mt8395-evk lunar/jammy: mt8365-evk, mt8390-evk, and mt8395-evk [Test Case] Verify audio function on Mediatek Genio boards (mt8365-evk, mt8390-evk, and mt8395-evk). 1. Headset Jack Playback 2. Audio (Speaker) Jack Playback 3. HDMI Playback Play audio by following commands. $ speaker-test -D pulse -c 2 -r 48000 -f S16_LE -t wav [Regression Potential] Add initial support for Mediatek Genio boards. There should be no risk. mantic: mt8390-evk, and mt8395-evk lunar/jammy: mt8365-evk, mt8390-evk, and mt8395-evk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2000228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037000] Re: No HDMI output with 6.5.0-2-generic
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: https://iso.qa.ubuntu.com/qatracker/reports/bugs/2037000 ** Tags added: iso-testing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-riscv in Ubuntu. https://bugs.launchpad.net/bugs/2037000 Title: No HDMI output with 6.5.0-2-generic Status in linux-meta-riscv package in Ubuntu: New Bug description: I am currently testing the mantic preinstalled server image for the LicheeRV Dock. After upgrading to Linux 6.5 from ppa:esmil/ppa output for HDMI is missing. Before we build the final images this needs to be fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-riscv/+bug/2037000/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037005] [NEW] Lunar update: upstream stable patchset 2023-09-21
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2023-09-21 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Lunar) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- 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/2037005 Title: Lunar update: upstream stable patchset 2023-09-21 Status in linux package in Ubuntu: Invalid Status in linux source package in Lunar: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2023-09-21 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
I've uploaded the jammy backport of this patch into the queue, so assigning it to myself. As I have readily seen this problem on my own test kernels I'll validate it with a local kernel with the matching kconfig options when it's accepted. This can then be done in advance of waiting for matching changes landing in OEM-6.5, or HWE-6.5. ** Changed in: gdm3 (Ubuntu Jammy) Status: Triaged => In Progress ** Changed in: gdm3 (Ubuntu Jammy) Assignee: (unassigned) => Mario Limonciello (superm1) ** Description changed: - [ Impact ] + [ Impact ] The fbdev subsystem has been deprecated for a long time. We should drop it in favour of using simpledrm with fbdev emulation layer. This requires Kernel config changes: FB_EFI=n FB_VESA=n fbcon will still require FB to be available, but will use the fbdev emulation layer When this stack is enabled, it changes boot timing such that some drivers may take a longer time to boot and GDM may hang in a black screen. + This issue has been readily reproduced in Ubuntu and reported to upstream mutter. + https://gitlab.gnome.org/GNOME/mutter/-/issues/2909 + [ Test Plan ] * Ensure that a kernel with required kernel changes can boot to GDM using DRM driver (amdgpu, i915, or nouveau) [ Where Problems could occur ] * Race conditions could be exposed to DE environments * Software that expects to find DRM device at /dev/dri/card0 may have a problem. * Some older versions of NVIDIA driver might not work properly. [ Other Info ] * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 -- 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/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer Status in gdm: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in gdm3 source package in Jammy: In Progress Status in linux source package in Jammy: Won't Fix Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in gdm3 source package in Mantic: Fix Released Status in linux source package in Mantic: Confirmed Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Status in linux package in Fedora: Fix Released Bug description: [ Impact ] The fbdev subsystem has been deprecated for a long time. We should drop it in favour of using simpledrm with fbdev emulation layer. This requires Kernel config changes: FB_EFI=n FB_VESA=n fbcon will still require FB to be available, but will use the fbdev emulation layer When this stack is enabled, it changes boot timing such that some drivers may take a longer time to boot and GDM may hang in a black screen. This issue has been readily reproduced in Ubuntu and reported to upstream mutter. https://gitlab.gnome.org/GNOME/mutter/-/issues/2909 [ Test Plan ] * Ensure that a kernel with required kernel changes can boot to GDM using DRM driver (amdgpu, i915, or nouveau) [ Where Problems could occur ] * Race conditions could be exposed to DE environments * Software that expects to find DRM device at /dev/dri/card0 may have a problem. * Some older versions of NVIDIA driver might not work properly. [ Other Info ] * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988806] Re: Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel
** Changed in: ubuntu-release-notes
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/1988806
Title:
Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel
Status in Release Notes for Ubuntu:
Invalid
Status in linux package in Ubuntu:
Triaged
Status in linux-hwe-5.19 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-hwe-5.19 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Status in linux-hwe-5.19 source package in Kinetic:
Invalid
Status in linux source package in Lunar:
Fix Released
Status in linux-hwe-5.19 source package in Lunar:
Invalid
Status in linux source package in Mantic:
Triaged
Status in linux-hwe-5.19 source package in Mantic:
Invalid
Bug description:
With below commit in 5.16 upstream kernel, support for
mdev_set_iommu_device() kABI was removed from kernel as there were no
in-tree drivers making use of the kABI.
fda49d97f2c4 ("vfio: remove the unused mdev iommu hook")
This kABI is used by SRIOV based Nvidia vGPU on Ubuntu 22.04. Ampere+
(SRIOV based) Nvidia vGPU use kernel's mdev framework and use this
kABI to pin all guest memory during VM boot.
As HWE kernel (for Ubuntu 22.04) will switch to 5.19 upstream kernel,
it will not include this kABI and as a result will break SRIOV based
Nvidia vGPU. So, filing this bug to request to have a custom patch in
HWE kernel which doesn't remove the support for
mdev_set_iommu_device() kABI.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1988806/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037000] Re: No HDMI output with 6.5.0-2-generic
$ uname -a Linux ubuntu 6.5.0-2-generic #2.1-Ubuntu SMP Tue Sep 5 14:10:40 UTC 2023 riscv64 riscv64 riscv64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-riscv in Ubuntu. https://bugs.launchpad.net/bugs/2037000 Title: No HDMI output with 6.5.0-2-generic Status in linux-meta-riscv package in Ubuntu: New Bug description: I am currently testing the mantic preinstalled server image for the LicheeRV Dock. After upgrading to Linux 6.5 from ppa:esmil/ppa output for HDMI is missing. Before we build the final images this needs to be fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-riscv/+bug/2037000/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037000] [NEW] No HDMI output with 6.5.0-2-generic
Public bug reported: I am currently testing the mantic preinstalled server image for the LicheeRV Dock. After upgrading to Linux 6.5 from ppa:esmil/ppa output for HDMI is missing. Before we build the final images this needs to be fixed. ** Affects: linux-meta-riscv (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-riscv in Ubuntu. https://bugs.launchpad.net/bugs/2037000 Title: No HDMI output with 6.5.0-2-generic Status in linux-meta-riscv package in Ubuntu: New Bug description: I am currently testing the mantic preinstalled server image for the LicheeRV Dock. After upgrading to Linux 6.5 from ppa:esmil/ppa output for HDMI is missing. Before we build the final images this needs to be fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-riscv/+bug/2037000/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036951] Re: unblock request: please migrate dkms from proposed
Bug description does not describe a beta-critical issue, only autopkgtest failures. Should be unblocked after Beta is released. ** Changed in: dkms (Ubuntu Mantic) Milestone: ubuntu-23.10-beta => None -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2036951 Title: unblock request: please migrate dkms from proposed Status in dkms package in Ubuntu: New Status in dkms source package in Mantic: New Bug description: Kernels now use zstd compressed modules. dkms autopkgtest was not expecting that correctly. autopkgtest was adjusted, and uploaded to proposed but did not migrate prior to feature freeze. Please unblock dkms to migrate, to resolve all ongoing dkms failures. The upload in question is https://launchpad.net/ubuntu/+source/dkms/3.0.11-1ubuntu10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2036951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035373] Re: Move nbd module into modules (from -extra)
** Also affects: linux-raspi (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Mantic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2035373 Title: Move nbd module into modules (from -extra) Status in linux-raspi package in Ubuntu: Fix Committed Status in linux-raspi source package in Jammy: New Status in linux-raspi source package in Mantic: Fix Committed Bug description: Would it be possible to move the "nbd" kernel module from linux- modules-extra-raspi into linux-modules-raspi? This would enable NBD- based network boot (which has certain advantages over the NFS-based network boot more traditional in the Pi world, such as permitting services that refuse to run on NFS -- like snapd). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2035373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036995] [NEW] [mantic] rpi3 has no video output on HDMI
Public bug reported: On the mantic beta (20230919.1) I don't see any video output on hdmi with rpi3. I've tested the same image and configuration with rpiz2 and rpi4 so far, and I do get hdmi output on both of those, so I don't think it's likely to be an issue with my monitor or cable. Logs attached. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-raspi (not installed) ProcVersionSignature: Ubuntu 6.5.0-1002.2-raspi 6.5.0 Uname: Linux 6.5.0-1002-raspi aarch64 ApportVersion: 2.27.0-0ubuntu2 Architecture: arm64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: config-disk (/dev/mmcblk0p1) Date: Thu Sep 21 17:04:47 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 ProcFB: 0 BCM2708 FB ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1080 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 console=ttyS0,115200 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash RelatedPackageVersions: linux-restricted-modules-6.5.0-1002-raspi N/A linux-backports-modules-6.5.0-1002-raspi N/A linux-firmware20230919.git3672ccab-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-raspi StagingDrivers: snd_bcm2835 bcm2835_mmal_vchiq bcm2835_v4l2 bcm2835_isp bcm2835_codec vc_sm_cma UpgradeStatus: No upgrade log present (probably fresh install) acpidump: ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 mantic staging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2036995 Title: [mantic] rpi3 has no video output on HDMI Status in linux-raspi package in Ubuntu: New Bug description: On the mantic beta (20230919.1) I don't see any video output on hdmi with rpi3. I've tested the same image and configuration with rpiz2 and rpi4 so far, and I do get hdmi output on both of those, so I don't think it's likely to be an issue with my monitor or cable. Logs attached. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-raspi (not installed) ProcVersionSignature: Ubuntu 6.5.0-1002.2-raspi 6.5.0 Uname: Linux 6.5.0-1002-raspi aarch64 ApportVersion: 2.27.0-0ubuntu2 Architecture: arm64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: config-disk (/dev/mmcblk0p1) Date: Thu Sep 21 17:04:47 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 ProcFB: 0 BCM2708 FB ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1080 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 console=ttyS0,115200 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash RelatedPackageVersions: linux-restricted-modules-6.5.0-1002-raspi N/A linux-backports-modules-6.5.0-1002-raspi N/A linux-firmware20230919.git3672ccab-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-raspi StagingDrivers: snd_bcm2835 bcm2835_mmal_vchiq bcm2835_v4l2 bcm2835_isp bcm2835_codec vc_sm_cma UpgradeStatus: No upgrade log present (probably fresh install) acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2036995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
** Changed in: gdm Status: Unknown => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer Status in gdm: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in gdm3 source package in Jammy: Triaged Status in linux source package in Jammy: Won't Fix Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in gdm3 source package in Mantic: Fix Released Status in linux source package in Mantic: Confirmed Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Status in linux package in Fedora: Fix Released Bug description: [ Impact ] The fbdev subsystem has been deprecated for a long time. We should drop it in favour of using simpledrm with fbdev emulation layer. This requires Kernel config changes: FB_EFI=n FB_VESA=n fbcon will still require FB to be available, but will use the fbdev emulation layer When this stack is enabled, it changes boot timing such that some drivers may take a longer time to boot and GDM may hang in a black screen. [ Test Plan ] * Ensure that a kernel with required kernel changes can boot to GDM using DRM driver (amdgpu, i915, or nouveau) [ Where Problems could occur ] * Race conditions could be exposed to DE environments * Software that expects to find DRM device at /dev/dri/card0 may have a problem. * Some older versions of NVIDIA driver might not work properly. [ Other Info ] * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
Launchpad has imported 6 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=2022385. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2021-11-11T14:33:25+00:00 bcotton wrote: This is a tracking bug for Change: Replace the fbdev drivers with simpledrm and the DRM fbdev emulation layer For more details, see: https://fedoraproject.org/wiki/Changes/ReplaceFbdevDrivers This change replaces the legacy Linux frame buffer device (fbdev) drivers that are still used in Fedora, with the latest simpledrm driver and the DRM fbdev emulation layer. If you encounter a bug related to this Change, please do not comment here. Instead create a new bug and set it to block this bug. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965303/comments/0 On 2021-12-23T11:26:38+00:00 fmartine wrote: This change has been present in the Fedora kernel since https://gitlab.com/cki-project/kernel- ark/-/commit/53d2c01aef5aaad8b8bb54e4254f6ae671c76ee5 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965303/comments/1 On 2021-12-23T11:44:17+00:00 fmartine wrote: *** Bug 1986222 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965303/comments/2 On 2022-02-08T21:06:33+00:00 bcotton wrote: This bug appears to have been reported against 'rawhide' during the Fedora Linux 36 development cycle. Changing version to 36. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965303/comments/3 On 2022-02-22T16:34:36+00:00 bcotton wrote: We have reached the 'Change complete (100% complete)' deadline in the Fedora Linux 36 release schedule. At this time, all Changes should be fully complete. Indicate this by setting this tracking bug to ON_QA. If you need to defer this Change to a subsequent release, please needinfo me. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965303/comments/4 On 2022-05-10T14:41:45+00:00 bcotton wrote: F36 was released today. If this Change did not land in the release, please notify bcotton as soon as possible. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965303/comments/6 ** Changed in: linux (Fedora) Status: Unknown => Fix Released ** Changed in: linux (Fedora) Importance: Unknown => Undecided -- 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/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer Status in gdm: Unknown Status in gdm3 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in gdm3 source package in Jammy: Triaged Status in linux source package in Jammy: Won't Fix Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in gdm3 source package in Mantic: Fix Released Status in linux source package in Mantic: Confirmed Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Status in linux package in Fedora: Fix Released Bug description: [ Impact ] The fbdev subsystem has been deprecated for a long time. We should drop it in favour of using simpledrm with fbdev emulation layer. This requires Kernel config changes: FB_EFI=n FB_VESA=n fbcon will still require FB to be available, but will use the fbdev emulation layer When this stack is enabled, it changes boot timing such that some drivers may take a longer time to boot and GDM may hang in a black screen. [ Test Plan ] * Ensure that a kernel with required kernel changes can boot to GDM using DRM driver (amdgpu, i915, or nouveau) [ Where Problems could occur ] * Race conditions could be exposed to DE environments * Software that expects to find DRM device at /dev/dri/card0 may have a problem. * Some older versions of NVIDIA driver might not work properly. [ Other Info ] * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 2036742] Re: amdgpu crash on Mantic
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2036742 Title: amdgpu crash on Mantic Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Booting from USB the latest Mantic Desktop daily image (2023-09-20), just after the initial logs, nothing is displayed on screen. The system is still alive since _autoinstall_ works as intended. Once provisioned, the problem is still present. It seems related to https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2029396 . dmesg attached. [Test Case] Live boot Ubuntu Mantic Desktop canary (2023-09-19) [Where Problems Could Occur] Dell Optiplex 5090 - Intel Core(TM) i7-11700 - Advanced Micro Devices, Inc. [AMD/ATI] - 1002:699f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
** Description changed: - The fbdev subsystem has been deprecated for a long time. We should drop - it in favour of using simpledrm with fbdev emulation layer. + [ Impact ] + The fbdev subsystem has been deprecated for a long time. We should drop it in favour of using simpledrm with fbdev emulation layer. - This requires config changes: + This requires Kernel config changes: FB_EFI=n FB_VESA=n fbcon will still require FB to be available, but will use the fbdev emulation layer - fedora bug: - https://bugzilla.redhat.com/show_bug.cgi?id=2022385 + When this stack is enabled, it changes boot timing such that some + drivers may take a longer time to boot and GDM may hang in a black + screen. + + [ Test Plan ] + * Ensure that a kernel with required kernel changes can boot to GDM using DRM driver (amdgpu, i915, or nouveau) + + [ Where Problems could occur ] + * Race conditions could be exposed to DE environments + * Software that expects to find DRM device at /dev/dri/card0 may have a problem. + * Some older versions of NVIDIA driver might not work properly. + + [ Other Info ] + * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2909 https://gitlab.gnome.org/GNOME/mutter/-/issues/2909 ** Also affects: gdm via https://gitlab.gnome.org/GNOME/mutter/-/issues/2909 Importance: Unknown Status: Unknown ** Bug watch added: Red Hat Bugzilla #2022385 https://bugzilla.redhat.com/show_bug.cgi?id=2022385 ** Also affects: linux (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=2022385 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer Status in gdm: Unknown Status in gdm3 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in gdm3 source package in Jammy: Triaged Status in linux source package in Jammy: Won't Fix Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in gdm3 source package in Mantic: Fix Released Status in linux source package in Mantic: Confirmed Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Status in linux package in Fedora: Unknown Bug description: [ Impact ] The fbdev subsystem has been deprecated for a long time. We should drop it in favour of using simpledrm with fbdev emulation layer. This requires Kernel config changes: FB_EFI=n FB_VESA=n fbcon will still require FB to be available, but will use the fbdev emulation layer When this stack is enabled, it changes boot timing such that some drivers may take a longer time to boot and GDM may hang in a black screen. [ Test Plan ] * Ensure that a kernel with required kernel changes can boot to GDM using DRM driver (amdgpu, i915, or nouveau) [ Where Problems could occur ] * Race conditions could be exposed to DE environments * Software that expects to find DRM device at /dev/dri/card0 may have a problem. * Some older versions of NVIDIA driver might not work properly. [ Other Info ] * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2030765] Re: mlxbf-gige: Fix kernel panic after reboot
After performing 1000 reboots, oob interface has an ip and no kernel panic have been discovered. ** Tags removed: verification-needed-focal-linux-bluefield ** Tags added: verification-done-focal-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2030765 Title: mlxbf-gige: Fix kernel panic after reboot Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] Previously we fixed 2022370 by modifying the shutdown() function but that creates a bug which needs to be reverted. It doesnt deinitialize the oob_net0 interface properly after reboot and causes issues for the UEFI OOB driver. [Fix] * Revert 2022370 changes * Instead, just check that "priv" is not NULL. [Test Case] * Run the reboot test 1000 times * Check that there is no kernel panic after reboot * Check that the UEFI OOB interface gets an ip [Regression Potential] * We could still see a kernel panic since it is very intermittent. QA reproduced it once every 350 reboots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2030765/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
Mantic has 45~beta-1ubuntu1 which picks up the fix for this. Jammy is still open. ** Changed in: gdm3 (Ubuntu Mantic) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer Status in gdm3 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in gdm3 source package in Jammy: Triaged Status in linux source package in Jammy: Won't Fix Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in gdm3 source package in Mantic: Fix Released Status in linux source package in Mantic: Confirmed Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Bug description: The fbdev subsystem has been deprecated for a long time. We should drop it in favour of using simpledrm with fbdev emulation layer. This requires config changes: FB_EFI=n FB_VESA=n fbcon will still require FB to be available, but will use the fbdev emulation layer fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1965303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036988] Re: Unable to boot on Lenovo L590 Laptop
** Description changed: - With Kernel images 6.2.0-32 and 6.2.0-33, I can no longer boot ubuntu on - my laptop. On regular graphic boot it just hangs on a black screen, with - advanced boot options, selecting the current kernel, It hangs - immediately after "Loading initioal ramdisk" without any error message. + With Kernel images 6.2.0-32 and 6.2.0-33, I can no longer boot ubuntu on my laptop. On regular graphic boot it just hangs on a black screen. + With advanced boot options and selecting the current kernel, it hangs immediately after "Loading initial ramdisk" without any error message. - I have to select an older kernel release to boot. 6.2.0-26 is the latest - I know to work. + I have to select an older kernel release to boot. + 6.2.0-26 is the latest I know to work. We have another identical laptop of type Lenovo L590 also installed with - Ubuntu and it shows the same behaviour, so it's likely not a hardware + Ubuntu and it shows the same behavior, so it's likely not a hardware problem on my device. The CPU type is Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 21 16:51:07 2023 InstallationDate: Installed on 2020-04-24 (1245 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=de_DE.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2022-11-20 (304 days ago) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2036988 Title: Unable to boot on Lenovo L590 Laptop Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: With Kernel images 6.2.0-32 and 6.2.0-33, I can no longer boot ubuntu on my laptop. On regular graphic boot it just hangs on a black screen. With advanced boot options and selecting the current kernel, it hangs immediately after "Loading initial ramdisk" without any error message. I have to select an older kernel release to boot. 6.2.0-26 is the latest I know to work. We have another identical laptop of type Lenovo L590 also installed with Ubuntu and it shows the same behavior, so it's likely not a hardware problem on my device. The CPU type is Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 21 16:51:07 2023 InstallationDate: Installed on 2020-04-24 (1245 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2022-11-20 (304 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2036988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036968] Re: Mantic minimized/minimal cloud images do not receive IP address during provisioning
cloud-init bug filed @ https://github.com/canonical/cloud- init/issues/4451 ** Bug watch added: github.com/canonical/cloud-init/issues #4451 https://github.com/canonical/cloud-init/issues/4451 -- 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/2036968 Title: Mantic minimized/minimal cloud images do not receive IP address during provisioning Status in cloud-images: New Status in linux package in Ubuntu: Incomplete Bug description: Following a recent change from linux-kvm kernel to linux-generic kernel in the mantic minimized images, there is a reproducable bug where a guest VM does not have an IP address assigned as part of cloud-init provisioning. This is easiest to reproduce when emulating arm64 on amd64 host. The bug is a race condition, so there could exist fast enough virtualisation on fast enough hardware where this bug is not present but in all my testing I have been able to reproduce. The latest mantic minimized images from http://cloud- images.ubuntu.com/minimal/daily/mantic/ have force initrdless boot and no initrd to fallback to. This but is not present in the non minimized/base images @ http://cloud-images.ubuntu.com/mantic/ as these boot with initrd with the required drivers present for virtio-net. Reproducer ``` wget -O "launch-qcow2-image-qemu-arm64.sh" https://people.canonical.com/~philroche/20230921-cloud-images-mantic-fail-to-provision/launch-qcow2-image-qemu-arm64.sh chmod +x ./launch-qcow2-image-qemu-arm64.sh wget https://people.canonical.com/~philroche/20230921-cloud-images-mantic-fail-to-provision/livecd.ubuntu-cpc.img ./launch-qcow2-image-qemu-arm64.sh --password passw0rd --image ./livecd.ubuntu-cpc.img ``` You will then be able to log in with user `ubuntu` and password `passw0rd`. You can run `ip a` and see that there is a network interface present (separate to `lo`) but no IP address has been assigned. ``` ubuntu@cloudimg:~$ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s1: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff ``` This is because when cloud-init is trying to configure network interfaces it doesn't find any so it doesn't configure any. But by the time boot is complete the network interface is present but cloud-init provisioning has already completed. You can verify this by running `sudo cloud-init clean && sudo cloud- init init` You can then see a successfully configured network interface ``` ubuntu@cloudimg:~$ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff inet 10.0.2.15/24 metric 100 brd 10.0.2.255 scope global dynamic enp0s1 valid_lft 86391sec preferred_lft 86391sec inet6 fec0::5054:ff:fe12:3456/64 scope site dynamic mngtmpaddr noprefixroute valid_lft 86393sec preferred_lft 14393sec inet6 fe80::5054:ff:fe12:3456/64 scope link valid_lft forever preferred_lft forever ``` The bug is also reproducible with amd64 guest on adm64 host on older/slower hardware. The suggested fixes while debugging this issue are: * to include `virtio-net` as a built-in in the mantic generic kernel * understand what needs to change in cloud-init so that it can react to late additions of network interfaces I will file a separate bug against cloud-init to address the race condition on emulated guest/older hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2036968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
Only fix here was to completely disable LPM in libata with "libata.force=nolpm" -- 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/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: SATA disk hot plug can't work on Ubuntu 20.04 ga-kernel of "Linux version 5.4.0-109-generic", but it works on earlier version of " Linux version 5.4.0-42-generic" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036988] [NEW] Unable to boot on Lenovo L590 Laptop
Public bug reported: With Kernel images 6.2.0-32 and 6.2.0-33, I can no longer boot ubuntu on my laptop. On regular graphic boot it just hangs on a black screen, with advanced boot options, selecting the current kernel, It hangs immediately after "Loading initioal ramdisk" without any error message. I have to select an older kernel release to boot. 6.2.0-26 is the latest I know to work. We have another identical laptop of type Lenovo L590 also installed with Ubuntu and it shows the same behaviour, so it's likely not a hardware problem on my device. The CPU type is Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 21 16:51:07 2023 InstallationDate: Installed on 2020-04-24 (1245 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2022-11-20 (304 days ago) ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2036988 Title: Unable to boot on Lenovo L590 Laptop Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: With Kernel images 6.2.0-32 and 6.2.0-33, I can no longer boot ubuntu on my laptop. On regular graphic boot it just hangs on a black screen, with advanced boot options, selecting the current kernel, It hangs immediately after "Loading initioal ramdisk" without any error message. I have to select an older kernel release to boot. 6.2.0-26 is the latest I know to work. We have another identical laptop of type Lenovo L590 also installed with Ubuntu and it shows the same behaviour, so it's likely not a hardware problem on my device. The CPU type is Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 21 16:51:07 2023 InstallationDate: Installed on 2020-04-24 (1245 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2022-11-20 (304 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2036988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
Adding the above line to the kernel on Mantic does not work - in fact setting values in /sys/class/scsi_host/host*/link_power_management_policy appears to get reverted during boot also. I have added this to rc.local but it changes back to med_power_with_dipm once the boot is completed. I have tried adding the kernel line, and also setting via systemd and cron tasks, it appears that something is reverting this setting. -- 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/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: SATA disk hot plug can't work on Ubuntu 20.04 ga-kernel of "Linux version 5.4.0-109-generic", but it works on earlier version of " Linux version 5.4.0-42-generic" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006716] Re: 5 failures reported in net:fcnal-test.sh on Jammy
Looks like: # With VRF # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # SYSCTL: net.ipv4.ping_group_range=0 2147483647 # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # TEST: ping out, vrf device+address bind - ns-B IPv6 LLA [FAIL] Has gone, verified with: * j-aws-5.15.0-1046.51 c4.large, t3a.2xlarge * j-5.15.0-85.95 openstack amd64 * j-gcp-5.15.0-1043.51 n1-standard-64 * j-azure-5.15.0-1048.55 Standard_D4s_v3-gen2 ** Summary changed: - 5 failures reported in net:fcnal-test.sh on Jammy + 4 failures reported in net:fcnal-test.sh on Jammy ** Description changed: This is not a regression, but something covered by bug 2006692 There are 5 sub-test failures reported in this test on Jammy: # Tests passed: 857 # Tests failed: 5 # With VRF # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # TEST: ping local, VRF bind - VRF IP [FAIL] # TEST: ping local, device bind - ns-A IP [FAIL] # SYSCTL: net.ipv4.ping_group_range=0 2147483647 # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # TEST: ping local, VRF bind - VRF IP [FAIL] # TEST: ping local, device bind - ns-A IP [FAIL] + === The following seems to be fixed, see comment #4 # With VRF # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # SYSCTL: net.ipv4.ping_group_range=0 2147483647 # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # TEST: ping out, vrf device+address bind - ns-B IPv6 LLA [FAIL] We might see failure came up in F/K after bug 2006391 being fixed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2006716 Title: 4 failures reported in net:fcnal-test.sh on Jammy Status in ubuntu-kernel-tests: New Status in linux-hwe-5.15 package in Ubuntu: New Status in linux-hwe-5.15 source package in Focal: New Bug description: This is not a regression, but something covered by bug 2006692 There are 5 sub-test failures reported in this test on Jammy: # Tests passed: 857 # Tests failed: 5 # With VRF # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # TEST: ping local, VRF bind - VRF IP [FAIL] # TEST: ping local, device bind - ns-A IP [FAIL] # SYSCTL: net.ipv4.ping_group_range=0 2147483647 # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # TEST: ping local, VRF bind - VRF IP [FAIL] # TEST: ping local, device bind - ns-A IP [FAIL] === The following seems to be fixed, see comment #4 # With VRF # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # SYSCTL: net.ipv4.ping_group_range=0 2147483647 # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # TEST: ping out, vrf device+address bind - ns-B IPv6 LLA [FAIL] We might see failure came up in F/K after bug 2006391 being fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2006716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036968] Re: Mantic minimized/minimal cloud images do not receive IP address during provisioning
** Description changed: Following a recent change from linux-kvm kernel to linux-generic kernel - in the mantic minimized images there is a reproducable bug where a guest - VM does not have an IP address assigned as part of cloud-init + in the mantic minimized images, there is a reproducable bug where a + guest VM does not have an IP address assigned as part of cloud-init provisioning. - This is easiest to reproduce when emulating arm64 on adm64 host. The bug - is a race condition so there could exist fast enough virtualisation on + This is easiest to reproduce when emulating arm64 on amd64 host. The bug + is a race condition, so there could exist fast enough virtualisation on fast enough hardware where this bug is not present but in all my testing I have been able to reproduce. The latest mantic minimized images from http://cloud- images.ubuntu.com/minimal/daily/mantic/ have force initrdless boot and no initrd to fallback to. - This bug is not present in the non minimized/base images @ http://cloud- + This but is not present in the non minimized/base images @ http://cloud- images.ubuntu.com/mantic/ as these boot with initrd with the required drivers present for virtio-net. Reproducer ``` wget -O "launch-qcow2-image-qemu-arm64.sh" https://people.canonical.com/~philroche/20230921-cloud-images-mantic-fail-to-provision/launch-qcow2-image-qemu-arm64.sh chmod +x ./launch-qcow2-image-qemu-arm64.sh wget https://people.canonical.com/~philroche/20230921-cloud-images-mantic-fail-to-provision/livecd.ubuntu-cpc.img ./launch-qcow2-image-qemu-arm64.sh --password passw0rd --image ./livecd.ubuntu-cpc.img ``` You will then be able to log in with user `ubuntu` and password `passw0rd`. You can run `ip a` and see that there is a network interface present (separate to `lo`) but no IP address has been assigned. ``` ubuntu@cloudimg:~$ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s1: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff ``` - This is because when cloud-init-local.service is trying to configure - network interfaces it doesn't find any so it doesn't configure any. But - by the time boot is complete the network interface is present but cloud- - init provisioning has already completed. + This is because when cloud-init is trying to configure network + interfaces it doesn't find any so it doesn't configure any. But by the + time boot is complete the network interface is present but cloud-init + provisioning has already completed. You can verify this by running `sudo cloud-init clean && sudo cloud-init init` You can then see a successfully configured network interface ``` ubuntu@cloudimg:~$ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff inet 10.0.2.15/24 metric 100 brd 10.0.2.255 scope global dynamic enp0s1 valid_lft 86391sec preferred_lft 86391sec inet6 fec0::5054:ff:fe12:3456/64 scope site dynamic mngtmpaddr noprefixroute valid_lft 86393sec preferred_lft 14393sec inet6 fe80::5054:ff:fe12:3456/64 scope link valid_lft forever preferred_lft forever ``` - The bug is also reproducable with amd64 guest on adm64 host on + The bug is also reproducible with amd64 guest on adm64 host on older/slower hardware. The suggested fixes while debugging this issue are: * to include `virtio-net` as a built-in in the mantic generic kernel * understand what needs to change in cloud-init so that it can react to late additions of network interfaces I will file a separate bug against cloud-init to address the race condition on emulated guest/older hardware. -- 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/2036968 Title: Mantic minimized/minimal cloud images do not receive IP address during provisioning Status in cloud-images: New Status in linux package in Ubuntu: Incomplete Bug description: Following a recent change from linux-kvm kernel to linux-generic kernel in the mantic minimized images, there is a reproducable bug where a guest VM does not have an IP address assigned as part of cloud-init provisioning.
[Kernel-packages] [Bug 2036968] 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 2036968 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/2036968 Title: Mantic minimized/minimal cloud images do not receive IP address during provisioning Status in cloud-images: New Status in linux package in Ubuntu: Incomplete Bug description: Following a recent change from linux-kvm kernel to linux-generic kernel in the mantic minimized images there is a reproducable bug where a guest VM does not have an IP address assigned as part of cloud-init provisioning. This is easiest to reproduce when emulating arm64 on adm64 host. The bug is a race condition so there could exist fast enough virtualisation on fast enough hardware where this bug is not present but in all my testing I have been able to reproduce. The latest mantic minimized images from http://cloud- images.ubuntu.com/minimal/daily/mantic/ have force initrdless boot and no initrd to fallback to. This bug is not present in the non minimized/base images @ http://cloud-images.ubuntu.com/mantic/ as these boot with initrd with the required drivers present for virtio-net. Reproducer ``` wget -O "launch-qcow2-image-qemu-arm64.sh" https://people.canonical.com/~philroche/20230921-cloud-images-mantic-fail-to-provision/launch-qcow2-image-qemu-arm64.sh chmod +x ./launch-qcow2-image-qemu-arm64.sh wget https://people.canonical.com/~philroche/20230921-cloud-images-mantic-fail-to-provision/livecd.ubuntu-cpc.img ./launch-qcow2-image-qemu-arm64.sh --password passw0rd --image ./livecd.ubuntu-cpc.img ``` You will then be able to log in with user `ubuntu` and password `passw0rd`. You can run `ip a` and see that there is a network interface present (separate to `lo`) but no IP address has been assigned. ``` ubuntu@cloudimg:~$ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s1: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff ``` This is because when cloud-init-local.service is trying to configure network interfaces it doesn't find any so it doesn't configure any. But by the time boot is complete the network interface is present but cloud-init provisioning has already completed. You can verify this by running `sudo cloud-init clean && sudo cloud- init init` You can then see a successfully configured network interface ``` ubuntu@cloudimg:~$ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff inet 10.0.2.15/24 metric 100 brd 10.0.2.255 scope global dynamic enp0s1 valid_lft 86391sec preferred_lft 86391sec inet6 fec0::5054:ff:fe12:3456/64 scope site dynamic mngtmpaddr noprefixroute valid_lft 86393sec preferred_lft 14393sec inet6 fe80::5054:ff:fe12:3456/64 scope link valid_lft forever preferred_lft forever ``` The bug is also reproducable with amd64 guest on adm64 host on older/slower hardware. The suggested fixes while debugging this issue are: * to include `virtio-net` as a built-in in the mantic generic kernel * understand what needs to change in cloud-init so that it can react to late additions of network interfaces I will file a separate bug against cloud-init to address the race condition on emulated guest/older hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2036968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035128] Re: mlxbf-gige: Enable the OOB port in mlxbf_gige_open
** Changed in: linux-bluefield (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2035128 Title: mlxbf-gige: Enable the OOB port in mlxbf_gige_open Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Focal: Fix Committed Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] At the moment, the OOB port is enabled in the mlxbf_gige_probe function. If the mlxbf_gige_open is not executed, this could cause pause frames to increase in the case where there is high backgroud traffic. This results in clogging the BMC port as well. [Fix] * Move enabling the OOB port to mlxbf_gige_open. [Test Case] * Main test for this bug: Check that the BMC is always pingable while pushing a BFB Other tests: * Check if the gige driver is loaded * Check that the oob_net0 interface is up and operational * Do the reboot test and powercycle test and check the oob_net0 interface again * Push BFB multiple times and make sure the OOB is up and running [Regression Potential] Since are moving code that hasn't moved since BF2, it is important to make sure that there is no regression. Make sure that the OOB interface is always up and pingable after the reboot test, the powercycle test and after pushing a BFB. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2035128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013743] Re: USB not working on Nezha D1
Same error exists with Linux ubuntu 6.2.0-19-generic on Nezha D1 board. ** Changed in: linux-allwinner (Ubuntu) Status: Fix Released => New ** Also affects: linux-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-allwinner in Ubuntu. https://bugs.launchpad.net/bugs/2013743 Title: USB not working on Nezha D1 Status in linux-allwinner package in Ubuntu: New Status in linux-meta package in Ubuntu: New Bug description: I am testing the Allwinner Nezha D1 board according to http://iso.qa.ubuntu.com/qatracker/milestones/444/builds/275098/testcases/1755/results Hitting a key on the USB keyboard (that was plugged in at boot) results in [ 760.275027] usb 3-1: device descriptor read/64, error -71 [ 761.671031] usb 1-1: device descriptor read/64, error -62 [ 761.975011] usb 1-1: device descriptor read/64, error -62 [ 762.466981] usb 1-1: device descriptor read/64, error -62 [ 762.770995] usb 1-1: device descriptor read/64, error -62 [ 763.514994] usb 1-1: device not accepting address 17, error -62 [ 764.122989] usb 1-1: device not accepting address 18, error -62 [ 764.129829] usb usb1-port1: unable to enumerate USB device lsusb does not show the keyboard: $ lsusb Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-5.19.0-1003-allwinner 5.19.0-1003.3 ProcVersionSignature: Ubuntu 5.19.0-1003.3-allwinner 5.19.7 Uname: Linux 5.19.0-1003-allwinner riscv64 ApportVersion: 2.26.0-0ubuntu2 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230329 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Fri Mar 31 14:31:08 2023 ProcCpuinfoMinimal: processor: 0 hart : 0 isa : rv64imafdc mmu : sv39 uarch: thead,c906 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 SourcePackage: linux-allwinner UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner/+bug/2013743/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036968] Re: Mantic minimized/minimal cloud images do not receive IP address during provisioning
** Description changed: Following a recent change from linux-kvm kernel to linux-generic kernel in the mantic minimized images there is a reproducable bug where a guest VM does not have an IP address assigned as part of cloud-init provisioning. This is easiest to reproduce when emulating arm64 on adm64 host. The bug is a race condition so there could exist fast enough virtualisation on fast enough hardware where this bug is not present but in all my testing I have been able to reproduce. The latest mantic minimized images from http://cloud- images.ubuntu.com/minimal/daily/mantic/ have force initrdless boot and no initrd to fallback to. - This but is not present in the non minimized/base images @ http://cloud- + This bug is not present in the non minimized/base images @ http://cloud- images.ubuntu.com/mantic/ as these boot with initrd with the required drivers present for virtio-net. Reproducer ``` wget -O "launch-qcow2-image-qemu-arm64.sh" https://people.canonical.com/~philroche/20230921-cloud-images-mantic-fail-to-provision/launch-qcow2-image-qemu-arm64.sh chmod +x ./launch-qcow2-image-qemu-arm64.sh wget https://people.canonical.com/~philroche/20230921-cloud-images-mantic-fail-to-provision/livecd.ubuntu-cpc.img ./launch-qcow2-image-qemu-arm64.sh --password passw0rd --image ./livecd.ubuntu-cpc.img ``` You will then be able to log in with user `ubuntu` and password `passw0rd`. You can run `ip a` and see that there is a network interface present (separate to `lo`) but no IP address has been assigned. ``` ubuntu@cloudimg:~$ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 - link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 - inet 127.0.0.1/8 scope host lo -valid_lft forever preferred_lft forever - inet6 ::1/128 scope host -valid_lft forever preferred_lft forever + link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 + inet 127.0.0.1/8 scope host lo + valid_lft forever preferred_lft forever + inet6 ::1/128 scope host + valid_lft forever preferred_lft forever 2: enp0s1: mtu 1500 qdisc noop state DOWN group default qlen 1000 - link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff + link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff ``` This is because when cloud-init is trying to configure network interfaces it doesn't find any so it doesn't configure any. But by the time boot is complete the network interface is present but cloud-init provisioning has already completed. You can verify this by running `sudo cloud-init clean && sudo cloud-init init` You can then see a successfully configured network interface ``` ubuntu@cloudimg:~$ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 - link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 - inet 127.0.0.1/8 scope host lo -valid_lft forever preferred_lft forever - inet6 ::1/128 scope host -valid_lft forever preferred_lft forever + link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 + inet 127.0.0.1/8 scope host lo + valid_lft forever preferred_lft forever + inet6 ::1/128 scope host + valid_lft forever preferred_lft forever 2: enp0s1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 - link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff - inet 10.0.2.15/24 metric 100 brd 10.0.2.255 scope global dynamic enp0s1 -valid_lft 86391sec preferred_lft 86391sec - inet6 fec0::5054:ff:fe12:3456/64 scope site dynamic mngtmpaddr noprefixroute -valid_lft 86393sec preferred_lft 14393sec - inet6 fe80::5054:ff:fe12:3456/64 scope link -valid_lft forever preferred_lft forever + link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff + inet 10.0.2.15/24 metric 100 brd 10.0.2.255 scope global dynamic enp0s1 + valid_lft 86391sec preferred_lft 86391sec + inet6 fec0::5054:ff:fe12:3456/64 scope site dynamic mngtmpaddr noprefixroute + valid_lft 86393sec preferred_lft 14393sec + inet6 fe80::5054:ff:fe12:3456/64 scope link + valid_lft forever preferred_lft forever ``` The bug is also reproducable with amd64 guest on adm64 host on older/slower hardware. The suggested fixes while debugging this issue are: * to include `virtio-net` as a built-in in the mantic generic kernel * understand what needs to change in cloud-init so that it can react to late additions of network interfaces I will file a separate bug against cloud-init to address the race condition on emulated guest/older hardware. ** Description changed: Following a recent change from linux-kvm kernel to linux-generic kernel in the mantic minimized images there is a reproducable bug where a guest VM does not have an IP address assigned as part of cloud-init provisioning. This is easiest
[Kernel-packages] [Bug 1878007] Re: Ubuntu 20.04 freeze on Dell inspiron 7373 when screen is turned off
I'm having same issue, I was never able to solve it, I tried every fix or workaround I found without success. @cccaballero did you manage to solve it? -- 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/1878007 Title: Ubuntu 20.04 freeze on Dell inspiron 7373 when screen is turned off Status in linux package in Ubuntu: Expired Bug description: This issue is happening with Ubuntu 18.04 and 20.04 in a Dell Inspiron 7373. When the screen is turned off (so, the suspend or screen lock features are affected), the system freeze and I need to force the laptop turn off and on again. There are some cases when it turn off the screen without issues, but most of the time it freezes. Even "SysRq REISUB" does not work for rebooting when system crash. I can reproduce the issue using `xset dpms force off`. Initially this bug report was filled thinking it was a suspend issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832144 Syslog or systemd journal does not provide any error information about the crash. "lsb_release -rd" output: Description: Ubuntu 20.04 LTS Release: 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cccaballero 2023 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-06-09 (344 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:58f5 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7373 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=d8203f53-c2e5-4934-8616-0a71507c9190 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-02 (16 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0JW0D6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd09/06/2019:svnDellInc.:pnInspiron7373:pvr:rvnDellInc.:rn0JW0D6:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7373 dmi.product.sku: 07EB dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036802] Re: HDMI not detected on HP Zbook Power 15 G9
I see hehe, sorry here it comes! ** Attachment added: "connections.txt" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2036802/+attachment/5703223/+files/connections.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2036802 Title: HDMI not detected on HP Zbook Power 15 G9 Status in linux-hwe-6.2 package in Ubuntu: Incomplete Bug description: As discussed in this thread: https://gitlab.freedesktop.org/drm/intel/-/issues/8601#note_2092811 On my laptop, HP Zbook Power 15 G9 (i7-12800H), HDMI is not detected. According to the discussion a fix has been implemented in kernel v6.6-rc1. If it's possible for Ubuntu to implement some fix in the current LTS version that would be MUCH helpful and appreciated for me and all other ubuntu users on the same laptop. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.104.05 Sat Aug 19 01:15:15 UTC 2023 GCC version: gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 20 19:25:44 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: evdi/1.14.1, 6.2.0-32-generic, x86_64: installed evdi/1.14.1, 6.2.0-33-generic, x86_64: installed nvidia/535.104.05, 6.2.0-32-generic, x86_64: installed nvidia/535.104.05, 6.2.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:89c0] Subsystem: Hewlett-Packard Company Device [103c:89c1] InstallationDate: Installed on 2023-08-21 (29 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: HP HP ZBook Power 15.6 inch G9 Mobile Workstation PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic root=UUID=8a70988e-02bd-462a-b919-7e3ff4500355 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2023 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: U97 Ver. 01.08.00 dmi.board.name: 89C0 dmi.board.vendor: HP dmi.board.version: KBC Version 11.63.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 17.99 dmi.modalias: dmi:bvnHP:bvrU97Ver.01.08.00:bd06/26/2023:br8.0:efr17.99:svnHP:pnHPZBookPower15.6inchG9MobileWorkstationPC:pvr:rvnHP:rn89C0:rvrKBCVersion11.63.00:cvnHP:ct10:cvr:sku6B867EA#UUW: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Power 15.6 inch G9 Mobile Workstation PC dmi.product.sku: 6B867EA#UUW dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2036802/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036968] Re: Mantic minimized/minimal cloud images do not receive IP address during provisioning
** Changed in: linux (Ubuntu) Milestone: None => ubuntu-23.10 -- 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/2036968 Title: Mantic minimized/minimal cloud images do not receive IP address during provisioning Status in cloud-images: New Status in linux package in Ubuntu: New Bug description: Following a recent change from linux-kvm kernel to linux-generic kernel in the mantic minimized images there is a reproducable bug where a guest VM does not have an IP address assigned as part of cloud-init provisioning. This is easiest to reproduce when emulating arm64 on adm64 host. The bug is a race condition so there could exist fast enough virtualisation on fast enough hardware where this bug is not present but in all my testing I have been able to reproduce. The latest mantic minimized images from http://cloud- images.ubuntu.com/minimal/daily/mantic/ have force initrdless boot and no initrd to fallback to. This bug is not present in the non minimized/base images @ http://cloud-images.ubuntu.com/mantic/ as these boot with initrd with the required drivers present for virtio-net. Reproducer ``` wget -O "launch-qcow2-image-qemu-arm64.sh" https://people.canonical.com/~philroche/20230921-cloud-images-mantic-fail-to-provision/launch-qcow2-image-qemu-arm64.sh chmod +x ./launch-qcow2-image-qemu-arm64.sh wget https://people.canonical.com/~philroche/20230921-cloud-images-mantic-fail-to-provision/livecd.ubuntu-cpc.img ./launch-qcow2-image-qemu-arm64.sh --password passw0rd --image ./livecd.ubuntu-cpc.img ``` You will then be able to log in with user `ubuntu` and password `passw0rd`. You can run `ip a` and see that there is a network interface present (separate to `lo`) but no IP address has been assigned. ``` ubuntu@cloudimg:~$ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s1: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff ``` This is because when cloud-init-local.service is trying to configure network interfaces it doesn't find any so it doesn't configure any. But by the time boot is complete the network interface is present but cloud-init provisioning has already completed. You can verify this by running `sudo cloud-init clean && sudo cloud- init init` You can then see a successfully configured network interface ``` ubuntu@cloudimg:~$ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff inet 10.0.2.15/24 metric 100 brd 10.0.2.255 scope global dynamic enp0s1 valid_lft 86391sec preferred_lft 86391sec inet6 fec0::5054:ff:fe12:3456/64 scope site dynamic mngtmpaddr noprefixroute valid_lft 86393sec preferred_lft 14393sec inet6 fe80::5054:ff:fe12:3456/64 scope link valid_lft forever preferred_lft forever ``` The bug is also reproducable with amd64 guest on adm64 host on older/slower hardware. The suggested fixes while debugging this issue are: * to include `virtio-net` as a built-in in the mantic generic kernel * understand what needs to change in cloud-init so that it can react to late additions of network interfaces I will file a separate bug against cloud-init to address the race condition on emulated guest/older hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2036968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025079] Re: [amdgpu] Multiple kernel errors and reboot
I forgot to add, this usually only happens when sharing screen. -- 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/2025079 Title: [amdgpu] Multiple kernel errors and reboot Status in linux package in Ubuntu: Confirmed Bug description: Preconditions: - Connect external monitor (not sure if necessary) - Have a Google Chrome o Microsoft Edge installed (did not test it with Chromium and Firefox) - Have access to at least 2 Gmail accounts to be able to use Meet (did not yet experience it with other videoconference systems) Steps to reproduce: - have a Google Meet call with someone else (does not reproduce when only I join the meeting) - click share the screen - select entire monitor - select external monitor - [new] press "Super" key to open Activities overview. Might need to rty it 2-3 times Symptomps: - Entire Wayland session freezes and after few stutters the entire system reboots Does not reproduce after uncommenting WaylandEnable=false in /etc/gdm3/custom.conf. Pretty certain that amdgpu is the culprit as never experienced this on Intel/Nvidia. Attached journal from the boot that ended in system crash. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 26 17:57:32 2023 InstallationDate: Installed on 2023-04-13 (74 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: mutter UpgradeStatus: Upgraded to lunar on 2023-04-21 (65 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-04-13 (145 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5415 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-32-generic N/A linux-backports-modules-6.2.0-32-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 Tags: lunar wayland-session Uname: Linux 6.2.0-32-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-21 (137 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/13/2023 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0WKFHK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.15.0 dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd02/13/2023:br1.15:svnDellInc.:pnInspiron5415:pvr1.15.0:rvnDellInc.:rn0WKFHK:rvrA00:cvnDellInc.:ct10:cvr1.15.0:sku0A77: dmi.product.family: Inspiron dmi.product.name: Inspiron 5415 dmi.product.sku: 0A77 dmi.product.version: 1.15.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025079/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025079] Re: [amdgpu] Multiple kernel errors and reboot
This happens to me too with both Slack and Google Meet in Chrome. Sometimes just a flashing of screens, sometimes (most) screens all black and with that sometimes complete hangup of the machine, or graphics broken so unusable. I use the evdi driver and displaylink, it might be related. -- 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/2025079 Title: [amdgpu] Multiple kernel errors and reboot Status in linux package in Ubuntu: Confirmed Bug description: Preconditions: - Connect external monitor (not sure if necessary) - Have a Google Chrome o Microsoft Edge installed (did not test it with Chromium and Firefox) - Have access to at least 2 Gmail accounts to be able to use Meet (did not yet experience it with other videoconference systems) Steps to reproduce: - have a Google Meet call with someone else (does not reproduce when only I join the meeting) - click share the screen - select entire monitor - select external monitor - [new] press "Super" key to open Activities overview. Might need to rty it 2-3 times Symptomps: - Entire Wayland session freezes and after few stutters the entire system reboots Does not reproduce after uncommenting WaylandEnable=false in /etc/gdm3/custom.conf. Pretty certain that amdgpu is the culprit as never experienced this on Intel/Nvidia. Attached journal from the boot that ended in system crash. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 26 17:57:32 2023 InstallationDate: Installed on 2023-04-13 (74 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: mutter UpgradeStatus: Upgraded to lunar on 2023-04-21 (65 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-04-13 (145 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5415 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-32-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-32-generic N/A linux-backports-modules-6.2.0-32-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 Tags: lunar wayland-session Uname: Linux 6.2.0-32-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-21 (137 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/13/2023 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0WKFHK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.15.0 dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd02/13/2023:br1.15:svnDellInc.:pnInspiron5415:pvr1.15.0:rvnDellInc.:rn0WKFHK:rvrA00:cvnDellInc.:ct10:cvr1.15.0:sku0A77: dmi.product.family: Inspiron dmi.product.name: Inspiron 5415 dmi.product.sku: 0A77 dmi.product.version: 1.15.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025079/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032933] Re: Mantic (23.10) minimal images increase in memory consumption, port usage and processes running
There is a related bug @ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036968 which might have affected boot speed. -- 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/2032933 Title: Mantic (23.10) minimal images increase in memory consumption, port usage and processes running Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: The Mantic (Ubuntu 23.10) download/qcow2 images available @ https://cloud-images.ubuntu.com/minimal/ are undergoing some big changes prior to 23.10 release in October. This is a devel release so this is the perfect time to be making these changes but we are noticing some changes that were not expected. This bug is to track the unexpected changes and discuss/resolve these. The changes that have been made to mantic minimal: * Move to the linux-generic kernel from the linux-kvm kernel * This also involved removal of the virtio-blk driver, which is the default for QEMU and OpenStack, but this is being restored in an upcoming 6.5 mantic kernel and is being trakced @ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2030745 * Move to using minimal-cloud seed - see https://ubuntu-archive-team.ubuntu.com/seeds/ubuntu.mantic/cloud-minimal * No longer installing Recommends packages * This is during image build only and will not affect any subsequent package installs * No initramfs fallback for boot - only initramfsless boot The latest mantic minimal images are available @ http://cloud- images.ubuntu.com/minimal/daily/mantic/ and are also available in the public clouds. A package name manifest diff can be seen @ https://pastebin.ubuntu.com/p/rRd6STnNmK/ We have had reports of higher memory usage on an idle system, higher number of ports open on an idle system and higher number of process running on a idle system. To help with debugging I have built and uploaded the following images and package manifests to https://people.canonical.com/~philroche/20230824-manticl-minimal- LP2032933/ * 20230618-before-kernel-change-before-seed-change-mantic-minimal-cloudimg-amd64 * Before kernel change and before seed change * 20230824-after-kernel-change-before-seed-change-mantic-minimal-cloudimg-amd64 * After kernel change and before seed change * 20230821.1-after-kernel-change-after-seed-change-mantic-minimal-cloudimg-amd64 * After kernel change and after seed change To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2032933/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035622] Re: Update broke keyboard on a Fujitsu Lifebook
Update: The issue did not persist after upgrading to 6.2.0-33-generic! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2035622 Title: Update broke keyboard on a Fujitsu Lifebook Status in linux-hwe-6.2 package in Ubuntu: New Bug description: After an update that I performed on my Ubuntu 22.04.3 on the 11. of September, the keyboard of my Fujitsu Lifebook (model E5410) stopped working (a USB keyboard however could be used as a temporary workaround). I have brought up this issue in the ask-ubuntu-forum as well: https://askubuntu.com/questions/1485408/keyboard-not-working-after- update Here I was recommended to reach out to you. I do not think this is a hardware issue as the keyboard functions as expected when I enter the GRUB menu or the BIOS. During the update in question my Notebooks Kernel was upgraded to 6.2.0-32 (I think from 5.19.0-50-generic). I have grepped the lines from /va/log/dpkg.log into the file "dpkg_log.txt" and attached here. Other attachments are the ones recommended somewhere on the Ubuntu- wiki, namely: $ uname -a > uname-a.log $ cat /proc/version_signature > version.log $ dmesg > dmesg.log $ sudo lspci -vvnn > lspci-vvnn.log If you need any more information, do not hesitate to contact me. Also, as I am not too knowledgeable on these-hardware-related issues I would appreciate your assessment: is it worthwhile doing a clean reinstall of the OS? For now I have helped myself with a kernel downgrade to 5.19.0-50-generic which fixes the keyboard whenever I need it but is still bumpy (currently no launchpad-, webcam- or sound-functionality). Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2035622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036968] Re: Mantic minimized/minimal cloud images do not receive IP address during provisioning
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2036968 Title: Mantic minimized/minimal cloud images do not receive IP address during provisioning Status in cloud-images: New Status in linux package in Ubuntu: New Bug description: Following a recent change from linux-kvm kernel to linux-generic kernel in the mantic minimized images there is a reproducable bug where a guest VM does not have an IP address assigned as part of cloud-init provisioning. This is easiest to reproduce when emulating arm64 on adm64 host. The bug is a race condition so there could exist fast enough virtualisation on fast enough hardware where this bug is not present but in all my testing I have been able to reproduce. The latest mantic minimized images from http://cloud- images.ubuntu.com/minimal/daily/mantic/ have force initrdless boot and no initrd to fallback to. This bug is not present in the non minimized/base images @ http://cloud-images.ubuntu.com/mantic/ as these boot with initrd with the required drivers present for virtio-net. Reproducer ``` wget -O "launch-qcow2-image-qemu-arm64.sh" https://people.canonical.com/~philroche/20230921-cloud-images-mantic-fail-to-provision/launch-qcow2-image-qemu-arm64.sh chmod +x ./launch-qcow2-image-qemu-arm64.sh wget https://people.canonical.com/~philroche/20230921-cloud-images-mantic-fail-to-provision/livecd.ubuntu-cpc.img ./launch-qcow2-image-qemu-arm64.sh --password passw0rd --image ./livecd.ubuntu-cpc.img ``` You will then be able to log in with user `ubuntu` and password `passw0rd`. You can run `ip a` and see that there is a network interface present (separate to `lo`) but no IP address has been assigned. ``` ubuntu@cloudimg:~$ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s1: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff ``` This is because when cloud-init is trying to configure network interfaces it doesn't find any so it doesn't configure any. But by the time boot is complete the network interface is present but cloud-init provisioning has already completed. You can verify this by running `sudo cloud-init clean && sudo cloud- init init` You can then see a successfully configured network interface ``` ubuntu@cloudimg:~$ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff inet 10.0.2.15/24 metric 100 brd 10.0.2.255 scope global dynamic enp0s1 valid_lft 86391sec preferred_lft 86391sec inet6 fec0::5054:ff:fe12:3456/64 scope site dynamic mngtmpaddr noprefixroute valid_lft 86393sec preferred_lft 14393sec inet6 fe80::5054:ff:fe12:3456/64 scope link valid_lft forever preferred_lft forever ``` The bug is also reproducable with amd64 guest on adm64 host on older/slower hardware. The suggested fixes while debugging this issue are: * to include `virtio-net` as a built-in in the mantic generic kernel * understand what needs to change in cloud-init so that it can react to late additions of network interfaces I will file a separate bug against cloud-init to address the race condition on emulated guest/older hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2036968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland
** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: Confirmed ** Also affects: mutter (Ubuntu Mantic) Importance: High Assignee: Daniel van Vugt (vanvugt) Status: In Progress ** Tags removed: rls-mm-incoming -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland Status in Linux: New Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: In Progress Status in linux source package in Mantic: Confirmed Status in mutter source package in Mantic: In Progress Bug description: I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036742] Re: amdgpu crash on Mantic
Yes it's a KVM of sorts, using Zapper. But apparently this did work before, so a rough bisect with mainline builds will be conducted. -- 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/2036742 Title: amdgpu crash on Mantic Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Booting from USB the latest Mantic Desktop daily image (2023-09-20), just after the initial logs, nothing is displayed on screen. The system is still alive since _autoinstall_ works as intended. Once provisioned, the problem is still present. It seems related to https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2029396 . dmesg attached. [Test Case] Live boot Ubuntu Mantic Desktop canary (2023-09-19) [Where Problems Could Occur] Dell Optiplex 5090 - Intel Core(TM) i7-11700 - Advanced Micro Devices, Inc. [AMD/ATI] - 1002:699f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036963] [NEW] Failed to query (GET_CUR) UVC control 1 on unit 3: -32
Public bug reported: OS: Ubuntu 22.04 IOT LTS (Desktop Variant) Kernel: 5.15.0-1041-intel-iotg I saw these messages in dmesg, which kept repeating. They appear from a connected camera. >From what I checked, on 5.15.x and 6.1.x these messages are reproduced. But in more recent versions this no longer appears. I also checked with 6.4.16, and they don't appear here. I think that some patches should be backported to fix this in 5.15.x/6.1.x. Error in dmesg: [ 33.544105] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 33.563270] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 33.574097] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 33.601145] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 33.613708] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 33.623929] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 33.634310] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 33.946547] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 33.957067] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 33.967461] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 33.977853] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 34.289393] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 34.299890] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 34.812146] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 36.124273] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 37.135203] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 38.146115] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 39.156864] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 40.167860] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 42.179408] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 47.192040] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 48.203038] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 49.213861] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 50.224582] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 53.236352] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 54.247259] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 55.258187] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 56.269120] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 58.280241] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 59.291090] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 60.301797] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 71.315896] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 77.328361] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 78.339034] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 91.354741] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 92.365583] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 100.379191] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 101.390003] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 102.400869] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 103.411702] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 107.423497] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 108.434002] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 110.444780] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 112.455848] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 113.466695] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 114.477536] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 115.488395] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 119.500343] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 120.511291] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit
[Kernel-packages] [Bug 2036951] [NEW] unblock request: please migrate dkms from proposed
Public bug reported: Kernels now use zstd compressed modules. dkms autopkgtest was not expecting that correctly. autopkgtest was adjusted, and uploaded to proposed but did not migrate prior to feature freeze. Please unblock dkms to migrate, to resolve all ongoing dkms failures. The upload in question is https://launchpad.net/ubuntu/+source/dkms/3.0.11-1ubuntu10 ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Affects: dkms (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: dkms (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: dkms (Ubuntu Mantic) Milestone: None => ubuntu-23.10-beta ** Summary changed: - FFe: please migrate dkms from proposed + unblock request: please migrate dkms from proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2036951 Title: unblock request: please migrate dkms from proposed Status in dkms package in Ubuntu: New Status in dkms source package in Mantic: New Bug description: Kernels now use zstd compressed modules. dkms autopkgtest was not expecting that correctly. autopkgtest was adjusted, and uploaded to proposed but did not migrate prior to feature freeze. Please unblock dkms to migrate, to resolve all ongoing dkms failures. The upload in question is https://launchpad.net/ubuntu/+source/dkms/3.0.11-1ubuntu10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2036951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033735] Re: [mantic] New 6.5.0.2 kernel + Intel GPU = no HDMI
Forgot to mention: in Windows 11, on-demand is working with hdmi
monitors.
--
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/2033735
Title:
[mantic] New 6.5.0.2 kernel + Intel GPU = no HDMI
Status in linux package in Ubuntu:
Confirmed
Bug description:
Hi,
Legion laptop with Nvidia.
- Nouveau : no hdmi
- Nvidia 535 dynamic graphics : no HDMI (screen not detected)
- Nvidia 535 discrete graphics : HDMI is detected
So I suppose this bug to be linked to Intel GPU.
All was ok with previous 6.3 kernel.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fthx 3395 F wireplumber
/dev/snd/controlC1: fthx 3395 F wireplumber
/dev/snd/seq:fthx 3390 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2021-09-15 (723 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
RelatedPackageVersions:
linux-restricted-modules-6.5.0-5-generic N/A
linux-backports-modules-6.5.0-5-generic N/A
linux-firmware 20230815.git0e048b06-0ubuntu1
Tags: mantic wayland-session
Uname: Linux 6.5.0-5-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-03-06 (186 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 07/10/2023
dmi.bios.release: 1.54
dmi.bios.vendor: LENOVO
dmi.bios.version: J2CN54WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76461 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion 5 Pro 16IAH7H
dmi.ec.firmware.release: 1.54
dmi.modalias:
dmi:bvnLENOVO:bvrJ2CN54WW:bd07/10/2023:br1.54:efr1.54:svnLENOVO:pn82RF:pvrLegion5Pro16IAH7H:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLegion5Pro16IAH7H:skuLENOVO_MT_82RF_BU_idea_FM_Legion5Pro16IAH7H:
dmi.product.family: Legion 5 Pro 16IAH7H
dmi.product.name: 82RF
dmi.product.sku: LENOVO_MT_82RF_BU_idea_FM_Legion 5 Pro 16IAH7H
dmi.product.version: Legion 5 Pro 16IAH7H
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033735/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029214] Re: pinctrl_emmitsburg module on L-6.2 cause failure to test_095_kernel_symbols_missing_proc_modules in ubuntu_qrt_kernel_security
This is also affecting J-oem-6.5.0-1004.4 on node grumman as well. ** Tags added: 6.5 -- 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/2029214 Title: pinctrl_emmitsburg module on L-6.2 cause failure to test_095_kernel_symbols_missing_proc_modules in ubuntu_qrt_kernel_security Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Lunar: New Bug description: Issue found with 6.2.0-26-generic on node grumman from Intel SDP cloud. Looks like this pinctrl_emmitsburg module does not match the requirement of test_095_kernel_symbols_missing_proc_modules test in ubuntu_qrt_kernel_security. Test failed with: $ sudo python3 ./test-kernel-security.py -v KernelSecurityTest.test_095_kernel_symbols_missing_proc_modules Running test: './test-kernel-security.py' distro: 'Ubuntu 23.04' kernel: '6.2.0-26.26 (Ubuntu 6.2.0-26.26-generic 6.2.13)' arch: 'amd64' init: 'systemd' uid: 0/0 SUDO_USER: 'ubuntu') test_095_kernel_symbols_missing_proc_modules (__main__.KernelSecurityTest.test_095_kernel_symbols_missing_proc_modules) kernel addresses in /proc/modules are zeroed out ... (In 4.15+, /proc/modules always zeroed for users) FAIL == FAIL: test_095_kernel_symbols_missing_proc_modules (__main__.KernelSecurityTest.test_095_kernel_symbols_missing_proc_modules) kernel addresses in /proc/modules are zeroed out -- Traceback (most recent call last): File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py", line 1431, in test_095_kernel_symbols_missing_proc_modules self._check_pK_files(self._095_kernel_symbols_missing_proc_modules, expected=expected) File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py", line 1289, in _check_pK_files test_function(expected_restricted) File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py", line 1329, in _095_kernel_symbols_missing_proc_modules self.assertTrue(os.path.exists(module_path), AssertionError: False is not true : Module text section /sys/module/pinctrl_emmitsburg/sections/.text does not exist -- Ran 1 test in 0.048s FAILED (failures=1) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26 ProcVersionSignature: User Name 6.2.0-26.26-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k6.2.0-26-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: server CloudID: maas CloudName: maas CloudPlatform: maas CloudSerial: 20230524 CloudSubPlatform: seed-dir (http://192.168.102.22:5248/MAAS/metadata/) CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Aug 1 09:04:34 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 11: Dev 2, If 0, Class=Hub, Driver=hub/7p, 480M MachineType: Intel Corporation ArcherCity ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=77d6e516-5dd8-4983-9afa-013505099591 ro apparmor=1 RelatedPackageVersions: linux-restricted-modules-6.2.0-26-generic N/A linux-backports-modules-6.2.0-26-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date:
[Kernel-packages] [Bug 2031845] Re: ubuntu_fan_smoke_test failed with "Error: Unsupported attribute." on J-oem-6.5
This issue still exists with Mantic 6.5.0-5.5, keep this open. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/2031845 Title: ubuntu_fan_smoke_test failed with "Error: Unsupported attribute." on J-oem-6.5 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.5 package in Ubuntu: Invalid Status in ubuntu-fan package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in ubuntu-fan source package in Jammy: Invalid Status in linux source package in Mantic: Incomplete Status in linux-oem-6.5 source package in Mantic: Invalid Status in ubuntu-fan source package in Mantic: Invalid Bug description: Issue found with J-oem-6.5.0-1002 The ubuntu_fan_smoke_test failed with: Error: Unsupported attribute. $ fanatic enable-fan -u 172.17.0.0/16 -o 250.0.0.0/8 configuring fan underlay:172.17.0.0/16 overlay:250.0.0.0/8 Error: Unsupported attribute. /usr/sbin/fanctl: ip link add ftun0 type vxlan id 16384000 dev docker0 dstport 0 local 172.17.0.1 fan-map 250.0.0.0/8:172.17.0.0/16 /usr/sbin/fanctl: WARNING: ftun0: failed to configure address translation RTNETLINK answers: Cannot assign requested address iptables v1.8.7 (nf_tables): Chain 'fan-egress' does not exist Try `iptables -h' or 'iptables --help' for more information. iptables: Bad rule (does a matching rule exist in that chain?). iptables: Bad rule (does a matching rule exist in that chain?). iptables: No chain/target/match by that name. rm: cannot remove '/run/ubuntu-fan/nat-core': No such file or directory /usr/sbin/fanctl: /etc/network/fan:40 172.17.0.0/16 250.0.0.0/8 -- failed err=1 /usr/sbin/fanatic: unable to bring fan up, unable to configure It is the ip command execute in fanctl script (called by fanatic) that trigger this "Error: Unsupported attribute." error: $ ip link add ftun0 type vxlan id 16384000 dev docker0 dstport 0 local 172.17.0.1 fan-map 250.0.0.0/8:172.17.0.0/16 Error: Unsupported attribute. $ ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens3: mtu 8942 qdisc fq_codel state UP group default qlen 1000 link/ether fa:16:3e:b9:7c:28 brd ff:ff:ff:ff:ff:ff altname enp0s3 inet 10.134.252.19/24 metric 100 brd 10.134.252.255 scope global dynamic ens3 valid_lft 33248sec preferred_lft 33248sec inet6 fe80::f816:3eff:feb9:7c28/64 scope link valid_lft forever preferred_lft forever 3: lxcbr0: mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 00:16:3e:00:00:00 brd ff:ff:ff:ff:ff:ff inet 10.0.3.1/24 brd 10.0.3.255 scope global lxcbr0 valid_lft forever preferred_lft forever 4: docker0: mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:52:9f:ef:1d brd ff:ff:ff:ff:ff:ff inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0 valid_lft forever preferred_lft forever To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2031845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031845] Re: ubuntu_fan_smoke_test failed with "Error: Unsupported attribute." on J-oem-6.5
This issue does not exist with J-oem-6.5.0-1004.4 anymore. ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => Fix Released ** Changed in: ubuntu-fan (Ubuntu Jammy) Status: New => Invalid ** Changed in: ubuntu-fan (Ubuntu Mantic) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/2031845 Title: ubuntu_fan_smoke_test failed with "Error: Unsupported attribute." on J-oem-6.5 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.5 package in Ubuntu: Invalid Status in ubuntu-fan package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in ubuntu-fan source package in Jammy: Invalid Status in linux source package in Mantic: Incomplete Status in linux-oem-6.5 source package in Mantic: Invalid Status in ubuntu-fan source package in Mantic: Invalid Bug description: Issue found with J-oem-6.5.0-1002 The ubuntu_fan_smoke_test failed with: Error: Unsupported attribute. $ fanatic enable-fan -u 172.17.0.0/16 -o 250.0.0.0/8 configuring fan underlay:172.17.0.0/16 overlay:250.0.0.0/8 Error: Unsupported attribute. /usr/sbin/fanctl: ip link add ftun0 type vxlan id 16384000 dev docker0 dstport 0 local 172.17.0.1 fan-map 250.0.0.0/8:172.17.0.0/16 /usr/sbin/fanctl: WARNING: ftun0: failed to configure address translation RTNETLINK answers: Cannot assign requested address iptables v1.8.7 (nf_tables): Chain 'fan-egress' does not exist Try `iptables -h' or 'iptables --help' for more information. iptables: Bad rule (does a matching rule exist in that chain?). iptables: Bad rule (does a matching rule exist in that chain?). iptables: No chain/target/match by that name. rm: cannot remove '/run/ubuntu-fan/nat-core': No such file or directory /usr/sbin/fanctl: /etc/network/fan:40 172.17.0.0/16 250.0.0.0/8 -- failed err=1 /usr/sbin/fanatic: unable to bring fan up, unable to configure It is the ip command execute in fanctl script (called by fanatic) that trigger this "Error: Unsupported attribute." error: $ ip link add ftun0 type vxlan id 16384000 dev docker0 dstport 0 local 172.17.0.1 fan-map 250.0.0.0/8:172.17.0.0/16 Error: Unsupported attribute. $ ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens3: mtu 8942 qdisc fq_codel state UP group default qlen 1000 link/ether fa:16:3e:b9:7c:28 brd ff:ff:ff:ff:ff:ff altname enp0s3 inet 10.134.252.19/24 metric 100 brd 10.134.252.255 scope global dynamic ens3 valid_lft 33248sec preferred_lft 33248sec inet6 fe80::f816:3eff:feb9:7c28/64 scope link valid_lft forever preferred_lft forever 3: lxcbr0: mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 00:16:3e:00:00:00 brd ff:ff:ff:ff:ff:ff inet 10.0.3.1/24 brd 10.0.3.255 scope global lxcbr0 valid_lft forever preferred_lft forever 4: docker0: mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:52:9f:ef:1d brd ff:ff:ff:ff:ff:ff inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0 valid_lft forever preferred_lft forever To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2031845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032704] Re: Fix panel brightness issues on HP laptops
linux-oem-22.04c 6.1.0.1022.22 in jammy-updates contains the fix. https://changelogs.ubuntu.com/changelogs/pool/main/l/linux- oem-6.1/linux-oem-6.1_6.1.0-1022.22/changelog -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2032704 Title: Fix panel brightness issues on HP laptops Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Brightness can't be changed or can only be changed once on some modern HP laptops. [Fix] BIOS folks identified the issue where the ACPI _PS0 method isn't called for the panel device. On Windows the method is being invoked. This is due to missing _PSC, but since Windows is the de facto spec, we have to perform the same to make the device functional. [Test] Once the fix is applied, the brightness can be changed smoothly. [Where problems could occur] According to BIOS folks, Windows also invokes _PS3 for sleep and shutdown, we need to tackle that in the future. Right now not calling _PS3 has no ill-effect, per BIOS folks. X-HWE-Bug: Bug #2032704 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2032704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036723] Re: package linux-image-6.2.0-33-generic 6.2.0-33.33+1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
News, the ethernet card is not functioning after manually installed linux-headers-6.2.0-33-generic 3:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2036723 Title: package linux-image-6.2.0-33-generic 6.2.0-33.33+1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 Status in dkms package in Ubuntu: Confirmed Bug description: No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 linux-image-6.2.0-33-generic: Installato: 6.2.0-33.33+1 Candidato: 6.2.0-33.33+1 Tabella versione: *** 6.2.0-33.33+1 500 500 http://it.archive.ubuntu.com/ubuntu lunar-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu lunar-security/main amd64 Packages 100 /var/lib/dpkg/status Apport has requested to send these information. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-33-generic 6.2.0-33.33+1 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lan2980 F wireplumber /dev/snd/controlC1: lan2980 F wireplumber /dev/snd/controlC2: lan2980 F wireplumber /dev/snd/seq:lan2973 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Wed Sep 20 10:57:32 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2022-10-21 (333 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. OptiPlex 3050 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic root=UUID=cb6f0c3d-cb89-4cf8-ad83-b78ac3375a56 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.4, python-is-python3, 3.11.1-3 RelatedPackageVersions: grub-pc 2.06-2ubuntu16 RfKill: SourcePackage: dkms Title: package linux-image-6.2.0-33-generic 6.2.0-33.33+1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: Upgraded to lunar on 2023-05-12 (130 days ago) dmi.bios.date: 04/05/2023 dmi.bios.release: 1.25 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.25.0 dmi.board.name: 0W0CHX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.25.0:bd04/05/2023:br1.25:svnDellInc.:pnOptiPlex3050:pvr:rvnDellInc.:rn0W0CHX:rvrA00:cvnDellInc.:ct3:cvr:sku07A3: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 3050 dmi.product.sku: 07A3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2036723/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032933] Re: Mantic (23.10) minimal images increase in memory consumption, port usage and processes running
@paelzer agreed. Good plan. -- 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/2032933 Title: Mantic (23.10) minimal images increase in memory consumption, port usage and processes running Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: The Mantic (Ubuntu 23.10) download/qcow2 images available @ https://cloud-images.ubuntu.com/minimal/ are undergoing some big changes prior to 23.10 release in October. This is a devel release so this is the perfect time to be making these changes but we are noticing some changes that were not expected. This bug is to track the unexpected changes and discuss/resolve these. The changes that have been made to mantic minimal: * Move to the linux-generic kernel from the linux-kvm kernel * This also involved removal of the virtio-blk driver, which is the default for QEMU and OpenStack, but this is being restored in an upcoming 6.5 mantic kernel and is being trakced @ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2030745 * Move to using minimal-cloud seed - see https://ubuntu-archive-team.ubuntu.com/seeds/ubuntu.mantic/cloud-minimal * No longer installing Recommends packages * This is during image build only and will not affect any subsequent package installs * No initramfs fallback for boot - only initramfsless boot The latest mantic minimal images are available @ http://cloud- images.ubuntu.com/minimal/daily/mantic/ and are also available in the public clouds. A package name manifest diff can be seen @ https://pastebin.ubuntu.com/p/rRd6STnNmK/ We have had reports of higher memory usage on an idle system, higher number of ports open on an idle system and higher number of process running on a idle system. To help with debugging I have built and uploaded the following images and package manifests to https://people.canonical.com/~philroche/20230824-manticl-minimal- LP2032933/ * 20230618-before-kernel-change-before-seed-change-mantic-minimal-cloudimg-amd64 * Before kernel change and before seed change * 20230824-after-kernel-change-before-seed-change-mantic-minimal-cloudimg-amd64 * After kernel change and before seed change * 20230821.1-after-kernel-change-after-seed-change-mantic-minimal-cloudimg-amd64 * After kernel change and after seed change To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2032933/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995511] Re: net-build failed in ubuntu_kernel_selftests with 6.1 kernel
We don't support J-oem-6.0 anymore, this bug can be closed. ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/1995511 Title: net-build failed in ubuntu_kernel_selftests with 6.1 kernel Status in ubuntu-kernel-tests: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Bug description: Issue found with J-oem-6.0.0-1007.7 This is not a regression, issue exists before this kernel. make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include reuseport_bpf.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include reuseport_bpf_cpu.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf_cpu gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include reuseport_bpf_numa.c -lnuma -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf_numa gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include reuseport_dualstack.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_dualstack gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include reuseaddr_conflict.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseaddr_conflict gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include tls.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/tls make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' stderr: tls.c:32:50: error: field ‘sm4gcm’ has incomplete type 32 | struct tls12_crypto_info_sm4_gcm sm4gcm; | ^~ tls.c:33:50: error: field ‘sm4ccm’ has incomplete type 33 | struct tls12_crypto_info_sm4_ccm sm4ccm; | ^~ tls.c: In function ‘tls_crypto_info_init’: tls.c:56:14: error: ‘TLS_CIPHER_SM4_GCM’ undeclared (first use in this function); did you mean ‘TLS_CIPHER_AES_GCM_256’? 56 | case TLS_CIPHER_SM4_GCM: | ^~ | TLS_CIPHER_AES_GCM_256 tls.c:56:14: note: each undeclared identifier is reported only once for each function it appears in tls.c:57:37: error: invalid application of ‘sizeof’ to incomplete type ‘struct tls12_crypto_info_sm4_gcm’ 57 | tls12->len = sizeof(struct tls12_crypto_info_sm4_gcm); | ^~ tls.c:61:14: error: ‘TLS_CIPHER_SM4_CCM’ undeclared (first use in this function); did you mean ‘TLS_CIPHER_AES_CCM_128’? 61 | case TLS_CIPHER_SM4_CCM: | ^~ | TLS_CIPHER_AES_CCM_128 tls.c:62:37: error: invalid application of ‘sizeof’ to incomplete type ‘struct tls12_crypto_info_sm4_ccm’ 62 | tls12->len = sizeof(struct tls12_crypto_info_sm4_ccm); | ^~ tls.c: At top level: tls.c:268:24: error: ‘TLS_CIPHER_SM4_GCM’ undeclared here (not in a function); did you mean ‘TLS_CIPHER_AES_GCM_256’? 268 | .cipher_type = TLS_CIPHER_SM4_GCM, |^~ |TLS_CIPHER_AES_GCM_256 tls.c:274:24: error: ‘TLS_CIPHER_SM4_CCM’ undeclared here (not in a function); did you mean ‘TLS_CIPHER_AES_CCM_128’? 274 | .cipher_type =
[Kernel-packages] [Bug 1995511] Re: net-build failed in ubuntu_kernel_selftests with 6.1 kernel
This issue has gone in J-oem-6.1 6.1.0-1023.23 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/1995511 Title: net-build failed in ubuntu_kernel_selftests with 6.1 kernel Status in ubuntu-kernel-tests: New Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Confirmed Bug description: Issue found with J-oem-6.0.0-1007.7 This is not a regression, issue exists before this kernel. make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include reuseport_bpf.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include reuseport_bpf_cpu.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf_cpu gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include reuseport_bpf_numa.c -lnuma -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf_numa gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include reuseport_dualstack.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_dualstack gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include reuseaddr_conflict.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseaddr_conflict gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include tls.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/tls make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' stderr: tls.c:32:50: error: field ‘sm4gcm’ has incomplete type 32 | struct tls12_crypto_info_sm4_gcm sm4gcm; | ^~ tls.c:33:50: error: field ‘sm4ccm’ has incomplete type 33 | struct tls12_crypto_info_sm4_ccm sm4ccm; | ^~ tls.c: In function ‘tls_crypto_info_init’: tls.c:56:14: error: ‘TLS_CIPHER_SM4_GCM’ undeclared (first use in this function); did you mean ‘TLS_CIPHER_AES_GCM_256’? 56 | case TLS_CIPHER_SM4_GCM: | ^~ | TLS_CIPHER_AES_GCM_256 tls.c:56:14: note: each undeclared identifier is reported only once for each function it appears in tls.c:57:37: error: invalid application of ‘sizeof’ to incomplete type ‘struct tls12_crypto_info_sm4_gcm’ 57 | tls12->len = sizeof(struct tls12_crypto_info_sm4_gcm); | ^~ tls.c:61:14: error: ‘TLS_CIPHER_SM4_CCM’ undeclared (first use in this function); did you mean ‘TLS_CIPHER_AES_CCM_128’? 61 | case TLS_CIPHER_SM4_CCM: | ^~ | TLS_CIPHER_AES_CCM_128 tls.c:62:37: error: invalid application of ‘sizeof’ to incomplete type ‘struct tls12_crypto_info_sm4_ccm’ 62 | tls12->len = sizeof(struct tls12_crypto_info_sm4_ccm); | ^~ tls.c: At top level: tls.c:268:24: error: ‘TLS_CIPHER_SM4_GCM’ undeclared here (not in a function); did you mean ‘TLS_CIPHER_AES_GCM_256’? 268 | .cipher_type = TLS_CIPHER_SM4_GCM, |^~ |TLS_CIPHER_AES_GCM_256 tls.c:274:24: error: ‘TLS_CIPHER_SM4_CCM’ undeclared here (not in a function); did you mean ‘TLS_CIPHER_AES_CCM_128’? 274 | .cipher_type = TLS_CIPHER_SM4_CCM, |^~ |TLS_CIPHER_AES_CCM_128 tls.c: In function ‘tls_setup’: tls.c:329:54: error:
[Kernel-packages] [Bug 1950792] Re: No boot possible - Cannot open root device
We suspect that on the affected systems the length of the kernel options cmdline exceeds the allowed maximum. Would it be possible to share the kernel options MAAS sends for machines that fail to deploy this way? The kernel options could be retrieved using IPMI console. ** Changed in: maas Status: Triaged => 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/1950792 Title: No boot possible - Cannot open root device Status in MAAS: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: MaaS cannot boot on my X11DPi-NT and will therefore fail to commission. It will instantly fail after grub. It will fail to boot saying that is not able to open root device. I even tried supplying the squashfs via python on a different port as the url is somehow cut off a bit, but to no avail. The python webserver doesn't even see any connection try. ( custom kernel params: root=squash:http://10.0.33.253:8080/squashfs python webserver: python3 -m http.server 8080) Steps to reproduce: 1. Setup maas ;) 2. Try to commision server 3. See the kernel and initrd download fly by 4. Boom kernel panic Hardware: Supermicro X11DPi-NT with UEFI http Networkboot enabled NIC: Intel X722 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1950792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver
** Changed in: mutter Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-495 in Ubuntu. https://bugs.launchpad.net/bugs/1959888 Title: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver Status in Mutter: Fix Released Status in OEM Priority Project: Fix Released Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-495 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-510 package in Ubuntu: Won't Fix Bug description: When an external display is connected to my laptop, running Ubuntu 22.04, the display is detected and I am sent to the login screen. After logging in again, the display is not running, although the primary laptop display works fine. The external monitor is looking for connection in that moment, which it never founds. The bug is tested on two Samsung monitors: S24R350FHUXEN and S22F350FHU. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 495.46 Wed Oct 27 16:31:33 UTC 2021 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-14ubuntu1) ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 3 13:25:04 2022 DistUpgraded: 2022-01-13 15:37:13,056 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/495.46, 5.15.0-17-generic, x86_64: installed nvidia/495.46, 5.15.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:086f] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:086f] InstallationDate: Installed on 2021-09-09 (146 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. G3 3579 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-01-13 (20 days ago) dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. nvidia-settings: ERROR: Unable to find display on any available system ERROR: Unable to find display on any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1959888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2030680] Re: AMD 6800h internal graphics: flickering white screen
** Changed in: linux Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2030680 Title: AMD 6800h internal graphics: flickering white screen Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: New Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: I am getting a flickering white screen occasionally. I have an Alienware M17 R5 AMD with a Ryzen 6800h CPU and an nvidia RTX 3070 Ti dedicated CPU. I'm getting a constant flickering white screen. According to a web search, this could be fixed in 6.2 with the kernel option amdgpu.sg_display=0. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-oem-22.04c 6.1.0.1017.17 ProcVersionSignature: Ubuntu 6.1.0-1017.17-oem 6.1.34 Uname: Linux 6.1.0-1017-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Aug 7 22:27:51 2023 InstallationDate: Installed on 2017-10-23 (2114 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: linux-meta-oem-6.1 UpgradeStatus: Upgraded to jammy on 2022-12-05 (245 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2030680/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034088] Re: 4k white screen on kernel-6.20 with AMD7950x
** Changed in: linux Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034088 Title: 4k white screen on kernel-6.20 with AMD7950x Status in Linux: Fix Released Status in linux-hwe-6.2 package in Ubuntu: New Bug description: 1. AMD7950X, without any other gpu 2. 4k display 3. if kernel.version >= 6.14 => the 4k display white screen ps1: https://gitlab.freedesktop.org/drm/amd/-/issues/2354 ps2: this bug has occured long time ago, but amd never fix it, so i can not upgrade my ubuntu kernel version to default 6.20 for ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-83.92-generic 5.15.116 Uname: Linux 5.15.0-83-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Sep 5 10:46:23 2023 DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:164e] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8877] InstallationDate: Installed on 2023-07-31 (35 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-83-generic root=UUID=656f1bf0-3f83-44eb-9793-47a2aeaa819a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2023-08-30 (5 days ago) dmi.bios.date: 07/28/2023 dmi.bios.release: 16.36 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1636 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING B650M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1636:bd07/28/2023:br16.36:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB650M-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036802] Re: HDMI not detected on HP Zbook Power 15 G9
That's correct, it silently produces a text file. Please attach that text file here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2036802 Title: HDMI not detected on HP Zbook Power 15 G9 Status in linux-hwe-6.2 package in Ubuntu: Incomplete Bug description: As discussed in this thread: https://gitlab.freedesktop.org/drm/intel/-/issues/8601#note_2092811 On my laptop, HP Zbook Power 15 G9 (i7-12800H), HDMI is not detected. According to the discussion a fix has been implemented in kernel v6.6-rc1. If it's possible for Ubuntu to implement some fix in the current LTS version that would be MUCH helpful and appreciated for me and all other ubuntu users on the same laptop. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.104.05 Sat Aug 19 01:15:15 UTC 2023 GCC version: gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 20 19:25:44 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: evdi/1.14.1, 6.2.0-32-generic, x86_64: installed evdi/1.14.1, 6.2.0-33-generic, x86_64: installed nvidia/535.104.05, 6.2.0-32-generic, x86_64: installed nvidia/535.104.05, 6.2.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:89c0] Subsystem: Hewlett-Packard Company Device [103c:89c1] InstallationDate: Installed on 2023-08-21 (29 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: HP HP ZBook Power 15.6 inch G9 Mobile Workstation PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic root=UUID=8a70988e-02bd-462a-b919-7e3ff4500355 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2023 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: U97 Ver. 01.08.00 dmi.board.name: 89C0 dmi.board.vendor: HP dmi.board.version: KBC Version 11.63.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 17.99 dmi.modalias: dmi:bvnHP:bvrU97Ver.01.08.00:bd06/26/2023:br8.0:efr17.99:svnHP:pnHPZBookPower15.6inchG9MobileWorkstationPC:pvr:rvnHP:rn89C0:rvrKBCVersion11.63.00:cvnHP:ct10:cvr:sku6B867EA#UUW: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Power 15.6 inch G9 Mobile Workstation PC dmi.product.sku: 6B867EA#UUW dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2036802/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036802] Re: HDMI not detected on HP Zbook Power 15 G9
Command grep . /sys/class/drm/*/status > connections.txt returns nothing. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2036802 Title: HDMI not detected on HP Zbook Power 15 G9 Status in linux-hwe-6.2 package in Ubuntu: Incomplete Bug description: As discussed in this thread: https://gitlab.freedesktop.org/drm/intel/-/issues/8601#note_2092811 On my laptop, HP Zbook Power 15 G9 (i7-12800H), HDMI is not detected. According to the discussion a fix has been implemented in kernel v6.6-rc1. If it's possible for Ubuntu to implement some fix in the current LTS version that would be MUCH helpful and appreciated for me and all other ubuntu users on the same laptop. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.104.05 Sat Aug 19 01:15:15 UTC 2023 GCC version: gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 20 19:25:44 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: evdi/1.14.1, 6.2.0-32-generic, x86_64: installed evdi/1.14.1, 6.2.0-33-generic, x86_64: installed nvidia/535.104.05, 6.2.0-32-generic, x86_64: installed nvidia/535.104.05, 6.2.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:89c0] Subsystem: Hewlett-Packard Company Device [103c:89c1] InstallationDate: Installed on 2023-08-21 (29 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: HP HP ZBook Power 15.6 inch G9 Mobile Workstation PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic root=UUID=8a70988e-02bd-462a-b919-7e3ff4500355 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2023 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: U97 Ver. 01.08.00 dmi.board.name: 89C0 dmi.board.vendor: HP dmi.board.version: KBC Version 11.63.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 17.99 dmi.modalias: dmi:bvnHP:bvrU97Ver.01.08.00:bd06/26/2023:br8.0:efr17.99:svnHP:pnHPZBookPower15.6inchG9MobileWorkstationPC:pvr:rvnHP:rn89C0:rvrKBCVersion11.63.00:cvnHP:ct10:cvr:sku6B867EA#UUW: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Power 15.6 inch G9 Mobile Workstation PC dmi.product.sku: 6B867EA#UUW dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2036802/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970291] Re: [nvidia] Secondary monitor performance is slow on an Nvidia hybrid system in Wayland sessions
** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** No longer affects: nvidia-graphics-drivers-525 (Ubuntu) ** Changed in: mutter (Ubuntu) Status: Triaged => In Progress ** Changed in: mutter (Ubuntu) Importance: High => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/1970291 Title: [nvidia] Secondary monitor performance is slow on an Nvidia hybrid system in Wayland sessions Status in GNOME Shell: New Status in Mutter: Fix Released Status in mutter package in Ubuntu: In Progress Bug description: In session with Wayland the Nvidia driver settings do not load. And there is a sluggishness when opening apps, show applications menu, maximize, changing workspace, resize, changing monitor windows etc. When in an Xorg session the Nvidia settings load correctly and the performance is satisfactory. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 25 21:18:08 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:2086] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation TU116M [GeForce GTX 1660 Ti Mobile] [8086:2086] InstallationDate: Installed on 2022-04-24 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: Avell High Performance A60 MUV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=894cb598-7172-481c-a449-3133b8f226e5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2020 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QCCFL357.0122.2020.0911.1520 dmi.board.name: Avell High Performance dmi.board.vendor: Avell High Performance dmi.chassis.type: 10 dmi.chassis.vendor: Avell High Performance dmi.chassis.version: 1.0 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnIntelCorp.:bvrQCCFL357.0122.2020.0911.1520:bd09/11/2020:br5.13:efr1.25:svnAvellHighPerformance:pnA60MUV:pvr:rvnAvellHighPerformance:rnAvellHighPerformance:rvr:cvnAvellHighPerformance:ct10:cvr1.0:skuA60MUV: dmi.product.family: A60 MUV dmi.product.name: A60 MUV dmi.product.sku: A60 MUV dmi.sys.vendor: Avell High Performance 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/gnome-shell/+bug/1970291/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036869] Re: package linux-image-6.2.0-33-generic 6.2.0-33.33+1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2036869 Title: package linux-image-6.2.0-33-generic 6.2.0-33.33+1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 Status in dkms package in Ubuntu: New Bug description: Ubuntu popped up with a message regarding the bug ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-33-generic 6.2.0-33.33+1 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: willem 2896 F wireplumber /dev/snd/controlC1: willem 2896 F wireplumber /dev/snd/seq:willem 2892 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Sep 21 08:00:50 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2022-10-21 (334 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: ASUSTeK COMPUTER INC. G752VM ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic root=UUID=9ff90b05-46f4-428b-adbd-875a3dc2cc0c ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: dkms Title: package linux-image-6.2.0-33-generic 6.2.0-33.33+1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G752VM.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G752VM 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.:bvrG752VM.308:bd04/24/2019:br5.11:svnASUSTeKCOMPUTERINC.:pnG752VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: G dmi.product.name: G752VM dmi.product.sku: ASUS-NotebookSKU 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/dkms/+bug/2036869/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036869] [NEW] package linux-image-6.2.0-33-generic 6.2.0-33.33+1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Public bug reported: Ubuntu popped up with a message regarding the bug ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-33-generic 6.2.0-33.33+1 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: willem 2896 F wireplumber /dev/snd/controlC1: willem 2896 F wireplumber /dev/snd/seq:willem 2892 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Sep 21 08:00:50 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2022-10-21 (334 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: ASUSTeK COMPUTER INC. G752VM ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic root=UUID=9ff90b05-46f4-428b-adbd-875a3dc2cc0c ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: dkms Title: package linux-image-6.2.0-33-generic 6.2.0-33.33+1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G752VM.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G752VM 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.:bvrG752VM.308:bd04/24/2019:br5.11:svnASUSTeKCOMPUTERINC.:pnG752VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: G dmi.product.name: G752VM dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2036869 Title: package linux-image-6.2.0-33-generic 6.2.0-33.33+1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 Status in dkms package in Ubuntu: New Bug description: Ubuntu popped up with a message regarding the bug ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-33-generic 6.2.0-33.33+1 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: willem 2896 F wireplumber /dev/snd/controlC1: willem 2896 F wireplumber /dev/snd/seq:willem 2892 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Sep 21 08:00:50 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2022-10-21 (334 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: ASUSTeK COMPUTER INC. G752VM ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic root=UUID=9ff90b05-46f4-428b-adbd-875a3dc2cc0c ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: dkms Title: package linux-image-6.2.0-33-generic 6.2.0-33.33+1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G752VM.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G752VM 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.:bvrG752VM.308:bd04/24/2019:br5.11:svnASUSTeKCOMPUTERINC.:pnG752VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: G dmi.product.name: G752VM dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to:
