[Kernel-packages] [Bug 1971576] Re: SATA device hot plug regression on AMD EYPC (Asus) server
For Rome, it is the same as Melian which the 20.04.4 kernel 5.4.0-42-generic can work with hotplug, while kernel 5.4.0-109-generic does't. -- 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 EYPC (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 1971432] Re: HP EliteBook 830 G8 Notebook MAC Address pass through doesn't work in Ubuntu 22.04
Looks like the MAC address is in ACPI table 'RTMA'. Without HP's help we can't do much here. ** Changed in: linux (Ubuntu) Importance: Undecided => Wishlist -- 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/1971432 Title: HP EliteBook 830 G8 Notebook MAC Address pass through doesn't work in Ubuntu 22.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi Title is self-explanatory I hope OS: Ubuntu 22.04 LTS x86_64 Host: HP EliteBook 830 G8 Notebook PC Ubuntu 5.15.0-27.28-generic 5.15.30 No problem with eth network services except that only the MAC address of the (HP) network adaptator is seen and not the internal MAC address BIOS MAC passthrough checked and tested with the automatic and custom values / no success. Tested and ok with Windows10 (double boot) Of course, manual configuration is ok via : ifconfig enx606d3cf22eb5 hw ether «MAC internal value» Firmware seems to be uptodate. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: estas 2889 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-02 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: HP HP EliteBook 830 G8 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=5cb2b369-be8f-4241-b514-acda51558628 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/11/2022 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: T76 Ver. 01.08.00 dmi.board.name: 880D dmi.board.vendor: HP dmi.board.version: KBC Version 30.37.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 48.55 dmi.modalias: dmi:bvnHP:bvrT76Ver.01.08.00:bd01/11/2022:br8.0:efr48.55:svnHP:pnHPEliteBook830G8NotebookPC:pvr:rvnHP:rn880D:rvrKBCVersion30.37.00:cvnHP:ct10:cvr:sku26D50AV: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 830 G8 Notebook PC dmi.product.sku: 26D50AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971432/+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 1960213] Re: Kernel Panic on linux-image-5.15.0-18-generic
Can you please attach `dpkg -l | grep 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/1960213
Title:
Kernel Panic on linux-image-5.15.0-18-generic
Status in linux package in Ubuntu:
Confirmed
Bug description:
Hello. Get a Kernel Panic on linux-image-5.15.0-18-generic
The same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957012
On 5.13.0-29-generic boot successfully.
Laptop: Lenovo
Model: 20RA002SRT
Stack trace in attached images.
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.13.0-29-generic.
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: CX8070 Analog [CX8070 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: grid 2375 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xb131c000 irq 149'
Mixer name : 'Conexant CX8070'
Components : 'HDA:14f11f86,17aa5079,00100100
HDA:8086280b,80860101,0010'
Controls : 55
Simple ctrls : 14
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
DistroRelease: Ubuntu 20.04
MachineType: LENOVO 20RA002SRT
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-29-generic
root=/dev/mapper/vg_core-sys ro ipv6.disable=1 quiet splash iommu=soft
resume=/dev/vg_core/sys resume_offset=34816 crashkernel=512M-:192M vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-29.32~20.04.1-generic 5.13.19
RelatedPackageVersions:
linux-restricted-modules-5.13.0-29-generic N/A
linux-backports-modules-5.13.0-29-generic N/A
linux-firmware 1.187.26
Tags: focal
Uname: Linux 5.13.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: dialout docker plugdev tty uucp vboxusers wireshark
WifiSyslog:
_MarkForUpload: True
dmi.bios.date: 09/15/2021
dmi.bios.release: 1.19
dmi.bios.vendor: LENOVO
dmi.bios.version: R16ET33W (1.19 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20RA002SRT
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.13
dmi.modalias:
dmi:bvnLENOVO:bvrR16ET33W(1.19):bd09/15/2021:br1.19:efr1.13:svnLENOVO:pn20RA002SRT:pvrThinkPadE14:rvnLENOVO:rn20RA002SRT:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20RA_BU_SMB_FM_ThinkPadE14:
dmi.product.family: ThinkPad E14
dmi.product.name: 20RA002SRT
dmi.product.sku: LENOVO_MT_20RA_BU_SMB_FM_ThinkPad E14
dmi.product.version: ThinkPad E14
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960213/+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 1971656] Re: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04
Does kernel parameter "iommu=off" help? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1971656 Title: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04 Status in linux-firmware package in Ubuntu: Confirmed Bug description: On a Lenovo P14s (RTL8111/8168/8411), the WiFi connection gets stuck at times. When this happens, there is no way to use `sudo`, the WiFi GNOME UI says NetworkManager is not running (which it is), and `dmesg -w` continuously outputs: ``` [90296.470925] rtw89_pci :03:00.0: failed to get available addr cam [90296.470935] rtw89_pci :03:00.0: failed to init addr cam [90296.586817] rtw89_pci :03:00.0: failed to get available addr cam [90296.586828] rtw89_pci :03:00.0: failed to init addr cam [90296.698790] rtw89_pci :03:00.0: failed to get available addr cam [90296.698797] rtw89_pci :03:00.0: failed to init addr cam [90296.810783] rtw89_pci :03:00.0: failed to get available addr cam [90296.810790] rtw89_pci :03:00.0: failed to init addr cam ``` The only solution I've found is to reboot the machine. However, turning off needs to be forced (magic keys still work for rebooting). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 5 07:49:18 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu2 InstallationDate: Installed on 2022-02-25 (68 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 21A3MZ PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) dmi.bios.date: 11/05/2021 dmi.bios.release: 1.13 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET43W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A3MZ dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrR1MET43W(1.13):bd11/05/2021:br1.13:efr1.13:svnLENOVO:pn21A3MZ:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A3MZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A3MZ dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971656/+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 1956086] Re: config CONFIG_HISI_PMU for kunpeng920
** Changed in: kunpeng920/ubuntu-20.04-hwe Status: In Progress => Fix Committed ** Changed in: kunpeng920/ubuntu-20.04 Status: In Progress => Fix Committed ** Changed in: kunpeng920 Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956086 Title: config CONFIG_HISI_PMU for kunpeng920 Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Bug description: [Impact] We have Hisilicon PMU modules built-in and they can not be unloaded. There is no way to replace with a updated module unless we build it as module. It also wastes memory on arm64 systems based on other SoCs. [Test Plan] `lsmod | grep hisi_uncore` shall see 4 modules loaded and they can be unloaded. [Regression Risk] CONFIG_HISI_PMU shall be only affected Hisilicon platforms that HISI0213 is found in ACPI tables. We shall have perf test run on these platforms and others have lowest risk. = [Bug Description] hisi pmu support x.ko module to use it for kunpeng920 [Steps to Reproduce] 1) cd /lib/modules/$(uname -r)/kernel/drivers/perf/hisilicon 2) check *.ko 3) [Actual Results] @ubuntu:~$ cat /boot/config-4.15.0-140-generic | grep -i CONFIG_HISI_PMU CONFIG_HISI_PMU=y [Expected Results] @ubuntu:~$ cat /boot/config-4.15.0-140-generic | grep -i CONFIG_HISI_PMU CONFIG_HISI_PMU=m [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] drivers/perf: hisi: Permit modular builds of HiSilicon uncore drivers To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1956086/+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 1965882] Re: [nouveau] External monitor plugged into (secondary) Nvidia GPU is all white (plus a little flicker)
We should check to see if this is the cause: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971146/comments/29 -- 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/1965882 Title: [nouveau] External monitor plugged into (secondary) Nvidia GPU is all white (plus a little flicker) Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: External monitor plugged into (secondary) Nvidia GPU is all white (plus a little flicker) for gnome-shell/mutter when using nouveau. The primary GPU (i915) still works fine. This seems to be a kernel regression... FAIL: 5.17.0-051700drmtip20220322-generic FAIL: 5.17.0-051700-generic FAIL: 5.15.0-23-generic FAIL: 5.14.21-051421-generic PASS: 5.14.20-051420-generic PASS: 5.14.18-051418-generic PASS: 5.14.15-051415-generic PASS: 5.14.10-051410-generic PASS: 5.14.0-051400-generic PASS: 5.13.19-051319-generic PASS: 5.10.107-0510107-generic ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Tue Mar 22 16:35:58 2022 InstallationDate: Installed on 2021-11-05 (136 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) MachineType: Intel(R) Client Systems NUC9i7QNX ProcFB: 0 i915drmfb 1 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QXCFL579.0034.2019.1125.1436 dmi.board.name: NUC9i7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K49245-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.33 dmi.modalias: dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX: dmi.product.family: QN dmi.product.name: NUC9i7QNX dmi.product.sku: BXNUC9i7QNX dmi.product.version: K49244-403 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1965882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958191] Re: Flickering and disforming booting into desktop both on wayland/xorg
The solution to bug 1970426 ended up being: i915.enable_dc=0 intel_idle.max_cstate=2 Can you try those? ** Summary changed: - Flickering and disforming booting into desktop both on wayland/xorg + [i915] Flickering and deformed booting into desktop both on wayland/xorg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958191 Title: [i915] Flickering and deformed booting into desktop both on wayland/xorg Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel paramater intel_idle.max_cstate=4 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971667] Re: Skip setting ethernet LED on Dell EMC board
** Changed in: linux-intel-5.13 (Ubuntu Focal) Assignee: (unassigned) => Jian Hui Lee (jianhuilee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1971667 Title: Skip setting ethernet LED on Dell EMC board Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-intel-5.13 source package in Focal: Confirmed Status in linux source package in Kinetic: Confirmed Status in linux-intel-5.13 source package in Kinetic: Invalid Bug description: [Impact] LED is not show networking status on the said Dell EMC board. [Fix] Don't set the LED on it. [Test] Check the LED and it's showing correct status. The LED continues to work after S3. [Where problems could occur] We use a UUID to match the board, so all other users are unaffected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1971667/+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 1970426] Re: [i915] screen is flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added)
** Summary changed: - [i915] screen is flickering in Ubuntu 22.04 + [i915] screen is flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- 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/1970426 Title: [i915] screen is flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) Status in linux package in Ubuntu: Triaged Bug description: After I updated to 22.04 sometimes (about 3 ~ 4 times a day) the screen starts glitching and flickering like in the attached video and it doesn't stop until I move the cursor. Description: Ubuntu 22.04 LTS Release: 22.04 wayland processor: Intel® Core™ i5-8265U CPU @ 1.60GHz × 8 graphics: Mesa Intel® UHD Graphics 620 (WHL GT2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970426/+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 1970552] Re: Mute/mic LEDs no function on EliteBook G9 platfroms
Enable proposed and install 5.14.0-1035.38 on 1) HP EliteBook x360 830 G9 2) HP EliteBook 830 G9 3) HP EliteBook 840 G9 4) HP EliteBook 860 G9 5) HP EliteBook 840 Aero G9 6) HP EliteBook x360 840 Aero G9 the audio/mic mute LEDs are working good. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1970552 Title: Mute/mic LEDs no function on EliteBook G9 platfroms Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] The mic mute/audio mute LEDS are not work on 1) HP EliteBook x360 830 G9 2) HP EliteBook 830 G9 3) HP EliteBook 840 G9 4) HP EliteBook 860 G9 5) HP EliteBook 840 Aero G9 6) HP EliteBook x360 840 Aero G9 [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1970552/+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 1962373] Re: Cannot resume from suspend
Is there anything I can do to help get this bug addressed? Configurations I could try, mainline kernels I could test, etc? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1962373 Title: Cannot resume from suspend Status in linux-hwe-5.13 package in Ubuntu: Confirmed Bug description: New HP Pavilion 15z-eh100 I am able to suspend via the power menu or by closing the laptop lid. However, I am unable to resume from suspend. Opening the lid does not do it. Hitting the power button does not do it. I have hit every key on the keyboard as well as clicked the touchpad. The power button has a slowly pulsing light, indicating it is suspended. Pressing and holding the power button for several seconds, causing the laptop to power off, is the only way I have found to get out of this state. $ cat /proc/acpi/wakeup DeviceS-state Status Sysfs node GPP1S4*disabled GP17S4*enabled pci::00:08.1 GPP0S4*disabled $ uname -a Linux pavilion 5.13.0-30-generic #33~20.04.1-Ubuntu SMP Mon Feb 7 14:25:10 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -rd Description: Ubuntu 20.04.4 LTS Release: 20.04 $ lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Renoir IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge 00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge 00:02.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge 00:02.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 51) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 5 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 6 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 7 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader (rev 01) 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device 8852 03:00.0 Non-Volatile memory controller: Sandisk Corp Device 5009 (rev 01) 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Device 164c (rev c2) 04:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device 1637 04:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor 04:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir USB 3.1 04:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir USB 3.1 04:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor (rev 01) 04:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller Please let me know if I can provide any other details to help get this solved. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Feb 26 11:49:38 2022 InstallationDate: Installed on 2022-02-16 (10 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1962373/+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 1969434] Re: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI
SRU V3: * https://lists.ubuntu.com/archives/kernel-team/2022-May/129985.html (kernel-versions) * https://lists.ubuntu.com/archives/kernel-team/2022-May/129989.html (linux-meta, oem-5.14/jammy/oem-5.17/unstable) * https://lists.ubuntu.com/archives/kernel-team/2022-May/129996.html (linux, oem-5.14/jammy/oem-5.17/unstable) ** Changed in: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-oem-5.17 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Also affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-meta-oem (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-meta (Ubuntu) Importance: Undecided => High ** Changed in: linux-meta (Ubuntu) Status: New => In Progress ** Changed in: linux-meta (Ubuntu) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-meta (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-meta (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-meta (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-meta (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-meta-oem (Ubuntu) Status: New => Invalid ** Changed in: linux-meta-oem (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-meta-oem (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-meta-oem (Ubuntu Focal) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-meta-oem (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-meta-oem (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-meta-oem (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux (Ubuntu) Importance: Medium => High ** Changed in: linux (Ubuntu) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux (Ubuntu Jammy) Importance: Medium => High ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1969434 Title: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-meta package in Ubuntu: In Progress Status in linux-meta-oem package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in backport-iwlwifi-dkms source package in Focal: New Status in linux source package in Focal: Invalid Status in linux-meta source package in Focal: Invalid Status in linux-meta-oem source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Status in linux-oem-5.17 source package in Focal: Invalid Status in backport-iwlwifi-dkms source package in Jammy: Fix Released Status in linux source package in Jammy: In Progress Status in linux-meta source package in Jammy: In Progress Status in linux-meta-oem source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [SRU Justfication] [Impact] Intel AX211 iwlwifi -64 firmware may fail to init under reboot stress, and -67 is immune. FW API -64 supported by oem-5.14, and -67 in v5.16. Not reproducible on every platform with AX211 installed, and the chances of such failures vary from one to another. [Fix] A few solutions were considered. The very first one is to ask Intel to fix -64 firmware directly, and the answer is a solid no claimed -64 is not the planned production version of AX211. It's also possible to backport FW API from v5.16, but while iwlwifi FW API is more or less a black box to us and the new FW APIs also depends on updates on the wireless stack, this is going to be very risky and actually we had regressions before after such backports. The last viable solution is to run backport-iwlwifi-dkms >= rev 8580 on the effected platforms. This means oem-5.14 and its migration target, hwe-5.15 will not be able to drive this piece of hw flawlessly without backport-iwlwifi-dkms installed. However, while we need secureboot to be enabled on these platforms, backport-iwlwifi-dkms must also be
[Kernel-packages] [Bug 1971480] Re: issuing invalid ioctl to /dev/vsock may spam dmesg
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1971480
Title:
issuing invalid ioctl to /dev/vsock may spam dmesg
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Bug description:
[Impact]
Any user may spam dmesg may issuing an invalid ioctl to /dev/vsock.
[Fix]
Do not print anything to dmesg when an invalid ioctl is issued to /dev/vsock.
[Test case]
ioctl(open("/dev/vsock", O_RDONLY), garbage, 0);
[Potential regression]
vsock users may regress.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971480/+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 1951289] Re: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3, 9, 11, 17, 19, 25 report incorrect sched domain for cpu#32
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951289 Title: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3,9,11,17,19,25 report incorrect sched domain for cpu#32 Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Won't Fix Bug description: [Impact] The LTP cpuset_sched_domains test, authored by Miao Xie, fails on a Kunpeng920 server that has 4 NUMA nodes: https://launchpad.net/bugs/1951289 This does appear to be a real bug. /proc/schedstat displays 4 domain levels for CPUs on 2 of the nodes, but only 3 levels for the others 2 (see below). I assume this means the scheduler is making suboptimal decisions about where to place/move processes. [Test Case] On a 128 core Kunpeng 920 system, observe that half the CPUs are missing a 3rd level scheduling domain: ubuntu@d06-4:~$ grep domain2 /proc/schedstat | wc -l 128 ubuntu@d06-4:~$ grep domain3 /proc/schedstat | wc -l 64 ubuntu@d06-4:~$ [What Could Go Wrong] This changes the code used for populating sched domains, so it could potentially break on other systems, potentially leading to poor scheduling characteristics (higher latencies, lower overall throughput etc). To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1951289/+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 EYPC (Asus) server
Hello @zhanglei-mao thanks for creating the bug report. There is a large time difference between those 5.4 kernels. 5.4.0-42 is from June 2020 and 5.4.0-109 is very recent. Is it possible to find out the first non-working 5.4 kernel? We would need to do a bisect. Do you think you might be able to test the 5.4.0-75 kernel to try to reproduce this problem? Thanks. -- 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 EYPC (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 1971151] Re: [Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Michael Reed (mreed8855) -- 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/1971151 Title: [Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support Status in linux package in Ubuntu: Incomplete Bug description: Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04.1(5.15 kernel). These patches got accepted by the upstream and please find the corresponding commit IDs as below: ed567615f7ec scsi: mpi3mr: Fix build errors in uapi header scsi_bsg_mpi3mr.h dde822e21700 scsi: mpi3mr: Update driver version to 8.0.0.69.0 04dfa01e77ea scsi: mpi3mr: Add support for NVMe passthrough 937a6f2c4f2e scsi: mpi3mr: Expose adapter state to sysfs 83959ce5204a scsi: mpi3mr: Add support for PEL commands eb8a3217cd7d scsi: mpi3mr: Add support for MPT commands 455aac4f7a13 scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header a212ebe7d4b1 scsi: mpi3mr: Add support for driver commands 7fbaf8b0d8b8 scsi: mpi3mr: Add bsg device support Thanks, Sumit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971151/+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 1971748] Re: package linux-image-4.15.0-96-generic 4.15.0-96.97~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 135
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: linux-hwe (Ubuntu) Importance: Undecided => Low ** Changed in: linux-hwe (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1971748 Title: package linux-image-4.15.0-96-generic 4.15.0-96.97~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 135 Status in linux-hwe package in Ubuntu: Invalid Bug description: not install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-96-generic 4.15.0-96.97~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-142-generic i686 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: i386 Date: Thu May 5 18:43:26 2022 DuplicateSignature: package:linux-image-4.15.0-96-generic:4.15.0-96.97~16.04.1 Setting up linux-image-4.15.0-96-generic (4.15.0-96.97~16.04.1) ... Bus error (core dumped) dpkg: error processing package linux-image-4.15.0-96-generic (--configure): subprocess installed post-installation script returned error exit status 135 ErrorMessage: subprocess installed post-installation script returned error exit status 135 InstallationDate: Installed on 2020-01-29 (827 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.7 apt 1.2.35 SourcePackage: linux-hwe Title: package linux-image-4.15.0-96-generic 4.15.0-96.97~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 135 UpgradeStatus: Upgraded to xenial on 2022-05-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1971748/+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 1971151] Re: [Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support
Hi Sumit, All of the patches in comment #2 cherry-pick cleanly. I noticed that the following patch is in the description but missing from comment #2: ed567615f7ec scsi: mpi3mr: Fix build errors in uapi header scsi_bsg_mpi3mr.h Is this patch still needed? I see that it has been applied to 5.19/scsi-staging (https://www.spinics.net/lists/linux-scsi/msg172765.html). I am having trouble locating it when I try to cherry-pick it. Has anything changed about this patch? commit ID, etc? -- 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/1971151 Title: [Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support Status in linux package in Ubuntu: Incomplete Bug description: Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04.1(5.15 kernel). These patches got accepted by the upstream and please find the corresponding commit IDs as below: ed567615f7ec scsi: mpi3mr: Fix build errors in uapi header scsi_bsg_mpi3mr.h dde822e21700 scsi: mpi3mr: Update driver version to 8.0.0.69.0 04dfa01e77ea scsi: mpi3mr: Add support for NVMe passthrough 937a6f2c4f2e scsi: mpi3mr: Expose adapter state to sysfs 83959ce5204a scsi: mpi3mr: Add support for PEL commands eb8a3217cd7d scsi: mpi3mr: Add support for MPT commands 455aac4f7a13 scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header a212ebe7d4b1 scsi: mpi3mr: Add support for driver commands 7fbaf8b0d8b8 scsi: mpi3mr: Add bsg device support Thanks, Sumit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971151/+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 1970065] Re: System not going to be completly powered off
I have the same issue. The power management system also doesn't recognize my laptop's battery level on this kernel. -- 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/1970065 Title: System not going to be completly powered off Status in linux package in Ubuntu: Confirmed Bug description: When i shutdown (Apr 23 23:15), it seems everything powered of except the keyboard lights. Then, i try to power on again, but, nothing happened because the notebook are still powered on. So, it's never powered off correctly? Now i force power off (Apr 23 23:20). After Start, the logs look like this: Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Stopped Create System Users. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: swapfile.swap: Deactivated successfully. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Deactivated swap /swapfile. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Reached target Unmount All Filesystems. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: systemd-remount-fs.service: Deactivated successfully. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Stopped Remount Root and Kernel File Systems. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Reached target System Shutdown. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Reached target Late Shutdown Services. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: systemd-poweroff.service: Deactivated successfully. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Finished System Power Off. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Reached target System Power Off. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd[1]: Shutting down. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd-shutdown[1]: Syncing filesystems and block devices. Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd-shutdown[1]: Sending SIGTERM to remaining processes... Apr 23 23:15:14 user-ThinkPad-X1-Yoga-1st systemd-journald[258]: Journal stopped -- Boot 286bc7f0640748e9996bbc70b090eb57 -- Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: microcode: microcode updated early to revision 0xea, date = 2021-01-25 Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: Linux version 5.15.0-25-generic (buildd@ubuntu) (gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #25-Ubuntu SMP Wed Mar 30 > Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=945f3621-37dd-40d0-be8d-295ac422c82f ro quiet splash vt.handoff=7 Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: KERNEL supported cpus: Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: Intel GenuineIntel Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: AMD AuthenticAMD Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: Hygon HygonGenuine Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: Centaur CentaurHauls Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: zhaoxin Shanghai Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers' Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR' Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64 Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64 Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format. Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: signal: max sigframe size: 2032 Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: BIOS-provided physical RAM map: Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: BIOS-e820: [mem 0x-0x00057fff] usable Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: BIOS-e820: [mem 0x00058000-0x00058fff] reserved Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: BIOS-e820: [mem 0x00059000-0x0009cfff] usable Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: BIOS-e820: [mem 0x0009d000-0x000f] reserved Apr 23 23:20:55 user-ThinkPad-X1-Yoga-1st kernel: BIOS-e820: [mem 0x0010-0xc3eecfff] usable It seems to me nothing bad? OS: Distributor ID: Ubuntu Description:
[Kernel-packages] [Bug 1968519] Re: [Lenovo Ubuntu 22.04 Bug]The Physical VGA displayer shows no signal (black screen) when install Ubuntu 22.04
For me, on a Dell R610, this regression was resolved by applying the patch referenced below: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.18-rc1=40ce1121c1d76daf9048a86e36c83e469281b9fd -- 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/1968519 Title: [Lenovo Ubuntu 22.04 Bug]The Physical VGA displayer shows no signal (black screen) when install Ubuntu 22.04 Status in linux package in Ubuntu: Confirmed Bug description: Description: When we install Ubuntu 22.04, the physical VGA displayer show black screen. It can only show rarely boot logs just for few seconds after kebyboard Enter key be pressed to install Ubuntu OS, and then the physical VGA displayer keeps black screen, but the XCC remote KVM monitor can show the boot log and the GUI interface. Produce Steps: 1. Connect a physical VGA displayer. 2. Fresh install Ubuntu22.04 on a server that integrated Matrox MGA G200-family. 3. When the install menu comes out, press keyboard Enter key, the physical VGA displayer just get the signal for few seconds and then the monitor go to black screen. Configuration: Systems：Lenovo SR590, SR650, SR630 with magag200 as GFX OS:jammy-live-server20220405-amd64.iso CPU:Intel(R) Xeon(R) Bronze 3104 CPU @ 1.70GHz UEFI:3.30 (Build ID: IVE178D) XCC:1.30 (Build ID: PDL114N) HDD:1.00TB 7.2K 6Gbps SATA 3.5" HD Actual results: The VGA display keep the black screen, during Ubuntu 22.04 installation. Expected results: The VGA display is OK when install the Ubuntu 22.04 in a server that integrated Matrox MGA G200-family video processor Additional info: 1. The issue can be reproduced 100% in the server that integrated Matrox MGA G200-family platforms. 2. Both UEFI mode and legacy mode are failed. 3. After we finish installing Ubuntu OS through XCC remote KVM monitor, and reboot the system, the physical VGA displayer still show nothing after a few seconds. 4. We did more tests, modified the cmdline of the kernel, add "nomodeset", the VGA displayer display well. 5. This issue could be found on both Intel and AMD platforms , which have onboard video chip as mgag200, also called pilot 4. 6. Upstream kernel patch https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.18-rc1=147696720eca12ae48d020726208b9a61cdd80bc (drm/mgag200: Select clock in PLL update functions) probalby resovle the issue on BIOS legacy mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968519/+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 1971460] Re: [amdgpu] System freezes coming out from suspension or randomly from screen power save
Finally got a freeze during monitor power save when was 3440x1440 @144hz. Here the log file. ** Attachment added: "freeze_on_monitor_powersave_144hz.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971460/+attachment/5587072/+files/freeze_on_monitor_powersave_144hz.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/1971460 Title: [amdgpu] System freezes coming out from suspension or randomly from screen power save Status in linux package in Ubuntu: Confirmed Bug description: I've Ubuntu 22.04 with Wayland and Sapphire Radeon RX 6600 with Xiaomi 34" curved gaming monitor capable of 3440x1440 @144,00hz. Using refresh of 120hz or 144hz, the system freezes coming out from suspension or randomly from screen power save. Setting @60hz it's more stable. It seems something related to wrong Modeline for this VGA and monitor resolution/frequencies. The problem is with both DP or HDMI cable. With HDMI it supports only 99,99hz I had no problem with the provious HP RX 460 HanSolo or XFX GTX 1060 3GB with proprietary nVidia drivers. 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 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 3 18:29:05 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] [1002:73ff] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Navi 23 [Radeon RX 6600/6600 XT/6600M] [1da2:e447] InstallationDate: Installed on 2022-04-23 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=be1c4139-f2bc-472b-87c1-099f2be97b1a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3604 dmi.board.asset.tag: Default string dmi.board.name: TUF B450M-PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3604:bd02/25/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFB450M-PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971460/+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 1971460] Re: [amdgpu] System freezes coming out from suspension or randomly from screen power save
And I got a freeze also switching from 144hz to 100hz (always at 3440x1440). Here the log file. ** Attachment added: "freeze_on_switch_from_144hz_to_100hz.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971460/+attachment/5587073/+files/freeze_on_switch_from_144hz_to_100hz.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/1971460 Title: [amdgpu] System freezes coming out from suspension or randomly from screen power save Status in linux package in Ubuntu: Confirmed Bug description: I've Ubuntu 22.04 with Wayland and Sapphire Radeon RX 6600 with Xiaomi 34" curved gaming monitor capable of 3440x1440 @144,00hz. Using refresh of 120hz or 144hz, the system freezes coming out from suspension or randomly from screen power save. Setting @60hz it's more stable. It seems something related to wrong Modeline for this VGA and monitor resolution/frequencies. The problem is with both DP or HDMI cable. With HDMI it supports only 99,99hz I had no problem with the provious HP RX 460 HanSolo or XFX GTX 1060 3GB with proprietary nVidia drivers. 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 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 3 18:29:05 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] [1002:73ff] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Navi 23 [Radeon RX 6600/6600 XT/6600M] [1da2:e447] InstallationDate: Installed on 2022-04-23 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=be1c4139-f2bc-472b-87c1-099f2be97b1a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3604 dmi.board.asset.tag: Default string dmi.board.name: TUF B450M-PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3604:bd02/25/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFB450M-PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971460/+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 1970957] Re: suspend problem
I've been using Awesome WM instead of Gnome. Now suspend does works properly. At least I did not have any incident so far. -- 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/1970957 Title: suspend problem Status in linux package in Ubuntu: Confirmed Bug description: I've installed Ubuntu 22.04 on the ThinkPad E480. Suspend functions ok intermittently. Some times it works fine, other times the computer does not enter the suspend mode (the screen gets blank, but the machine is still running and the ThinPad led is on, and there is no way out... no response from keyboard or mouse... the only solution is to switch off manually hitting and holding the power button), other times the machine does not wakes up from suspension mode. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 10:53:59 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leoca 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20KQ000EBR Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=1e7d6212-699d-4319-b137-8a7059545433 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/14/2018 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R0PET42W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KQ000EBR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR0PET42W(1.19):bd06/14/2018:br1.19:efr1.19:svnLENOVO:pn20KQ000EBR:pvrThinkPadE480:rvnLENOVO:rn20KQ000EBR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KQ_BU_Think_FM_ThinkPadE480: dmi.product.family: ThinkPad E480 dmi.product.name: 20KQ000EBR dmi.product.sku: LENOVO_MT_20KQ_BU_Think_FM_ThinkPad E480 dmi.product.version: ThinkPad E480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970957/+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 1971748] [NEW] package linux-image-4.15.0-96-generic 4.15.0-96.97~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 135
Public bug reported: not install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-96-generic 4.15.0-96.97~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-142-generic i686 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: i386 Date: Thu May 5 18:43:26 2022 DuplicateSignature: package:linux-image-4.15.0-96-generic:4.15.0-96.97~16.04.1 Setting up linux-image-4.15.0-96-generic (4.15.0-96.97~16.04.1) ... Bus error (core dumped) dpkg: error processing package linux-image-4.15.0-96-generic (--configure): subprocess installed post-installation script returned error exit status 135 ErrorMessage: subprocess installed post-installation script returned error exit status 135 InstallationDate: Installed on 2020-01-29 (827 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.7 apt 1.2.35 SourcePackage: linux-hwe Title: package linux-image-4.15.0-96-generic 4.15.0-96.97~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 135 UpgradeStatus: Upgraded to xenial on 2022-05-05 (0 days ago) ** Affects: linux-hwe (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 need-duplicate-check third-party-packages xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1971748 Title: package linux-image-4.15.0-96-generic 4.15.0-96.97~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 135 Status in linux-hwe package in Ubuntu: New Bug description: not install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-96-generic 4.15.0-96.97~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-142-generic i686 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: i386 Date: Thu May 5 18:43:26 2022 DuplicateSignature: package:linux-image-4.15.0-96-generic:4.15.0-96.97~16.04.1 Setting up linux-image-4.15.0-96-generic (4.15.0-96.97~16.04.1) ... Bus error (core dumped) dpkg: error processing package linux-image-4.15.0-96-generic (--configure): subprocess installed post-installation script returned error exit status 135 ErrorMessage: subprocess installed post-installation script returned error exit status 135 InstallationDate: Installed on 2020-01-29 (827 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.7 apt 1.2.35 SourcePackage: linux-hwe Title: package linux-image-4.15.0-96-generic 4.15.0-96.97~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 135 UpgradeStatus: Upgraded to xenial on 2022-05-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1971748/+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 1971656] Re: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04
@lissyx is that an Intel or Ryzen P14s you have? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1971656 Title: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04 Status in linux-firmware package in Ubuntu: Confirmed Bug description: On a Lenovo P14s (RTL8111/8168/8411), the WiFi connection gets stuck at times. When this happens, there is no way to use `sudo`, the WiFi GNOME UI says NetworkManager is not running (which it is), and `dmesg -w` continuously outputs: ``` [90296.470925] rtw89_pci :03:00.0: failed to get available addr cam [90296.470935] rtw89_pci :03:00.0: failed to init addr cam [90296.586817] rtw89_pci :03:00.0: failed to get available addr cam [90296.586828] rtw89_pci :03:00.0: failed to init addr cam [90296.698790] rtw89_pci :03:00.0: failed to get available addr cam [90296.698797] rtw89_pci :03:00.0: failed to init addr cam [90296.810783] rtw89_pci :03:00.0: failed to get available addr cam [90296.810790] rtw89_pci :03:00.0: failed to init addr cam ``` The only solution I've found is to reboot the machine. However, turning off needs to be forced (magic keys still work for rebooting). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 5 07:49:18 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu2 InstallationDate: Installed on 2022-02-25 (68 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 21A3MZ PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) dmi.bios.date: 11/05/2021 dmi.bios.release: 1.13 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET43W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A3MZ dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrR1MET43W(1.13):bd11/05/2021:br1.13:efr1.13:svnLENOVO:pn21A3MZ:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A3MZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A3MZ dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971656/+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 1971656] Re: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04
As maintainer of an rtw89 repo at GitHub, I have seen lots of complaints about this kind of hangups. Nearly all of these happen with Lenovo laptops. The remainder are a few HP machines. For some reason, the BIOS or the PCI interface in the Lenovo laptops are incompatible with the PCI code used in RTW89. My laptop is a Toshiba from 2014, and it never has any problems, thus I cannot diagnose the difficulty. The same is true for the software developers in Taiwan, with whom I have discussed the problem. This is the first I have heard that the problem started/got worse around April 11. That sounds like a candidate for bisection, which would have to be done with the mainline kernel, or even better, the one at wireless-next (git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless- next.git). Due to special patches in the GitHub version needed to build on older kernels, I upgrade the repo in batches, and lose the details of each individual patch from wireless-testing. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1971656 Title: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04 Status in linux-firmware package in Ubuntu: Confirmed Bug description: On a Lenovo P14s (RTL8111/8168/8411), the WiFi connection gets stuck at times. When this happens, there is no way to use `sudo`, the WiFi GNOME UI says NetworkManager is not running (which it is), and `dmesg -w` continuously outputs: ``` [90296.470925] rtw89_pci :03:00.0: failed to get available addr cam [90296.470935] rtw89_pci :03:00.0: failed to init addr cam [90296.586817] rtw89_pci :03:00.0: failed to get available addr cam [90296.586828] rtw89_pci :03:00.0: failed to init addr cam [90296.698790] rtw89_pci :03:00.0: failed to get available addr cam [90296.698797] rtw89_pci :03:00.0: failed to init addr cam [90296.810783] rtw89_pci :03:00.0: failed to get available addr cam [90296.810790] rtw89_pci :03:00.0: failed to init addr cam ``` The only solution I've found is to reboot the machine. However, turning off needs to be forced (magic keys still work for rebooting). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 5 07:49:18 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu2 InstallationDate: Installed on 2022-02-25 (68 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 21A3MZ PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) dmi.bios.date: 11/05/2021 dmi.bios.release: 1.13 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET43W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A3MZ dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrR1MET43W(1.13):bd11/05/2021:br1.13:efr1.13:svnLENOVO:pn21A3MZ:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A3MZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A3MZ dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971656/+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 1938650] Re: iwd on Ubuntu 20.04 stopped working since update to kernel 5.11
** Changed in: iwd (Ubuntu) Status: Confirmed => Invalid ** Changed in: iwd (Ubuntu) Importance: Medium => Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1938650 Title: iwd on Ubuntu 20.04 stopped working since update to kernel 5.11 Status in iwd package in Ubuntu: Invalid Status in linux-meta-hwe-5.11 package in Ubuntu: Confirmed Bug description: I was using iwd on my Acer aspire v17 nitro with Ubuntu 20.04, and it was working great. But after the last update to kernel 5.11 it suddenly had stopped working. I’ve tried to reinstall it but that didn’t help. I've tried back with kernel 5.8 and iwd was working again. Quick google search showed that this is actually a wide spread problem since kernel 5.9.x, so I wish to ask is there going to be a solution of any kind? Regards! I.Ivanov --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-28 (6 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) NonfreeKernelModules: nvidia_modeset nvidia Package: iwd 1.5-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Tags: focal Uname: Linux 5.11.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iwd/+bug/1938650/+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 1971700] Re: [jammy] 5.17.0-1004-oem breaks resume from sleep
happens only through S0ix, that's fine with S3. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1971700 Title: [jammy] 5.17.0-1004-oem breaks resume from sleep Status in linux-oem-5.17 package in Ubuntu: New Bug description: I cannot resume from sleep, I have to hard reboot. Does not happen with 5.17.0-1003-oem. Thinkpad P14s, AMD 5850u, wifi rtl 8852a, ssd nvme hynix Cannot give more details atm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta/5.15.0.29.32)
All autopkgtests for the newly accepted linux-meta (5.15.0.29.32) for jammy have finished running. The following regressions have been reported in tests triggered by the package: rtl8821ce/unknown (armhf) oss4/4.2-build2010-5ubuntu9 (amd64) ubuntu-drivers-common/unknown (armhf) systemd/249.11-0ubuntu3 (armhf) v4l2loopback/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970426] Re: [i915] screen is flickering in Ubuntu 22.04
In file /etc/default/grub I added to parameter GRUB_CMDLINE_LINUX_DEFAULT: i915.enable_dc=0 intel_idle.max_cstate=2 updated grub and now I'm flicker free for a few days. The last kernel without the flickering for me was the kernel that shipped with 21.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/1970426 Title: [i915] screen is flickering in Ubuntu 22.04 Status in linux package in Ubuntu: Confirmed Bug description: After I updated to 22.04 sometimes (about 3 ~ 4 times a day) the screen starts glitching and flickering like in the attached video and it doesn't stop until I move the cursor. Description: Ubuntu 22.04 LTS Release: 22.04 wayland processor: Intel® Core™ i5-8265U CPU @ 1.60GHz × 8 graphics: Mesa Intel® UHD Graphics 620 (WHL GT2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970426/+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 1956086] Re: config CONFIG_HISI_PMU for kunpeng920
** Description changed: [Impact] - We have Hisilicon PMU modules built-in and they can not be unloaded. There is no way to replace with a updated module unless we build it as module. + We have Hisilicon PMU modules built-in and they can not be unloaded. There is no way to replace with a updated module unless we build it as module. It also wastes memory on arm64 systems based on other SoCs. [Test Plan] `lsmod | grep hisi_uncore` shall see 4 modules loaded and they can be unloaded. [Regression Risk] CONFIG_HISI_PMU shall be only affected Hisilicon platforms that HISI0213 is found in ACPI tables. We shall have perf test run on these platforms and others have lowest risk. = [Bug Description] hisi pmu support x.ko module to use it for kunpeng920 [Steps to Reproduce] 1) cd /lib/modules/$(uname -r)/kernel/drivers/perf/hisilicon 2) check *.ko 3) [Actual Results] @ubuntu:~$ cat /boot/config-4.15.0-140-generic | grep -i CONFIG_HISI_PMU CONFIG_HISI_PMU=y [Expected Results] @ubuntu:~$ cat /boot/config-4.15.0-140-generic | grep -i CONFIG_HISI_PMU CONFIG_HISI_PMU=m [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] drivers/perf: hisi: Permit modular builds of HiSilicon uncore drivers -- 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/1956086 Title: config CONFIG_HISI_PMU for kunpeng920 Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 ubuntu-20.04-hwe series: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Bug description: [Impact] We have Hisilicon PMU modules built-in and they can not be unloaded. There is no way to replace with a updated module unless we build it as module. It also wastes memory on arm64 systems based on other SoCs. [Test Plan] `lsmod | grep hisi_uncore` shall see 4 modules loaded and they can be unloaded. [Regression Risk] CONFIG_HISI_PMU shall be only affected Hisilicon platforms that HISI0213 is found in ACPI tables. We shall have perf test run on these platforms and others have lowest risk. = [Bug Description] hisi pmu support x.ko module to use it for kunpeng920 [Steps to Reproduce] 1) cd /lib/modules/$(uname -r)/kernel/drivers/perf/hisilicon 2) check *.ko 3) [Actual Results] @ubuntu:~$ cat /boot/config-4.15.0-140-generic | grep -i CONFIG_HISI_PMU CONFIG_HISI_PMU=y [Expected Results] @ubuntu:~$ cat /boot/config-4.15.0-140-generic | grep -i CONFIG_HISI_PMU CONFIG_HISI_PMU=m [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] drivers/perf: hisi: Permit modular builds of HiSilicon uncore drivers To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1956086/+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 1969689] Re: USB devices not detected on CM4
Argh, I'm an idiot -- had the flashing cable plugged into the micro-USB while the keyboard was *also* plugged into the USB-A sockets (which I knew doesn't work and apparently missed when originally debugging this). Closing as invalid. ** Changed in: linux-raspi (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-raspi (Ubuntu Kinetic) Status: Confirmed => Invalid -- 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/1969689 Title: USB devices not detected on CM4 Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi source package in Jammy: Invalid Status in linux-raspi source package in Kinetic: Invalid Bug description: USB devices are not working on the CM4. When running `lsusb` the hub is detected, but devices are not. ``` ubuntu@ubuntu:~$ sudo dmesg | egrep -i "dwc2|usb" [0.151915] usbcore: registered new interface driver usbfs [0.151976] usbcore: registered new interface driver hub [0.152047] usbcore: registered new device driver usb [1.125855] usbcore: registered new interface driver lan78xx [1.125926] usbcore: registered new interface driver smsc95xx [1.125965] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [1.126070] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [1.126318] uhci_hcd: USB Universal Host Controller Interface driver [1.765785] usb_phy_generic phy: supply vcc not found, using dummy regulator [1.864470] dwc2 fe98.usb: supply vusb_d not found, using dummy regulator [1.864674] dwc2 fe98.usb: supply vusb_a not found, using dummy regulator [1.916752] dwc2 fe98.usb: DWC OTG Controller [1.916788] dwc2 fe98.usb: new USB bus registered, assigned bus number 1 [1.916822] dwc2 fe98.usb: irq 36, io mem 0xfe98 [1.917028] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15 [1.917040] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [1.917048] usb usb1: Product: DWC OTG Controller [1.917055] usb usb1: Manufacturer: Linux 5.15.0-1005-raspi dwc2_hsotg [1.917062] usb usb1: SerialNumber: fe98.usb [1.917627] hub 1-0:1.0: USB hub found [7.831293] usbcore: registered new interface driver brcmfmac ``` @waveform was able to confirm the issue. The line `dtoverlay=dwc2,dr_mode=host` is present in config.txt. We suspect this to be a dtb/kernel issue. This is happening on both armhf and arm64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1969689/+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 1970451] Re: Update to the 510.68.02 UDA NVIDIA driver series in Bionic, Focal, Impish, and Jammy
** Changed in: linux-restricted-modules (Ubuntu Bionic) Assignee: (unassigned) => Ian May (ian-may) ** Changed in: linux-restricted-modules (Ubuntu Focal) Assignee: (unassigned) => Ian May (ian-may) ** Changed in: linux-restricted-modules (Ubuntu Impish) Assignee: (unassigned) => Ian May (ian-may) ** Changed in: linux-restricted-modules (Ubuntu Jammy) Assignee: (unassigned) => Ian May (ian-may) ** Changed in: nvidia-graphics-drivers-510 (Ubuntu Bionic) Assignee: (unassigned) => Ian May (ian-may) ** Changed in: nvidia-graphics-drivers-510 (Ubuntu Focal) Assignee: (unassigned) => Ian May (ian-may) ** Changed in: nvidia-graphics-drivers-510 (Ubuntu Impish) Assignee: (unassigned) => Ian May (ian-may) ** Changed in: nvidia-graphics-drivers-510 (Ubuntu Jammy) Assignee: (unassigned) => Ian May (ian-may) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1970451 Title: Update to the 510.68.02 UDA NVIDIA driver series in Bionic, Focal, Impish, and Jammy Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in linux-restricted-modules source package in Bionic: Confirmed Status in nvidia-graphics-drivers-510 source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Focal: Confirmed Status in nvidia-graphics-drivers-510 source package in Focal: Fix Committed Status in linux-restricted-modules source package in Impish: Confirmed Status in nvidia-graphics-drivers-510 source package in Impish: Fix Committed Status in linux-restricted-modules source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] === 510 jammy/impish/focal/bionic === * New upstream release (LP: #1970451): - Fixed an issue where NvFBC was requesting Vulkan 1.0 while using Vulkan 1.1 core features. This caused NvFBC to fail to initialize with Vulkan loader versions 1.3.204 or newer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1970451/+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 1971567] Re: TPM breaks resume from standby
Tried latest mainline kernel (amd64/linux-image-
unsigned-5.18.0-051800rc5-generic_5.18.0-051800rc5.202205011831_amd64.deb)
- bug persists.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1971567
Title:
TPM breaks resume from standby
Status in linux package in Ubuntu:
Confirmed
Bug description:
After upgrading Lenovo Thinkpad X260 from 21.10 to 22.04, following
error shows at boot:
[4.830657] tpm tpm0: Operation Timed out
[ 11.654699] tpm tpm0: Operation Timed out
[ 11.654718] tpm_crb: probe of MSFT0101:00 failed with error -62
Notable consequence is that the laptop will not resume from standby
any more, even with the power button pressed.
After disabling TPM ("Security Chip" in Lenovo BIOS) completely,
everything works normal.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-27-generic 5.15.0-27.28
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: martin 2147 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed May 4 13:15:17 2022
InstallationDate: Installed on 2022-03-06 (59 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 20F5S0V400
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.15.0-27-generic N/A
linux-backports-modules-5.15.0-27-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu1
SourcePackage: linux
UpgradeStatus: Upgraded to jammy on 2022-04-24 (10 days ago)
dmi.bios.date: 02/23/2022
dmi.bios.release: 1.49
dmi.bios.vendor: LENOVO
dmi.bios.version: R02ET76W (1.49 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20F5S0V400
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.16
dmi.modalias:
dmi:bvnLENOVO:bvrR02ET76W(1.49):bd02/23/2022:br1.49:efr1.16:svnLENOVO:pn20F5S0V400:pvrThinkPadX260:rvnLENOVO:rn20F5S0V400:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20F5_BU_Think_FM_ThinkPadX260:
dmi.product.family: ThinkPad X260
dmi.product.name: 20F5S0V400
dmi.product.sku: LENOVO_MT_20F5_BU_Think_FM_ThinkPad X260
dmi.product.version: ThinkPad X260
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971567/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oem-5.17/5.17.0.1004.4)
All autopkgtests for the newly accepted linux-meta-oem-5.17 (5.17.0.1004.4) for jammy have finished running. The following regressions have been reported in tests triggered by the package: dahdi-linux/1:2.11.1~dfsg-1ubuntu11 (amd64) r8168/8.049.02-1ubuntu1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-oem-5.17 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971460] Re: [amdgpu] System freezes coming out from suspension or randomly from screen power save
Adding log file. This time the system freezed switching from 100hz to 144hz the monitor frequency. ** Attachment added: "freeze_on_switch_from_100hz_to_144hz.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971460/+attachment/5587020/+files/freeze_on_switch_from_100hz_to_144hz.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/1971460 Title: [amdgpu] System freezes coming out from suspension or randomly from screen power save Status in linux package in Ubuntu: Confirmed Bug description: I've Ubuntu 22.04 with Wayland and Sapphire Radeon RX 6600 with Xiaomi 34" curved gaming monitor capable of 3440x1440 @144,00hz. Using refresh of 120hz or 144hz, the system freezes coming out from suspension or randomly from screen power save. Setting @60hz it's more stable. It seems something related to wrong Modeline for this VGA and monitor resolution/frequencies. The problem is with both DP or HDMI cable. With HDMI it supports only 99,99hz I had no problem with the provious HP RX 460 HanSolo or XFX GTX 1060 3GB with proprietary nVidia drivers. 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 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 3 18:29:05 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] [1002:73ff] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Navi 23 [Radeon RX 6600/6600 XT/6600M] [1da2:e447] InstallationDate: Installed on 2022-04-23 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=be1c4139-f2bc-472b-87c1-099f2be97b1a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3604 dmi.board.asset.tag: Default string dmi.board.name: TUF B450M-PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3604:bd02/25/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFB450M-PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971460/+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 1971712] [NEW] Add support for Intel DG2
Public bug reported: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: use a dkms provided by Intel and integrated in the OEM kernel source, the module will be shipped in a separate modules package [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. ** Affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: mesa (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1971712 Title: Add support for Intel DG2 Status in linux-oem-5.17 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in linux-oem-5.17 source package in Jammy: New Status in mesa source package in Jammy: New Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: use a dkms provided by Intel and integrated in the OEM kernel source, the module will be shipped in a separate modules package [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971712/+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 1969815] Re: [radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state
FYI: $ apport-collect 1969815 dpkg-query: no packages found matching linux $ ** 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/1969815 Title: [radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state Status in linux package in Ubuntu: Confirmed Status in marco package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: I've just updated to 22.04 on 3x boxes: 2x laptops and 1x tower. Laptops went well as they are standard running wifi (note to self: next time upgrade one using a USB docking station+as many externally attached devices as possible should prove in a quite pleasurable end- user experience) For the tower: this is the dual-screen portrait system I have been opening up defects for months now. Same config too. Anyways, after I rebooted the overall booting process happened pretty well until TTY7 tried kicking it and totally failed doing so hence rendered my system totally broken. The behavior of my screens is that they started blinking from blank to another type of blank for =<1 second each state. But during one of those states there seemed to be Wayland as I could just see the mouse cursor fly around when activated. Accessing other TTYs was also impossible as even though pressing CTRL+ALT+F2|F3|etc would indeed display a login prompt that within that same blinking instant that it had altered back to only that blinking cursor symbol(_) at the top-hand-left. That behavior held true for all TTYs. Pressing the power button did showed up the UM symbol alongside standard shutdown routine happened OK. Solution was: unplug one of the two monitor and automagically jammy's login screen popped up. If I replug that 2nd monitor while I am inside a working TTY7 session then the same (original) problem happens in which I cannot use any of the screens and when I re-unplug one of the two screens again I am re- back again at the jammy login having lost the current session that I had. Both of my screens are the same model and both use HDMI. I have attached my ~/.config/monitors.xml --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dd3464333 F pulseaudio /dev/snd/controlC0: dd3464333 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 HibernationDevice: RESUME=UUID=88228def-1fb1-4fc3-964c-3106218355eb InstallationDate: Installed on 2020-08-29 (613 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp7s0no wireless extensions. tun0 no wireless extensions. MachineType: System manufacturer System Product Name Package: xorg-server PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/02/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5809 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969815/+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 1969815] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1969815/+attachment/5587017/+files/acpidump.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/1969815 Title: [radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state Status in linux package in Ubuntu: Confirmed Status in marco package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: I've just updated to 22.04 on 3x boxes: 2x laptops and 1x tower. Laptops went well as they are standard running wifi (note to self: next time upgrade one using a USB docking station+as many externally attached devices as possible should prove in a quite pleasurable end- user experience) For the tower: this is the dual-screen portrait system I have been opening up defects for months now. Same config too. Anyways, after I rebooted the overall booting process happened pretty well until TTY7 tried kicking it and totally failed doing so hence rendered my system totally broken. The behavior of my screens is that they started blinking from blank to another type of blank for =<1 second each state. But during one of those states there seemed to be Wayland as I could just see the mouse cursor fly around when activated. Accessing other TTYs was also impossible as even though pressing CTRL+ALT+F2|F3|etc would indeed display a login prompt that within that same blinking instant that it had altered back to only that blinking cursor symbol(_) at the top-hand-left. That behavior held true for all TTYs. Pressing the power button did showed up the UM symbol alongside standard shutdown routine happened OK. Solution was: unplug one of the two monitor and automagically jammy's login screen popped up. If I replug that 2nd monitor while I am inside a working TTY7 session then the same (original) problem happens in which I cannot use any of the screens and when I re-unplug one of the two screens again I am re- back again at the jammy login having lost the current session that I had. Both of my screens are the same model and both use HDMI. I have attached my ~/.config/monitors.xml --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dd3464333 F pulseaudio /dev/snd/controlC0: dd3464333 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 HibernationDevice: RESUME=UUID=88228def-1fb1-4fc3-964c-3106218355eb InstallationDate: Installed on 2020-08-29 (613 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp7s0no wireless extensions. tun0 no wireless extensions. MachineType: System manufacturer System Product Name Package: xorg-server PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/02/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5809 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969815/+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 1969815] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1969815/+attachment/5587016/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1969815 Title: [radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state Status in linux package in Ubuntu: Confirmed Status in marco package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: I've just updated to 22.04 on 3x boxes: 2x laptops and 1x tower. Laptops went well as they are standard running wifi (note to self: next time upgrade one using a USB docking station+as many externally attached devices as possible should prove in a quite pleasurable end- user experience) For the tower: this is the dual-screen portrait system I have been opening up defects for months now. Same config too. Anyways, after I rebooted the overall booting process happened pretty well until TTY7 tried kicking it and totally failed doing so hence rendered my system totally broken. The behavior of my screens is that they started blinking from blank to another type of blank for =<1 second each state. But during one of those states there seemed to be Wayland as I could just see the mouse cursor fly around when activated. Accessing other TTYs was also impossible as even though pressing CTRL+ALT+F2|F3|etc would indeed display a login prompt that within that same blinking instant that it had altered back to only that blinking cursor symbol(_) at the top-hand-left. That behavior held true for all TTYs. Pressing the power button did showed up the UM symbol alongside standard shutdown routine happened OK. Solution was: unplug one of the two monitor and automagically jammy's login screen popped up. If I replug that 2nd monitor while I am inside a working TTY7 session then the same (original) problem happens in which I cannot use any of the screens and when I re-unplug one of the two screens again I am re- back again at the jammy login having lost the current session that I had. Both of my screens are the same model and both use HDMI. I have attached my ~/.config/monitors.xml --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dd3464333 F pulseaudio /dev/snd/controlC0: dd3464333 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 HibernationDevice: RESUME=UUID=88228def-1fb1-4fc3-964c-3106218355eb InstallationDate: Installed on 2020-08-29 (613 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp7s0no wireless extensions. tun0 no wireless extensions. MachineType: System manufacturer System Product Name Package: xorg-server PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/02/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5809 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969815/+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 1969815] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1969815/+attachment/5587015/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1969815 Title: [radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state Status in linux package in Ubuntu: Confirmed Status in marco package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: I've just updated to 22.04 on 3x boxes: 2x laptops and 1x tower. Laptops went well as they are standard running wifi (note to self: next time upgrade one using a USB docking station+as many externally attached devices as possible should prove in a quite pleasurable end- user experience) For the tower: this is the dual-screen portrait system I have been opening up defects for months now. Same config too. Anyways, after I rebooted the overall booting process happened pretty well until TTY7 tried kicking it and totally failed doing so hence rendered my system totally broken. The behavior of my screens is that they started blinking from blank to another type of blank for =<1 second each state. But during one of those states there seemed to be Wayland as I could just see the mouse cursor fly around when activated. Accessing other TTYs was also impossible as even though pressing CTRL+ALT+F2|F3|etc would indeed display a login prompt that within that same blinking instant that it had altered back to only that blinking cursor symbol(_) at the top-hand-left. That behavior held true for all TTYs. Pressing the power button did showed up the UM symbol alongside standard shutdown routine happened OK. Solution was: unplug one of the two monitor and automagically jammy's login screen popped up. If I replug that 2nd monitor while I am inside a working TTY7 session then the same (original) problem happens in which I cannot use any of the screens and when I re-unplug one of the two screens again I am re- back again at the jammy login having lost the current session that I had. Both of my screens are the same model and both use HDMI. I have attached my ~/.config/monitors.xml --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dd3464333 F pulseaudio /dev/snd/controlC0: dd3464333 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 HibernationDevice: RESUME=UUID=88228def-1fb1-4fc3-964c-3106218355eb InstallationDate: Installed on 2020-08-29 (613 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp7s0no wireless extensions. tun0 no wireless extensions. MachineType: System manufacturer System Product Name Package: xorg-server PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/02/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5809 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969815/+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 1969815] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1969815/+attachment/5587014/+files/PulseList.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/1969815 Title: [radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state Status in linux package in Ubuntu: Confirmed Status in marco package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: I've just updated to 22.04 on 3x boxes: 2x laptops and 1x tower. Laptops went well as they are standard running wifi (note to self: next time upgrade one using a USB docking station+as many externally attached devices as possible should prove in a quite pleasurable end- user experience) For the tower: this is the dual-screen portrait system I have been opening up defects for months now. Same config too. Anyways, after I rebooted the overall booting process happened pretty well until TTY7 tried kicking it and totally failed doing so hence rendered my system totally broken. The behavior of my screens is that they started blinking from blank to another type of blank for =<1 second each state. But during one of those states there seemed to be Wayland as I could just see the mouse cursor fly around when activated. Accessing other TTYs was also impossible as even though pressing CTRL+ALT+F2|F3|etc would indeed display a login prompt that within that same blinking instant that it had altered back to only that blinking cursor symbol(_) at the top-hand-left. That behavior held true for all TTYs. Pressing the power button did showed up the UM symbol alongside standard shutdown routine happened OK. Solution was: unplug one of the two monitor and automagically jammy's login screen popped up. If I replug that 2nd monitor while I am inside a working TTY7 session then the same (original) problem happens in which I cannot use any of the screens and when I re-unplug one of the two screens again I am re- back again at the jammy login having lost the current session that I had. Both of my screens are the same model and both use HDMI. I have attached my ~/.config/monitors.xml --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dd3464333 F pulseaudio /dev/snd/controlC0: dd3464333 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 HibernationDevice: RESUME=UUID=88228def-1fb1-4fc3-964c-3106218355eb InstallationDate: Installed on 2020-08-29 (613 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp7s0no wireless extensions. tun0 no wireless extensions. MachineType: System manufacturer System Product Name Package: xorg-server PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/02/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5809 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969815/+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 1969815] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1969815/+attachment/5587011/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1969815 Title: [radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state Status in linux package in Ubuntu: Confirmed Status in marco package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: I've just updated to 22.04 on 3x boxes: 2x laptops and 1x tower. Laptops went well as they are standard running wifi (note to self: next time upgrade one using a USB docking station+as many externally attached devices as possible should prove in a quite pleasurable end- user experience) For the tower: this is the dual-screen portrait system I have been opening up defects for months now. Same config too. Anyways, after I rebooted the overall booting process happened pretty well until TTY7 tried kicking it and totally failed doing so hence rendered my system totally broken. The behavior of my screens is that they started blinking from blank to another type of blank for =<1 second each state. But during one of those states there seemed to be Wayland as I could just see the mouse cursor fly around when activated. Accessing other TTYs was also impossible as even though pressing CTRL+ALT+F2|F3|etc would indeed display a login prompt that within that same blinking instant that it had altered back to only that blinking cursor symbol(_) at the top-hand-left. That behavior held true for all TTYs. Pressing the power button did showed up the UM symbol alongside standard shutdown routine happened OK. Solution was: unplug one of the two monitor and automagically jammy's login screen popped up. If I replug that 2nd monitor while I am inside a working TTY7 session then the same (original) problem happens in which I cannot use any of the screens and when I re-unplug one of the two screens again I am re- back again at the jammy login having lost the current session that I had. Both of my screens are the same model and both use HDMI. I have attached my ~/.config/monitors.xml --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dd3464333 F pulseaudio /dev/snd/controlC0: dd3464333 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 HibernationDevice: RESUME=UUID=88228def-1fb1-4fc3-964c-3106218355eb InstallationDate: Installed on 2020-08-29 (613 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp7s0no wireless extensions. tun0 no wireless extensions. MachineType: System manufacturer System Product Name Package: xorg-server PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/02/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5809 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969815/+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 1969815] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1969815/+attachment/5587013/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1969815 Title: [radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state Status in linux package in Ubuntu: Confirmed Status in marco package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: I've just updated to 22.04 on 3x boxes: 2x laptops and 1x tower. Laptops went well as they are standard running wifi (note to self: next time upgrade one using a USB docking station+as many externally attached devices as possible should prove in a quite pleasurable end- user experience) For the tower: this is the dual-screen portrait system I have been opening up defects for months now. Same config too. Anyways, after I rebooted the overall booting process happened pretty well until TTY7 tried kicking it and totally failed doing so hence rendered my system totally broken. The behavior of my screens is that they started blinking from blank to another type of blank for =<1 second each state. But during one of those states there seemed to be Wayland as I could just see the mouse cursor fly around when activated. Accessing other TTYs was also impossible as even though pressing CTRL+ALT+F2|F3|etc would indeed display a login prompt that within that same blinking instant that it had altered back to only that blinking cursor symbol(_) at the top-hand-left. That behavior held true for all TTYs. Pressing the power button did showed up the UM symbol alongside standard shutdown routine happened OK. Solution was: unplug one of the two monitor and automagically jammy's login screen popped up. If I replug that 2nd monitor while I am inside a working TTY7 session then the same (original) problem happens in which I cannot use any of the screens and when I re-unplug one of the two screens again I am re- back again at the jammy login having lost the current session that I had. Both of my screens are the same model and both use HDMI. I have attached my ~/.config/monitors.xml --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dd3464333 F pulseaudio /dev/snd/controlC0: dd3464333 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 HibernationDevice: RESUME=UUID=88228def-1fb1-4fc3-964c-3106218355eb InstallationDate: Installed on 2020-08-29 (613 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp7s0no wireless extensions. tun0 no wireless extensions. MachineType: System manufacturer System Product Name Package: xorg-server PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/02/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5809 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969815/+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 1969815] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1969815/+attachment/5587012/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1969815 Title: [radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state Status in linux package in Ubuntu: Confirmed Status in marco package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: I've just updated to 22.04 on 3x boxes: 2x laptops and 1x tower. Laptops went well as they are standard running wifi (note to self: next time upgrade one using a USB docking station+as many externally attached devices as possible should prove in a quite pleasurable end- user experience) For the tower: this is the dual-screen portrait system I have been opening up defects for months now. Same config too. Anyways, after I rebooted the overall booting process happened pretty well until TTY7 tried kicking it and totally failed doing so hence rendered my system totally broken. The behavior of my screens is that they started blinking from blank to another type of blank for =<1 second each state. But during one of those states there seemed to be Wayland as I could just see the mouse cursor fly around when activated. Accessing other TTYs was also impossible as even though pressing CTRL+ALT+F2|F3|etc would indeed display a login prompt that within that same blinking instant that it had altered back to only that blinking cursor symbol(_) at the top-hand-left. That behavior held true for all TTYs. Pressing the power button did showed up the UM symbol alongside standard shutdown routine happened OK. Solution was: unplug one of the two monitor and automagically jammy's login screen popped up. If I replug that 2nd monitor while I am inside a working TTY7 session then the same (original) problem happens in which I cannot use any of the screens and when I re-unplug one of the two screens again I am re- back again at the jammy login having lost the current session that I had. Both of my screens are the same model and both use HDMI. I have attached my ~/.config/monitors.xml --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dd3464333 F pulseaudio /dev/snd/controlC0: dd3464333 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 HibernationDevice: RESUME=UUID=88228def-1fb1-4fc3-964c-3106218355eb InstallationDate: Installed on 2020-08-29 (613 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp7s0no wireless extensions. tun0 no wireless extensions. MachineType: System manufacturer System Product Name Package: xorg-server PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/02/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5809 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969815/+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 1969815] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1969815/+attachment/5587010/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1969815 Title: [radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state Status in linux package in Ubuntu: Confirmed Status in marco package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: I've just updated to 22.04 on 3x boxes: 2x laptops and 1x tower. Laptops went well as they are standard running wifi (note to self: next time upgrade one using a USB docking station+as many externally attached devices as possible should prove in a quite pleasurable end- user experience) For the tower: this is the dual-screen portrait system I have been opening up defects for months now. Same config too. Anyways, after I rebooted the overall booting process happened pretty well until TTY7 tried kicking it and totally failed doing so hence rendered my system totally broken. The behavior of my screens is that they started blinking from blank to another type of blank for =<1 second each state. But during one of those states there seemed to be Wayland as I could just see the mouse cursor fly around when activated. Accessing other TTYs was also impossible as even though pressing CTRL+ALT+F2|F3|etc would indeed display a login prompt that within that same blinking instant that it had altered back to only that blinking cursor symbol(_) at the top-hand-left. That behavior held true for all TTYs. Pressing the power button did showed up the UM symbol alongside standard shutdown routine happened OK. Solution was: unplug one of the two monitor and automagically jammy's login screen popped up. If I replug that 2nd monitor while I am inside a working TTY7 session then the same (original) problem happens in which I cannot use any of the screens and when I re-unplug one of the two screens again I am re- back again at the jammy login having lost the current session that I had. Both of my screens are the same model and both use HDMI. I have attached my ~/.config/monitors.xml --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dd3464333 F pulseaudio /dev/snd/controlC0: dd3464333 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 HibernationDevice: RESUME=UUID=88228def-1fb1-4fc3-964c-3106218355eb InstallationDate: Installed on 2020-08-29 (613 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp7s0no wireless extensions. tun0 no wireless extensions. MachineType: System manufacturer System Product Name Package: xorg-server PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/02/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5809 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969815/+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 1969815] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1969815/+attachment/5587009/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1969815 Title: [radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state Status in linux package in Ubuntu: Confirmed Status in marco package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: I've just updated to 22.04 on 3x boxes: 2x laptops and 1x tower. Laptops went well as they are standard running wifi (note to self: next time upgrade one using a USB docking station+as many externally attached devices as possible should prove in a quite pleasurable end- user experience) For the tower: this is the dual-screen portrait system I have been opening up defects for months now. Same config too. Anyways, after I rebooted the overall booting process happened pretty well until TTY7 tried kicking it and totally failed doing so hence rendered my system totally broken. The behavior of my screens is that they started blinking from blank to another type of blank for =<1 second each state. But during one of those states there seemed to be Wayland as I could just see the mouse cursor fly around when activated. Accessing other TTYs was also impossible as even though pressing CTRL+ALT+F2|F3|etc would indeed display a login prompt that within that same blinking instant that it had altered back to only that blinking cursor symbol(_) at the top-hand-left. That behavior held true for all TTYs. Pressing the power button did showed up the UM symbol alongside standard shutdown routine happened OK. Solution was: unplug one of the two monitor and automagically jammy's login screen popped up. If I replug that 2nd monitor while I am inside a working TTY7 session then the same (original) problem happens in which I cannot use any of the screens and when I re-unplug one of the two screens again I am re- back again at the jammy login having lost the current session that I had. Both of my screens are the same model and both use HDMI. I have attached my ~/.config/monitors.xml --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dd3464333 F pulseaudio /dev/snd/controlC0: dd3464333 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 HibernationDevice: RESUME=UUID=88228def-1fb1-4fc3-964c-3106218355eb InstallationDate: Installed on 2020-08-29 (613 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp7s0no wireless extensions. tun0 no wireless extensions. MachineType: System manufacturer System Product Name Package: xorg-server PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/02/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5809 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969815/+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 1969815] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1969815/+attachment/5587008/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1969815 Title: [radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state Status in linux package in Ubuntu: Confirmed Status in marco package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: I've just updated to 22.04 on 3x boxes: 2x laptops and 1x tower. Laptops went well as they are standard running wifi (note to self: next time upgrade one using a USB docking station+as many externally attached devices as possible should prove in a quite pleasurable end- user experience) For the tower: this is the dual-screen portrait system I have been opening up defects for months now. Same config too. Anyways, after I rebooted the overall booting process happened pretty well until TTY7 tried kicking it and totally failed doing so hence rendered my system totally broken. The behavior of my screens is that they started blinking from blank to another type of blank for =<1 second each state. But during one of those states there seemed to be Wayland as I could just see the mouse cursor fly around when activated. Accessing other TTYs was also impossible as even though pressing CTRL+ALT+F2|F3|etc would indeed display a login prompt that within that same blinking instant that it had altered back to only that blinking cursor symbol(_) at the top-hand-left. That behavior held true for all TTYs. Pressing the power button did showed up the UM symbol alongside standard shutdown routine happened OK. Solution was: unplug one of the two monitor and automagically jammy's login screen popped up. If I replug that 2nd monitor while I am inside a working TTY7 session then the same (original) problem happens in which I cannot use any of the screens and when I re-unplug one of the two screens again I am re- back again at the jammy login having lost the current session that I had. Both of my screens are the same model and both use HDMI. I have attached my ~/.config/monitors.xml --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dd3464333 F pulseaudio /dev/snd/controlC0: dd3464333 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 HibernationDevice: RESUME=UUID=88228def-1fb1-4fc3-964c-3106218355eb InstallationDate: Installed on 2020-08-29 (613 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp7s0no wireless extensions. tun0 no wireless extensions. MachineType: System manufacturer System Product Name Package: xorg-server PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/02/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5809 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969815/+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 1969815] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1969815/+attachment/5587004/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1969815 Title: [radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state Status in linux package in Ubuntu: Confirmed Status in marco package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: I've just updated to 22.04 on 3x boxes: 2x laptops and 1x tower. Laptops went well as they are standard running wifi (note to self: next time upgrade one using a USB docking station+as many externally attached devices as possible should prove in a quite pleasurable end- user experience) For the tower: this is the dual-screen portrait system I have been opening up defects for months now. Same config too. Anyways, after I rebooted the overall booting process happened pretty well until TTY7 tried kicking it and totally failed doing so hence rendered my system totally broken. The behavior of my screens is that they started blinking from blank to another type of blank for =<1 second each state. But during one of those states there seemed to be Wayland as I could just see the mouse cursor fly around when activated. Accessing other TTYs was also impossible as even though pressing CTRL+ALT+F2|F3|etc would indeed display a login prompt that within that same blinking instant that it had altered back to only that blinking cursor symbol(_) at the top-hand-left. That behavior held true for all TTYs. Pressing the power button did showed up the UM symbol alongside standard shutdown routine happened OK. Solution was: unplug one of the two monitor and automagically jammy's login screen popped up. If I replug that 2nd monitor while I am inside a working TTY7 session then the same (original) problem happens in which I cannot use any of the screens and when I re-unplug one of the two screens again I am re- back again at the jammy login having lost the current session that I had. Both of my screens are the same model and both use HDMI. I have attached my ~/.config/monitors.xml --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dd3464333 F pulseaudio /dev/snd/controlC0: dd3464333 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 HibernationDevice: RESUME=UUID=88228def-1fb1-4fc3-964c-3106218355eb InstallationDate: Installed on 2020-08-29 (613 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp7s0no wireless extensions. tun0 no wireless extensions. MachineType: System manufacturer System Product Name Package: xorg-server PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/02/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5809 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969815/+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 1969815] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1969815/+attachment/5587006/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1969815 Title: [radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state Status in linux package in Ubuntu: Confirmed Status in marco package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: I've just updated to 22.04 on 3x boxes: 2x laptops and 1x tower. Laptops went well as they are standard running wifi (note to self: next time upgrade one using a USB docking station+as many externally attached devices as possible should prove in a quite pleasurable end- user experience) For the tower: this is the dual-screen portrait system I have been opening up defects for months now. Same config too. Anyways, after I rebooted the overall booting process happened pretty well until TTY7 tried kicking it and totally failed doing so hence rendered my system totally broken. The behavior of my screens is that they started blinking from blank to another type of blank for =<1 second each state. But during one of those states there seemed to be Wayland as I could just see the mouse cursor fly around when activated. Accessing other TTYs was also impossible as even though pressing CTRL+ALT+F2|F3|etc would indeed display a login prompt that within that same blinking instant that it had altered back to only that blinking cursor symbol(_) at the top-hand-left. That behavior held true for all TTYs. Pressing the power button did showed up the UM symbol alongside standard shutdown routine happened OK. Solution was: unplug one of the two monitor and automagically jammy's login screen popped up. If I replug that 2nd monitor while I am inside a working TTY7 session then the same (original) problem happens in which I cannot use any of the screens and when I re-unplug one of the two screens again I am re- back again at the jammy login having lost the current session that I had. Both of my screens are the same model and both use HDMI. I have attached my ~/.config/monitors.xml --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dd3464333 F pulseaudio /dev/snd/controlC0: dd3464333 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 HibernationDevice: RESUME=UUID=88228def-1fb1-4fc3-964c-3106218355eb InstallationDate: Installed on 2020-08-29 (613 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp7s0no wireless extensions. tun0 no wireless extensions. MachineType: System manufacturer System Product Name Package: xorg-server PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/02/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5809 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969815/+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 1969815] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1969815/+attachment/5587007/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1969815 Title: [radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state Status in linux package in Ubuntu: Confirmed Status in marco package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: I've just updated to 22.04 on 3x boxes: 2x laptops and 1x tower. Laptops went well as they are standard running wifi (note to self: next time upgrade one using a USB docking station+as many externally attached devices as possible should prove in a quite pleasurable end- user experience) For the tower: this is the dual-screen portrait system I have been opening up defects for months now. Same config too. Anyways, after I rebooted the overall booting process happened pretty well until TTY7 tried kicking it and totally failed doing so hence rendered my system totally broken. The behavior of my screens is that they started blinking from blank to another type of blank for =<1 second each state. But during one of those states there seemed to be Wayland as I could just see the mouse cursor fly around when activated. Accessing other TTYs was also impossible as even though pressing CTRL+ALT+F2|F3|etc would indeed display a login prompt that within that same blinking instant that it had altered back to only that blinking cursor symbol(_) at the top-hand-left. That behavior held true for all TTYs. Pressing the power button did showed up the UM symbol alongside standard shutdown routine happened OK. Solution was: unplug one of the two monitor and automagically jammy's login screen popped up. If I replug that 2nd monitor while I am inside a working TTY7 session then the same (original) problem happens in which I cannot use any of the screens and when I re-unplug one of the two screens again I am re- back again at the jammy login having lost the current session that I had. Both of my screens are the same model and both use HDMI. I have attached my ~/.config/monitors.xml --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dd3464333 F pulseaudio /dev/snd/controlC0: dd3464333 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 HibernationDevice: RESUME=UUID=88228def-1fb1-4fc3-964c-3106218355eb InstallationDate: Installed on 2020-08-29 (613 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp7s0no wireless extensions. tun0 no wireless extensions. MachineType: System manufacturer System Product Name Package: xorg-server PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/02/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5809 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969815/+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 1969815] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1969815/+attachment/5587005/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1969815 Title: [radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state Status in linux package in Ubuntu: Confirmed Status in marco package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: I've just updated to 22.04 on 3x boxes: 2x laptops and 1x tower. Laptops went well as they are standard running wifi (note to self: next time upgrade one using a USB docking station+as many externally attached devices as possible should prove in a quite pleasurable end- user experience) For the tower: this is the dual-screen portrait system I have been opening up defects for months now. Same config too. Anyways, after I rebooted the overall booting process happened pretty well until TTY7 tried kicking it and totally failed doing so hence rendered my system totally broken. The behavior of my screens is that they started blinking from blank to another type of blank for =<1 second each state. But during one of those states there seemed to be Wayland as I could just see the mouse cursor fly around when activated. Accessing other TTYs was also impossible as even though pressing CTRL+ALT+F2|F3|etc would indeed display a login prompt that within that same blinking instant that it had altered back to only that blinking cursor symbol(_) at the top-hand-left. That behavior held true for all TTYs. Pressing the power button did showed up the UM symbol alongside standard shutdown routine happened OK. Solution was: unplug one of the two monitor and automagically jammy's login screen popped up. If I replug that 2nd monitor while I am inside a working TTY7 session then the same (original) problem happens in which I cannot use any of the screens and when I re-unplug one of the two screens again I am re- back again at the jammy login having lost the current session that I had. Both of my screens are the same model and both use HDMI. I have attached my ~/.config/monitors.xml --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dd3464333 F pulseaudio /dev/snd/controlC0: dd3464333 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 HibernationDevice: RESUME=UUID=88228def-1fb1-4fc3-964c-3106218355eb InstallationDate: Installed on 2020-08-29 (613 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp7s0no wireless extensions. tun0 no wireless extensions. MachineType: System manufacturer System Product Name Package: xorg-server PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/02/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5809 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969815/+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 1969815] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1969815/+attachment/5587002/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1969815 Title: [radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state Status in linux package in Ubuntu: Confirmed Status in marco package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: I've just updated to 22.04 on 3x boxes: 2x laptops and 1x tower. Laptops went well as they are standard running wifi (note to self: next time upgrade one using a USB docking station+as many externally attached devices as possible should prove in a quite pleasurable end- user experience) For the tower: this is the dual-screen portrait system I have been opening up defects for months now. Same config too. Anyways, after I rebooted the overall booting process happened pretty well until TTY7 tried kicking it and totally failed doing so hence rendered my system totally broken. The behavior of my screens is that they started blinking from blank to another type of blank for =<1 second each state. But during one of those states there seemed to be Wayland as I could just see the mouse cursor fly around when activated. Accessing other TTYs was also impossible as even though pressing CTRL+ALT+F2|F3|etc would indeed display a login prompt that within that same blinking instant that it had altered back to only that blinking cursor symbol(_) at the top-hand-left. That behavior held true for all TTYs. Pressing the power button did showed up the UM symbol alongside standard shutdown routine happened OK. Solution was: unplug one of the two monitor and automagically jammy's login screen popped up. If I replug that 2nd monitor while I am inside a working TTY7 session then the same (original) problem happens in which I cannot use any of the screens and when I re-unplug one of the two screens again I am re- back again at the jammy login having lost the current session that I had. Both of my screens are the same model and both use HDMI. I have attached my ~/.config/monitors.xml --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dd3464333 F pulseaudio /dev/snd/controlC0: dd3464333 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 HibernationDevice: RESUME=UUID=88228def-1fb1-4fc3-964c-3106218355eb InstallationDate: Installed on 2020-08-29 (613 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp7s0no wireless extensions. tun0 no wireless extensions. MachineType: System manufacturer System Product Name Package: xorg-server PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/02/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5809 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969815/+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 1969815] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1969815/+attachment/5587003/+files/Dependencies.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/1969815 Title: [radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state Status in linux package in Ubuntu: Confirmed Status in marco package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: I've just updated to 22.04 on 3x boxes: 2x laptops and 1x tower. Laptops went well as they are standard running wifi (note to self: next time upgrade one using a USB docking station+as many externally attached devices as possible should prove in a quite pleasurable end- user experience) For the tower: this is the dual-screen portrait system I have been opening up defects for months now. Same config too. Anyways, after I rebooted the overall booting process happened pretty well until TTY7 tried kicking it and totally failed doing so hence rendered my system totally broken. The behavior of my screens is that they started blinking from blank to another type of blank for =<1 second each state. But during one of those states there seemed to be Wayland as I could just see the mouse cursor fly around when activated. Accessing other TTYs was also impossible as even though pressing CTRL+ALT+F2|F3|etc would indeed display a login prompt that within that same blinking instant that it had altered back to only that blinking cursor symbol(_) at the top-hand-left. That behavior held true for all TTYs. Pressing the power button did showed up the UM symbol alongside standard shutdown routine happened OK. Solution was: unplug one of the two monitor and automagically jammy's login screen popped up. If I replug that 2nd monitor while I am inside a working TTY7 session then the same (original) problem happens in which I cannot use any of the screens and when I re-unplug one of the two screens again I am re- back again at the jammy login having lost the current session that I had. Both of my screens are the same model and both use HDMI. I have attached my ~/.config/monitors.xml --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dd3464333 F pulseaudio /dev/snd/controlC0: dd3464333 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 HibernationDevice: RESUME=UUID=88228def-1fb1-4fc3-964c-3106218355eb InstallationDate: Installed on 2020-08-29 (613 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp7s0no wireless extensions. tun0 no wireless extensions. MachineType: System manufacturer System Product Name Package: xorg-server PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/02/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5809 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969815/+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 1969815] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1969815/+attachment/5587001/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1969815 Title: [radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state Status in linux package in Ubuntu: Confirmed Status in marco package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: I've just updated to 22.04 on 3x boxes: 2x laptops and 1x tower. Laptops went well as they are standard running wifi (note to self: next time upgrade one using a USB docking station+as many externally attached devices as possible should prove in a quite pleasurable end- user experience) For the tower: this is the dual-screen portrait system I have been opening up defects for months now. Same config too. Anyways, after I rebooted the overall booting process happened pretty well until TTY7 tried kicking it and totally failed doing so hence rendered my system totally broken. The behavior of my screens is that they started blinking from blank to another type of blank for =<1 second each state. But during one of those states there seemed to be Wayland as I could just see the mouse cursor fly around when activated. Accessing other TTYs was also impossible as even though pressing CTRL+ALT+F2|F3|etc would indeed display a login prompt that within that same blinking instant that it had altered back to only that blinking cursor symbol(_) at the top-hand-left. That behavior held true for all TTYs. Pressing the power button did showed up the UM symbol alongside standard shutdown routine happened OK. Solution was: unplug one of the two monitor and automagically jammy's login screen popped up. If I replug that 2nd monitor while I am inside a working TTY7 session then the same (original) problem happens in which I cannot use any of the screens and when I re-unplug one of the two screens again I am re- back again at the jammy login having lost the current session that I had. Both of my screens are the same model and both use HDMI. I have attached my ~/.config/monitors.xml --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dd3464333 F pulseaudio /dev/snd/controlC0: dd3464333 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 HibernationDevice: RESUME=UUID=88228def-1fb1-4fc3-964c-3106218355eb InstallationDate: Installed on 2020-08-29 (613 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp7s0no wireless extensions. tun0 no wireless extensions. MachineType: System manufacturer System Product Name Package: xorg-server PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/02/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5809 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969815/+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 1969815] Re: [radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state
apport information ** Tags added: apport-collected ** Description changed: I've just updated to 22.04 on 3x boxes: 2x laptops and 1x tower. Laptops went well as they are standard running wifi (note to self: next time upgrade one using a USB docking station+as many externally attached devices as possible should prove in a quite pleasurable end-user experience) For the tower: this is the dual-screen portrait system I have been opening up defects for months now. Same config too. Anyways, after I rebooted the overall booting process happened pretty well until TTY7 tried kicking it and totally failed doing so hence rendered my system totally broken. The behavior of my screens is that they started blinking from blank to another type of blank for =<1 second each state. But during one of those states there seemed to be Wayland as I could just see the mouse cursor fly around when activated. Accessing other TTYs was also impossible as even though pressing CTRL+ALT+F2|F3|etc would indeed display a login prompt that within that same blinking instant that it had altered back to only that blinking cursor symbol(_) at the top-hand-left. That behavior held true for all TTYs. Pressing the power button did showed up the UM symbol alongside standard shutdown routine happened OK. Solution was: unplug one of the two monitor and automagically jammy's login screen popped up. If I replug that 2nd monitor while I am inside a working TTY7 session then the same (original) problem happens in which I cannot use any of the screens and when I re-unplug one of the two screens again I am re- back again at the jammy login having lost the current session that I had. Both of my screens are the same model and both use HDMI. I have attached my ~/.config/monitors.xml + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: dd3464333 F pulseaudio + /dev/snd/controlC0: dd3464333 F pulseaudio + CasperMD5CheckResult: unknown + CurrentDesktop: MATE + DistroRelease: Ubuntu 22.04 + HibernationDevice: RESUME=UUID=88228def-1fb1-4fc3-964c-3106218355eb + InstallationDate: Installed on 2020-08-29 (613 days ago) + InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) + IwConfig: + lono wireless extensions. + + enp7s0no wireless extensions. + + tun0 no wireless extensions. + MachineType: System manufacturer System Product Name + Package: xorg-server + PackageArchitecture: amd64 + ProcFB: 0 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-25-generic N/A + linux-backports-modules-5.15.0-25-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu1 + RfKill: + + Tags: jammy + Uname: Linux 5.15.0-25-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 12/02/2020 + dmi.bios.release: 5.17 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 5809 + dmi.board.asset.tag: Default string + dmi.board.name: TUF X470-PLUS GAMING + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: Rev X.0x + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 3 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: System Product Name + dmi.product.sku: SKU + dmi.product.version: System Version + dmi.sys.vendor: System manufacturer ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1969815/+attachment/5587000/+files/AlsaInfo.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/1969815 Title: [radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state Status in linux package in Ubuntu: Confirmed Status in marco package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: I've just updated to 22.04 on 3x boxes: 2x laptops and 1x tower. Laptops went well as they are standard running wifi (note to self: next time upgrade one using a USB docking station+as many externally attached devices as possible should prove in a quite pleasurable end- user experience) For the tower: this is the dual-screen
[Kernel-packages] [Bug 1971656] Re: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04
I have been running into the same on my P14s, and I did upgrade to Jammy early march, but it only started to happen very very much only around the 11th of april (I have been updating mostly daily). Since that date, any intensive use of the wifi started to trigger the same behavior, whatever the version of rtw89 driver I was using (bundled in the 5.15 kernel or the one on github). This made my life mostly impossible to work, I switched my laptop to an Intel AC9260 WiFi chip and no more problem since. Over the course of my debugging, I tested older versions of rtw89 repo (that were known to be fine from my earlier use) as well as different rtw89 firmwares versions, to no help. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1971656 Title: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04 Status in linux-firmware package in Ubuntu: Confirmed Bug description: On a Lenovo P14s (RTL8111/8168/8411), the WiFi connection gets stuck at times. When this happens, there is no way to use `sudo`, the WiFi GNOME UI says NetworkManager is not running (which it is), and `dmesg -w` continuously outputs: ``` [90296.470925] rtw89_pci :03:00.0: failed to get available addr cam [90296.470935] rtw89_pci :03:00.0: failed to init addr cam [90296.586817] rtw89_pci :03:00.0: failed to get available addr cam [90296.586828] rtw89_pci :03:00.0: failed to init addr cam [90296.698790] rtw89_pci :03:00.0: failed to get available addr cam [90296.698797] rtw89_pci :03:00.0: failed to init addr cam [90296.810783] rtw89_pci :03:00.0: failed to get available addr cam [90296.810790] rtw89_pci :03:00.0: failed to init addr cam ``` The only solution I've found is to reboot the machine. However, turning off needs to be forced (magic keys still work for rebooting). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 5 07:49:18 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu2 InstallationDate: Installed on 2022-02-25 (68 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 21A3MZ PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) dmi.bios.date: 11/05/2021 dmi.bios.release: 1.13 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET43W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A3MZ dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrR1MET43W(1.13):bd11/05/2021:br1.13:efr1.13:svnLENOVO:pn21A3MZ:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A3MZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A3MZ dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971656/+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 1971656] Re: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1971656 Title: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04 Status in linux-firmware package in Ubuntu: Confirmed Bug description: On a Lenovo P14s (RTL8111/8168/8411), the WiFi connection gets stuck at times. When this happens, there is no way to use `sudo`, the WiFi GNOME UI says NetworkManager is not running (which it is), and `dmesg -w` continuously outputs: ``` [90296.470925] rtw89_pci :03:00.0: failed to get available addr cam [90296.470935] rtw89_pci :03:00.0: failed to init addr cam [90296.586817] rtw89_pci :03:00.0: failed to get available addr cam [90296.586828] rtw89_pci :03:00.0: failed to init addr cam [90296.698790] rtw89_pci :03:00.0: failed to get available addr cam [90296.698797] rtw89_pci :03:00.0: failed to init addr cam [90296.810783] rtw89_pci :03:00.0: failed to get available addr cam [90296.810790] rtw89_pci :03:00.0: failed to init addr cam ``` The only solution I've found is to reboot the machine. However, turning off needs to be forced (magic keys still work for rebooting). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 5 07:49:18 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu2 InstallationDate: Installed on 2022-02-25 (68 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 21A3MZ PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) dmi.bios.date: 11/05/2021 dmi.bios.release: 1.13 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET43W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A3MZ dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrR1MET43W(1.13):bd11/05/2021:br1.13:efr1.13:svnLENOVO:pn21A3MZ:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A3MZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A3MZ dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971656/+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 1971597] Re: amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x0000 to IRQ, err -517
** Changed in: linux (Ubuntu Jammy)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1971597
Title:
amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err
-517
Status in HWE Next:
New
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.14 source package in Focal:
Confirmed
Status in linux-oem-5.17 source package in Focal:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux-oem-5.14 source package in Jammy:
Invalid
Status in linux-oem-5.17 source package in Jammy:
Confirmed
Bug description:
Commit 5467801f1fcb ("gpio: Restrict usage of GPIO chip irq members
before initialization") attempted to fix a race condition that lead to
a NULL pointer, but in the process caused a regression for _AEI/_EVT
declared GPIOs.
This manifests in messages showing deferred probing while trying to
allocate IRQs like so:
amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err -517
amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x002C to IRQ, err -517
amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x003D to IRQ, err -517
[ .. more of the same .. ]
The code for walking _AEI doesn't handle deferred probing and so this
leads to non-functional GPIO interrupts.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1971597/+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 1956086] Re: config CONFIG_HISI_PMU for kunpeng920
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Impish) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956086 Title: config CONFIG_HISI_PMU for kunpeng920 Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 ubuntu-20.04-hwe series: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Bug description: [Impact] We have Hisilicon PMU modules built-in and they can not be unloaded. There is no way to replace with a updated module unless we build it as module. [Test Plan] `lsmod | grep hisi_uncore` shall see 4 modules loaded and they can be unloaded. [Regression Risk] CONFIG_HISI_PMU shall be only affected Hisilicon platforms that HISI0213 is found in ACPI tables. We shall have perf test run on these platforms and others have lowest risk. = [Bug Description] hisi pmu support x.ko module to use it for kunpeng920 [Steps to Reproduce] 1) cd /lib/modules/$(uname -r)/kernel/drivers/perf/hisilicon 2) check *.ko 3) [Actual Results] @ubuntu:~$ cat /boot/config-4.15.0-140-generic | grep -i CONFIG_HISI_PMU CONFIG_HISI_PMU=y [Expected Results] @ubuntu:~$ cat /boot/config-4.15.0-140-generic | grep -i CONFIG_HISI_PMU CONFIG_HISI_PMU=m [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] drivers/perf: hisi: Permit modular builds of HiSilicon uncore drivers To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1956086/+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 1971701] Re: Azure: swiotlb patch needed for CVM
** Also affects: linux-azure (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1971701 Title: Azure: swiotlb patch needed for CVM Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Jammy: In Progress Bug description: SRU Justification [Impact] [Azure][CVM] Include the swiotlb patch to increase the disk/network performance Description As we discussed, there will be new CVM-supporting linux-azure kernels that're based on v5.13 and v5.15. Here I'm requesting the below patch to be included into the two kernels because it can significantly improve the disk/network performance: swiotlb: Split up single swiotlb lock: https://github.com/intel/tdx/commit/4529b5784c141782c72ec9bd9a92df2b68cb7d45 We have tested the patch with the upstream 5.16-rc8. BTW, the patch is unlikely to be in the mainline kernel, as the community is trying to resolve the lock contention issue in the swiotlb code using a different per-device per-queue implementation, which would need quite some time to be finalized -- before that happens, we need this out-of-tree patch to achieve good disk/network performance for CVM GA on Azure. (BTW, the v5.4-based linux-azure-cvm kernel does not need the patch, because it uses a private bounce buffer implementation: drivers/hv/hv_bounce.c, which doesn’t have the I/O performance issue caused by lock contention in the mainline kernel’s swiotlb code.) [Test Case] [Microsoft tested] I tried the April-27 amd64 test kernel and it worked great for me: 1. The test kernels booted up successfully with 256 virtual CPUs + 100 GB memory. 2. The kernel worked when I changed the MTU of the NetVSC NIC. 3. The Hyper-V HeartBeat/TimeSync/ShutDown VMBsus devices also worked as expected. 4. I did some quick disk I/O and network stress tests and found no issue. When I did the above tests, I changed the low MMIO size to 3GB (which is the setting for a VM on Azure today) by "set-vm decui-u2004-cvm -LowMemoryMappedIoSpace 3GB". Our test team will do more testing, including performance test. We expect the performance of this v5.15 test kernel should be on par with the v5.4 linux-azure-cvm kernel. [Where things could go wrong] Networking could fail or continue to suffer from poor performance. [Other Info] SF: #00332721 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1971701/+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 1970552] Re: Mute/mic LEDs no function on EliteBook G9 platfroms
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1970552 Title: Mute/mic LEDs no function on EliteBook G9 platfroms Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] The mic mute/audio mute LEDS are not work on 1) HP EliteBook x360 830 G9 2) HP EliteBook 830 G9 3) HP EliteBook 840 G9 4) HP EliteBook 860 G9 5) HP EliteBook 840 Aero G9 6) HP EliteBook x360 840 Aero G9 [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1970552/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971699] Re: disable Intel DMA remapping by default
** Summary changed: - disable Intel DMA remapping options by default + disable Intel DMA remapping by default -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971699 Title: disable Intel DMA remapping by default Status in linux package in Ubuntu: Incomplete Bug description: [Impact] It seems that enabling Intel IOMMU can cause some weird gfx problems, see for example: https://bugs.launchpad.net/bugs/1971146 https://bugs.launchpad.net/bugs/1965882 [Test case] We don't have any specific test case, only other bug reports that tracked down the origin of the issue as being introduced when CONFIG_INTEL_IOMMU_DEFAULT_ON has been enabled by default. [Fix] Revert "UBUNTU: [Config] enable Intel DMA remapping options by default" [Regression potential] DMA remapping device not present at boot by default, users that require this feature will need to specifically add intel_iommu=on to the kernel boot parameters to enable it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971700] [NEW] [jammy] 5.17.0-1004-oem breaks resume from sleep
Public bug reported: I cannot resume from sleep, I have to hard reboot. Does not happen with 5.17.0-1003-oem. Thinkpad P14s, AMD 5850u, wifi rtl 8852a, ssd nvme hynix Cannot give more details atm. ** Affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1971700 Title: [jammy] 5.17.0-1004-oem breaks resume from sleep Status in linux-oem-5.17 package in Ubuntu: New Bug description: I cannot resume from sleep, I have to hard reboot. Does not happen with 5.17.0-1003-oem. Thinkpad P14s, AMD 5850u, wifi rtl 8852a, ssd nvme hynix Cannot give more details atm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971700/+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 1971701] [NEW] Azure: swiotlb patch needed for CVM
Public bug reported: SRU Justification [Impact] [Azure][CVM] Include the swiotlb patch to increase the disk/network performance Description As we discussed, there will be new CVM-supporting linux-azure kernels that're based on v5.13 and v5.15. Here I'm requesting the below patch to be included into the two kernels because it can significantly improve the disk/network performance: swiotlb: Split up single swiotlb lock: https://github.com/intel/tdx/commit/4529b5784c141782c72ec9bd9a92df2b68cb7d45 We have tested the patch with the upstream 5.16-rc8. BTW, the patch is unlikely to be in the mainline kernel, as the community is trying to resolve the lock contention issue in the swiotlb code using a different per-device per-queue implementation, which would need quite some time to be finalized -- before that happens, we need this out-of-tree patch to achieve good disk/network performance for CVM GA on Azure. (BTW, the v5.4-based linux-azure-cvm kernel does not need the patch, because it uses a private bounce buffer implementation: drivers/hv/hv_bounce.c, which doesn’t have the I/O performance issue caused by lock contention in the mainline kernel’s swiotlb code.) [Test Case] [Microsoft tested] I tried the April-27 amd64 test kernel and it worked great for me: 1. The test kernels booted up successfully with 256 virtual CPUs + 100 GB memory. 2. The kernel worked when I changed the MTU of the NetVSC NIC. 3. The Hyper-V HeartBeat/TimeSync/ShutDown VMBsus devices also worked as expected. 4. I did some quick disk I/O and network stress tests and found no issue. When I did the above tests, I changed the low MMIO size to 3GB (which is the setting for a VM on Azure today) by "set-vm decui-u2004-cvm -LowMemoryMappedIoSpace 3GB". Our test team will do more testing, including performance test. We expect the performance of this v5.15 test kernel should be on par with the v5.4 linux-azure-cvm kernel. [Where things could go wrong] Networking could fail or continue to suffer from poor performance. [Other Info] SF: #00332721 ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => linux-azure (Ubuntu) ** Description changed: SRU Justification [Impact] - [Azure][CVM] Include the swiotlb patch to increase the disk/network performance + [Azure][CVM] Include the swiotlb patch to increase the disk/network + performance + Description As we discussed, there will be new CVM-supporting linux-azure kernels that're based on v5.13 and v5.15. Here I'm requesting the below patch to be included into the two kernels because it can significantly improve the disk/network performance: swiotlb: Split up single swiotlb lock: https://github.com/intel/tdx/commit/4529b5784c141782c72ec9bd9a92df2b68cb7d45 We have tested the patch with the upstream 5.16-rc8. - Not sure if the patch can apply cleanly to the v5.13 and v5.15 kernels. If not, I think we can help do the rebasing. BTW, the patch is unlikely to be in the mainline kernel, as the community is trying to resolve the lock contention issue in the swiotlb code using a different per-device per-queue implementation, which would need quite some time to be finalized -- before that happens, we need this out-of-tree patch to achieve good disk/network performance for CVM GA on Azure. (BTW, the v5.4-based linux-azure-cvm kernel does not need the patch, because it uses a private bounce buffer implementation: drivers/hv/hv_bounce.c, which doesn’t have the I/O performance issue caused by lock contention in the mainline kernel’s swiotlb code.) [Test Case] [Microsoft tested] - -I tried the April-27 amd64 test kernel and it worked great for me: + I tried the April-27 amd64 test kernel and it worked great for me: 1. The test kernels booted up successfully with 256 virtual CPUs + 100 GB memory. 2. The kernel worked when I changed the MTU of the NetVSC NIC. 3. The Hyper-V HeartBeat/TimeSync/ShutDown VMBsus devices also worked as expected. 4. I did some quick disk I/O and network stress tests and found no issue. When I did the above tests, I changed the low MMIO size to 3GB (which is the setting for a VM on Azure today) by "set-vm decui-u2004-cvm -LowMemoryMappedIoSpace 3GB". Our test team will do more testing, including performance test. We expect the performance of this v5.15 test kernel should be on par with the v5.4 linux-azure-cvm kernel. [Where things could go wrong] Networking could fail or continue to suffer from poor performance. [Other Info] SF: #00332721 -- 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/1971701 Title: Azure: swiotlb patch needed for CVM Status in linux-azure package in Ubuntu: New Bug description: SRU Justification [Impact] [Azure][CVM] Include the swiotlb patch to increase
[Kernel-packages] [Bug 1971656] Re: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04
Is this a regression? I.e. did this work before you upgraded to Jammy? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1971656 Title: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04 Status in linux-firmware package in Ubuntu: New Bug description: On a Lenovo P14s (RTL8111/8168/8411), the WiFi connection gets stuck at times. When this happens, there is no way to use `sudo`, the WiFi GNOME UI says NetworkManager is not running (which it is), and `dmesg -w` continuously outputs: ``` [90296.470925] rtw89_pci :03:00.0: failed to get available addr cam [90296.470935] rtw89_pci :03:00.0: failed to init addr cam [90296.586817] rtw89_pci :03:00.0: failed to get available addr cam [90296.586828] rtw89_pci :03:00.0: failed to init addr cam [90296.698790] rtw89_pci :03:00.0: failed to get available addr cam [90296.698797] rtw89_pci :03:00.0: failed to init addr cam [90296.810783] rtw89_pci :03:00.0: failed to get available addr cam [90296.810790] rtw89_pci :03:00.0: failed to init addr cam ``` The only solution I've found is to reboot the machine. However, turning off needs to be forced (magic keys still work for rebooting). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 5 07:49:18 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu2 InstallationDate: Installed on 2022-02-25 (68 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 21A3MZ PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) dmi.bios.date: 11/05/2021 dmi.bios.release: 1.13 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET43W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A3MZ dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrR1MET43W(1.13):bd11/05/2021:br1.13:efr1.13:svnLENOVO:pn21A3MZ:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A3MZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A3MZ dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971656/+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 1967924] Re: re-apply missing overlayfs SAUCE patch
** Changed in: linux (Ubuntu Impish)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967924
Title:
re-apply missing overlayfs SAUCE patch
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Status in linux source package in Jammy:
Fix Committed
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch seems to be required to use overlayfs on top of shiftfs and
without this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
[Test case]
No specific test case provided.
[Fix]
The original SAUCE patch relies on AUFS in order to use
vma->vm_prfile, but we're not providing AUFS anymore in jammy,.
The fix consists of re-apply this patch with a little refactoring to
be dependent on CONFIG_AUFS_FS.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs.
[Original bug report]
The next patch has not been ported to the the 5.13 branch:
$ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
Author: Alexander Mikhalitsyn
Date: Mon Apr 26 10:11:00 2021 +0200
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
BugLink: https://bugs.launchpad.net/bugs/1857257
...
Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
underlay")
But it isn't in the 5.13 branch:
$ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct
ovl_aio_req
7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying
fs doesn't support direct IO
1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with
shiftfs as underlay
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971699] 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 1971699 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/1971699 Title: disable Intel DMA remapping by default Status in linux package in Ubuntu: Incomplete Bug description: [Impact] It seems that enabling Intel IOMMU can cause some weird gfx problems, see for example: https://bugs.launchpad.net/bugs/1971146 https://bugs.launchpad.net/bugs/1965882 [Test case] We don't have any specific test case, only other bug reports that tracked down the origin of the issue as being introduced when CONFIG_INTEL_IOMMU_DEFAULT_ON has been enabled by default. [Fix] Revert "UBUNTU: [Config] enable Intel DMA remapping options by default" [Regression potential] DMA remapping device not present at boot by default, users that require this feature will need to specifically add intel_iommu=on to the kernel boot parameters to enable it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971699] [NEW] disable Intel DMA remapping by default
Public bug reported: [Impact] It seems that enabling Intel IOMMU can cause some weird gfx problems, see for example: https://bugs.launchpad.net/bugs/1971146 https://bugs.launchpad.net/bugs/1965882 [Test case] We don't have any specific test case, only other bug reports that tracked down the origin of the issue as being introduced when CONFIG_INTEL_IOMMU_DEFAULT_ON has been enabled by default. [Fix] Revert "UBUNTU: [Config] enable Intel DMA remapping options by default" [Regression potential] DMA remapping device not present at boot by default, users that require this feature will need to specifically add intel_iommu=on to the kernel boot parameters to enable it. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Package changed: linux-firmware (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1971699 Title: disable Intel DMA remapping by default Status in linux package in Ubuntu: Incomplete Bug description: [Impact] It seems that enabling Intel IOMMU can cause some weird gfx problems, see for example: https://bugs.launchpad.net/bugs/1971146 https://bugs.launchpad.net/bugs/1965882 [Test case] We don't have any specific test case, only other bug reports that tracked down the origin of the issue as being introduced when CONFIG_INTEL_IOMMU_DEFAULT_ON has been enabled by default. [Fix] Revert "UBUNTU: [Config] enable Intel DMA remapping options by default" [Regression potential] DMA remapping device not present at boot by default, users that require this feature will need to specifically add intel_iommu=on to the kernel boot parameters to enable it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1969959] Re: [nouveau] Weird colors after startup (Ubuntu 22.04)
I struggled with this issue for a while until I discovered thar the issue is with the color profile as described in this question https://askubuntu.com/questions/1404516/screen-turns-yellow-even-using- the-live-option-ubuntu-22-04. The way to solve it for me was to add a new color profile in Setting/Color tab -> Add profile for a display. "Standard Space - sRGB" works just right for my Dell XPS 9560 laptop. The issue must be with how the default color profiles are generated for a screen. I have an external monitor and there were no issue with colors there. -- 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/1969959 Title: [nouveau] Weird colors after startup (Ubuntu 22.04) Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: [Workaround/Fix] 1. When starting the Ubuntu live image, select the option 'Ubuntu (safe graphics)' from the boot menu. 2. During installation be sure to select the third-party software option checkbox in order to get the right Nvidia driver installed. [Original Description] I started Ubuntu 22.04 from a live pen drive. Everything seems fine, the usual screen with the options to "Try Ubuntu" or "Install" Ubuntu appears. When hitting "Try Ubuntu", the screen turns black for a couple of seconds and then re-appears in yellow and brown colors, feels like a 4 color display (white, black, yellow and orange) and I can hardly see anything - sending this bug report from that live system right after starting it up. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.470 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:54:05 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d9) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7C56 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969959/+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 1971656] Re: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.18-rc5/ Please try AMD64 build. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1971656 Title: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04 Status in linux-firmware package in Ubuntu: New Bug description: On a Lenovo P14s (RTL8111/8168/8411), the WiFi connection gets stuck at times. When this happens, there is no way to use `sudo`, the WiFi GNOME UI says NetworkManager is not running (which it is), and `dmesg -w` continuously outputs: ``` [90296.470925] rtw89_pci :03:00.0: failed to get available addr cam [90296.470935] rtw89_pci :03:00.0: failed to init addr cam [90296.586817] rtw89_pci :03:00.0: failed to get available addr cam [90296.586828] rtw89_pci :03:00.0: failed to init addr cam [90296.698790] rtw89_pci :03:00.0: failed to get available addr cam [90296.698797] rtw89_pci :03:00.0: failed to init addr cam [90296.810783] rtw89_pci :03:00.0: failed to get available addr cam [90296.810790] rtw89_pci :03:00.0: failed to init addr cam ``` The only solution I've found is to reboot the machine. However, turning off needs to be forced (magic keys still work for rebooting). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 5 07:49:18 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu2 InstallationDate: Installed on 2022-02-25 (68 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 21A3MZ PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) dmi.bios.date: 11/05/2021 dmi.bios.release: 1.13 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET43W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A3MZ dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrR1MET43W(1.13):bd11/05/2021:br1.13:efr1.13:svnLENOVO:pn21A3MZ:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A3MZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A3MZ dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971656/+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 1971656] Re: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04
Thanks for your reply Aaron. Is there an official Ubuntu package for kernel 5.18-rc which I could try? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1971656 Title: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04 Status in linux-firmware package in Ubuntu: New Bug description: On a Lenovo P14s (RTL8111/8168/8411), the WiFi connection gets stuck at times. When this happens, there is no way to use `sudo`, the WiFi GNOME UI says NetworkManager is not running (which it is), and `dmesg -w` continuously outputs: ``` [90296.470925] rtw89_pci :03:00.0: failed to get available addr cam [90296.470935] rtw89_pci :03:00.0: failed to init addr cam [90296.586817] rtw89_pci :03:00.0: failed to get available addr cam [90296.586828] rtw89_pci :03:00.0: failed to init addr cam [90296.698790] rtw89_pci :03:00.0: failed to get available addr cam [90296.698797] rtw89_pci :03:00.0: failed to init addr cam [90296.810783] rtw89_pci :03:00.0: failed to get available addr cam [90296.810790] rtw89_pci :03:00.0: failed to init addr cam ``` The only solution I've found is to reboot the machine. However, turning off needs to be forced (magic keys still work for rebooting). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 5 07:49:18 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu2 InstallationDate: Installed on 2022-02-25 (68 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 21A3MZ PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) dmi.bios.date: 11/05/2021 dmi.bios.release: 1.13 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET43W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A3MZ dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrR1MET43W(1.13):bd11/05/2021:br1.13:efr1.13:svnLENOVO:pn21A3MZ:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A3MZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A3MZ dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971656/+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 1877415] Re: Add crda dependency
** Changed in: linux-raspi-5.4 (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux-raspi2 (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1877415 Title: Add crda dependency Status in linux-raspi package in Ubuntu: Fix Released Status in linux-raspi-5.4 package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi-5.4 source package in Bionic: Fix Committed Status in linux-raspi2 source package in Bionic: Fix Committed Status in linux-raspi source package in Focal: Fix Released Bug description: [Impact] crda is required to setup wifi. For the main kernel, the modules extra package depends on crda so it's pulled in automatically but the raspi kernel doesn't provide a modules extra package with the result that the crda package is missing from the raspi images. Apparently building images with device-specific packages installed is not possible. [Test Case] Spin up a preinstalled server image and: $ dpkg -l crda dpkg-query: no packages found matching crda [Regression Potential] Low. This will just pull in the crda package with its dependencies. [Original Description] We need to add the "iw" package to the pi images (for configuration of the wifi region upon boot). However, as we don't have per-device seeds this can't be placed directly in the seed for the images (without affecting other images which don't need it). Hence, adding it as a "fake" dependency of the pi-specific kernel package is a reasonably clean solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1877415/+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 1971696] [NEW] package libgl1-amber-dri (not installed) failed to install/upgrade: Versuch, »/usr/lib/x86_64-linux-gnu/dri/i915_dri.so« zu überschreiben, welches auch in Paket l
Public bug reported: Some problems with the amber driver that pops up after the startup ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libgl1-amber-dri (not installed) Uname: Linux 5.17.5-051705-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu May 5 10:49:05 2022 ErrorMessage: Versuch, »/usr/lib/x86_64-linux-gnu/dri/i915_dri.so« zu überschreiben, welches auch in Paket libgl1-mesa-dri:amd64 22.2~git2205050600.7a6d85~oibaf~j ist InstallationDate: Installed on 2022-04-04 (30 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2 apt 2.4.5 SourcePackage: mesa-amber Title: package libgl1-amber-dri (not installed) failed to install/upgrade: Versuch, »/usr/lib/x86_64-linux-gnu/dri/i915_dri.so« zu überschreiben, welches auch in Paket libgl1-mesa-dri:amd64 22.2~git2205050600.7a6d85~oibaf~j ist UpgradeStatus: Upgraded to jammy on 2022-04-04 (30 days ago) ** Affects: mesa-amber (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to mesa-amber in Ubuntu. https://bugs.launchpad.net/bugs/1971696 Title: package libgl1-amber-dri (not installed) failed to install/upgrade: Versuch, »/usr/lib/x86_64-linux-gnu/dri/i915_dri.so« zu überschreiben, welches auch in Paket libgl1-mesa-dri:amd64 22.2~git2205050600.7a6d85~oibaf~j ist Status in mesa-amber package in Ubuntu: New Bug description: Some problems with the amber driver that pops up after the startup ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libgl1-amber-dri (not installed) Uname: Linux 5.17.5-051705-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu May 5 10:49:05 2022 ErrorMessage: Versuch, »/usr/lib/x86_64-linux-gnu/dri/i915_dri.so« zu überschreiben, welches auch in Paket libgl1-mesa-dri:amd64 22.2~git2205050600.7a6d85~oibaf~j ist InstallationDate: Installed on 2022-04-04 (30 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2 apt 2.4.5 SourcePackage: mesa-amber Title: package libgl1-amber-dri (not installed) failed to install/upgrade: Versuch, »/usr/lib/x86_64-linux-gnu/dri/i915_dri.so« zu überschreiben, welches auch in Paket libgl1-mesa-dri:amd64 22.2~git2205050600.7a6d85~oibaf~j ist UpgradeStatus: Upgraded to jammy on 2022-04-04 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa-amber/+bug/1971696/+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 1971146] Re: [radeon] Pictures including wallpaper not showing in kernel 5.14.21 and later (but 5.14.20 and earlier works)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951440 -- 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/1971146 Title: [radeon] Pictures including wallpaper not showing in kernel 5.14.21 and later (but 5.14.20 and earlier works) Status in linux package in Ubuntu: Triaged Bug description: I can't see pictures in emails or on some pictures on websites. Sometimes it just shows the bottom 20mm of pictures. The wallpaper is just a blank white screen. 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 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 2 13:12:31 2022 DistUpgraded: 2022-04-24 19:05:38,365 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Venus XT [Radeon HD 8870M / R9 M270X/M370X] [1002:6821] (rev 83) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Radeon R9 M370X Mac Edition [106b:0149] InstallationDate: Installed on 2021-04-26 (371 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 003: ID 05ac:8406 Apple, Inc. Internal Memory Card Reader Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bluetooth Host Controller Bus 001 Device 003: ID 05ac:0274 Apple, Inc. Apple Internal Keyboard / Trackpad Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro11,5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=2234e6d3-3ebc-44e6-b0a5-bef132fd1f72 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-24 (7 days ago) dmi.bios.date: 06/11/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 199.0.0.0.0 dmi.board.name: Mac-06F11F11946D27C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,5 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11F11946D27C5 dmi.modalias: dmi:bvnAppleInc.:bvr199.0.0.0.0:bd06/11/2020:br0.1:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5:sku: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,5 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971146/+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 1971146] Re: [radeon] Pictures including wallpaper not showing in kernel 5.14.21 and later (but 5.14.20 and earlier works)
--- config-5.14.20-051420-generic 2021-11-18 16:31:49.0 +0200 +++ config-5.14.21-051421-generic 2021-11-21 15:31:59.0 +0200 @@ -1,8 +1,8 @@ # # Automatically generated file; DO NOT EDIT. -# Linux/x86 5.14.20-051420-generic Kernel Configuration +# Linux/x86 5.14.21-051421-generic Kernel Configuration # -CONFIG_CC_VERSION_TEXT="gcc (Ubuntu 11.2.0-10ubuntu1) 11.2.0" +CONFIG_CC_VERSION_TEXT="gcc (Ubuntu 11.2.0-12ubuntu1) 11.2.0" CONFIG_CC_IS_GCC=y CONFIG_GCC_VERSION=110200 CONFIG_CLANG_VERSION=0 @@ -9036,9 +9036,9 @@ CONFIG_DMAR_TABLE=y CONFIG_INTEL_IOMMU=y CONFIG_INTEL_IOMMU_SVM=y -# CONFIG_INTEL_IOMMU_DEFAULT_ON is not set +CONFIG_INTEL_IOMMU_DEFAULT_ON=y CONFIG_INTEL_IOMMU_FLOPPY_WA=y -# CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON is not set +CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON=y CONFIG_IRQ_REMAP=y CONFIG_HYPERV_IOMMU=y CONFIG_VIRTIO_IOMMU=y -- 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/1971146 Title: [radeon] Pictures including wallpaper not showing in kernel 5.14.21 and later (but 5.14.20 and earlier works) Status in linux package in Ubuntu: Triaged Bug description: I can't see pictures in emails or on some pictures on websites. Sometimes it just shows the bottom 20mm of pictures. The wallpaper is just a blank white screen. 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 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 2 13:12:31 2022 DistUpgraded: 2022-04-24 19:05:38,365 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Venus XT [Radeon HD 8870M / R9 M270X/M370X] [1002:6821] (rev 83) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Radeon R9 M370X Mac Edition [106b:0149] InstallationDate: Installed on 2021-04-26 (371 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 003: ID 05ac:8406 Apple, Inc. Internal Memory Card Reader Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bluetooth Host Controller Bus 001 Device 003: ID 05ac:0274 Apple, Inc. Apple Internal Keyboard / Trackpad Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro11,5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=2234e6d3-3ebc-44e6-b0a5-bef132fd1f72 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-24 (7 days ago) dmi.bios.date: 06/11/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 199.0.0.0.0 dmi.board.name: Mac-06F11F11946D27C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,5 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11F11946D27C5 dmi.modalias: dmi:bvnAppleInc.:bvr199.0.0.0.0:bd06/11/2020:br0.1:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5:sku: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,5 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971146/+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 1971146] Re: [radeon] Pictures including wallpaper not showing in kernel 5.14.21 and later (but 5.14.20 and earlier works)
extract the kernel, diff ../boot/config-* -- 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/1971146 Title: [radeon] Pictures including wallpaper not showing in kernel 5.14.21 and later (but 5.14.20 and earlier works) Status in linux package in Ubuntu: Triaged Bug description: I can't see pictures in emails or on some pictures on websites. Sometimes it just shows the bottom 20mm of pictures. The wallpaper is just a blank white screen. 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 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 2 13:12:31 2022 DistUpgraded: 2022-04-24 19:05:38,365 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Venus XT [Radeon HD 8870M / R9 M270X/M370X] [1002:6821] (rev 83) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Radeon R9 M370X Mac Edition [106b:0149] InstallationDate: Installed on 2021-04-26 (371 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 003: ID 05ac:8406 Apple, Inc. Internal Memory Card Reader Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bluetooth Host Controller Bus 001 Device 003: ID 05ac:0274 Apple, Inc. Apple Internal Keyboard / Trackpad Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro11,5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=2234e6d3-3ebc-44e6-b0a5-bef132fd1f72 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-24 (7 days ago) dmi.bios.date: 06/11/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 199.0.0.0.0 dmi.board.name: Mac-06F11F11946D27C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,5 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11F11946D27C5 dmi.modalias: dmi:bvnAppleInc.:bvr199.0.0.0.0:bd06/11/2020:br0.1:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5:sku: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,5 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971146/+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 1970957] Re: suspend problem
+1 for T460. I have to poweroff the laptop and then hold power button to totally cut the power. Hope the fix will be available soon. -- 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/1970957 Title: suspend problem Status in linux package in Ubuntu: Confirmed Bug description: I've installed Ubuntu 22.04 on the ThinkPad E480. Suspend functions ok intermittently. Some times it works fine, other times the computer does not enter the suspend mode (the screen gets blank, but the machine is still running and the ThinPad led is on, and there is no way out... no response from keyboard or mouse... the only solution is to switch off manually hitting and holding the power button), other times the machine does not wakes up from suspension mode. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 10:53:59 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leoca 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20KQ000EBR Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=1e7d6212-699d-4319-b137-8a7059545433 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/14/2018 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R0PET42W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KQ000EBR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR0PET42W(1.19):bd06/14/2018:br1.19:efr1.19:svnLENOVO:pn20KQ000EBR:pvrThinkPadE480:rvnLENOVO:rn20KQ000EBR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KQ_BU_Think_FM_ThinkPadE480: dmi.product.family: ThinkPad E480 dmi.product.name: 20KQ000EBR dmi.product.sku: LENOVO_MT_20KQ_BU_Think_FM_ThinkPad E480 dmi.product.version: ThinkPad E480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970957/+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 1969181] Re: [SRU][OEM-5.14] Fix iwlwifi iwl-nvm-parse.c warning
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1969181 Title: [SRU][OEM-5.14] Fix iwlwifi iwl-nvm-parse.c warning Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] With Intel wifi card [8086:51f0], boot with oem-5.14.0-1027+, the warning will be shown: Mar 14 23:30:36 Phoenix-1 kernel: Call Trace: Mar 14 23:30:36 Phoenix-1 kernel: Mar 14 23:30:36 Phoenix-1 kernel: iwl_mvm_get_regdomain+0xe2/0x1d0 [iwlmvm] Mar 14 23:30:36 Phoenix-1 kernel: iwl_mvm_get_current_regdomain+0x4c/0x50 [iwlmvm] Mar 14 23:30:36 Phoenix-1 kernel: iwl_mvm_init_mcc+0x81/0x1d0 [iwlmvm] Mar 14 23:30:36 Phoenix-1 kernel: ? iwl_acpi_get_dsm_u32+0x2f/0x60 [iwlwifi] Mar 14 23:30:36 Phoenix-1 kernel: iwl_mvm_up+0x87a/0xd70 [iwlmvm] Mar 14 23:30:36 Phoenix-1 kernel: __iwl_mvm_mac_start+0x2b/0x190 [iwlmvm] Mar 14 23:30:36 Phoenix-1 kernel: iwl_mvm_mac_start+0x50/0xb0 [iwlmvm] Mar 14 23:30:36 Phoenix-1 kernel: drv_start+0x40/0xd0 [mac80211] Mar 14 23:30:36 Phoenix-1 kernel: ieee80211_do_open+0x394/0x810 [mac80211] Mar 14 23:30:36 Phoenix-1 kernel: ieee80211_open+0x6c/0x90 [mac80211] [Fix] This warning is introduced by commit: commit 827b84824ef2d910930c9974765de592e77b5072 Author: Chia-Lin Kao (AceLan) Date: Wed Feb 23 18:40:13 2022 +0800 UBUNTU: SAUCE: iwlwifi: disable 6-7 GHz channels BugLink: https://bugs.launchpad.net/bugs/1961971 Disable UHB (ultra high band) channels on all AX210/AX211 cards Signed-off-by: Chia-Lin Kao (AceLan) Signed-off-by: Timo Aaltonen Replace the warning to debug info to avoid the error message. [Test] Verified on HW with Intel wifi card, no errors after boot. [Where problems could occur] It may break Intel wifi driver. Change the debug info only, it's unlikely. The issue is on oem-5.14 only, no need for other kernel version. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1969181/+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 EYPC (Asus) server
more test as below: 5.11.0-27 hotplug works 5.13.0-40 hotplug doesn't work -- 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 EYPC (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 1956760] Re: xHCI (xhci_hcd) host controller not working after unattended kernel upgrade
I guess the problem is already fixed in a newer version because I cannot reproduce it anymore. ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1956760 Title: xHCI (xhci_hcd) host controller not working after unattended kernel upgrade Status in linux package in Ubuntu: Fix Released Bug description: After the unattended-upgrade on January 5th (i.e. 5.4.0-92.103~18.04.2, automatic), the xHCI (xhci_hcd) host controller stopped working (i.e. no USB device is working): ===>dmesg log: linux1804 kernel: xhci_hcd :00:14.0: Abort failed to stop command ring: -110 linux1804 kernel: xhci_hcd :00:14.0: xHCI host controller not responding, assume dead linux1804 kernel: xhci_hcd :00:14.0: HC died; cleaning up linux1804 kernel: xhci_hcd :00:14.0: Timeout while waiting for setup device command linux1804 kernel: usb 4-1: device not accepting address 2, error -108 linux1804 kernel: usb usb4-port1: couldn't allocate usb_device linux1804 kernel: usb usb3-port1: couldn't allocate usb_device ===>unattended-upgrade info: Start-Date: 2022-01-05 11:08:54 Commandline: /usr/bin/unattended-upgrade Install: linux-image-5.4.0-92-generic:amd64 (5.4.0-92.103~18.04.2, automatic), linux-modules- extra-5.4.0-92-generic:amd64 (5.4.0-92.103~18.04.2, automatic), linux-headers-5.4.0-92 -generic:amd64 (5.4.0-92.103~18.04.2, automatic), linux-hwe-5.4-headers-5.4.0-92:amd64 (5.4.0-92.103~18.04.2, automatic), linux-modules-5.4.0-92-generic:amd64 (5.4.0-92.103~18.04.2, automatic) Upgrade: linux-headers-generic-hwe-18.04:amd64 (5.4.0.91.102~18.04.81, 5.4.0.92.103~18.04.82), linux-image-generic-hwe-18.04:amd64 (5.4.0.91.102~18.04.81, 5.4.0.92.103~18.04.82), linux-generic-hwe-18.04:amd64 (5.4.0.91.102~18.04.81, 5.4.0.92.103~18.04.82) End-Date: 2022-01-05 11:09:29 ===>lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 ===>Workaround: This happens on any boot after power off. If I restart the computer, the problem is not reproducible. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2060 F pulseaudio igoretov 8697 F pulseaudio /dev/snd/controlC0: gdm2060 F pulseaudio igoretov 8697 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-07-15 (913 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. N551JW Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-92-generic root=UUID=446babcc-3c36-4899-ac47-f721db732d2a ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-92.103~18.04.2-generic 5.4.157 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-92-generic N/A linux-backports-modules-5.4.0-92-generic N/A linux-firmware1.173.20 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.4.0-92-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 01/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N551JW.202 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N551JW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN551JW.202:bd01/16/2015:svnASUSTeKCOMPUTERINC.:pnN551JW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551JW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N551JW 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/linux/+bug/1956760/+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 1971418] Re: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
With the revert, the network-manager ADT tests work again. https://autopkgtest.ubuntu.com/results/autopkgtest- jammy/jammy/amd64/n/network-manager/20220505_053118_fb2db@/log.gz ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- 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/1971418 Title: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29 Status in linux package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in network-manager source package in Jammy: Invalid Bug description: This is a scripted bug report about ADT failures while running network-manager tests for linux/5.15.0-28.29 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/n/network-manager/20220503_090742_432dd@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/n/network-manager/20220429_062345_345a3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/n/network-manager/20220429_060513_fc2a9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971418/+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 1935754] Re: [HP EliteBook 850 G6] laptop brightness hotkey after latest update
Shutdown the system, press power button for 15 seconds should fix 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/1935754 Title: [HP EliteBook 850 G6] laptop brightness hotkey after latest update Status in linux package in Ubuntu: Confirmed Bug description: Hello! After recent update I have a problem brightness laptop button are turning my mic off instead of reduce or high it Could you fix it please? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu4.2 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jul 10 21:32:04 2021 InstallationDate: Installed on 2020-04-08 (458 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP HP EliteBook 850 G6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=78466619-ba7c-4459-92c2-58fc31c658f2 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-15 (86 days ago) dmi.bios.date: 09/12/2019 dmi.bios.release: 3.0 dmi.bios.vendor: HP dmi.bios.version: R70 Ver. 01.03.00 dmi.board.name: 8549 dmi.board.vendor: HP dmi.board.version: KBC Version 52.52.00 dmi.chassis.asset.tag: 5CG9450KGR dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 82.82 dmi.modalias: dmi:bvnHP:bvrR70Ver.01.03.00:bd09/12/2019:br3.0:efr82.82:svnHP:pnHPEliteBook850G6:pvr:rvnHP:rn8549:rvrKBCVersion52.52.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G6 dmi.product.sku: 7KP17EA#ACB dmi.sys.vendor: HP hciconfig: hci0:Type: Primary Bus: USB BD Address: 94:E6:F7:2D:22:F5 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:21793 acl:0 sco:0 events:3343 errors:0 TX bytes:796729 acl:0 sco:0 commands:3321 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935754/+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 1914949] Re: Resume from suspend not working with i915 driver and PulseAudio (linux 5.4 and 5.8)
** Changed in: linux (Ubuntu) Status: Confirmed => 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/1914949 Title: Resume from suspend not working with i915 driver and PulseAudio (linux 5.4 and 5.8) Status in linux package in Ubuntu: Fix Released Bug description: Using kernel 5.4.0-65, the system does not wake up anymore from suspend to ram (S3). The screen stays black, only the backlight comes on. Following the instructions in "wiki.ubuntu.com/DebuggingKernelSuspend", it shows that this PCI device is the problem: 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 18) This is a 1st gen Intel HD graphics (Ironlake) Testing various versions of kernels 5.4.0.x , I found that the problem seems to be introduced with 5.4.0-59 Versions after -59 don't wake up, and versions until 5.4.0-58 work fine. Testing 5.8.0-41, it doesn't wake up. Testing mainline 5.11.0-051100rc6-generic, it works fine. More testing showed that it is also related to PulseAudio: I have removed this line from /etc/pulse/default.pa: load-module module-suspend-on-idle If I add it again, the system wakes up normally. I don't know what this means -- was the pm_trace wrong about the VGA controller? Is the kernel not suspending the sound device properly before going to sleep? All the kernels before 5.4.0-59 did not have a problem with this PulseAudio configuration. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20 HibernationDevice: RESUME=UUID=31673f7c-6b7f-4407-bc0b-e8f0652008be InstallationDate: Installed on 2018-09-11 (879 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=6de19ac7-7f66-4b39-a81f-3c955a60ae7a ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.187.9 Tags: ulyana Uname: Linux 5.4.0-65-generic x86_64 UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht installiert ist. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 05/25/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.30 dmi.board.name: HM55-HT dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd05/25/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM55-HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914949/+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 1969666] Re: Impish update: upstream stable patchset 2022-04-20
** Changed in: linux (Ubuntu Impish) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1969666 Title: Impish update: upstream stable patchset 2022-04-20 Status in linux package in Ubuntu: Invalid Status in linux source package in Impish: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2022-04-20 Ported from the following upstream stable releases: v5.10.104, v5.15.27 from git://git.kernel.org/ mac80211_hwsim: report NOACK frames in tx_status mac80211_hwsim: initialize ieee80211_tx_info at hw_scan_work i2c: bcm2835: Avoid clock stretching timeouts ASoC: rt5668: do not block workqueue if card is unbound ASoC: rt5682: do not block workqueue if card is unbound regulator: core: fix false positive in regulator_late_cleanup() KVM: arm64: vgic: Read HW interrupt pending state from the HW tipc: fix a bit overflow in tipc_crypto_key_rcv() cifs: fix double free race when mount fails in cifs_get_root() selftests/seccomp: Fix seccomp failure by adding missing headers i2c: cadence: allow COMPILE_TEST i2c: qup: allow COMPILE_TEST net: usb: cdc_mbim: avoid altsetting toggling for Telit FN990 usb: gadget: don't release an existing dev->buf usb: gadget: clear related members when goto fail exfat: reuse exfat_inode_info variable instead of calling EXFAT_I() exfat: fix i_blocks for files truncated over 4 GiB tracing: Add test for user space strings when filtering on string pointers serial: stm32: prevent TDR register overwrite when sending x_char ata: pata_hpt37x: fix PCI clock detection drm/amdgpu: check vm ready by amdgpu_vm->evicting flag tracing: Add ustring operation to filtering string pointers ALSA: intel_hdmi: Fix reference to PCM buffer address riscv/efi_stub: Fix get_boot_hartid_from_fdt() return value riscv: Fix config KASAN && SPARSEMEM && !SPARSE_VMEMMAP riscv: Fix config KASAN && DEBUG_VIRTUAL ASoC: ops: Shift tested values in snd_soc_put_volsw() by +min iommu/amd: Recover from event log overflow drm/i915: s/JSP2/ICP2/ PCH xen/netfront: destroy queues before real_num_tx_queues is zeroed thermal: core: Fix TZ_GET_TRIP NULL pointer dereference ntb: intel: fix port config status offset for SPR mm: Consider __GFP_NOWARN flag for oversized kvmalloc() calls xfrm: fix MTU regression netfilter: fix use-after-free in __nf_register_net_hook() bpf, sockmap: Do not ignore orig_len parameter xfrm: enforce validity of offload input flags e1000e: Correct NVM checksum verification flow net: fix up skbs delta_truesize in UDP GRO frag_list netfilter: nf_queue: don't assume sk is full socket netfilter: nf_queue: fix possible use-after-free netfilter: nf_queue: handle socket prefetch batman-adv: Request iflink once in batadv-on-batadv check batman-adv: Request iflink once in batadv_get_real_netdevice batman-adv: Don't expect inter-netns unique iflink indices net: ipv6: ensure we call ipv6_mc_down() at most once net: dcb: flush lingering app table entries for unregistered devices net/smc: fix connection leak net/smc: fix unexpected SMC_CLC_DECL_ERR_REGRMB error generated by client net/smc: fix unexpected SMC_CLC_DECL_ERR_REGRMB error cause by server mac80211: fix forwarded mesh frames AC & queue selection net: stmmac: fix return value of __setup handler mac80211: treat some SAE auth steps as final iavf: Fix missing check for running netdev net: sxgbe: fix return value of __setup handler ibmvnic: register netdev after init of adapter net: arcnet: com20020: Fix null-ptr-deref in com20020pci_probe() ixgbe: xsk: change !netif_carrier_ok() handling in ixgbe_xmit_zc() efivars: Respect "block" flag in efivar_entry_set_safe() firmware: arm_scmi: Remove space in MODULE_ALIAS name ASoC: cs4265: Fix the duplicated control name can: gs_usb: change active_channels's type from atomic_t to u8 arm64: dts: rockchip: Switch RK3399-Gru DP to SPDIF output igc: igc_read_phy_reg_gpy: drop premature return ARM: Fix kgdb breakpoint for Thumb2 ARM: 9182/1: mmu: fix returns from early_param() and __setup() functions selftests: mlxsw: tc_police_scale: Make test more robust pinctrl: sunxi: Use unique lockdep classes for IRQs igc: igc_write_phy_reg_gpy: drop premature return ibmvnic: free reset-work-item when flushing memfd: fix
[Kernel-packages] [Bug 1969689] Re: USB devices not detected on CM4
** Also affects: linux-raspi (Ubuntu Kinetic) Importance: Undecided Status: Confirmed ** Also affects: linux-raspi (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1969689 Title: USB devices not detected on CM4 Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi source package in Jammy: New Status in linux-raspi source package in Kinetic: Confirmed Bug description: USB devices are not working on the CM4. When running `lsusb` the hub is detected, but devices are not. ``` ubuntu@ubuntu:~$ sudo dmesg | egrep -i "dwc2|usb" [0.151915] usbcore: registered new interface driver usbfs [0.151976] usbcore: registered new interface driver hub [0.152047] usbcore: registered new device driver usb [1.125855] usbcore: registered new interface driver lan78xx [1.125926] usbcore: registered new interface driver smsc95xx [1.125965] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [1.126070] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [1.126318] uhci_hcd: USB Universal Host Controller Interface driver [1.765785] usb_phy_generic phy: supply vcc not found, using dummy regulator [1.864470] dwc2 fe98.usb: supply vusb_d not found, using dummy regulator [1.864674] dwc2 fe98.usb: supply vusb_a not found, using dummy regulator [1.916752] dwc2 fe98.usb: DWC OTG Controller [1.916788] dwc2 fe98.usb: new USB bus registered, assigned bus number 1 [1.916822] dwc2 fe98.usb: irq 36, io mem 0xfe98 [1.917028] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15 [1.917040] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [1.917048] usb usb1: Product: DWC OTG Controller [1.917055] usb usb1: Manufacturer: Linux 5.15.0-1005-raspi dwc2_hsotg [1.917062] usb usb1: SerialNumber: fe98.usb [1.917627] hub 1-0:1.0: USB hub found [7.831293] usbcore: registered new interface driver brcmfmac ``` @waveform was able to confirm the issue. The line `dtoverlay=dwc2,dr_mode=host` is present in config.txt. We suspect this to be a dtb/kernel issue. This is happening on both armhf and arm64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1969689/+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 1971149] Re: Wayland session: Internal display is black after sleep
Thank you Daniel, I just did (bug #1971674) -- 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/1971149 Title: Wayland session: Internal display is black after sleep Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: I have a laptop with Intel 630 and NVIDIA 1050 Ti, I have connected an external display via HDMI. I have set this external display as primary. I also chose a Wayland session. My Ubuntu 22.04 has all the latest updates as of today. When my laptop sleeps after I re-login the internal display (connected to Intel 630 AFAIK) is black. It appears enabled in the settings and if I change it to be the primary it lights up. I don't remember seeing this in an X.org session. 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 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 2 15:29:43 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:0798] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0798] InstallationDate: Installed on 2022-05-01 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=19e3ad11-d1ce-49ce-8809-80fc68612eb3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 065C71 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrX02:cvnDellInc.:ct10:cvr:sku0798: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.product.sku: 0798 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.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/ubuntu/+source/linux/+bug/1971149/+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 1966841] Re: alsa/sdw: Fix the audio issue on a Dell machine without internal mic
This bug was fixed in the package firmware-sof - 2.0-1ubuntu3 --- firmware-sof (2.0-1ubuntu3) jammy; urgency=low * Add a new tplg file to v2.0.x - Intel released a new tplg file in the sof-bin-v1.9.3-tplg2 for a Dell machine which has no internal mic. Now picking that file and put it as v2.0.x/sof-tplg-v2.0/sof-adl-rt711-l2-rt1316-l01.tplg. (LP: #1966841) -- Hui Wang Wed, 13 Apr 2022 11:30:46 +0800 ** Changed in: firmware-sof (Ubuntu Jammy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1966841 Title: alsa/sdw: Fix the audio issue on a Dell machine without internal mic Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Fix Committed Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in firmware-sof source package in Jammy: Fix Released Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: SRU template for linux-firmware [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current asoc driver can't work on this machine, the speaker and headset couldn't work. [Fix] Backport a tplg file which is specific to this mahcine [Test] Install the patched linux-firmware and boot the latest oem-5.14 kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] This SRU is adding a new tplg file, it has no chance to introduce a regression. SRU template for linux [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current soc driver can't work on this machine, it will load a wrong tplg without this patch, and the speaker and headset couldn't work. [Fix] Backport one patch from upstream. [Test] Boot the patched kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] If it could introduce regression, it will be on the sdw codec matching for adl machines, then it will make the driver load wrong tplg and make output device and input device not work anymore. But this possibility is very low, we already tested the patch on some dell adl machines, no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966841/+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 1970798] Re: 32 GT/s PCI link speeds reporting "Unknown speed" in sysfs
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1970798 Title: 32 GT/s PCI link speeds reporting "Unknown speed" in sysfs Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Bug description: SRU Justification [Impact] NVIDIA Collective Communication Library software uses sysfs to report performance statistics. Users have reported entries showing "Unknown speed" when they should be reporting "32 GT/s". Example: "" PCIe 5.0 supports 32 GT/s and is available in the 5.4 kernel, but the patches for properly reporting speeds in sysfs are missing. The following upstream v5.7 patches add the reporting capability. PCI ML submission https://lore.kernel.org/linux-pci/20200229030706.17835-1-helg...@kernel.org/ Upstream Patches https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9cb3985af63555810bb07de50acdf4170771451d https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e56faff57f0b39661093c00e0262d4ab9088830e https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=6348a34dcb98d8e285685a205f2a601817fa2d38 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=757bfaa2c3515803dde9a6728bbf8c8a3c5f098a [Test Plan] Testing these speeds requires special hardware. A Test kernel with these patches applied was provided to the customer and they confirmed the proper numbers are reported. [Where problems could occur] Changes are for reporting info so chance of problems should be low. If a problem did occur it would be with sysfs or pcie driver misreporting speeds. [Other] SF-00333784 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970798/+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 1971149] Re: Wayland session: Internal display is black after sleep
Here you have ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1971149/+attachment/5586890/+files/journal.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/1971149 Title: Wayland session: Internal display is black after sleep Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: I have a laptop with Intel 630 and NVIDIA 1050 Ti, I have connected an external display via HDMI. I have set this external display as primary. I also chose a Wayland session. My Ubuntu 22.04 has all the latest updates as of today. When my laptop sleeps after I re-login the internal display (connected to Intel 630 AFAIK) is black. It appears enabled in the settings and if I change it to be the primary it lights up. I don't remember seeing this in an X.org session. 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 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 2 15:29:43 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:0798] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0798] InstallationDate: Installed on 2022-05-01 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=19e3ad11-d1ce-49ce-8809-80fc68612eb3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 065C71 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrX02:cvnDellInc.:ct10:cvr:sku0798: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.product.sku: 0798 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.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/ubuntu/+source/linux/+bug/1971149/+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 1960213] Re: Kernel Panic on linux-image-5.15.0-18-generic
have the same on 5.15.0-29-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1960213
Title:
Kernel Panic on linux-image-5.15.0-18-generic
Status in linux package in Ubuntu:
Confirmed
Bug description:
Hello. Get a Kernel Panic on linux-image-5.15.0-18-generic
The same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957012
On 5.13.0-29-generic boot successfully.
Laptop: Lenovo
Model: 20RA002SRT
Stack trace in attached images.
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.13.0-29-generic.
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: CX8070 Analog [CX8070 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: grid 2375 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xb131c000 irq 149'
Mixer name : 'Conexant CX8070'
Components : 'HDA:14f11f86,17aa5079,00100100
HDA:8086280b,80860101,0010'
Controls : 55
Simple ctrls : 14
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
DistroRelease: Ubuntu 20.04
MachineType: LENOVO 20RA002SRT
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-29-generic
root=/dev/mapper/vg_core-sys ro ipv6.disable=1 quiet splash iommu=soft
resume=/dev/vg_core/sys resume_offset=34816 crashkernel=512M-:192M vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-29.32~20.04.1-generic 5.13.19
RelatedPackageVersions:
linux-restricted-modules-5.13.0-29-generic N/A
linux-backports-modules-5.13.0-29-generic N/A
linux-firmware 1.187.26
Tags: focal
Uname: Linux 5.13.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: dialout docker plugdev tty uucp vboxusers wireshark
WifiSyslog:
_MarkForUpload: True
dmi.bios.date: 09/15/2021
dmi.bios.release: 1.19
dmi.bios.vendor: LENOVO
dmi.bios.version: R16ET33W (1.19 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20RA002SRT
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.13
dmi.modalias:
dmi:bvnLENOVO:bvrR16ET33W(1.19):bd09/15/2021:br1.19:efr1.13:svnLENOVO:pn20RA002SRT:pvrThinkPadE14:rvnLENOVO:rn20RA002SRT:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20RA_BU_SMB_FM_ThinkPadE14:
dmi.product.family: ThinkPad E14
dmi.product.name: 20RA002SRT
dmi.product.sku: LENOVO_MT_20RA_BU_SMB_FM_ThinkPad E14
dmi.product.version: ThinkPad E14
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960213/+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 1971480] Re: issuing invalid ioctl to /dev/vsock may spam dmesg
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1971480
Title:
issuing invalid ioctl to /dev/vsock may spam dmesg
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Focal:
Fix Committed
Bug description:
[Impact]
Any user may spam dmesg may issuing an invalid ioctl to /dev/vsock.
[Fix]
Do not print anything to dmesg when an invalid ioctl is issued to /dev/vsock.
[Test case]
ioctl(open("/dev/vsock", O_RDONLY), garbage, 0);
[Potential regression]
vsock users may regress.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971480/+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 1956086] Re: config CONFIG_HISI_PMU for kunpeng920
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956086 Title: config CONFIG_HISI_PMU for kunpeng920 Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 ubuntu-20.04-hwe series: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: [Impact] We have Hisilicon PMU modules built-in and they can not be unloaded. There is no way to replace with a updated module unless we build it as module. [Test Plan] `lsmod | grep hisi_uncore` shall see 4 modules loaded and they can be unloaded. [Regression Risk] CONFIG_HISI_PMU shall be only affected Hisilicon platforms that HISI0213 is found in ACPI tables. We shall have perf test run on these platforms and others have lowest risk. = [Bug Description] hisi pmu support x.ko module to use it for kunpeng920 [Steps to Reproduce] 1) cd /lib/modules/$(uname -r)/kernel/drivers/perf/hisilicon 2) check *.ko 3) [Actual Results] @ubuntu:~$ cat /boot/config-4.15.0-140-generic | grep -i CONFIG_HISI_PMU CONFIG_HISI_PMU=y [Expected Results] @ubuntu:~$ cat /boot/config-4.15.0-140-generic | grep -i CONFIG_HISI_PMU CONFIG_HISI_PMU=m [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] drivers/perf: hisi: Permit modular builds of HiSilicon uncore drivers To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1956086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971417] Re: Fix REG_WAIT timeout for Yellow Carp
** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Kinetic) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1971417 Title: Fix REG_WAIT timeout for Yellow Carp Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Kinetic: Invalid Bug description: [Impact] During hotplug built-in hdmi, the error message show up. #REG_WAIT timeout for yellow Carp [Fix] This tends to take miliseconds in certain scenarios and we'd rather not wait that long. Due to how this interacts with det size update and locking waiting should not be necessary as compbuf updates before unlock. Add a watch for config error instead as that is something we actually do care about. [Test Case] 1. Plug and unplug hdmi 2. cant get the error message in dmesg. [Where problems could occur] Low To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1971417/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956086] Re: config CONFIG_HISI_PMU for kunpeng920
** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium -- 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/1956086 Title: config CONFIG_HISI_PMU for kunpeng920 Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 ubuntu-20.04-hwe series: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Impish: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: [Impact] We have Hisilicon PMU modules built-in and they can not be unloaded. There is no way to replace with a updated module unless we build it as module. [Test Plan] `lsmod | grep hisi_uncore` shall see 4 modules loaded and they can be unloaded. [Regression Risk] CONFIG_HISI_PMU shall be only affected Hisilicon platforms that HISI0213 is found in ACPI tables. We shall have perf test run on these platforms and others have lowest risk. = [Bug Description] hisi pmu support x.ko module to use it for kunpeng920 [Steps to Reproduce] 1) cd /lib/modules/$(uname -r)/kernel/drivers/perf/hisilicon 2) check *.ko 3) [Actual Results] @ubuntu:~$ cat /boot/config-4.15.0-140-generic | grep -i CONFIG_HISI_PMU CONFIG_HISI_PMU=y [Expected Results] @ubuntu:~$ cat /boot/config-4.15.0-140-generic | grep -i CONFIG_HISI_PMU CONFIG_HISI_PMU=m [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] drivers/perf: hisi: Permit modular builds of HiSilicon uncore drivers To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1956086/+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 1970426] Re: [i915] screen is flickering in Ubuntu 22.04
Well I can say only about 20.04.04 there was 5.13 hwe kernel without that flickering. After I upgraded to 22.04 with 5.15, problem starts. -- 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/1970426 Title: [i915] screen is flickering in Ubuntu 22.04 Status in linux package in Ubuntu: Confirmed Bug description: After I updated to 22.04 sometimes (about 3 ~ 4 times a day) the screen starts glitching and flickering like in the attached video and it doesn't stop until I move the cursor. Description: Ubuntu 22.04 LTS Release: 22.04 wayland processor: Intel® Core™ i5-8265U CPU @ 1.60GHz × 8 graphics: Mesa Intel® UHD Graphics 620 (WHL GT2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970426/+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 1971612] Re: [UBUNTU 22.04] GLIBC: Adding new s390 platform IBM z16
** Package changed: linux (Ubuntu) => glibc (Ubuntu) ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: glibc (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Foundations Team (canonical-foundations) ** Changed in: ubuntu-z-systems Importance: Undecided => Medium ** Changed in: ubuntu-z-systems Importance: Medium => High -- 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/1971612 Title: [UBUNTU 22.04] GLIBC: Adding new s390 platform IBM z16 Status in Ubuntu on IBM z Systems: New Status in glibc package in Ubuntu: New Bug description: After IBM z16 has been announced, we need to add the new s390 platform in glibc. S390: Add new s390 platform z16. https://sourceware.org/git/?p=glibc.git;a=commit;h=2376944b9e5c0364b9fb473e4d8dabca31b57167 Backport to glibc 2.35 release branch: https://sourceware.org/git/?p=glibc.git;a=commit;h=6583d534458e7f8beec8d0766b6db0bdaae6749c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1971612/+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 1971656] Re: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04
Could you try upstream kernel? 5.18-rc kernel got a lot of patches for rtw89. upstream bug: https://github.com/lwfinger/rtw89/issues/144 ** Bug watch added: github.com/lwfinger/rtw89/issues #144 https://github.com/lwfinger/rtw89/issues/144 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1971656 Title: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04 Status in linux-firmware package in Ubuntu: New Bug description: On a Lenovo P14s (RTL8111/8168/8411), the WiFi connection gets stuck at times. When this happens, there is no way to use `sudo`, the WiFi GNOME UI says NetworkManager is not running (which it is), and `dmesg -w` continuously outputs: ``` [90296.470925] rtw89_pci :03:00.0: failed to get available addr cam [90296.470935] rtw89_pci :03:00.0: failed to init addr cam [90296.586817] rtw89_pci :03:00.0: failed to get available addr cam [90296.586828] rtw89_pci :03:00.0: failed to init addr cam [90296.698790] rtw89_pci :03:00.0: failed to get available addr cam [90296.698797] rtw89_pci :03:00.0: failed to init addr cam [90296.810783] rtw89_pci :03:00.0: failed to get available addr cam [90296.810790] rtw89_pci :03:00.0: failed to init addr cam ``` The only solution I've found is to reboot the machine. However, turning off needs to be forced (magic keys still work for rebooting). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 5 07:49:18 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu2 InstallationDate: Installed on 2022-02-25 (68 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 21A3MZ PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) dmi.bios.date: 11/05/2021 dmi.bios.release: 1.13 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET43W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A3MZ dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrR1MET43W(1.13):bd11/05/2021:br1.13:efr1.13:svnLENOVO:pn21A3MZ:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A3MZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A3MZ dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971656/+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 1967842] Re: Ubuntu 22.04 Beta: linux-firmware iwlwifi-9260-th-b0-jf-b0-46.ucode - Wireless-AC 9260 not working
I had the same issue today (May 5th 2022), and the workaround proposed by Giacomo Tazzari worked just fine. Strangely, the adapter was working just fine after the Ubuntu 22.04 installation (earlier this week). So maybe some recent update caused the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1967842 Title: Ubuntu 22.04 Beta: linux-firmware iwlwifi-9260-th-b0-jf-b0-46.ucode - Wireless-AC 9260 not working Status in linux-firmware package in Ubuntu: Confirmed Bug description: Hi with the current Ubuntu 22.04 beta my WIFI device Intel Corporation Wireless-AC 9260 is not shown/working. If I copy/use the firmware from an current Ubuntu 20.04 system it is working again. Md5sum working from Ubuntu 20.04 linux-firmware: 0668e93b8766bf95d6adffdb33ec7bdb /lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode Md5sum not working from Ubuntu 22.04 linux-firmware: dcf642fd7412614e19d1d54f57147539 /lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode Outputs from the Ubuntu 22.04 system: Device Dell 7530: # lspci -Q -v -s 6e:00.0 6e:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29) Subsystem: Intel Corporation Device 4010 Flags: bus master, fast devsel, latency 0, IRQ 18, IOMMU group 16 Memory at a000 (64-bit, non-prefetchable) [size=16K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [80] MSI-X: Enable+ Count=16 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [14c] Latency Tolerance Reporting Capabilities: [154] L1 PM Substates Kernel driver in use: iwlwifi Kernel modules: iwlwifi # dpkg -l | grep linux-firmware ii linux-firmware 20220329.git681281e4-0ubuntu1 # uname -a Linux hostname 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux # dmesg with broken firmware: [ 13.690647] kernel: iwlwifi :6e:00.0: enabling device ( -> 0002) [ 13.707780] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 0 [ 13.707784] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 1 [ 13.707786] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 2 [ 13.707787] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 3 [ 13.707788] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 4 [ 13.707790] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 6 [ 13.707791] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 8 [ 13.707792] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 9 [ 13.707793] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 10 [ 13.707795] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 11 [ 13.707796] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 15 [ 13.707797] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 16 [ 13.707798] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 18 [ 13.707800] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 19 [ 13.707801] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 20 [ 13.707802] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 21 [ 13.707804] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 28 [ 13.708080] kernel: iwlwifi :6e:00.0: loaded firmware version 46.fae53a8b.0 9260-th-b0-jf-b0-46.ucode op_mode iwlmvm [ 13.954798] kernel: iwlwifi :6e:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324 [ 14.779900] kernel: iwlwifi :6e:00.0: RF_KILL bit toggled to disable radio. [ 14.779904] kernel: iwlwifi :6e:00.0: reporting RF_KILL (radio disabled) [ 15.045652] kernel: iwlwifi :6e:00.0: SecBoot CPU1 Status: 0xa5a5a5a2, CPU2 Status: 0xa5a5a5a2 [ 15.045657] kernel: iwlwifi :6e:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [ 15.293971] kernel: iwlwifi :6e:00.0: Not valid error log pointer 0x for Init uCode [ 15.294270] kernel: iwlwifi :6e:00.0: Hardware error detected. Restarting. [ 15.294271] kernel: iwlwifi :6e:00.0: IML/ROM dump: [ 15.294272] kernel: iwlwifi :6e:00.0: 0xA5A5 | IML/ROM SYSASSERT [ 15.294273] kernel: iwlwifi :6e:00.0: 0xA5A5A5A2 | IML/ROM error/state [ 15.294420] kernel: iwlwifi :6e:00.0: 0xA5A5A5A2 | IML/ROM data1 [ 15.294429] kernel: iwlwifi :6e:00.0: Fseq Registers: [ 15.294563] kernel: iwlwifi :6e:00.0: 0xA5A5A5A2 | FSEQ_ERROR_CODE [ 15.294697] kernel: iwlwifi :6e:00.0: 0xA5A5A5A2 | FSEQ_TOP_INIT_VERSION [ 15.294831] kernel: iwlwifi :6e:00.0: 0xA5A5A5A2 | FSEQ_CNVIO_INIT_VERSION [ 15.294965] kernel: iwlwifi :6e:00.0: 0xA5A5A5A2 | FSEQ_OTP_VERSION [ 15.295100] kernel: iwlwifi :6e:00.0:
[Kernel-packages] [Bug 1952581] Re: ACPI Error: No handler for Region [VRTC]
I am being affected by this issue as well. My machine fails to boot at all, providing the following error after GRUB [0.39] ACPI Error: No handler for Region [VRTC] (b44dee92) [SystemCMOS] (20210730/euregion-130) [0.394449] ACPI Error: Region SystemCMOS (ID=5) has no handler (20210730/exfldio-261) [0.394457] ACPI Error: Aborting method N_SB.PCOO.LPCB.ECO.RTEC due to previous error (AE_HOT_EXIST) (20210730/psparse-529) [0.394460] ACPI Error: Aborting method N_SII.PCOO.LPCB.ECO._REG due to previous error (AE_MOT_EXIST) (20210730/psparse-529) [0.994991] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [0.995017] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.15.0-25-generic #25-Ubuntu [0.995039] Hardware name: Razer Blade 17 (2022) - RZ09-0423/DI780, BIOS 1.06 01/27/2022 [0.995060] Call Trace: [0.995071] [0.995084] show_stack.0x52/0x58 [0.995105] dump_stack_lu1.0x4a/Ox5f [0.995126] dump_stack.0x10/0x12 [0.995143] panic.0x149/0x321 [0.995160] mount_block_root.0x144/0x1d9 [0.995182] mount_root.0x10c/Ox118 [0.995200] prepare_namespace.0x13f/Ox18d [0.995220] kernel_init_freeable.0x18c/Ox1b1 [0.995243] ? rest_init.0x100/0x100 [0.995264] kernel_init.0x1b/0x150 [0.995283] ? rest init.0x100/0x100 [0.995302] ret_from_fork.0x1f/0x30 [0.995324] [0.995471] Kernel Offset: 0x180 from Ox8100 (relocation range: Ox8000-Oxbfff) [0.995524] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0) ]--- -- 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/1952581 Title: ACPI Error: No handler for Region [VRTC] Status in linux package in Ubuntu: Confirmed Bug description: From sniffing around seems to be something Kernal related specific to the recent Razor Blade laptops with GPUs. https://bugzilla.kernel.org/show_bug.cgi?id=205665 I don't think its Xorg but its graphic related? Fully documented here with screen shot https://askubuntu.com/questions/1376401/acpi-error-causing-suspend-loop-bug-in-21-10 Tried to register on bugzilla.kernal.org but since i'm not compiling my own Kernal they say its Ubuntu problem? ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 Uname: Linux 5.13.19-051319-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 470.82.00 Thu Oct 14 10:24:40 UTC 2021 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 29 20:12:32 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: nvidia, 470.82.00, 5.13.0-20-generic, x86_64: installed nvidia, 470.82.00, 5.13.0-21-generic, x86_64: installed nvidia, 470.82.00, 5.13.19-051319-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. CometLake-H GT2 [UHD Graphics] [1a58:200f] NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [10de:249c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [1a58:200f] InstallationDate: Installed on 2021-10-24 (36 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Razer Blade 15 Advanced Model (Early 2021) - RZ09-036 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.19-051319-generic root=UUID=006b8912-4943-4915-bf29-0927fd50045f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2021 dmi.bios.release: 1.1 dmi.bios.vendor: Razer dmi.bios.version: 1.01 dmi.board.name: CH560 dmi.board.vendor: Razer dmi.board.version: 4 dmi.chassis.type: 10 dmi.chassis.vendor: Razer dmi.ec.firmware.release: 1.0 dmi.modalias: dmi:bvnRazer:bvr1.01:bd02/02/2021:br1.1:efr1.0:svnRazer:pnBlade15AdvancedModel(Early2021)-RZ09-036:pvr6.04:rvnRazer:rnCH560:rvr4:cvnRazer:ct10:cvr:skuRZ09-0367CE53: dmi.product.family: 1A58200F Razer Blade dmi.product.name: Blade 15 Advanced Model (Early 2021) - RZ09-036
