[Kernel-packages] [Bug 1928138] Re: Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bisected and workaround attached]
I guess you have some different issue. In my case HP Folio 1040 G1 had this that problem since kernel 4.1 and it was never fixed. But still you can analyze dmesg for anything suspicious (maybe try it with different kernels) Here's a command to output information into dmesg.log in your home folder. sudo dmesg > ~/dmesg.log -- 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/1928138 Title: Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bisected and workaround attached] Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Since kernel 4.1 laptop HP Elitebook Folio 1040 G1 (with Intel i5-4210U) has a pretty serious issue with flickering Symptoms: 1) If I leave mouse cursor for a few seconds, then start moving it, there's a slight flicker (like display brightness changes a bit). There's also some flickering even without user interactions. 2) On the top left corner sometimes appears artifacts. It's relatively easy to see with black window decorations on top of the screen. This one is showed at the attached video bellow 3) With kernel boot options drm.debug=0x1e log_buf_len=4M dmesg shows constant refresh rate changes (even if it's set to 40HZ) [ 29.977378] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 30.456537] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz [ 33.973392] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 35.055923] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz nomodeset boot option eliminates flickering Turns out Display Refresh Rate Switching (DRRS) feature doesn't work correctly here. It was implemented on kernels 4.0...4.1 but on a particular machine flickering started with 4.1. As a workaround I'm attaching a patch which disables DRRS by default and adds module parameter "enable_drrs" to activate it. It's made for kernel 5.12 and should work for older versions as well (tested with 5.11). Until this issue is resolved, please consider adding parameter to disable DRRS. Windows has such option on Intel® Graphics Command Center. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1928138/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943902] Re: NVME errors in confidential vms
** Description changed: See https://canonical.lightning.force.com/lightning/r/Case/5004K09WBzrQAG/view for more info [Impact] Using nvme with swiotlb in confidential VMs can encounter hardware read/write errors. [Fix] - The following upstream patches address this: + The following upstream patches from v5.12 address this: 3d2d861eb03e nvme-pci: set min_align_mask 1f221a0d0dbf swiotlb: respect min_align_mask 16fc3cef33a0 swiotlb: don't modify orig_addr in swiotlb_tbl_sync_single 26a7e094783d swiotlb: refactor swiotlb_tbl_map_single ca10d0f8e530 swiotlb: clean up swiotlb_tbl_unmap_single c32a77fd1878 swiotlb: factor out a nr_slots helper c7fbeca757fe swiotlb: factor out an io_tlb_offset helper b5d7ccb7aac3 swiotlb: add a IO_TLB_SIZE define [Test] Using a confidential VM, with 'swiotlb=force' set on the kernel command line, and an additional nvme device attached: $ sudo mkfs.xfs -f /dev/nvme2n1 meta-data=/dev/nvme2n1 isize=512agcount=4, agsize=131072 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, refl ink=0 data = bsize=4096 blocks=524288, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=2560, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 mkfs.xfs: pwrite failed: Input/output error Note the input/output error The error no longer happens with the fixes applied. [Regression Potential] Low risk as the patches are mostly clean-up and refactor. Regression in swiotlb could cause hardware read/write errors -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1943902 Title: NVME errors in confidential vms Status in linux-gcp package in Ubuntu: New Status in linux-gcp-5.4 package in Ubuntu: New Status in linux-gcp-5.4 source package in Bionic: New Status in linux-gcp source package in Focal: New Bug description: See https://canonical.lightning.force.com/lightning/r/Case/5004K09WBzrQAG/view for more info [Impact] Using nvme with swiotlb in confidential VMs can encounter hardware read/write errors. [Fix] The following upstream patches from v5.12 address this: 3d2d861eb03e nvme-pci: set min_align_mask 1f221a0d0dbf swiotlb: respect min_align_mask 16fc3cef33a0 swiotlb: don't modify orig_addr in swiotlb_tbl_sync_single 26a7e094783d swiotlb: refactor swiotlb_tbl_map_single ca10d0f8e530 swiotlb: clean up swiotlb_tbl_unmap_single c32a77fd1878 swiotlb: factor out a nr_slots helper c7fbeca757fe swiotlb: factor out an io_tlb_offset helper b5d7ccb7aac3 swiotlb: add a IO_TLB_SIZE define [Test] Using a confidential VM, with 'swiotlb=force' set on the kernel command line, and an additional nvme device attached: $ sudo mkfs.xfs -f /dev/nvme2n1 meta-data=/dev/nvme2n1 isize=512agcount=4, agsize=131072 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, refl ink=0 data = bsize=4096 blocks=524288, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=2560, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 mkfs.xfs: pwrite failed: Input/output error Note the input/output error The error no longer happens with the fixes applied. [Regression Potential] Low risk as the patches are mostly clean-up and refactor. Regression in swiotlb could cause hardware read/write errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1943902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943902] Re: NVME errors in confidential vms
** Description changed: See https://canonical.lightning.force.com/lightning/r/Case/5004K09WBzrQAG/view for more info [Impact] - Using nvme hardware that uses swiotlb in confidential VMs can encounter hardware read/write errors. - + Using nvme hardware that uses in confidential VMs can encounter hardware read/write errors. [Fix] The following upstream patches address this: 3d2d861eb03e nvme-pci: set min_align_mask 1f221a0d0dbf swiotlb: respect min_align_mask 16fc3cef33a0 swiotlb: don't modify orig_addr in swiotlb_tbl_sync_single 26a7e094783d swiotlb: refactor swiotlb_tbl_map_single ca10d0f8e530 swiotlb: clean up swiotlb_tbl_unmap_single c32a77fd1878 swiotlb: factor out a nr_slots helper c7fbeca757fe swiotlb: factor out an io_tlb_offset helper b5d7ccb7aac3 swiotlb: add a IO_TLB_SIZE define - [Test] Using a confidential VM, with 'swiotlb=force' set on the kernel command - line, and an additional swiotlb nvme device attached: + line, and an additional nvme device attached: - $ sudo mkfs.xfs -f /dev/nvme2n1 - meta-data=/dev/nvme2n1 isize=512agcount=4, agsize=131072 blks - = sectsz=512 attr=2, projid32bit=1 - = crc=1finobt=1, sparse=0, rmapbt=0, refl - ink=0 - data = bsize=4096 blocks=524288, imaxpct=25 - = sunit=0 swidth=0 blks - naming =version 2 bsize=4096 ascii-ci=0 ftype=1 - log =internal log bsize=4096 blocks=2560, version=2 - = sectsz=512 sunit=0 blks, lazy-count=1 - realtime =none extsz=4096 blocks=0, rtextents=0 + $ sudo mkfs.xfs -f /dev/nvme2n1 + meta-data=/dev/nvme2n1 isize=512agcount=4, agsize=131072 blks + = sectsz=512 attr=2, projid32bit=1 + = crc=1finobt=1, sparse=0, rmapbt=0, refl + ink=0 + data = bsize=4096 blocks=524288, imaxpct=25 + = sunit=0 swidth=0 blks + naming =version 2 bsize=4096 ascii-ci=0 ftype=1 + log =internal log bsize=4096 blocks=2560, version=2 + = sectsz=512 sunit=0 blks, lazy-count=1 + realtime =none extsz=4096 blocks=0, rtextents=0 mkfs.xfs: pwrite failed: Input/output error - Note the input/output error The error no longer happens with the fixes applied. + [Regression Potential] + + Low risk as the patches are mostly clean-up and refactor. + Regression in swiotlb could cause hardware read/write errors ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-oracle (Ubuntu) ** Also affects: linux-gcp (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-gcp-5.4 (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-gcp-5.4 (Ubuntu Focal) ** No longer affects: linux-gcp (Ubuntu Bionic) ** Changed in: linux-gcp (Ubuntu) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gcp-5.4 (Ubuntu) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gcp (Ubuntu Focal) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gcp-5.4 (Ubuntu Bionic) Assignee: (unassigned) => Khaled El Mously (kmously) ** Description changed: See https://canonical.lightning.force.com/lightning/r/Case/5004K09WBzrQAG/view for more info [Impact] - Using nvme hardware that uses in confidential VMs can encounter hardware read/write errors. + Using nvme with swiotlb in confidential VMs can encounter hardware read/write errors. [Fix] The following upstream patches address this: 3d2d861eb03e nvme-pci: set min_align_mask 1f221a0d0dbf swiotlb: respect min_align_mask 16fc3cef33a0 swiotlb: don't modify orig_addr in swiotlb_tbl_sync_single 26a7e094783d swiotlb: refactor swiotlb_tbl_map_single ca10d0f8e530 swiotlb: clean up swiotlb_tbl_unmap_single c32a77fd1878 swiotlb: factor out a nr_slots helper c7fbeca757fe swiotlb: factor out an io_tlb_offset helper b5d7ccb7aac3 swiotlb: add a IO_TLB_SIZE define [Test] Using a confidential VM, with 'swiotlb=force' set on the kernel command line, and an additional nvme device attached: $ sudo mkfs.xfs -f /dev/nvme2n1 meta-data=/dev/nvme2n1 isize=512agcount=4, agsize=131072 blks = sectsz=512 attr=2, projid32bit=1 =
[Kernel-packages] [Bug 1943902] [NEW] NVME errors in confidential vms
Public bug reported: See https://canonical.lightning.force.com/lightning/r/Case/5004K09WBzrQAG/view for more info [Impact] Using nvme hardware that uses swiotlb in confidential VMs can encounter hardware read/write errors. [Fix] The following upstream patches address this: 3d2d861eb03e nvme-pci: set min_align_mask 1f221a0d0dbf swiotlb: respect min_align_mask 16fc3cef33a0 swiotlb: don't modify orig_addr in swiotlb_tbl_sync_single 26a7e094783d swiotlb: refactor swiotlb_tbl_map_single ca10d0f8e530 swiotlb: clean up swiotlb_tbl_unmap_single c32a77fd1878 swiotlb: factor out a nr_slots helper c7fbeca757fe swiotlb: factor out an io_tlb_offset helper b5d7ccb7aac3 swiotlb: add a IO_TLB_SIZE define [Test] Using a confidential VM, with 'swiotlb=force' set on the kernel command line, and an additional swiotlb nvme device attached: $ sudo mkfs.xfs -f /dev/nvme2n1 meta-data=/dev/nvme2n1 isize=512agcount=4, agsize=131072 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, refl ink=0 data = bsize=4096 blocks=524288, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=2560, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 mkfs.xfs: pwrite failed: Input/output error Note the input/output error The error no longer happens with the fixes applied. [Regression Potential] ** Affects: linux-oracle (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1943902 Title: NVME errors in confidential vms Status in linux-oracle package in Ubuntu: New Bug description: See https://canonical.lightning.force.com/lightning/r/Case/5004K09WBzrQAG/view for more info [Impact] Using nvme hardware that uses swiotlb in confidential VMs can encounter hardware read/write errors. [Fix] The following upstream patches address this: 3d2d861eb03e nvme-pci: set min_align_mask 1f221a0d0dbf swiotlb: respect min_align_mask 16fc3cef33a0 swiotlb: don't modify orig_addr in swiotlb_tbl_sync_single 26a7e094783d swiotlb: refactor swiotlb_tbl_map_single ca10d0f8e530 swiotlb: clean up swiotlb_tbl_unmap_single c32a77fd1878 swiotlb: factor out a nr_slots helper c7fbeca757fe swiotlb: factor out an io_tlb_offset helper b5d7ccb7aac3 swiotlb: add a IO_TLB_SIZE define [Test] Using a confidential VM, with 'swiotlb=force' set on the kernel command line, and an additional swiotlb nvme device attached: $ sudo mkfs.xfs -f /dev/nvme2n1 meta-data=/dev/nvme2n1 isize=512agcount=4, agsize=131072 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, refl ink=0 data = bsize=4096 blocks=524288, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=2560, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 mkfs.xfs: pwrite failed: Input/output error Note the input/output error The error no longer happens with the fixes applied. [Regression Potential] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1943902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894046] Re: Bluetooth keyboard has lag
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1894046 Title: Bluetooth keyboard has lag Status in bluez package in Ubuntu: Expired Bug description: For some days, I observe an annoying lag with my Logitech K380 keyboard and Ubuntu 20.04. After a couple of seconds not typing, new keystrokes are registered only after 1–2 seconds lag. From there on, I can type without lag, until the next typing pause. I seems that the Bluetooth component switches Bluetooth in some sort of hibernate after a couple of seconds of not typing, and then it needs 1–2 seconds to wake up again and process the keystrokes. No keys are missing – they just arrive with a lag. Probably the keyboard buffers them. Important: If I listen to music with a Bluetooth headset, I can type without *any* problems because the Bluetooth module remains awake due to the music transmission. The keyboard does not exhibit this issues at my Android tablet. Furthermore, I am sometimes lucky can work with the keyboard without any lag (and without music). In the BIOS settings of the computer, I do not find anything Bluetooth-related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1894046/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942684] Re: Kernel 5.14.X / 5.13.14 fails to boot
Just to confirm, Ubuntu's mainline 5.14.5 kernel does boot successfully on my machine with CONFIG_UBSAN_TRAP not set. -- 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/1942684 Title: Kernel 5.14.X / 5.13.14 fails to boot Status in linux package in Ubuntu: Confirmed Bug description: I have been testing kernels 5.14.0 and 5.14.1 since their release on https://kernel.ubuntu.com/~kernel-ppa/mainline/ and my machine fails to boot with either one. However, I am able to boot just fine with 5.14.0-rc7. journalctl -b output attached with 5.14.1 Motherboard: MSI X570 Tomahawk CPU: AMD 5900X GPU: AsusTek 6800XT OS: Hirsute 21.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-04 (62 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: wayland-session hirsute Uname: Linux 5.14.0-051400rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942684/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932966] Re: kvm_unit_tests: emulator test fails on 4.4 / 4.15 kernel, timeout
Test passed with 4.15 kernel, verified on X-Azure
4.15.0-1124.137~16.04.1 and B-4.15 4.15.0-157.164
** Tags removed: verification-needed-bionic
** Tags added: verificationeon-d-bionic
** Tags removed: verificationeon-d-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1932966
Title:
kvm_unit_tests: emulator test fails on 4.4 / 4.15 kernel, timeout
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Confirmed
Status in linux source package in Bionic:
Fix Committed
Bug description:
[Impact]
Our Bionic 4.15 kernel lacks of movups/movupd emulation support.
With the following commit added into the emulator test in
ubuntu_kvm_unit_tests:
commit 8726f9771911d6749dbd36ab2fc70f0f25e2b1a9
Author: Jacob Xu
Date: Wed Apr 21 16:12:57 2021 -0700
x86: add movups/movupd sse testcases to emulator.c
Here we add movups/movupd tests corresponding to functionality
introduced in commit 29916968c486 ("kvm: Add emulation for
movups/movupd").
Signed-off-by: Jacob Xu
Message-Id: <20210421231258.2583654-1-jacob...@google.com>
Signed-off-by: Paolo Bonzini
It will cause the emulator test in ubuntu_kvm_unit_tests fail with timeout:
...
PASS: movdqu (read)
PASS: movdqu (write)
PASS: movaps (read)
PASS: movaps (write)
PASS: movapd (read)
PASS: movapd (write)
KVM internal error. Suberror: 1
emulation failure
RAX=000a RBX=e000 RCX=03fd
RDX=03f8
RSI=00419991 RDI=00419991 RBP=0051b490
RSP=0051b470
R8 =000a R9 =03f8 R10=000d
R11=
R12=e000 R13= R14=d000
R15=
RIP=00400a1f RFL=00010006 [-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0010 00c09300 DPL=0 DS [-WA]
CS =0008 00a09b00 DPL=0 CS64 [-RA]
SS =0010 00c09300 DPL=0 DS [-WA]
DS =0010 00c09300 DPL=0 DS [-WA]
FS =0010 00c09300 DPL=0 DS [-WA]
GS =0010 0051a510 00c09300 DPL=0 DS [-WA]
LDT= 8200 DPL=0 LDT
TR =0080 0041207a 8b00 DPL=0 TSS64-busy
GDT= 0041100a 106f
IDT= 0041 0fff
CR0=80010011 CR2= CR3=01007000 CR4=0220
DR0= DR1= DR2=
DR3=
DR6=0ff0 DR7=0400
EFER=0500
Code=00 c7 45 e8 03 00 00 00 c7 45 ec 04 00 00 00 66 0f 6f 45 e0 <0f> 11 03
48 89 de 48 8d 7d e0 e8 e5 f9 ff ff 0f b6 f8 be a1 8f 41 00 b8 00 00 00 00 e8 07
qemu-system-x86_64: terminating on signal 15 from pid 15758 (timeout)
FAIL emulator (timeout; duration=90s)
[Fix]
* 29916968c48691 kvm: Add emulation for movups/movupd
This patch can be cherry-picked into Bionic.
It can fix our test failure plus, as mentioned in the commit message,
emulation failures with openbsd as guest and with Windows 10 with
intel HD graphics pass through.
[Test]
Test kernel can be found here:
https://people.canonical.com/~phlin/kernel/lp-1932966-kvm-emulator/
Run the emulator test from ubuntu_kvm_unit_tests, with this patch
applied it will pass without any issue:
...
PASS: movdqu (read)
PASS: movdqu (write)
PASS: movaps (read)
PASS: movaps (write)
PASS: movapd (read)
PASS: movapd (write)
PASS: movups (read)
PASS: movups (write)
PASS: movupd (read)
PASS: movupd (write)
PASS: movups unaligned
PASS: movupd unaligned
PASS: unaligned movaps exception
PASS: movups unaligned crosspage
PASS: movups crosspage exception
PASS: movq (mmx, read)
PASS: movq (mmx, write)
PASS: movb $imm, 0(%rip)
PASS: shld (cl)
PASS: shrd (cl)
PASS: mov null, %ss
PASS: mov null, %ss (with ss.rpl != cpl)
PASS: Test ret/iret with a nullified segment
PASS: ltr
PASS: cmovnel
SKIP: skipping register-only tests, use kvm.force_emulation_prefix=1 to
enable
PASS: push16
PASS: cross-page mmio read
PASS: cross-page mmio write
PASS: string_io_mmio
PASS: jump to non-canonical address
SKIP: illegal movbe
SUMMARY: 135 tests, 2 skipped
PASS emulator (135 tests, 2 skipped)
[Where problems could occur]
I didn't see any other patch that claims to be a fix of this one in
the upstream tree. The problem I think of for the moment is that we
might see other failures when using this in the future.
[Original Bug Report]
Found this on B/KVM, current
[Kernel-packages] [Bug 1942684] Re: Kernel 5.14.X / 5.13.14 fails to boot
I also can't boot the mainline 5.14-4 or 5.14-5 kernels on a Lenovo S7 (AMD 5800H and NVIDIA GPU) - it goes to a blank screen when trying to boot graphics and freezes - I can't open a tty and have to hard reset the system. It looks like I have the laptop in the same mode as the other posters, ie hybrid/dynamic graphics mode using the amdgpu driver for the laptop screen. I can't see any relevant errors in the output "journalctl -b -1" for the failed boot - I think the hang occurs before it has a chance to log them. However, when booting the stock Ubuntu 21.10 5.13.0-16 kernel I do see some nvidia_drm RIP errors in the log in nv_drm_master_set(). Presumably these errors in combination with CONFIG_UBSAN_TRAP are causing the hang? The documentation says that in order to save around 5% of the kernel size, CONFIG_UBSAN_TRAP "reduces the kernel size overhead but turns all warnings (including potentially harmless conditions) into full exceptions that abort the running kernel code (regardless of context, locks held, etc), which may destabilize the system." It seems like a pretty aggressive config option to set! -- 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/1942684 Title: Kernel 5.14.X / 5.13.14 fails to boot Status in linux package in Ubuntu: Confirmed Bug description: I have been testing kernels 5.14.0 and 5.14.1 since their release on https://kernel.ubuntu.com/~kernel-ppa/mainline/ and my machine fails to boot with either one. However, I am able to boot just fine with 5.14.0-rc7. journalctl -b output attached with 5.14.1 Motherboard: MSI X570 Tomahawk CPU: AMD 5900X GPU: AsusTek 6800XT OS: Hirsute 21.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-04 (62 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: wayland-session hirsute Uname: Linux 5.14.0-051400rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942684/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943469] Re: sleep mode
I'm not sure if that is relevant. I was recommending you unplug any keyboards and mice etc but it looks like you might not have any such things plugged in... Do you have any Bluetooth devices configured? If so then please try disabling Bluetooth on the laptop before entering sleep mode. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1943469 Title: sleep mode Status in linux-hwe-5.11 package in Ubuntu: Incomplete Bug description: computer "wakes up" from sleep mode after 1 second no matter if i wait the given time for it to sleep, or if i put it to sleep with terminal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 13 18:56:14 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Integrated Graphics Controller [8086:5a84] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Celeron N3350/Pentium N4200/Atom E3900 Series Integrated Graphics Controller [1043:16a0] Subsystem: ASUSTeK Computer Inc. GK107M [GeForce 810M] [1043:137e] InstallationDate: Installed on 2021-07-30 (44 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 13d3:5a01 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 002: ID 0bda:b721 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X541NC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=264f931b-e96b-44e9-a13d-bf5c3236a567 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X541NC.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X541NC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX541NC.307:bd06/19/2017:br5.12:svnASUSTeKCOMPUTERINC.:pnX541NC:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnX541NC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X541NC dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1943469/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940285] Re: [Teclast F7] Laptop screen flickering on kernels above 5.4 (not included)
Please download both: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.14.5/amd64/linux- image- unsigned-5.14.5-051405-generic_5.14.5-051405.202109161131_amd64.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.14.5/amd64/linux- modules-5.14.5-051405-generic_5.14.5-051405.202109161131_amd64.deb and then install them in a single command: sudo dpkg -i linux*.deb and reboot. Then verify the new kernel version is running: uname -a and tell us if the problem persists. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1940285 Title: [Teclast F7] Laptop screen flickering on kernels above 5.4 (not included) Status in linux package in Ubuntu: Incomplete Bug description: Recently, I installed Ubuntu 21.04 on my laptop and I was having the same problem I had like with others distros such as Fedora; for some reason, the screen just ramdonly and briefly turns off, (more like a flickering) and it also "autoregulates" a the brightness, just a little bit down and then a little bit up. I noticed I don't have this problem on Linux Mint, and I also noticed that going back to Kernel 5.8 on either Ubuntu 21.04 or 20.04.2 this problem stops. I have been using Mainline ( https://github.com/bkw777/mainline ) to install previous kernels (5.8 and 5.4 wok just fine, but anything above this problem comes again). Thanks so much beforehand. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940285/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939966] Re: Random system stops
Comment #19 seems to have a bunch of: kernel: rtw_8822ce :03:00.0: pci bus timeout, check dma status which can also be seen in the log of comment #17. And that message relates to: Realtek Semiconductor Co., Ltd. RTL8822CE 802.11ac PCIe Wireless Network Adapter It's unclear to me whether that card is causing the problems or just a victim of some deeper bus/motherboard issue. ** Changed in: linux-hwe-5.11 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939966 Title: Random system stops Status in linux-hwe-5.11 package in Ubuntu: New Bug description: Every once in a while (it's been three times this week), the entire system will just stop. There's still electricity running. The keyboard is lit up, and the monitor is black (electricity-running black, and not shutdown-black). There's no picture and no sound. Just immediately before it does, I know it's about to happen because whatever audio is playing at the time will begin repeating, and then the computer goes down. I don't actually know if it's an Xorg problem. It just sounded like the closest possibility, based on the way the computer actually behaves. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.57.02 Tue Jul 13 16:14:05 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Aug 14 19:34:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1e21] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21] InstallationDate: Installed on 2021-03-20 (147 days ago) InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506IV.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506IV 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: 3.9 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:br5.16:efr3.9:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming FA506IV dmi.product.name: TUF Gaming FA506IV_TUF506IV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gcp-4.15/4.15.0.1109.128)
All autopkgtests for the newly accepted linux-meta-gcp-4.15 (4.15.0.1109.128) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxc/3.0.3-0ubuntu1~18.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-gcp-4.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
@2021yunotcompile kumk has been used workaround way only on system with libc6 <2.33... but i changed this in just updated kumk version, now is used if kernel package "need" higher libc6 than is installed... -- 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/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS Status in linux package in Ubuntu: Confirmed Bug description: Hi all, The Mainline wiki states that the mainline kernels are built with the previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are being built with Hirsuite 21.04, and before that Groovy? If this is intentional, then the wiki should be updated to reflect the change in policy. From https://wiki.ubuntu.com/Kernel/MainlineBuilds Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On my Focal LTS system I have GCC 9.3.0. The Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The *linux-headers-generic* packages have unmet dependencies on 20.04 LTS. I could install Groovy built kernels fine, but the Hirsuite ones built with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels can't be installed on Focal (libc 2.31). Thanks, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941657] Re: Server boot failure after adding checks for ACPI IRQ override
** Tags removed: verification-needed-focal verification-needed-hirsute
** Tags added: verification-done-focal verification-done-hirsute
--
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/1941657
Title:
Server boot failure after adding checks for ACPI IRQ override
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Focal:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Bug description:
SRU Justification:
Impact:
The commit 0ec4e55e9f57 ("ACPI: resources: Add checks for ACPI IRQ
override") introduces regression on some platforms, at least it makes
the UART can't get correct irq setting on two different platforms, and
it makes the kernel can't bootup on these two platforms.
discussion regarding the regression:
https://bugzilla.kernel.org/show_bug.cgi?id=213031#c32
Fix: Revert "ACPI: resources: Add checks for ACPI IRQ override"
Risk: Reverting this patch will keep LP#1909814 ("Keyboard not working")
unfixed.
https://launchpad.net/bugs/1909814
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943817] Re: Realtek 8852 wifi kernel module is missing
** Description changed: Hi, Just got a Thinkpad with Realtek 8852a wifi card. I installed Impish daily (kernel 5.13). Not recognized. - The driver is natively present in firmware folder, /rtw89/rtw8852a_fw.bin . + The firmware is natively present in firmware folder, /rtw89/rtw8852a_fw.bin . But the kernel module is not loaded and in fact no module is loadable! sudo modprobe rtw8[completion] does not return this wifi card's module. So I did run for: https://github.com/lwfinger/rtw89 and it does work but needs to be done for each kernel upgrade... Note that Bluetooth was natively ok. I tried 5.14 Ubuntu kernel from unstable ppa but same issue. lspci 03:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device 8852 - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC2: fthx 2333 F pulseaudio - /dev/snd/controlC1: fthx 2333 F pulseaudio - /dev/snd/controlC0: fthx 2333 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC2: fthx 2333 F pulseaudio + /dev/snd/controlC1: fthx 2333 F pulseaudio + /dev/snd/controlC0: fthx 2333 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-09-15 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) MachineType: LENOVO 21AVFR Package: linux (not installed) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=fr_FR.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash ProcFB: 0 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.14.0-9-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9.9-generic 5.14.1 RelatedPackageVersions: - linux-restricted-modules-5.14.0-9-generic N/A - linux-backports-modules-5.14.0-9-generic N/A - linux-firmware1.199 + linux-restricted-modules-5.14.0-9-generic N/A + linux-backports-modules-5.14.0-9-generic N/A + linux-firmware1.199 Tags: impish Uname: Linux 5.14.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2021 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET39W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 21AVFR dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1MET39W(1.09):bd06/21/2021:br1.9:efr1.9:svnLENOVO:pn21AVFR:pvrThinkPadP14sGen2a:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:rvnLENOVO:rn21AVFR:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21AVFR dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO -- 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/1943817 Title: Realtek 8852 wifi kernel module is missing Status in linux package in Ubuntu: Confirmed Bug description: Hi, Just got a Thinkpad with Realtek 8852a wifi card. I installed Impish daily (kernel 5.13). Not recognized. The firmware is natively present in firmware folder, /rtw89/rtw8852a_fw.bin . But the kernel module is not loaded and in fact no module is loadable! sudo modprobe rtw8[completion] does not return this wifi card's module. So I did run for: https://github.com/lwfinger/rtw89 and it does work but needs to be done for each kernel upgrade... Note that Bluetooth was natively ok. I tried 5.14 Ubuntu kernel from unstable ppa but same issue. lspci 03:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device 8852 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: fthx 2333 F pulseaudio /dev/snd/controlC1: fthx 2333 F pulseaudio /dev/snd/controlC0: fthx 2333 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-09-15 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) MachineType: LENOVO 21AVFR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8
[Kernel-packages] [Bug 1933496] Comment bridged from LTC Bugzilla
--- Comment From fre...@de.ibm.com 2021-09-16 03:52 EDT--- downloaded and installed the kernel packages. Here is the uname output: uname -a Linux t8314009.lnxne.boe 5.13.0-14-generic #14~lp1933496-Ubuntu SMP Mon Aug 16 10:53:26 UTC 2021 s390x s390x s390x GNU/Linux Verified with some hand-triggered tests that the feature is there and works as expected. All good. -- 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/1933496 Title: [21.10 FEAT] zcrypt DD: AP bus and zcrypt device driver uevent extensions - Kernel Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Provide uevents for the following AP bus events: online state change config state change add crypto mode all uevents Feature will be made available with kernel 5.14. Git-commit or backport will be provided on top of 5.13. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1933496/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943160] Please test proposed package
Hello Shengyao, or anyone else affected,
Accepted nvidia-settings into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/nvidia-
settings/470.57.01-0ubuntu0.20.04.2 in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1943160
Title:
[SRU] It will take about 90+ seconds to open the 'Nvidia settings' app
when 'Power Saving mode' running.
Status in OEM Priority Project:
In Progress
Status in nvidia-settings package in Ubuntu:
Fix Released
Status in nvidia-settings source package in Focal:
Fix Committed
Status in nvidia-settings source package in Hirsute:
Fix Committed
Bug description:
[Impact]
On some I+N configs, It will take about 90+ seconds to open the 'Nvidia
settings' window when 'Power Saving mode' running.
[Fix]
do not read config file if Nvidia driver did not loaded:
change nvidia-settings/src/nvidia-settings.c
if (!op->no_load) {
ret = nv_read_config_file(op, op->config, op->ctrl_display,
p, , );
to
if (!op->no_load && systems.n != 0) {
ret = nv_read_config_file(op, op->config, op->ctrl_display,
p, , );
[Test]
1. Install Ubuntu image.
2. Boot and login the system.
3. Open 'Nvidia Settings' app
4. Select the prime is 'Power saving' mode
5. Reboot system and login
6. Open 'Nvidia Settings' app
7. Verify the result
[Where problems will occur]
the "systems.n" gets from
NvCtrlConnectToSystem(op->ctrl_display, );
If there is a possibility that systems.n is zero and we still need to read
nvidia config file, then it will be a problem. I tried and cannot find a
situation like that.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1943160/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943160] Re: [SRU] It will take about 90+ seconds to open the 'Nvidia settings' app when 'Power Saving mode' running.
Hello Shengyao, or anyone else affected,
Accepted nvidia-settings into hirsute-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/nvidia-
settings/470.57.01-0ubuntu0.21.04.2 in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. In either case, without details of your
testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: nvidia-settings (Ubuntu Hirsute)
Status: New => Fix Committed
** Tags added: verification-needed verification-needed-hirsute
** Changed in: nvidia-settings (Ubuntu Focal)
Status: In Progress => Fix Committed
** Tags added: verification-needed-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1943160
Title:
[SRU] It will take about 90+ seconds to open the 'Nvidia settings' app
when 'Power Saving mode' running.
Status in OEM Priority Project:
In Progress
Status in nvidia-settings package in Ubuntu:
Fix Released
Status in nvidia-settings source package in Focal:
Fix Committed
Status in nvidia-settings source package in Hirsute:
Fix Committed
Bug description:
[Impact]
On some I+N configs, It will take about 90+ seconds to open the 'Nvidia
settings' window when 'Power Saving mode' running.
[Fix]
do not read config file if Nvidia driver did not loaded:
change nvidia-settings/src/nvidia-settings.c
if (!op->no_load) {
ret = nv_read_config_file(op, op->config, op->ctrl_display,
p, , );
to
if (!op->no_load && systems.n != 0) {
ret = nv_read_config_file(op, op->config, op->ctrl_display,
p, , );
[Test]
1. Install Ubuntu image.
2. Boot and login the system.
3. Open 'Nvidia Settings' app
4. Select the prime is 'Power saving' mode
5. Reboot system and login
6. Open 'Nvidia Settings' app
7. Verify the result
[Where problems will occur]
the "systems.n" gets from
NvCtrlConnectToSystem(op->ctrl_display, );
If there is a possibility that systems.n is zero and we still need to read
nvidia config file, then it will be a problem. I tried and cannot find a
situation like that.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1943160/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943879] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1943879/+attachment/5525754/+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/1943879 Title: NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out Status in linux package in Ubuntu: Incomplete Bug description: I am running ubuntu Focal version with following kernel and NIC and noticed where strange error in kernel logs and my nic went down, does any one know about this? # uname -a Linux ostack-phx-comp-gen-1-27.v1v0x.net 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64x # lspci | grep -i eth 06:00.0 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) 06:00.1 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) [Thu Sep 16 01:43:51 2021] [ cut here ] [Thu Sep 16 01:43:51 2021] NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out [Thu Sep 16 01:43:51 2021] WARNING: CPU: 11 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Modules linked in: nf_conntrack_netlink ebt_arp nft_compat nf_tables_set nft_meta_bridgel [Thu Sep 16 01:43:51 2021] ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_mi [Thu Sep 16 01:43:51 2021] CPU: 11 PID: 0 Comm: swapper/11 Not tainted 5.4.0-42-generic #46-Ubuntu [Thu Sep 16 01:43:51 2021] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017 [Thu Sep 16 01:43:51 2021] RIP: 0010:dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 1f f5 e7 00 01 e8 8d bb fa ff 44 89 e9 4c 89 fe 47 [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d466b4e30 EFLAGS: 00010286 [Thu Sep 16 01:43:51 2021] RAX: RBX: 9373ef57cec0 RCX: 083f [Thu Sep 16 01:43:51 2021] RDX: RSI: 00f6 RDI: 083f [Thu Sep 16 01:43:51 2021] RBP: b92d466b4e60 R08: 937bdf8d78c8 R09: 0004 [Thu Sep 16 01:43:51 2021] R10: R11: 0001 R12: 0040 [Thu Sep 16 01:43:51 2021] R13: 0022 R14: 9373ef580480 R15: 9373ef58 [Thu Sep 16 01:43:51 2021] FS: () GS:937bdf8c() knlGS: [Thu Sep 16 01:43:51 2021] CS: 0010 DS: ES: CR0: 80050033 [Thu Sep 16 01:43:51 2021] CR2: 7f3697ec19dc CR3: 00103ce0a001 CR4: 001626e0 [Thu Sep 16 01:43:51 2021] Call Trace: [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] ? pfifo_fast_enqueue+0x150/0x150 [Thu Sep 16 01:43:51 2021] call_timer_fn+0x32/0x130 [Thu Sep 16 01:43:51 2021] __run_timers.part.0+0x180/0x280 [Thu Sep 16 01:43:51 2021] ? tick_sched_handle+0x33/0x60 [Thu Sep 16 01:43:51 2021] ? tick_sched_timer+0x3d/0x80 [Thu Sep 16 01:43:51 2021] ? ktime_get+0x3e/0xa0 [Thu Sep 16 01:43:51 2021] run_timer_softirq+0x2a/0x50 [Thu Sep 16 01:43:51 2021] __do_softirq+0xe1/0x2d6 [Thu Sep 16 01:43:51 2021] ? hrtimer_interrupt+0x13b/0x220 [Thu Sep 16 01:43:51 2021] irq_exit+0xae/0xb0 [Thu Sep 16 01:43:51 2021] smp_apic_timer_interrupt+0x7b/0x140 [Thu Sep 16 01:43:51 2021] apic_timer_interrupt+0xf/0x20 [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [Thu Sep 16 01:43:51 2021] Code: ff e8 bf 08 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 0d [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d4634fe38 EFLAGS: 0246 ORIG_RAX: ff13 [Thu Sep 16 01:43:51 2021] RAX: 937bdf8ead00 RBX: 8d159c00 RCX: 001f [Thu Sep 16 01:43:51 2021] RDX: RSI: 3342629e RDI: [Thu Sep 16 01:43:51 2021] RBP: b92d4634fe78 R08: 0011dc129ea2a1f1 R09: 0011dc17357faf00 [Thu Sep 16 01:43:51 2021] R10: 937bdf8e9a00 R11: 937bdf8e99e0 R12: d9253fac20a8 [Thu Sep 16 01:43:51 2021] R13: 0004 R14: 0004 R15: d9253fac20a8 [Thu Sep 16 01:43:51 2021] ? cpuidle_enter_state+0xa1/0x450 [Thu Sep 16 01:43:51 2021] cpuidle_enter+0x2e/0x40 [Thu Sep 16 01:43:51 2021] call_cpuidle+0x23/0x40 [Thu Sep 16 01:43:51 2021] do_idle+0x1dd/0x270 [Thu Sep 16 01:43:51 2021] cpu_startup_entry+0x20/0x30 [Thu Sep 16 01:43:51 2021] start_secondary+0x167/0x1c0 [Thu Sep 16 01:43:51 2021] secondary_startup_64+0xa4/0xb0 [Thu Sep 16 01:43:51 2021] ---[ end trace cb80e9f61341ace0 ]--- [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: initiating reset due to tx timeout [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: Reset adapter [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: TXDCTL.ENABLE for one or more queues
[Kernel-packages] [Bug 1943879] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1943879/+attachment/5525750/+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/1943879 Title: NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out Status in linux package in Ubuntu: Incomplete Bug description: I am running ubuntu Focal version with following kernel and NIC and noticed where strange error in kernel logs and my nic went down, does any one know about this? # uname -a Linux ostack-phx-comp-gen-1-27.v1v0x.net 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64x # lspci | grep -i eth 06:00.0 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) 06:00.1 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) [Thu Sep 16 01:43:51 2021] [ cut here ] [Thu Sep 16 01:43:51 2021] NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out [Thu Sep 16 01:43:51 2021] WARNING: CPU: 11 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Modules linked in: nf_conntrack_netlink ebt_arp nft_compat nf_tables_set nft_meta_bridgel [Thu Sep 16 01:43:51 2021] ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_mi [Thu Sep 16 01:43:51 2021] CPU: 11 PID: 0 Comm: swapper/11 Not tainted 5.4.0-42-generic #46-Ubuntu [Thu Sep 16 01:43:51 2021] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017 [Thu Sep 16 01:43:51 2021] RIP: 0010:dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 1f f5 e7 00 01 e8 8d bb fa ff 44 89 e9 4c 89 fe 47 [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d466b4e30 EFLAGS: 00010286 [Thu Sep 16 01:43:51 2021] RAX: RBX: 9373ef57cec0 RCX: 083f [Thu Sep 16 01:43:51 2021] RDX: RSI: 00f6 RDI: 083f [Thu Sep 16 01:43:51 2021] RBP: b92d466b4e60 R08: 937bdf8d78c8 R09: 0004 [Thu Sep 16 01:43:51 2021] R10: R11: 0001 R12: 0040 [Thu Sep 16 01:43:51 2021] R13: 0022 R14: 9373ef580480 R15: 9373ef58 [Thu Sep 16 01:43:51 2021] FS: () GS:937bdf8c() knlGS: [Thu Sep 16 01:43:51 2021] CS: 0010 DS: ES: CR0: 80050033 [Thu Sep 16 01:43:51 2021] CR2: 7f3697ec19dc CR3: 00103ce0a001 CR4: 001626e0 [Thu Sep 16 01:43:51 2021] Call Trace: [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] ? pfifo_fast_enqueue+0x150/0x150 [Thu Sep 16 01:43:51 2021] call_timer_fn+0x32/0x130 [Thu Sep 16 01:43:51 2021] __run_timers.part.0+0x180/0x280 [Thu Sep 16 01:43:51 2021] ? tick_sched_handle+0x33/0x60 [Thu Sep 16 01:43:51 2021] ? tick_sched_timer+0x3d/0x80 [Thu Sep 16 01:43:51 2021] ? ktime_get+0x3e/0xa0 [Thu Sep 16 01:43:51 2021] run_timer_softirq+0x2a/0x50 [Thu Sep 16 01:43:51 2021] __do_softirq+0xe1/0x2d6 [Thu Sep 16 01:43:51 2021] ? hrtimer_interrupt+0x13b/0x220 [Thu Sep 16 01:43:51 2021] irq_exit+0xae/0xb0 [Thu Sep 16 01:43:51 2021] smp_apic_timer_interrupt+0x7b/0x140 [Thu Sep 16 01:43:51 2021] apic_timer_interrupt+0xf/0x20 [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [Thu Sep 16 01:43:51 2021] Code: ff e8 bf 08 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 0d [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d4634fe38 EFLAGS: 0246 ORIG_RAX: ff13 [Thu Sep 16 01:43:51 2021] RAX: 937bdf8ead00 RBX: 8d159c00 RCX: 001f [Thu Sep 16 01:43:51 2021] RDX: RSI: 3342629e RDI: [Thu Sep 16 01:43:51 2021] RBP: b92d4634fe78 R08: 0011dc129ea2a1f1 R09: 0011dc17357faf00 [Thu Sep 16 01:43:51 2021] R10: 937bdf8e9a00 R11: 937bdf8e99e0 R12: d9253fac20a8 [Thu Sep 16 01:43:51 2021] R13: 0004 R14: 0004 R15: d9253fac20a8 [Thu Sep 16 01:43:51 2021] ? cpuidle_enter_state+0xa1/0x450 [Thu Sep 16 01:43:51 2021] cpuidle_enter+0x2e/0x40 [Thu Sep 16 01:43:51 2021] call_cpuidle+0x23/0x40 [Thu Sep 16 01:43:51 2021] do_idle+0x1dd/0x270 [Thu Sep 16 01:43:51 2021] cpu_startup_entry+0x20/0x30 [Thu Sep 16 01:43:51 2021] start_secondary+0x167/0x1c0 [Thu Sep 16 01:43:51 2021] secondary_startup_64+0xa4/0xb0 [Thu Sep 16 01:43:51 2021] ---[ end trace cb80e9f61341ace0 ]--- [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: initiating reset due to tx timeout [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: Reset adapter [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: TXDCTL.ENABLE for one
[Kernel-packages] [Bug 1943879] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1943879/+attachment/5525755/+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/1943879 Title: NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out Status in linux package in Ubuntu: Incomplete Bug description: I am running ubuntu Focal version with following kernel and NIC and noticed where strange error in kernel logs and my nic went down, does any one know about this? # uname -a Linux ostack-phx-comp-gen-1-27.v1v0x.net 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64x # lspci | grep -i eth 06:00.0 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) 06:00.1 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) [Thu Sep 16 01:43:51 2021] [ cut here ] [Thu Sep 16 01:43:51 2021] NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out [Thu Sep 16 01:43:51 2021] WARNING: CPU: 11 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Modules linked in: nf_conntrack_netlink ebt_arp nft_compat nf_tables_set nft_meta_bridgel [Thu Sep 16 01:43:51 2021] ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_mi [Thu Sep 16 01:43:51 2021] CPU: 11 PID: 0 Comm: swapper/11 Not tainted 5.4.0-42-generic #46-Ubuntu [Thu Sep 16 01:43:51 2021] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017 [Thu Sep 16 01:43:51 2021] RIP: 0010:dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 1f f5 e7 00 01 e8 8d bb fa ff 44 89 e9 4c 89 fe 47 [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d466b4e30 EFLAGS: 00010286 [Thu Sep 16 01:43:51 2021] RAX: RBX: 9373ef57cec0 RCX: 083f [Thu Sep 16 01:43:51 2021] RDX: RSI: 00f6 RDI: 083f [Thu Sep 16 01:43:51 2021] RBP: b92d466b4e60 R08: 937bdf8d78c8 R09: 0004 [Thu Sep 16 01:43:51 2021] R10: R11: 0001 R12: 0040 [Thu Sep 16 01:43:51 2021] R13: 0022 R14: 9373ef580480 R15: 9373ef58 [Thu Sep 16 01:43:51 2021] FS: () GS:937bdf8c() knlGS: [Thu Sep 16 01:43:51 2021] CS: 0010 DS: ES: CR0: 80050033 [Thu Sep 16 01:43:51 2021] CR2: 7f3697ec19dc CR3: 00103ce0a001 CR4: 001626e0 [Thu Sep 16 01:43:51 2021] Call Trace: [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] ? pfifo_fast_enqueue+0x150/0x150 [Thu Sep 16 01:43:51 2021] call_timer_fn+0x32/0x130 [Thu Sep 16 01:43:51 2021] __run_timers.part.0+0x180/0x280 [Thu Sep 16 01:43:51 2021] ? tick_sched_handle+0x33/0x60 [Thu Sep 16 01:43:51 2021] ? tick_sched_timer+0x3d/0x80 [Thu Sep 16 01:43:51 2021] ? ktime_get+0x3e/0xa0 [Thu Sep 16 01:43:51 2021] run_timer_softirq+0x2a/0x50 [Thu Sep 16 01:43:51 2021] __do_softirq+0xe1/0x2d6 [Thu Sep 16 01:43:51 2021] ? hrtimer_interrupt+0x13b/0x220 [Thu Sep 16 01:43:51 2021] irq_exit+0xae/0xb0 [Thu Sep 16 01:43:51 2021] smp_apic_timer_interrupt+0x7b/0x140 [Thu Sep 16 01:43:51 2021] apic_timer_interrupt+0xf/0x20 [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [Thu Sep 16 01:43:51 2021] Code: ff e8 bf 08 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 0d [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d4634fe38 EFLAGS: 0246 ORIG_RAX: ff13 [Thu Sep 16 01:43:51 2021] RAX: 937bdf8ead00 RBX: 8d159c00 RCX: 001f [Thu Sep 16 01:43:51 2021] RDX: RSI: 3342629e RDI: [Thu Sep 16 01:43:51 2021] RBP: b92d4634fe78 R08: 0011dc129ea2a1f1 R09: 0011dc17357faf00 [Thu Sep 16 01:43:51 2021] R10: 937bdf8e9a00 R11: 937bdf8e99e0 R12: d9253fac20a8 [Thu Sep 16 01:43:51 2021] R13: 0004 R14: 0004 R15: d9253fac20a8 [Thu Sep 16 01:43:51 2021] ? cpuidle_enter_state+0xa1/0x450 [Thu Sep 16 01:43:51 2021] cpuidle_enter+0x2e/0x40 [Thu Sep 16 01:43:51 2021] call_cpuidle+0x23/0x40 [Thu Sep 16 01:43:51 2021] do_idle+0x1dd/0x270 [Thu Sep 16 01:43:51 2021] cpu_startup_entry+0x20/0x30 [Thu Sep 16 01:43:51 2021] start_secondary+0x167/0x1c0 [Thu Sep 16 01:43:51 2021] secondary_startup_64+0xa4/0xb0 [Thu Sep 16 01:43:51 2021] ---[ end trace cb80e9f61341ace0 ]--- [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: initiating reset due to tx timeout [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: Reset adapter [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: TXDCTL.ENABLE for one or more queues not
[Kernel-packages] [Bug 1943879] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1943879/+attachment/5525751/+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/1943879 Title: NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out Status in linux package in Ubuntu: Incomplete Bug description: I am running ubuntu Focal version with following kernel and NIC and noticed where strange error in kernel logs and my nic went down, does any one know about this? # uname -a Linux ostack-phx-comp-gen-1-27.v1v0x.net 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64x # lspci | grep -i eth 06:00.0 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) 06:00.1 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) [Thu Sep 16 01:43:51 2021] [ cut here ] [Thu Sep 16 01:43:51 2021] NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out [Thu Sep 16 01:43:51 2021] WARNING: CPU: 11 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Modules linked in: nf_conntrack_netlink ebt_arp nft_compat nf_tables_set nft_meta_bridgel [Thu Sep 16 01:43:51 2021] ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_mi [Thu Sep 16 01:43:51 2021] CPU: 11 PID: 0 Comm: swapper/11 Not tainted 5.4.0-42-generic #46-Ubuntu [Thu Sep 16 01:43:51 2021] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017 [Thu Sep 16 01:43:51 2021] RIP: 0010:dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 1f f5 e7 00 01 e8 8d bb fa ff 44 89 e9 4c 89 fe 47 [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d466b4e30 EFLAGS: 00010286 [Thu Sep 16 01:43:51 2021] RAX: RBX: 9373ef57cec0 RCX: 083f [Thu Sep 16 01:43:51 2021] RDX: RSI: 00f6 RDI: 083f [Thu Sep 16 01:43:51 2021] RBP: b92d466b4e60 R08: 937bdf8d78c8 R09: 0004 [Thu Sep 16 01:43:51 2021] R10: R11: 0001 R12: 0040 [Thu Sep 16 01:43:51 2021] R13: 0022 R14: 9373ef580480 R15: 9373ef58 [Thu Sep 16 01:43:51 2021] FS: () GS:937bdf8c() knlGS: [Thu Sep 16 01:43:51 2021] CS: 0010 DS: ES: CR0: 80050033 [Thu Sep 16 01:43:51 2021] CR2: 7f3697ec19dc CR3: 00103ce0a001 CR4: 001626e0 [Thu Sep 16 01:43:51 2021] Call Trace: [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] ? pfifo_fast_enqueue+0x150/0x150 [Thu Sep 16 01:43:51 2021] call_timer_fn+0x32/0x130 [Thu Sep 16 01:43:51 2021] __run_timers.part.0+0x180/0x280 [Thu Sep 16 01:43:51 2021] ? tick_sched_handle+0x33/0x60 [Thu Sep 16 01:43:51 2021] ? tick_sched_timer+0x3d/0x80 [Thu Sep 16 01:43:51 2021] ? ktime_get+0x3e/0xa0 [Thu Sep 16 01:43:51 2021] run_timer_softirq+0x2a/0x50 [Thu Sep 16 01:43:51 2021] __do_softirq+0xe1/0x2d6 [Thu Sep 16 01:43:51 2021] ? hrtimer_interrupt+0x13b/0x220 [Thu Sep 16 01:43:51 2021] irq_exit+0xae/0xb0 [Thu Sep 16 01:43:51 2021] smp_apic_timer_interrupt+0x7b/0x140 [Thu Sep 16 01:43:51 2021] apic_timer_interrupt+0xf/0x20 [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [Thu Sep 16 01:43:51 2021] Code: ff e8 bf 08 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 0d [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d4634fe38 EFLAGS: 0246 ORIG_RAX: ff13 [Thu Sep 16 01:43:51 2021] RAX: 937bdf8ead00 RBX: 8d159c00 RCX: 001f [Thu Sep 16 01:43:51 2021] RDX: RSI: 3342629e RDI: [Thu Sep 16 01:43:51 2021] RBP: b92d4634fe78 R08: 0011dc129ea2a1f1 R09: 0011dc17357faf00 [Thu Sep 16 01:43:51 2021] R10: 937bdf8e9a00 R11: 937bdf8e99e0 R12: d9253fac20a8 [Thu Sep 16 01:43:51 2021] R13: 0004 R14: 0004 R15: d9253fac20a8 [Thu Sep 16 01:43:51 2021] ? cpuidle_enter_state+0xa1/0x450 [Thu Sep 16 01:43:51 2021] cpuidle_enter+0x2e/0x40 [Thu Sep 16 01:43:51 2021] call_cpuidle+0x23/0x40 [Thu Sep 16 01:43:51 2021] do_idle+0x1dd/0x270 [Thu Sep 16 01:43:51 2021] cpu_startup_entry+0x20/0x30 [Thu Sep 16 01:43:51 2021] start_secondary+0x167/0x1c0 [Thu Sep 16 01:43:51 2021] secondary_startup_64+0xa4/0xb0 [Thu Sep 16 01:43:51 2021] ---[ end trace cb80e9f61341ace0 ]--- [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: initiating reset due to tx timeout [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: Reset adapter [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: TXDCTL.ENABLE for one or
[Kernel-packages] [Bug 1943879] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1943879/+attachment/5525743/+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/1943879 Title: NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out Status in linux package in Ubuntu: Incomplete Bug description: I am running ubuntu Focal version with following kernel and NIC and noticed where strange error in kernel logs and my nic went down, does any one know about this? # uname -a Linux ostack-phx-comp-gen-1-27.v1v0x.net 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64x # lspci | grep -i eth 06:00.0 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) 06:00.1 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) [Thu Sep 16 01:43:51 2021] [ cut here ] [Thu Sep 16 01:43:51 2021] NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out [Thu Sep 16 01:43:51 2021] WARNING: CPU: 11 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Modules linked in: nf_conntrack_netlink ebt_arp nft_compat nf_tables_set nft_meta_bridgel [Thu Sep 16 01:43:51 2021] ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_mi [Thu Sep 16 01:43:51 2021] CPU: 11 PID: 0 Comm: swapper/11 Not tainted 5.4.0-42-generic #46-Ubuntu [Thu Sep 16 01:43:51 2021] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017 [Thu Sep 16 01:43:51 2021] RIP: 0010:dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 1f f5 e7 00 01 e8 8d bb fa ff 44 89 e9 4c 89 fe 47 [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d466b4e30 EFLAGS: 00010286 [Thu Sep 16 01:43:51 2021] RAX: RBX: 9373ef57cec0 RCX: 083f [Thu Sep 16 01:43:51 2021] RDX: RSI: 00f6 RDI: 083f [Thu Sep 16 01:43:51 2021] RBP: b92d466b4e60 R08: 937bdf8d78c8 R09: 0004 [Thu Sep 16 01:43:51 2021] R10: R11: 0001 R12: 0040 [Thu Sep 16 01:43:51 2021] R13: 0022 R14: 9373ef580480 R15: 9373ef58 [Thu Sep 16 01:43:51 2021] FS: () GS:937bdf8c() knlGS: [Thu Sep 16 01:43:51 2021] CS: 0010 DS: ES: CR0: 80050033 [Thu Sep 16 01:43:51 2021] CR2: 7f3697ec19dc CR3: 00103ce0a001 CR4: 001626e0 [Thu Sep 16 01:43:51 2021] Call Trace: [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] ? pfifo_fast_enqueue+0x150/0x150 [Thu Sep 16 01:43:51 2021] call_timer_fn+0x32/0x130 [Thu Sep 16 01:43:51 2021] __run_timers.part.0+0x180/0x280 [Thu Sep 16 01:43:51 2021] ? tick_sched_handle+0x33/0x60 [Thu Sep 16 01:43:51 2021] ? tick_sched_timer+0x3d/0x80 [Thu Sep 16 01:43:51 2021] ? ktime_get+0x3e/0xa0 [Thu Sep 16 01:43:51 2021] run_timer_softirq+0x2a/0x50 [Thu Sep 16 01:43:51 2021] __do_softirq+0xe1/0x2d6 [Thu Sep 16 01:43:51 2021] ? hrtimer_interrupt+0x13b/0x220 [Thu Sep 16 01:43:51 2021] irq_exit+0xae/0xb0 [Thu Sep 16 01:43:51 2021] smp_apic_timer_interrupt+0x7b/0x140 [Thu Sep 16 01:43:51 2021] apic_timer_interrupt+0xf/0x20 [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [Thu Sep 16 01:43:51 2021] Code: ff e8 bf 08 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 0d [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d4634fe38 EFLAGS: 0246 ORIG_RAX: ff13 [Thu Sep 16 01:43:51 2021] RAX: 937bdf8ead00 RBX: 8d159c00 RCX: 001f [Thu Sep 16 01:43:51 2021] RDX: RSI: 3342629e RDI: [Thu Sep 16 01:43:51 2021] RBP: b92d4634fe78 R08: 0011dc129ea2a1f1 R09: 0011dc17357faf00 [Thu Sep 16 01:43:51 2021] R10: 937bdf8e9a00 R11: 937bdf8e99e0 R12: d9253fac20a8 [Thu Sep 16 01:43:51 2021] R13: 0004 R14: 0004 R15: d9253fac20a8 [Thu Sep 16 01:43:51 2021] ? cpuidle_enter_state+0xa1/0x450 [Thu Sep 16 01:43:51 2021] cpuidle_enter+0x2e/0x40 [Thu Sep 16 01:43:51 2021] call_cpuidle+0x23/0x40 [Thu Sep 16 01:43:51 2021] do_idle+0x1dd/0x270 [Thu Sep 16 01:43:51 2021] cpu_startup_entry+0x20/0x30 [Thu Sep 16 01:43:51 2021] start_secondary+0x167/0x1c0 [Thu Sep 16 01:43:51 2021] secondary_startup_64+0xa4/0xb0 [Thu Sep 16 01:43:51 2021] ---[ end trace cb80e9f61341ace0 ]--- [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: initiating reset due to tx timeout [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: Reset adapter [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: TXDCTL.ENABLE for one or more
[Kernel-packages] [Bug 1943879] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1943879/+attachment/5525747/+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/1943879 Title: NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out Status in linux package in Ubuntu: Incomplete Bug description: I am running ubuntu Focal version with following kernel and NIC and noticed where strange error in kernel logs and my nic went down, does any one know about this? # uname -a Linux ostack-phx-comp-gen-1-27.v1v0x.net 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64x # lspci | grep -i eth 06:00.0 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) 06:00.1 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) [Thu Sep 16 01:43:51 2021] [ cut here ] [Thu Sep 16 01:43:51 2021] NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out [Thu Sep 16 01:43:51 2021] WARNING: CPU: 11 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Modules linked in: nf_conntrack_netlink ebt_arp nft_compat nf_tables_set nft_meta_bridgel [Thu Sep 16 01:43:51 2021] ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_mi [Thu Sep 16 01:43:51 2021] CPU: 11 PID: 0 Comm: swapper/11 Not tainted 5.4.0-42-generic #46-Ubuntu [Thu Sep 16 01:43:51 2021] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017 [Thu Sep 16 01:43:51 2021] RIP: 0010:dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 1f f5 e7 00 01 e8 8d bb fa ff 44 89 e9 4c 89 fe 47 [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d466b4e30 EFLAGS: 00010286 [Thu Sep 16 01:43:51 2021] RAX: RBX: 9373ef57cec0 RCX: 083f [Thu Sep 16 01:43:51 2021] RDX: RSI: 00f6 RDI: 083f [Thu Sep 16 01:43:51 2021] RBP: b92d466b4e60 R08: 937bdf8d78c8 R09: 0004 [Thu Sep 16 01:43:51 2021] R10: R11: 0001 R12: 0040 [Thu Sep 16 01:43:51 2021] R13: 0022 R14: 9373ef580480 R15: 9373ef58 [Thu Sep 16 01:43:51 2021] FS: () GS:937bdf8c() knlGS: [Thu Sep 16 01:43:51 2021] CS: 0010 DS: ES: CR0: 80050033 [Thu Sep 16 01:43:51 2021] CR2: 7f3697ec19dc CR3: 00103ce0a001 CR4: 001626e0 [Thu Sep 16 01:43:51 2021] Call Trace: [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] ? pfifo_fast_enqueue+0x150/0x150 [Thu Sep 16 01:43:51 2021] call_timer_fn+0x32/0x130 [Thu Sep 16 01:43:51 2021] __run_timers.part.0+0x180/0x280 [Thu Sep 16 01:43:51 2021] ? tick_sched_handle+0x33/0x60 [Thu Sep 16 01:43:51 2021] ? tick_sched_timer+0x3d/0x80 [Thu Sep 16 01:43:51 2021] ? ktime_get+0x3e/0xa0 [Thu Sep 16 01:43:51 2021] run_timer_softirq+0x2a/0x50 [Thu Sep 16 01:43:51 2021] __do_softirq+0xe1/0x2d6 [Thu Sep 16 01:43:51 2021] ? hrtimer_interrupt+0x13b/0x220 [Thu Sep 16 01:43:51 2021] irq_exit+0xae/0xb0 [Thu Sep 16 01:43:51 2021] smp_apic_timer_interrupt+0x7b/0x140 [Thu Sep 16 01:43:51 2021] apic_timer_interrupt+0xf/0x20 [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [Thu Sep 16 01:43:51 2021] Code: ff e8 bf 08 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 0d [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d4634fe38 EFLAGS: 0246 ORIG_RAX: ff13 [Thu Sep 16 01:43:51 2021] RAX: 937bdf8ead00 RBX: 8d159c00 RCX: 001f [Thu Sep 16 01:43:51 2021] RDX: RSI: 3342629e RDI: [Thu Sep 16 01:43:51 2021] RBP: b92d4634fe78 R08: 0011dc129ea2a1f1 R09: 0011dc17357faf00 [Thu Sep 16 01:43:51 2021] R10: 937bdf8e9a00 R11: 937bdf8e99e0 R12: d9253fac20a8 [Thu Sep 16 01:43:51 2021] R13: 0004 R14: 0004 R15: d9253fac20a8 [Thu Sep 16 01:43:51 2021] ? cpuidle_enter_state+0xa1/0x450 [Thu Sep 16 01:43:51 2021] cpuidle_enter+0x2e/0x40 [Thu Sep 16 01:43:51 2021] call_cpuidle+0x23/0x40 [Thu Sep 16 01:43:51 2021] do_idle+0x1dd/0x270 [Thu Sep 16 01:43:51 2021] cpu_startup_entry+0x20/0x30 [Thu Sep 16 01:43:51 2021] start_secondary+0x167/0x1c0 [Thu Sep 16 01:43:51 2021] secondary_startup_64+0xa4/0xb0 [Thu Sep 16 01:43:51 2021] ---[ end trace cb80e9f61341ace0 ]--- [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: initiating reset due to tx timeout [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: Reset adapter [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: TXDCTL.ENABLE for one or more queues not
[Kernel-packages] [Bug 1943879] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1943879/+attachment/5525753/+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/1943879 Title: NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out Status in linux package in Ubuntu: Incomplete Bug description: I am running ubuntu Focal version with following kernel and NIC and noticed where strange error in kernel logs and my nic went down, does any one know about this? # uname -a Linux ostack-phx-comp-gen-1-27.v1v0x.net 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64x # lspci | grep -i eth 06:00.0 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) 06:00.1 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) [Thu Sep 16 01:43:51 2021] [ cut here ] [Thu Sep 16 01:43:51 2021] NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out [Thu Sep 16 01:43:51 2021] WARNING: CPU: 11 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Modules linked in: nf_conntrack_netlink ebt_arp nft_compat nf_tables_set nft_meta_bridgel [Thu Sep 16 01:43:51 2021] ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_mi [Thu Sep 16 01:43:51 2021] CPU: 11 PID: 0 Comm: swapper/11 Not tainted 5.4.0-42-generic #46-Ubuntu [Thu Sep 16 01:43:51 2021] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017 [Thu Sep 16 01:43:51 2021] RIP: 0010:dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 1f f5 e7 00 01 e8 8d bb fa ff 44 89 e9 4c 89 fe 47 [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d466b4e30 EFLAGS: 00010286 [Thu Sep 16 01:43:51 2021] RAX: RBX: 9373ef57cec0 RCX: 083f [Thu Sep 16 01:43:51 2021] RDX: RSI: 00f6 RDI: 083f [Thu Sep 16 01:43:51 2021] RBP: b92d466b4e60 R08: 937bdf8d78c8 R09: 0004 [Thu Sep 16 01:43:51 2021] R10: R11: 0001 R12: 0040 [Thu Sep 16 01:43:51 2021] R13: 0022 R14: 9373ef580480 R15: 9373ef58 [Thu Sep 16 01:43:51 2021] FS: () GS:937bdf8c() knlGS: [Thu Sep 16 01:43:51 2021] CS: 0010 DS: ES: CR0: 80050033 [Thu Sep 16 01:43:51 2021] CR2: 7f3697ec19dc CR3: 00103ce0a001 CR4: 001626e0 [Thu Sep 16 01:43:51 2021] Call Trace: [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] ? pfifo_fast_enqueue+0x150/0x150 [Thu Sep 16 01:43:51 2021] call_timer_fn+0x32/0x130 [Thu Sep 16 01:43:51 2021] __run_timers.part.0+0x180/0x280 [Thu Sep 16 01:43:51 2021] ? tick_sched_handle+0x33/0x60 [Thu Sep 16 01:43:51 2021] ? tick_sched_timer+0x3d/0x80 [Thu Sep 16 01:43:51 2021] ? ktime_get+0x3e/0xa0 [Thu Sep 16 01:43:51 2021] run_timer_softirq+0x2a/0x50 [Thu Sep 16 01:43:51 2021] __do_softirq+0xe1/0x2d6 [Thu Sep 16 01:43:51 2021] ? hrtimer_interrupt+0x13b/0x220 [Thu Sep 16 01:43:51 2021] irq_exit+0xae/0xb0 [Thu Sep 16 01:43:51 2021] smp_apic_timer_interrupt+0x7b/0x140 [Thu Sep 16 01:43:51 2021] apic_timer_interrupt+0xf/0x20 [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [Thu Sep 16 01:43:51 2021] Code: ff e8 bf 08 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 0d [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d4634fe38 EFLAGS: 0246 ORIG_RAX: ff13 [Thu Sep 16 01:43:51 2021] RAX: 937bdf8ead00 RBX: 8d159c00 RCX: 001f [Thu Sep 16 01:43:51 2021] RDX: RSI: 3342629e RDI: [Thu Sep 16 01:43:51 2021] RBP: b92d4634fe78 R08: 0011dc129ea2a1f1 R09: 0011dc17357faf00 [Thu Sep 16 01:43:51 2021] R10: 937bdf8e9a00 R11: 937bdf8e99e0 R12: d9253fac20a8 [Thu Sep 16 01:43:51 2021] R13: 0004 R14: 0004 R15: d9253fac20a8 [Thu Sep 16 01:43:51 2021] ? cpuidle_enter_state+0xa1/0x450 [Thu Sep 16 01:43:51 2021] cpuidle_enter+0x2e/0x40 [Thu Sep 16 01:43:51 2021] call_cpuidle+0x23/0x40 [Thu Sep 16 01:43:51 2021] do_idle+0x1dd/0x270 [Thu Sep 16 01:43:51 2021] cpu_startup_entry+0x20/0x30 [Thu Sep 16 01:43:51 2021] start_secondary+0x167/0x1c0 [Thu Sep 16 01:43:51 2021] secondary_startup_64+0xa4/0xb0 [Thu Sep 16 01:43:51 2021] ---[ end trace cb80e9f61341ace0 ]--- [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: initiating reset due to tx timeout [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: Reset adapter [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: TXDCTL.ENABLE for one or more queues not
[Kernel-packages] [Bug 1943879] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1943879/+attachment/5525752/+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/1943879 Title: NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out Status in linux package in Ubuntu: Incomplete Bug description: I am running ubuntu Focal version with following kernel and NIC and noticed where strange error in kernel logs and my nic went down, does any one know about this? # uname -a Linux ostack-phx-comp-gen-1-27.v1v0x.net 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64x # lspci | grep -i eth 06:00.0 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) 06:00.1 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) [Thu Sep 16 01:43:51 2021] [ cut here ] [Thu Sep 16 01:43:51 2021] NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out [Thu Sep 16 01:43:51 2021] WARNING: CPU: 11 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Modules linked in: nf_conntrack_netlink ebt_arp nft_compat nf_tables_set nft_meta_bridgel [Thu Sep 16 01:43:51 2021] ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_mi [Thu Sep 16 01:43:51 2021] CPU: 11 PID: 0 Comm: swapper/11 Not tainted 5.4.0-42-generic #46-Ubuntu [Thu Sep 16 01:43:51 2021] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017 [Thu Sep 16 01:43:51 2021] RIP: 0010:dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 1f f5 e7 00 01 e8 8d bb fa ff 44 89 e9 4c 89 fe 47 [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d466b4e30 EFLAGS: 00010286 [Thu Sep 16 01:43:51 2021] RAX: RBX: 9373ef57cec0 RCX: 083f [Thu Sep 16 01:43:51 2021] RDX: RSI: 00f6 RDI: 083f [Thu Sep 16 01:43:51 2021] RBP: b92d466b4e60 R08: 937bdf8d78c8 R09: 0004 [Thu Sep 16 01:43:51 2021] R10: R11: 0001 R12: 0040 [Thu Sep 16 01:43:51 2021] R13: 0022 R14: 9373ef580480 R15: 9373ef58 [Thu Sep 16 01:43:51 2021] FS: () GS:937bdf8c() knlGS: [Thu Sep 16 01:43:51 2021] CS: 0010 DS: ES: CR0: 80050033 [Thu Sep 16 01:43:51 2021] CR2: 7f3697ec19dc CR3: 00103ce0a001 CR4: 001626e0 [Thu Sep 16 01:43:51 2021] Call Trace: [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] ? pfifo_fast_enqueue+0x150/0x150 [Thu Sep 16 01:43:51 2021] call_timer_fn+0x32/0x130 [Thu Sep 16 01:43:51 2021] __run_timers.part.0+0x180/0x280 [Thu Sep 16 01:43:51 2021] ? tick_sched_handle+0x33/0x60 [Thu Sep 16 01:43:51 2021] ? tick_sched_timer+0x3d/0x80 [Thu Sep 16 01:43:51 2021] ? ktime_get+0x3e/0xa0 [Thu Sep 16 01:43:51 2021] run_timer_softirq+0x2a/0x50 [Thu Sep 16 01:43:51 2021] __do_softirq+0xe1/0x2d6 [Thu Sep 16 01:43:51 2021] ? hrtimer_interrupt+0x13b/0x220 [Thu Sep 16 01:43:51 2021] irq_exit+0xae/0xb0 [Thu Sep 16 01:43:51 2021] smp_apic_timer_interrupt+0x7b/0x140 [Thu Sep 16 01:43:51 2021] apic_timer_interrupt+0xf/0x20 [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [Thu Sep 16 01:43:51 2021] Code: ff e8 bf 08 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 0d [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d4634fe38 EFLAGS: 0246 ORIG_RAX: ff13 [Thu Sep 16 01:43:51 2021] RAX: 937bdf8ead00 RBX: 8d159c00 RCX: 001f [Thu Sep 16 01:43:51 2021] RDX: RSI: 3342629e RDI: [Thu Sep 16 01:43:51 2021] RBP: b92d4634fe78 R08: 0011dc129ea2a1f1 R09: 0011dc17357faf00 [Thu Sep 16 01:43:51 2021] R10: 937bdf8e9a00 R11: 937bdf8e99e0 R12: d9253fac20a8 [Thu Sep 16 01:43:51 2021] R13: 0004 R14: 0004 R15: d9253fac20a8 [Thu Sep 16 01:43:51 2021] ? cpuidle_enter_state+0xa1/0x450 [Thu Sep 16 01:43:51 2021] cpuidle_enter+0x2e/0x40 [Thu Sep 16 01:43:51 2021] call_cpuidle+0x23/0x40 [Thu Sep 16 01:43:51 2021] do_idle+0x1dd/0x270 [Thu Sep 16 01:43:51 2021] cpu_startup_entry+0x20/0x30 [Thu Sep 16 01:43:51 2021] start_secondary+0x167/0x1c0 [Thu Sep 16 01:43:51 2021] secondary_startup_64+0xa4/0xb0 [Thu Sep 16 01:43:51 2021] ---[ end trace cb80e9f61341ace0 ]--- [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: initiating reset due to tx timeout [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: Reset adapter [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: TXDCTL.ENABLE for one or more
[Kernel-packages] [Bug 1943879] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1943879/+attachment/5525746/+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/1943879 Title: NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out Status in linux package in Ubuntu: Incomplete Bug description: I am running ubuntu Focal version with following kernel and NIC and noticed where strange error in kernel logs and my nic went down, does any one know about this? # uname -a Linux ostack-phx-comp-gen-1-27.v1v0x.net 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64x # lspci | grep -i eth 06:00.0 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) 06:00.1 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) [Thu Sep 16 01:43:51 2021] [ cut here ] [Thu Sep 16 01:43:51 2021] NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out [Thu Sep 16 01:43:51 2021] WARNING: CPU: 11 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Modules linked in: nf_conntrack_netlink ebt_arp nft_compat nf_tables_set nft_meta_bridgel [Thu Sep 16 01:43:51 2021] ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_mi [Thu Sep 16 01:43:51 2021] CPU: 11 PID: 0 Comm: swapper/11 Not tainted 5.4.0-42-generic #46-Ubuntu [Thu Sep 16 01:43:51 2021] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017 [Thu Sep 16 01:43:51 2021] RIP: 0010:dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 1f f5 e7 00 01 e8 8d bb fa ff 44 89 e9 4c 89 fe 47 [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d466b4e30 EFLAGS: 00010286 [Thu Sep 16 01:43:51 2021] RAX: RBX: 9373ef57cec0 RCX: 083f [Thu Sep 16 01:43:51 2021] RDX: RSI: 00f6 RDI: 083f [Thu Sep 16 01:43:51 2021] RBP: b92d466b4e60 R08: 937bdf8d78c8 R09: 0004 [Thu Sep 16 01:43:51 2021] R10: R11: 0001 R12: 0040 [Thu Sep 16 01:43:51 2021] R13: 0022 R14: 9373ef580480 R15: 9373ef58 [Thu Sep 16 01:43:51 2021] FS: () GS:937bdf8c() knlGS: [Thu Sep 16 01:43:51 2021] CS: 0010 DS: ES: CR0: 80050033 [Thu Sep 16 01:43:51 2021] CR2: 7f3697ec19dc CR3: 00103ce0a001 CR4: 001626e0 [Thu Sep 16 01:43:51 2021] Call Trace: [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] ? pfifo_fast_enqueue+0x150/0x150 [Thu Sep 16 01:43:51 2021] call_timer_fn+0x32/0x130 [Thu Sep 16 01:43:51 2021] __run_timers.part.0+0x180/0x280 [Thu Sep 16 01:43:51 2021] ? tick_sched_handle+0x33/0x60 [Thu Sep 16 01:43:51 2021] ? tick_sched_timer+0x3d/0x80 [Thu Sep 16 01:43:51 2021] ? ktime_get+0x3e/0xa0 [Thu Sep 16 01:43:51 2021] run_timer_softirq+0x2a/0x50 [Thu Sep 16 01:43:51 2021] __do_softirq+0xe1/0x2d6 [Thu Sep 16 01:43:51 2021] ? hrtimer_interrupt+0x13b/0x220 [Thu Sep 16 01:43:51 2021] irq_exit+0xae/0xb0 [Thu Sep 16 01:43:51 2021] smp_apic_timer_interrupt+0x7b/0x140 [Thu Sep 16 01:43:51 2021] apic_timer_interrupt+0xf/0x20 [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [Thu Sep 16 01:43:51 2021] Code: ff e8 bf 08 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 0d [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d4634fe38 EFLAGS: 0246 ORIG_RAX: ff13 [Thu Sep 16 01:43:51 2021] RAX: 937bdf8ead00 RBX: 8d159c00 RCX: 001f [Thu Sep 16 01:43:51 2021] RDX: RSI: 3342629e RDI: [Thu Sep 16 01:43:51 2021] RBP: b92d4634fe78 R08: 0011dc129ea2a1f1 R09: 0011dc17357faf00 [Thu Sep 16 01:43:51 2021] R10: 937bdf8e9a00 R11: 937bdf8e99e0 R12: d9253fac20a8 [Thu Sep 16 01:43:51 2021] R13: 0004 R14: 0004 R15: d9253fac20a8 [Thu Sep 16 01:43:51 2021] ? cpuidle_enter_state+0xa1/0x450 [Thu Sep 16 01:43:51 2021] cpuidle_enter+0x2e/0x40 [Thu Sep 16 01:43:51 2021] call_cpuidle+0x23/0x40 [Thu Sep 16 01:43:51 2021] do_idle+0x1dd/0x270 [Thu Sep 16 01:43:51 2021] cpu_startup_entry+0x20/0x30 [Thu Sep 16 01:43:51 2021] start_secondary+0x167/0x1c0 [Thu Sep 16 01:43:51 2021] secondary_startup_64+0xa4/0xb0 [Thu Sep 16 01:43:51 2021] ---[ end trace cb80e9f61341ace0 ]--- [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: initiating reset due to tx timeout [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: Reset adapter [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: TXDCTL.ENABLE for one or more queues not
[Kernel-packages] [Bug 1943879] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1943879/+attachment/5525749/+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/1943879 Title: NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out Status in linux package in Ubuntu: Incomplete Bug description: I am running ubuntu Focal version with following kernel and NIC and noticed where strange error in kernel logs and my nic went down, does any one know about this? # uname -a Linux ostack-phx-comp-gen-1-27.v1v0x.net 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64x # lspci | grep -i eth 06:00.0 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) 06:00.1 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) [Thu Sep 16 01:43:51 2021] [ cut here ] [Thu Sep 16 01:43:51 2021] NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out [Thu Sep 16 01:43:51 2021] WARNING: CPU: 11 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Modules linked in: nf_conntrack_netlink ebt_arp nft_compat nf_tables_set nft_meta_bridgel [Thu Sep 16 01:43:51 2021] ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_mi [Thu Sep 16 01:43:51 2021] CPU: 11 PID: 0 Comm: swapper/11 Not tainted 5.4.0-42-generic #46-Ubuntu [Thu Sep 16 01:43:51 2021] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017 [Thu Sep 16 01:43:51 2021] RIP: 0010:dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 1f f5 e7 00 01 e8 8d bb fa ff 44 89 e9 4c 89 fe 47 [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d466b4e30 EFLAGS: 00010286 [Thu Sep 16 01:43:51 2021] RAX: RBX: 9373ef57cec0 RCX: 083f [Thu Sep 16 01:43:51 2021] RDX: RSI: 00f6 RDI: 083f [Thu Sep 16 01:43:51 2021] RBP: b92d466b4e60 R08: 937bdf8d78c8 R09: 0004 [Thu Sep 16 01:43:51 2021] R10: R11: 0001 R12: 0040 [Thu Sep 16 01:43:51 2021] R13: 0022 R14: 9373ef580480 R15: 9373ef58 [Thu Sep 16 01:43:51 2021] FS: () GS:937bdf8c() knlGS: [Thu Sep 16 01:43:51 2021] CS: 0010 DS: ES: CR0: 80050033 [Thu Sep 16 01:43:51 2021] CR2: 7f3697ec19dc CR3: 00103ce0a001 CR4: 001626e0 [Thu Sep 16 01:43:51 2021] Call Trace: [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] ? pfifo_fast_enqueue+0x150/0x150 [Thu Sep 16 01:43:51 2021] call_timer_fn+0x32/0x130 [Thu Sep 16 01:43:51 2021] __run_timers.part.0+0x180/0x280 [Thu Sep 16 01:43:51 2021] ? tick_sched_handle+0x33/0x60 [Thu Sep 16 01:43:51 2021] ? tick_sched_timer+0x3d/0x80 [Thu Sep 16 01:43:51 2021] ? ktime_get+0x3e/0xa0 [Thu Sep 16 01:43:51 2021] run_timer_softirq+0x2a/0x50 [Thu Sep 16 01:43:51 2021] __do_softirq+0xe1/0x2d6 [Thu Sep 16 01:43:51 2021] ? hrtimer_interrupt+0x13b/0x220 [Thu Sep 16 01:43:51 2021] irq_exit+0xae/0xb0 [Thu Sep 16 01:43:51 2021] smp_apic_timer_interrupt+0x7b/0x140 [Thu Sep 16 01:43:51 2021] apic_timer_interrupt+0xf/0x20 [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [Thu Sep 16 01:43:51 2021] Code: ff e8 bf 08 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 0d [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d4634fe38 EFLAGS: 0246 ORIG_RAX: ff13 [Thu Sep 16 01:43:51 2021] RAX: 937bdf8ead00 RBX: 8d159c00 RCX: 001f [Thu Sep 16 01:43:51 2021] RDX: RSI: 3342629e RDI: [Thu Sep 16 01:43:51 2021] RBP: b92d4634fe78 R08: 0011dc129ea2a1f1 R09: 0011dc17357faf00 [Thu Sep 16 01:43:51 2021] R10: 937bdf8e9a00 R11: 937bdf8e99e0 R12: d9253fac20a8 [Thu Sep 16 01:43:51 2021] R13: 0004 R14: 0004 R15: d9253fac20a8 [Thu Sep 16 01:43:51 2021] ? cpuidle_enter_state+0xa1/0x450 [Thu Sep 16 01:43:51 2021] cpuidle_enter+0x2e/0x40 [Thu Sep 16 01:43:51 2021] call_cpuidle+0x23/0x40 [Thu Sep 16 01:43:51 2021] do_idle+0x1dd/0x270 [Thu Sep 16 01:43:51 2021] cpu_startup_entry+0x20/0x30 [Thu Sep 16 01:43:51 2021] start_secondary+0x167/0x1c0 [Thu Sep 16 01:43:51 2021] secondary_startup_64+0xa4/0xb0 [Thu Sep 16 01:43:51 2021] ---[ end trace cb80e9f61341ace0 ]--- [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: initiating reset due to tx timeout [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: Reset adapter [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: TXDCTL.ENABLE for one or more
[Kernel-packages] [Bug 1943879] Re: NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out
apport information ** Tags added: apport-collected uec-images ** Description changed: I am running ubuntu Focal version with following kernel and NIC and noticed where strange error in kernel logs and my nic went down, does any one know about this? # uname -a Linux ostack-phx-comp-gen-1-27.v1v0x.net 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64x # lspci | grep -i eth 06:00.0 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) 06:00.1 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) [Thu Sep 16 01:43:51 2021] [ cut here ] [Thu Sep 16 01:43:51 2021] NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out [Thu Sep 16 01:43:51 2021] WARNING: CPU: 11 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Modules linked in: nf_conntrack_netlink ebt_arp nft_compat nf_tables_set nft_meta_bridgel [Thu Sep 16 01:43:51 2021] ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_mi [Thu Sep 16 01:43:51 2021] CPU: 11 PID: 0 Comm: swapper/11 Not tainted 5.4.0-42-generic #46-Ubuntu [Thu Sep 16 01:43:51 2021] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017 [Thu Sep 16 01:43:51 2021] RIP: 0010:dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 1f f5 e7 00 01 e8 8d bb fa ff 44 89 e9 4c 89 fe 47 [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d466b4e30 EFLAGS: 00010286 [Thu Sep 16 01:43:51 2021] RAX: RBX: 9373ef57cec0 RCX: 083f [Thu Sep 16 01:43:51 2021] RDX: RSI: 00f6 RDI: 083f [Thu Sep 16 01:43:51 2021] RBP: b92d466b4e60 R08: 937bdf8d78c8 R09: 0004 [Thu Sep 16 01:43:51 2021] R10: R11: 0001 R12: 0040 [Thu Sep 16 01:43:51 2021] R13: 0022 R14: 9373ef580480 R15: 9373ef58 [Thu Sep 16 01:43:51 2021] FS: () GS:937bdf8c() knlGS: [Thu Sep 16 01:43:51 2021] CS: 0010 DS: ES: CR0: 80050033 [Thu Sep 16 01:43:51 2021] CR2: 7f3697ec19dc CR3: 00103ce0a001 CR4: 001626e0 [Thu Sep 16 01:43:51 2021] Call Trace: [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] ? pfifo_fast_enqueue+0x150/0x150 [Thu Sep 16 01:43:51 2021] call_timer_fn+0x32/0x130 [Thu Sep 16 01:43:51 2021] __run_timers.part.0+0x180/0x280 [Thu Sep 16 01:43:51 2021] ? tick_sched_handle+0x33/0x60 [Thu Sep 16 01:43:51 2021] ? tick_sched_timer+0x3d/0x80 [Thu Sep 16 01:43:51 2021] ? ktime_get+0x3e/0xa0 [Thu Sep 16 01:43:51 2021] run_timer_softirq+0x2a/0x50 [Thu Sep 16 01:43:51 2021] __do_softirq+0xe1/0x2d6 [Thu Sep 16 01:43:51 2021] ? hrtimer_interrupt+0x13b/0x220 [Thu Sep 16 01:43:51 2021] irq_exit+0xae/0xb0 [Thu Sep 16 01:43:51 2021] smp_apic_timer_interrupt+0x7b/0x140 [Thu Sep 16 01:43:51 2021] apic_timer_interrupt+0xf/0x20 [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [Thu Sep 16 01:43:51 2021] Code: ff e8 bf 08 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 0d [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d4634fe38 EFLAGS: 0246 ORIG_RAX: ff13 [Thu Sep 16 01:43:51 2021] RAX: 937bdf8ead00 RBX: 8d159c00 RCX: 001f [Thu Sep 16 01:43:51 2021] RDX: RSI: 3342629e RDI: [Thu Sep 16 01:43:51 2021] RBP: b92d4634fe78 R08: 0011dc129ea2a1f1 R09: 0011dc17357faf00 [Thu Sep 16 01:43:51 2021] R10: 937bdf8e9a00 R11: 937bdf8e99e0 R12: d9253fac20a8 [Thu Sep 16 01:43:51 2021] R13: 0004 R14: 0004 R15: d9253fac20a8 [Thu Sep 16 01:43:51 2021] ? cpuidle_enter_state+0xa1/0x450 [Thu Sep 16 01:43:51 2021] cpuidle_enter+0x2e/0x40 [Thu Sep 16 01:43:51 2021] call_cpuidle+0x23/0x40 [Thu Sep 16 01:43:51 2021] do_idle+0x1dd/0x270 [Thu Sep 16 01:43:51 2021] cpu_startup_entry+0x20/0x30 [Thu Sep 16 01:43:51 2021] start_secondary+0x167/0x1c0 [Thu Sep 16 01:43:51 2021] secondary_startup_64+0xa4/0xb0 [Thu Sep 16 01:43:51 2021] ---[ end trace cb80e9f61341ace0 ]--- [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: initiating reset due to tx timeout [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: Reset adapter [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: TXDCTL.ENABLE for one or more queues not cleared within the pod [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: NIC Link is Up 10 Gbps, Flow Control: RX/TX [Thu Sep 16 01:43:52 2021] ixgbe :06:00.0 eno49: NIC Link is Down [Thu Sep 16 01:43:52 2021] bond0: (slave eno49): link status definitely down, disabling slave [Thu Sep 16 01:43:52 2021] bond0: (slave eno50):
[Kernel-packages] [Bug 1943879] Re: NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out
Find attached Report ** Attachment added: "apport.linux.7t7az__i.apport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943879/+attachment/5525756/+files/apport.linux.7t7az__i.apport -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943879 Title: NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out Status in linux package in Ubuntu: Incomplete Bug description: I am running ubuntu Focal version with following kernel and NIC and noticed where strange error in kernel logs and my nic went down, does any one know about this? # uname -a Linux ostack-phx-comp-gen-1-27.v1v0x.net 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64x # lspci | grep -i eth 06:00.0 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) 06:00.1 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) [Thu Sep 16 01:43:51 2021] [ cut here ] [Thu Sep 16 01:43:51 2021] NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out [Thu Sep 16 01:43:51 2021] WARNING: CPU: 11 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Modules linked in: nf_conntrack_netlink ebt_arp nft_compat nf_tables_set nft_meta_bridgel [Thu Sep 16 01:43:51 2021] ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_mi [Thu Sep 16 01:43:51 2021] CPU: 11 PID: 0 Comm: swapper/11 Not tainted 5.4.0-42-generic #46-Ubuntu [Thu Sep 16 01:43:51 2021] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017 [Thu Sep 16 01:43:51 2021] RIP: 0010:dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 1f f5 e7 00 01 e8 8d bb fa ff 44 89 e9 4c 89 fe 47 [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d466b4e30 EFLAGS: 00010286 [Thu Sep 16 01:43:51 2021] RAX: RBX: 9373ef57cec0 RCX: 083f [Thu Sep 16 01:43:51 2021] RDX: RSI: 00f6 RDI: 083f [Thu Sep 16 01:43:51 2021] RBP: b92d466b4e60 R08: 937bdf8d78c8 R09: 0004 [Thu Sep 16 01:43:51 2021] R10: R11: 0001 R12: 0040 [Thu Sep 16 01:43:51 2021] R13: 0022 R14: 9373ef580480 R15: 9373ef58 [Thu Sep 16 01:43:51 2021] FS: () GS:937bdf8c() knlGS: [Thu Sep 16 01:43:51 2021] CS: 0010 DS: ES: CR0: 80050033 [Thu Sep 16 01:43:51 2021] CR2: 7f3697ec19dc CR3: 00103ce0a001 CR4: 001626e0 [Thu Sep 16 01:43:51 2021] Call Trace: [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] ? pfifo_fast_enqueue+0x150/0x150 [Thu Sep 16 01:43:51 2021] call_timer_fn+0x32/0x130 [Thu Sep 16 01:43:51 2021] __run_timers.part.0+0x180/0x280 [Thu Sep 16 01:43:51 2021] ? tick_sched_handle+0x33/0x60 [Thu Sep 16 01:43:51 2021] ? tick_sched_timer+0x3d/0x80 [Thu Sep 16 01:43:51 2021] ? ktime_get+0x3e/0xa0 [Thu Sep 16 01:43:51 2021] run_timer_softirq+0x2a/0x50 [Thu Sep 16 01:43:51 2021] __do_softirq+0xe1/0x2d6 [Thu Sep 16 01:43:51 2021] ? hrtimer_interrupt+0x13b/0x220 [Thu Sep 16 01:43:51 2021] irq_exit+0xae/0xb0 [Thu Sep 16 01:43:51 2021] smp_apic_timer_interrupt+0x7b/0x140 [Thu Sep 16 01:43:51 2021] apic_timer_interrupt+0xf/0x20 [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [Thu Sep 16 01:43:51 2021] Code: ff e8 bf 08 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 0d [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d4634fe38 EFLAGS: 0246 ORIG_RAX: ff13 [Thu Sep 16 01:43:51 2021] RAX: 937bdf8ead00 RBX: 8d159c00 RCX: 001f [Thu Sep 16 01:43:51 2021] RDX: RSI: 3342629e RDI: [Thu Sep 16 01:43:51 2021] RBP: b92d4634fe78 R08: 0011dc129ea2a1f1 R09: 0011dc17357faf00 [Thu Sep 16 01:43:51 2021] R10: 937bdf8e9a00 R11: 937bdf8e99e0 R12: d9253fac20a8 [Thu Sep 16 01:43:51 2021] R13: 0004 R14: 0004 R15: d9253fac20a8 [Thu Sep 16 01:43:51 2021] ? cpuidle_enter_state+0xa1/0x450 [Thu Sep 16 01:43:51 2021] cpuidle_enter+0x2e/0x40 [Thu Sep 16 01:43:51 2021] call_cpuidle+0x23/0x40 [Thu Sep 16 01:43:51 2021] do_idle+0x1dd/0x270 [Thu Sep 16 01:43:51 2021] cpu_startup_entry+0x20/0x30 [Thu Sep 16 01:43:51 2021] start_secondary+0x167/0x1c0 [Thu Sep 16 01:43:51 2021] secondary_startup_64+0xa4/0xb0 [Thu Sep 16 01:43:51 2021] ---[ end trace cb80e9f61341ace0 ]--- [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: initiating reset due to tx timeout [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: Reset adapter [Thu Sep 16 01:43:51 2021] ixgbe
[Kernel-packages] [Bug 1943879] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1943879/+attachment/5525744/+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/1943879 Title: NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out Status in linux package in Ubuntu: Incomplete Bug description: I am running ubuntu Focal version with following kernel and NIC and noticed where strange error in kernel logs and my nic went down, does any one know about this? # uname -a Linux ostack-phx-comp-gen-1-27.v1v0x.net 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64x # lspci | grep -i eth 06:00.0 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) 06:00.1 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) [Thu Sep 16 01:43:51 2021] [ cut here ] [Thu Sep 16 01:43:51 2021] NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out [Thu Sep 16 01:43:51 2021] WARNING: CPU: 11 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Modules linked in: nf_conntrack_netlink ebt_arp nft_compat nf_tables_set nft_meta_bridgel [Thu Sep 16 01:43:51 2021] ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_mi [Thu Sep 16 01:43:51 2021] CPU: 11 PID: 0 Comm: swapper/11 Not tainted 5.4.0-42-generic #46-Ubuntu [Thu Sep 16 01:43:51 2021] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017 [Thu Sep 16 01:43:51 2021] RIP: 0010:dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 1f f5 e7 00 01 e8 8d bb fa ff 44 89 e9 4c 89 fe 47 [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d466b4e30 EFLAGS: 00010286 [Thu Sep 16 01:43:51 2021] RAX: RBX: 9373ef57cec0 RCX: 083f [Thu Sep 16 01:43:51 2021] RDX: RSI: 00f6 RDI: 083f [Thu Sep 16 01:43:51 2021] RBP: b92d466b4e60 R08: 937bdf8d78c8 R09: 0004 [Thu Sep 16 01:43:51 2021] R10: R11: 0001 R12: 0040 [Thu Sep 16 01:43:51 2021] R13: 0022 R14: 9373ef580480 R15: 9373ef58 [Thu Sep 16 01:43:51 2021] FS: () GS:937bdf8c() knlGS: [Thu Sep 16 01:43:51 2021] CS: 0010 DS: ES: CR0: 80050033 [Thu Sep 16 01:43:51 2021] CR2: 7f3697ec19dc CR3: 00103ce0a001 CR4: 001626e0 [Thu Sep 16 01:43:51 2021] Call Trace: [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] ? pfifo_fast_enqueue+0x150/0x150 [Thu Sep 16 01:43:51 2021] call_timer_fn+0x32/0x130 [Thu Sep 16 01:43:51 2021] __run_timers.part.0+0x180/0x280 [Thu Sep 16 01:43:51 2021] ? tick_sched_handle+0x33/0x60 [Thu Sep 16 01:43:51 2021] ? tick_sched_timer+0x3d/0x80 [Thu Sep 16 01:43:51 2021] ? ktime_get+0x3e/0xa0 [Thu Sep 16 01:43:51 2021] run_timer_softirq+0x2a/0x50 [Thu Sep 16 01:43:51 2021] __do_softirq+0xe1/0x2d6 [Thu Sep 16 01:43:51 2021] ? hrtimer_interrupt+0x13b/0x220 [Thu Sep 16 01:43:51 2021] irq_exit+0xae/0xb0 [Thu Sep 16 01:43:51 2021] smp_apic_timer_interrupt+0x7b/0x140 [Thu Sep 16 01:43:51 2021] apic_timer_interrupt+0xf/0x20 [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [Thu Sep 16 01:43:51 2021] Code: ff e8 bf 08 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 0d [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d4634fe38 EFLAGS: 0246 ORIG_RAX: ff13 [Thu Sep 16 01:43:51 2021] RAX: 937bdf8ead00 RBX: 8d159c00 RCX: 001f [Thu Sep 16 01:43:51 2021] RDX: RSI: 3342629e RDI: [Thu Sep 16 01:43:51 2021] RBP: b92d4634fe78 R08: 0011dc129ea2a1f1 R09: 0011dc17357faf00 [Thu Sep 16 01:43:51 2021] R10: 937bdf8e9a00 R11: 937bdf8e99e0 R12: d9253fac20a8 [Thu Sep 16 01:43:51 2021] R13: 0004 R14: 0004 R15: d9253fac20a8 [Thu Sep 16 01:43:51 2021] ? cpuidle_enter_state+0xa1/0x450 [Thu Sep 16 01:43:51 2021] cpuidle_enter+0x2e/0x40 [Thu Sep 16 01:43:51 2021] call_cpuidle+0x23/0x40 [Thu Sep 16 01:43:51 2021] do_idle+0x1dd/0x270 [Thu Sep 16 01:43:51 2021] cpu_startup_entry+0x20/0x30 [Thu Sep 16 01:43:51 2021] start_secondary+0x167/0x1c0 [Thu Sep 16 01:43:51 2021] secondary_startup_64+0xa4/0xb0 [Thu Sep 16 01:43:51 2021] ---[ end trace cb80e9f61341ace0 ]--- [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: initiating reset due to tx timeout [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: Reset adapter [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: TXDCTL.ENABLE for one or more queues not
[Kernel-packages] [Bug 1943879] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1943879/+attachment/5525745/+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/1943879 Title: NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out Status in linux package in Ubuntu: Incomplete Bug description: I am running ubuntu Focal version with following kernel and NIC and noticed where strange error in kernel logs and my nic went down, does any one know about this? # uname -a Linux ostack-phx-comp-gen-1-27.v1v0x.net 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64x # lspci | grep -i eth 06:00.0 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) 06:00.1 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) [Thu Sep 16 01:43:51 2021] [ cut here ] [Thu Sep 16 01:43:51 2021] NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out [Thu Sep 16 01:43:51 2021] WARNING: CPU: 11 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Modules linked in: nf_conntrack_netlink ebt_arp nft_compat nf_tables_set nft_meta_bridgel [Thu Sep 16 01:43:51 2021] ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_mi [Thu Sep 16 01:43:51 2021] CPU: 11 PID: 0 Comm: swapper/11 Not tainted 5.4.0-42-generic #46-Ubuntu [Thu Sep 16 01:43:51 2021] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017 [Thu Sep 16 01:43:51 2021] RIP: 0010:dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 1f f5 e7 00 01 e8 8d bb fa ff 44 89 e9 4c 89 fe 47 [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d466b4e30 EFLAGS: 00010286 [Thu Sep 16 01:43:51 2021] RAX: RBX: 9373ef57cec0 RCX: 083f [Thu Sep 16 01:43:51 2021] RDX: RSI: 00f6 RDI: 083f [Thu Sep 16 01:43:51 2021] RBP: b92d466b4e60 R08: 937bdf8d78c8 R09: 0004 [Thu Sep 16 01:43:51 2021] R10: R11: 0001 R12: 0040 [Thu Sep 16 01:43:51 2021] R13: 0022 R14: 9373ef580480 R15: 9373ef58 [Thu Sep 16 01:43:51 2021] FS: () GS:937bdf8c() knlGS: [Thu Sep 16 01:43:51 2021] CS: 0010 DS: ES: CR0: 80050033 [Thu Sep 16 01:43:51 2021] CR2: 7f3697ec19dc CR3: 00103ce0a001 CR4: 001626e0 [Thu Sep 16 01:43:51 2021] Call Trace: [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] ? pfifo_fast_enqueue+0x150/0x150 [Thu Sep 16 01:43:51 2021] call_timer_fn+0x32/0x130 [Thu Sep 16 01:43:51 2021] __run_timers.part.0+0x180/0x280 [Thu Sep 16 01:43:51 2021] ? tick_sched_handle+0x33/0x60 [Thu Sep 16 01:43:51 2021] ? tick_sched_timer+0x3d/0x80 [Thu Sep 16 01:43:51 2021] ? ktime_get+0x3e/0xa0 [Thu Sep 16 01:43:51 2021] run_timer_softirq+0x2a/0x50 [Thu Sep 16 01:43:51 2021] __do_softirq+0xe1/0x2d6 [Thu Sep 16 01:43:51 2021] ? hrtimer_interrupt+0x13b/0x220 [Thu Sep 16 01:43:51 2021] irq_exit+0xae/0xb0 [Thu Sep 16 01:43:51 2021] smp_apic_timer_interrupt+0x7b/0x140 [Thu Sep 16 01:43:51 2021] apic_timer_interrupt+0xf/0x20 [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [Thu Sep 16 01:43:51 2021] Code: ff e8 bf 08 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 0d [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d4634fe38 EFLAGS: 0246 ORIG_RAX: ff13 [Thu Sep 16 01:43:51 2021] RAX: 937bdf8ead00 RBX: 8d159c00 RCX: 001f [Thu Sep 16 01:43:51 2021] RDX: RSI: 3342629e RDI: [Thu Sep 16 01:43:51 2021] RBP: b92d4634fe78 R08: 0011dc129ea2a1f1 R09: 0011dc17357faf00 [Thu Sep 16 01:43:51 2021] R10: 937bdf8e9a00 R11: 937bdf8e99e0 R12: d9253fac20a8 [Thu Sep 16 01:43:51 2021] R13: 0004 R14: 0004 R15: d9253fac20a8 [Thu Sep 16 01:43:51 2021] ? cpuidle_enter_state+0xa1/0x450 [Thu Sep 16 01:43:51 2021] cpuidle_enter+0x2e/0x40 [Thu Sep 16 01:43:51 2021] call_cpuidle+0x23/0x40 [Thu Sep 16 01:43:51 2021] do_idle+0x1dd/0x270 [Thu Sep 16 01:43:51 2021] cpu_startup_entry+0x20/0x30 [Thu Sep 16 01:43:51 2021] start_secondary+0x167/0x1c0 [Thu Sep 16 01:43:51 2021] secondary_startup_64+0xa4/0xb0 [Thu Sep 16 01:43:51 2021] ---[ end trace cb80e9f61341ace0 ]--- [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: initiating reset due to tx timeout [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: Reset adapter [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: TXDCTL.ENABLE for one or more queues not
[Kernel-packages] [Bug 1943879] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1943879/+attachment/5525748/+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/1943879 Title: NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out Status in linux package in Ubuntu: Incomplete Bug description: I am running ubuntu Focal version with following kernel and NIC and noticed where strange error in kernel logs and my nic went down, does any one know about this? # uname -a Linux ostack-phx-comp-gen-1-27.v1v0x.net 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64x # lspci | grep -i eth 06:00.0 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) 06:00.1 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) [Thu Sep 16 01:43:51 2021] [ cut here ] [Thu Sep 16 01:43:51 2021] NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out [Thu Sep 16 01:43:51 2021] WARNING: CPU: 11 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Modules linked in: nf_conntrack_netlink ebt_arp nft_compat nf_tables_set nft_meta_bridgel [Thu Sep 16 01:43:51 2021] ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_mi [Thu Sep 16 01:43:51 2021] CPU: 11 PID: 0 Comm: swapper/11 Not tainted 5.4.0-42-generic #46-Ubuntu [Thu Sep 16 01:43:51 2021] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017 [Thu Sep 16 01:43:51 2021] RIP: 0010:dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 1f f5 e7 00 01 e8 8d bb fa ff 44 89 e9 4c 89 fe 47 [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d466b4e30 EFLAGS: 00010286 [Thu Sep 16 01:43:51 2021] RAX: RBX: 9373ef57cec0 RCX: 083f [Thu Sep 16 01:43:51 2021] RDX: RSI: 00f6 RDI: 083f [Thu Sep 16 01:43:51 2021] RBP: b92d466b4e60 R08: 937bdf8d78c8 R09: 0004 [Thu Sep 16 01:43:51 2021] R10: R11: 0001 R12: 0040 [Thu Sep 16 01:43:51 2021] R13: 0022 R14: 9373ef580480 R15: 9373ef58 [Thu Sep 16 01:43:51 2021] FS: () GS:937bdf8c() knlGS: [Thu Sep 16 01:43:51 2021] CS: 0010 DS: ES: CR0: 80050033 [Thu Sep 16 01:43:51 2021] CR2: 7f3697ec19dc CR3: 00103ce0a001 CR4: 001626e0 [Thu Sep 16 01:43:51 2021] Call Trace: [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] ? pfifo_fast_enqueue+0x150/0x150 [Thu Sep 16 01:43:51 2021] call_timer_fn+0x32/0x130 [Thu Sep 16 01:43:51 2021] __run_timers.part.0+0x180/0x280 [Thu Sep 16 01:43:51 2021] ? tick_sched_handle+0x33/0x60 [Thu Sep 16 01:43:51 2021] ? tick_sched_timer+0x3d/0x80 [Thu Sep 16 01:43:51 2021] ? ktime_get+0x3e/0xa0 [Thu Sep 16 01:43:51 2021] run_timer_softirq+0x2a/0x50 [Thu Sep 16 01:43:51 2021] __do_softirq+0xe1/0x2d6 [Thu Sep 16 01:43:51 2021] ? hrtimer_interrupt+0x13b/0x220 [Thu Sep 16 01:43:51 2021] irq_exit+0xae/0xb0 [Thu Sep 16 01:43:51 2021] smp_apic_timer_interrupt+0x7b/0x140 [Thu Sep 16 01:43:51 2021] apic_timer_interrupt+0xf/0x20 [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [Thu Sep 16 01:43:51 2021] Code: ff e8 bf 08 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 0d [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d4634fe38 EFLAGS: 0246 ORIG_RAX: ff13 [Thu Sep 16 01:43:51 2021] RAX: 937bdf8ead00 RBX: 8d159c00 RCX: 001f [Thu Sep 16 01:43:51 2021] RDX: RSI: 3342629e RDI: [Thu Sep 16 01:43:51 2021] RBP: b92d4634fe78 R08: 0011dc129ea2a1f1 R09: 0011dc17357faf00 [Thu Sep 16 01:43:51 2021] R10: 937bdf8e9a00 R11: 937bdf8e99e0 R12: d9253fac20a8 [Thu Sep 16 01:43:51 2021] R13: 0004 R14: 0004 R15: d9253fac20a8 [Thu Sep 16 01:43:51 2021] ? cpuidle_enter_state+0xa1/0x450 [Thu Sep 16 01:43:51 2021] cpuidle_enter+0x2e/0x40 [Thu Sep 16 01:43:51 2021] call_cpuidle+0x23/0x40 [Thu Sep 16 01:43:51 2021] do_idle+0x1dd/0x270 [Thu Sep 16 01:43:51 2021] cpu_startup_entry+0x20/0x30 [Thu Sep 16 01:43:51 2021] start_secondary+0x167/0x1c0 [Thu Sep 16 01:43:51 2021] secondary_startup_64+0xa4/0xb0 [Thu Sep 16 01:43:51 2021] ---[ end trace cb80e9f61341ace0 ]--- [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: initiating reset due to tx timeout [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: Reset adapter [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: TXDCTL.ENABLE for one or more queues not
[Kernel-packages] [Bug 1943879] 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 1943879 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 ** Tags added: focal -- 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/1943879 Title: NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out Status in linux package in Ubuntu: Incomplete Bug description: I am running ubuntu Focal version with following kernel and NIC and noticed where strange error in kernel logs and my nic went down, does any one know about this? # uname -a Linux ostack-phx-comp-gen-1-27.v1v0x.net 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64x # lspci | grep -i eth 06:00.0 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) 06:00.1 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) [Thu Sep 16 01:43:51 2021] [ cut here ] [Thu Sep 16 01:43:51 2021] NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out [Thu Sep 16 01:43:51 2021] WARNING: CPU: 11 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Modules linked in: nf_conntrack_netlink ebt_arp nft_compat nf_tables_set nft_meta_bridgel [Thu Sep 16 01:43:51 2021] ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_mi [Thu Sep 16 01:43:51 2021] CPU: 11 PID: 0 Comm: swapper/11 Not tainted 5.4.0-42-generic #46-Ubuntu [Thu Sep 16 01:43:51 2021] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017 [Thu Sep 16 01:43:51 2021] RIP: 0010:dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 1f f5 e7 00 01 e8 8d bb fa ff 44 89 e9 4c 89 fe 47 [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d466b4e30 EFLAGS: 00010286 [Thu Sep 16 01:43:51 2021] RAX: RBX: 9373ef57cec0 RCX: 083f [Thu Sep 16 01:43:51 2021] RDX: RSI: 00f6 RDI: 083f [Thu Sep 16 01:43:51 2021] RBP: b92d466b4e60 R08: 937bdf8d78c8 R09: 0004 [Thu Sep 16 01:43:51 2021] R10: R11: 0001 R12: 0040 [Thu Sep 16 01:43:51 2021] R13: 0022 R14: 9373ef580480 R15: 9373ef58 [Thu Sep 16 01:43:51 2021] FS: () GS:937bdf8c() knlGS: [Thu Sep 16 01:43:51 2021] CS: 0010 DS: ES: CR0: 80050033 [Thu Sep 16 01:43:51 2021] CR2: 7f3697ec19dc CR3: 00103ce0a001 CR4: 001626e0 [Thu Sep 16 01:43:51 2021] Call Trace: [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] ? pfifo_fast_enqueue+0x150/0x150 [Thu Sep 16 01:43:51 2021] call_timer_fn+0x32/0x130 [Thu Sep 16 01:43:51 2021] __run_timers.part.0+0x180/0x280 [Thu Sep 16 01:43:51 2021] ? tick_sched_handle+0x33/0x60 [Thu Sep 16 01:43:51 2021] ? tick_sched_timer+0x3d/0x80 [Thu Sep 16 01:43:51 2021] ? ktime_get+0x3e/0xa0 [Thu Sep 16 01:43:51 2021] run_timer_softirq+0x2a/0x50 [Thu Sep 16 01:43:51 2021] __do_softirq+0xe1/0x2d6 [Thu Sep 16 01:43:51 2021] ? hrtimer_interrupt+0x13b/0x220 [Thu Sep 16 01:43:51 2021] irq_exit+0xae/0xb0 [Thu Sep 16 01:43:51 2021] smp_apic_timer_interrupt+0x7b/0x140 [Thu Sep 16 01:43:51 2021] apic_timer_interrupt+0xf/0x20 [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [Thu Sep 16 01:43:51 2021] Code: ff e8 bf 08 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 0d [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d4634fe38 EFLAGS: 0246 ORIG_RAX: ff13 [Thu Sep 16 01:43:51 2021] RAX: 937bdf8ead00 RBX: 8d159c00 RCX: 001f [Thu Sep 16 01:43:51 2021] RDX: RSI: 3342629e RDI: [Thu Sep 16 01:43:51 2021] RBP: b92d4634fe78 R08: 0011dc129ea2a1f1 R09: 0011dc17357faf00 [Thu Sep 16 01:43:51 2021] R10: 937bdf8e9a00 R11: 937bdf8e99e0 R12: d9253fac20a8 [Thu Sep 16 01:43:51 2021] R13: 0004 R14: 0004 R15: d9253fac20a8 [Thu Sep 16 01:43:51 2021] ? cpuidle_enter_state+0xa1/0x450 [Thu Sep 16 01:43:51 2021] cpuidle_enter+0x2e/0x40 [Thu Sep 16 01:43:51 2021] call_cpuidle+0x23/0x40 [Thu Sep 16 01:43:51 2021] do_idle+0x1dd/0x270 [Thu Sep
[Kernel-packages] [Bug 1943879] [NEW] NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out
Public bug reported: I am running ubuntu Focal version with following kernel and NIC and noticed where strange error in kernel logs and my nic went down, does any one know about this? # uname -a Linux ostack-phx-comp-gen-1-27.v1v0x.net 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64x # lspci | grep -i eth 06:00.0 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) 06:00.1 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) [Thu Sep 16 01:43:51 2021] [ cut here ] [Thu Sep 16 01:43:51 2021] NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out [Thu Sep 16 01:43:51 2021] WARNING: CPU: 11 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Modules linked in: nf_conntrack_netlink ebt_arp nft_compat nf_tables_set nft_meta_bridgel [Thu Sep 16 01:43:51 2021] ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_mi [Thu Sep 16 01:43:51 2021] CPU: 11 PID: 0 Comm: swapper/11 Not tainted 5.4.0-42-generic #46-Ubuntu [Thu Sep 16 01:43:51 2021] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017 [Thu Sep 16 01:43:51 2021] RIP: 0010:dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 1f f5 e7 00 01 e8 8d bb fa ff 44 89 e9 4c 89 fe 47 [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d466b4e30 EFLAGS: 00010286 [Thu Sep 16 01:43:51 2021] RAX: RBX: 9373ef57cec0 RCX: 083f [Thu Sep 16 01:43:51 2021] RDX: RSI: 00f6 RDI: 083f [Thu Sep 16 01:43:51 2021] RBP: b92d466b4e60 R08: 937bdf8d78c8 R09: 0004 [Thu Sep 16 01:43:51 2021] R10: R11: 0001 R12: 0040 [Thu Sep 16 01:43:51 2021] R13: 0022 R14: 9373ef580480 R15: 9373ef58 [Thu Sep 16 01:43:51 2021] FS: () GS:937bdf8c() knlGS: [Thu Sep 16 01:43:51 2021] CS: 0010 DS: ES: CR0: 80050033 [Thu Sep 16 01:43:51 2021] CR2: 7f3697ec19dc CR3: 00103ce0a001 CR4: 001626e0 [Thu Sep 16 01:43:51 2021] Call Trace: [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] ? pfifo_fast_enqueue+0x150/0x150 [Thu Sep 16 01:43:51 2021] call_timer_fn+0x32/0x130 [Thu Sep 16 01:43:51 2021] __run_timers.part.0+0x180/0x280 [Thu Sep 16 01:43:51 2021] ? tick_sched_handle+0x33/0x60 [Thu Sep 16 01:43:51 2021] ? tick_sched_timer+0x3d/0x80 [Thu Sep 16 01:43:51 2021] ? ktime_get+0x3e/0xa0 [Thu Sep 16 01:43:51 2021] run_timer_softirq+0x2a/0x50 [Thu Sep 16 01:43:51 2021] __do_softirq+0xe1/0x2d6 [Thu Sep 16 01:43:51 2021] ? hrtimer_interrupt+0x13b/0x220 [Thu Sep 16 01:43:51 2021] irq_exit+0xae/0xb0 [Thu Sep 16 01:43:51 2021] smp_apic_timer_interrupt+0x7b/0x140 [Thu Sep 16 01:43:51 2021] apic_timer_interrupt+0xf/0x20 [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [Thu Sep 16 01:43:51 2021] Code: ff e8 bf 08 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 0d [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d4634fe38 EFLAGS: 0246 ORIG_RAX: ff13 [Thu Sep 16 01:43:51 2021] RAX: 937bdf8ead00 RBX: 8d159c00 RCX: 001f [Thu Sep 16 01:43:51 2021] RDX: RSI: 3342629e RDI: [Thu Sep 16 01:43:51 2021] RBP: b92d4634fe78 R08: 0011dc129ea2a1f1 R09: 0011dc17357faf00 [Thu Sep 16 01:43:51 2021] R10: 937bdf8e9a00 R11: 937bdf8e99e0 R12: d9253fac20a8 [Thu Sep 16 01:43:51 2021] R13: 0004 R14: 0004 R15: d9253fac20a8 [Thu Sep 16 01:43:51 2021] ? cpuidle_enter_state+0xa1/0x450 [Thu Sep 16 01:43:51 2021] cpuidle_enter+0x2e/0x40 [Thu Sep 16 01:43:51 2021] call_cpuidle+0x23/0x40 [Thu Sep 16 01:43:51 2021] do_idle+0x1dd/0x270 [Thu Sep 16 01:43:51 2021] cpu_startup_entry+0x20/0x30 [Thu Sep 16 01:43:51 2021] start_secondary+0x167/0x1c0 [Thu Sep 16 01:43:51 2021] secondary_startup_64+0xa4/0xb0 [Thu Sep 16 01:43:51 2021] ---[ end trace cb80e9f61341ace0 ]--- [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: initiating reset due to tx timeout [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: Reset adapter [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: TXDCTL.ENABLE for one or more queues not cleared within the pod [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: NIC Link is Up 10 Gbps, Flow Control: RX/TX [Thu Sep 16 01:43:52 2021] ixgbe :06:00.0 eno49: NIC Link is Down [Thu Sep 16 01:43:52 2021] bond0: (slave eno49): link status definitely down, disabling slave [Thu Sep 16 01:43:52 2021] bond0: (slave eno50): making interface the new active one [Thu Sep 16 01:43:52 2021] device eno49 left promiscuous mode [Thu Sep 16 01:43:52 2021] device eno50 entered promiscuous mode [Thu Sep 16 01:43:53 2021] ixgbe
[Kernel-packages] [Bug 1943832] Re: Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA)
Here's dmesg of recompiled kernel with CONFIG_KEYBOARD_ATKBD=m CONFIG_SERIO_I8042=m CONFIG_SERIO_LIBPS2=m ** Attachment added: "dmesg_recompiled.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943832/+attachment/5525740/+files/dmesg_recompiled.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/1943832 Title: Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA) Status in linux package in Ubuntu: Confirmed Bug description: ASUS UM425UA internal keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. I noticed it when tried to boot live image of Ubuntu 20.04.3 This problem probably appeared with kernel version 5.9 or 5.10 because with Ubuntu 20.04.2 live image (Linux 5.8) keyboard loads fine. Tried kernel 5.14 and it's still affected. I tried to recompile kernels 5.11 & 5.13 with SERIO_I8042 set as a module (as suggested in an Arch Linux bug report) and keyboard now works from the first start. In "make config" the changes are: Device Drivers -> > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for U14.04 > Input device support > Keyboards -> [M] AT keyboard > Hardware I/O ports -> [M] i8042 PC Keyboard controller It changed such lines in config: CONFIG_KEYBOARD_ATKBD=m CONFIG_SERIO_I8042=m CONFIG_SERIO_LIBPS2=m References: https://bugs.archlinux.org/task/70384 https://ubuntuforums.org/showthread.php?t=2459149 https://linux.org/threads/asus-zenbook-14-um425ua-keyboard-not-respond-during-cold-boot.33738/#post-133830 P.S. Other option which helped me was a GRUB parameter "i8042.reset=1" but it had a positive effect only with kernel 5.11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: 807 F pulseaudio /dev/snd/controlC2: 807 F pulseaudio /dev/snd/controlC1: 807 F pulseaudio /dev/snd/controlC0: 807 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-01 (14 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425UA_UM425UA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=3e7eadd0-dd33-487a-8e38-3e516c0dc8d5 ro quiet i8042.reset=1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.199 Tags: focal Uname: Linux 5.11.0-34-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: 04/01/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX425UA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425UA 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: 3.1 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX425UA.301:bd04/01/2021:br5.19:efr3.1:svnASUSTeKCOMPUTERINC.:pnZenBookUX425UA_UM425UA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX425UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425UA_UM425UA 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/1943832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928138] Re: Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bisected and workaround attached]
I changed that line so that it says: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash drm.debug=0x1e log_buf_len=4M" and follower the rest of the steps. when typing: sudo dmesg | grep "Refresh Rate" on the terminal, nothing really happens. I am not sure I am doing that last step well, since I checked the previous ones. -- 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/1928138 Title: Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bisected and workaround attached] Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Since kernel 4.1 laptop HP Elitebook Folio 1040 G1 (with Intel i5-4210U) has a pretty serious issue with flickering Symptoms: 1) If I leave mouse cursor for a few seconds, then start moving it, there's a slight flicker (like display brightness changes a bit). There's also some flickering even without user interactions. 2) On the top left corner sometimes appears artifacts. It's relatively easy to see with black window decorations on top of the screen. This one is showed at the attached video bellow 3) With kernel boot options drm.debug=0x1e log_buf_len=4M dmesg shows constant refresh rate changes (even if it's set to 40HZ) [ 29.977378] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 30.456537] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz [ 33.973392] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 35.055923] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz nomodeset boot option eliminates flickering Turns out Display Refresh Rate Switching (DRRS) feature doesn't work correctly here. It was implemented on kernels 4.0...4.1 but on a particular machine flickering started with 4.1. As a workaround I'm attaching a patch which disables DRRS by default and adds module parameter "enable_drrs" to activate it. It's made for kernel 5.12 and should work for older versions as well (tested with 5.11). Until this issue is resolved, please consider adding parameter to disable DRRS. Windows has such option on Intel® Graphics Command Center. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1928138/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943030] Re: Enable riscv64 build of nvidia-settings
** Changed in: nvidia-settings (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1943030 Title: Enable riscv64 build of nvidia-settings Status in nvidia-settings package in Ubuntu: In Progress Bug description: Please enable the build on riscv64 architecture of nvidia-settings since it works fine using the attached debdiff: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+build/22050736 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1943030/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943030] Re: Enable riscv64 build of nvidia-settings
Looking at the debian/control file we can see the package is built for arm64 and ppc64el and that this was deliberately added when Thomas was involved in Ubuntu development. nvidia-settings (367.35-0ubuntu1) yakkety; urgency=medium * debian/control: - Build for arm64 and ppc64el, even though we don't provide the driver for these architectures yet. * debian/patches/12_nostrip.patch, debian/patches/13_libxnvctrl_so_0.patch: - Refresh patches. -- Alberto Milone Tue, 09 Aug 2016 11:10:31 +0200 Given the precedent I'm going to go ahead and sponsor this. ** Changed in: nvidia-settings (Ubuntu) Status: Won't Fix => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1943030 Title: Enable riscv64 build of nvidia-settings Status in nvidia-settings package in Ubuntu: In Progress Bug description: Please enable the build on riscv64 architecture of nvidia-settings since it works fine using the attached debdiff: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+build/22050736 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1943030/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943832] Re: Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA)
Here's dmesg of kernel 5.11.0-34 with i8042.reset=1 ** Attachment added: "dmesg_with_i8042_reset.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943832/+attachment/5525734/+files/dmesg_with_i8042_reset.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/1943832 Title: Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA) Status in linux package in Ubuntu: Confirmed Bug description: ASUS UM425UA internal keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. I noticed it when tried to boot live image of Ubuntu 20.04.3 This problem probably appeared with kernel version 5.9 or 5.10 because with Ubuntu 20.04.2 live image (Linux 5.8) keyboard loads fine. Tried kernel 5.14 and it's still affected. I tried to recompile kernels 5.11 & 5.13 with SERIO_I8042 set as a module (as suggested in an Arch Linux bug report) and keyboard now works from the first start. In "make config" the changes are: Device Drivers -> > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for U14.04 > Input device support > Keyboards -> [M] AT keyboard > Hardware I/O ports -> [M] i8042 PC Keyboard controller It changed such lines in config: CONFIG_KEYBOARD_ATKBD=m CONFIG_SERIO_I8042=m CONFIG_SERIO_LIBPS2=m References: https://bugs.archlinux.org/task/70384 https://ubuntuforums.org/showthread.php?t=2459149 https://linux.org/threads/asus-zenbook-14-um425ua-keyboard-not-respond-during-cold-boot.33738/#post-133830 P.S. Other option which helped me was a GRUB parameter "i8042.reset=1" but it had a positive effect only with kernel 5.11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: 807 F pulseaudio /dev/snd/controlC2: 807 F pulseaudio /dev/snd/controlC1: 807 F pulseaudio /dev/snd/controlC0: 807 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-01 (14 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425UA_UM425UA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=3e7eadd0-dd33-487a-8e38-3e516c0dc8d5 ro quiet i8042.reset=1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.199 Tags: focal Uname: Linux 5.11.0-34-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: 04/01/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX425UA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425UA 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: 3.1 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX425UA.301:bd04/01/2021:br5.19:efr3.1:svnASUSTeKCOMPUTERINC.:pnZenBookUX425UA_UM425UA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX425UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425UA_UM425UA 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/1943832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928138] Re: Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bisected and workaround attached]
@alepasgar 1)Edit your GRUB configuration sudo nano /etc/default/grub At the line with "GRUB_CMDLINE_LINUX_DEFAULT" add parameters drm.debug=0x1e log_buf_len=4M Ctrl+X , confirm changes with "Y" 2) sudo update-grub 3) Restart 4) sudo dmesg | grep "Refresh Rate" -- 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/1928138 Title: Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bisected and workaround attached] Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Since kernel 4.1 laptop HP Elitebook Folio 1040 G1 (with Intel i5-4210U) has a pretty serious issue with flickering Symptoms: 1) If I leave mouse cursor for a few seconds, then start moving it, there's a slight flicker (like display brightness changes a bit). There's also some flickering even without user interactions. 2) On the top left corner sometimes appears artifacts. It's relatively easy to see with black window decorations on top of the screen. This one is showed at the attached video bellow 3) With kernel boot options drm.debug=0x1e log_buf_len=4M dmesg shows constant refresh rate changes (even if it's set to 40HZ) [ 29.977378] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 30.456537] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz [ 33.973392] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 35.055923] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz nomodeset boot option eliminates flickering Turns out Display Refresh Rate Switching (DRRS) feature doesn't work correctly here. It was implemented on kernels 4.0...4.1 but on a particular machine flickering started with 4.1. As a workaround I'm attaching a patch which disables DRRS by default and adds module parameter "enable_drrs" to activate it. It's made for kernel 5.12 and should work for older versions as well (tested with 5.11). Until this issue is resolved, please consider adding parameter to disable DRRS. Windows has such option on Intel® Graphics Command Center. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1928138/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943841] Re: svm from ubuntu_kvm_unit_tests interrupt with "Unhandled exception 13 #GP at ip 00000000004027e3" on F-intel-5.13
This issue can be reproduced on the same node gonzo with F-intel 5.13.0-1003.3 Therefore this is not a regression. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1943841 Title: svm from ubuntu_kvm_unit_tests interrupt with "Unhandled exception 13 #GP at ip 004027e3" on F-intel-5.13 Status in ubuntu-kernel-tests: New Status in linux-intel-5.13 package in Ubuntu: New Bug description: Failing with Focal Intel 5.13.0-1004.4 on node gonzo A bit like bug 1934939, but this time it looks like this has passed through more cases than that bug. Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/svm' BUILD_HEAD=1593e88a timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.8QIXdsXIyJ -smp 2 -cpu max,+svm -m 4g # -initrd /tmp/tmp.VvuuwXHRuX enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 10bf000 cr4 = 20 NPT detected - running all tests with NPT enabled PASS: null PASS: vmrun PASS: ioio PASS: vmrun intercept check PASS: rsm PASS: cr3 read intercept PASS: cr3 read nointercept PASS: cr3 read intercept emulate PASS: dr intercept check PASS: next_rip PASS: msr intercept check PASS: mode_switch PASS: asid_zero PASS: sel_cr0_bug PASS: npt_nx PASS: npt_np PASS: npt_us PASS: npt_rw PASS: npt_rw_pfwalk PASS: npt_l1mmio PASS: npt_rw_l1mmio PASS: tsc_adjust Latency VMRUN : max: 322434 min: 21233 avg: 36460 Latency VMEXIT: max: 298726 min: 16889 avg: 17717 PASS: latency_run_exit Latency VMRUN : max: 334040 min: 23446 avg: 36313 Latency VMEXIT: max: 310725 min: 16935 avg: 17618 PASS: latency_run_exit_clean Latency VMLOAD: max: 732466 min: 4675 avg: 4879 Latency VMSAVE: max: 60901 min: 4565 avg: 4850 Latency STGI: max: 43057 min: 3726 avg: 3862 Latency CLGI: max: 723675 min: 3644 avg: 3724 PASS: latency_svm_insn PASS: exception with vector 2 not injected PASS: divide overflow exception injected PASS: eventinj.VALID cleared PASS: exc_inject PASS: pending_event PASS: pending_event_cli PASS: direct interrupt while running guest PASS: intercepted interrupt while running guest PASS: direct interrupt + hlt PASS: intercepted interrupt + hlt PASS: interrupt PASS: direct NMI while running guest PASS: NMI intercept while running guest PASS: nmi PASS: direct NMI + hlt PASS: NMI intercept while running guest PASS: intercepted NMI + hlt PASS: nmi_hlt PASS: virq_inject PASS: No RIP corruption detected after 1 timer interrupts PASS: reg_corruption enabling apic PASS: svm_init_startup_test PASS: host_rflags PASS: CPUID.01H:ECX.XSAVE set before VMRUN PASS: svm_cr4_osxsave_test_guest finished with VMMCALL PASS: CPUID.01H:ECX.XSAVE set after VMRUN PASS: EFER.SVME: 1500 PASS: EFER.SVME: 500 PASS: Test EFER 9:8: 1700 PASS: Test EFER 63:16: 11500 PASS: Test EFER 63:16: 101500 PASS: Test EFER 63:16: 1001500 PASS: Test EFER 63:16: 10001500 PASS: Test EFER 63:16: 11500 PASS: Test EFER 63:16: 101500 PASS: Test EFER 63:16: 1001500 PASS: Test EFER 63:16: 10001500 PASS: Test EFER 63:16: 11500 PASS: Test EFER 63:16: 101500 PASS: Test EFER 63:16: 1001500 PASS: Test EFER 63:16: 10001500 PASS: EFER.LME=1 (1500), CR0.PG=1 (80010011) and CR4.PAE=0 (4) PASS: EFER.LME=1 (1500), CR0.PG=1 and CR0.PE=0 (80010010) PASS: EFER.LME=1 (1500), CR0.PG=1 (80010011), CR4.PAE=1 (40020), CS.L=1 and CS.D=1 (699) PASS: Test CR0 CD=1,NW=0: c0010011 PASS: Test CR0 CD=1,NW=1: e0010011 PASS: Test CR0 CD=0,NW=0: 80010011 PASS: Test CR0 CD=0,NW=1: a0010011 PASS: Test CR0 63:32: 180010011 PASS: Test CR0 63:32: 1080010011 PASS: Test CR0 63:32: 10080010011 PASS: Test CR0 63:32: 100080010011 PASS: Test CR0 63:32: 180010011 PASS: Test CR0 63:32: 1080010011 PASS: Test CR0 63:32: 10080010011 PASS: Test CR0 63:32: 100080010011 PASS: Test CR3 63:0: 10010bf000, wanted exit 0x, got 0x PASS: Test CR3 63:0: 20010bf000, wanted exit 0x, got 0x PASS: Test CR3 63:0: 40010bf000, wanted exit 0x, got 0x PASS: Test CR3 63:0: 80010bf000, wanted exit 0x, got 0x PASS: Test CR3 63:0: 100010bf000, wanted exit 0x, got 0x PASS: Test CR3 63:0: 200010bf000, wanted exit 0x, got 0x PASS: Test CR3 63:0: 400010bf000, wanted exit 0x, got 0x PASS: Test CR3 63:0: 800010bf000, wanted exit
[Kernel-packages] [Bug 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1])
About this latest comment. So, CPU #0 has crashed at pc = c00813566eb8, its ctr and r12 match, same as usual, it was called by __bpf_prog_run_save_cb as the BPF JITed program. Dumping the program from CPU #0 perspective, it has traps at that address. It turns out the JIT fills up a whole page with traps and puts the JITed BPF program on a random offset of that page (look at kernel/bpf/core.c:bpf_jit_binary_alloc). When we go to the hotplugged CPU, however, CPU #9f (159), that same page looks different, with the code placed where it was expected. Still, it looks like fp->aux->jit_data is NULL on both CPUs, which is not as expected. I am wondering if either the icache is not being flushed properly, or RCU is not operating correctly. As other issues are not seen, more likely something related to the icache. But I don't see any IPIs involved when flushing the icache, so possibly firmware or micro- architecture related? Cascardo. -- 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/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1]) Status in ubuntu-kernel-tests: New Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Status in linux source package in Hirsute: Confirmed Bug description: It looks like our P8 node "entei" tend to fail with the IPv6 TCP test from reuseport_bpf_cpu in ubuntu_kernel_selftests/net on 5.8 kernels: # send cpu 119, receive socket 119 # send cpu 121, receive socket 121 # send cpu 123, receive socket 123 # send cpu 125, receive socket 125 # send cpu 127, receive socket 127 # IPv6 TCP publish-job-status: using request.json It failed silently here, this can be 100% reproduced with Groovy 5.8 and Focal 5.8. This will cause the ubuntu_kernel_selftests being interrupted, the test result for other tests cannot be processed to our result page. Please find attachment for the complete "net" test result on this node with Groovy 5.8.0-52.59 Add the kqa-blocker tag as this might needs to be manually verified. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943684] Re: upgrading from 1.187.15 -> 1.187.16 breaks iwlwifi for intel 8260
Tried an Intel 8260 module [8086:24F3] subsystem [8086:0010] on a Intel Comet Lake platform with kernel 5.6-oem, 5.8, 5.11. All works just fine with linux-firmware version 1.187.17. While its firmware, iwlwifi-8000C-36.ucode, has never ever been updated since linux-firmware/focal was released, we'll need complete information of your system for further inspection. $ md5sum iwlwifi-8000C-* fd0ac79f34b10ce98d58100b509be73f iwlwifi-8000C-13.ucode 2d2b06c5644c9d718e7c0495aafa215b iwlwifi-8000C-16.ucode d7c59c75d442b6c0a10cb7505ca2dd6a iwlwifi-8000C-21.ucode 2d192842e3d76c574ab1a4513d06000a iwlwifi-8000C-22.ucode dbed38f155cada773ebdfb78ed4f5ebc iwlwifi-8000C-27.ucode 6b201b78799a78d154bfdd67e12792f0 iwlwifi-8000C-31.ucode 6bdfcdc1b5564504f0a8ff2de21b172a iwlwifi-8000C-34.ucode e4d63f8eaaf9d03d0c1dcfb3af435e48 iwlwifi-8000C-36.ucode -- 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/1943684 Title: upgrading from 1.187.15 -> 1.187.16 breaks iwlwifi for intel 8260 Status in linux-firmware package in Ubuntu: Incomplete Bug description: After a reboot my wifi suddenly didn't work anymore, dmesg showed: [8.711330] iwlwifi :04:00.0: SecBoot CPU1 Status: 0x3040001, CPU2 Status: 0x0 [8.711336] iwlwifi :04:00.0: Collecting data: trigger 15 fired. [8.960114] iwlwifi :04:00.0: Not valid error log pointer 0x for Init uCode [8.960236] iwlwifi :04:00.0: Fseq Registers: [8.960285] iwlwifi :04:00.0: 0x355FFACF | FSEQ_ERROR_CODE [8.960340] iwlwifi :04:00.0: 0x5E555D0C | FSEQ_TOP_INIT_VERSION [8.960390] iwlwifi :04:00.0: 0x00440480 | FSEQ_CNVIO_INIT_VERSION [8.960439] iwlwifi :04:00.0: 0xA056 | FSEQ_OTP_VERSION [8.960488] iwlwifi :04:00.0: 0xBA8CC809 | FSEQ_TOP_CONTENT_VERSION [8.960537] iwlwifi :04:00.0: 0xBF49711A | FSEQ_ALIVE_TOKEN [8.960586] iwlwifi :04:00.0: 0x823938D2 | FSEQ_CNVI_ID [8.960635] iwlwifi :04:00.0: 0x01B9E7F7 | FSEQ_CNVR_ID [8.960684] iwlwifi :04:00.0: 0x0300 | CNVI_AUX_MISC_CHIP [8.960734] iwlwifi :04:00.0: 0x0BADCAFE | CNVR_AUX_MISC_CHIP [8.960783] iwlwifi :04:00.0: 0x0BADCAFE | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM [8.960841] iwlwifi :04:00.0: 0x0BADCAFE | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR [8.960891] iwlwifi :04:00.0: Failed to start INIT ucode: -110 [8.960903] iwlwifi :04:00.0: Collecting data: trigger 16 fired. [9.994975] iwlwifi :04:00.0: Failed to run INIT ucode: -110 first I thought it was something with secure boot however I didn't change anything in the bios and checking showed that it is infact disabled, also running sudo mokutil --sb-state shows SecureBoot disabled anyways I found out that I had an update of the package linux-firmware from 1.187.16 to 1.187.15 the day before. Downgrading to 1.187 (for unknown reason I couldn't find the binary of the old version 1.187.15 on my notebook nor on the internet
[Kernel-packages] [Bug 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1])
9f:mon> di c00813566000 1000 c00813566000 7fe8 trap ... c00813566eb8 6000 nop ... c00813566ec0 7c0802a6 mflrr0 c00813566ec4 f8010010 std r0,16(r1) c00813566ec8 f821ffa1 stdur1,-96(r1) c00813566ecc 3d80c000 lis r12,-16384 c00813566ed0 798c07c6 rldicr r12,r12,32,31 c00813566ed4 658c0036 orisr12,r12,54 c00813566ed8 618c51e0 ori r12,r12,20960 c00813566edc 7d8903a6 mtctr r12 c00813566ee0 4e800421 bctrl c00813566ee4 7c681b78 mr r8,r3 c00813566ee8 38210060 addir1,r1,96 c00813566eec e8010010 ld r0,16(r1) c00813566ef0 7c0803a6 mtlrr0 c00813566ef4 7d034378 mr r3,r8 c00813566ef8 4e800020 blr c00813566efc 7fe8 trap ... 9f:mon> r R00 = c00173d8 R16 = c07fe13e8cb0 R01 = c040074efda0 R17 = c07f8f6a R02 = c22d9900 R18 = c07f8f6a0080 R03 = c040074efbd8 R19 = c07f8f6a0080 R04 = 0020 R20 = c12ff767 R05 = 0003 R21 = c07f8f6a0080 R06 = 0002 R22 = c136cc78 R07 = 00517782 R23 = 0001 R08 = 001ebf7e3a55 R24 = 009f R09 = R25 = 0e60 R10 = 0001 R26 = 0900 R11 = 0f8e R27 = 0500 R12 = 4400 R28 = 0a00 R13 = c07fff6f4f80 R29 = 0f00 R14 = R30 = 0002 R15 = c12f6020 R31 = 0003 pc = c0017038 replay_soft_interrupts+0x68/0x2e0 cfar= lr = c00173d8 arch_local_irq_restore+0x128/0x160 msr = 90001033 cr = 24004428 ctr = c0042468 xer = 2000 trap = 500 9f:mon> c0 [link register ] c0f36d4c __bpf_prog_run_save_cb+0x5c/0x190 [c03a3780] c0fdf76c __ip_finish_output+0x8c/0x140 (unreliable) [c03a37f0] c0f36f2c run_bpf_filter+0xac/0x200 [c03a3850] c0f37104 reuseport_select_sock+0x84/0x170 [c03a3890] c112c1f8 inet6_lhash2_lookup+0x1c8/0x200 [c03a3910] c112c48c inet6_lookup_listener+0x25c/0x280 [c03a3a00] c1105e58 tcp_v6_rcv+0x7b8/0xf50 [c03a3b50] c10b79c0 ip6_protocol_deliver_rcu+0x110/0x630 [c03a3bc0] c10b803c ip6_input+0x10c/0x130 [c03a3c40] c10b76c4 ipv6_rcv+0x194/0x1c0 [c03a3cc0] c0ef68f4 __netif_receive_skb_one_core+0x74/0xb0 [c03a3d10] c0ef6d68 process_backlog+0x138/0x280 [c03a3d80] c0ef7e00 napi_poll+0x100/0x3c0 [c03a3e10] c0ef81b4 net_rx_action+0xf4/0x2d0 [c03a3ea0] c11815f0 __do_softirq+0x150/0x428 [c03a3f90] c002caec call_do_softirq+0x14/0x24 [c8fcf630] c0017448 do_softirq_own_stack+0x38/0x50 [c8fcf650] c01640a0 do_softirq+0xa0/0xb0 [c8fcf680] c01641a8 __local_bh_enable_ip+0xf8/0x120 [c8fcf6a0] c10b1a98 ip6_finish_output2+0x248/0x7c0 [c8fcf740] c10b1410 ip6_xmit+0x370/0x7b0 [c8fcf860] c110f7f4 inet6_csk_xmit+0xb4/0x130 [c8fcf900] c100e910 __tcp_transmit_skb+0x440/0x9f0 [c8fcfa10] c100f758 tcp_connect+0x2e8/0x390 [c8fcfae0] c11023e4 tcp_v6_connect+0x5e4/0x7b0 [c8fcfbd0] c1042e10 __inet_stream_connect+0x130/0x3a0 [c8fcfc30] c10430dc inet_stream_connect+0x5c/0x90 [c8fcfc70] c0eb8e58 __sys_connect_file+0xa8/0xe0 [c8fcfcb0] c0eb8f74 __sys_connect+0xe4/0x140 [c8fcfd90] c0eb8ff8 sys_connect+0x28/0x40 [c8fcfdb0] c0036fe4 system_call_exception+0xf4/0x200 [c8fcfe10] c000d860 system_call_common+0xf0/0x27c --- Exception: c00 (System Call) at 7cf993a78388 SP (712cb970) is in userspace 0:mon> r R00 = c0f36f2c R16 = ada3 R01 = c03a3780 R17 = 000a R02 = c22d9900 R18 = 0001 R03 = c00037c930e0 R19 = 0001 R04 = c00813110038 R20 = c040213f4d48 R05 = c0081311 R21 = R06 = c00037c930e0 R22 = 22b9 R07 = 0001 R23 = 0001 R08 = 0001 R24 = ada3 R09 = R25 = c0081311 R10 = c0011c2edf00 R26 = R11 = R27 = 00a0 R12 = c00813566eb8 R28 = c00037c930e0 R13 = c259 R29 = 0028 R14 = c21fa500 R30 = 0028 R15 = 22b9 R31 = c0081311 pc = c00813566eb8 cfar= c0f36d48 __bpf_prog_run_save_cb+0x58/0x190 lr = c0f36d4c __bpf_prog_run_save_cb+0x5c/0x190 msr = 90029033 cr =
[Kernel-packages] [Bug 1940780] Re: [HP EliteBook Folio G1] Screen keeps flickering on ubuntu 20.04
Hello Alejandro, I notified them about the bug & they are aware of it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1940780 Title: [HP EliteBook Folio G1] Screen keeps flickering on ubuntu 20.04 Status in linux-hwe-5.11 package in Ubuntu: Incomplete Bug description: Just installed ubuntu 20.04 and the screen has been flickering all through. tried applying the ubuntu on Wayland solution but no change. Please help with a solution on workaround for this. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 22 21:39:46 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 515 [8086:191e] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 515 [103c:8170] InstallationDate: Installed on 2021-08-22 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP EliteBook Folio G1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=4b37b99a-c4bf-42ca-9e24-733b7a991c4d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2016 dmi.bios.release: 1.10 dmi.bios.vendor: HP dmi.bios.version: N91 Ver. 01.10 dmi.board.name: 8170 dmi.board.vendor: HP dmi.board.version: KBC Version 29.68 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 41.104 dmi.modalias: dmi:bvnHP:bvrN91Ver.01.10:bd07/19/2016:br1.10:efr41.104:svnHP:pnHPEliteBookFolioG1:pvr:rvnHP:rn8170:rvrKBCVersion29.68:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook Folio G1 dmi.product.sku: Z5Z39US#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1940780/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943030] Re: Enable riscv64 build of nvidia-settings
*TECHNICALLY* you aren't wrong. However, let's consider that I"ve been around since 2009 in the Ubuntu world (2012 when I started deep diving into it technically) and NVIDIA has *never* provided any drivers binary or otherwise that work on non-x86 infras. I don't see any time yet that NVIDIA is going to change that. Therefore, unless NVIDIA ships drivers, making the tool functional in RISCv is 'not useful' and is simply going to open us to the risk of more bugs of "This isn't working". One of the requirements for sponsoring and enabling packages for other archs is "Is it going to prove useful?" And currently, this is not going to prove useful unless NVIDIA decides to start distributing binaries for alternate architectures (which I don't think they even have graphics cards compatible with the other archs). If NVIDIA decides to publish RISCv binaries in the future this can be revisited. However, rejecting now on the basis as stated above. ** Changed in: nvidia-settings (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1943030 Title: Enable riscv64 build of nvidia-settings Status in nvidia-settings package in Ubuntu: Won't Fix Bug description: Please enable the build on riscv64 architecture of nvidia-settings since it works fine using the attached debdiff: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+build/22050736 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1943030/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928138] Re: Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bisected and workaround attached]
Hello there, I am having a problem that sounds quite similar to yours. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940285 Could you tell me what exactly I must type on terminal to check how my laptop's refresh rate changes (if any), just to check if it behaves like yours. Thank you. -- 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/1928138 Title: Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bisected and workaround attached] Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Since kernel 4.1 laptop HP Elitebook Folio 1040 G1 (with Intel i5-4210U) has a pretty serious issue with flickering Symptoms: 1) If I leave mouse cursor for a few seconds, then start moving it, there's a slight flicker (like display brightness changes a bit). There's also some flickering even without user interactions. 2) On the top left corner sometimes appears artifacts. It's relatively easy to see with black window decorations on top of the screen. This one is showed at the attached video bellow 3) With kernel boot options drm.debug=0x1e log_buf_len=4M dmesg shows constant refresh rate changes (even if it's set to 40HZ) [ 29.977378] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 30.456537] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz [ 33.973392] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 35.055923] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz nomodeset boot option eliminates flickering Turns out Display Refresh Rate Switching (DRRS) feature doesn't work correctly here. It was implemented on kernels 4.0...4.1 but on a particular machine flickering started with 4.1. As a workaround I'm attaching a patch which disables DRRS by default and adds module parameter "enable_drrs" to activate it. It's made for kernel 5.12 and should work for older versions as well (tested with 5.11). Until this issue is resolved, please consider adding parameter to disable DRRS. Windows has such option on Intel® Graphics Command Center. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1928138/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943782] Re: Ubuntu does not boot on kernel 5.14.4
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943782 Title: Ubuntu does not boot on kernel 5.14.4 Status in linux package in Ubuntu: Invalid Bug description: I built linux 5.14.4 from kernel.org on my Dell XPS 7590, but Ubuntu 21.04 fails to load if I boot into it, getting stuck on "Loading initial ramdisk" even when using verbose mode and recovery mode. It never moves past this point and I end up having to hard reboot the laptop into a stable kernel. I made them into a package for easy installation/uninstallation. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ian5081 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-22 (56 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 15 7590 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=7cce21e7-6064-4d17-9431-1c4fd9ccea0e ro mem_sleep_default=deep dis_ucode_ldr ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.197.3 Tags: hirsute Uname: Linux 5.11.0-34-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: 07/22/2021 dmi.bios.release: 1.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd07/22/2021:br1.13:svnDellInc.:pnXPS157590:pvr:sku0905:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943624] Re: Driver r8169 causes very slow download speed due to ASPM
Ok, installed and booted off the oem kernel without the pcie_asm kernel parameter and the speedtest-cli results are promising. uname -r 5.13.0-1012-oem Output from 'speedtest-cli': Retrieving speedtest.net configuration... Testing from XX ()... Retrieving speedtest.net server list... Selecting best server based on ping... Hosted by Totalplay (Toluca) [249.28 km]: 16.321 ms Testing download speed Download: 197.65 Mbit/s Testing upload speed.. Upload: 105.19 Mbit/s And output from 'ethtool -S enp3s0' doesn't show any rx_missed packets. ethtool -S enp3s0 NIC statistics: tx_packets: 351099 rx_packets: 445611 tx_errors: 0 rx_errors: 0 rx_missed: 0 align_errors: 0 tx_single_collisions: 0 tx_multi_collisions: 0 unicast: 445185 broadcast: 276 multicast: 150 tx_aborted: 0 tx_underrun: 0 Output from 'ethtool enp3s0': ethtool enp3s0 Settings for enp3s0: Supported ports: [ TPMII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Link partner advertised link modes: 100baseT/Half 100baseT/Full 1000baseT/Full Link partner advertised pause frame use: No Link partner advertised auto-negotiation: Yes Link partner advertised FEC modes: Not reported Speed: 1000Mb/s Duplex: Full Auto-negotiation: on master-slave cfg: preferred slave master-slave status: master Port: Twisted Pair PHYAD: 0 Transceiver: external MDI-X: Unknown Supports Wake-on: pumbg Wake-on: d Link detected: yes Output from lspci -vnvn -s 03:00.0: 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15) Subsystem: Lenovo RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [17aa:3835] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/bugs/1943624 Title: Driver r8169 causes very slow download speed due to ASPM Status in linux package in Ubuntu: Confirmed Bug description: Running Ubuntu Server 21.04 (kernel 5.11.0-34-generic) and have run into a serious network issue where the internet download speed is around 25Mbps on a 150Mbps connection! My setup: Lenovo Ideapad 300S with a wired Ethernet connection. Running Ubuntu Server 21.04 (kernel version 5.11.0-34-generic). Wired Ethernet connection with RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (r8169) driver. My contract with the ISP is for a 150Mbps download speed. My problem: The download speed is extremely low, around 25Mbps whereas my upload speed is 'normal' around 80-90Mbps. I use 'speedtest-cli' for measuring the bandwidth, by the way. This problem does not happen on an Acer Aspire One laptop running the same kernel and connected to the same router. After scouring through countless articles, I noticed that there were lot of issues with the r8169 driver and the RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller subsystem. What eventually fixed the issue for me was setting the "pcie_aspm=off" kernel parameter during boot. But I strongly feel that is a 'workaround' and not a solution to the real problem, which is the r8169 driver has regression with newer kernels, hence filing this bug. Thanks in advance for all your support! I'm a big fan of Ubuntu!!! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-34-generic 5.11.0-34.36 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.11.0-34-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2',
[Kernel-packages] [Bug 1882669] Re: Focal / Groovy aws and azure instances crash with ftracetest in ubuntu_kernel_selftests and ubuntu_ftrace_smoke_test
** Tags added: hinted -- 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/1882669 Title: Focal / Groovy aws and azure instances crash with ftracetest in ubuntu_kernel_selftests and ubuntu_ftrace_smoke_test Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Confirmed Status in linux-azure source package in Focal: Confirmed Status in linux-azure source package in Groovy: Fix Released Bug description: Issue found on 5.4.0-1013.13 The ftrace in ubuntu_kernel_selftests failed on the second test: # === Ftrace unit tests === # [1] Basic trace file check [PASS] # [2] Basic test for tracers (System hang here) Syslog: kernel: [ 2234.408225] in mmio_trace_init kernel: [ 2234.988256] mmiotrace: Disabling non-boot CPUs... kernel: [ 2235.028451] mmiotrace: Error taking CPU1 down: -16 kernel: [ 2235.052564] mmiotrace: Error taking CPU2 down: -16 kernel: [ 2235.076593] mmiotrace: Error taking CPU3 down: -16 kernel: [ 2235.096576] mmiotrace: Error taking CPU4 down: -16 kernel: [ 2235.116487] mmiotrace: Error taking CPU5 down: -16 kernel: [ 2235.132446] mmiotrace: Error taking CPU6 down: -16 kernel: [ 2235.152488] mmiotrace: Error taking CPU7 down: -16 kernel: [ 2235.172526] mmiotrace: Error taking CPU8 down: -16 kernel: [ 2235.192486] mmiotrace: Error taking CPU9 down: -16 kernel: [ 2235.212455] mmiotrace: Error taking CPU10 down: -16 kernel: [ 2235.233020] mmiotrace: Error taking CPU11 down: -16 kernel: [ 2235.256355] mmiotrace: Error taking CPU12 down: -16 kernel: [ 2235.272473] mmiotrace: Error taking CPU13 down: -16 kernel: [ 2235.292393] mmiotrace: Error taking CPU14 down: -16 kernel: [ 2235.312426] mmiotrace: Error taking CPU15 down: -16 kernel: [ 2235.344407] mmiotrace: Error taking CPU16 down: -16 kernel: [ 2235.380494] mmiotrace: Error taking CPU17 down: -16 kernel: [ 2235.400319] mmiotrace: Error taking CPU18 down: -16 kernel: [ 2235.432631] mmiotrace: Error taking CPU19 down: -16 kernel: [ 2235.456453] mmiotrace: Error taking CPU20 down: -16 kernel: [ 2235.480432] mmiotrace: Error taking CPU21 down: -16 kernel: [ 2235.496501] mmiotrace: Error taking CPU22 down: -16 kernel: [ 2235.516442] mmiotrace: Error taking CPU23 down: -16 kernel: [ 2235.536394] mmiotrace: Error taking CPU24 down: -16 kernel: [ 2235.556489] mmiotrace: Error taking CPU25 down: -16 kernel: [ 2235.573759] smpboot: CPU 26 is now offline kernel: [ 2235.575071] mmiotrace: CPU26 is down. kernel: [ 2235.585643] smpboot: CPU 27 is now offline kernel: [ 2235.586699] mmiotrace: CPU27 is down. kernel: [ 2235.609679] smpboot: CPU 28 is now offline kernel: [ 2235.610788] mmiotrace: CPU28 is down. kernel: [ 2235.633530] smpboot: CPU 29 is now offline kernel: [ 2235.634511] mmiotrace: CPU29 is down. kernel: [ 2235.653652] smpboot: CPU 30 is now offline kernel: [ 2235.655415] mmiotrace: CPU30 is down. kernel: [ 2235.678126] smpboot: CPU 31 is now offline kernel: [ 2235.679061] mmiotrace: CPU31 is down. kernel: [ 2235.679062] mmiotrace: multiple CPUs still online, may miss events. kernel: [ 2235.679063] mmiotrace: enabled. kernel: [ 2235.679128] in mmio_trace_reset kernel: [ 2235.696163] mmiotrace: Re-enabling CPUs... kernel: [ 2235.732157] mmiotrace: enabled CPU1. kernel: [ 2235.772207] mmiotrace: enabled CPU2. kernel: [ 2235.812216] mmiotrace: enabled CPU3. kernel: [ 2235.844220] mmiotrace: enabled CPU4. kernel: [ 2235.876211] mmiotrace: enabled CPU5. kernel: [ 2235.916159] mmiotrace: enabled CPU6. kernel: [ 2235.956214] mmiotrace: enabled CPU7. kernel: [ 2235.988145] mmiotrace: enabled CPU8. kernel: [ 2236.020214] mmiotrace: enabled CPU9. kernel: [ 2236.060207] mmiotrace: enabled CPU10. kernel: [ 2236.096208] mmiotrace: enabled CPU11. kernel: [ 2236.128205] mmiotrace: enabled CPU12. /usr/sbin/irqbalance: WARNING, didn't collect load info for all cpus, balancing is broken kernel: [ 2236.168204] mmiotrace: enabled CPU13. kernel: [ 2236.200206] mmiotrace: enabled CPU14. kernel: [ 2236.232207] mmiotrace: enabled CPU15. kernel: [ 2236.264224] mmiotrace: enabled CPU16. kernel: [ 2236.300207] mmiotrace: enabled CPU17. kernel: [ 2236.332210] mmiotrace: enabled CPU18. kernel: [ 2236.372224] mmiotrace: enabled CPU19. kernel: [ 2236.404147] mmiotrace: enabled CPU20. kernel: [ 2236.452153] mmiotrace: enabled CPU21. kernel: [ 2236.492152] mmiotrace: enabled CPU22. kernel: [ 2236.524153] mmiotrace: enabled CPU23. kernel: [ 2236.564211] mmiotrace: enabled CPU24. kernel: [ 2236.612204] mmiotrace: enabled CPU25. kernel: [ 2236.644353] smpboot: Booting Node 0 Processor 26 APIC 0x1a kernel: [ 2236.645769] mmiotrace: enabled CPU26. kernel: [ 2236.684537] smpboot: Booting Node 0 Processor 27 APIC 0x1b kernel: [
[Kernel-packages] [Bug 1882669] Re: Focal / Groovy aws and azure instances crash with ftracetest in ubuntu_kernel_selftests and ubuntu_ftrace_smoke_test
ubuntu_ftrace_smoke_test on all v5.4 kernels on all Azure instances
hangs:
114 11:22:52 INFO | Writing results to
/home/azure/autotest/client/results/default
115 11:22:52 DEBUG| Initializing the state engine
116 11:22:52 DEBUG| Persistent state client.steps now set to []
117 11:22:52 DEBUG| Persistent option harness now set to None
118 11:22:52 DEBUG| Persistent option harness_args now set to None
119 11:22:52 DEBUG| Selected harness: standalone
120 11:22:52 INFO | START timestamp=1631791372 localtime=Sep 16
11:22:52
121 11:22:52 DEBUG| Persistent state client._record_indent now set to 1
122 11:22:52 DEBUG| Test has timeout: 900 sec.
123 11:22:52 INFO | START ubuntu_ftrace_smoke_test.ftrace-smoke-test
ubuntu_ftrace_smoke_test.ftrace-smoke-test timestamp=1631791372 timeout=900
localtime=Sep 16 11:22:52
124 11:22:52 DEBUG| Persistent state client._record_indent now set to 2
125 11:22:52 DEBUG| Persistent state client.unexpected_reboot now set to
('ubuntu_ftrace_smoke_test.ftrace-smoke-test',
'ubuntu_ftrace_smoke_test.ftrace-smoke-test')
126 11:22:52 DEBUG| Waiting for pid 2953 for 900 seconds
127 11:22:52 DEBUG| Running
'/home/azure/autotest/client/tests/ubuntu_ftrace_smoke_test/ubuntu_ftrace_smoke_test.sh'
128 11:22:52 DEBUG| [stdout] PASSED (CONFIG_FUNCTION_TRACER=y in
/boot/config-5.4.0-1059-azure)
129 11:22:52 DEBUG| [stdout] PASSED (CONFIG_FUNCTION_GRAPH_TRACER=y in
/boot/config-5.4.0-1059-azure)
130 11:22:52 DEBUG| [stdout] PASSED (CONFIG_STACK_TRACER=y in
/boot/config-5.4.0-1059-azure)
131 11:22:52 DEBUG| [stdout] PASSED (CONFIG_DYNAMIC_FTRACE=y in
/boot/config-5.4.0-1059-azure)
132 11:22:54 DEBUG| [stdout] PASSED all expected /sys/kernel/debug/tracing
files exist
133 11:22:54 DEBUG| [stdout] PASSED (function_graph in
/sys/kernel/debug/tracing/available_tracers)
134 11:22:54 DEBUG| [stdout] PASSED (function in
/sys/kernel/debug/tracing/available_tracers)
135 11:22:54 DEBUG| [stdout] PASSED (nop in
/sys/kernel/debug/tracing/available_tracers)
136 11:22:57 DEBUG| [stdout] PASSED (tracer function can be enabled)
Found on Azure clouds:
* focal/linux/5.4.0-85.95
* focal/linux-azure/5.4.0-1059.62
* bionic/linux-azure-5.4/5.4.0-1059.62~18.04.1
* SRU cycles: 2021.08.16, 2021.07.19, 2021.05.31 (not checked earlier)
Not found:
* Other clouds.
* Azure: hirsute/linux/5.11.0-35.37
* Azure: focal/linux-azure-5.11/5.11.0-1016.17~20.04.1
* Azure: focal/linux-azure-5.8/5.8.0-1042.45~20.04.1
* Azure: bionic/linux-azure-4.15/4.15.0-1124.137
--
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/1882669
Title:
Focal / Groovy aws and azure instances crash with ftracetest in
ubuntu_kernel_selftests and ubuntu_ftrace_smoke_test
Status in ubuntu-kernel-tests:
New
Status in linux-aws package in Ubuntu:
Confirmed
Status in linux-azure package in Ubuntu:
Confirmed
Status in linux-azure source package in Focal:
Confirmed
Status in linux-azure source package in Groovy:
Fix Released
Bug description:
Issue found on 5.4.0-1013.13
The ftrace in ubuntu_kernel_selftests failed on the second test:
# === Ftrace unit tests ===
# [1] Basic trace file check [PASS]
# [2] Basic test for tracers
(System hang here)
Syslog:
kernel: [ 2234.408225] in mmio_trace_init
kernel: [ 2234.988256] mmiotrace: Disabling non-boot CPUs...
kernel: [ 2235.028451] mmiotrace: Error taking CPU1 down: -16
kernel: [ 2235.052564] mmiotrace: Error taking CPU2 down: -16
kernel: [ 2235.076593] mmiotrace: Error taking CPU3 down: -16
kernel: [ 2235.096576] mmiotrace: Error taking CPU4 down: -16
kernel: [ 2235.116487] mmiotrace: Error taking CPU5 down: -16
kernel: [ 2235.132446] mmiotrace: Error taking CPU6 down: -16
kernel: [ 2235.152488] mmiotrace: Error taking CPU7 down: -16
kernel: [ 2235.172526] mmiotrace: Error taking CPU8 down: -16
kernel: [ 2235.192486] mmiotrace: Error taking CPU9 down: -16
kernel: [ 2235.212455] mmiotrace: Error taking CPU10 down: -16
kernel: [ 2235.233020] mmiotrace: Error taking CPU11 down: -16
kernel: [ 2235.256355] mmiotrace: Error taking CPU12 down: -16
kernel: [ 2235.272473] mmiotrace: Error taking CPU13 down: -16
kernel: [ 2235.292393] mmiotrace: Error taking CPU14 down: -16
kernel: [ 2235.312426] mmiotrace: Error taking CPU15 down: -16
kernel: [ 2235.344407] mmiotrace: Error taking CPU16 down: -16
kernel: [ 2235.380494] mmiotrace: Error taking CPU17 down: -16
kernel: [ 2235.400319] mmiotrace: Error taking CPU18 down: -16
kernel: [ 2235.432631] mmiotrace: Error taking CPU19 down: -16
kernel: [ 2235.456453] mmiotrace: Error taking CPU20 down: -16
kernel: [ 2235.480432] mmiotrace: Error taking CPU21 down: -16
kernel: [ 2235.496501] mmiotrace: Error taking CPU22 down: -16
kernel: [ 2235.516442] mmiotrace: Error taking CPU23 down: -16
kernel: [ 2235.536394] mmiotrace: Error taking CPU24 down: -16
kernel: [
[Kernel-packages] [Bug 1882669] Re: Focal / Groovy aws and azure instances crash with ftracetest in ubuntu_kernel_selftests and ubuntu_ftrace_smoke_test
Seems that AWS got fixed (or issue was not related) but all Azure cases with v5.4 are affected. ** Tags added: sru-20210816 sru-20210906 -- 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/1882669 Title: Focal / Groovy aws and azure instances crash with ftracetest in ubuntu_kernel_selftests and ubuntu_ftrace_smoke_test Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Confirmed Status in linux-azure source package in Focal: Confirmed Status in linux-azure source package in Groovy: Fix Released Bug description: Issue found on 5.4.0-1013.13 The ftrace in ubuntu_kernel_selftests failed on the second test: # === Ftrace unit tests === # [1] Basic trace file check [PASS] # [2] Basic test for tracers (System hang here) Syslog: kernel: [ 2234.408225] in mmio_trace_init kernel: [ 2234.988256] mmiotrace: Disabling non-boot CPUs... kernel: [ 2235.028451] mmiotrace: Error taking CPU1 down: -16 kernel: [ 2235.052564] mmiotrace: Error taking CPU2 down: -16 kernel: [ 2235.076593] mmiotrace: Error taking CPU3 down: -16 kernel: [ 2235.096576] mmiotrace: Error taking CPU4 down: -16 kernel: [ 2235.116487] mmiotrace: Error taking CPU5 down: -16 kernel: [ 2235.132446] mmiotrace: Error taking CPU6 down: -16 kernel: [ 2235.152488] mmiotrace: Error taking CPU7 down: -16 kernel: [ 2235.172526] mmiotrace: Error taking CPU8 down: -16 kernel: [ 2235.192486] mmiotrace: Error taking CPU9 down: -16 kernel: [ 2235.212455] mmiotrace: Error taking CPU10 down: -16 kernel: [ 2235.233020] mmiotrace: Error taking CPU11 down: -16 kernel: [ 2235.256355] mmiotrace: Error taking CPU12 down: -16 kernel: [ 2235.272473] mmiotrace: Error taking CPU13 down: -16 kernel: [ 2235.292393] mmiotrace: Error taking CPU14 down: -16 kernel: [ 2235.312426] mmiotrace: Error taking CPU15 down: -16 kernel: [ 2235.344407] mmiotrace: Error taking CPU16 down: -16 kernel: [ 2235.380494] mmiotrace: Error taking CPU17 down: -16 kernel: [ 2235.400319] mmiotrace: Error taking CPU18 down: -16 kernel: [ 2235.432631] mmiotrace: Error taking CPU19 down: -16 kernel: [ 2235.456453] mmiotrace: Error taking CPU20 down: -16 kernel: [ 2235.480432] mmiotrace: Error taking CPU21 down: -16 kernel: [ 2235.496501] mmiotrace: Error taking CPU22 down: -16 kernel: [ 2235.516442] mmiotrace: Error taking CPU23 down: -16 kernel: [ 2235.536394] mmiotrace: Error taking CPU24 down: -16 kernel: [ 2235.556489] mmiotrace: Error taking CPU25 down: -16 kernel: [ 2235.573759] smpboot: CPU 26 is now offline kernel: [ 2235.575071] mmiotrace: CPU26 is down. kernel: [ 2235.585643] smpboot: CPU 27 is now offline kernel: [ 2235.586699] mmiotrace: CPU27 is down. kernel: [ 2235.609679] smpboot: CPU 28 is now offline kernel: [ 2235.610788] mmiotrace: CPU28 is down. kernel: [ 2235.633530] smpboot: CPU 29 is now offline kernel: [ 2235.634511] mmiotrace: CPU29 is down. kernel: [ 2235.653652] smpboot: CPU 30 is now offline kernel: [ 2235.655415] mmiotrace: CPU30 is down. kernel: [ 2235.678126] smpboot: CPU 31 is now offline kernel: [ 2235.679061] mmiotrace: CPU31 is down. kernel: [ 2235.679062] mmiotrace: multiple CPUs still online, may miss events. kernel: [ 2235.679063] mmiotrace: enabled. kernel: [ 2235.679128] in mmio_trace_reset kernel: [ 2235.696163] mmiotrace: Re-enabling CPUs... kernel: [ 2235.732157] mmiotrace: enabled CPU1. kernel: [ 2235.772207] mmiotrace: enabled CPU2. kernel: [ 2235.812216] mmiotrace: enabled CPU3. kernel: [ 2235.844220] mmiotrace: enabled CPU4. kernel: [ 2235.876211] mmiotrace: enabled CPU5. kernel: [ 2235.916159] mmiotrace: enabled CPU6. kernel: [ 2235.956214] mmiotrace: enabled CPU7. kernel: [ 2235.988145] mmiotrace: enabled CPU8. kernel: [ 2236.020214] mmiotrace: enabled CPU9. kernel: [ 2236.060207] mmiotrace: enabled CPU10. kernel: [ 2236.096208] mmiotrace: enabled CPU11. kernel: [ 2236.128205] mmiotrace: enabled CPU12. /usr/sbin/irqbalance: WARNING, didn't collect load info for all cpus, balancing is broken kernel: [ 2236.168204] mmiotrace: enabled CPU13. kernel: [ 2236.200206] mmiotrace: enabled CPU14. kernel: [ 2236.232207] mmiotrace: enabled CPU15. kernel: [ 2236.264224] mmiotrace: enabled CPU16. kernel: [ 2236.300207] mmiotrace: enabled CPU17. kernel: [ 2236.332210] mmiotrace: enabled CPU18. kernel: [ 2236.372224] mmiotrace: enabled CPU19. kernel: [ 2236.404147] mmiotrace: enabled CPU20. kernel: [ 2236.452153] mmiotrace: enabled CPU21. kernel: [ 2236.492152] mmiotrace: enabled CPU22. kernel: [ 2236.524153] mmiotrace: enabled CPU23. kernel: [ 2236.564211] mmiotrace: enabled CPU24. kernel: [ 2236.612204] mmiotrace: enabled CPU25. kernel: [ 2236.644353] smpboot: Booting Node 0 Processor 26 APIC 0x1a kernel: [ 2236.645769]
[Kernel-packages] [Bug 1882669] Re: Focal / Groovy aws and azure instances crash with ftracetest in ubuntu_kernel_selftests and ubuntu_ftrace_smoke_test
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-azure (Ubuntu Focal) Status: New => Confirmed -- 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/1882669 Title: Focal / Groovy aws and azure instances crash with ftracetest in ubuntu_kernel_selftests and ubuntu_ftrace_smoke_test Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Confirmed Status in linux-azure source package in Focal: Confirmed Status in linux-azure source package in Groovy: Fix Released Bug description: Issue found on 5.4.0-1013.13 The ftrace in ubuntu_kernel_selftests failed on the second test: # === Ftrace unit tests === # [1] Basic trace file check [PASS] # [2] Basic test for tracers (System hang here) Syslog: kernel: [ 2234.408225] in mmio_trace_init kernel: [ 2234.988256] mmiotrace: Disabling non-boot CPUs... kernel: [ 2235.028451] mmiotrace: Error taking CPU1 down: -16 kernel: [ 2235.052564] mmiotrace: Error taking CPU2 down: -16 kernel: [ 2235.076593] mmiotrace: Error taking CPU3 down: -16 kernel: [ 2235.096576] mmiotrace: Error taking CPU4 down: -16 kernel: [ 2235.116487] mmiotrace: Error taking CPU5 down: -16 kernel: [ 2235.132446] mmiotrace: Error taking CPU6 down: -16 kernel: [ 2235.152488] mmiotrace: Error taking CPU7 down: -16 kernel: [ 2235.172526] mmiotrace: Error taking CPU8 down: -16 kernel: [ 2235.192486] mmiotrace: Error taking CPU9 down: -16 kernel: [ 2235.212455] mmiotrace: Error taking CPU10 down: -16 kernel: [ 2235.233020] mmiotrace: Error taking CPU11 down: -16 kernel: [ 2235.256355] mmiotrace: Error taking CPU12 down: -16 kernel: [ 2235.272473] mmiotrace: Error taking CPU13 down: -16 kernel: [ 2235.292393] mmiotrace: Error taking CPU14 down: -16 kernel: [ 2235.312426] mmiotrace: Error taking CPU15 down: -16 kernel: [ 2235.344407] mmiotrace: Error taking CPU16 down: -16 kernel: [ 2235.380494] mmiotrace: Error taking CPU17 down: -16 kernel: [ 2235.400319] mmiotrace: Error taking CPU18 down: -16 kernel: [ 2235.432631] mmiotrace: Error taking CPU19 down: -16 kernel: [ 2235.456453] mmiotrace: Error taking CPU20 down: -16 kernel: [ 2235.480432] mmiotrace: Error taking CPU21 down: -16 kernel: [ 2235.496501] mmiotrace: Error taking CPU22 down: -16 kernel: [ 2235.516442] mmiotrace: Error taking CPU23 down: -16 kernel: [ 2235.536394] mmiotrace: Error taking CPU24 down: -16 kernel: [ 2235.556489] mmiotrace: Error taking CPU25 down: -16 kernel: [ 2235.573759] smpboot: CPU 26 is now offline kernel: [ 2235.575071] mmiotrace: CPU26 is down. kernel: [ 2235.585643] smpboot: CPU 27 is now offline kernel: [ 2235.586699] mmiotrace: CPU27 is down. kernel: [ 2235.609679] smpboot: CPU 28 is now offline kernel: [ 2235.610788] mmiotrace: CPU28 is down. kernel: [ 2235.633530] smpboot: CPU 29 is now offline kernel: [ 2235.634511] mmiotrace: CPU29 is down. kernel: [ 2235.653652] smpboot: CPU 30 is now offline kernel: [ 2235.655415] mmiotrace: CPU30 is down. kernel: [ 2235.678126] smpboot: CPU 31 is now offline kernel: [ 2235.679061] mmiotrace: CPU31 is down. kernel: [ 2235.679062] mmiotrace: multiple CPUs still online, may miss events. kernel: [ 2235.679063] mmiotrace: enabled. kernel: [ 2235.679128] in mmio_trace_reset kernel: [ 2235.696163] mmiotrace: Re-enabling CPUs... kernel: [ 2235.732157] mmiotrace: enabled CPU1. kernel: [ 2235.772207] mmiotrace: enabled CPU2. kernel: [ 2235.812216] mmiotrace: enabled CPU3. kernel: [ 2235.844220] mmiotrace: enabled CPU4. kernel: [ 2235.876211] mmiotrace: enabled CPU5. kernel: [ 2235.916159] mmiotrace: enabled CPU6. kernel: [ 2235.956214] mmiotrace: enabled CPU7. kernel: [ 2235.988145] mmiotrace: enabled CPU8. kernel: [ 2236.020214] mmiotrace: enabled CPU9. kernel: [ 2236.060207] mmiotrace: enabled CPU10. kernel: [ 2236.096208] mmiotrace: enabled CPU11. kernel: [ 2236.128205] mmiotrace: enabled CPU12. /usr/sbin/irqbalance: WARNING, didn't collect load info for all cpus, balancing is broken kernel: [ 2236.168204] mmiotrace: enabled CPU13. kernel: [ 2236.200206] mmiotrace: enabled CPU14. kernel: [ 2236.232207] mmiotrace: enabled CPU15. kernel: [ 2236.264224] mmiotrace: enabled CPU16. kernel: [ 2236.300207] mmiotrace: enabled CPU17. kernel: [ 2236.332210] mmiotrace: enabled CPU18. kernel: [ 2236.372224] mmiotrace: enabled CPU19. kernel: [ 2236.404147] mmiotrace: enabled CPU20. kernel: [ 2236.452153] mmiotrace: enabled CPU21. kernel: [ 2236.492152] mmiotrace: enabled CPU22. kernel: [ 2236.524153] mmiotrace: enabled CPU23. kernel: [ 2236.564211] mmiotrace: enabled CPU24. kernel: [ 2236.612204] mmiotrace: enabled CPU25. kernel: [ 2236.644353] smpboot: Booting Node 0 Processor 26 APIC 0x1a kernel: [
[Kernel-packages] [Bug 1882669] Re: Focal / Groovy aws and azure instances crash with ftracetest in ubuntu_kernel_selftests and ubuntu_ftrace_smoke_test
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-aws (Ubuntu) Status: New => Confirmed -- 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/1882669 Title: Focal / Groovy aws and azure instances crash with ftracetest in ubuntu_kernel_selftests and ubuntu_ftrace_smoke_test Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Confirmed Status in linux-azure source package in Focal: Confirmed Status in linux-azure source package in Groovy: Fix Released Bug description: Issue found on 5.4.0-1013.13 The ftrace in ubuntu_kernel_selftests failed on the second test: # === Ftrace unit tests === # [1] Basic trace file check [PASS] # [2] Basic test for tracers (System hang here) Syslog: kernel: [ 2234.408225] in mmio_trace_init kernel: [ 2234.988256] mmiotrace: Disabling non-boot CPUs... kernel: [ 2235.028451] mmiotrace: Error taking CPU1 down: -16 kernel: [ 2235.052564] mmiotrace: Error taking CPU2 down: -16 kernel: [ 2235.076593] mmiotrace: Error taking CPU3 down: -16 kernel: [ 2235.096576] mmiotrace: Error taking CPU4 down: -16 kernel: [ 2235.116487] mmiotrace: Error taking CPU5 down: -16 kernel: [ 2235.132446] mmiotrace: Error taking CPU6 down: -16 kernel: [ 2235.152488] mmiotrace: Error taking CPU7 down: -16 kernel: [ 2235.172526] mmiotrace: Error taking CPU8 down: -16 kernel: [ 2235.192486] mmiotrace: Error taking CPU9 down: -16 kernel: [ 2235.212455] mmiotrace: Error taking CPU10 down: -16 kernel: [ 2235.233020] mmiotrace: Error taking CPU11 down: -16 kernel: [ 2235.256355] mmiotrace: Error taking CPU12 down: -16 kernel: [ 2235.272473] mmiotrace: Error taking CPU13 down: -16 kernel: [ 2235.292393] mmiotrace: Error taking CPU14 down: -16 kernel: [ 2235.312426] mmiotrace: Error taking CPU15 down: -16 kernel: [ 2235.344407] mmiotrace: Error taking CPU16 down: -16 kernel: [ 2235.380494] mmiotrace: Error taking CPU17 down: -16 kernel: [ 2235.400319] mmiotrace: Error taking CPU18 down: -16 kernel: [ 2235.432631] mmiotrace: Error taking CPU19 down: -16 kernel: [ 2235.456453] mmiotrace: Error taking CPU20 down: -16 kernel: [ 2235.480432] mmiotrace: Error taking CPU21 down: -16 kernel: [ 2235.496501] mmiotrace: Error taking CPU22 down: -16 kernel: [ 2235.516442] mmiotrace: Error taking CPU23 down: -16 kernel: [ 2235.536394] mmiotrace: Error taking CPU24 down: -16 kernel: [ 2235.556489] mmiotrace: Error taking CPU25 down: -16 kernel: [ 2235.573759] smpboot: CPU 26 is now offline kernel: [ 2235.575071] mmiotrace: CPU26 is down. kernel: [ 2235.585643] smpboot: CPU 27 is now offline kernel: [ 2235.586699] mmiotrace: CPU27 is down. kernel: [ 2235.609679] smpboot: CPU 28 is now offline kernel: [ 2235.610788] mmiotrace: CPU28 is down. kernel: [ 2235.633530] smpboot: CPU 29 is now offline kernel: [ 2235.634511] mmiotrace: CPU29 is down. kernel: [ 2235.653652] smpboot: CPU 30 is now offline kernel: [ 2235.655415] mmiotrace: CPU30 is down. kernel: [ 2235.678126] smpboot: CPU 31 is now offline kernel: [ 2235.679061] mmiotrace: CPU31 is down. kernel: [ 2235.679062] mmiotrace: multiple CPUs still online, may miss events. kernel: [ 2235.679063] mmiotrace: enabled. kernel: [ 2235.679128] in mmio_trace_reset kernel: [ 2235.696163] mmiotrace: Re-enabling CPUs... kernel: [ 2235.732157] mmiotrace: enabled CPU1. kernel: [ 2235.772207] mmiotrace: enabled CPU2. kernel: [ 2235.812216] mmiotrace: enabled CPU3. kernel: [ 2235.844220] mmiotrace: enabled CPU4. kernel: [ 2235.876211] mmiotrace: enabled CPU5. kernel: [ 2235.916159] mmiotrace: enabled CPU6. kernel: [ 2235.956214] mmiotrace: enabled CPU7. kernel: [ 2235.988145] mmiotrace: enabled CPU8. kernel: [ 2236.020214] mmiotrace: enabled CPU9. kernel: [ 2236.060207] mmiotrace: enabled CPU10. kernel: [ 2236.096208] mmiotrace: enabled CPU11. kernel: [ 2236.128205] mmiotrace: enabled CPU12. /usr/sbin/irqbalance: WARNING, didn't collect load info for all cpus, balancing is broken kernel: [ 2236.168204] mmiotrace: enabled CPU13. kernel: [ 2236.200206] mmiotrace: enabled CPU14. kernel: [ 2236.232207] mmiotrace: enabled CPU15. kernel: [ 2236.264224] mmiotrace: enabled CPU16. kernel: [ 2236.300207] mmiotrace: enabled CPU17. kernel: [ 2236.332210] mmiotrace: enabled CPU18. kernel: [ 2236.372224] mmiotrace: enabled CPU19. kernel: [ 2236.404147] mmiotrace: enabled CPU20. kernel: [ 2236.452153] mmiotrace: enabled CPU21. kernel: [ 2236.492152] mmiotrace: enabled CPU22. kernel: [ 2236.524153] mmiotrace: enabled CPU23. kernel: [ 2236.564211] mmiotrace: enabled CPU24. kernel: [ 2236.612204] mmiotrace: enabled CPU25. kernel: [ 2236.644353] smpboot: Booting Node 0 Processor 26 APIC 0x1a kernel: [ 2236.645769]
[Kernel-packages] [Bug 1882669] Re: Focal / Groovy aws and azure instances crash with ftracetest in ubuntu_kernel_selftests and ubuntu_ftrace_smoke_test
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-azure (Ubuntu) Status: New => Confirmed -- 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/1882669 Title: Focal / Groovy aws and azure instances crash with ftracetest in ubuntu_kernel_selftests and ubuntu_ftrace_smoke_test Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Confirmed Status in linux-azure source package in Focal: Confirmed Status in linux-azure source package in Groovy: Fix Released Bug description: Issue found on 5.4.0-1013.13 The ftrace in ubuntu_kernel_selftests failed on the second test: # === Ftrace unit tests === # [1] Basic trace file check [PASS] # [2] Basic test for tracers (System hang here) Syslog: kernel: [ 2234.408225] in mmio_trace_init kernel: [ 2234.988256] mmiotrace: Disabling non-boot CPUs... kernel: [ 2235.028451] mmiotrace: Error taking CPU1 down: -16 kernel: [ 2235.052564] mmiotrace: Error taking CPU2 down: -16 kernel: [ 2235.076593] mmiotrace: Error taking CPU3 down: -16 kernel: [ 2235.096576] mmiotrace: Error taking CPU4 down: -16 kernel: [ 2235.116487] mmiotrace: Error taking CPU5 down: -16 kernel: [ 2235.132446] mmiotrace: Error taking CPU6 down: -16 kernel: [ 2235.152488] mmiotrace: Error taking CPU7 down: -16 kernel: [ 2235.172526] mmiotrace: Error taking CPU8 down: -16 kernel: [ 2235.192486] mmiotrace: Error taking CPU9 down: -16 kernel: [ 2235.212455] mmiotrace: Error taking CPU10 down: -16 kernel: [ 2235.233020] mmiotrace: Error taking CPU11 down: -16 kernel: [ 2235.256355] mmiotrace: Error taking CPU12 down: -16 kernel: [ 2235.272473] mmiotrace: Error taking CPU13 down: -16 kernel: [ 2235.292393] mmiotrace: Error taking CPU14 down: -16 kernel: [ 2235.312426] mmiotrace: Error taking CPU15 down: -16 kernel: [ 2235.344407] mmiotrace: Error taking CPU16 down: -16 kernel: [ 2235.380494] mmiotrace: Error taking CPU17 down: -16 kernel: [ 2235.400319] mmiotrace: Error taking CPU18 down: -16 kernel: [ 2235.432631] mmiotrace: Error taking CPU19 down: -16 kernel: [ 2235.456453] mmiotrace: Error taking CPU20 down: -16 kernel: [ 2235.480432] mmiotrace: Error taking CPU21 down: -16 kernel: [ 2235.496501] mmiotrace: Error taking CPU22 down: -16 kernel: [ 2235.516442] mmiotrace: Error taking CPU23 down: -16 kernel: [ 2235.536394] mmiotrace: Error taking CPU24 down: -16 kernel: [ 2235.556489] mmiotrace: Error taking CPU25 down: -16 kernel: [ 2235.573759] smpboot: CPU 26 is now offline kernel: [ 2235.575071] mmiotrace: CPU26 is down. kernel: [ 2235.585643] smpboot: CPU 27 is now offline kernel: [ 2235.586699] mmiotrace: CPU27 is down. kernel: [ 2235.609679] smpboot: CPU 28 is now offline kernel: [ 2235.610788] mmiotrace: CPU28 is down. kernel: [ 2235.633530] smpboot: CPU 29 is now offline kernel: [ 2235.634511] mmiotrace: CPU29 is down. kernel: [ 2235.653652] smpboot: CPU 30 is now offline kernel: [ 2235.655415] mmiotrace: CPU30 is down. kernel: [ 2235.678126] smpboot: CPU 31 is now offline kernel: [ 2235.679061] mmiotrace: CPU31 is down. kernel: [ 2235.679062] mmiotrace: multiple CPUs still online, may miss events. kernel: [ 2235.679063] mmiotrace: enabled. kernel: [ 2235.679128] in mmio_trace_reset kernel: [ 2235.696163] mmiotrace: Re-enabling CPUs... kernel: [ 2235.732157] mmiotrace: enabled CPU1. kernel: [ 2235.772207] mmiotrace: enabled CPU2. kernel: [ 2235.812216] mmiotrace: enabled CPU3. kernel: [ 2235.844220] mmiotrace: enabled CPU4. kernel: [ 2235.876211] mmiotrace: enabled CPU5. kernel: [ 2235.916159] mmiotrace: enabled CPU6. kernel: [ 2235.956214] mmiotrace: enabled CPU7. kernel: [ 2235.988145] mmiotrace: enabled CPU8. kernel: [ 2236.020214] mmiotrace: enabled CPU9. kernel: [ 2236.060207] mmiotrace: enabled CPU10. kernel: [ 2236.096208] mmiotrace: enabled CPU11. kernel: [ 2236.128205] mmiotrace: enabled CPU12. /usr/sbin/irqbalance: WARNING, didn't collect load info for all cpus, balancing is broken kernel: [ 2236.168204] mmiotrace: enabled CPU13. kernel: [ 2236.200206] mmiotrace: enabled CPU14. kernel: [ 2236.232207] mmiotrace: enabled CPU15. kernel: [ 2236.264224] mmiotrace: enabled CPU16. kernel: [ 2236.300207] mmiotrace: enabled CPU17. kernel: [ 2236.332210] mmiotrace: enabled CPU18. kernel: [ 2236.372224] mmiotrace: enabled CPU19. kernel: [ 2236.404147] mmiotrace: enabled CPU20. kernel: [ 2236.452153] mmiotrace: enabled CPU21. kernel: [ 2236.492152] mmiotrace: enabled CPU22. kernel: [ 2236.524153] mmiotrace: enabled CPU23. kernel: [ 2236.564211] mmiotrace: enabled CPU24. kernel: [ 2236.612204] mmiotrace: enabled CPU25. kernel: [ 2236.644353] smpboot: Booting Node 0 Processor 26 APIC 0x1a kernel: [
[Kernel-packages] [Bug 1943841] [NEW] svm from ubuntu_kvm_unit_tests interrupt with "Unhandled exception 13 #GP at ip 00000000004027e3" on F-intel-5.13
Public bug reported: Failing with Focal Intel 5.13.0-1004.4 on node gonzo A bit like bug 1934939, but this time it looks like this has passed through more cases than that bug. Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/svm' BUILD_HEAD=1593e88a timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.8QIXdsXIyJ -smp 2 -cpu max,+svm -m 4g # -initrd /tmp/tmp.VvuuwXHRuX enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 10bf000 cr4 = 20 NPT detected - running all tests with NPT enabled PASS: null PASS: vmrun PASS: ioio PASS: vmrun intercept check PASS: rsm PASS: cr3 read intercept PASS: cr3 read nointercept PASS: cr3 read intercept emulate PASS: dr intercept check PASS: next_rip PASS: msr intercept check PASS: mode_switch PASS: asid_zero PASS: sel_cr0_bug PASS: npt_nx PASS: npt_np PASS: npt_us PASS: npt_rw PASS: npt_rw_pfwalk PASS: npt_l1mmio PASS: npt_rw_l1mmio PASS: tsc_adjust Latency VMRUN : max: 322434 min: 21233 avg: 36460 Latency VMEXIT: max: 298726 min: 16889 avg: 17717 PASS: latency_run_exit Latency VMRUN : max: 334040 min: 23446 avg: 36313 Latency VMEXIT: max: 310725 min: 16935 avg: 17618 PASS: latency_run_exit_clean Latency VMLOAD: max: 732466 min: 4675 avg: 4879 Latency VMSAVE: max: 60901 min: 4565 avg: 4850 Latency STGI: max: 43057 min: 3726 avg: 3862 Latency CLGI: max: 723675 min: 3644 avg: 3724 PASS: latency_svm_insn PASS: exception with vector 2 not injected PASS: divide overflow exception injected PASS: eventinj.VALID cleared PASS: exc_inject PASS: pending_event PASS: pending_event_cli PASS: direct interrupt while running guest PASS: intercepted interrupt while running guest PASS: direct interrupt + hlt PASS: intercepted interrupt + hlt PASS: interrupt PASS: direct NMI while running guest PASS: NMI intercept while running guest PASS: nmi PASS: direct NMI + hlt PASS: NMI intercept while running guest PASS: intercepted NMI + hlt PASS: nmi_hlt PASS: virq_inject PASS: No RIP corruption detected after 1 timer interrupts PASS: reg_corruption enabling apic PASS: svm_init_startup_test PASS: host_rflags PASS: CPUID.01H:ECX.XSAVE set before VMRUN PASS: svm_cr4_osxsave_test_guest finished with VMMCALL PASS: CPUID.01H:ECX.XSAVE set after VMRUN PASS: EFER.SVME: 1500 PASS: EFER.SVME: 500 PASS: Test EFER 9:8: 1700 PASS: Test EFER 63:16: 11500 PASS: Test EFER 63:16: 101500 PASS: Test EFER 63:16: 1001500 PASS: Test EFER 63:16: 10001500 PASS: Test EFER 63:16: 11500 PASS: Test EFER 63:16: 101500 PASS: Test EFER 63:16: 1001500 PASS: Test EFER 63:16: 10001500 PASS: Test EFER 63:16: 11500 PASS: Test EFER 63:16: 101500 PASS: Test EFER 63:16: 1001500 PASS: Test EFER 63:16: 10001500 PASS: EFER.LME=1 (1500), CR0.PG=1 (80010011) and CR4.PAE=0 (4) PASS: EFER.LME=1 (1500), CR0.PG=1 and CR0.PE=0 (80010010) PASS: EFER.LME=1 (1500), CR0.PG=1 (80010011), CR4.PAE=1 (40020), CS.L=1 and CS.D=1 (699) PASS: Test CR0 CD=1,NW=0: c0010011 PASS: Test CR0 CD=1,NW=1: e0010011 PASS: Test CR0 CD=0,NW=0: 80010011 PASS: Test CR0 CD=0,NW=1: a0010011 PASS: Test CR0 63:32: 180010011 PASS: Test CR0 63:32: 1080010011 PASS: Test CR0 63:32: 10080010011 PASS: Test CR0 63:32: 100080010011 PASS: Test CR0 63:32: 180010011 PASS: Test CR0 63:32: 1080010011 PASS: Test CR0 63:32: 10080010011 PASS: Test CR0 63:32: 100080010011 PASS: Test CR3 63:0: 10010bf000, wanted exit 0x, got 0x PASS: Test CR3 63:0: 20010bf000, wanted exit 0x, got 0x PASS: Test CR3 63:0: 40010bf000, wanted exit 0x, got 0x PASS: Test CR3 63:0: 80010bf000, wanted exit 0x, got 0x PASS: Test CR3 63:0: 100010bf000, wanted exit 0x, got 0x PASS: Test CR3 63:0: 200010bf000, wanted exit 0x, got 0x PASS: Test CR3 63:0: 400010bf000, wanted exit 0x, got 0x PASS: Test CR3 63:0: 800010bf000, wanted exit 0x, got 0x PASS: Test CR3 63:0: 110bf000, wanted exit 0x, got 0x PASS: Test CR3 63:0: 210bf000, wanted exit 0x, got 0x PASS: Test CR3 63:0: 410bf000, wanted exit 0x, got 0x PASS: Test CR3 63:0: 810bf000, wanted exit 0x, got 0x PASS: Test CR3 63:0: 10bf000 PASS: Test CR3 (PCIDE=0) 11:0: 10bf001, wanted exit 0x400, got 0x400 PASS: Test CR3 (PCIDE=0) 11:0: 10bf002, wanted exit 0x400, got 0x400 PASS: Test CR3 (PCIDE=0) 11:0: 10bf004, wanted exit 0x400, got 0x400 PASS: Test CR3 (PCIDE=0) 11:0: 10bf020, wanted exit 0x400, got 0x400 PASS: Test CR3 (PCIDE=0) 11:0: 10bf040, wanted exit 0x400, got 0x400
[Kernel-packages] [Bug 1939986] Re: Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads i915
** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Invalid -- 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/1939986 Title: Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads i915 Status in initramfs-tools package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Confirmed Bug description: Dear all, I can see that the linux-firmware is missing firmware files, in Ubuntu 20.04.1 LTS, for initramfs, when it loads i915. Package: linux-firmware 1.187.15 It contains the following files, for the module i915: i915/tgl_dmc_ver2_04.bin 2019-09-13 installed i915/tgl_dmc_ver2_06.bin 2020-03-04 installed i915/tgl_dmc_ver2_08.bin 2020-08-13 installed i915/tgl_guc_35.2.0.bin 2019-11-06 installed i915/tgl_huc_7.0.12.bin 2020-03-04 installed i915/tgl_huc_7.0.3.bin2019-11-06 installed Package: linux-firmware MUST at least contain the following files, for the module i915: i915/tgl_huc_7.5.0.bin2020-08-13 i915: Add HuC firwmare v7.5.0 for TGL as the module asks for it, during 'update-initramfs', to avoid: W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 But it COULD also contain : i915/tgl_dmc_ver2_12.bin 2021-07-28 i915: Add v2.12 DMC for TGL i915/tgl_guc_49.0.1.bin 2020-11-24 i915: Add GuC firmware v49.0.1 for all platforms i915/tgl_guc_62.0.0.bin 2021-06-29 firmware/i915/guc: Add GuC v62.0.0 for all platforms i915/tgl_huc_7.9.3.bin2021-06-29 firmware/i915/guc: Add HuC v7.9.3 for TGL & DG1 Source: $ modprobe --show-depends --ignore-install i915 ... insmod /lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko $ modinfo -F firmware /lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko ... i915/tgl_dmc_ver2_08.bin i915/tgl_guc_35.2.0.bin i915/tgl_huc_7.5.0.bin Actual result: $ sudo update-initramfs -u W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 Expected result: No Warning. and the firmware "i915/tgl_huc_7.5.0.bin" loaded for module i915 Info : INTEL Repository of firmware: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.15 ProcVersionSignature: Ubuntu 5.10.0-1038.40-oem 5.10.46 Uname: Linux 5.10.0-1038-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1699 F pulseaudio /dev/snd/pcmC0D0p: chris 1699 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Aug 15 14:46:47 2021 Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X54 InstallationDate: Installed on 2021-08-12 (2 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1038-oem root=UUID=3dae0247-a884-48d8-83b7-fea7c803faa3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.10.0-1038-oem N/A linux-backports-modules-5.10.0-1038-oem N/A linux-firmware 1.187.15 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 07/16/2021 dmi.bios.release: 3.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.0.4 dmi.board.name: 08607K dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.0.4:bd07/16/2021:br3.0:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1939986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943832] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943832 Title: Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA) Status in linux package in Ubuntu: Confirmed Bug description: ASUS UM425UA internal keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. I noticed it when tried to boot live image of Ubuntu 20.04.3 This problem probably appeared with kernel version 5.9 or 5.10 because with Ubuntu 20.04.2 live image (Linux 5.8) keyboard loads fine. Tried kernel 5.14 and it's still affected. I tried to recompile kernels 5.11 & 5.13 with SERIO_I8042 set as a module (as suggested in an Arch Linux bug report) and keyboard now works from the first start. In "make config" the changes are: Device Drivers -> > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for U14.04 > Input device support > Keyboards -> [M] AT keyboard > Hardware I/O ports -> [M] i8042 PC Keyboard controller It changed such lines in config: CONFIG_KEYBOARD_ATKBD=m CONFIG_SERIO_I8042=m CONFIG_SERIO_LIBPS2=m References: https://bugs.archlinux.org/task/70384 https://ubuntuforums.org/showthread.php?t=2459149 https://linux.org/threads/asus-zenbook-14-um425ua-keyboard-not-respond-during-cold-boot.33738/#post-133830 P.S. Other option which helped me was a GRUB parameter "i8042.reset=1" but it had a positive effect only with kernel 5.11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: 807 F pulseaudio /dev/snd/controlC2: 807 F pulseaudio /dev/snd/controlC1: 807 F pulseaudio /dev/snd/controlC0: 807 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-01 (14 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425UA_UM425UA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=3e7eadd0-dd33-487a-8e38-3e516c0dc8d5 ro quiet i8042.reset=1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.199 Tags: focal Uname: Linux 5.11.0-34-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: 04/01/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX425UA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425UA 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: 3.1 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX425UA.301:bd04/01/2021:br5.19:efr3.1:svnASUSTeKCOMPUTERINC.:pnZenBookUX425UA_UM425UA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX425UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425UA_UM425UA 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/1943832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943832] Re: Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA)
apport information ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943832/+attachment/5525703/+files/CurrentDmesg.txt ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943832/+attachment/5525722/+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/1943832 Title: Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA) Status in linux package in Ubuntu: Confirmed Bug description: ASUS UM425UA internal keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. I noticed it when tried to boot live image of Ubuntu 20.04.3 This problem probably appeared with kernel version 5.9 or 5.10 because with Ubuntu 20.04.2 live image (Linux 5.8) keyboard loads fine. Tried kernel 5.14 and it's still affected. I tried to recompile kernels 5.11 & 5.13 with SERIO_I8042 set as a module (as suggested in an Arch Linux bug report) and keyboard now works from the first start. In "make config" the changes are: Device Drivers -> > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for U14.04 > Input device support > Keyboards -> [M] AT keyboard > Hardware I/O ports -> [M] i8042 PC Keyboard controller It changed such lines in config: CONFIG_KEYBOARD_ATKBD=m CONFIG_SERIO_I8042=m CONFIG_SERIO_LIBPS2=m References: https://bugs.archlinux.org/task/70384 https://ubuntuforums.org/showthread.php?t=2459149 https://linux.org/threads/asus-zenbook-14-um425ua-keyboard-not-respond-during-cold-boot.33738/#post-133830 P.S. Other option which helped me was a GRUB parameter "i8042.reset=1" but it had a positive effect only with kernel 5.11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: 807 F pulseaudio /dev/snd/controlC2: 807 F pulseaudio /dev/snd/controlC1: 807 F pulseaudio /dev/snd/controlC0: 807 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-01 (14 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425UA_UM425UA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=3e7eadd0-dd33-487a-8e38-3e516c0dc8d5 ro quiet i8042.reset=1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.199 Tags: focal Uname: Linux 5.11.0-34-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: 04/01/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX425UA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425UA 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: 3.1 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX425UA.301:bd04/01/2021:br5.19:efr3.1:svnASUSTeKCOMPUTERINC.:pnZenBookUX425UA_UM425UA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX425UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425UA_UM425UA 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/1943832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942498] Re: can_bcm01 from can in ubuntu_ltp_stable crash system on F-OEM-5.13
Found this on Intel 5.13 5.13.0-1004.4 ** Also affects: linux-intel-5.13 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-intel-5.13 (Ubuntu) Status: New => Invalid ** Changed in: linux-intel-5.13 (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1942498 Title: can_bcm01 from can in ubuntu_ltp_stable crash system on F-OEM-5.13 Status in ubuntu-kernel-tests: New Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-signed-oem-5.13 package in Ubuntu: Invalid Status in linux-intel-5.13 source package in Focal: Confirmed Status in linux-signed-oem-5.13 source package in Focal: Fix Committed Bug description: It looks like this is a test case for CVE-2021-3609 This issue does not exist in the last cycle for OEM 5.13.0-1010 as this test case does not exist back then. can_bcm01 test in ubuntu_ltp_stable/can will trigger the following error on 5.13.0-1011-oem and crash the system: Sep 3 04:30:20 spitfire kernel: [ 324.458389] LTP: starting can_bcm01 Sep 3 04:30:20 spitfire kernel: [ 324.474313] vcan: Virtual CAN interface driver Sep 3 04:30:20 spitfire systemd-networkd[1967]: ltp_vcan0: Link UP Sep 3 04:30:20 spitfire networkd-dispatcher[2025]: WARNING:Unknown index 4 seen, reloading interface list Sep 3 04:30:20 spitfire systemd-networkd[1967]: ltp_vcan0: Gained carrier Sep 3 04:30:20 spitfire systemd-udevd[4596]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. Sep 3 04:30:20 spitfire systemd-udevd[4596]: Using default interface naming scheme 'v245'. Sep 3 04:30:20 spitfire kernel: [ 324.483778] can: controller area network core Sep 3 04:30:20 spitfire kernel: [ 324.483819] NET: Registered protocol family 29 Sep 3 04:30:20 spitfire kernel: [ 324.491947] can: broadcast manager protocol Sep 3 04:30:20 spitfire kernel: [ 324.515859] [ cut here ] Sep 3 04:30:20 spitfire kernel: [ 324.515863] WARNING: CPU: 7 PID: 4591 at lib/timerqueue.c:55 timerqueue_del+0x43/0x50 Sep 3 04:30:20 spitfire kernel: [ 324.515877] Modules linked in: can_bcm can vcan nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua intel_rapl_msr intel_rapl_common i10nm_edac nfit x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm ipmi_ssif rapl joydev input_leds efi_pstore isst_if_mbox_pci isst_if_mmio isst_if_common mei_me intel_pch_thermal mei ioatdma acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter acpi_pad mac_hid sch_fq_codel msr ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid crct10dif_pclmul ast crc32_pclmul drm_vram_helper i2c_algo_bit drm_ttm_helper ttm ghash_clmulni_intel drm_kms_helper aesni_intel syscopyarea ixgbe sysfillrect sysimgblt fb_sys_fops crypto_simd cec xfrm_algo rc_core cryptd dca drm mdio ahci i2c_i801 xhci_pci i2c_smbus xhci_pci_renesas intel_pmt libahci wmi Sep 3 04:30:20 spitfire kernel: [ 324.515953] CPU: 7 PID: 4591 Comm: can_bcm01 Not tainted 5.13.0-1011-oem #15-Ubuntu Sep 3 04:30:20 spitfire kernel: [ 324.515957] Hardware name: Intel Corporation M50CYP2SB2U/M50CYP2SB2U, BIOS SE5C6200.86B.0021.D40.2101090208 01/09/2021 Sep 3 04:30:20 spitfire kernel: [ 324.515959] RIP: 0010:timerqueue_del+0x43/0x50 Sep 3 04:30:20 spitfire kernel: [ 324.515965] Code: 48 89 df e8 ef c5 ff ff 49 89 44 24 08 4c 89 e6 48 89 df e8 9f be ff ff 48 89 1b 49 8b 04 24 5b 41 5c 48 85 c0 5d 0f 95 c0 c3 <0f> 0b eb cb cc cc cc cc cc cc cc cc cc 48 8b 07 45 31 c0 48 83 c0 Sep 3 04:30:20 spitfire kernel: [ 324.515968] RSP: 0018:ff46f753c8917d40 EFLAGS: 00010046 Sep 3 04:30:20 spitfire kernel: [ 324.515972] RAX: 0001 RBX: ff3a23c5110cae50 RCX: Sep 3 04:30:20 spitfire kernel: [ 324.515974] RDX: RSI: ff3a23c5110cae50 RDI: ff3a23cc5f85f260 Sep 3 04:30:20 spitfire kernel: [ 324.515975] RBP: ff46f753c8917d50 R08: a3ce6048 R09: ff3a23c51bc84e40 Sep 3 04:30:20 spitfire kernel: [ 324.515977] R10: 0008 R11: ff3a23c54ea21a10 R12: ff3a23cc5f85f260 Sep 3 04:30:20 spitfire kernel: [ 324.515979] R13: R14: ff3a23cc5f85f100 R15: ff3a23c54ea2df10 Sep 3 04:30:20 spitfire kernel: [ 324.515980] FS: 7f196de15740() GS:ff3a23cc5f3c() knlGS: Sep 3 04:30:20 spitfire kernel: [ 324.515983] CS: 0010 DS: ES: CR0: 80050033 Sep 3 04:30:20 spitfire kernel: [ 324.515984] CR2: 7f196e008fec CR3: 00010ea66003 CR4: 00771ee0 Sep 3 04:30:20 spitfire kernel: [ 324.515986] DR0: DR1:
[Kernel-packages] [Bug 1943832] Re: Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA)
** Description changed: ASUS UM425UA internal keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. I noticed it when tried to boot live image of Ubuntu 20.04.3 This problem probably appeared with kernel version 5.9 or 5.10 because with Ubuntu 20.04.2 live image (Linux 5.8) keyboard loads fine. Tried kernel 5.14 and it's still affected. I tried to recompile kernels 5.11 & 5.13 with SERIO_I8042 set as a module (as suggested in an Arch Linux bug report) and keyboard now works from the first start. In "make config" the changes are: Device Drivers -> > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for U14.04 > Input device support > Keyboards -> [M] AT keyboard > Hardware I/O ports -> [M] i8042 PC Keyboard controller It changed such lines in config: CONFIG_KEYBOARD_ATKBD=m CONFIG_SERIO_I8042=m CONFIG_SERIO_LIBPS2=m References: https://bugs.archlinux.org/task/70384 https://ubuntuforums.org/showthread.php?t=2459149 https://linux.org/threads/asus-zenbook-14-um425ua-keyboard-not-respond-during-cold-boot.33738/#post-133830 P.S. Other option which helped me was a GRUB parameter "i8042.reset=1" but it had a positive effect only with kernel 5.11 - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC3: marketing-trade807 F pulseaudio - /dev/snd/controlC2: marketing-trade807 F pulseaudio - /dev/snd/controlC1: marketing-trade807 F pulseaudio - /dev/snd/controlC0: marketing-trade807 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC3: 807 F pulseaudio + /dev/snd/controlC2: 807 F pulseaudio + /dev/snd/controlC1: 807 F pulseaudio + /dev/snd/controlC0: 807 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-01 (14 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425UA_UM425UA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=3e7eadd0-dd33-487a-8e38-3e516c0dc8d5 ro quiet i8042.reset=1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 RelatedPackageVersions: - linux-restricted-modules-5.11.0-34-generic N/A - linux-backports-modules-5.11.0-34-generic N/A - linux-firmware 1.199 + linux-restricted-modules-5.11.0-34-generic N/A + linux-backports-modules-5.11.0-34-generic N/A + linux-firmware 1.199 Tags: focal Uname: Linux 5.11.0-34-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: 04/01/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX425UA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425UA 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: 3.1 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX425UA.301:bd04/01/2021:br5.19:efr3.1:svnASUSTeKCOMPUTERINC.:pnZenBookUX425UA_UM425UA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX425UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425UA_UM425UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Attachment removed: "PulseList.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943832/+attachment/5525715/+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/1943832 Title: Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA) Status in linux package in Ubuntu: New Bug description: ASUS UM425UA internal keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. I noticed it when tried to boot live image of Ubuntu 20.04.3 This problem probably appeared with kernel version 5.9 or 5.10 because with Ubuntu 20.04.2 live image (Linux 5.8) keyboard loads fine. Tried kernel 5.14 and it's still affected. I tried to recompile kernels 5.11 & 5.13 with SERIO_I8042 set as a module (as suggested in an Arch Linux bug report) and keyboard now works from the first start. In "make config" the changes are: Device Drivers -> > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for
[Kernel-packages] [Bug 1943832] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1943832/+attachment/5525717/+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/1943832 Title: Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA) Status in linux package in Ubuntu: New Bug description: ASUS UM425UA internal keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. I noticed it when tried to boot live image of Ubuntu 20.04.3 This problem probably appeared with kernel version 5.9 or 5.10 because with Ubuntu 20.04.2 live image (Linux 5.8) keyboard loads fine. Tried kernel 5.14 and it's still affected. I tried to recompile kernels 5.11 & 5.13 with SERIO_I8042 set as a module (as suggested in an Arch Linux bug report) and keyboard now works from the first start. In "make config" the changes are: Device Drivers -> > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for U14.04 > Input device support > Keyboards -> [M] AT keyboard > Hardware I/O ports -> [M] i8042 PC Keyboard controller It changed such lines in config: CONFIG_KEYBOARD_ATKBD=m CONFIG_SERIO_I8042=m CONFIG_SERIO_LIBPS2=m References: https://bugs.archlinux.org/task/70384 https://ubuntuforums.org/showthread.php?t=2459149 https://linux.org/threads/asus-zenbook-14-um425ua-keyboard-not-respond-during-cold-boot.33738/#post-133830 P.S. Other option which helped me was a GRUB parameter "i8042.reset=1" but it had a positive effect only with kernel 5.11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: marketing-trade807 F pulseaudio /dev/snd/controlC2: marketing-trade807 F pulseaudio /dev/snd/controlC1: marketing-trade807 F pulseaudio /dev/snd/controlC0: marketing-trade807 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-01 (14 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425UA_UM425UA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=3e7eadd0-dd33-487a-8e38-3e516c0dc8d5 ro quiet i8042.reset=1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.199 Tags: focal Uname: Linux 5.11.0-34-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: 04/01/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX425UA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425UA 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: 3.1 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX425UA.301:bd04/01/2021:br5.19:efr3.1:svnASUSTeKCOMPUTERINC.:pnZenBookUX425UA_UM425UA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX425UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425UA_UM425UA 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/1943832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943832] Re: Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA)
** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943832/+attachment/5525718/+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/1943832 Title: Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA) Status in linux package in Ubuntu: New Bug description: ASUS UM425UA internal keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. I noticed it when tried to boot live image of Ubuntu 20.04.3 This problem probably appeared with kernel version 5.9 or 5.10 because with Ubuntu 20.04.2 live image (Linux 5.8) keyboard loads fine. Tried kernel 5.14 and it's still affected. I tried to recompile kernels 5.11 & 5.13 with SERIO_I8042 set as a module (as suggested in an Arch Linux bug report) and keyboard now works from the first start. In "make config" the changes are: Device Drivers -> > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for U14.04 > Input device support > Keyboards -> [M] AT keyboard > Hardware I/O ports -> [M] i8042 PC Keyboard controller It changed such lines in config: CONFIG_KEYBOARD_ATKBD=m CONFIG_SERIO_I8042=m CONFIG_SERIO_LIBPS2=m References: https://bugs.archlinux.org/task/70384 https://ubuntuforums.org/showthread.php?t=2459149 https://linux.org/threads/asus-zenbook-14-um425ua-keyboard-not-respond-during-cold-boot.33738/#post-133830 P.S. Other option which helped me was a GRUB parameter "i8042.reset=1" but it had a positive effect only with kernel 5.11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: marketing-trade807 F pulseaudio /dev/snd/controlC2: marketing-trade807 F pulseaudio /dev/snd/controlC1: marketing-trade807 F pulseaudio /dev/snd/controlC0: marketing-trade807 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-01 (14 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425UA_UM425UA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=3e7eadd0-dd33-487a-8e38-3e516c0dc8d5 ro quiet i8042.reset=1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.199 Tags: focal Uname: Linux 5.11.0-34-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: 04/01/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX425UA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425UA 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: 3.1 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX425UA.301:bd04/01/2021:br5.19:efr3.1:svnASUSTeKCOMPUTERINC.:pnZenBookUX425UA_UM425UA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX425UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425UA_UM425UA 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/1943832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943832] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1943832/+attachment/5525716/+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/1943832 Title: Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA) Status in linux package in Ubuntu: New Bug description: ASUS UM425UA internal keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. I noticed it when tried to boot live image of Ubuntu 20.04.3 This problem probably appeared with kernel version 5.9 or 5.10 because with Ubuntu 20.04.2 live image (Linux 5.8) keyboard loads fine. Tried kernel 5.14 and it's still affected. I tried to recompile kernels 5.11 & 5.13 with SERIO_I8042 set as a module (as suggested in an Arch Linux bug report) and keyboard now works from the first start. In "make config" the changes are: Device Drivers -> > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for U14.04 > Input device support > Keyboards -> [M] AT keyboard > Hardware I/O ports -> [M] i8042 PC Keyboard controller It changed such lines in config: CONFIG_KEYBOARD_ATKBD=m CONFIG_SERIO_I8042=m CONFIG_SERIO_LIBPS2=m References: https://bugs.archlinux.org/task/70384 https://ubuntuforums.org/showthread.php?t=2459149 https://linux.org/threads/asus-zenbook-14-um425ua-keyboard-not-respond-during-cold-boot.33738/#post-133830 P.S. Other option which helped me was a GRUB parameter "i8042.reset=1" but it had a positive effect only with kernel 5.11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: marketing-trade807 F pulseaudio /dev/snd/controlC2: marketing-trade807 F pulseaudio /dev/snd/controlC1: marketing-trade807 F pulseaudio /dev/snd/controlC0: marketing-trade807 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-01 (14 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425UA_UM425UA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=3e7eadd0-dd33-487a-8e38-3e516c0dc8d5 ro quiet i8042.reset=1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.199 Tags: focal Uname: Linux 5.11.0-34-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: 04/01/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX425UA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425UA 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: 3.1 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX425UA.301:bd04/01/2021:br5.19:efr3.1:svnASUSTeKCOMPUTERINC.:pnZenBookUX425UA_UM425UA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX425UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425UA_UM425UA 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/1943832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943832] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1943832/+attachment/5525719/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1943832 Title: Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA) Status in linux package in Ubuntu: New Bug description: ASUS UM425UA internal keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. I noticed it when tried to boot live image of Ubuntu 20.04.3 This problem probably appeared with kernel version 5.9 or 5.10 because with Ubuntu 20.04.2 live image (Linux 5.8) keyboard loads fine. Tried kernel 5.14 and it's still affected. I tried to recompile kernels 5.11 & 5.13 with SERIO_I8042 set as a module (as suggested in an Arch Linux bug report) and keyboard now works from the first start. In "make config" the changes are: Device Drivers -> > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for U14.04 > Input device support > Keyboards -> [M] AT keyboard > Hardware I/O ports -> [M] i8042 PC Keyboard controller It changed such lines in config: CONFIG_KEYBOARD_ATKBD=m CONFIG_SERIO_I8042=m CONFIG_SERIO_LIBPS2=m References: https://bugs.archlinux.org/task/70384 https://ubuntuforums.org/showthread.php?t=2459149 https://linux.org/threads/asus-zenbook-14-um425ua-keyboard-not-respond-during-cold-boot.33738/#post-133830 P.S. Other option which helped me was a GRUB parameter "i8042.reset=1" but it had a positive effect only with kernel 5.11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: marketing-trade807 F pulseaudio /dev/snd/controlC2: marketing-trade807 F pulseaudio /dev/snd/controlC1: marketing-trade807 F pulseaudio /dev/snd/controlC0: marketing-trade807 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-01 (14 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425UA_UM425UA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=3e7eadd0-dd33-487a-8e38-3e516c0dc8d5 ro quiet i8042.reset=1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.199 Tags: focal Uname: Linux 5.11.0-34-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: 04/01/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX425UA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425UA 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: 3.1 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX425UA.301:bd04/01/2021:br5.19:efr3.1:svnASUSTeKCOMPUTERINC.:pnZenBookUX425UA_UM425UA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX425UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425UA_UM425UA 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/1943832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943832] WifiSyslog.txt
** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1943832/+attachment/5525718/+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/1943832 Title: Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA) Status in linux package in Ubuntu: New Bug description: ASUS UM425UA internal keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. I noticed it when tried to boot live image of Ubuntu 20.04.3 This problem probably appeared with kernel version 5.9 or 5.10 because with Ubuntu 20.04.2 live image (Linux 5.8) keyboard loads fine. Tried kernel 5.14 and it's still affected. I tried to recompile kernels 5.11 & 5.13 with SERIO_I8042 set as a module (as suggested in an Arch Linux bug report) and keyboard now works from the first start. In "make config" the changes are: Device Drivers -> > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for U14.04 > Input device support > Keyboards -> [M] AT keyboard > Hardware I/O ports -> [M] i8042 PC Keyboard controller It changed such lines in config: CONFIG_KEYBOARD_ATKBD=m CONFIG_SERIO_I8042=m CONFIG_SERIO_LIBPS2=m References: https://bugs.archlinux.org/task/70384 https://ubuntuforums.org/showthread.php?t=2459149 https://linux.org/threads/asus-zenbook-14-um425ua-keyboard-not-respond-during-cold-boot.33738/#post-133830 P.S. Other option which helped me was a GRUB parameter "i8042.reset=1" but it had a positive effect only with kernel 5.11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: marketing-trade807 F pulseaudio /dev/snd/controlC2: marketing-trade807 F pulseaudio /dev/snd/controlC1: marketing-trade807 F pulseaudio /dev/snd/controlC0: marketing-trade807 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-01 (14 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425UA_UM425UA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=3e7eadd0-dd33-487a-8e38-3e516c0dc8d5 ro quiet i8042.reset=1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.199 Tags: focal Uname: Linux 5.11.0-34-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: 04/01/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX425UA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425UA 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: 3.1 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX425UA.301:bd04/01/2021:br5.19:efr3.1:svnASUSTeKCOMPUTERINC.:pnZenBookUX425UA_UM425UA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX425UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425UA_UM425UA 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/1943832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943832] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1943832/+attachment/5525714/+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/1943832 Title: Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA) Status in linux package in Ubuntu: New Bug description: ASUS UM425UA internal keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. I noticed it when tried to boot live image of Ubuntu 20.04.3 This problem probably appeared with kernel version 5.9 or 5.10 because with Ubuntu 20.04.2 live image (Linux 5.8) keyboard loads fine. Tried kernel 5.14 and it's still affected. I tried to recompile kernels 5.11 & 5.13 with SERIO_I8042 set as a module (as suggested in an Arch Linux bug report) and keyboard now works from the first start. In "make config" the changes are: Device Drivers -> > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for U14.04 > Input device support > Keyboards -> [M] AT keyboard > Hardware I/O ports -> [M] i8042 PC Keyboard controller It changed such lines in config: CONFIG_KEYBOARD_ATKBD=m CONFIG_SERIO_I8042=m CONFIG_SERIO_LIBPS2=m References: https://bugs.archlinux.org/task/70384 https://ubuntuforums.org/showthread.php?t=2459149 https://linux.org/threads/asus-zenbook-14-um425ua-keyboard-not-respond-during-cold-boot.33738/#post-133830 P.S. Other option which helped me was a GRUB parameter "i8042.reset=1" but it had a positive effect only with kernel 5.11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: marketing-trade807 F pulseaudio /dev/snd/controlC2: marketing-trade807 F pulseaudio /dev/snd/controlC1: marketing-trade807 F pulseaudio /dev/snd/controlC0: marketing-trade807 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-01 (14 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425UA_UM425UA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=3e7eadd0-dd33-487a-8e38-3e516c0dc8d5 ro quiet i8042.reset=1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.199 Tags: focal Uname: Linux 5.11.0-34-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: 04/01/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX425UA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425UA 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: 3.1 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX425UA.301:bd04/01/2021:br5.19:efr3.1:svnASUSTeKCOMPUTERINC.:pnZenBookUX425UA_UM425UA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX425UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425UA_UM425UA 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/1943832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943832] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1943832/+attachment/5525712/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943832 Title: Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA) Status in linux package in Ubuntu: New Bug description: ASUS UM425UA internal keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. I noticed it when tried to boot live image of Ubuntu 20.04.3 This problem probably appeared with kernel version 5.9 or 5.10 because with Ubuntu 20.04.2 live image (Linux 5.8) keyboard loads fine. Tried kernel 5.14 and it's still affected. I tried to recompile kernels 5.11 & 5.13 with SERIO_I8042 set as a module (as suggested in an Arch Linux bug report) and keyboard now works from the first start. In "make config" the changes are: Device Drivers -> > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for U14.04 > Input device support > Keyboards -> [M] AT keyboard > Hardware I/O ports -> [M] i8042 PC Keyboard controller It changed such lines in config: CONFIG_KEYBOARD_ATKBD=m CONFIG_SERIO_I8042=m CONFIG_SERIO_LIBPS2=m References: https://bugs.archlinux.org/task/70384 https://ubuntuforums.org/showthread.php?t=2459149 https://linux.org/threads/asus-zenbook-14-um425ua-keyboard-not-respond-during-cold-boot.33738/#post-133830 P.S. Other option which helped me was a GRUB parameter "i8042.reset=1" but it had a positive effect only with kernel 5.11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: marketing-trade807 F pulseaudio /dev/snd/controlC2: marketing-trade807 F pulseaudio /dev/snd/controlC1: marketing-trade807 F pulseaudio /dev/snd/controlC0: marketing-trade807 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-01 (14 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425UA_UM425UA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=3e7eadd0-dd33-487a-8e38-3e516c0dc8d5 ro quiet i8042.reset=1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.199 Tags: focal Uname: Linux 5.11.0-34-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: 04/01/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX425UA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425UA 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: 3.1 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX425UA.301:bd04/01/2021:br5.19:efr3.1:svnASUSTeKCOMPUTERINC.:pnZenBookUX425UA_UM425UA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX425UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425UA_UM425UA 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/1943832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943832] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1943832/+attachment/5525715/+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/1943832 Title: Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA) Status in linux package in Ubuntu: New Bug description: ASUS UM425UA internal keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. I noticed it when tried to boot live image of Ubuntu 20.04.3 This problem probably appeared with kernel version 5.9 or 5.10 because with Ubuntu 20.04.2 live image (Linux 5.8) keyboard loads fine. Tried kernel 5.14 and it's still affected. I tried to recompile kernels 5.11 & 5.13 with SERIO_I8042 set as a module (as suggested in an Arch Linux bug report) and keyboard now works from the first start. In "make config" the changes are: Device Drivers -> > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for U14.04 > Input device support > Keyboards -> [M] AT keyboard > Hardware I/O ports -> [M] i8042 PC Keyboard controller It changed such lines in config: CONFIG_KEYBOARD_ATKBD=m CONFIG_SERIO_I8042=m CONFIG_SERIO_LIBPS2=m References: https://bugs.archlinux.org/task/70384 https://ubuntuforums.org/showthread.php?t=2459149 https://linux.org/threads/asus-zenbook-14-um425ua-keyboard-not-respond-during-cold-boot.33738/#post-133830 P.S. Other option which helped me was a GRUB parameter "i8042.reset=1" but it had a positive effect only with kernel 5.11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: marketing-trade807 F pulseaudio /dev/snd/controlC2: marketing-trade807 F pulseaudio /dev/snd/controlC1: marketing-trade807 F pulseaudio /dev/snd/controlC0: marketing-trade807 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-01 (14 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425UA_UM425UA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=3e7eadd0-dd33-487a-8e38-3e516c0dc8d5 ro quiet i8042.reset=1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.199 Tags: focal Uname: Linux 5.11.0-34-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: 04/01/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX425UA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425UA 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: 3.1 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX425UA.301:bd04/01/2021:br5.19:efr3.1:svnASUSTeKCOMPUTERINC.:pnZenBookUX425UA_UM425UA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX425UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425UA_UM425UA 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/1943832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943832] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1943832/+attachment/5525711/+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/1943832 Title: Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA) Status in linux package in Ubuntu: New Bug description: ASUS UM425UA internal keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. I noticed it when tried to boot live image of Ubuntu 20.04.3 This problem probably appeared with kernel version 5.9 or 5.10 because with Ubuntu 20.04.2 live image (Linux 5.8) keyboard loads fine. Tried kernel 5.14 and it's still affected. I tried to recompile kernels 5.11 & 5.13 with SERIO_I8042 set as a module (as suggested in an Arch Linux bug report) and keyboard now works from the first start. In "make config" the changes are: Device Drivers -> > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for U14.04 > Input device support > Keyboards -> [M] AT keyboard > Hardware I/O ports -> [M] i8042 PC Keyboard controller It changed such lines in config: CONFIG_KEYBOARD_ATKBD=m CONFIG_SERIO_I8042=m CONFIG_SERIO_LIBPS2=m References: https://bugs.archlinux.org/task/70384 https://ubuntuforums.org/showthread.php?t=2459149 https://linux.org/threads/asus-zenbook-14-um425ua-keyboard-not-respond-during-cold-boot.33738/#post-133830 P.S. Other option which helped me was a GRUB parameter "i8042.reset=1" but it had a positive effect only with kernel 5.11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: marketing-trade807 F pulseaudio /dev/snd/controlC2: marketing-trade807 F pulseaudio /dev/snd/controlC1: marketing-trade807 F pulseaudio /dev/snd/controlC0: marketing-trade807 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-01 (14 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425UA_UM425UA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=3e7eadd0-dd33-487a-8e38-3e516c0dc8d5 ro quiet i8042.reset=1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.199 Tags: focal Uname: Linux 5.11.0-34-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: 04/01/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX425UA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425UA 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: 3.1 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX425UA.301:bd04/01/2021:br5.19:efr3.1:svnASUSTeKCOMPUTERINC.:pnZenBookUX425UA_UM425UA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX425UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425UA_UM425UA 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/1943832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943832] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1943832/+attachment/5525708/+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/1943832 Title: Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA) Status in linux package in Ubuntu: New Bug description: ASUS UM425UA internal keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. I noticed it when tried to boot live image of Ubuntu 20.04.3 This problem probably appeared with kernel version 5.9 or 5.10 because with Ubuntu 20.04.2 live image (Linux 5.8) keyboard loads fine. Tried kernel 5.14 and it's still affected. I tried to recompile kernels 5.11 & 5.13 with SERIO_I8042 set as a module (as suggested in an Arch Linux bug report) and keyboard now works from the first start. In "make config" the changes are: Device Drivers -> > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for U14.04 > Input device support > Keyboards -> [M] AT keyboard > Hardware I/O ports -> [M] i8042 PC Keyboard controller It changed such lines in config: CONFIG_KEYBOARD_ATKBD=m CONFIG_SERIO_I8042=m CONFIG_SERIO_LIBPS2=m References: https://bugs.archlinux.org/task/70384 https://ubuntuforums.org/showthread.php?t=2459149 https://linux.org/threads/asus-zenbook-14-um425ua-keyboard-not-respond-during-cold-boot.33738/#post-133830 P.S. Other option which helped me was a GRUB parameter "i8042.reset=1" but it had a positive effect only with kernel 5.11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: marketing-trade807 F pulseaudio /dev/snd/controlC2: marketing-trade807 F pulseaudio /dev/snd/controlC1: marketing-trade807 F pulseaudio /dev/snd/controlC0: marketing-trade807 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-01 (14 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425UA_UM425UA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=3e7eadd0-dd33-487a-8e38-3e516c0dc8d5 ro quiet i8042.reset=1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.199 Tags: focal Uname: Linux 5.11.0-34-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: 04/01/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX425UA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425UA 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: 3.1 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX425UA.301:bd04/01/2021:br5.19:efr3.1:svnASUSTeKCOMPUTERINC.:pnZenBookUX425UA_UM425UA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX425UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425UA_UM425UA 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/1943832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943832] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1943832/+attachment/5525702/+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/1943832 Title: Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA) Status in linux package in Ubuntu: New Bug description: ASUS UM425UA internal keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. I noticed it when tried to boot live image of Ubuntu 20.04.3 This problem probably appeared with kernel version 5.9 or 5.10 because with Ubuntu 20.04.2 live image (Linux 5.8) keyboard loads fine. Tried kernel 5.14 and it's still affected. I tried to recompile kernels 5.11 & 5.13 with SERIO_I8042 set as a module (as suggested in an Arch Linux bug report) and keyboard now works from the first start. In "make config" the changes are: Device Drivers -> > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for U14.04 > Input device support > Keyboards -> [M] AT keyboard > Hardware I/O ports -> [M] i8042 PC Keyboard controller It changed such lines in config: CONFIG_KEYBOARD_ATKBD=m CONFIG_SERIO_I8042=m CONFIG_SERIO_LIBPS2=m References: https://bugs.archlinux.org/task/70384 https://ubuntuforums.org/showthread.php?t=2459149 https://linux.org/threads/asus-zenbook-14-um425ua-keyboard-not-respond-during-cold-boot.33738/#post-133830 P.S. Other option which helped me was a GRUB parameter "i8042.reset=1" but it had a positive effect only with kernel 5.11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: marketing-trade807 F pulseaudio /dev/snd/controlC2: marketing-trade807 F pulseaudio /dev/snd/controlC1: marketing-trade807 F pulseaudio /dev/snd/controlC0: marketing-trade807 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-01 (14 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425UA_UM425UA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=3e7eadd0-dd33-487a-8e38-3e516c0dc8d5 ro quiet i8042.reset=1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.199 Tags: focal Uname: Linux 5.11.0-34-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: 04/01/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX425UA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425UA 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: 3.1 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX425UA.301:bd04/01/2021:br5.19:efr3.1:svnASUSTeKCOMPUTERINC.:pnZenBookUX425UA_UM425UA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX425UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425UA_UM425UA 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/1943832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943832] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1943832/+attachment/5525709/+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/1943832 Title: Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA) Status in linux package in Ubuntu: New Bug description: ASUS UM425UA internal keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. I noticed it when tried to boot live image of Ubuntu 20.04.3 This problem probably appeared with kernel version 5.9 or 5.10 because with Ubuntu 20.04.2 live image (Linux 5.8) keyboard loads fine. Tried kernel 5.14 and it's still affected. I tried to recompile kernels 5.11 & 5.13 with SERIO_I8042 set as a module (as suggested in an Arch Linux bug report) and keyboard now works from the first start. In "make config" the changes are: Device Drivers -> > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for U14.04 > Input device support > Keyboards -> [M] AT keyboard > Hardware I/O ports -> [M] i8042 PC Keyboard controller It changed such lines in config: CONFIG_KEYBOARD_ATKBD=m CONFIG_SERIO_I8042=m CONFIG_SERIO_LIBPS2=m References: https://bugs.archlinux.org/task/70384 https://ubuntuforums.org/showthread.php?t=2459149 https://linux.org/threads/asus-zenbook-14-um425ua-keyboard-not-respond-during-cold-boot.33738/#post-133830 P.S. Other option which helped me was a GRUB parameter "i8042.reset=1" but it had a positive effect only with kernel 5.11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: marketing-trade807 F pulseaudio /dev/snd/controlC2: marketing-trade807 F pulseaudio /dev/snd/controlC1: marketing-trade807 F pulseaudio /dev/snd/controlC0: marketing-trade807 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-01 (14 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425UA_UM425UA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=3e7eadd0-dd33-487a-8e38-3e516c0dc8d5 ro quiet i8042.reset=1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.199 Tags: focal Uname: Linux 5.11.0-34-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: 04/01/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX425UA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425UA 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: 3.1 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX425UA.301:bd04/01/2021:br5.19:efr3.1:svnASUSTeKCOMPUTERINC.:pnZenBookUX425UA_UM425UA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX425UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425UA_UM425UA 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/1943832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943832] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1943832/+attachment/5525710/+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/1943832 Title: Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA) Status in linux package in Ubuntu: New Bug description: ASUS UM425UA internal keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. I noticed it when tried to boot live image of Ubuntu 20.04.3 This problem probably appeared with kernel version 5.9 or 5.10 because with Ubuntu 20.04.2 live image (Linux 5.8) keyboard loads fine. Tried kernel 5.14 and it's still affected. I tried to recompile kernels 5.11 & 5.13 with SERIO_I8042 set as a module (as suggested in an Arch Linux bug report) and keyboard now works from the first start. In "make config" the changes are: Device Drivers -> > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for U14.04 > Input device support > Keyboards -> [M] AT keyboard > Hardware I/O ports -> [M] i8042 PC Keyboard controller It changed such lines in config: CONFIG_KEYBOARD_ATKBD=m CONFIG_SERIO_I8042=m CONFIG_SERIO_LIBPS2=m References: https://bugs.archlinux.org/task/70384 https://ubuntuforums.org/showthread.php?t=2459149 https://linux.org/threads/asus-zenbook-14-um425ua-keyboard-not-respond-during-cold-boot.33738/#post-133830 P.S. Other option which helped me was a GRUB parameter "i8042.reset=1" but it had a positive effect only with kernel 5.11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: marketing-trade807 F pulseaudio /dev/snd/controlC2: marketing-trade807 F pulseaudio /dev/snd/controlC1: marketing-trade807 F pulseaudio /dev/snd/controlC0: marketing-trade807 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-01 (14 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425UA_UM425UA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=3e7eadd0-dd33-487a-8e38-3e516c0dc8d5 ro quiet i8042.reset=1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.199 Tags: focal Uname: Linux 5.11.0-34-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: 04/01/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX425UA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425UA 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: 3.1 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX425UA.301:bd04/01/2021:br5.19:efr3.1:svnASUSTeKCOMPUTERINC.:pnZenBookUX425UA_UM425UA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX425UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425UA_UM425UA 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/1943832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943832] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1943832/+attachment/5525704/+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/1943832 Title: Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA) Status in linux package in Ubuntu: New Bug description: ASUS UM425UA internal keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. I noticed it when tried to boot live image of Ubuntu 20.04.3 This problem probably appeared with kernel version 5.9 or 5.10 because with Ubuntu 20.04.2 live image (Linux 5.8) keyboard loads fine. Tried kernel 5.14 and it's still affected. I tried to recompile kernels 5.11 & 5.13 with SERIO_I8042 set as a module (as suggested in an Arch Linux bug report) and keyboard now works from the first start. In "make config" the changes are: Device Drivers -> > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for U14.04 > Input device support > Keyboards -> [M] AT keyboard > Hardware I/O ports -> [M] i8042 PC Keyboard controller It changed such lines in config: CONFIG_KEYBOARD_ATKBD=m CONFIG_SERIO_I8042=m CONFIG_SERIO_LIBPS2=m References: https://bugs.archlinux.org/task/70384 https://ubuntuforums.org/showthread.php?t=2459149 https://linux.org/threads/asus-zenbook-14-um425ua-keyboard-not-respond-during-cold-boot.33738/#post-133830 P.S. Other option which helped me was a GRUB parameter "i8042.reset=1" but it had a positive effect only with kernel 5.11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: marketing-trade807 F pulseaudio /dev/snd/controlC2: marketing-trade807 F pulseaudio /dev/snd/controlC1: marketing-trade807 F pulseaudio /dev/snd/controlC0: marketing-trade807 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-01 (14 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425UA_UM425UA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=3e7eadd0-dd33-487a-8e38-3e516c0dc8d5 ro quiet i8042.reset=1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.199 Tags: focal Uname: Linux 5.11.0-34-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: 04/01/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX425UA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425UA 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: 3.1 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX425UA.301:bd04/01/2021:br5.19:efr3.1:svnASUSTeKCOMPUTERINC.:pnZenBookUX425UA_UM425UA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX425UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425UA_UM425UA 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/1943832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943832] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1943832/+attachment/5525706/+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/1943832 Title: Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA) Status in linux package in Ubuntu: New Bug description: ASUS UM425UA internal keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. I noticed it when tried to boot live image of Ubuntu 20.04.3 This problem probably appeared with kernel version 5.9 or 5.10 because with Ubuntu 20.04.2 live image (Linux 5.8) keyboard loads fine. Tried kernel 5.14 and it's still affected. I tried to recompile kernels 5.11 & 5.13 with SERIO_I8042 set as a module (as suggested in an Arch Linux bug report) and keyboard now works from the first start. In "make config" the changes are: Device Drivers -> > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for U14.04 > Input device support > Keyboards -> [M] AT keyboard > Hardware I/O ports -> [M] i8042 PC Keyboard controller It changed such lines in config: CONFIG_KEYBOARD_ATKBD=m CONFIG_SERIO_I8042=m CONFIG_SERIO_LIBPS2=m References: https://bugs.archlinux.org/task/70384 https://ubuntuforums.org/showthread.php?t=2459149 https://linux.org/threads/asus-zenbook-14-um425ua-keyboard-not-respond-during-cold-boot.33738/#post-133830 P.S. Other option which helped me was a GRUB parameter "i8042.reset=1" but it had a positive effect only with kernel 5.11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: marketing-trade807 F pulseaudio /dev/snd/controlC2: marketing-trade807 F pulseaudio /dev/snd/controlC1: marketing-trade807 F pulseaudio /dev/snd/controlC0: marketing-trade807 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-01 (14 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425UA_UM425UA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=3e7eadd0-dd33-487a-8e38-3e516c0dc8d5 ro quiet i8042.reset=1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.199 Tags: focal Uname: Linux 5.11.0-34-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: 04/01/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX425UA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425UA 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: 3.1 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX425UA.301:bd04/01/2021:br5.19:efr3.1:svnASUSTeKCOMPUTERINC.:pnZenBookUX425UA_UM425UA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX425UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425UA_UM425UA 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/1943832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943832] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1943832/+attachment/5525705/+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/1943832 Title: Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA) Status in linux package in Ubuntu: New Bug description: ASUS UM425UA internal keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. I noticed it when tried to boot live image of Ubuntu 20.04.3 This problem probably appeared with kernel version 5.9 or 5.10 because with Ubuntu 20.04.2 live image (Linux 5.8) keyboard loads fine. Tried kernel 5.14 and it's still affected. I tried to recompile kernels 5.11 & 5.13 with SERIO_I8042 set as a module (as suggested in an Arch Linux bug report) and keyboard now works from the first start. In "make config" the changes are: Device Drivers -> > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for U14.04 > Input device support > Keyboards -> [M] AT keyboard > Hardware I/O ports -> [M] i8042 PC Keyboard controller It changed such lines in config: CONFIG_KEYBOARD_ATKBD=m CONFIG_SERIO_I8042=m CONFIG_SERIO_LIBPS2=m References: https://bugs.archlinux.org/task/70384 https://ubuntuforums.org/showthread.php?t=2459149 https://linux.org/threads/asus-zenbook-14-um425ua-keyboard-not-respond-during-cold-boot.33738/#post-133830 P.S. Other option which helped me was a GRUB parameter "i8042.reset=1" but it had a positive effect only with kernel 5.11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: marketing-trade807 F pulseaudio /dev/snd/controlC2: marketing-trade807 F pulseaudio /dev/snd/controlC1: marketing-trade807 F pulseaudio /dev/snd/controlC0: marketing-trade807 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-01 (14 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425UA_UM425UA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=3e7eadd0-dd33-487a-8e38-3e516c0dc8d5 ro quiet i8042.reset=1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.199 Tags: focal Uname: Linux 5.11.0-34-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: 04/01/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX425UA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425UA 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: 3.1 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX425UA.301:bd04/01/2021:br5.19:efr3.1:svnASUSTeKCOMPUTERINC.:pnZenBookUX425UA_UM425UA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX425UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425UA_UM425UA 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/1943832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943832] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1943832/+attachment/5525713/+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/1943832 Title: Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA) Status in linux package in Ubuntu: New Bug description: ASUS UM425UA internal keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. I noticed it when tried to boot live image of Ubuntu 20.04.3 This problem probably appeared with kernel version 5.9 or 5.10 because with Ubuntu 20.04.2 live image (Linux 5.8) keyboard loads fine. Tried kernel 5.14 and it's still affected. I tried to recompile kernels 5.11 & 5.13 with SERIO_I8042 set as a module (as suggested in an Arch Linux bug report) and keyboard now works from the first start. In "make config" the changes are: Device Drivers -> > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for U14.04 > Input device support > Keyboards -> [M] AT keyboard > Hardware I/O ports -> [M] i8042 PC Keyboard controller It changed such lines in config: CONFIG_KEYBOARD_ATKBD=m CONFIG_SERIO_I8042=m CONFIG_SERIO_LIBPS2=m References: https://bugs.archlinux.org/task/70384 https://ubuntuforums.org/showthread.php?t=2459149 https://linux.org/threads/asus-zenbook-14-um425ua-keyboard-not-respond-during-cold-boot.33738/#post-133830 P.S. Other option which helped me was a GRUB parameter "i8042.reset=1" but it had a positive effect only with kernel 5.11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: marketing-trade807 F pulseaudio /dev/snd/controlC2: marketing-trade807 F pulseaudio /dev/snd/controlC1: marketing-trade807 F pulseaudio /dev/snd/controlC0: marketing-trade807 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-01 (14 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425UA_UM425UA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=3e7eadd0-dd33-487a-8e38-3e516c0dc8d5 ro quiet i8042.reset=1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.199 Tags: focal Uname: Linux 5.11.0-34-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: 04/01/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX425UA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425UA 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: 3.1 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX425UA.301:bd04/01/2021:br5.19:efr3.1:svnASUSTeKCOMPUTERINC.:pnZenBookUX425UA_UM425UA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX425UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425UA_UM425UA 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/1943832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943832] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1943832/+attachment/5525707/+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/1943832 Title: Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA) Status in linux package in Ubuntu: New Bug description: ASUS UM425UA internal keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. I noticed it when tried to boot live image of Ubuntu 20.04.3 This problem probably appeared with kernel version 5.9 or 5.10 because with Ubuntu 20.04.2 live image (Linux 5.8) keyboard loads fine. Tried kernel 5.14 and it's still affected. I tried to recompile kernels 5.11 & 5.13 with SERIO_I8042 set as a module (as suggested in an Arch Linux bug report) and keyboard now works from the first start. In "make config" the changes are: Device Drivers -> > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for U14.04 > Input device support > Keyboards -> [M] AT keyboard > Hardware I/O ports -> [M] i8042 PC Keyboard controller It changed such lines in config: CONFIG_KEYBOARD_ATKBD=m CONFIG_SERIO_I8042=m CONFIG_SERIO_LIBPS2=m References: https://bugs.archlinux.org/task/70384 https://ubuntuforums.org/showthread.php?t=2459149 https://linux.org/threads/asus-zenbook-14-um425ua-keyboard-not-respond-during-cold-boot.33738/#post-133830 P.S. Other option which helped me was a GRUB parameter "i8042.reset=1" but it had a positive effect only with kernel 5.11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: marketing-trade807 F pulseaudio /dev/snd/controlC2: marketing-trade807 F pulseaudio /dev/snd/controlC1: marketing-trade807 F pulseaudio /dev/snd/controlC0: marketing-trade807 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-01 (14 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425UA_UM425UA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=3e7eadd0-dd33-487a-8e38-3e516c0dc8d5 ro quiet i8042.reset=1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.199 Tags: focal Uname: Linux 5.11.0-34-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: 04/01/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX425UA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425UA 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: 3.1 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX425UA.301:bd04/01/2021:br5.19:efr3.1:svnASUSTeKCOMPUTERINC.:pnZenBookUX425UA_UM425UA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX425UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425UA_UM425UA 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/1943832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943832] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1943832/+attachment/5525703/+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/1943832 Title: Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA) Status in linux package in Ubuntu: New Bug description: ASUS UM425UA internal keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. I noticed it when tried to boot live image of Ubuntu 20.04.3 This problem probably appeared with kernel version 5.9 or 5.10 because with Ubuntu 20.04.2 live image (Linux 5.8) keyboard loads fine. Tried kernel 5.14 and it's still affected. I tried to recompile kernels 5.11 & 5.13 with SERIO_I8042 set as a module (as suggested in an Arch Linux bug report) and keyboard now works from the first start. In "make config" the changes are: Device Drivers -> > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for U14.04 > Input device support > Keyboards -> [M] AT keyboard > Hardware I/O ports -> [M] i8042 PC Keyboard controller It changed such lines in config: CONFIG_KEYBOARD_ATKBD=m CONFIG_SERIO_I8042=m CONFIG_SERIO_LIBPS2=m References: https://bugs.archlinux.org/task/70384 https://ubuntuforums.org/showthread.php?t=2459149 https://linux.org/threads/asus-zenbook-14-um425ua-keyboard-not-respond-during-cold-boot.33738/#post-133830 P.S. Other option which helped me was a GRUB parameter "i8042.reset=1" but it had a positive effect only with kernel 5.11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: marketing-trade807 F pulseaudio /dev/snd/controlC2: marketing-trade807 F pulseaudio /dev/snd/controlC1: marketing-trade807 F pulseaudio /dev/snd/controlC0: marketing-trade807 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-01 (14 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425UA_UM425UA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=3e7eadd0-dd33-487a-8e38-3e516c0dc8d5 ro quiet i8042.reset=1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.199 Tags: focal Uname: Linux 5.11.0-34-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: 04/01/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX425UA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425UA 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: 3.1 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX425UA.301:bd04/01/2021:br5.19:efr3.1:svnASUSTeKCOMPUTERINC.:pnZenBookUX425UA_UM425UA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX425UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425UA_UM425UA 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/1943832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943832] Re: Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA)
apport information ** Tags added: apport-collected focal ** Description changed: ASUS UM425UA internal keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. I noticed it when tried to boot live image of Ubuntu 20.04.3 This problem probably appeared with kernel version 5.9 or 5.10 because with Ubuntu 20.04.2 live image (Linux 5.8) keyboard loads fine. Tried kernel 5.14 and it's still affected. I tried to recompile kernels 5.11 & 5.13 with SERIO_I8042 set as a module (as suggested in an Arch Linux bug report) and keyboard now works from the first start. In "make config" the changes are: Device Drivers -> > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for U14.04 > Input device support > Keyboards -> [M] AT keyboard > Hardware I/O ports -> [M] i8042 PC Keyboard controller It changed such lines in config: CONFIG_KEYBOARD_ATKBD=m CONFIG_SERIO_I8042=m CONFIG_SERIO_LIBPS2=m References: https://bugs.archlinux.org/task/70384 https://ubuntuforums.org/showthread.php?t=2459149 https://linux.org/threads/asus-zenbook-14-um425ua-keyboard-not-respond-during-cold-boot.33738/#post-133830 - P.S. Other option which helped me was a GRUB parameter "i8042.reset=1" - but it had a positive effect only with kernel 5.11 + P.S. Other option which helped me was a GRUB parameter "i8042.reset=1" but it had a positive effect only with kernel 5.11 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.20 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC3: marketing-trade807 F pulseaudio + /dev/snd/controlC2: marketing-trade807 F pulseaudio + /dev/snd/controlC1: marketing-trade807 F pulseaudio + /dev/snd/controlC0: marketing-trade807 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: KDE + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2021-09-01 (14 days ago) + InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) + MachineType: ASUSTeK COMPUTER INC. ZenBook UX425UA_UM425UA + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=3e7eadd0-dd33-487a-8e38-3e516c0dc8d5 ro quiet i8042.reset=1 + ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 + RelatedPackageVersions: + linux-restricted-modules-5.11.0-34-generic N/A + linux-backports-modules-5.11.0-34-generic N/A + linux-firmware 1.199 + Tags: focal + Uname: Linux 5.11.0-34-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: 04/01/2021 + dmi.bios.release: 5.19 + dmi.bios.vendor: American Megatrends International, LLC. + dmi.bios.version: UX425UA.301 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: UX425UA + 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: 3.1 + dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX425UA.301:bd04/01/2021:br5.19:efr3.1:svnASUSTeKCOMPUTERINC.:pnZenBookUX425UA_UM425UA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX425UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: + dmi.product.family: ZenBook + dmi.product.name: ZenBook UX425UA_UM425UA + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1943832/+attachment/5525701/+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/1943832 Title: Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA) Status in linux package in Ubuntu: New Bug description: ASUS UM425UA internal keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. I noticed it when tried to boot live image of Ubuntu 20.04.3 This problem probably appeared with kernel version 5.9 or 5.10 because with Ubuntu 20.04.2 live image (Linux 5.8) keyboard loads fine. Tried kernel 5.14 and it's still affected. I tried to recompile kernels 5.11 & 5.13 with SERIO_I8042 set as a module (as suggested in an Arch Linux bug report) and keyboard now works from the first start. In "make config" the changes are: Device Drivers -> > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for U14.04 > Input device support > Keyboards -> [M] AT keyboard > Hardware I/O ports -> [M] i8042 PC Keyboard controller It changed such lines in config: CONFIG_KEYBOARD_ATKBD=m CONFIG_SERIO_I8042=m
[Kernel-packages] [Bug 1939966] Re: Random system stops
It did the blackscreen crash thing again, so I ran journalctl. Hopefully, this one has some more answers. ** Attachment added: "prevboot-2021-09-16-post-crash.txt" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1939966/+attachment/5525699/+files/prevboot-2021-09-16-post-crash.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939966 Title: Random system stops Status in linux-hwe-5.11 package in Ubuntu: Incomplete Bug description: Every once in a while (it's been three times this week), the entire system will just stop. There's still electricity running. The keyboard is lit up, and the monitor is black (electricity-running black, and not shutdown-black). There's no picture and no sound. Just immediately before it does, I know it's about to happen because whatever audio is playing at the time will begin repeating, and then the computer goes down. I don't actually know if it's an Xorg problem. It just sounded like the closest possibility, based on the way the computer actually behaves. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.57.02 Tue Jul 13 16:14:05 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Aug 14 19:34:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1e21] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21] InstallationDate: Installed on 2021-03-20 (147 days ago) InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506IV.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506IV 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: 3.9 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:br5.16:efr3.9:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming FA506IV dmi.product.name: TUF Gaming FA506IV_TUF506IV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1909005] Re: Ubuntu does not resume (wake up) from suspend
I have got the same issue here on two Lenovo notebooks. One is a T14 and the other one is a T480. Kernel is 5.11.0-34-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux- image-5.0.0-1070-oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943832] 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 1943832 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/1943832 Title: Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA) Status in linux package in Ubuntu: Incomplete Bug description: ASUS UM425UA internal keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. I noticed it when tried to boot live image of Ubuntu 20.04.3 This problem probably appeared with kernel version 5.9 or 5.10 because with Ubuntu 20.04.2 live image (Linux 5.8) keyboard loads fine. Tried kernel 5.14 and it's still affected. I tried to recompile kernels 5.11 & 5.13 with SERIO_I8042 set as a module (as suggested in an Arch Linux bug report) and keyboard now works from the first start. In "make config" the changes are: Device Drivers -> > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for U14.04 > Input device support > Keyboards -> [M] AT keyboard > Hardware I/O ports -> [M] i8042 PC Keyboard controller It changed such lines in config: CONFIG_KEYBOARD_ATKBD=m CONFIG_SERIO_I8042=m CONFIG_SERIO_LIBPS2=m References: https://bugs.archlinux.org/task/70384 https://ubuntuforums.org/showthread.php?t=2459149 https://linux.org/threads/asus-zenbook-14-um425ua-keyboard-not-respond-during-cold-boot.33738/#post-133830 P.S. Other option which helped me was a GRUB parameter "i8042.reset=1" but it had a positive effect only with kernel 5.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943832] [NEW] Keyboard doesn't work on a "cold boot" with built-in "i8042 PC Keyboard controller" (ASUS UM425UA)
Public bug reported: ASUS UM425UA internal keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. I noticed it when tried to boot live image of Ubuntu 20.04.3 This problem probably appeared with kernel version 5.9 or 5.10 because with Ubuntu 20.04.2 live image (Linux 5.8) keyboard loads fine. Tried kernel 5.14 and it's still affected. I tried to recompile kernels 5.11 & 5.13 with SERIO_I8042 set as a module (as suggested in an Arch Linux bug report) and keyboard now works from the first start. In "make config" the changes are: Device Drivers -> > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for U14.04 > Input device support > Keyboards -> [M] AT keyboard > Hardware I/O ports -> [M] i8042 PC Keyboard controller It changed such lines in config: CONFIG_KEYBOARD_ATKBD=m CONFIG_SERIO_I8042=m CONFIG_SERIO_LIBPS2=m References: https://bugs.archlinux.org/task/70384 https://ubuntuforums.org/showthread.php?t=2459149 https://linux.org/threads/asus-zenbook-14-um425ua-keyboard-not-respond-during-cold-boot.33738/#post-133830 P.S. Other option which helped me was a GRUB parameter "i8042.reset=1" but it had a positive effect only with kernel 5.11 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: asus i8042 keyboard serio um425ua ** Description changed: - ASUS UM425UA doesn't work on a "cold boot" (first power-on). It activates only after restart. + ASUS UM425UA internval keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. I noticed it when tried to install Ubuntu 20.04.3. This problem probably appeared with kernel version 5.9 or 5.10 because with Ubuntu 20.04.2 live image (Linux 5.8) keyboard loads fine. I tried to recompile kernel with SERIO_I8042 (link to Arch bug report bellow) set as a module and keyboard works now. In "make config" the changes are: Device Drivers -> - > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for U14.04 - > Input device support - > Keyboards -> [M] AT keyboard - > Hardware I/O ports -> [M] i8042 PC Keyboard controller + > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for U14.04 + > Input device support + > Keyboards -> [M] AT keyboard + > Hardware I/O ports -> [M] i8042 PC Keyboard controller It changed such lines in config: CONFIG_KEYBOARD_ATKBD=m CONFIG_SERIO_I8042=m CONFIG_SERIO_LIBPS2=m - References: https://bugs.archlinux.org/task/70384 https://ubuntuforums.org/showthread.php?t=2459149 https://linux.org/threads/asus-zenbook-14-um425ua-keyboard-not-respond-during-cold-boot.33738/#post-133830 ** Description changed: - ASUS UM425UA internval keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. + ASUS UM425UA internal keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. I noticed it when tried to install Ubuntu 20.04.3. This problem probably appeared with kernel version 5.9 or 5.10 because with Ubuntu 20.04.2 live image (Linux 5.8) keyboard loads fine. I tried to recompile kernel with SERIO_I8042 (link to Arch bug report bellow) set as a module and keyboard works now. In "make config" the changes are: Device Drivers -> > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for U14.04 > Input device support > Keyboards -> [M] AT keyboard > Hardware I/O ports -> [M] i8042 PC Keyboard controller It changed such lines in config: CONFIG_KEYBOARD_ATKBD=m CONFIG_SERIO_I8042=m CONFIG_SERIO_LIBPS2=m References: https://bugs.archlinux.org/task/70384 https://ubuntuforums.org/showthread.php?t=2459149 https://linux.org/threads/asus-zenbook-14-um425ua-keyboard-not-respond-during-cold-boot.33738/#post-133830 ** Description changed: ASUS UM425UA internal keyboard doesn't work on a "cold boot" (first power-on). It activates only after restart. I noticed it when tried to install Ubuntu 20.04.3. This problem probably appeared with kernel version 5.9 or 5.10 because with Ubuntu 20.04.2 live image (Linux 5.8) keyboard loads fine. I tried to recompile kernel with SERIO_I8042 (link to Arch bug report bellow) set as a module and keyboard works now. In "make config" the changes are: - Device Drivers -> > Generic Driver Options -> [ ] Support for uevent #may slowdown boot, needed only for U14.04 > Input device support > Keyboards -> [M] AT keyboard > Hardware I/O ports -> [M] i8042 PC Keyboard controller It changed such lines in config: CONFIG_KEYBOARD_ATKBD=m CONFIG_SERIO_I8042=m CONFIG_SERIO_LIBPS2=m References: https://bugs.archlinux.org/task/70384 https://ubuntuforums.org/showthread.php?t=2459149
[Kernel-packages] [Bug 1903288] Re: Power guest secure boot with static keys: kernel portion
We are looking at the patches and following the upstream discussions. Once the upstream discussions have settled out, we can build a test 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/1903288 Title: Power guest secure boot with static keys: kernel portion Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Incomplete Bug description: == Comment: #2 - Daniel John Axtens - 2020-11-05 20:15:10 == This is the kernel side of changes needed for LPAR/guest secure boot. Because Ubuntu keeps its kernels so wonderfully up to date, I don't think there are any extra patches you need to pick up. (I'll double- check against the 21.04 tree once my git pulls finish!) However, we potentially need some configuration changes to make sure kexec-ing into a crashdump kernel still works. Because Lockdown requires that kexec kernels are signed by a key trusted by IMA, the public key for used for signing the kdump kernel needs to be in the IMA keyring or the platform keyring. For host secure boot (and in the UEFI case), it's loaded into the platform keyring. But in the case of guest secure boot with static keys, it's not loaded into the platform keyring so it needs to be loaded into the IMA keyring. This is easy enough to do. Firstly, load the Secure Boot CA into the .primary_trusted_keys keyring via the CONFIG_SYSTEM_TRUSTED_KEYS property. We assume the key used to sign the kernel is signed by this CA. Then, enable IMA_LOAD_X509, which allows certificates signed by a key on the .primary_trusted_keys keyring to be loaded into the IMA keyring. Then set IMA_X509_PATH to provide a path to the signing key on installed file system. (It may also be possible to do this step in userspace, so long as the CA is trusted by the kernel.) Then that key will be loaded into the .ima keyring at boot and be used to appraise the kexec kernel for crashdumps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1903288/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928138] Re: Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bisected and workaround attached]
I still believe that this bug is present since initial implementation of DRRS (kernels 4.0 and 4.1). For now I have to disable DRRS by default with a patch. Updated version in attachment. ** Patch added: "Patch for 5.13 and 5.14" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928138/+attachment/5525692/+files/i915---disable_drrs_by_default_5-13.patch -- 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/1928138 Title: Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bisected and workaround attached] Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Since kernel 4.1 laptop HP Elitebook Folio 1040 G1 (with Intel i5-4210U) has a pretty serious issue with flickering Symptoms: 1) If I leave mouse cursor for a few seconds, then start moving it, there's a slight flicker (like display brightness changes a bit). There's also some flickering even without user interactions. 2) On the top left corner sometimes appears artifacts. It's relatively easy to see with black window decorations on top of the screen. This one is showed at the attached video bellow 3) With kernel boot options drm.debug=0x1e log_buf_len=4M dmesg shows constant refresh rate changes (even if it's set to 40HZ) [ 29.977378] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 30.456537] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz [ 33.973392] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 35.055923] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz nomodeset boot option eliminates flickering Turns out Display Refresh Rate Switching (DRRS) feature doesn't work correctly here. It was implemented on kernels 4.0...4.1 but on a particular machine flickering started with 4.1. As a workaround I'm attaching a patch which disables DRRS by default and adds module parameter "enable_drrs" to activate it. It's made for kernel 5.12 and should work for older versions as well (tested with 5.11). Until this issue is resolved, please consider adding parameter to disable DRRS. Windows has such option on Intel® Graphics Command Center. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1928138/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806681]
same problem with new HP ProDesk 405 G6 Desktop Mini PC: renoir ]# dmesg | grep hp_wmi [6.317443] hp_wmi: query 0x4 returned error 0x5 [6.319159] hp_wmi: query 0xd returned error 0x5 [6.323094] hp_wmi: query 0x1b returned error 0x5 kernel 5.14.3-zen1-1-zen -- 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/1806681 Title: hp_wmi: query 0xd returned error 0x5 Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [ 18.296366] hp_wmi: query 0xd returned error 0x5 Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2739 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 4 09:05:38 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806681]
Created attachment 298829 dmesg output -- 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/1806681 Title: hp_wmi: query 0xd returned error 0x5 Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [ 18.296366] hp_wmi: query 0xd returned error 0x5 Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2739 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 4 09:05:38 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931001] Re: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!
I also have this problem. After the automatic update from kernel 5.8 to 5.11 this error occurs. The error only occurs during a cold boot. When rebooting the system, this error does not occur. Here an interesting thread about this problem: https://bbs.minisforum.com/threads/ubuntu-stuck-booting.1830/ ** Attachment added: "logs_and_infos.zip" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1931001/+attachment/5525689/+files/logs_and_infos.zip -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1931001 Title: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! Status in linux-hwe-5.11 package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 LTS and Ubuntu 21.04 occasionally boots with very bad performance and very unresponsive to user input on Lenovo laptop Lenovo 300e 2nd Gen 81M9 (LENOVO_MT_81M9_BU_idea_FM_300e 2nd G). When this happens you can read this kind of messages on journal: --- root@alumne-1-58:~# journalctl | grep "BUG: soft" may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 22 09:33:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [prometheus-node:4220] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [swapper/1:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:02:15 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 21s! [swapper/0:0] jun 05 08:22:58 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [swapper/2:0] jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [lxd:3975] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [swapper/2:0] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [irq/138-iwlwifi:1044] jun 05 08:27:38 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [irq/138-iwlwifi:1044] jun 05 08:28:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:29:46 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] root@alumne-1-58:~# --- Usually if you reboot everything works fine but it's very annoying when happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1931001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931001] Re: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!
** Package changed: linux (Ubuntu) => linux-hwe-5.11 (Ubuntu) ** Changed in: linux-hwe-5.11 (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1931001 Title: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! Status in linux-hwe-5.11 package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 LTS and Ubuntu 21.04 occasionally boots with very bad performance and very unresponsive to user input on Lenovo laptop Lenovo 300e 2nd Gen 81M9 (LENOVO_MT_81M9_BU_idea_FM_300e 2nd G). When this happens you can read this kind of messages on journal: --- root@alumne-1-58:~# journalctl | grep "BUG: soft" may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 22 09:33:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [prometheus-node:4220] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [swapper/1:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:02:15 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 21s! [swapper/0:0] jun 05 08:22:58 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [swapper/2:0] jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [lxd:3975] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [swapper/2:0] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [irq/138-iwlwifi:1044] jun 05 08:27:38 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [irq/138-iwlwifi:1044] jun 05 08:28:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:29:46 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] root@alumne-1-58:~# --- Usually if you reboot everything works fine but it's very annoying when happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1931001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943782] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1943782/+attachment/5525680/+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/1943782 Title: Ubuntu does not boot on kernel 5.14.4 Status in linux package in Ubuntu: Confirmed Bug description: I built linux 5.14.4 from kernel.org on my Dell XPS 7590, but Ubuntu 21.04 fails to load if I boot into it, getting stuck on "Loading initial ramdisk" even when using verbose mode and recovery mode. It never moves past this point and I end up having to hard reboot the laptop into a stable kernel. I made them into a package for easy installation/uninstallation. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ian5081 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-22 (56 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 15 7590 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=7cce21e7-6064-4d17-9431-1c4fd9ccea0e ro mem_sleep_default=deep dis_ucode_ldr ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.197.3 Tags: hirsute Uname: Linux 5.11.0-34-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: 07/22/2021 dmi.bios.release: 1.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd07/22/2021:br1.13:svnDellInc.:pnXPS157590:pvr:sku0905:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943782] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1943782/+attachment/5525682/+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/1943782 Title: Ubuntu does not boot on kernel 5.14.4 Status in linux package in Ubuntu: Confirmed Bug description: I built linux 5.14.4 from kernel.org on my Dell XPS 7590, but Ubuntu 21.04 fails to load if I boot into it, getting stuck on "Loading initial ramdisk" even when using verbose mode and recovery mode. It never moves past this point and I end up having to hard reboot the laptop into a stable kernel. I made them into a package for easy installation/uninstallation. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ian5081 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-22 (56 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 15 7590 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=7cce21e7-6064-4d17-9431-1c4fd9ccea0e ro mem_sleep_default=deep dis_ucode_ldr ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.197.3 Tags: hirsute Uname: Linux 5.11.0-34-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: 07/22/2021 dmi.bios.release: 1.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd07/22/2021:br1.13:svnDellInc.:pnXPS157590:pvr:sku0905:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943030] Re: Enable riscv64 build of nvidia-settings
I may be wrong here but I'd see things differently: when the binaries get available, we won't be notified and people will start trying to install it and it will fail since we decided not to make it available. A few people will take the time to file a bug report, others will get disappointed: this seems like a bad user experience to me whereas it does not cost that much to enable. But I'm quite new to this, so feel free to explain where I'm wrong :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1943030 Title: Enable riscv64 build of nvidia-settings Status in nvidia-settings package in Ubuntu: Incomplete Bug description: Please enable the build on riscv64 architecture of nvidia-settings since it works fine using the attached debdiff: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+build/22050736 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1943030/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943782] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1943782/+attachment/5525685/+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/1943782 Title: Ubuntu does not boot on kernel 5.14.4 Status in linux package in Ubuntu: Confirmed Bug description: I built linux 5.14.4 from kernel.org on my Dell XPS 7590, but Ubuntu 21.04 fails to load if I boot into it, getting stuck on "Loading initial ramdisk" even when using verbose mode and recovery mode. It never moves past this point and I end up having to hard reboot the laptop into a stable kernel. I made them into a package for easy installation/uninstallation. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ian5081 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-22 (56 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 15 7590 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=7cce21e7-6064-4d17-9431-1c4fd9ccea0e ro mem_sleep_default=deep dis_ucode_ldr ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.197.3 Tags: hirsute Uname: Linux 5.11.0-34-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: 07/22/2021 dmi.bios.release: 1.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd07/22/2021:br1.13:svnDellInc.:pnXPS157590:pvr:sku0905:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943782] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1943782/+attachment/5525686/+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/1943782 Title: Ubuntu does not boot on kernel 5.14.4 Status in linux package in Ubuntu: Confirmed Bug description: I built linux 5.14.4 from kernel.org on my Dell XPS 7590, but Ubuntu 21.04 fails to load if I boot into it, getting stuck on "Loading initial ramdisk" even when using verbose mode and recovery mode. It never moves past this point and I end up having to hard reboot the laptop into a stable kernel. I made them into a package for easy installation/uninstallation. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ian5081 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-22 (56 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 15 7590 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=7cce21e7-6064-4d17-9431-1c4fd9ccea0e ro mem_sleep_default=deep dis_ucode_ldr ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.197.3 Tags: hirsute Uname: Linux 5.11.0-34-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: 07/22/2021 dmi.bios.release: 1.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd07/22/2021:br1.13:svnDellInc.:pnXPS157590:pvr:sku0905:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943782] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1943782/+attachment/5525688/+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/1943782 Title: Ubuntu does not boot on kernel 5.14.4 Status in linux package in Ubuntu: Confirmed Bug description: I built linux 5.14.4 from kernel.org on my Dell XPS 7590, but Ubuntu 21.04 fails to load if I boot into it, getting stuck on "Loading initial ramdisk" even when using verbose mode and recovery mode. It never moves past this point and I end up having to hard reboot the laptop into a stable kernel. I made them into a package for easy installation/uninstallation. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ian5081 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-22 (56 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 15 7590 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=7cce21e7-6064-4d17-9431-1c4fd9ccea0e ro mem_sleep_default=deep dis_ucode_ldr ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.197.3 Tags: hirsute Uname: Linux 5.11.0-34-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: 07/22/2021 dmi.bios.release: 1.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd07/22/2021:br1.13:svnDellInc.:pnXPS157590:pvr:sku0905:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943782] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1943782/+attachment/5525679/+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/1943782 Title: Ubuntu does not boot on kernel 5.14.4 Status in linux package in Ubuntu: Confirmed Bug description: I built linux 5.14.4 from kernel.org on my Dell XPS 7590, but Ubuntu 21.04 fails to load if I boot into it, getting stuck on "Loading initial ramdisk" even when using verbose mode and recovery mode. It never moves past this point and I end up having to hard reboot the laptop into a stable kernel. I made them into a package for easy installation/uninstallation. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ian5081 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-22 (56 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 15 7590 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=7cce21e7-6064-4d17-9431-1c4fd9ccea0e ro mem_sleep_default=deep dis_ucode_ldr ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.197.3 Tags: hirsute Uname: Linux 5.11.0-34-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: 07/22/2021 dmi.bios.release: 1.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd07/22/2021:br1.13:svnDellInc.:pnXPS157590:pvr:sku0905:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943782] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1943782/+attachment/5525687/+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/1943782 Title: Ubuntu does not boot on kernel 5.14.4 Status in linux package in Ubuntu: Confirmed Bug description: I built linux 5.14.4 from kernel.org on my Dell XPS 7590, but Ubuntu 21.04 fails to load if I boot into it, getting stuck on "Loading initial ramdisk" even when using verbose mode and recovery mode. It never moves past this point and I end up having to hard reboot the laptop into a stable kernel. I made them into a package for easy installation/uninstallation. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ian5081 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-22 (56 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 15 7590 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=7cce21e7-6064-4d17-9431-1c4fd9ccea0e ro mem_sleep_default=deep dis_ucode_ldr ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.197.3 Tags: hirsute Uname: Linux 5.11.0-34-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: 07/22/2021 dmi.bios.release: 1.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd07/22/2021:br1.13:svnDellInc.:pnXPS157590:pvr:sku0905:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
