[Kernel-packages] [Bug 1878321] Re: TP-Link UE300 [2357:0601]: Kernel workqueue rtl_work_func_t [r8152] gets stuck, preventing network connectivity: Bad RIP value
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878321 Title: TP-Link UE300 [2357:0601]: Kernel workqueue rtl_work_func_t [r8152] gets stuck, preventing network connectivity: Bad RIP value Status in linux package in Ubuntu: Expired Bug description: $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 Package: linux-image-5.3.0-51-generic What happened: After plugging my TP-Link (Realtek 8152 based) USB GbE ethernet device into my laptop and using it, network connectivity loss occurs several minutes later. Once this has occurred, various processes on the system hang when I run them (eg "ip a"; "sudo"). It appears that the rtnetlink lock is held and is never released. The device disappears from the list of available devices. What I expected: I can plug the ethernet device in and use it to successfully observe cats on the internet for hours at a time. Kernel logs: May 11 22:15:58 allosaurus kernel: usb 2-2: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd May 11 22:15:58 allosaurus kernel: usb 2-2: New USB device found, idVendor=2357, idProduct=0601, bcdDevice=30.00 May 11 22:15:58 allosaurus kernel: usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=6 May 11 22:15:58 allosaurus kernel: usb 2-2: Product: USB 10/100/1000 LAN May 11 22:15:58 allosaurus kernel: usb 2-2: Manufacturer: TP-LINK May 11 22:15:58 allosaurus kernel: usb 2-2: SerialNumber: 0100 May 11 22:15:59 allosaurus kernel: usbcore: registered new interface driver r8152 May 11 22:15:59 allosaurus kernel: usbcore: registered new interface driver cdc_ether May 11 22:15:59 allosaurus kernel: usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd May 11 22:15:59 allosaurus kernel: r8152 2-2:1.0 eth0: v1.09.11 May 11 22:15:59 allosaurus kernel: r8152 2-2:1.0 enxd03745081b4b: renamed from eth0 May 11 22:16:02 allosaurus kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enxd03745081b4b: link becomes ready May 11 22:16:02 allosaurus kernel: r8152 2-2:1.0 enxd03745081b4b: carrier on May 11 22:16:02 allosaurus kernel: r8152 2-2:1.0 enxd03745081b4b: carrier off May 11 22:16:05 allosaurus kernel: r8152 2-2:1.0 enxd03745081b4b: carrier on May 11 22:20:17 allosaurus kernel: NOHZ: local_softirq_pending 08 May 11 22:24:33 allosaurus kernel: NOHZ: local_softirq_pending 08 May 11 22:24:39 allosaurus kernel: NOHZ: local_softirq_pending 08 May 11 22:25:14 allosaurus kernel: NOHZ: local_softirq_pending 08 May 11 22:30:31 allosaurus kernel: INFO: task kworker/1:2:10776 blocked for more than 120 seconds. May 11 22:30:31 allosaurus kernel: Tainted: P OE 5.3.0-51-generic #44-Ubuntu May 11 22:30:31 allosaurus kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. May 11 22:30:31 allosaurus kernel: kworker/1:2 D0 10776 2 0x80004000 May 11 22:30:31 allosaurus kernel: Workqueue: events rtl_work_func_t [r8152] May 11 22:30:31 allosaurus kernel: Call Trace: May 11 22:30:31 allosaurus kernel: __schedule+0x2b9/0x6c0 May 11 22:30:31 allosaurus kernel: schedule+0x42/0xb0 May 11 22:30:31 allosaurus kernel: rpm_resume+0x174/0x780 May 11 22:30:31 allosaurus kernel: ? wait_woken+0x80/0x80 May 11 22:30:31 allosaurus kernel: rpm_resume+0x31d/0x780 May 11 22:30:31 allosaurus kernel: ? __switch_to_asm+0x34/0x70 May 11 22:30:31 allosaurus kernel: ? __switch_to_xtra+0x1c5/0x5c0 May 11 22:30:31 allosaurus kernel: ? __switch_to_asm+0x34/0x70 May 11 22:30:31 allosaurus kernel: ? __switch_to_asm+0x40/0x70 May 11 22:30:31 allosaurus kernel: ? __switch_to_asm+0x34/0x70 May 11 22:30:31 allosaurus kernel: __pm_runtime_resume+0x52/0x80 May 11 22:30:31 allosaurus kernel: usb_autopm_get_interface+0x1d/0x50 May 11 22:30:31 allosaurus kernel: rtl_work_func_t+0x70/0x285 [r8152] May 11 22:30:31 allosaurus kernel: ? __schedule+0x2c1/0x6c0 May 11 22:30:31 allosaurus kernel: process_one_work+0x1db/0x380 May 11 22:30:31 allosaurus kernel: worker_thread+0x4d/0x400 May 11 22:30:31 allosaurus kernel: kthread+0x104/0x140 May 11 22:30:31 allosaurus kernel: ? process_one_work+0x380/0x380 May 11 22:30:31 allosaurus kernel: ? kthread_park+0x80/0x80 May 11 22:30:31 allosaurus kernel: ret_from_fork+0x35/0x40 May 11 22:31:34 allosaurus kernel: usb 2-2: USB disconnect, device number 2 May 11 22:32:32 allosaurus kernel: INFO: task NetworkManager:1470 blocked for more than 120 seconds. May 11 22:32:32 allosaurus kernel: Tainted: P OE 5.3.0-51-generic #44-Ubuntu May 11 22:32:32 allosaurus kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. May 11
[Kernel-packages] [Bug 1926517] Re: [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES
5.8 test kernel https://people.canonical.com/~mreed/lp_1926517_mpt3sas_groovy/ 5.11 test kernel https://people.canonical.com/~mreed/lp_1926517_mpt3sas_hirsute/ The focal 5.4 kernel is liked in comment #2 -- 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/1926517 Title: [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: New Status in linux source package in Groovy: New Status in linux source package in Hirsute: New Bug description: [Impact] Whenever the driver is adding a vSES to virtual-phys list it is reinitializing the list head. Hence those vSES devices which were added previously are lost. [FIXES] Stop reinitializing the list every time a new vSES device is added. https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?id=4c51f9569651 CommitID: 4c51f956965120b3441cdd39c358b87daba13e19 [TESTING] [REGRESSION RISK] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922336] Re: ACPI errors and USB reset loop when hot-plugging a Titan Ridge laptop into a dock (9500, TB16)
@Georgi, would you please dump #boltctl #fwupdmgr get-device -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1922336 Title: ACPI errors and USB reset loop when hot-plugging a Titan Ridge laptop into a dock (9500, TB16) Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-oem-5.6 package in Ubuntu: New Bug description: I've recently upgraded my workhorse from XPS 9560 (2016) to a newer generation XPS 9500 (2020) and ran into several things that feel like regressions, but are probably related to hardware changes. This is one of them. tl;dr: When using XPS 9500 with a TB16 dock, hot-plugging the dock causes ACPI errors in dmesg and some kind of reset loop with USB peripherals connected via the dock. details: USB peripherals keep reconnecting according to dmesg, but in practice they barely ever finish registering with the system before disappearing again. Maybe 1 out of 40 USB keyboard presses registers while this is happening. At this point my choices are to either reboot with the dock connected or work without the dock and consequently without any peripherals on my desk. Booting with an open lid and the dock connected works fine until I re-plug the dock. Notably, it hot-plugs fine every time when using XPS 9560 or Precision 5520 in the same setup which I have been using for ages and which had similar problems until around kernel 4.13. Since it was fine with 9560, 5520 and a friend with a 9570 has no issues either, my gut feeling is that this is due to the upgrade from Alpine Ridge to a Titan Ridge Thunderbolt controller that happened in this generation - something wrong with the driver, or the firmware may have missed some of the "lessons learned" in Alpine Ridge and caused this regression. That would also make it applicable to 9300, which has a "developer edition" option under Project Sputnik. I have attempted 5.8 Ubuntu generic, 5.6 OEM (-20.04) and 5.10 OEM (-20.04b and -20.04-edge) kernels on the 9500 with same results. I have attempted rebinding the XHCI controller after reconnecting the dock. I have attempted disabling USB autosuspend and ASPM via a GRUB kernel parameter. I have attempted playing with BIOS settings: wake on dell usb-c docks, disable early sign of life for both checkboxes, disabling SGX and SMM, checking all 3 boxes for Thunderbolt and switching off Thunderbolt security. None of these make a noticeable difference. System config: XPS 9500, i7, 32GB RAM BIOS 1.6.1, TB3 firmware NVM60 Ubuntu 20.04.02 LTS, kernels 5.6-oem, 5.8-generic, 5.10-oem (same behaviour) TB16 dock firmware 1.0.4 (MST 3.12.02) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: gboiko 1990 F pulseaudio /dev/snd/controlC2: gboiko 1990 F pulseaudio /dev/snd/controlC1: gboiko 1990 F pulseaudio /dev/snd/controlC0: gboiko 1990 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-31 (6 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 15 9500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux-meta-oem-5.6 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.6.0-1052-oem root=/dev/mapper/vgubuntu-root ro net.ifnames=0 biosdevname=0 ipv6.disable=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1052.56-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1052-oem N/A linux-backports-modules-5.6.0-1052-oem N/A linux-firmware 1.187.10 Tags: focal Uname: Linux 5.6.0-1052-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.1 dmi.board.name: 0RHXRG dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.1:bd12/24/2020:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn0RHXRG:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1922336/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907262] Re: raid10: discard leads to corrupted file system
** Changed in: linux (Ubuntu Groovy) Assignee: Sinclair Willis (yousure1222) => (unassigned) -- 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/1907262 Title: raid10: discard leads to corrupted file system Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Invalid Status in linux source package in Xenial: Invalid Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Bug description: Seems to be closely related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578 After updating the Ubuntu 18.04 kernel from 4.15.0-124 to 4.15.0-126 the fstrim command triggered by fstrim.timer causes a severe number of mismatches between two RAID10 component devices. This bug affects several machines in our company with different HW configurations (All using ECC RAM). Both, NVMe and SATA SSDs are affected. How to reproduce: - Create a RAID10 LVM and filesystem on two SSDs mdadm -C -v -l10 -n2 -N "lv-raid" -R /dev/md0 /dev/nvme0n1p2 /dev/nvme1n1p2 pvcreate -ff -y /dev/md0 vgcreate -f -y VolGroup /dev/md0 lvcreate -n root-L 100G -ay -y VolGroup mkfs.ext4 /dev/VolGroup/root mount /dev/VolGroup/root /mnt - Write some data, sync and delete it dd if=/dev/zero of=/mnt/data.raw bs=4K count=1M sync rm /mnt/data.raw - Check the RAID device echo check >/sys/block/md0/md/sync_action - After finishing (see /proc/mdstat), check the mismatch_cnt (should be 0): cat /sys/block/md0/md/mismatch_cnt - Trigger the bug fstrim /mnt - Re-Check the RAID device echo check >/sys/block/md0/md/sync_action - After finishing (see /proc/mdstat), check the mismatch_cnt (probably in the range of N*1): cat /sys/block/md0/md/mismatch_cnt After investigating this issue on several machines it *seems* that the first drive does the trim correctly while the second one goes wild. At least the number and severity of errors found by a USB stick live session fsck.ext4 suggests this. To perform the single drive evaluation the RAID10 was started using a single drive at once: mdadm --assemble /dev/md127 /dev/nvme0n1p2 mdadm --run /dev/md127 fsck.ext4 -n -f /dev/VolGroup/root vgchange -a n /dev/VolGroup mdadm --stop /dev/md127 mdadm --assemble /dev/md127 /dev/nvme1n1p2 mdadm --run /dev/md127 fsck.ext4 -n -f /dev/VolGroup/root When starting these fscks without -n, on the first device it seems the directory structure is OK while on the second device there is only the lost+found folder left. Side-note: Another machine using HWE kernel 5.4.0-56 (after using -53 before) seems to have a quite similar issue. Unfortunately the risk/regression assessment in the aforementioned bug is not complete: the workaround only mitigates the issues during FS creation. This bug on the other hand is triggered by a weekly service (fstrim) causing severe file system corruption. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907262/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926081] Re: nr_writeback memory leak in kernel 4.15.0-137+
Patches submitted: https://lists.ubuntu.com/archives/kernel-
team/2021-April/119661.html
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
--
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/1926081
Title:
nr_writeback memory leak in kernel 4.15.0-137+
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
SRU Justification
[Impact]
Ubuntu 18.04.5 4.15.0 LTS kernels at version 4.15.0-137 and above
contain a memory leak due to the inclusion of patch from the upstream
kernel, but not the fix for that patch which was released later.
Bad patch in bionic:linux 2c17fa778db85644458b52a7df8eacc402cbc1ef mm:
memcontrol: fix excessive complexity in memory.stat reporting
This issue manifests itself as an increasing amount of memory used by
the writeback queue, which never returns to zero. This can been seen
either as the value of `nr_writeback` in /proc/vmstat, or the value of
`Writeback` in /proc/meminfo.
Ordinarily these values should be at or around zero, but on our
servers we observe the `nr_writeback` value increasing to over 8
million, (32GB of memory), at which point it isn't long before the
system IO slows to a crawl (tens of Kb/s). Our servers have 256GB of
memory, and are performing many CI related activities - this issue
appears to be related to concurrent writing to disk, and can be
demonstrated with a simple testcase (see later).
On our heavily used systems this memory leak can result in an unstable
server after 2-3 days, requiring a reboot to fix it.
After much investigation the issue appears to be because the patch
"mm: memcontrol: fix excessive complexity in memory.stat reporting"
was brought in to the 4.15.0-137 Ubuntu kernel (see
https://launchpad.net/ubuntu/+source/linux/4.15.0-137.141) as part of
" Bionic update: upstream stable patchset 2021-01-25 (LP: #1913214)",
however in the mainline kernel there was a follow up patch because
this initial patch introduced concurrency issues. The patch "mm:
memcontrol: fix NR_WRITEBACK leak in memcg and system stats" is
required, and should be brought into the Ubuntu packaged kernel to fix
the issues reported.
The required patch is here:
https://github.com/torvalds/linux/commit/c3cc39118c3610eb6ab4711bc624af7fc48a35fe
and was committed a few weeks after the original (broken) patch:
https://github.com/torvalds/linux/commit/a983b5ebee57209c99f68c8327072f25e0e6e3da
I have checked the release notes for Ubuntu versions -137 to -143, and
none include this second patch that should fix the issue. (I checked
https://people.canonical.com/~kernel/info/kernel-version-map.html for
all the kernel versions, and then visited each changelog page in turn,
e.g. https://launchpad.net/ubuntu/+source/linux/4.15.0-143.147 looking
for "mm: memcontrol: fix NR_WRITEBACK leak in memcg and system
stats").
We do not observe this on the 5.4.0 kernel (supported HWE kernel on
18.05.5), which includes this second patch. That kernel may also
include other patches, so we do not know if any other fixes are also
required, but the one we have linked above seems to definitely be
needed, and seems to match our symptoms.
[Test Plan]
Testcase:
The following is enough to permanently increase the value of
`nr_writeback` on our systems (by about 2000 during most executions):
```
date
grep nr_writeback /proc/vmstat
mkdir -p /docker/testfiles/{1..5}
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/1/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/2/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/3/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/4/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/5/file.% bs=4k count=10 status=none' &
wait $(jobs -p)
grep nr_writeback /proc/vmstat
date
```
Subsequent iterations of the test raise it further, and on a system
doing a lot of writing from a lot of different processes, it can rise
quickly.
System details:
lsb_release -rd
Description: Ubuntu 18.04.5 LTS
Release: 18.04
Affected kernel: 4.15.0-137 onwards (current latest version tried was
4.15.0-142)
e.g.
apt-cache policy linux-image-4.15.0-141-generic
linux-image-4.15.0-141-generic:
Installed: 4.15.0-141.145
Candidate: 4.15.0-141.145
Version table:
*** 4.15.0-141.145 500
500 http://mirrors.service.networklayer.com/ubuntu
bionic-updates/main amd64 Packages
500
[Kernel-packages] [Bug 1922955] Re: Screen artifacts on recent amd gpu with kernel > 5.11.0-11
It turned out to be a weird interaction with mesa. Upgrading from mesa 21.0.1 included in the main repo to 21.0.3 resolves the problem. -- 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/1922955 Title: Screen artifacts on recent amd gpu with kernel > 5.11.0-11 Status in linux package in Ubuntu: Confirmed Bug description: This is my first time filing a bug report, so apologies in advance for any mistakes and please feel free to point me in the right direction. I'm posting this for the kernel package because the problem is reliably eliminated by downgrading to 5.11.0-11 and reliably returns by upgrading to any greater version. I've been testing Hirsute as my daily driver for a couple of weeks on my PC with one of the recent AMD GPU's (6700XT). Everything was running flawlessly until the kernel upgrade from 5.11.0-11 to 5.11.0-13. After the upgrade I had a lot of artifacts (flashing squares of either the background or random colors) on the screen. Example picture attached. * I suspect it's only in parts that are being hardware-accelerated. Turning off hardware acceleration in chrome, eliminated them in the content part of the browser, but the windows title bar continues to be affected. * The gnome panels and application menu also have random square artifacts appearing and disappearing. * The issue exists both in X11 and Wayland sessions. * I see nothing out of the ordinary in dmesg or journalctl -r. * Downgrading to kernel 5.11.0-11 eliminates the issue. * I tried installing the latest mainline kernel (5.12-rc6), the issue returned, so I downgraded to 5.11.0-11 again (which fixed it). * To see if other packages I installed may be causing the issue, I did a clean install of the latest daily iso (20210407) and can confirm the issue is also in there. I'm happy to provide more information or testing. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-13-generic 5.11.0-13.14 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rob1654 F pulseaudio /dev/snd/controlC1: rob1654 F pulseaudio /dev/snd/controlC0: rob1654 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Apr 7 20:48:15 2021 InstallationDate: Installed on 2021-04-07 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210407) MachineType: Micro-Star International Co., Ltd. MS-7C84 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=66ca562a-996d-408a-a49b-6225bfb86cb6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-13-generic N/A linux-backports-modules-5.11.0-13-generic N/A linux-firmware 1.196 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/01/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.61 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAG X570 TOMAHAWK WIFI (MS-7C84) 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:bvnAmericanMegatrendsInternational,LLC.:bvr1.61:bd03/01/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C84:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGX570TOMAHAWKWIFI(MS-7C84):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C84 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922955/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926081] Re: nr_writeback memory leak in kernel 4.15.0-137+
Andrew - thanks for the testing and results. I'll get these patches
submitted for review.
--
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/1926081
Title:
nr_writeback memory leak in kernel 4.15.0-137+
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
SRU Justification
[Impact]
Ubuntu 18.04.5 4.15.0 LTS kernels at version 4.15.0-137 and above
contain a memory leak due to the inclusion of patch from the upstream
kernel, but not the fix for that patch which was released later.
Bad patch in bionic:linux 2c17fa778db85644458b52a7df8eacc402cbc1ef mm:
memcontrol: fix excessive complexity in memory.stat reporting
This issue manifests itself as an increasing amount of memory used by
the writeback queue, which never returns to zero. This can been seen
either as the value of `nr_writeback` in /proc/vmstat, or the value of
`Writeback` in /proc/meminfo.
Ordinarily these values should be at or around zero, but on our
servers we observe the `nr_writeback` value increasing to over 8
million, (32GB of memory), at which point it isn't long before the
system IO slows to a crawl (tens of Kb/s). Our servers have 256GB of
memory, and are performing many CI related activities - this issue
appears to be related to concurrent writing to disk, and can be
demonstrated with a simple testcase (see later).
On our heavily used systems this memory leak can result in an unstable
server after 2-3 days, requiring a reboot to fix it.
After much investigation the issue appears to be because the patch
"mm: memcontrol: fix excessive complexity in memory.stat reporting"
was brought in to the 4.15.0-137 Ubuntu kernel (see
https://launchpad.net/ubuntu/+source/linux/4.15.0-137.141) as part of
" Bionic update: upstream stable patchset 2021-01-25 (LP: #1913214)",
however in the mainline kernel there was a follow up patch because
this initial patch introduced concurrency issues. The patch "mm:
memcontrol: fix NR_WRITEBACK leak in memcg and system stats" is
required, and should be brought into the Ubuntu packaged kernel to fix
the issues reported.
The required patch is here:
https://github.com/torvalds/linux/commit/c3cc39118c3610eb6ab4711bc624af7fc48a35fe
and was committed a few weeks after the original (broken) patch:
https://github.com/torvalds/linux/commit/a983b5ebee57209c99f68c8327072f25e0e6e3da
I have checked the release notes for Ubuntu versions -137 to -143, and
none include this second patch that should fix the issue. (I checked
https://people.canonical.com/~kernel/info/kernel-version-map.html for
all the kernel versions, and then visited each changelog page in turn,
e.g. https://launchpad.net/ubuntu/+source/linux/4.15.0-143.147 looking
for "mm: memcontrol: fix NR_WRITEBACK leak in memcg and system
stats").
We do not observe this on the 5.4.0 kernel (supported HWE kernel on
18.05.5), which includes this second patch. That kernel may also
include other patches, so we do not know if any other fixes are also
required, but the one we have linked above seems to definitely be
needed, and seems to match our symptoms.
[Test Plan]
Testcase:
The following is enough to permanently increase the value of
`nr_writeback` on our systems (by about 2000 during most executions):
```
date
grep nr_writeback /proc/vmstat
mkdir -p /docker/testfiles/{1..5}
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/1/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/2/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/3/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/4/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/5/file.% bs=4k count=10 status=none' &
wait $(jobs -p)
grep nr_writeback /proc/vmstat
date
```
Subsequent iterations of the test raise it further, and on a system
doing a lot of writing from a lot of different processes, it can rise
quickly.
System details:
lsb_release -rd
Description: Ubuntu 18.04.5 LTS
Release: 18.04
Affected kernel: 4.15.0-137 onwards (current latest version tried was
4.15.0-142)
e.g.
apt-cache policy linux-image-4.15.0-141-generic
linux-image-4.15.0-141-generic:
Installed: 4.15.0-141.145
Candidate: 4.15.0-141.145
Version table:
*** 4.15.0-141.145 500
500 http://mirrors.service.networklayer.com/ubuntu
bionic-updates/main amd64 Packages
500 http://mirrors.service.networklayer.com/ubuntu
bionic-security/main amd64 Packages
100 /var/lib/dpkg/status
[Kernel-packages] [Bug 1919177] Re: Azure: issues with accelerated networking on Hirsute
** Tags removed: rls-hh-incoming
--
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/1919177
Title:
Azure: issues with accelerated networking on Hirsute
Status in cloud-init:
Incomplete
Status in cloud-init package in Ubuntu:
Incomplete
Status in linux-azure package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Bug description:
[General]
On Azure, when provisioning a Hirsute VM with Accelerated Networking
enabled, sometimes part of the cloud-init configuration is not
applied.
Especially, in those cases, the public SSH key is not setup properly.
[how to reproduce]
Start a VM with AN enabled:
```
az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South"
--image
'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size
Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY"
--accelerated-networking
```
After a moment, try to SSH: if you succeed, delete and recreate a new
VM.
[troubleshooting]
To be able to connect into the VM, run:
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
```
In "/run/cloud-init/instance-data.json", I can see:
```
"publicKeys": [
{
"keyData": "",
"path": "/home/ubuntu/.ssh/authorized_keys"
}
],
```
as expected.
[workaround]
As mentioned, Azure allows the user to run command into the VM without
SSH connection. To do so, one can use the Azure CLI:
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
This example uses "ssh-import-id" but it's also possible to just echo
a given public key into /home/ubuntu/.ssh/authorized_keys
NOTE: this will only solves the SSH issue, I do not know if this bug
affects other things. If so the user would have to apply those things
manually.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1919177/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926608] Re: upgrading does not defer initramfs updates
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/1926608 Title: upgrading does not defer initramfs updates Status in linux-firmware package in Ubuntu: Confirmed Bug description: Upgrading linux-firmware (1.173.20) on Ubuntu (18.04.5) will cause the initramfs files to be updated during the "setting up" phase of linux- firmware's installation. However, if there are other packages that also require initramfs to be updated, they will be updated again later during the "processing triggers" phase. The triggers mechanism of deb-installer is designed to avoid this duplication of effort and speed up the time taken to complete an upgrade. If there is no specific reason for linux-firmware to force the initramfs update during setup, I believe it makes sense to defer that action. In the excerpt below, udev and linux-firmware are both in the list of packages to be upgraded. Udev uses the trigger mechanism and linux- firmware does not. > # apt dist-upgrade > ... > Setting up libglib2.0-data (2.56.4-0ubuntu0.18.04.8) ... > Setting up udev (237-3ubuntu10.46) ... > update-initramfs: deferring update (trigger activated) > Setting up libldap-2.4-2:amd64 (2.4.45+dfsg-1ubuntu1.10) ... > ... > Setting up python3-ptyprocess (0.5.2-1) ... > Setting up linux-firmware (1.173.20) ... > update-initramfs: Generating /boot/initrd.img-5.4.0-72-generic > update-initramfs: Generating /boot/initrd.img-5.4.0-65-generic > Setting up liblwres160:amd64 (1:9.11.3+dfsg-1ubuntu1.15) ... > ... > Processing triggers for libc-bin (2.27-3ubuntu1.4) ... > Processing triggers for initramfs-tools (0.130ubuntu3.11) ... > update-initramfs: Generating /boot/initrd.img-5.4.0-72-generic > # Reference: https://wiki.debian.org/DpkgTriggers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1926608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919177] Re: Azure: issues with accelerated networking on Hirsute
** Tags added: fr-1324
--
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/1919177
Title:
Azure: issues with accelerated networking on Hirsute
Status in cloud-init:
Incomplete
Status in cloud-init package in Ubuntu:
Incomplete
Status in linux-azure package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Bug description:
[General]
On Azure, when provisioning a Hirsute VM with Accelerated Networking
enabled, sometimes part of the cloud-init configuration is not
applied.
Especially, in those cases, the public SSH key is not setup properly.
[how to reproduce]
Start a VM with AN enabled:
```
az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South"
--image
'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size
Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY"
--accelerated-networking
```
After a moment, try to SSH: if you succeed, delete and recreate a new
VM.
[troubleshooting]
To be able to connect into the VM, run:
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
```
In "/run/cloud-init/instance-data.json", I can see:
```
"publicKeys": [
{
"keyData": "",
"path": "/home/ubuntu/.ssh/authorized_keys"
}
],
```
as expected.
[workaround]
As mentioned, Azure allows the user to run command into the VM without
SSH connection. To do so, one can use the Azure CLI:
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
This example uses "ssh-import-id" but it's also possible to just echo
a given public key into /home/ubuntu/.ssh/authorized_keys
NOTE: this will only solves the SSH issue, I do not know if this bug
affects other things. If so the user would have to apply those things
manually.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1919177/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926081] Re: nr_writeback memory leak in kernel 4.15.0-137+
Installed and booted into the newly supplied kernel: root@jenkins-lon02-02-general-swarm-node-03:~# dpkg -l | grep linux | grep 144 ii linux-image-unsigned-4.15.0-144-generic 4.15.0-144.148~LP1926081.2 amd64Linux kernel image for version 4.15.0 on 64 bit x86 SMP ii linux-modules-4.15.0-144-generic4.15.0-144.148~LP1926081.2 amd64Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP root@jenkins-lon02-02-general-swarm-node-03:~# uname -r 4.15.0-144-generic root@jenkins-lon02-02-general-swarm-node-03:~# uptime 08:06:22 up 19 min, 1 user, load average: 0.74, 0.31, 0.21 root@jenkins-lon02-02-general-swarm-node-03:~# ls -l /boot/ total 201933 -rw-r--r-- 1 root root 1537161 Jul 17 2018 abi-4.15.0-29-generic -rw-r--r-- 1 root root 217414 Mar 24 12:47 config-4.15.0-141-generic -rw-r--r-- 1 root root 217426 Apr 28 09:46 config-4.15.0-144-generic -rw-r--r-- 1 root root 216807 Jul 17 2018 config-4.15.0-29-generic -rw-r--r-- 1 root root 237757 Apr 12 17:02 config-5.4.0-72-generic drwxr-xr-x 5 root root 1024 Apr 29 04:06 grub -rw-r--r-- 1 root root 43066106 Apr 15 09:40 initrd.img-4.15.0-141-generic -rw-r--r-- 1 root root 24589989 Apr 29 04:06 initrd.img-4.15.0-144-generic -rw-r--r-- 1 root root 39975786 Apr 15 08:14 initrd.img-4.15.0-29-generic -rw-r--r-- 1 root root 44490420 Apr 27 04:50 initrd.img-5.4.0-72-generic drwx-- 2 root root12288 Apr 15 07:55 lost+found -rw-r--r-- 1 root root0 Jul 17 2018 retpoline-4.15.0-29-generic -rw--- 1 root root 4081420 Mar 24 12:47 System.map-4.15.0-141-generic -rw--- 1 root root 4081469 Apr 28 09:46 System.map-4.15.0-144-generic -rw--- 1 root root 4040379 Jul 17 2018 System.map-4.15.0-29-generic -rw--- 1 root root 4585968 Apr 12 17:02 System.map-5.4.0-72-generic -rw--- 1 root root 8445600 Mar 24 11:00 vmlinuz-4.15.0-141-generic -rw--- 1 root root 8447776 Apr 28 09:46 vmlinuz-4.15.0-144-generic -rw--- 1 root root 8257272 Jul 17 2018 vmlinuz-4.15.0-29-generic -rw--- 1 root root 9445632 Apr 12 17:15 vmlinuz-5.4.0-72-generic I've run my test through 5 times, and there has been no observed leak in the writeback queue/memory used, so everything still looks good from my side. -- 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/1926081 Title: nr_writeback memory leak in kernel 4.15.0-137+ Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: SRU Justification [Impact] Ubuntu 18.04.5 4.15.0 LTS kernels at version 4.15.0-137 and above contain a memory leak due to the inclusion of patch from the upstream kernel, but not the fix for that patch which was released later. Bad patch in bionic:linux 2c17fa778db85644458b52a7df8eacc402cbc1ef mm: memcontrol: fix excessive complexity in memory.stat reporting This issue manifests itself as an increasing amount of memory used by the writeback queue, which never returns to zero. This can been seen either as the value of `nr_writeback` in /proc/vmstat, or the value of `Writeback` in /proc/meminfo. Ordinarily these values should be at or around zero, but on our servers we observe the `nr_writeback` value increasing to over 8 million, (32GB of memory), at which point it isn't long before the system IO slows to a crawl (tens of Kb/s). Our servers have 256GB of memory, and are performing many CI related activities - this issue appears to be related to concurrent writing to disk, and can be demonstrated with a simple testcase (see later). On our heavily used systems this memory leak can result in an unstable server after 2-3 days, requiring a reboot to fix it. After much investigation the issue appears to be because the patch "mm: memcontrol: fix excessive complexity in memory.stat reporting" was brought in to the 4.15.0-137 Ubuntu kernel (see https://launchpad.net/ubuntu/+source/linux/4.15.0-137.141) as part of " Bionic update: upstream stable patchset 2021-01-25 (LP: #1913214)", however in the mainline kernel there was a follow up patch because this initial patch introduced concurrency issues. The patch "mm: memcontrol: fix NR_WRITEBACK leak in memcg and system stats" is required, and should be brought into the Ubuntu packaged kernel to fix the issues reported. The required patch is here: https://github.com/torvalds/linux/commit/c3cc39118c3610eb6ab4711bc624af7fc48a35fe and was committed a few weeks after the original (broken) patch: https://github.com/torvalds/linux/commit/a983b5ebee57209c99f68c8327072f25e0e6e3da I have checked the release notes for Ubuntu versions -137 to -143, and none include this second patch that should fix the issue. (I checked https://people.canonical.com/~kernel/info/kernel-version-map.html for all the kernel
[Kernel-packages] [Bug 1926517] Re: [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926517 Title: [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: New Status in linux source package in Groovy: New Status in linux source package in Hirsute: New Bug description: [Impact] Whenever the driver is adding a vSES to virtual-phys list it is reinitializing the list head. Hence those vSES devices which were added previously are lost. [FIXES] Stop reinitializing the list every time a new vSES device is added. https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?id=4c51f9569651 CommitID: 4c51f956965120b3441cdd39c358b87daba13e19 [TESTING] [REGRESSION RISK] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877088] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2021-04-29 10:52 EDT--- (In reply to comment #41) > Hm, I think I know what went wrong. In my local tree the new script is > executable but that seems to get lost when going via debdiff. Right now it > likely will start to work doing a "chmod a+x > /etc/kernel/postinst.d/xx-update-initrd-links". Great find! After doing the chmod a+x and redoing installkernel the symlink is correct. --- Comment From niklas.schne...@ibm.com 2021-04-29 10:53 EDT--- Oh and I see the following output: Testing softlinks in /boot/... /boot/initrd.img invalid target (initrd.img-5.4.0-73-generic) Softlink: /boot/initrd.img -> initrd.img-5.12.0-07607-g8029c2a40054 /boot/initrd.img.old invalid target (initrd.img-5.4.0-72-generic) Softlink: /boot/initrd.img.old -> initrd.img-5.12.0-07607-g8029c2a40054.old -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: Fix Committed Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Hirsute: Fix Released Bug description: [Impact] * initrd link is not updated when using installkernel or "make install" from kernel sources. This leads to boot failure after installing a new kernel with mentioned methods because the kernel does not match initrd. * It's a regression because for Focal it was working before. * Issue was reproduced also on Bionic. * The proposed fixed by Stefan Bader adds a hook in /etc/kernel/postinst.d/ so installkernel will relink the initrd. The kernel DEB packages should not be affected. * The solution from Stefan (first patch) was tested by the bug reporter (niklas.schne...@ibm.com). [Test Plan] * Build a kernel * sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot * Check if /boot/initrd or /initrd symlink to the new initrd [Where problems could occur] * Installing kernel via: installkernel or "make install", so mostly kernel developer environments [Other info from developer] When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root 4031691 May 6 11:52 System.map-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 4031691 May 6 11:49 System.map-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root37 May 6 11:52 vmlinuz -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw--- 1 root root 8086072 Apr 29 15:54 vmlinuz-5.4.0-29-generic -rw-r--r-- 1 root root 9080832 May 6 11:52 vmlinuz-5.7.0-rc4-06500-gb67ea026badd
[Kernel-packages] [Bug 1922759] Re: SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10
Tested the clevo NL50RU and it works without issues with both 50 and 51. Also ubuntu 5.11 kernel works on both nuc10 and clevo NH55RZQ. I have no other device at hand that usses the ALC269_FIXUP_DMIC quirk and the NUC10 quirk is exclusive for that device. Both quirks are pretty straight forward and I don't see why only they fail but other quirks work. I asks my colleague for some additional testing, maybe ist gives a new hint. -- 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/1922759 Title: SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10 Status in linux package in Ubuntu: Fix Released Status in linux source package in Groovy: Fix Committed Bug description: The Clevo NH55RZQ and Intel NUC10 need SND_PCI_QUIRKs to fix wrong pin setup and enable microphones to work correctly when using via the audio jacks. Patches that are fixing these problems have already been accepted to current Linux stable releases: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=48698c973e6b4dde94d87cd1ded56d9436e9c97d https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=73e7161eab5dee98114987239ec9c87fe8034ddb Commit-hash: 48698c973e6b4dde94d87cd1ded56d9436e9c97d 73e7161eab5dee98114987239ec9c87fe8034ddb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918298] Re: Allow only one nvidia kernel module to be installed at once
** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: In Progress => Fix Released ** Changed in: nvidia-graphics-drivers-460 (Ubuntu Bionic) Status: In Progress => Fix Released ** Changed in: nvidia-graphics-drivers-460 (Ubuntu Focal) Status: In Progress => Fix Released ** Changed in: nvidia-graphics-drivers-460 (Ubuntu Groovy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1918298 Title: Allow only one nvidia kernel module to be installed at once Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Bug description: Currently, having different nvidia modules for the same kernel ABI is allowed. For example, both linux-modules-nvidia-450-5.4.0-66-generic and linux-modules-nvidia-460-5.4.0-66-generic can be installed at the same time. This can cause systems to boot using the wrong kernel modules. A simple fix is to use the same dependency on nvidia-kernel- common-$flavour for the binary (ABI) packages that the linux-modules- nvidia-$flavour packages already have. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1918298/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877088] Re: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf
Working on fixed up package(s)... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: Fix Committed Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Hirsute: Fix Released Bug description: [Impact] * initrd link is not updated when using installkernel or "make install" from kernel sources. This leads to boot failure after installing a new kernel with mentioned methods because the kernel does not match initrd. * It's a regression because for Focal it was working before. * Issue was reproduced also on Bionic. * The proposed fixed by Stefan Bader adds a hook in /etc/kernel/postinst.d/ so installkernel will relink the initrd. The kernel DEB packages should not be affected. * The solution from Stefan (first patch) was tested by the bug reporter (niklas.schne...@ibm.com). [Test Plan] * Build a kernel * sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot * Check if /boot/initrd or /initrd symlink to the new initrd [Where problems could occur] * Installing kernel via: installkernel or "make install", so mostly kernel developer environments [Other info from developer] When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root 4031691 May 6 11:52 System.map-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 4031691 May 6 11:49 System.map-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root37 May 6 11:52 vmlinuz -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw--- 1 root root 8086072 Apr 29 15:54 vmlinuz-5.4.0-29-generic -rw-r--r-- 1 root root 9080832 May 6 11:52 vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 9080832 May 6 11:49 vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root41 May 6 11:52 vmlinuz.old -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909422] Re: ubuntu_ftrace_smoke_test timeout on G-riscv
** Tags added: focal
** Also affects: linux-riscv (Ubuntu Groovy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1909422
Title:
ubuntu_ftrace_smoke_test timeout on G-riscv
Status in ubuntu-kernel-tests:
New
Status in linux-riscv package in Ubuntu:
New
Status in linux-riscv source package in Groovy:
New
Bug description:
Issue found on 5.8.0-13.15 RISCV with a KVM instance.
Test failed with "Timer expired (1350 sec.), nuking pid 520", test log:
$ AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local
--verbose autotest/client/tests/ubuntu_ftrace_smoke_test/control
03:46:12 INFO | Writing results to
/home/ubuntu/autotest/client/results/default
03:46:12 DEBUG| Initializing the state engine
03:46:12 DEBUG| Persistent state client.steps now set to []
03:46:13 DEBUG| Persistent option harness now set to None
03:46:13 DEBUG| Persistent option harness_args now set to None
03:46:13 DEBUG| Selected harness: standalone
03:46:15 INFO | START timestamp=1609127175localtime=Dec
28 03:46:15
03:46:16 DEBUG| Persistent state client._record_indent now set to 1
03:46:16 DEBUG| Test has timeout: 1350 sec.
03:46:16 INFO | START ubuntu_ftrace_smoke_test.ftrace-smoke-test
ubuntu_ftrace_smoke_test.ftrace-smoke-test timestamp=1609127176
timeout=1350localtime=Dec 28 03:46:16
03:46:16 DEBUG| Persistent state client._record_indent now set to 2
03:46:16 DEBUG| Persistent state client.unexpected_reboot now set to
('ubuntu_ftrace_smoke_test.ftrace-smoke-test',
'ubuntu_ftrace_smoke_test.ftrace-smoke-test')
03:46:16 DEBUG| Waiting for pid 520 for 1350 seconds
03:46:16 WARNI| System python is too old, crash handling disabled
03:46:16 DEBUG| Running
'/home/ubuntu/autotest/client/tests/ubuntu_ftrace_smoke_test/ubuntu_ftrace_smoke_test.sh'
03:46:16 DEBUG| [stdout] PASSED (CONFIG_FUNCTION_TRACER=y in
/boot/config-5.8.0-13-generic)
03:46:17 DEBUG| [stdout] PASSED (CONFIG_FUNCTION_GRAPH_TRACER=y in
/boot/config-5.8.0-13-generic)
03:46:17 DEBUG| [stdout] PASSED (CONFIG_STACK_TRACER=y in
/boot/config-5.8.0-13-generic)
03:46:17 DEBUG| [stdout] PASSED (CONFIG_DYNAMIC_FTRACE=y in
/boot/config-5.8.0-13-generic)
03:46:19 DEBUG| [stdout] PASSED all expected /sys/kernel/debug/tracing files
exist
03:46:19 DEBUG| [stdout] PASSED (function_graph in
/sys/kernel/debug/tracing/available_tracers)
03:46:19 DEBUG| [stdout] PASSED (function in
/sys/kernel/debug/tracing/available_tracers)
03:46:20 DEBUG| [stdout] PASSED (nop in
/sys/kernel/debug/tracing/available_tracers)
03:46:26 DEBUG| [stdout] PASSED (tracer function can be enabled)
03:46:35 DEBUG| [stdout] PASSED (tracer function_graph can be enabled)
03:46:35 DEBUG| [stdout] - tracer function_graph got enough data
03:46:35 DEBUG| [stdout] - tracer function_graph completed
03:46:36 DEBUG| [stdout] - tracer function_graph being turned off
03:46:36 DEBUG| [stdout] - tracer got 532 irq events
03:46:43 DEBUG| [stdout] - tracer hwlat got enough data
03:46:43 DEBUG| [stdout] - tracer hwlat completed
03:46:43 DEBUG| [stdout] - tracer hwlat being turned off
03:46:44 DEBUG| [stdout] - tracer nop being set as current tracer
03:46:46 DEBUG| [stdout] PASSED (tracer hwlat can be enabled (got 12 lines of
tracing output))
03:46:48 DEBUG| [stdout] - tracer blk got enough data
03:46:48 DEBUG| [stdout] - tracer blk completed
03:46:48 DEBUG| [stdout] - tracer blk being turned off
03:46:48 DEBUG| [stdout] - tracer nop being set as current tracer
03:46:50 DEBUG| [stdout] PASSED (tracer blk can be enabled (got 2 lines of
tracing output))
03:46:56 INFO | Timer expired (1350 sec.), nuking pid 520
03:46:57 INFO | ERROR
ubuntu_ftrace_smoke_test.ftrace-smoke-test
ubuntu_ftrace_smoke_test.ftrace-smoke-test timestamp=1609127216
localtime=Dec 28 03:46:56 Unhandled AutoservRunError: Could not kill 520
None
Traceback (most recent call last):
File "/home/ubuntu/autotest/client/job.py", line 510, in _runtest
parallel.fork_waitfor_timed(self.resultdir, pid, timeout)
File "/home/ubuntu/autotest/client/parallel.py", line 112, in
fork_waitfor_timed
utils.nuke_pid(pid)
File "/home/ubuntu/autotest/client/shared/utils.py", line 1214, in
nuke_pid
raise error.AutoservRunError('Could not kill %d' % pid, None)
AutoservRunError: Could not kill 520
None
03:46:57 INFO | END ERROR
ubuntu_ftrace_smoke_test.ftrace-smoke-test
ubuntu_ftrace_smoke_test.ftrace-smoke-test timestamp=1609127217
localtime=Dec 28 03:46:57
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1909422/+subscriptions
--
Mailing list:
[Kernel-packages] [Bug 1909422] Re: ubuntu_ftrace_smoke_test timeout on G-riscv
** Tags added: sru-20210412
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1909422
Title:
ubuntu_ftrace_smoke_test timeout on G-riscv
Status in ubuntu-kernel-tests:
New
Status in linux-riscv package in Ubuntu:
New
Status in linux-riscv source package in Groovy:
New
Bug description:
Issue found on 5.8.0-13.15 RISCV with a KVM instance.
Test failed with "Timer expired (1350 sec.), nuking pid 520", test log:
$ AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local
--verbose autotest/client/tests/ubuntu_ftrace_smoke_test/control
03:46:12 INFO | Writing results to
/home/ubuntu/autotest/client/results/default
03:46:12 DEBUG| Initializing the state engine
03:46:12 DEBUG| Persistent state client.steps now set to []
03:46:13 DEBUG| Persistent option harness now set to None
03:46:13 DEBUG| Persistent option harness_args now set to None
03:46:13 DEBUG| Selected harness: standalone
03:46:15 INFO | START timestamp=1609127175localtime=Dec
28 03:46:15
03:46:16 DEBUG| Persistent state client._record_indent now set to 1
03:46:16 DEBUG| Test has timeout: 1350 sec.
03:46:16 INFO | START ubuntu_ftrace_smoke_test.ftrace-smoke-test
ubuntu_ftrace_smoke_test.ftrace-smoke-test timestamp=1609127176
timeout=1350localtime=Dec 28 03:46:16
03:46:16 DEBUG| Persistent state client._record_indent now set to 2
03:46:16 DEBUG| Persistent state client.unexpected_reboot now set to
('ubuntu_ftrace_smoke_test.ftrace-smoke-test',
'ubuntu_ftrace_smoke_test.ftrace-smoke-test')
03:46:16 DEBUG| Waiting for pid 520 for 1350 seconds
03:46:16 WARNI| System python is too old, crash handling disabled
03:46:16 DEBUG| Running
'/home/ubuntu/autotest/client/tests/ubuntu_ftrace_smoke_test/ubuntu_ftrace_smoke_test.sh'
03:46:16 DEBUG| [stdout] PASSED (CONFIG_FUNCTION_TRACER=y in
/boot/config-5.8.0-13-generic)
03:46:17 DEBUG| [stdout] PASSED (CONFIG_FUNCTION_GRAPH_TRACER=y in
/boot/config-5.8.0-13-generic)
03:46:17 DEBUG| [stdout] PASSED (CONFIG_STACK_TRACER=y in
/boot/config-5.8.0-13-generic)
03:46:17 DEBUG| [stdout] PASSED (CONFIG_DYNAMIC_FTRACE=y in
/boot/config-5.8.0-13-generic)
03:46:19 DEBUG| [stdout] PASSED all expected /sys/kernel/debug/tracing files
exist
03:46:19 DEBUG| [stdout] PASSED (function_graph in
/sys/kernel/debug/tracing/available_tracers)
03:46:19 DEBUG| [stdout] PASSED (function in
/sys/kernel/debug/tracing/available_tracers)
03:46:20 DEBUG| [stdout] PASSED (nop in
/sys/kernel/debug/tracing/available_tracers)
03:46:26 DEBUG| [stdout] PASSED (tracer function can be enabled)
03:46:35 DEBUG| [stdout] PASSED (tracer function_graph can be enabled)
03:46:35 DEBUG| [stdout] - tracer function_graph got enough data
03:46:35 DEBUG| [stdout] - tracer function_graph completed
03:46:36 DEBUG| [stdout] - tracer function_graph being turned off
03:46:36 DEBUG| [stdout] - tracer got 532 irq events
03:46:43 DEBUG| [stdout] - tracer hwlat got enough data
03:46:43 DEBUG| [stdout] - tracer hwlat completed
03:46:43 DEBUG| [stdout] - tracer hwlat being turned off
03:46:44 DEBUG| [stdout] - tracer nop being set as current tracer
03:46:46 DEBUG| [stdout] PASSED (tracer hwlat can be enabled (got 12 lines of
tracing output))
03:46:48 DEBUG| [stdout] - tracer blk got enough data
03:46:48 DEBUG| [stdout] - tracer blk completed
03:46:48 DEBUG| [stdout] - tracer blk being turned off
03:46:48 DEBUG| [stdout] - tracer nop being set as current tracer
03:46:50 DEBUG| [stdout] PASSED (tracer blk can be enabled (got 2 lines of
tracing output))
03:46:56 INFO | Timer expired (1350 sec.), nuking pid 520
03:46:57 INFO | ERROR
ubuntu_ftrace_smoke_test.ftrace-smoke-test
ubuntu_ftrace_smoke_test.ftrace-smoke-test timestamp=1609127216
localtime=Dec 28 03:46:56 Unhandled AutoservRunError: Could not kill 520
None
Traceback (most recent call last):
File "/home/ubuntu/autotest/client/job.py", line 510, in _runtest
parallel.fork_waitfor_timed(self.resultdir, pid, timeout)
File "/home/ubuntu/autotest/client/parallel.py", line 112, in
fork_waitfor_timed
utils.nuke_pid(pid)
File "/home/ubuntu/autotest/client/shared/utils.py", line 1214, in
nuke_pid
raise error.AutoservRunError('Could not kill %d' % pid, None)
AutoservRunError: Could not kill 520
None
03:46:57 INFO | END ERROR
ubuntu_ftrace_smoke_test.ftrace-smoke-test
ubuntu_ftrace_smoke_test.ftrace-smoke-test timestamp=1609127217
localtime=Dec 28 03:46:57
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1909422/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1926608] [NEW] upgrading does not defer initramfs updates
Public bug reported: Upgrading linux-firmware (1.173.20) on Ubuntu (18.04.5) will cause the initramfs files to be updated during the "setting up" phase of linux- firmware's installation. However, if there are other packages that also require initramfs to be updated, they will be updated again later during the "processing triggers" phase. The triggers mechanism of deb- installer is designed to avoid this duplication of effort and speed up the time taken to complete an upgrade. If there is no specific reason for linux-firmware to force the initramfs update during setup, I believe it makes sense to defer that action. In the excerpt below, udev and linux-firmware are both in the list of packages to be upgraded. Udev uses the trigger mechanism and linux- firmware does not. > # apt dist-upgrade > ... > Setting up libglib2.0-data (2.56.4-0ubuntu0.18.04.8) ... > Setting up udev (237-3ubuntu10.46) ... > update-initramfs: deferring update (trigger activated) > Setting up libldap-2.4-2:amd64 (2.4.45+dfsg-1ubuntu1.10) ... > ... > Setting up python3-ptyprocess (0.5.2-1) ... > Setting up linux-firmware (1.173.20) ... > update-initramfs: Generating /boot/initrd.img-5.4.0-72-generic > update-initramfs: Generating /boot/initrd.img-5.4.0-65-generic > Setting up liblwres160:amd64 (1:9.11.3+dfsg-1ubuntu1.15) ... > ... > Processing triggers for libc-bin (2.27-3ubuntu1.4) ... > Processing triggers for initramfs-tools (0.130ubuntu3.11) ... > update-initramfs: Generating /boot/initrd.img-5.4.0-72-generic > # Reference: https://wiki.debian.org/DpkgTriggers ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- 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/1926608 Title: upgrading does not defer initramfs updates Status in linux-firmware package in Ubuntu: New Bug description: Upgrading linux-firmware (1.173.20) on Ubuntu (18.04.5) will cause the initramfs files to be updated during the "setting up" phase of linux- firmware's installation. However, if there are other packages that also require initramfs to be updated, they will be updated again later during the "processing triggers" phase. The triggers mechanism of deb-installer is designed to avoid this duplication of effort and speed up the time taken to complete an upgrade. If there is no specific reason for linux-firmware to force the initramfs update during setup, I believe it makes sense to defer that action. In the excerpt below, udev and linux-firmware are both in the list of packages to be upgraded. Udev uses the trigger mechanism and linux- firmware does not. > # apt dist-upgrade > ... > Setting up libglib2.0-data (2.56.4-0ubuntu0.18.04.8) ... > Setting up udev (237-3ubuntu10.46) ... > update-initramfs: deferring update (trigger activated) > Setting up libldap-2.4-2:amd64 (2.4.45+dfsg-1ubuntu1.10) ... > ... > Setting up python3-ptyprocess (0.5.2-1) ... > Setting up linux-firmware (1.173.20) ... > update-initramfs: Generating /boot/initrd.img-5.4.0-72-generic > update-initramfs: Generating /boot/initrd.img-5.4.0-65-generic > Setting up liblwres160:amd64 (1:9.11.3+dfsg-1ubuntu1.15) ... > ... > Processing triggers for libc-bin (2.27-3ubuntu1.4) ... > Processing triggers for initramfs-tools (0.130ubuntu3.11) ... > update-initramfs: Generating /boot/initrd.img-5.4.0-72-generic > # Reference: https://wiki.debian.org/DpkgTriggers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1926608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905728] Re: log_check / tainted_check failed in ubuntu_boot because of warnings (Found insecure W+X mapping at address) found on G-riscv
** Tags added: sru-20210412 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1905728 Title: log_check / tainted_check failed in ubuntu_boot because of warnings (Found insecure W+X mapping at address) found on G-riscv Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux-riscv package in Ubuntu: New Status in linux source package in Groovy: New Status in linux-riscv source package in Groovy: Confirmed Bug description: Issue found on 5.8.0-10-generic riscv Message reported on boot. [ 13.483103] [ cut here ] [ 13.483711] riscv/mm: Found insecure W+X mapping at address (ptrval)/0xffdff800 [ 13.484542] WARNING: CPU: 5 PID: 1 at arch/riscv/mm/ptdump.c:200 note_page+0x24c/0x252 [ 13.485175] Modules linked in: [ 13.485606] CPU: 5 PID: 1 Comm: swapper/0 Not tainted 5.8.0-10-generic #12-Ubuntu [ 13.486091] epc: ffe000208f18 ra : ffe000208f18 sp : ffe1f5bfbb30 [ 13.486471] gp : ffe001728ee0 tp : ffe1f5bf5080 t0 : ffe00173ed88 [ 13.486850] t1 : ffe00173ed20 t2 : 0001fecbe000 s0 : ffe1f5bfbb80 [ 13.487250] s1 : ffe1f5bfbe10 a0 : 0053 a1 : 0020 [ 13.487633] a2 : ffe1f5bfb870 a3 : a4 : ffe0016200f8 [ 13.488040] a5 : ffe0016200f8 a6 : 00b5 a7 : ffe0006f2806 [ 13.488421] s2 : ffdff8001000 s3 : s4 : 0004 [ 13.488800] s5 : s6 : s7 : ffe1f5bfbd20 [ 13.489322] s8 : ffdff8001000 s9 : ffe00172a148 s10: ffdff8002000 [ 13.489738] s11: ffe000c16e20 t3 : 0003cec0 t4 : 0003cec0 [ 13.490119] t5 : t6 : ffe001739462 [ 13.490406] status: 0120 badaddr: cause: 0003 [ 13.490849] ---[ end trace 607c551edff1ef12 ]--- Please find attachment for the boot dmesg log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1905728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918134] Re: LRMv4: switch to signing nvidia modules via the Ubuntu Modules signing key
I confirm that with the recent changes synced back to groovy linux packaging the installation of linux-modules-nvidia-460-generic can be performed successfully. The driver is built and the module fails to load due to lack of hardware as expected. Tested with: $ uname -r 5.8.0-51-generic ** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- 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/1918134 Title: LRMv4: switch to signing nvidia modules via the Ubuntu Modules signing key Status in linux package in Ubuntu: Fix Released Status in linux-restricted-modules package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Bionic: Fix Released Status in linux source package in Focal: Fix Committed Status in linux-restricted-modules source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux-restricted-modules source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-restricted-modules source package in Hirsute: Fix Released Bug description: To allow decoupling of nvidia-graphics-drivers- streams and versions from the underlying kernel versions we wish to be able to sign new kernel modules into an existing kernel after the fact. Under bug #1898716 we added support for an Ubuntu Modules signing key certificate. Rebuild the LRM package to make use of this new signature. This involves splitting the LRM package into three. linux-restricted- modules first builds the nvidia-graphics-drivers-* we require signed. linux-restricted-generate then consumes the .o's produced in that build and forms a signing custom binary upload for this. linux- restricted-signatures then consumes the signing result from the LRG upload and expresses clean redistributible signatures which are consumed by LRM at installation time. LRG must be embargoed as it (necessarily) generates fully formed .ko files for signing. Additional process is added to the kernel build life-cycle to handle the privacy requirements of the LRG/LRS interaction. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926597] Re: Linux 5.10.0-1024.25 breaks HDMI with Intel i915
I cannot install this 5.12 kernel because dependencies issue against libc6 (>2.33 needed). -- 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/1926597 Title: Linux 5.10.0-1024.25 breaks HDMI with Intel i915 Status in linux package in Ubuntu: Incomplete Bug description: Hi, [Thinkpad T480s, Intel iGPU 8550u, Ubuntu Focal up-to-date, GNOME Wayland session] Previous 5.10.0-1023.24 was ok. Kernel 5.8 HWE is ok. I did not test a X session. Plugging HDMI after GNOME is loaded fails to display anything on the HDMI display. Plugging HDMI at boot or at GDM screen makes the HDMI display works as usual. Unplugging HDMI (display only on this one) during GNOME session does not update displays state. Nothing happens. I have to press the switch-display-key on my laptop to actualize the setup and make my laptop's display active. When I unplug HDMI during GNOME session, nothing appears in logs. My laptop fails to enter sleep after having unplugged the HDMI. Related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924238 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926597/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926597] Re: Linux 5.10.0-1024.25 breaks HDMI with Intel i915
Please test latest drm-tip kernel to make sure the bug is not present in upstream: https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/ -- 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/1926597 Title: Linux 5.10.0-1024.25 breaks HDMI with Intel i915 Status in linux package in Ubuntu: Incomplete Bug description: Hi, [Thinkpad T480s, Intel iGPU 8550u, Ubuntu Focal up-to-date, GNOME Wayland session] Previous 5.10.0-1023.24 was ok. Kernel 5.8 HWE is ok. I did not test a X session. Plugging HDMI after GNOME is loaded fails to display anything on the HDMI display. Plugging HDMI at boot or at GDM screen makes the HDMI display works as usual. Unplugging HDMI (display only on this one) during GNOME session does not update displays state. Nothing happens. I have to press the switch-display-key on my laptop to actualize the setup and make my laptop's display active. When I unplug HDMI during GNOME session, nothing appears in logs. My laptop fails to enter sleep after having unplugged the HDMI. Related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924238 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926597/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922759] Re: SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10
NUC 10 also tested, also doesn't work Since the clevo and the nuc are completly different platforms with different quirks i suspect it's not the quirk causing the issue between 50 and 51. I'm currently installing ubuntu on a different clevo that should already be working, and let you know my results. -- 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/1922759 Title: SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10 Status in linux package in Ubuntu: Fix Released Status in linux source package in Groovy: Fix Committed Bug description: The Clevo NH55RZQ and Intel NUC10 need SND_PCI_QUIRKs to fix wrong pin setup and enable microphones to work correctly when using via the audio jacks. Patches that are fixing these problems have already been accepted to current Linux stable releases: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=48698c973e6b4dde94d87cd1ded56d9436e9c97d https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=73e7161eab5dee98114987239ec9c87fe8034ddb Commit-hash: 48698c973e6b4dde94d87cd1ded56d9436e9c97d 73e7161eab5dee98114987239ec9c87fe8034ddb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924238] Re: Fix no picture from HDMI when it's plugged after boot
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926597 -- 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/1924238 Title: Fix no picture from HDMI when it's plugged after boot Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] On Intel CML desktop, there's no HDMI output when the cable is not connected pre-boot. [Fix] Properly handle lane polarity so the driver can write different values to the register to enable the port. [Test] 1. Boot with DP display. 2. Connect HDMI under GNOME desktop. 3. No picture on HDMI monitor. With the fix applied, the issue is resolved. [Where problems could occur] If the BIOS VBT table is not correct, which did happen in the pase, this fix may break those ports. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926597] 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 1926597 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/1926597 Title: Linux 5.10.0-1024.25 breaks HDMI with Intel i915 Status in linux package in Ubuntu: Incomplete Bug description: Hi, [Thinkpad T480s, Intel iGPU 8550u, Ubuntu Focal up-to-date, GNOME Wayland session] Previous 5.10.0-1023.24 was ok. Kernel 5.8 HWE is ok. I did not test a X session. Plugging HDMI after GNOME is loaded fails to display anything on the HDMI display. Plugging HDMI at boot or at GDM screen makes the HDMI display works as usual. Unplugging HDMI (display only on this one) during GNOME session does not update displays state. Nothing happens. I have to press the switch-display-key on my laptop to actualize the setup and make my laptop's display active. When I unplug HDMI during GNOME session, nothing appears in logs. My laptop fails to enter sleep after having unplugged the HDMI. Related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924238 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926597/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926597] [NEW] Linux 5.10.0-1024.25 breaks HDMI with Intel i915
Public bug reported: Hi, [Thinkpad T480s, Intel iGPU 8550u, Ubuntu Focal up-to-date, GNOME Wayland session] Previous 5.10.0-1023.24 was ok. Kernel 5.8 HWE is ok. I did not test a X session. Plugging HDMI after GNOME is loaded fails to display anything on the HDMI display. Plugging HDMI at boot or at GDM screen makes the HDMI display works as usual. Unplugging HDMI (display only on this one) during GNOME session does not update displays state. Nothing happens. I have to press the switch- display-key on my laptop to actualize the setup and make my laptop's display active. When I unplug HDMI during GNOME session, nothing appears in logs. My laptop fails to enter sleep after having unplugged the HDMI. Related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924238 ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1926597 Title: Linux 5.10.0-1024.25 breaks HDMI with Intel i915 Status in linux package in Ubuntu: Incomplete Bug description: Hi, [Thinkpad T480s, Intel iGPU 8550u, Ubuntu Focal up-to-date, GNOME Wayland session] Previous 5.10.0-1023.24 was ok. Kernel 5.8 HWE is ok. I did not test a X session. Plugging HDMI after GNOME is loaded fails to display anything on the HDMI display. Plugging HDMI at boot or at GDM screen makes the HDMI display works as usual. Unplugging HDMI (display only on this one) during GNOME session does not update displays state. Nothing happens. I have to press the switch-display-key on my laptop to actualize the setup and make my laptop's display active. When I unplug HDMI during GNOME session, nothing appears in logs. My laptop fails to enter sleep after having unplugged the HDMI. Related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924238 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926597/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922759] Re: SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10
Sorry, by "remove these patches" on the previous comment I mean for now only the Clevo quirk. The NUC change is still to be tested and can be kept if we have positive test results. -- 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/1922759 Title: SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10 Status in linux package in Ubuntu: Fix Released Status in linux source package in Groovy: Fix Committed Bug description: The Clevo NH55RZQ and Intel NUC10 need SND_PCI_QUIRKs to fix wrong pin setup and enable microphones to work correctly when using via the audio jacks. Patches that are fixing these problems have already been accepted to current Linux stable releases: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=48698c973e6b4dde94d87cd1ded56d9436e9c97d https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=73e7161eab5dee98114987239ec9c87fe8034ddb Commit-hash: 48698c973e6b4dde94d87cd1ded56d9436e9c97d 73e7161eab5dee98114987239ec9c87fe8034ddb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922759] Re: SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10
Hello Werner, Thank you for your feedback. If with these patches it is worse than with the unpatched kernel we might need some prerequisite commits. I think the best option would be to remove these patches for now until we have identified which are the missing commits. Would you agree? -- 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/1922759 Title: SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10 Status in linux package in Ubuntu: Fix Released Status in linux source package in Groovy: Fix Committed Bug description: The Clevo NH55RZQ and Intel NUC10 need SND_PCI_QUIRKs to fix wrong pin setup and enable microphones to work correctly when using via the audio jacks. Patches that are fixing these problems have already been accepted to current Linux stable releases: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=48698c973e6b4dde94d87cd1ded56d9436e9c97d https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=73e7161eab5dee98114987239ec9c87fe8034ddb Commit-hash: 48698c973e6b4dde94d87cd1ded56d9436e9c97d 73e7161eab5dee98114987239ec9c87fe8034ddb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877088] Re: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf
Hm, I think I know what went wrong. In my local tree the new script is executable but that seems to get lost when going via debdiff. Right now it likely will start to work doing a "chmod a+x /etc/kernel/postinst.d /xx-update-initrd-links". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: Fix Committed Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Hirsute: Fix Released Bug description: [Impact] * initrd link is not updated when using installkernel or "make install" from kernel sources. This leads to boot failure after installing a new kernel with mentioned methods because the kernel does not match initrd. * It's a regression because for Focal it was working before. * Issue was reproduced also on Bionic. * The proposed fixed by Stefan Bader adds a hook in /etc/kernel/postinst.d/ so installkernel will relink the initrd. The kernel DEB packages should not be affected. * The solution from Stefan (first patch) was tested by the bug reporter (niklas.schne...@ibm.com). [Test Plan] * Build a kernel * sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot * Check if /boot/initrd or /initrd symlink to the new initrd [Where problems could occur] * Installing kernel via: installkernel or "make install", so mostly kernel developer environments [Other info from developer] When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root 4031691 May 6 11:52 System.map-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 4031691 May 6 11:49 System.map-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root37 May 6 11:52 vmlinuz -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw--- 1 root root 8086072 Apr 29 15:54 vmlinuz-5.4.0-29-generic -rw-r--r-- 1 root root 9080832 May 6 11:52 vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 9080832 May 6 11:49 vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root41 May 6 11:52 vmlinuz.old -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926081] Re: nr_writeback memory leak in kernel 4.15.0-137+
Tim,
I'll cordon off the machine we've been using again and run some tests
with this new kernel, hopefully I'll be able to do it today.
--
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/1926081
Title:
nr_writeback memory leak in kernel 4.15.0-137+
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
SRU Justification
[Impact]
Ubuntu 18.04.5 4.15.0 LTS kernels at version 4.15.0-137 and above
contain a memory leak due to the inclusion of patch from the upstream
kernel, but not the fix for that patch which was released later.
Bad patch in bionic:linux 2c17fa778db85644458b52a7df8eacc402cbc1ef mm:
memcontrol: fix excessive complexity in memory.stat reporting
This issue manifests itself as an increasing amount of memory used by
the writeback queue, which never returns to zero. This can been seen
either as the value of `nr_writeback` in /proc/vmstat, or the value of
`Writeback` in /proc/meminfo.
Ordinarily these values should be at or around zero, but on our
servers we observe the `nr_writeback` value increasing to over 8
million, (32GB of memory), at which point it isn't long before the
system IO slows to a crawl (tens of Kb/s). Our servers have 256GB of
memory, and are performing many CI related activities - this issue
appears to be related to concurrent writing to disk, and can be
demonstrated with a simple testcase (see later).
On our heavily used systems this memory leak can result in an unstable
server after 2-3 days, requiring a reboot to fix it.
After much investigation the issue appears to be because the patch
"mm: memcontrol: fix excessive complexity in memory.stat reporting"
was brought in to the 4.15.0-137 Ubuntu kernel (see
https://launchpad.net/ubuntu/+source/linux/4.15.0-137.141) as part of
" Bionic update: upstream stable patchset 2021-01-25 (LP: #1913214)",
however in the mainline kernel there was a follow up patch because
this initial patch introduced concurrency issues. The patch "mm:
memcontrol: fix NR_WRITEBACK leak in memcg and system stats" is
required, and should be brought into the Ubuntu packaged kernel to fix
the issues reported.
The required patch is here:
https://github.com/torvalds/linux/commit/c3cc39118c3610eb6ab4711bc624af7fc48a35fe
and was committed a few weeks after the original (broken) patch:
https://github.com/torvalds/linux/commit/a983b5ebee57209c99f68c8327072f25e0e6e3da
I have checked the release notes for Ubuntu versions -137 to -143, and
none include this second patch that should fix the issue. (I checked
https://people.canonical.com/~kernel/info/kernel-version-map.html for
all the kernel versions, and then visited each changelog page in turn,
e.g. https://launchpad.net/ubuntu/+source/linux/4.15.0-143.147 looking
for "mm: memcontrol: fix NR_WRITEBACK leak in memcg and system
stats").
We do not observe this on the 5.4.0 kernel (supported HWE kernel on
18.05.5), which includes this second patch. That kernel may also
include other patches, so we do not know if any other fixes are also
required, but the one we have linked above seems to definitely be
needed, and seems to match our symptoms.
[Test Plan]
Testcase:
The following is enough to permanently increase the value of
`nr_writeback` on our systems (by about 2000 during most executions):
```
date
grep nr_writeback /proc/vmstat
mkdir -p /docker/testfiles/{1..5}
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/1/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/2/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/3/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/4/file.% bs=4k count=10 status=none' &
seq -w 1 10 | xargs -n1 -I% sh -c 'dd if=/dev/urandom
of=/docker/testfiles/5/file.% bs=4k count=10 status=none' &
wait $(jobs -p)
grep nr_writeback /proc/vmstat
date
```
Subsequent iterations of the test raise it further, and on a system
doing a lot of writing from a lot of different processes, it can rise
quickly.
System details:
lsb_release -rd
Description: Ubuntu 18.04.5 LTS
Release: 18.04
Affected kernel: 4.15.0-137 onwards (current latest version tried was
4.15.0-142)
e.g.
apt-cache policy linux-image-4.15.0-141-generic
linux-image-4.15.0-141-generic:
Installed: 4.15.0-141.145
Candidate: 4.15.0-141.145
Version table:
*** 4.15.0-141.145 500
500 http://mirrors.service.networklayer.com/ubuntu
bionic-updates/main amd64 Packages
500 http://mirrors.service.networklayer.com/ubuntu
bionic-security/main
[Kernel-packages] [Bug 1877088] Re: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf
Need to take a deeper look into it later but I really think I have added some output about checking the links to the /etc/kernel/postinst.d script which does not show in the output of the last comment. I think it did not do either in the previous attempts but I missed that back then. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: Fix Committed Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Hirsute: Fix Released Bug description: [Impact] * initrd link is not updated when using installkernel or "make install" from kernel sources. This leads to boot failure after installing a new kernel with mentioned methods because the kernel does not match initrd. * It's a regression because for Focal it was working before. * Issue was reproduced also on Bionic. * The proposed fixed by Stefan Bader adds a hook in /etc/kernel/postinst.d/ so installkernel will relink the initrd. The kernel DEB packages should not be affected. * The solution from Stefan (first patch) was tested by the bug reporter (niklas.schne...@ibm.com). [Test Plan] * Build a kernel * sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot * Check if /boot/initrd or /initrd symlink to the new initrd [Where problems could occur] * Installing kernel via: installkernel or "make install", so mostly kernel developer environments [Other info from developer] When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root 4031691 May 6 11:52 System.map-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 4031691 May 6 11:49 System.map-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root37 May 6 11:52 vmlinuz -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw--- 1 root root 8086072 Apr 29 15:54 vmlinuz-5.4.0-29-generic -rw-r--r-- 1 root root 9080832 May 6 11:52 vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 9080832 May 6 11:49 vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root41 May 6 11:52 vmlinuz.old -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924238] Re: Fix no picture from HDMI when it's plugged after boot
There are many i915 changes between 1023 and 1024. Can you please file a new bug? -- 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/1924238 Title: Fix no picture from HDMI when it's plugged after boot Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] On Intel CML desktop, there's no HDMI output when the cable is not connected pre-boot. [Fix] Properly handle lane polarity so the driver can write different values to the register to enable the port. [Test] 1. Boot with DP display. 2. Connect HDMI under GNOME desktop. 3. No picture on HDMI monitor. With the fix applied, the issue is resolved. [Where problems could occur] If the BIOS VBT table is not correct, which did happen in the pase, this fix may break those ports. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847982] Re: memcg_subgroup_charge from controllers in ubuntu_ltp failed on D/E/F/G
Found on F-oem-5.10 5.10.0-1025.26-oem rumford -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1847982 Title: memcg_subgroup_charge from controllers in ubuntu_ltp failed on D/E/F/G Status in ubuntu-kernel-tests: New Status in linux-azure package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-azure source package in Disco: Won't Fix Status in linux-kvm source package in Disco: Won't Fix Status in linux-oracle source package in Disco: Won't Fix Bug description: Issue found on Azure Disco kernel 5.0.0-1023.24 Failed on instance: * Standard_GS2 * Standard_D16s_v3 Passed on instance: * Standard_F32s_v2 * Standard_L8s_v2 * Standard_L4s * Standard_L8s_v2 (Although it has passed on these instances, but they all have the same test output, just the pids are different) Test failed with: /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error tag=memcg_subgroup_charge stime=1570239843 dur=3 exit=exited stat=1 core=no cu=7 cs=11 startup='Sat Oct 5 01:44:03 2019' memcg_subgroup_charge 1 TINFO: Starting test 1 /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error memcg_subgroup_charge 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_subgroup_charge 1 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_subgroup_charge 1 TINFO: Warming up pid: 119041 memcg_subgroup_charge 1 TINFO: Process is still here after warm up: 119041 memcg_subgroup_charge 1 TPASS: rss is 135168 as expected memcg_subgroup_charge 2 TPASS: rss is 0 as expected memcg_subgroup_charge 3 TINFO: Starting test 2 /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error memcg_subgroup_charge 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_subgroup_charge 3 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_subgroup_charge 3 TINFO: Warming up pid: 119071 memcg_subgroup_charge 3 TINFO: Process is still here after warm up: 119071 memcg_subgroup_charge 3 TFAIL: rss is 0, 135168 expected memcg_subgroup_charge 4 TPASS: rss is 0 as expected memcg_subgroup_charge 5 TINFO: Starting test 3 /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error memcg_subgroup_charge 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_subgroup_charge 5 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_subgroup_charge 5 TINFO: Warming up pid: 119094 memcg_subgroup_charge 5 TINFO: Process is still here after warm up: 119094 memcg_subgroup_charge 5 TPASS: rss is 135168 as expected memcg_subgroup_charge 6 TPASS: rss is 0 as expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1847982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924238] Re: Fix no picture from HDMI when it's plugged after boot
Previous one: *-1023 I'm sure of that because I use HDMI every day, at work or at home. And I checked my apt/Synaptic's history. Nothing else was updated this day apart kernels. I updated GS and Mutter to 3.36.9 *way after* having experienced the issue for the first time. And kernel 5.8 hwe is working nicely with HDMI... Please note that I did have some partially similar issues with 5.10 oem with my Dell WD15 dock (2 displays) at work: after unplugging the usb-c, I have to force the shutdown and sleep is broken. I absolutely don't know if this is related to this bug here. -- 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/1924238 Title: Fix no picture from HDMI when it's plugged after boot Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] On Intel CML desktop, there's no HDMI output when the cable is not connected pre-boot. [Fix] Properly handle lane polarity so the driver can write different values to the register to enable the port. [Test] 1. Boot with DP display. 2. Connect HDMI under GNOME desktop. 3. No picture on HDMI monitor. With the fix applied, the issue is resolved. [Where problems could occur] If the BIOS VBT table is not correct, which did happen in the pase, this fix may break those ports. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877088] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2021-04-29 04:39 EDT--- Redid the test on a freshly installed Focal + Proposed + "apt update && apt upgrade". Still the same behavior: root@t46lp77:~/testkernel# installkernel 5.12.0-07607-g8029c2a40054 bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.12.0-07607-g8029c2a40054 /boot/vmlinuz-5.12.0-07607-g8029c2a40054 run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.12.0-07607-g8029c2a40054 /boot/vmlinuz-5.12.0-07607-g8029c2a40054 update-initramfs: Generating /boot/initrd.img-5.12.0-07607-g8029c2a40054 Using config file '/etc/zipl.conf' Building bootmap in '/boot' Adding IPL section 'ubuntu' (default) Preparing boot device: sdn. Done. run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 5.12.0-07607-g8029c2a40054 /boot/vmlinuz-5.12.0-07607-g8029c2a40054 run-parts: executing /etc/kernel/postinst.d/update-notifier 5.12.0-07607-g8029c2a40054 /boot/vmlinuz-5.12.0-07607-g8029c2a40054 run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.12.0-07607-g8029c2a40054 /boot/vmlinuz-5.12.0-07607-g8029c2a40054 Using config file '/etc/zipl.conf' Building bootmap in '/boot' Adding IPL section 'ubuntu' (default) Preparing boot device: sdn. Done. root@t46lp77:~/testkernel# ls -l /boot total 103288 -rw-r--r-- 1 root root 4475592 Apr 29 08:35 System.map-5.12.0-07607-g8029c2a40054 -rw--- 1 root root 3099673 Apr 12 15:12 System.map-5.4.0-72-generic -rw--- 1 root root 3100152 Apr 14 16:35 System.map-5.4.0-73-generic -rw--- 1 root root45056 Apr 29 08:36 bootmap -rw-r--r-- 1 root root90468 Apr 12 15:12 config-5.4.0-72-generic -rw-r--r-- 1 root root90468 Apr 14 16:35 config-5.4.0-73-generic lrwxrwxrwx 1 root root 27 Apr 29 08:19 initrd.img -> initrd.img-5.4.0-73-generic -rw-r--r-- 1 root root 20355770 Apr 29 08:36 initrd.img-5.12.0-07607-g8029c2a40054 -rw-r--r-- 1 root root 24195082 Apr 29 08:19 initrd.img-5.4.0-72-generic -rw-r--r-- 1 root root 24199441 Apr 29 08:19 initrd.img-5.4.0-73-generic lrwxrwxrwx 1 root root 27 Apr 28 15:27 initrd.img.old -> initrd.img-5.4.0-72-generic lrwxrwxrwx 1 root root 34 Apr 29 08:35 vmlinuz -> vmlinuz-5.12.0-07607-g8029c2a40054 -rw-r--r-- 1 root root 9744384 Apr 29 08:35 vmlinuz-5.12.0-07607-g8029c2a40054 -rw--- 1 root root 8172088 Apr 12 16:56 vmlinuz-5.4.0-72-generic -rw--- 1 root root 8172088 Apr 14 16:37 vmlinuz-5.4.0-73-generic lrwxrwxrwx 1 root root 24 Apr 29 08:19 vmlinuz.old -> vmlinuz-5.4.0-73-generic The vmlinuz link is updated correctly but the initrd.img links (initrd.img and initrd.img.old) are not. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: Fix Committed Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Hirsute: Fix Released Bug description: [Impact] * initrd link is not updated when using installkernel or "make install" from kernel sources. This leads to boot failure after installing a new kernel with mentioned methods because the kernel does not match initrd. * It's a regression because for Focal it was working before. * Issue was reproduced also on Bionic. * The proposed fixed by Stefan Bader adds a hook in /etc/kernel/postinst.d/ so installkernel will relink the initrd. The kernel DEB packages should not be affected. * The solution from Stefan (first patch) was tested by the bug reporter (niklas.schne...@ibm.com). [Test Plan] * Build a kernel * sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot * Check if /boot/initrd or /initrd symlink to the new initrd [Where problems could occur] * Installing kernel via: installkernel or "make install", so mostly kernel developer environments [Other info from developer] When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing
[Kernel-packages] [Bug 1921345] Re: Support MIPI camera through Intel IPU6
Verified linux-oem-5.10 kernel packages version 5.10.0-1024.25 from focal-proposed. ** 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-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1921345 Title: Support MIPI camera through Intel IPU6 Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-firmware source package in Hirsute: Invalid Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [SRU Justification] [Impact] There are new platforms with MIPI camera based on Intel IPU6(Imaging Processing Unit version 6) currently unsupported in Ubuntu. [Fix] Intel IPU6 can be enabled by integration of following kernel driver, firmware, userspace HAL libraries as well as a GStreamer source element: * https://github.com/intel/ipu6-drivers * https://github.com/intel/ipu6-camera-bins * https://github.com/intel/ipu6-camera-hal * https://github.com/intel/icamerasrc This patchset took kernel patches from intel/ipu6-drivers. [Test Case] With kernel/firmware properly installed, the hardware should be ready for further development: $ dmesg | grep ipu intel-ipu6 intel-ipu: enabling device ( -> 0002) intel-ipu6 intel-ipu: Device 0x9a19 (rev: 0x1) intel-ipu6 intel-ipu: physical base address 0x605400 intel-ipu6 intel-ipu: mapped as: 0x97793328 intel-ipu6 intel-ipu: IPU in secure mode intel-ipu6 intel-ipu: IPC reset done intel-ipu6 intel-ipu: cpd file name: intel/ipu6_fw.bin intel-ipu6 intel-ipu: FW version: 20201222 intel-ipu6 intel-ipu: Sending BOOT_LOAD to CSE intel-ipu6 intel-ipu: Sending AUTHENTICATE_RUN to CSE intel-ipu6 intel-ipu: CSE authenticate_run done intel-ipu6 intel-ipu: IPU driver version 1.0 intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 intel-ipu6-isys intel-ipu6-isys0: bind ov01a1s 20-0036 nlanes is 1 port is 1 intel-ipu6-isys intel-ipu6-isys0: All sensor registration completed. intel-ipu6-isys intel-ipu6-isys0: stream on ov01a1s 20-0036 There should be nearly 24 video4linux devices created under /dev. [Where problems could occur] MIPI camera through Intel IPU6 takes also firmware blobs loaded in runtime from user space, addtional softwares are also required to fully enable it for oridinary use. The exposed video devices are hidden from general users and a relay daemon+v4l2loopback is used to enable use from existing applications. >From kernel's point of view, there is still a known issue that it takes root priviledge to access these devices. [Other Info] So far Intel has no plan to commit this driver to upstream yet, so it's only nominated for oem-5.10. It will only be nominated to generic kernels when the plan/requirements have changed. The original driver Kconfig would disable VIDEO_IPU3_CIO2, but that's reverted to avoid unnecessary changes to existing users. == original bug description == The Intel imaging processing unit version 6, found in Intel SoCs and used for capturing images and video from a camera sensor is enabled by integration of following kernel driver, firmware, userspace HAL libraries as well as a GStreamer source element: * https://github.com/intel/ipu6-drivers * https://github.com/intel/ipu6-camera-bins * https://github.com/intel/ipu6-camera-hal * https://github.com/intel/icamerasrc With all components properly installed, the hardware should be ready for further development: intel-ipu6 intel-ipu: enabling device ( -> 0002) intel-ipu6 intel-ipu: Device 0x9a19 (rev: 0x1) intel-ipu6 intel-ipu: physical base address 0x605400 intel-ipu6 intel-ipu: mapped as: 0x97793328 intel-ipu6 intel-ipu: IPU in secure mode intel-ipu6 intel-ipu: IPC reset done intel-ipu6 intel-ipu: cpd file name: intel/ipu6_fw.bin intel-ipu6 intel-ipu: FW version: 20201222 intel-ipu6 intel-ipu: Sending BOOT_LOAD to CSE intel-ipu6 intel-ipu: Sending AUTHENTICATE_RUN to CSE intel-ipu6 intel-ipu: CSE authenticate_run done intel-ipu6 intel-ipu: IPU driver version 1.0 intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 intel-ipu6-isys intel-ipu6-isys0: bind ov01a1s 20-0036 nlanes is 1 port is 1 intel-ipu6-isys intel-ipu6-isys0: All sensor registration completed. intel-ipu6-isys intel-ipu6-isys0: stream on ov01a1s 20-0036 This one equips an OV01A1S sensor, and HM11B1 is also supported. --- ProblemType:
[Kernel-packages] [Bug 1926579] [NEW] On TGL platforms screen shows garbage when browsing website by scrolling mouse
Public bug reported: [Impact] On Dell TGL platforms screen shows garbage when browsing website by scrolling mouse [Fix] This patch fixes the issue https://patchwork.freedesktop.org/patch/430153/?series=89348=1 [Test] Verified on Dell TGL-H platforms. [Where problems could occur] It disable PSR2 on A0 and B0 TGL-H platforms, should introduce no regression. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Groovy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Hirsute) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Impish) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Tags: oem-priority originate-from-1916966 somerville ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Focal) ** No longer affects: linux-oem-5.10 (Ubuntu Groovy) ** No longer affects: linux-oem-5.10 (Ubuntu Hirsute) ** No longer affects: linux-oem-5.10 (Ubuntu Impish) ** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Groovy) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Groovy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-5.10 (Ubuntu Focal) Assignee: (unassigned) => AceLan Kao (acelankao) ** Tags added: oem-priority originate-from-1916966 somerville -- 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/1926579 Title: On TGL platforms screen shows garbage when browsing website by scrolling mouse Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Bug description: [Impact] On Dell TGL platforms screen shows garbage when browsing website by scrolling mouse [Fix] This patch fixes the issue https://patchwork.freedesktop.org/patch/430153/?series=89348=1 [Test] Verified on Dell TGL-H platforms. [Where problems could occur] It disable PSR2 on A0 and B0 TGL-H platforms, should introduce no regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1926579/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907262] Re: raid10: discard leads to corrupted file system
** Changed in: linux (Ubuntu Groovy) Assignee: (unassigned) => Sinclair Willis (yousure1222) -- 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/1907262 Title: raid10: discard leads to corrupted file system Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Invalid Status in linux source package in Xenial: Invalid Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Bug description: Seems to be closely related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578 After updating the Ubuntu 18.04 kernel from 4.15.0-124 to 4.15.0-126 the fstrim command triggered by fstrim.timer causes a severe number of mismatches between two RAID10 component devices. This bug affects several machines in our company with different HW configurations (All using ECC RAM). Both, NVMe and SATA SSDs are affected. How to reproduce: - Create a RAID10 LVM and filesystem on two SSDs mdadm -C -v -l10 -n2 -N "lv-raid" -R /dev/md0 /dev/nvme0n1p2 /dev/nvme1n1p2 pvcreate -ff -y /dev/md0 vgcreate -f -y VolGroup /dev/md0 lvcreate -n root-L 100G -ay -y VolGroup mkfs.ext4 /dev/VolGroup/root mount /dev/VolGroup/root /mnt - Write some data, sync and delete it dd if=/dev/zero of=/mnt/data.raw bs=4K count=1M sync rm /mnt/data.raw - Check the RAID device echo check >/sys/block/md0/md/sync_action - After finishing (see /proc/mdstat), check the mismatch_cnt (should be 0): cat /sys/block/md0/md/mismatch_cnt - Trigger the bug fstrim /mnt - Re-Check the RAID device echo check >/sys/block/md0/md/sync_action - After finishing (see /proc/mdstat), check the mismatch_cnt (probably in the range of N*1): cat /sys/block/md0/md/mismatch_cnt After investigating this issue on several machines it *seems* that the first drive does the trim correctly while the second one goes wild. At least the number and severity of errors found by a USB stick live session fsck.ext4 suggests this. To perform the single drive evaluation the RAID10 was started using a single drive at once: mdadm --assemble /dev/md127 /dev/nvme0n1p2 mdadm --run /dev/md127 fsck.ext4 -n -f /dev/VolGroup/root vgchange -a n /dev/VolGroup mdadm --stop /dev/md127 mdadm --assemble /dev/md127 /dev/nvme1n1p2 mdadm --run /dev/md127 fsck.ext4 -n -f /dev/VolGroup/root When starting these fscks without -n, on the first device it seems the directory structure is OK while on the second device there is only the lost+found folder left. Side-note: Another machine using HWE kernel 5.4.0-56 (after using -53 before) seems to have a quite similar issue. Unfortunately the risk/regression assessment in the aforementioned bug is not complete: the workaround only mitigates the issues during FS creation. This bug on the other hand is triggered by a weekly service (fstrim) causing severe file system corruption. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907262/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926573] Re: TGL-H USB DWC3 ID complement
** Description changed: [Impact] + [Fix] - Cherry pick below series of patches + Cherry pick below series of patches from v5.12-rc2 https://patchwork.kernel.org/project/linux-acpi/cover/20210115094914.88401-1-heikki.kroge...@linux.intel.com/ f08fc2c30e78 usb: dwc3: pci: add support for the Intel Alder Lake-P 73203bde3a95 usb: dwc3: pci: ID for Tiger Lake CPU e492ce9bcaa1 usb: dwc3: pci: Register a software node for the dwc3 platform device e68d0119e328 software node: Introduce device_add_software_node() [Test] [Where problems could occur] ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Groovy) Importance: Undecided Status: New ** No longer affects: linux-oem-5.10 (Ubuntu Groovy) ** Changed in: linux (Ubuntu Groovy) Status: New => In Progress ** Changed in: linux (Ubuntu Groovy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Description changed: [Impact] - + There is a new USB DWC3 ID which is required by TGL-H platform. [Fix] Cherry pick below series of patches from v5.12-rc2 https://patchwork.kernel.org/project/linux-acpi/cover/20210115094914.88401-1-heikki.kroge...@linux.intel.com/ f08fc2c30e78 usb: dwc3: pci: add support for the Intel Alder Lake-P 73203bde3a95 usb: dwc3: pci: ID for Tiger Lake CPU e492ce9bcaa1 usb: dwc3: pci: Register a software node for the dwc3 platform device e68d0119e328 software node: Introduce device_add_software_node() [Test] + Verified on Dell TGL-H gaming platform [Where problems could occur] -- 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/1926573 Title: TGL-H USB DWC3 ID complement Status in linux package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: In Progress Bug description: [Impact] There is a new USB DWC3 ID which is required by TGL-H platform. [Fix] Cherry pick below series of patches from v5.12-rc2 https://patchwork.kernel.org/project/linux-acpi/cover/20210115094914.88401-1-heikki.kroge...@linux.intel.com/ f08fc2c30e78 usb: dwc3: pci: add support for the Intel Alder Lake-P 73203bde3a95 usb: dwc3: pci: ID for Tiger Lake CPU e492ce9bcaa1 usb: dwc3: pci: Register a software node for the dwc3 platform device e68d0119e328 software node: Introduce device_add_software_node() [Test] Verified on Dell TGL-H gaming platform [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926527] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493269/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag:
[Kernel-packages] [Bug 1926527] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493272/+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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag:
[Kernel-packages] [Bug 1926527] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493276/+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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag:
[Kernel-packages] [Bug 1926527] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493267/+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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag:
[Kernel-packages] [Bug 1926527] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493271/+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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308
[Kernel-packages] [Bug 1926527] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493274/+files/RfKill.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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag:
[Kernel-packages] [Bug 1926527] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493277/+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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag:
[Kernel-packages] [Bug 1926527] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493275/+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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag:
[Kernel-packages] [Bug 1926527] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493265/+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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag:
[Kernel-packages] [Bug 1926527] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493270/+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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308
[Kernel-packages] [Bug 1926527] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493268/+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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag:
[Kernel-packages] [Bug 1926527] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493266/+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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag:
[Kernel-packages] [Bug 1926527] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493273/+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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag:
[Kernel-packages] [Bug 1926527] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493264/+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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag:
[Kernel-packages] [Bug 1926527] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493263/+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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag:
[Kernel-packages] [Bug 1926527] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493262/+files/IwConfig.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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag:
[Kernel-packages] [Bug 1926527] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493261/+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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag:
[Kernel-packages] [Bug 1926527] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493260/+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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag:
[Kernel-packages] [Bug 1926527] Re: "Power off" dialog appears when any three keyboard keys are pressed quickly
apport information ** Description changed: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu65 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: pete 1570 F pulseaudio + /dev/snd/controlC2: pete 1570 F pulseaudio + /dev/snd/controlC1: pete 1570 F pulseaudio + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 21.04 + InstallationDate: Installed on 2021-04-28 (0 days ago) + InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) + MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=es_ES.UTF-8 + SHELL=/bin/bash + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 + RelatedPackageVersions: + linux-restricted-modules-5.11.0-16-generic N/A + linux-backports-modules-5.11.0-16-generic N/A + linux-firmware 1.197 + Tags: wayland-session hirsute + Uname: Linux 5.11.0-16-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: 12/30/2020 + dmi.bios.release: 5.19 + dmi.bios.vendor: American Megatrends International, LLC. + dmi.bios.version: G713QR.308 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: G713QR + 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.ec.firmware.release: 0.41 + dmi.modalias:
[Kernel-packages] [Bug 1926573] [NEW] TGL-H USB DWC3 ID complement
Public bug reported: [Impact] [Fix] Cherry pick below series of patches from v5.12-rc2 https://patchwork.kernel.org/project/linux-acpi/cover/20210115094914.88401-1-heikki.kroge...@linux.intel.com/ f08fc2c30e78 usb: dwc3: pci: add support for the Intel Alder Lake-P 73203bde3a95 usb: dwc3: pci: ID for Tiger Lake CPU e492ce9bcaa1 usb: dwc3: pci: Register a software node for the dwc3 platform device e68d0119e328 software node: Introduce device_add_software_node() [Test] [Where problems could occur] ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Hirsute) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Focal) ** No longer affects: linux-oem-5.10 (Ubuntu Hirsute) ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-5.10 (Ubuntu Focal) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => In Progress ** Description changed: [Impact] [Fix] + Cherry pick below series of patches https://patchwork.kernel.org/project/linux-acpi/cover/20210115094914.88401-1-heikki.kroge...@linux.intel.com/ + f08fc2c30e78 usb: dwc3: pci: add support for the Intel Alder Lake-P + 73203bde3a95 usb: dwc3: pci: ID for Tiger Lake CPU + e492ce9bcaa1 usb: dwc3: pci: Register a software node for the dwc3 platform device + e68d0119e328 software node: Introduce device_add_software_node() [Test] [Where problems could occur] -- 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/1926573 Title: TGL-H USB DWC3 ID complement Status in linux package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Bug description: [Impact] [Fix] Cherry pick below series of patches from v5.12-rc2 https://patchwork.kernel.org/project/linux-acpi/cover/20210115094914.88401-1-heikki.kroge...@linux.intel.com/ f08fc2c30e78 usb: dwc3: pci: add support for the Intel Alder Lake-P 73203bde3a95 usb: dwc3: pci: ID for Tiger Lake CPU e492ce9bcaa1 usb: dwc3: pci: Register a software node for the dwc3 platform device e68d0119e328 software node: Introduce device_add_software_node() [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926527] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493255/+files/RfKill.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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR 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/1926527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926527] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493258/+files/acpidump.txt ** 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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR 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/1926527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926527] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493257/+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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR 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/1926527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926527] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493256/+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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR 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/1926527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926527] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493254/+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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR 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/1926527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926527] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493251/+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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR 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/1926527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926527] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493253/+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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR 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/1926527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926527] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493252/+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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR 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/1926527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926527] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493250/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR 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/1926527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926527] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493249/+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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR 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/1926527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926527] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493248/+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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR 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/1926527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926527] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493247/+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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR 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/1926527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926527] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493246/+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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR 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/1926527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926527] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493245/+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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR 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/1926527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926527] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493244/+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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR 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/1926527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926527] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493243/+files/IwConfig.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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR 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/1926527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926527] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493242/+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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR 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/1926527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926527] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493241/+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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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: 12/30/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G713QR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G713QR 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.ec.firmware.release: 0.41 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G713QR_G713QR 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/1926527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926527] Re: "Power off" dialog appears when any three keyboard keys are pressed quickly
apport information ** Tags added: apport-collected hirsute wayland-session ** Description changed: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu65 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: pete 1570 F pulseaudio + /dev/snd/controlC2: pete 1570 F pulseaudio + /dev/snd/controlC1: pete 1570 F pulseaudio + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 21.04 + InstallationDate: Installed on 2021-04-28 (0 days ago) + InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) + MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=es_ES.UTF-8 + SHELL=/bin/bash + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8a599a27-c957-4af8-a0a1-3e3635010326 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 + RelatedPackageVersions: + linux-restricted-modules-5.11.0-16-generic N/A + linux-backports-modules-5.11.0-16-generic N/A + linux-firmware 1.197 + Tags: wayland-session hirsute + Uname: Linux 5.11.0-16-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: 12/30/2020 + dmi.bios.release: 5.19 + dmi.bios.vendor: American Megatrends International, LLC. + dmi.bios.version: G713QR.308 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: G713QR + 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.ec.firmware.release: 0.41 + dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG713QR.308:bd12/30/2020:br5.19:efr0.41:svnASUSTeKCOMPUTERINC.:pnROGStrixG713QR_G713QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG713QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: + dmi.product.family: ROG Strix + dmi.product.name: ROG Strix G713QR_G713QR + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1926527/+attachment/5493240/+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/1926527 Title: "Power off" dialog appears when any three keyboard keys are pressed quickly Status in linux package in Ubuntu: Confirmed Bug description: Fresh 21.04 install on a fresh Asus G713QR-HG016. Gnome desktop, Spanish language. I first noticed the bug while typing, but I can reduce it to this: when three keyboard keys are pressed fast enough (and it doesn't need to be really fast, I'm not a fast typist), the "Power off" dialog appears, announcing that the system is shutting down automatically in 60 seconds. It doesn't happen pressing the same key three times quickly. It doesn't happen either keeping a key pushed. It needs to be at least two different keys. Typing "aaa" really fast doesn't trigger the bug. Typing "off" or "any" does. This happens even when there is no text field in the focus. I can trigger it pushing keys in the desktop. Of course, this renders the system unusable for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1570 F pulseaudio /dev/snd/controlC2: pete 1570 F pulseaudio /dev/snd/controlC1: pete 1570 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. ROG Strix G713QR_G713QR Package: linux (not installed) ProcEnviron: TERM=xterm-256color
[Kernel-packages] [Bug 1924238] Re: Fix no picture from HDMI when it's plugged after boot
Francois, what was the last working 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/1924238 Title: Fix no picture from HDMI when it's plugged after boot Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] On Intel CML desktop, there's no HDMI output when the cable is not connected pre-boot. [Fix] Properly handle lane polarity so the driver can write different values to the register to enable the port. [Test] 1. Boot with DP display. 2. Connect HDMI under GNOME desktop. 3. No picture on HDMI monitor. With the fix applied, the issue is resolved. [Where problems could occur] If the BIOS VBT table is not correct, which did happen in the pase, this fix may break those ports. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924238] Re: Fix no picture from HDMI when it's plugged after boot
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1924238 Title: Fix no picture from HDMI when it's plugged after boot Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] On Intel CML desktop, there's no HDMI output when the cable is not connected pre-boot. [Fix] Properly handle lane polarity so the driver can write different values to the register to enable the port. [Test] 1. Boot with DP display. 2. Connect HDMI under GNOME desktop. 3. No picture on HDMI monitor. With the fix applied, the issue is resolved. [Where problems could occur] If the BIOS VBT table is not correct, which did happen in the pase, this fix may break those ports. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926564] [NEW] An recursive locking in igb and igc drivers
Public bug reported: [Impact] The rtnl_lock() has been called in rtnetlink_rcv_msg(), and then in __dev_open() it calls pm_runtime_resume() to resume devices, and in some devices' resume function(igb_resum,igc_resume) they calls rtnl_lock() again. That leads to a recursive lock. This issue is introduced by below commit since v5.9-rc1 bd869245a3dc net: core: try to runtime-resume detached device in __dev_open [Fix] This commit currently is still under discussion fixes the issue. https://lkml.org/lkml/2021/4/20/123 [Test] Verified on Dell Precision workstations. [Where problems could occur] The patch is pretty straightforward, no problems could occur by this change. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Hirsute) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Impish) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Tags: oem-priority originate-from-1916870 originate-from-1917841 originate-from-1924661 somerville ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Focal) ** No longer affects: linux-oem-5.10 (Ubuntu Hirsute) ** No longer affects: linux-oem-5.10 (Ubuntu Impish) ** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-5.10 (Ubuntu Focal) Assignee: (unassigned) => AceLan Kao (acelankao) ** Description changed: [Impact] + bd869245a3dc net: core: try to runtime-resume detached device in __dev_open [Fix] [Test] [Where problems could occur] ** Tags added: oem-priority originate-from-1924661 somerville ** Tags added: originate-from-1916870 ** Tags added: originate-from-1917841 ** Description changed: [Impact] + The rtnl_lock() has been called in rtnetlink_rcv_msg(), and then in + __dev_open() it calls pm_runtime_resume() to resume devices, and in + some devices' resume function(igb_resum,igc_resume) they calls rtnl_lock() + again. That leads to a recursive lock. + + This issue is introduced by below commit since v5.9-rc1 bd869245a3dc net: core: try to runtime-resume detached device in __dev_open [Fix] + This commit currently is still under discussion fixes the issue. + https://www.spinics.net/lists/netdev/msg736880.html [Test] + Verified on Dell Precision workstations. [Where problems could occur] + The patch is pretty straightforward, no problems could occur by this change. ** Description changed: [Impact] The rtnl_lock() has been called in rtnetlink_rcv_msg(), and then in __dev_open() it calls pm_runtime_resume() to resume devices, and in some devices' resume function(igb_resum,igc_resume) they calls rtnl_lock() again. That leads to a recursive lock. This issue is introduced by below commit since v5.9-rc1 bd869245a3dc net: core: try to runtime-resume detached device in __dev_open [Fix] This commit currently is still under discussion fixes the issue. - https://www.spinics.net/lists/netdev/msg736880.html + https://lkml.org/lkml/2021/4/20/123 [Test] Verified on Dell Precision workstations. [Where problems could occur] The patch is pretty straightforward, no problems could occur by this change. -- 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/1926564 Title: An recursive locking in igb and igc drivers Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Bug description: [Impact]
[Kernel-packages] [Bug 1924238] Re: Fix no picture from HDMI when it's plugged after boot
Hi, [Focal, Thinkpad T480s, 8550u/intel igpu] Unfortunately I suspect this: * Fix no picture from HDMI when it's plugged after boot (LP: #1924238) - drm/i915/display: Handle lane polarity for DDI port in *-1024 OEM 5.10 kernel, that I do use in Focal, did break HDMI hotplug after GNOME is loaded. HDMI works if plugged when at GDM login screen and then in GNOME itself. Additionally, my laptop's sleep seems to be broken (I don't remember if this happens when HDMI is working or not). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1924238 Title: Fix no picture from HDMI when it's plugged after boot Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] On Intel CML desktop, there's no HDMI output when the cable is not connected pre-boot. [Fix] Properly handle lane polarity so the driver can write different values to the register to enable the port. [Test] 1. Boot with DP display. 2. Connect HDMI under GNOME desktop. 3. No picture on HDMI monitor. With the fix applied, the issue is resolved. [Where problems could occur] If the BIOS VBT table is not correct, which did happen in the pase, this fix may break those ports. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924624] Re: After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (gen7, Haswell/Ivy Bridge) a lot of glitches render screen unusable
Is there a plan, roadmap, or experience values for when to expect -51 for focal without using the above mentioned – not recommended – PPA? It’s not that I want to complain; it would be simply helpful for my own planning. -- 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/1924624 Title: After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (gen7, Haswell/Ivy Bridge) a lot of glitches render screen unusable Status in linux package in Ubuntu: Confirmed Status in linux-meta-hwe-5.8 package in Ubuntu: Confirmed Bug description: After upgrading to 5.8.0-49, on a laprtop with intel graphics, graphics was suddenly extremely glitchy. Icons from the desktop flash through the browser, windows top bar gets distorted, all sort of glitches appear, parts of characters are missing in terminal, scrolling is inconsistent and the whole desktop becomes unusable. Under wayland the graphics are a bit more stable, but lots of glitches appear anyway, video reproduction in browser is stuttering and wobbly. Booting with previous kernel 5.8.0-48 seems to fix the issues. 5.8.0-50 is broken as well. this is the result of 'sudo lshw -c video' on my hp Elitebook 8470: *-display description: VGA compatible controller product: 3rd Gen Core processor Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:33 memory:d400-d43f memory:c000-cfff ioport:4000(size=64) memory:c-d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924624/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1920674] Re: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation
There are no entries in the journal for those particular boots I'm afraid. That is, the journal is empty if I boot without "nomodeset" or without "amdgpu.ip_block_mask=0xfdff". There are some very quick boot messages appearing on the screen before it turns all black, but nothing in the log. I rebooted several times to make sure it is not a random behaviour. I even tried "verbose debug" kernel boot parameters with no success. I packed all the logs from that particular date in case I analysed the situation wrong. What can I do now? ** Attachment added: "journal_AMD_A8-7680.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920674/+attachment/5493224/+files/journal_AMD_A8-7680.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/1920674 Title: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation Status in linux package in Ubuntu: Incomplete Bug description: Dear developers, please let me thank you for all your hard work first of all, I'm a big fan of yours! On my desktop PC with AMD A8-7680 APU, I'm facing 2 problems which seem to be connected to the amdgpu kernel module: 1. Amdgpu kernel module loads correctly during boot, but VESA Xorg module is loaded instead of AMDGPU Xorg module during X startup. This results in non-accelerated X and high CPU load. - This situation is always reproducible. - I'm experiencing it with all kernel versions in between 5.4.0-47-generic and 5.4.0-67-generic inclusive. - The situation escalates more with newer kernel version. For 5.8.0-45-generic and 5.11.8-051108-generic, X even does not start and I just get black screen. - I have found a workaround after many days of googling and testing. AMDGPU Xorg module is loaded correctly if and only if I disable AMD ACP by means of the following kernel boot parameter: amdgpu.ip_block_mask=0xfdff - Acceleration is ok with kernels where AMD ACP is disabled by default (linux-image-linuxlite-5.6.0 for example) 2. The 2nd problem I'm facing is with non functioning hibernation after I "fixed" the X acceleration. Hibernation image does not seem to get created, screen goes black, PC freezes but never turns off whenever AMDGPU Xorg module is loaded. Hibernation and subsequent resume is all ok if I disable AMDGPU by means of "nomodeset" and go just with VESA module. - always reproducible but tested only with 5.4.0-67-generic Thank you and best regards, Radek ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-67-generic 5.4.0-67.75 ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94 Uname: Linux 5.4.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: radek 1513 F pulseaudio /dev/snd/controlC0: radek 1513 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Mar 21 15:22:29 2021 HibernationDevice: RESUME=/dev/disk/by-label/SSD_LinuxSwap IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic root=UUID=1cc747ae-f2db-4733-aa04-be8d4bde050a ro ipv6.disable=1 net.ifnames=0 nmi_watchdog=0 resume=LABEL=SSD_LinuxSwap amdgpu.ip_block_mask=0xfdff no_console_suspend RelatedPackageVersions: linux-restricted-modules-5.4.0-67-generic N/A linux-backports-modules-5.4.0-67-generic N/A linux-firmware1.187.10 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.20 dmi.board.name: FM2A68M-HD+ 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.:bvrP5.20:bd02/13/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A68M-HD+: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/1920674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
