[Kernel-packages] [Bug 1932029] Re: Support builtin revoked certificates
** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.10 (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1932029 Title: Support builtin revoked certificates Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Xenial: New Status in linux-oem-5.10 source package in Xenial: Invalid Status in linux source package in Bionic: New Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] Upstream linux kernel now supports configuring built-in revoked certificates for the .blacklist keyring. Add support in our kernel configuration to have built-in revoked certificates. Revoke UEFI amd64 & arm64 2012 signing certificate. Under UEFI Secureboot with lockdown, shim may attempt to communicate revoked certificates to the kernel and depending on how good EFI firmware is, this may or may not succeed. By having these built-in, it will be prohibited to kexec file_load older kernels that were signed with now revoked certificates, however one boots. [Test Plan] * Boot kernel directly, or just with grub, and without shim * Check that $ sudo keyctl list %:.blacklist Contains assymetric 2012 key. [Where problems could occur] * Derivative and per-arch kernels may need to revoke different keys, thus this should be evaluated on per arch & flavour basis as to which keys to revoke. [Other Info] * In theory, this only needs to be revoked on amd64 and arm64, but empty revocation list is not allowed by the kernel configury, thus at the moment revoking 2012 UEFI cert for all architectures. * an ubuntu kernel team regression test is being added to assert that expected revoked certificates have been revoked see https://lists.ubuntu.com/archives/kernel-team/2021-August/122986.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928679] Re: Support importing mokx keys into revocation list from the mok table
** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.10 (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1928679 Title: Support importing mokx keys into revocation list from the mok table Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Xenial: New Status in linux-oem-5.10 source package in Xenial: Invalid Status in linux source package in Bionic: New Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] * Ubuntu's 15.4 based shim ships a very large vendor-dbx (aka mokx) which revokes many Ubuntu kernel hashes and 2012 signing key. * Kernel should import those into it's %:.blacklist keyring such that it prohibits signed kexec of the revoked kernels. * v5.13-rc1 kernel has learned how to import mokx and how to import full certs into the %:.blacklist keyring. * However, it only does so by reading MokListXRT efi variable. * Due to the large size of Ubuntu's vendor-dbx, shim does not create MokListXRT efi variable, but instead creates MokListXRT1 MokListXRT2 MokListXRT3 which currently v5.13-rc1 kernel cannot read. Shim also exposes MokListXRT via mokvar table, which is easier to parse and contains all the revocations in full. Kernel needs a patch to read MokListXRT via mokvar table. * We have two options on how to proceed from here, either we include the same hashes and certs as our vendordbx in in the kernel as revocation list, or we fix kernel to read MokListXRT via mokvar table * The above is known as CVE-2020-26541 * Separately it would be nice to add informational dmesg messages when revoking signing certificates, as a good indication that signing key rotation events have happened and have been applied correctly. [Test Plan] * Boot kernel with 15.4 based Ubuntu shim * Install keyutils package * Execute $ sudo keyctl list %:.blacklist it should list in exccess of 300+ hash entries. It also must list assymetric Canonical signing key from 2012. * Separately check dmesg to observe that asymmetric canonical signing key from 2012 is revoked. [Where problems could occur] * EFI variable storage can be full thus preventing shim to mirror efivars and the moktable. On decent hardware this should not happen, but has been observed to be corrupted on some older EDKII based OVMF instances with small EFI variable storage space (pre-4MB). [Other Info] * The patches to fix the above have been submitted upstream https://lore.kernel.org/keyrings/20210512153100.285169-1-dimitri.led...@canonical.com/ https://lore.kernel.org/keyrings/20210512110302.262104-1-dimitri.led...@canonical.com/ This will now be submitted as SAUCE patches for the Ubuntu UNSTABLE kernel, until accepted upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941829] Re: ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page()
** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1941829 Title: ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page() Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.13 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] The memory-hotplug test has been intermittently timing out (or trashing the test VM, see below) on Impish/Hirsute ppc64el and x86-64 for quite some time now. While the offline memory test obey ratio limit, the same test with error injection does not and tries to offline all the hotpluggable memory, spamming system logs with hundreds of thousands of dump_page() entries, slowing system down (to the point the test itself timesout and gets terminated) and excessive fs occupation: ... [ 9784.393354] page:c00c007d1b40 refcount:3 mapcount:0 mapping:c001fc03e950 index:0xe7b [ 9784.393355] def_blk_aops [ 9784.393356] flags: 0x382062(referenced|active|workingset|private) [ 9784.393358] raw: 00382062 c001b9343a68 c001b9343a68 c001fc03e950 [ 9784.393359] raw: 0e7b c6607b18 0003 c490d000 [ 9784.393359] page dumped because: migration failure [ 9784.393360] page->mem_cgroup:c490d000 [ 9784.393416] migrating pfn 1f46d failed ret:1 ... $ grep "page dumped because: migration failure" /var/log/kern.log | wc -l 2405558 $ ls -la /var/log/kern.log -rw-r- 1 syslog adm 2256109539 Jun 30 14:19 /var/log/kern.log [Fix] * 0c0f6299ba71fa selftests: memory-hotplug: avoid spamming logs with dump_page(), ratio limit hot-remove error test [Test Plan] Run the memory-hotplug test, this log spamming issue should not happen again. [Where problems could occur] If this fix is incorrect we might be unable to catch some other issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1941829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892213] Re: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy/hirsute/impish
** Changed in: linux-oem-5.10 (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1892213
Title:
psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with
focal/groovy/hirsute/impish
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Focal:
In Progress
Status in linux-oem-5.10 source package in Focal:
Fix Committed
Status in linux-oem-5.13 source package in Focal:
In Progress
Status in linux-oem-5.14 source package in Focal:
In Progress
Status in linux source package in Groovy:
Won't Fix
Status in linux source package in Hirsute:
In Progress
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux-oem-5.14 source package in Hirsute:
Invalid
Bug description:
[Impact]
The expected to fail 'raw gso min size - 1' test in psock_snd.sh is
not failing as expected, and thus this test will fail with:
raw gso min size - 1 (expected to fail)
tx: 1524
rx: 1472
OK
This is because after commit 7c6d2ec ("net: be more gentle about silly
gso requests coming from user"), we relaxed the min gso_size check in
virtio_net_hdr_to_skb().
So when a packet which is smaller then the gso_size, GSO for this
packet will not be set, the packet will be send/recv successfully.
[Fix]
* cfba3fb68960b4 selftests/net: remove min gso test in packet_snd
This patch can be cherry-picked into all affected kernels.
I decided to skip those 5.8 variants, as the current cycle
(2021-09-06) might be the last cycle for them.
[Test]
Run this psock_snd.sh script, this test will no longer exist and the
script can proceed with the next test.
[Where problems could occur]
Removing this broken test should not have any negative impact to our
tests. We will need to update our hints later.
[Original Bug Report]
Testing failed on focal/linux 5.4.0-44.48:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20200812_171444_31971@/log.gz
arm64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/l/linux/20200812_210509_145fd@/log.gz
ppc64el:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/l/linux/20200812_165855_1dabd@/log.gz
s390x:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200812_153600_9c7cb@/log.gz
psock_snd.sh output:
16:28:30 DEBUG| [stdout] # selftests: net: psock_snd.sh
16:28:31 DEBUG| [stdout] # dgram
16:28:31 DEBUG| [stdout] # tx: 128
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # dgram bind
16:28:31 DEBUG| [stdout] # tx: 128
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw
16:28:31 DEBUG| [stdout] # tx: 142
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw bind
16:28:31 DEBUG| [stdout] # tx: 142
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw qdisc bypass
16:28:31 DEBUG| [stdout] # tx: 142
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw vlan
16:28:31 DEBUG| [stdout] # tx: 146
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw vnet hdr
16:28:31 DEBUG| [stdout] # tx: 152
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw csum_off
16:28:31 DEBUG| [stdout] # tx: 152
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw csum_off with bad offset (fails)
16:28:31 DEBUG| [stdout] # ./psock_snd: write: Invalid argument
16:28:31 DEBUG| [stdout] # raw min size
16:28:31 DEBUG| [stdout] # tx: 42
16:28:31 DEBUG| [stdout] # rx: 0
[Kernel-packages] [Bug 1941696] Re: Fix Intel AC9560 BT function cannot turn on if BT turn off before S3 entry
** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1941696 Title: Fix Intel AC9560 BT function cannot turn on if BT turn off before S3 entry Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] 1. On Troy JSL platform, add AC9560 2. Enter Settings -> Bluetooth menu 3. Default Bluetooth option is ON, try to toggle the BT option to OFF 4. Into suspend mode(S3) and resume the system 5. Enter BT settings and try to turn on BT, 6. BT function cannot enabled until reboot. [Fix] Turn off the msft ext only for AC9560. Maintainer thought Intel should take care this and reject this workaround. https://marc.info/?l=linux-bluetooth=162938546804458=2 Intel is working on this issue and sru the workaround for the schedule. [Test] Verified with the bellow steps 10 times. 1. On Troy JSL and add AC9560 2. Turn off BT 3. suspend the machine 10 times. 4. turn on BT and works well. [Regression Potential] Medium, it's a workaround to turn off the MSFT ext only for ac9560. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1941696/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930754] Re: e1000e extremly slow
** Tags added: originate-from-1942834 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1930754 Title: e1000e extremly slow Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in linux-oem-5.10 package in Ubuntu: Confirmed Bug description: We have dell latitude 5420 & 5520 laptops with onboard intel ethernet controller. Problem is that the ethernet port is extremely slow. about 100kbyte/s download throughput while on a gigabit connection. Upload seems to work just fine. Also when I pxe boot the system it's also painfully slow. But here comes the funny part. When I attach a usb memory stick the throughput of the networkcontroller is as expected. I've used latest ubuntu 20.04.2 kernel 5.8.0-55 I've used latest ubuntu 20.04.2 kernel 5.10.0-1029-oem Turns out this problem is not showing up when I manually install the 5.8.18 kernel. Also when I create my own iso with the help of Cubic and install the 5.8.18 kernel in it the pxe boot is working as expected with high throughput system: Dell latitude 5420 + 5520 nic: Ethernet Connection (13) I219-LM ubuntu 20.04.2 module: e1000e Please assist. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1930754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-aws/5.4.0.1057.60)
All autopkgtests for the newly accepted linux-meta-aws (5.4.0.1057.60) for focal have finished running. The following regressions have been reported in tests triggered by the package: backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (amd64, arm64) 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/focal/update_excuses.html#linux-meta-aws [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 1925246] Re: binderfs support is not enabled
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1925246 Title: binderfs support is not enabled Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure-5.8 package in Ubuntu: Invalid Status in linux-azure source package in Focal: Fix Committed Status in linux-azure-5.8 source package in Focal: Fix Committed Status in linux-azure source package in Hirsute: Fix Committed Status in linux-azure-5.8 source package in Hirsute: Invalid Status in linux-azure source package in Impish: Fix Committed Status in linux-azure-5.8 source package in Impish: Invalid Bug description: [Impact] Hey, in https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1914568 we got binder support enabled but the configuration is completely different from what we have in our other cloud and generic kernels: ubuntu@machine-1:~$ cat /boot/config-5.4.0-1046-azure | grep BINDER CONFIG_ANDROID_BINDER_IPC=m # CONFIG_ANDROID_BINDERFS is not set CONFIG_ANDROID_BINDER_DEVICES="binder,hwbinder,vndbinder" # CONFIG_ANDROID_BINDER_IPC_SELFTEST is not set $ cat /boot/config-5.4.0-14-generic | grep BINDER CONFIG_ANDROID_BINDER_IPC=m CONFIG_ANDROID_BINDERFS=m CONFIG_ANDROID_BINDER_DEVICES="" # CONFIG_ANDROID_BINDER_IPC_SELFTEST is not set Not having binderfs support is breaking Anbox Cloud support. What is the reason for not having the config aligned between the kernels here? Thanks! [Test Plan] After installing the extra modules package, binderfs should be available via mount. [Where problems could occur] It could cause issues to any existing users of the existing binder_linux module. However this module is currently shipped as extra and should not affect regular users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1925246/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898912] Re: ath3k: probe of 2-1.3:1.0 failed with error -110
** Tags removed: impish ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1898912 Title: ath3k: probe of 2-1.3:1.0 failed with error -110 Status in linux package in Ubuntu: Fix Released Bug description: Bluetooth AR3011 doesn't work in 20.10 but works in 20.04 dmesg.log [ 10.300282] Bluetooth: Can't change to loading configuration err [ 10.300332] ath3k: probe of 2-1.3:1.0 failed with error -110 [ 10.300424] usbcore: registered new interface driver ath3k lsusb | grep Blue 0cf3:3002 Qualcomm Atheros Communications AR3011 Bluetooth blueman-manager error: No adapter(s) found ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-20-generic 5.8.0-20.21 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: navycat1983 F pulseaudio /dev/snd/controlC0: navycat1983 F pulseaudio /dev/snd/controlC1: navycat1983 F pulseaudio CasperMD5CheckResult: skip Date: Wed Oct 7 20:08:25 2020 InstallationDate: Installed on 2020-10-07 (0 days ago) InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME ProcEnviron: LANGUAGE=ru TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic root=UUID=98343bbf-e244-4e6d-889d-fa14ff0254ed ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-20-generic N/A linux-backports-modules-5.8.0-20-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 150-SE-E789 dmi.board.vendor: EVGA dmi.board.version: Patsburg dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg: dmi.product.family: X86 AT dmi.product.name: MODEL_NAME dmi.product.sku: PROJECT_SUB_TAG dmi.product.version: BASE_BOARD_VERSION dmi.sys.vendor: BASE_BOARD_MANUFACTURER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937078] Re: Drivers: hv: vmbus: Fix duplicate CPU assignments within a device
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
hirsute' to 'verification-done-hirsute'. If the problem still exists,
change the tag 'verification-needed-hirsute' to 'verification-failed-
hirsute'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-hirsute
--
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/1937078
Title:
Drivers: hv: vmbus: Fix duplicate CPU assignments within a device
Status in linux-azure package in Ubuntu:
Incomplete
Status in linux-azure source package in Focal:
Fix Committed
Status in linux-azure source package in Hirsute:
Fix Committed
Bug description:
SRU Justification
[Impact]
Customers have degraded network performance on Hyper-V/Azure
This is a request to pick up a patch from the upstream, the patch
fixes an issue with Ubuntu as a hyper-v and Azure guest. This patch
need to get picked up for 20.04, 18.04. The link to the upstream patch
follows:
https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv-
fixes=7c9ff3d61b253715dcf968a6307af148c9b2
Description of issue and solution:
The vmbus module uses a rotational algorithm to assign target CPUs to
a device's channels. Depending on the timing of different device's channel
offers, different channels of a device may be assigned to the same CPU.
For example on a VM with 2 CPUs, if NIC A and B's channels are offered
in the following order, NIC A will have both channels on CPU0, and
NIC B will have both channels on CPU1 -- see below. This kind of
assignment causes RSS load that is spreading across different channels
to end up on the same CPU.
Timing of channel offers:
NIC A channel 0
NIC B channel 0
NIC A channel 1
NIC B channel 1
VMBUS ID 14: Class_ID = {f8615163-df3e-46c5-913f-f2d2f965ed0e} - Synthetic
network adapter
Device_ID = {cab064cd-1f31-47d5-a8b4-9d57e320cccd}
Sysfs path: /sys/bus/vmbus/devices/cab064cd-1f31-47d5-a8b4-9d57e320cccd
Rel_ID=14, target_cpu=0
Rel_ID=17, target_cpu=0
VMBUS ID 16: Class_ID = {f8615163-df3e-46c5-913f-f2d2f965ed0e} - Synthetic
network adapter
Device_ID = {244225ca-743e-4020-a17d-d7baa13d6cea}
Sysfs path: /sys/bus/vmbus/devices/244225ca-743e-4020-a17d-d7baa13d6cea
Rel_ID=16, target_cpu=1
Rel_ID=18, target_cpu=1
Update the vmbus CPU assignment algorithm to avoid duplicate CPU
assignments within a device.
The new algorithm iterates num_online_cpus + 1 times.
The existing rotational algorithm to find "next NUMA & CPU" is still here.
But if the resulting CPU is already used by the same device, it will try
the next CPU.
In the last iteration, it assigns the channel to the next available CPU
like the existing algorithm. This is not normally expected, because
during device probe, we limit the number of channels of a device to
be <= number of online CPUs.
[Test Plan]
This could be tough to test as the patch fixes a race condition.
[Where problems could occur]
Network performance issues could persist.
[Other Info]
SF:#00315347
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1937078/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898912] Re: ath3k: probe of 2-1.3:1.0 failed with error -110
Broken again at 21.10 ** Changed in: linux (Ubuntu) Status: Fix Released => Confirmed ** Tags added: impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1898912 Title: ath3k: probe of 2-1.3:1.0 failed with error -110 Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth AR3011 doesn't work in 20.10 but works in 20.04 dmesg.log [ 10.300282] Bluetooth: Can't change to loading configuration err [ 10.300332] ath3k: probe of 2-1.3:1.0 failed with error -110 [ 10.300424] usbcore: registered new interface driver ath3k lsusb | grep Blue 0cf3:3002 Qualcomm Atheros Communications AR3011 Bluetooth blueman-manager error: No adapter(s) found ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-20-generic 5.8.0-20.21 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: navycat1983 F pulseaudio /dev/snd/controlC0: navycat1983 F pulseaudio /dev/snd/controlC1: navycat1983 F pulseaudio CasperMD5CheckResult: skip Date: Wed Oct 7 20:08:25 2020 InstallationDate: Installed on 2020-10-07 (0 days ago) InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME ProcEnviron: LANGUAGE=ru TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic root=UUID=98343bbf-e244-4e6d-889d-fa14ff0254ed ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-20-generic N/A linux-backports-modules-5.8.0-20-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 150-SE-E789 dmi.board.vendor: EVGA dmi.board.version: Patsburg dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg: dmi.product.family: X86 AT dmi.product.name: MODEL_NAME dmi.product.sku: PROJECT_SUB_TAG dmi.product.version: BASE_BOARD_VERSION dmi.sys.vendor: BASE_BOARD_MANUFACTURER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gcp/5.4.0.1053.63)
All autopkgtests for the newly accepted linux-meta-gcp (5.4.0.1053.63) for focal have finished running. The following regressions have been reported in tests triggered by the package: backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (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/focal/update_excuses.html#linux-meta-gcp [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 1938999] Re: External displays not working on Thinkpad T490 with ThinkPad Thunderbolt 3 Dock
Thanks for the fix. I'm not sure to whom the previous message is addressed but I will not be able to test it because I'm will not be at the office until end of September. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938999 Title: External displays not working on Thinkpad T490 with ThinkPad Thunderbolt 3 Dock Status in linux package in Ubuntu: Confirmed Status in linux source package in Hirsute: Fix Committed Bug description: I have two external displays chained via Display port connected to the ThinkPad Thunderbolt 3 Dock. They are working with kernel 5.8.0-63 but not with the new 5.11.0-25 kernel. I could reproduce this behavior several times for both kernels, as follows: I booted up with disconnected dock, logged in, then I connected it, disconnected it, and connected it again. With the 5.11.0-25 kernel the external displays go black; the main screen turns off and on several times. Sometimes the main screen remains working, but UI is lagging. I'm attaching the logs. Two separate boots for each variant are marked 'a'/'b'. SRU Justifications: === [Impact] External displays not working on Thinkpad T490 with ThinkPad Thunderbolt 3 Dock [Fix] Some SKL systems DP output fails when AUX timeout of LTTPR detection. Disable the LTTPR detection until GLK to fix the link training. [Test] Verified on hardware, external DP work fine. Also tested on I+N GPU laptop and a iGPU only laptop, all displays with dock are good. [Where problems could occur] It may break output of external DP. This patch from 5.12-rc5, only Hirsute kernel is SRUed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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])
Hi, Patricia. Can you clarify if you always need to run the hotplug test before reuseport_bpf_cpu in order to reproduce? I wonder what is the state that the hotplug test leaves the system in? How is it being run? The makefile runs it with the -a option, which in the systems I have available would fail to offline the last CPU (which is expected, different behavior from x86, where cpu0 cannot be offlined). Running it without any options would only offline the last CPU and online it again. I tried looking for differences between our kernels and 5.11.22 and the only cpuset changes I noticed were already present in the kernel you have just tested, and they were on paths unrelated to hotplug or BPF, so I am still baffled as to the real differences here. And given the different systems fail differently, it looks like this will require a dump or xmon so we can debug it. Thanks for all the help. I may ask for system access next week in order to help there. 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 Hirsute: New 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 1942784] Re: makedumpfile not properly working on focal with 5.11 kernel
** Changed in: makedumpfile (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1942784 Title: makedumpfile not properly working on focal with 5.11 kernel Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Focal: In Progress Status in makedumpfile source package in Hirsute: In Progress Bug description: [IMPACT] When running Focal with the hwe 5.11 kernel makedumpfile is not working as it should. Instead of compressing the dump makedumpfile falls back to cp. This can create problems on systems with very large RAM and result into exhausting all storage on the host. This can be resolved with upstream commit 54aec3878b3f([PATCH] make use of 'uts_namespace.name' offset in VMCOREINFO). In addition the dmesg. is not created. This can be resolved with the following two commits : - commit c617ec633392([PATCH 1/2] printk: add support for lockless ringbuffer) - commit 44b073b7ec46([PATCH 2/2] printk: use committed/finalized state values) [TEST CASE] For testing a machine running focal with the 5.11 kernel is required. Then trigger a crash. On the console we can see that makedumpfile fails and `falls back to cp`. In /var/crash we can see that no dmesg file is created and instead of the dump file the uncompressed vmcoreinfo is created. [WHERE PROBLEMS COULD OCCUR] The 3 commits pulled into focal make makedumpfile compatible with the 5.11 kernel. Any regression potential would involve the crash dump not being created after a crash in case kdump is configured. [OTHER] Only Focal with 5.11 kernel is affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1942784/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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.
** Changed in: nvidia-settings (Ubuntu)
Importance: Undecided => Medium
--
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:
In Progress
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 1935034] Re: Update mpt3sas Driver to 38.100.00.00 for Ubuntu 21.10 and 20.04
I need an impact statement before I can submit this to the mailing list for approval. SRU Justification: [Impact] [FIXES] [TESTING] [REGRESSION RISK] [Other Info] (optional) Here is an additional reference. https://wiki.ubuntu.com/Kernel/Dev/StablePatchFormat -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1935034 Title: Update mpt3sas Driver to 38.100.00.00 for Ubuntu 21.10 and 20.04 Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: New Status in linux source package in Hirsute: New Status in linux source package in Impish: Confirmed Bug description: This is a feature request to update the mpt3sas driver to latest version in upstream 38.100.00.00 in Ubuntu 21.10 and Ubuntu 20.04. This will allow users to use fixes and enhancements that landed upstream in 5.14. For this reason, Broadcom and Dell have requested to pull these patches to update the mpt3sas driver to the current upstream version. I could see both Ubuntu 21.10 and 20.04 HWE has mpt3sas driver v36.100.00.00, following are the commit ID's to update to 38.100.00.00 8b3c803529 scsi: mpt3sas: Signedness bug in _base_get_diag_triggers() 39718fe7ad scsi: mpt3sas: Fix spelling mistake in Kconfig "compatiblity" -> "compatibility" bfb3f00c06 scsi: mpt3sas: Simplify bool comparison d309ae0732 scsi: mpt3sas: Fix ReplyPostFree pool allocation 664f0dce20 scsi: mpt3sas: Add support for shared host tagset for CPU hotplug 688c1a0a13 scsi: mpt3sas: Additional diagnostic buffer query interface 446b5f3d3f scsi: mpt3sas: Update driver version to 37.100.00.00 8278807abd scsi: core: Add scsi_device_busy() wrapper 020b0f0a31 scsi: core: Replace sdev->device_busy with sbitmap e015e0ded1 scsi: mpt3sas: Fix misspelling of _base_put_smid_default_atomic() 2111ba8781 scsi: mpt3sas: Move a little data from the stack onto the heap cf9e575e62 scsi: mpt3sas: Fix a bunch of potential naming doc-rot 54cb88dc30 scsi: mpt3sas: Fix a couple of misdocumented functions/params 782a1ab33f scsi: mpt3sas: Fix some kernel-doc misnaming issues a50bd64616 scsi: mpt3sas: Do not use GFP_KERNEL in atomic context a1c4d77413 scsi: mpt3sas: Replace unnecessary dynamic allocation with a static one d6adc251dd scsi: mpt3sas: Force PCIe scatterlist allocations to be within same 4 GB region 7dd847dae1 scsi: mpt3sas: Force chain buffer allocations to be within same 4 GB region 970ac2bb70 scsi: mpt3sas: Force sense buffer allocations to be within same 4 GB region 58501fd937 scsi: mpt3sas: Force reply buffer allocations to be within same 4 GB region 2e4e858732 scsi: mpt3sas: Force reply post buffer allocations to be within same 4 GB region c569de899b scsi: mpt3sas: Force reply post array allocations to be within same 4 GB region 37067b9793 scsi: mpt3sas: Update driver version to 37.101.00.00 a8d548b0b3 scsi: mpt3sas: Fix a few kernel-doc issues 3401ecf7fc scsi: mpt3sas: Fix error return code of mpt3sas_base_attach() 206a3afa94 scsi: mpt3sas: Fix a typo 4c51f95696 scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES c0629d70ca scsi: mpt3sas: Fix endianness for ActiveCablePowerRequirement 3c8604691d scsi: mpt3sas: Block PCI config access from userspace during reset 16660db3fc scsi: mpt3sas: Fix out-of-bounds warnings in _ctl_addnl_diag_query 3ad0b1da0d scsi: mpt3sas: Fix two kernel-doc headers 2910a4a9e9 scsi: mpt3sas: Documentation cleanup e2fac6c44a scsi: mpt3sas: Fix deadlock while cancelling the running firmware event 19a622c39a scsi: mpt3sas: Handle firmware faults during first half of IOC init a0815c45c8 scsi: mpt3sas: Handle firmware faults during second half of IOC init f2b1e9c6f8 scsi: core: Introduce scsi_build_sense() 84a84cc6af scsi: mpt3sas: Fix fall-through warnings for Clang cf750be8e6 scsi: mpt3sas: Fix Coverity reported issue d6c2ce435f scsi: mpt3sas: Fix error return value in _scsih_expander_add() Note: We have already posted patch to update driver version to 38.100.00.00 Other patches are already available in upstream . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935034/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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])
Krzysztof, you were on a PowerVM LPAR (P8LPAR05), just let me know if there's anything that need to be tested -- You 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 Hirsute: New 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 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])
Also re-ran on `entei` it is also a POWER8 (8335-GTA) with Hirsute latest kernel (5.11.0-34-generic) hit the same error - second run of `reuseport_bpf_cpu`: ``` [ 232.349547] Oops: Exception in kernel mode, sig: 4 [#1] [ 232.349647] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV ... [ 232.355607] LR [08d19f3b15a8] 0x8d19f3b15a8 [ 232.355855] --- interrupt: c00 [ 232.355869] Instruction dump: [ 232.356114] [ 232.356374] [ 232.356905] ---[ end trace c99c88cea832039b ]--- [ 232.508560] [ 233.508662] Kernel panic - not syncing: Aiee, killing interrupt handler! [ 233.950570] Rebooting in 10 seconds.. ``` -- You 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 Hirsute: New 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 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])
** Attachment added: "lscpu_entei" https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+attachment/5524453/+files/lscpu_entei -- You 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 Hirsute: New 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 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])
Ok I've re-ran the test with latest kernel versions on the same systems: `thiel` (8001-22C) with focal-hwe (5.11.0-34-generic): ``` [ 3255.763649] Oops: Exception in kernel mode, sig: 5 [#1] [ 3255.763723] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV ``` And `gulpin` (8335-GTA) with hirsute (5.11.0-34-generic) 2nd run of `reuseport_bpf_cpu`: ``` [ 760.451968] BUG: Unable to handle kernel instruction fetch (NULL pointer?) [ 760.452035] Faulting instruction address: 0x [ 760.452196] Oops: Kernel access of bad area, sig: 11 [#1] [ 760.452212] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV ``` -- You 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 Hirsute: New 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 1941963] Re: package shim-signed 1.40.7+15.4-0ubuntu9 failed to install/upgrade: kernel segfault. Hard lock
The only available logs are already attached. I have resolved my specific issue by removing the offending package, but the bug that triggered the segfault still remains when reinstalled. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941963 Title: package shim-signed 1.40.7+15.4-0ubuntu9 failed to install/upgrade: kernel segfault. Hard lock Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu-Studio 20.04.3 LTS on MacPro 5,1, dual W3520 From /proc/version: Linux version 5.11.0-27-lowlatency (buildd@lcy01-amd64-019) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #29~20.04.1-Ubuntu SMP PREEMPT Wed Aug 11 17:06:56 UTC 2021 # apt-cache policy shim-signed shim-signed: Installed: 1.40.7+15.4-0ubuntu9 Candidate: 1.40.7+15.4-0ubuntu9 Version table: *** 1.40.7+15.4-0ubuntu9 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.40.3+15+1533136590.3beb971-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages >What you expected to happen Running `apt upgrade` would complete without issue. >What happened instead System hard lock, becomes completely unresponsive both from the local terminal and over established SSH. Eventually memory is exhausted and the machine reboots. Upon restart, running `apt upgrade` returns the error: "E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem." Running `dpkg --configure -a` attempts to complete installation of shim-signed, segfaults, requiring a cold boot. Only a fraction of the errors generated get written to the logs before the crash as the crash prevents a final flush to disk. From a remote machine I tailed several logs and triggered the crash again, then copied the results from the terminal and attached to report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941963/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939071] Re: Dual screen not working
Hi Chris, I have just loaded kernel "Linux 5.11.0-34-generic #36~20.04.1-Ubuntu SMP Fri Aug 27 08:06:32 UTC 2021" through the update manager : Dual screen is now working fine. Status of this bug 1939071 can be changed to "fixed". Thanks for your help Thanks to the team Denis -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939071 Title: Dual screen not working Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Dual screen issue with kernel family 5.11. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: denis 2641 F pulseaudio /dev/snd/controlC2: denis 2641 F pulseaudio /dev/snd/controlC1: denis 2641 F pulseaudio /dev/snd/pcmC1D3p: denis 2641 F...m pulseaudio CasperMD5CheckResult: skip DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2020-07-25 (400 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: lono wireless extensions. enp8s0no wireless extensions. eno1 no wireless extensions. MachineType: Dell Inc. Precision T3600 Package: linux (not installed) ProcEnviron: LANGUAGE=fr_FR TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=be7e25b0-a451-4097-b177-4855317e502b ro quiet splash ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-27-generic N/A linux-backports-modules-5.11.0-27-generic N/A linux-firmware 1.187.16 RfKill: Tags: uma Uname: Linux 5.11.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/07/2013 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: E12 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrE12:bd11/07/2013:br4.6:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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.0/1/5.13.14 fails to boot
It started to happen since rc7 I'm supposing that it is happening because of this: 10/09/21 16:18 CRIS-DELL kernel [3.880089] RIP: 0010:nv_drm_format_array_alloc+0xb3/0xb5 [nvidia_drm] 10/09/21 16:18 CRIS-DELL kernel [3.880094] Code: 16 5b 4c 89 c0 41 5c 5d c3 f3 48 0f bc c0 89 c1 83 f8 22 76 b2 eb e2 4c 89 c7 e8 c8 e6 ff ff 45 31 c0 5b 41 5c 4c 89 c0 5d c3 <0f> 0b 0f 1f 44 00 00 55 48 89 e5 41 56 41 55 41 54 49 89 fc 53 48 10/09/21 16:18 CRIS-DELL kernel [3.880095] RSP: 0018:ae2a00f83a58 EFLAGS: 00010212 10/09/21 16:18 CRIS-DELL kernel [3.880097] RAX: 0020 RBX: 0001efff RCX: 0020 10/09/21 16:18 CRIS-DELL kernel [3.880098] RDX: 32313050 RSI: 0001 RDI: 0012 10/09/21 16:18 CRIS-DELL kernel [3.880099] RBP: ae2a00f83a68 R08: 8fbf0770c580 R09: 8fbf0770c580 10/09/21 16:18 CRIS-DELL kernel [3.880100] R10: 8fbf06e90028 R11: 8fbf1888e808 R12: ae2a00f83a9c 10/09/21 16:18 CRIS-DELL kernel [3.880101] R13: 8fbf0708a000 R14: 8fbf077a6600 R15: 10/09/21 16:18 CRIS-DELL kernel [3.880102] FS: 7f0c3ba20d00() GS:8fc28bc4() knlGS: 10/09/21 16:18 CRIS-DELL kernel [3.880104] CS: 0010 DS: ES: CR0: 80050033 10/09/21 16:18 CRIS-DELL kernel [3.880105] CR2: 563d833a3000 CR3: 000100cb6001 CR4: 003706e0 10/09/21 16:18 CRIS-DELL kernel [3.880106] DR0: DR1: DR2: 10/09/21 16:18 CRIS-DELL kernel [3.880106] DR3: DR6: fffe0ff0 DR7: 0400 10/09/21 16:18 CRIS-DELL kernel [3.880107] Call Trace: 10/09/21 16:18 CRIS-DELL kernel [3.880109] nv_drm_plane_create+0x7d/0x2f0 [nvidia_drm] 10/09/21 16:18 CRIS-DELL kernel [3.880114] nv_drm_enumerate_crtcs_and_planes+0x13f/0x2a0 [nvidia_drm] 10/09/21 16:18 CRIS-DELL kernel [3.880117] nv_drm_load+0x253/0x3b4 [nvidia_drm] 10/09/21 16:18 CRIS-DELL kernel [3.880121] ? __cond_resched+0x1a/0x50 10/09/21 16:18 CRIS-DELL kernel [3.880123] ? nv_drm_master_drop+0x60/0x60 [nvidia_drm] 10/09/21 16:18 CRIS-DELL kernel [3.880127] drm_dev_register+0xd6/0x1c0 [drm] 10/09/21 16:18 CRIS-DELL kernel [3.880142] nv_drm_probe_devices+0x10b/0x1f0 [nvidia_drm] 10/09/21 16:18 CRIS-DELL kernel [3.880145] ? 0xc0b86000 10/09/21 16:18 CRIS-DELL kernel [3.880146] nv_drm_init+0x1e/0x50 [nvidia_drm] 10/09/21 16:18 CRIS-DELL kernel [3.880149] nv_linux_drm_init+0xe/0x1000 [nvidia_drm] 10/09/21 16:18 CRIS-DELL kernel [3.880152] do_one_initcall+0x46/0x1d0 10/09/21 16:18 CRIS-DELL kernel [3.880154] ? kmem_cache_alloc_trace+0x159/0x2c0 10/09/21 16:18 CRIS-DELL kernel [3.880157] do_init_module+0x62/0x290 10/09/21 16:18 CRIS-DELL kernel [3.880159] load_module+0xaa3/0xb30 10/09/21 16:18 CRIS-DELL kernel [3.880162] __do_sys_finit_module+0xbf/0x120 10/09/21 16:18 CRIS-DELL kernel [3.880164] __x64_sys_finit_module+0x18/0x20 10/09/21 16:18 CRIS-DELL kernel [3.880166] do_syscall_64+0x59/0xc0 10/09/21 16:18 CRIS-DELL kernel [3.880168] ? syscall_exit_to_user_mode+0x27/0x50 10/09/21 16:18 CRIS-DELL kernel [3.880170] ? __x64_sys_newfstatat+0x1c/0x20 10/09/21 16:18 CRIS-DELL kernel [3.880171] ? do_syscall_64+0x69/0xc0 10/09/21 16:18 CRIS-DELL kernel [3.880173] ? do_syscall_64+0x69/0xc0 10/09/21 16:18 CRIS-DELL kernel [3.880174] ? do_syscall_64+0x69/0xc0 10/09/21 16:18 CRIS-DELL kernel [3.880175] ? sysvec_call_function+0x4e/0x90 10/09/21 16:18 CRIS-DELL kernel [3.880176] ? asm_sysvec_call_function+0xa/0x20 10/09/21 16:18 CRIS-DELL kernel [3.880178] entry_SYSCALL_64_after_hwframe+0x44/0xae 10/09/21 16:18 CRIS-DELL kernel [3.880180] RIP: 0033:0x7f0c3bfba70d 10/09/21 16:18 CRIS-DELL kernel [3.880181] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d f3 66 0f 00 f7 d8 64 89 01 48 10/09/21 16:18 CRIS-DELL kernel [3.880183] RSP: 002b:7fff8c8cbf48 EFLAGS: 0246 ORIG_RAX: 0139 10/09/21 16:18 CRIS-DELL kernel [3.880184] RAX: ffda RBX: 55c88ef2b280 RCX: 7f0c3bfba70d 10/09/21 16:18 CRIS-DELL kernel [3.880185] RDX: RSI: 55c88ef0ccb0 RDI: 0017 10/09/21 16:18 CRIS-DELL kernel [3.880186] RBP: 0002 R08: R09: 55c88ef0ff60 10/09/21 16:18 CRIS-DELL kernel [
[Kernel-packages] [Bug 1938477] Re: Screen brightness changing randomly with kernel 5.11.0-25
Since the -16 version of the kernel was not available anymore, the bug was back for me. I then downloaded and installed 5.11.1-051101-generic with mainline and the bug is NOT happening with this kernel version. Hope this info helps. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938477 Title: Screen brightness changing randomly with kernel 5.11.0-25 Status in linux package in Ubuntu: Confirmed Bug description: Hello guys! The brightness of the screen on my laptop (Dell 7573 with touch ips 1080 panel) slightly changes randomly when using the laptop builtin display. It feels the same as I changed the brightness one step using the keyboard keys. Here is a video: https://drive.google.com/file/d/1XQLXKLWu2TlOoGP-p8eaUGZR78713ErH/view?usp=sharing I suffer with this problem since a long time ago. I think since ubuntu 19. I tried everything you can imagine, I will make a list of things I've tried. I had gave up trying to fix this already but in a beautiful sunny day suddenly the bug stopped happening. So I decided to report this bug now because this bug does NOT happen with only this version of the kernel: Linux 5.11.0-16-generic. So that can probably e useful to help discovering the bug reason. I am choosing this version on grub every time I reboot so the bug doesn't happen. If I boot on 5.11.0-25 the bug is back. List of things I've tried: - Changing i915 parameters like enable_psr to false and many others. - Upgrading BIOS version. - Installing windows and applying all the patches on dell's website and installing ubuntu again. - Disabling "dynamic backlight control" on BIOS. Some maybe useful info: - I've tried other distros like Fedora and PopOS and the same bug happens. - The bug does not happen when using live ubuntu from usb. - When you fresh install ubuntu (I've tried with 20.04, 20.10 and 21.04) the bug doesn't happen when you have just installed the os but it starts again after the first update. The same applies to the other distro's mentioned above. - When you disable i915 driver with modeset parameter, it does not happen. - The bug does NOT happen only with this kernel version 5.11.0-16-generic, BUT it starts happening again if I lock screen and login again. So I am never locking my screen and holding this kernel version for now. Thanks guys! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 29 20:54:14 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.18, 5.11.0-16-generic, x86_64: installed virtualbox, 6.1.18, 5.11.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:07ec] InstallationDate: Installed on 2021-07-25 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. Inspiron 7573 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=663d1a67-7acb-428f-a6c8-a9a259a5427c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2021 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.1 dmi.board.name: 023FRC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.1:bd05/06/2021:br1.18:svnDellInc.:pnInspiron7573:pvr:rvnDellInc.:rn023FRC:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7573 dmi.product.sku: 07EC dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1903288] Comment bridged from LTC Bugzilla
--- Comment From naynj...@ibm.com 2021-09-10 13:31 EDT--- I have posted the patch today - https://lore.kernel.org/linux-integrity/20210910172515.8430-1-na...@linux.ibm.com/T/#u . It would be very helpful if someone from Canonical can test it and confirm. Thanks & Regards, - Nayna -- You 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 1937897] Re: GPIO error logs in start and dmesg after update of kernel
Added tag 'verification-failed-hirsute'. Enabled proposed and installed package 'linux-image-5.13.0-14-generic' version '5.13.0-14.14~20.04.4' on my 20.04.3 LTS, and still get in dmesg: [1.228729] gpio gpiochip1: (gpio_aaeon): tried to insert a GPIO chip with zero lines [1.228732] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to register, -22 [1.228735] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22 [7.238390] gpio gpiochip1: (gpio_aaeon): tried to insert a GPIO chip with zero lines [7.238396] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to register, -22 [7.238401] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22 ** Tags removed: verification-needed-hirsute ** Tags added: verification-failed-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/1937897 Title: GPIO error logs in start and dmesg after update of kernel Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: In Progress Bug description: [Impact] After upgrade kernel to 5.11.0-25 which introduce some ODM patches from AAEON, user encounters below errors [ 5.852182] gpio gpiochip2: (gpio_aaeon): tried to insert a GPIO chip with zero lines [5.852187] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to register, -22 [5.852194] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22 [Fix] AAEON provides a patch to check the BFPI version before loading the driver. Which fixes the issue introduced by Hirsute: 45a8bb8699cc UBUNTU: ODM: mfd: Add support for IO functions of AAEON devices Impish: 424945128781 UBUNTU: ODM: mfd: Add support for IO functions of AAEON devices [Test] Verified by AAEON. [Where problems could occur] It adds a check while probing the driver, should have no impact to normal user. = After update from kernel 5.11.0-22 to 5.11.0-25 i see next logs error to gpio: 5.852182] gpio gpiochip2: (gpio_aaeon): tried to insert a GPIO chip with zero lines [5.852187] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to register, -22 [5.852194] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22 On pc: description: Desktop Computer product: System Product Name (SKU) vendor: ASUS version: System Version serial: System Serial Number width: 64 bits capabilities: smbios-3.3.0 dmi-3.3.0 smp vsyscall32 configuration: boot=normal chassis=desktop family=To be filled by O.E.M. sku=SKU uuid=0ABCA172-BFA8-2AC5-FC37-3C7C3FD88FE4 *-core description: Motherboard product: TUF GAMING B550M-PLUS (WI-FI) vendor: ASUSTeK COMPUTER INC. physical id: 0 version: Rev X.0x serial: 201176738701636 slot: Default string *-firmware description: BIOS vendor: American Megatrends Inc. physical id: 0 version: 2403 date: 06/16/2021 size: 64KiB capacity: 16MiB capabilities: pci apm upgrade shadowing cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb biosbootspecification uefi *-memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923114] Re: ubuntu_kernel_selftests: ./cpu-on-off-test.sh: line 94: echo: write error: Device or resource busy
While looking for some improvements on cpu-on-off-test.sh, I investigated the path that is taken on azure. One good tool to debug these failures is the cpuhp tracing. echo 1 > /sys/kernel/debug/tracing/events/cpuhp/enable echo 1 > /sys/kernel/debug/tracing/tracing_on cat /sys/kernel/debug/tracing/trace_pipe & echo 0 > /sys/devices/system/cpu/cpu1/online bash-2660[001] 10306.404476: cpuhp_enter: cpu: 0001 target: 143 step: 213 (cpuhp_kick_ap_work) cpuhp/1-14 [001] 10306.404506: cpuhp_enter: cpu: 0001 target: 143 step: 212 (sched_cpu_deactivate) cpuhp/1-14 [001] 10306.420476: cpuhp_exit: cpu: 0001 state: 211 step: 212 ret: 0 cpuhp/1-14 [001] 10306.420502: cpuhp_enter: cpu: 0001 target: 143 step: 189 (msr_device_destroy [msr]) cpuhp/1-14 [001] 10306.420623: cpuhp_exit: cpu: 0001 state: 188 step: 189 ret: 0 cpuhp/1-14 [001] 10306.420629: cpuhp_enter: cpu: 0001 target: 143 step: 187 (mce_cpu_pre_down) cpuhp/1-14 [001] 10306.420653: cpuhp_exit: cpu: 0001 state: 186 step: 187 ret: 0 cpuhp/1-14 [001] 10306.420654: cpuhp_enter: cpu: 0001 target: 143 step: 184 (hv_synic_cleanup) cpuhp/1-14 [001] 10306.420655: cpuhp_exit: cpu: 0001 state: 183 step: 184 ret: -16 cpuhp/1-14 [001] 10306.426523: cpuhp_enter: cpu: 0001 target: 213 step: 185 (compute_batch_value) cpuhp/1-14 [001] 10306.426541: cpuhp_exit: cpu: 0001 state: 185 step: 185 ret: 0 cpuhp/1-14 [001] 10306.426546: cpuhp_enter: cpu: 0001 target: 213 step: 186 (acpi_soft_cpu_online) cpuhp/1-14 [001] 10306.426553: cpuhp_exit: cpu: 0001 state: 186 step: 186 ret: 0 cpuhp/1-14 [001] 10306.426553: cpuhp_enter: cpu: 0001 target: 213 step: 187 (mce_cpu_online) cpuhp/1-14 [001] 10306.426597: cpuhp_exit: cpu: 0001 state: 187 step: 187 ret: 0 cpuhp/1-14 [001] 10306.426606: cpuhp_enter: cpu: 0001 target: 213 step: 188 (console_cpu_notify) cpuhp/1-14 [001] 10306.426607: cpuhp_exit: cpu: 0001 state: 188 step: 188 ret: 0 cpuhp/1-14 [001] 10306.426611: cpuhp_enter: cpu: 0001 target: 213 step: 189 (msr_device_create [msr]) cpuhp/1-14 [001] 10306.426665: cpuhp_exit: cpu: 0001 state: 189 step: 189 ret: 0 cpuhp/1-14 [001] 10306.426667: cpuhp_enter: cpu: 0001 target: 213 step: 212 (sched_cpu_activate) cpuhp/1-14 [001] 10306.426670: cpuhp_exit: cpu: 0001 state: 212 step: 212 ret: 0 Notice the -16 failure on hv_synic_cleanup. It can fail for two reasons: the cpu is VMBUS_CONNECT_CPU, which is 0, not the case here, or the cpu is the target_cpu for a vmbus_channel. # grep 1 /sys/bus/vmbus/devices/*/channels/*/cpu /sys/bus/vmbus/devices/-0001-8899--/channels/3/cpu:1 /sys/bus/vmbus/devices/000d3a6e-002e-000d-3a6e-002e000d3a6e/channels/15/cpu:1 /sys/bus/vmbus/devices/f8b3781b-1e82-4818-a1c3-63d806ec15bb/channels/13/cpu:1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-4.15 in Ubuntu. https://bugs.launchpad.net/bugs/1923114 Title: ubuntu_kernel_selftests: ./cpu-on-off-test.sh: line 94: echo: write error: Device or resource busy Status in ubuntu-kernel-tests: In Progress Status in linux-azure package in Ubuntu: New Status in linux-azure-4.15 package in Ubuntu: New Status in linux-azure source package in Trusty: New Status in linux-azure-4.15 source package in Trusty: New Status in linux-azure source package in Xenial: New Status in linux-azure-4.15 source package in Xenial: New Status in linux-azure source package in Bionic: New Status in linux-azure-4.15 source package in Bionic: New Status in linux-azure source package in Groovy: New Status in linux-azure-4.15 source package in Groovy: New Bug description: Test cpu-hotplug from ubuntu_kernel_selftests failed with bionic:linux-azure-4.15 running on a Basic A2 with 2 cores (besides other instance types): selftests: cpu-on-off-test.sh pid 28041's current affinity mask: 3 pid 28041's new affinity mask: 1 CPU online/offline summary: present_cpus = 0-1 present_max = 1 Cpus in online state: 0-1 Cpus in offline state: 0 Limited scope test: one hotplug cpu (leaves cpu in the original state): online to offline to online: cpu 1 not ok 1..1 selftests: cpu-on-off-test.sh [FAIL] ./cpu-on-off-test.sh: line 94: echo: write error: Device or resource busy offline_cpu_expect_success 1: unexpected fail http://10.246.72.46/4.15.0-1112.124~16.04.1-azure/xenial-linux-azure- azure- amd64-4.15.0-Basic_A2-ubuntu_kernel_selftests/ubuntu_kernel_selftests/results/ubuntu_kernel_selftests.cpu-
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-aws/5.11.0.1018.19)
All autopkgtests for the newly accepted linux-meta-aws (5.11.0.1018.19) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: systemd/247.3-3ubuntu3.4 (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/hirsute/update_excuses.html#linux-meta-aws [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 1933359] Re: [Ubuntu 21.10][Broadcom] mpi3mr driver submission request
** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: 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/1933359 Title: [Ubuntu 21.10][Broadcom] mpi3mr driver submission request Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: Broadcom is coming up with next generation high performance Storage IO and RAID controllers. For details, follow: https://www.spinics.net/lists/linux-scsi/msg147868.html This family of controllers is managed by "mpi3mr" Linux device driver(written from scratch). First patchset of the driver is accepted by Linux upstream. The driver is available in git branch - 5.14/scsi-staging of Linux SCSI tree: https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git The driver will be part of 5.14 mainline Linux kernel release. Here is the list of commit ids: 9fc4abfe5a5f scsi: mpi3mr: Add event handling debug prints 74e1f30a2868 scsi: mpi3mr: Add EEDP DIF DIX support 28cbe2f420d3 scsi: mpi3mr: Add support for DSN secure firmware check 2f9c4d520aa6 scsi: mpi3mr: Add support for PM suspend and resume 44dc724f5eec scsi: mpi3mr: Wait for pending I/O completions upon detection of VD I/O timeout 71e80106d059 scsi: mpi3mr: Print pending host I/Os for debugging f061178e0762 scsi: mpi3mr: Complete support for soft reset 463429f8dd5c scsi: mpi3mr: Add support for threaded ISR 392bbeb85b2a scsi: mpi3mr: Hardware workaround for UNMAP commands to NVMe drives 82141ddba90a scsi: mpi3mr: Allow certain commands during pci-remove hook 0ea177343f1f scsi: mpi3mr: Add change queue depth support e844adb1fbdc scsi: mpi3mr: Implement SCSI error handler hooks 8f9c6173ca46 scsi: mpi3mr: Add bios_param SCSI host template hook ff9561e910fc scsi: mpi3mr: Print IOC info for debugging 54dfcffb4191 scsi: mpi3mr: Add support for timestamp sync with firmware fb9b04574f14 scsi: mpi3mr: Add support for recovering controller e36710dc06e3 scsi: mpi3mr: Additional event handling 8e653455547a scsi: mpi3mr: Add support for PCIe device event handling 13ef29ea4aa0 scsi: mpi3mr: Add support for device add/remove event handling 672ae26c8216 scsi: mpi3mr: Add support for internal watchdog thread 023ab2a9b4ed scsi: mpi3mr: Add support for queue command processing c9566231cfaf scsi: mpi3mr: Create operational request and reply queue pair 824a156633df scsi: mpi3mr: Base driver code c4f7ac64616e scsi: mpi3mr: Add mpi30 Rev-R headers and Kconfig Please include this driver in Ubuntu 21.10 release. Let me know for any questions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933359/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942633] Re: Can not boot impish in Cavium ThunderX
I can attempt a bisect - let me know if someone else is already doing that :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942633 Title: Can not boot impish in Cavium ThunderX Status in linux package in Ubuntu: Confirmed Bug description: Hi I am trying to deploy a Impish server (Ubuntu 5.11.0-13.14-generic 5.11.7) in arm64 description: Computer product: Cavium ThunderX CN88XX board width: 64 bits I tried 2 releases: - 20210817 ( https://images.maas.io/ephemeral-v3/stable/impish/arm64/20210817/ga-21.10/ ) - 20210830 ( https://images.maas.io/ephemeral-v3/candidate/impish/arm64/20210830/ ) 20210817: Ends the deploy successfully but fails to boot from disk: ``` [0.00] Booting Linux on physical CPU 0x00 [0x431f0a11] [0.00] Linux version 5.13.0-14-generic (buildd@bos02-arm64-018) (gcc (Ubuntu 10.3.0-6ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.37) #14-Ubuntu SMP Mon Aug 2 12:40:58 UTC 2021 (Ubuntu 5.13.0-14.14-generic 5.13.1) [0.00] Machine model: Cavium ThunderX CN88XX board [ 139.896752] raid6: xor() 1224 MB/s, rmw enabled [ 139.957046] raid6: using neon recovery algorithm [ 140.020937] xor: measuring software checksum speed [ 140.085571]8regs : 2432 MB/sec [ 140.149834]32regs : 2687 MB/sec [ 140.212202]arm64_neon : 4390 MB/sec [ 140.271985] xor: using function: arm64_neon (4390 MB/sec) [ 140.335013] async_tx: api initialized (async) done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... [ 140.569847] Btrfs loaded, crc32c=crc32c-generic, zoned=yes Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... mdadm: No devices listed in conf file were found. done. mdadm: No devices listed in conf file were found. ``` 20210830 Fails the network boot: ``` [ 140.351066] async_tx: api initialized (async) done. Begin: Running /scripts/init-premount ... cloud-initramfs-dyn-netconf: did no find a nic with 1c:1b:0d:0d:52:7c done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Begin: Waiting up to 180 secs for BOOTIF to become available ... Failure: Interface BOOTIF did not appear in time done. ipconfig: BOOTIF: SIOCGIFINDEX: No such device ipconfig: no devices to configure ``` I will attach full logs of each try. JFYI, this is the same machine as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930903] Re: Frequent kernel oops related to nvidia / nv_drm_master_set
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-restricted-modules (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1930903 Title: Frequent kernel oops related to nvidia / nv_drm_master_set Status in linux-restricted-modules package in Ubuntu: New Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: After upgrading yesterday from ubuntu 20 to 21.04 my machine now exhibits frequent involuntary restarts, related to a kernel oops of the form Jun 3 10:48:32 zotac kernel: [ 20.464926] RIP: 0010:nv_drm_master_set+0x27/0x30 [nvidia_drm] [...] Jun 3 10:48:32 zotac kernel: [ 20.464958] Call Trace: Jun 3 10:48:32 zotac kernel: [ 20.464964] drm_new_set_master+0x7e/0x100 [drm] Jun 3 10:48:32 zotac kernel: [ 20.464994] drm_master_open+0x6e/0xa0 [drm] Jun 3 10:48:32 zotac kernel: [ 20.465017] drm_open+0xf8/0x250 [drm] Jun 3 10:48:32 zotac kernel: [ 20.465044] drm_stub_open+0xba/0x140 [drm] Jun 3 10:48:32 zotac kernel: [ 20.465070] chrdev_open+0xf7/0x220 Jun 3 10:48:32 zotac kernel: [ 20.465075] ? cdev_device_add+0x90/0x90 Jun 3 10:48:32 zotac kernel: [ 20.465078] do_dentry_open+0x156/0x370 Jun 3 10:48:32 zotac kernel: [ 20.465081] vfs_open+0x2d/0x30 Jun 3 10:48:32 zotac kernel: [ 20.465084] do_open+0x1c3/0x340 Jun 3 10:48:32 zotac kernel: [ 20.465087] path_openat+0x10a/0x1d0 Jun 3 10:48:32 zotac kernel: [ 20.465090] do_filp_open+0x8c/0x130 Jun 3 10:48:32 zotac kernel: [ 20.465093] ? __check_object_size+0x1c/0x20 Jun 3 10:48:32 zotac kernel: [ 20.465096] do_sys_openat2+0x9b/0x150 Jun 3 10:48:32 zotac kernel: [ 20.465099] __x64_sys_openat+0x56/0x90 Jun 3 10:48:32 zotac kernel: [ 20.465102] do_syscall_64+0x38/0x90 Jun 3 10:48:32 zotac kernel: [ 20.465105] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 3 10:48:32 zotac kernel: [ 20.465108] RIP: 0033:0x7fe6ea270954 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..0a.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 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1) ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Jun 4 17:00:45 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.11.0-18-generic, x86_64: installed nvidia, 460.80, 5.8.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] [19da:2438] InstallationDate: Installed on 2020-05-09 (391 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: NA ZBOX-ER51070 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=4e73512b-1846-4fe4-87d1-079bbaae2a1a ro quiet splash crashkernel=512M-:192M vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Default string dmi.board.name: ZBOX-ER51070 dmi.board.vendor: NA dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd04/25/2019:br5.12:svnNA:pnZBOX-ER51070:pvrDefaultstring:rvnNA:rnZBOX-ER51070:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZBOX-ER51070 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: NA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 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
[Kernel-packages] [Bug 1930903] Re: Frequent kernel oops related to nvidia / nv_drm_master_set
This bug affects the signed and ubuntu packaged versions distributed via the linux-modules-nvidia-460-generic and it's dependencies ** Package changed: nvidia-graphics-drivers-470 (Ubuntu) => linux- restricted-modules (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1930903 Title: Frequent kernel oops related to nvidia / nv_drm_master_set Status in linux-restricted-modules package in Ubuntu: New Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: After upgrading yesterday from ubuntu 20 to 21.04 my machine now exhibits frequent involuntary restarts, related to a kernel oops of the form Jun 3 10:48:32 zotac kernel: [ 20.464926] RIP: 0010:nv_drm_master_set+0x27/0x30 [nvidia_drm] [...] Jun 3 10:48:32 zotac kernel: [ 20.464958] Call Trace: Jun 3 10:48:32 zotac kernel: [ 20.464964] drm_new_set_master+0x7e/0x100 [drm] Jun 3 10:48:32 zotac kernel: [ 20.464994] drm_master_open+0x6e/0xa0 [drm] Jun 3 10:48:32 zotac kernel: [ 20.465017] drm_open+0xf8/0x250 [drm] Jun 3 10:48:32 zotac kernel: [ 20.465044] drm_stub_open+0xba/0x140 [drm] Jun 3 10:48:32 zotac kernel: [ 20.465070] chrdev_open+0xf7/0x220 Jun 3 10:48:32 zotac kernel: [ 20.465075] ? cdev_device_add+0x90/0x90 Jun 3 10:48:32 zotac kernel: [ 20.465078] do_dentry_open+0x156/0x370 Jun 3 10:48:32 zotac kernel: [ 20.465081] vfs_open+0x2d/0x30 Jun 3 10:48:32 zotac kernel: [ 20.465084] do_open+0x1c3/0x340 Jun 3 10:48:32 zotac kernel: [ 20.465087] path_openat+0x10a/0x1d0 Jun 3 10:48:32 zotac kernel: [ 20.465090] do_filp_open+0x8c/0x130 Jun 3 10:48:32 zotac kernel: [ 20.465093] ? __check_object_size+0x1c/0x20 Jun 3 10:48:32 zotac kernel: [ 20.465096] do_sys_openat2+0x9b/0x150 Jun 3 10:48:32 zotac kernel: [ 20.465099] __x64_sys_openat+0x56/0x90 Jun 3 10:48:32 zotac kernel: [ 20.465102] do_syscall_64+0x38/0x90 Jun 3 10:48:32 zotac kernel: [ 20.465105] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 3 10:48:32 zotac kernel: [ 20.465108] RIP: 0033:0x7fe6ea270954 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..0a.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 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1) ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Jun 4 17:00:45 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.11.0-18-generic, x86_64: installed nvidia, 460.80, 5.8.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] [19da:2438] InstallationDate: Installed on 2020-05-09 (391 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: NA ZBOX-ER51070 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=4e73512b-1846-4fe4-87d1-079bbaae2a1a ro quiet splash crashkernel=512M-:192M vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Default string dmi.board.name: ZBOX-ER51070 dmi.board.vendor: NA dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd04/25/2019:br5.12:svnNA:pnZBOX-ER51070:pvrDefaultstring:rvnNA:rnZBOX-ER51070:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZBOX-ER51070 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: NA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers:
[Kernel-packages] [Bug 1930903] Re: Frequent kernel oops related to nvidia / nv_drm_master_set
I am seeing the same bug on the nvidia-470 drivers specifically the linux-module-nvidia-470-generic Ubuntu packaged pre-built modules. I do not have dkms installed. These messages do not occur periodically but do seem to occur multiple times in quick succession after un-blanking and unlocking the laptop after the screen-saver has blanked the displays. I have a 2nd screen plugged in via DisplayPort. The machine is pugged into mains power and has not suspended or hibernated, between the screen locking and being unlocked a few hours later. [ cut here ] Sep 10 22:07:08 tim-ThinkPad-P17 kernel: WARNING: CPU: 10 PID: 195514 at build/nvidia/460.91.03/build/nvidia-drm/nvidia-drm-drv.c:530 nv_drm_master_set+0x27/0x30 [nvidia_drm] Sep 10 22:07:08 tim-ThinkPad-P17 kernel: Modules linked in: exfat mmc_block hid_logitech_hidpp uhid rfcomm xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype nft_compat br_netfilter ccm nft_counter nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct bridge stp llc nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 overlay ip_set nf_tables nfnetlink cmac algif_hash algif_skcipher af_alg bnep binfmt_misc nls_iso8859_1 nvidia_uvm(PO) nvidia_drm(PO) nvidia_modeset(PO) snd_sof_pci snd_sof_intel_hda_common snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi nvidia(PO) x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi kvm_intel snd_hda_codec_realtek mei_hdcp snd_hda_codec_generic intel_rapl_msr kvm iwlmvm snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation soundwire_cadence Sep 10 22:07:08 tim-ThinkPad-P17 kernel: crct10dif_pclmul snd_hda_codec ghash_clmulni_intel mac80211 aesni_intel snd_hda_core crypto_simd cryptd glue_helper soundwire_bus rapl btusb btrtl btbcm libarc4 snd_usb_audio uvcvideo snd_soc_core thinkpad_acpi intel_cstate btintel videobuf2_vmalloc processor_thermal_device snd_usbmidi_lib iwlwifi snd_hwdep bluetooth cdc_ether videobuf2_memops processor_thermal_rfim videobuf2_v4l2 usbnet processor_thermal_mbox efi_pstore intel_wmi_thunderbolt wmi_bmof snd_compress videobuf2_common nvram ac97_bus snd_seq_midi ledtrig_audio ee1004 r8152 snd_seq_midi_event videodev snd_rawmidi snd_pcm_dmaengine mii joydev input_leds ucsi_acpi processor_thermal_rapl mei_me intel_rapl_common mc typec_ucsi ecdh_generic cfg80211 snd_pcm ecc mei intel_soc_dts_iosf intel_pch_thermal serio_raw typec snd_seq snd_seq_device snd_timer snd soundcore int3403_thermal int340x_thermal_zone int3400_thermal mac_hid acpi_thermal_rel acpi_pad sch_fq_codel msr parport_pc ppdev lp parport ip_tables x_tables Sep 10 22:07:08 tim-ThinkPad-P17 kernel: autofs4 zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) btrfs blake2b_generic xor hid_generic usbhid hid raid6_pq libcrc32c dm_mirror dm_region_hash dm_log i915 rtsx_pci_sdmmc i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core crc32_pclmul e1000e psmouse drm i2c_i801 i2c_smbus intel_lpss_pci thunderbolt nvme rtsx_pci intel_lpss xhci_pci idma64 nvme_core xhci_pci_renesas virt_dma wmi pinctrl_cannonlake video Sep 10 22:07:08 tim-ThinkPad-P17 kernel: CPU: 10 PID: 195514 Comm: gpu-manager Tainted: PW O 5.11.0-34-generic #36-Ubuntu Sep 10 22:07:08 tim-ThinkPad-P17 kernel: Hardware name: LENOVO 20SNCTO1WW/20SNCTO1WW, BIOS N30ET40W (1.23 ) 08/03/2021 Sep 10 22:07:08 tim-ThinkPad-P17 kernel: RIP: 0010:nv_drm_master_set+0x27/0x30 [nvidia_drm] Sep 10 22:07:08 tim-ThinkPad-P17 kernel: Code: 10 94 c5 0f 1f 44 00 00 55 48 8b 47 48 48 8b 78 20 48 8b 05 db 5c 00 00 48 89 e5 48 8b 40 28 e8 0f 70 d0 c5 84 c0 74 02 5d c3 <0f> 0b 5d c3 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 41 57 41 56 Sep 10 22:07:08 tim-ThinkPad-P17 kernel: RSP: 0018:b412d214bb80 EFLAGS: 00010246 Sep 10 22:07:08 tim-ThinkPad-P17 kernel: RAX: RBX: 9567cd121600 RCX: 0008 Sep 10 22:07:08 tim-ThinkPad-P17 kernel: RDX: c1be1ed8 RSI: 0292 RDI: c1be1ea0 Sep 10 22:07:08 tim-ThinkPad-P17 kernel: RBP: b412d214bb80 R08: 0008 R09: b412d214bb68 Sep 10 22:07:08 tim-ThinkPad-P17 kernel: R10: R11: 9566404546da R12: 95699d09dc80 Sep 10 22:07:08 tim-ThinkPad-P17 kernel: R13: 95664fa64800 R14: R15: 95664fa64800 Sep 10 22:07:08 tim-ThinkPad-P17 kernel: FS: 7fd6d0285b80() GS:956d5f68() knlGS: Sep 10 22:07:08 tim-ThinkPad-P17 kernel: CS: 0010 DS: ES: CR0: 80050033 Sep 10 22:07:08 tim-ThinkPad-P17 kernel: CR2: 7fd6d098d3ea CR3: 0004ba274002 CR4: 007706e0 Sep 10 22:07:08 tim-ThinkPad-P17 kernel: PKRU: 5554 Sep 10 22:07:08 tim-ThinkPad-P17 kernel:
[Kernel-packages] [Bug 1930903] Re: Frequent kernel oops related to nvidia / nv_drm_master_set
** Also affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1930903 Title: Frequent kernel oops related to nvidia / nv_drm_master_set Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: After upgrading yesterday from ubuntu 20 to 21.04 my machine now exhibits frequent involuntary restarts, related to a kernel oops of the form Jun 3 10:48:32 zotac kernel: [ 20.464926] RIP: 0010:nv_drm_master_set+0x27/0x30 [nvidia_drm] [...] Jun 3 10:48:32 zotac kernel: [ 20.464958] Call Trace: Jun 3 10:48:32 zotac kernel: [ 20.464964] drm_new_set_master+0x7e/0x100 [drm] Jun 3 10:48:32 zotac kernel: [ 20.464994] drm_master_open+0x6e/0xa0 [drm] Jun 3 10:48:32 zotac kernel: [ 20.465017] drm_open+0xf8/0x250 [drm] Jun 3 10:48:32 zotac kernel: [ 20.465044] drm_stub_open+0xba/0x140 [drm] Jun 3 10:48:32 zotac kernel: [ 20.465070] chrdev_open+0xf7/0x220 Jun 3 10:48:32 zotac kernel: [ 20.465075] ? cdev_device_add+0x90/0x90 Jun 3 10:48:32 zotac kernel: [ 20.465078] do_dentry_open+0x156/0x370 Jun 3 10:48:32 zotac kernel: [ 20.465081] vfs_open+0x2d/0x30 Jun 3 10:48:32 zotac kernel: [ 20.465084] do_open+0x1c3/0x340 Jun 3 10:48:32 zotac kernel: [ 20.465087] path_openat+0x10a/0x1d0 Jun 3 10:48:32 zotac kernel: [ 20.465090] do_filp_open+0x8c/0x130 Jun 3 10:48:32 zotac kernel: [ 20.465093] ? __check_object_size+0x1c/0x20 Jun 3 10:48:32 zotac kernel: [ 20.465096] do_sys_openat2+0x9b/0x150 Jun 3 10:48:32 zotac kernel: [ 20.465099] __x64_sys_openat+0x56/0x90 Jun 3 10:48:32 zotac kernel: [ 20.465102] do_syscall_64+0x38/0x90 Jun 3 10:48:32 zotac kernel: [ 20.465105] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 3 10:48:32 zotac kernel: [ 20.465108] RIP: 0033:0x7fe6ea270954 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..0a.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 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1) ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Jun 4 17:00:45 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.11.0-18-generic, x86_64: installed nvidia, 460.80, 5.8.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] [19da:2438] InstallationDate: Installed on 2020-05-09 (391 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: NA ZBOX-ER51070 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=4e73512b-1846-4fe4-87d1-079bbaae2a1a ro quiet splash crashkernel=512M-:192M vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Default string dmi.board.name: ZBOX-ER51070 dmi.board.vendor: NA dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd04/25/2019:br5.12:svnNA:pnZBOX-ER51070:pvrDefaultstring:rvnNA:rnZBOX-ER51070:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZBOX-ER51070 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: NA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 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.11-1ubuntu1
[Kernel-packages] [Bug 1847340] Re: ext4 journal recovery fails w/ data=journal + mmap
Just updating the numbers for Focal / Original in comment #9 (the issue did happen more times overnight.) [ 10.018315] rc.local[744]: 61 FAILED [ 10.018882] rc.local[744]:1186 PASSED -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1847340 Title: ext4 journal recovery fails w/ data=journal + mmap Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: In Progress Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Fix Released Bug description: [Impact] With mmap()ed files on ext4's data journaling it's possible to change a mapped page's buffers contents during their jbd2 transaction commit (as currently nothing prevents/blocks the write access at that time.) This might happen between the buffers checksum calculation and actual write to journal, so the (old) checksum is invalid for the (new) data. If the system crashes after that, but before such journal entry makes it to the filesystem, the journal replay on the next mount just fails, and the filesystem now requires fsck. (apparently curtin might set up /etc/fstab with passno=0, requiring manual intervention.) [39751.096455] EXT4-fs: Warning: mounting with data=journal disables delayed allocation and O_DIRECT support! [39751.114435] JBD2: Invalid checksum recovering block 87305 in log [39751.146133] JBD2: Invalid checksum recovering block 88039 in log [39751.195950] JBD2: Invalid checksum recovering block 49633 in log [39751.265158] JBD2: recovery failed [39751.265163] EXT4-fs (vdc): error loading journal [Fix] The fix is to write-protect the pages during journal transaction commit, so that writes to mapped pages hit a page fault, then ext4's page_mkwrite hook can block until the commit finishes and the buffers can be modified. In order to do that, add jbd2 journal callbacks that the filesystems can customize, called before/after the critical region in transaction commit, then have ext4 in data journaling mode to write-protect the pages whose buffers are being committed (and handle cases that need pages redirtied.) The changes are restricted to the data journaling mode and page_mkwrite hook, and other modes/paths use the same code/behavior in the callbacks. [Test Case] Set up an ext4 filesystem in data journaling mode, and run stress-ng's mmap file test on it, then crash the system after a bit; check whether the filesystem can mount again or not (i.e., with jbd2 checksum errors.) # mkfs.ext4 $DEV # mount -o data=journal $DEV $DIR # cd $DIR # stress-ng --mmap $((4*$(nproc))) --mmap-file & # sleep 60 # echo c >/proc/sysrq-trigger ... # mount -o data=journal $DEV $DIR # PASS/FAIL. # dmesg | tail [Regression Potential] Regressions would likely manifest in ext4 data journaling mode (which is not the default mode, 'ordered') with memory mapped access, as the other modes/paths are largely unaffected by the changes/same behavior. This has been tested with (x)fstests, that showed no regressions on data=ordered and data=journal on both Bionic and Focal (with kernel versions 4.15.0-156-generic and 5.4.0-84-generic) w/in 10 runs each. And the stress-ng test-case as well. (Numbers/details in the LP bug.) [Other info] The patchset is applied on 5.10, so Hirsute (5.11) is already fixed; only Focal and Bionic need it. There are little changes in the patches between Focal and Bionic (mostly minor backport adjustments, mainly due to no vm_fault_t) but unfortunately that needs separate versions for most patches. ... [Original Bug Description] [Impact] In the event of a loss of power, ext4 filesystems mounted w/ data=journal,journal_checksum are subject to a corruption issue that requires a fsck to recover. This is exacerbated by installations by curtin that set passno=0 in /etc/fstab, preventing fsck from running automatically and thus requiring a manual recovery. And *that* is further exacerbated because initramfs-tools is smart enough to not include fsck.ext4 when passno=0 is detected in /etc/fstab, requiring the user to boot from recovery media. [Test Case] Forcibly power cycle a system running 'stress-ng --dir 0'. I've created a package to automate the reproduction: https://git.launchpad.net/~dannf/+git/dgx2-ext4-csum-repro?h=master [Fix] [Regression Risk] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help
[Kernel-packages] [Bug 1925246] Re: binderfs support is not enabled
** Also affects: linux-azure (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-azure (Ubuntu Hirsute) Status: New => Fix Committed ** Changed in: linux-azure (Ubuntu Impish) Status: New => Fix Committed ** Also affects: linux-azure-5.8 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-azure-5.8 (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-azure-5.8 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-azure-5.8 (Ubuntu Impish) Status: New => Invalid -- 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/1925246 Title: binderfs support is not enabled Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure-5.8 package in Ubuntu: Invalid Status in linux-azure source package in Focal: Fix Committed Status in linux-azure-5.8 source package in Focal: Fix Committed Status in linux-azure source package in Hirsute: Fix Committed Status in linux-azure-5.8 source package in Hirsute: Invalid Status in linux-azure source package in Impish: Fix Committed Status in linux-azure-5.8 source package in Impish: Invalid Bug description: [Impact] Hey, in https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1914568 we got binder support enabled but the configuration is completely different from what we have in our other cloud and generic kernels: ubuntu@machine-1:~$ cat /boot/config-5.4.0-1046-azure | grep BINDER CONFIG_ANDROID_BINDER_IPC=m # CONFIG_ANDROID_BINDERFS is not set CONFIG_ANDROID_BINDER_DEVICES="binder,hwbinder,vndbinder" # CONFIG_ANDROID_BINDER_IPC_SELFTEST is not set $ cat /boot/config-5.4.0-14-generic | grep BINDER CONFIG_ANDROID_BINDER_IPC=m CONFIG_ANDROID_BINDERFS=m CONFIG_ANDROID_BINDER_DEVICES="" # CONFIG_ANDROID_BINDER_IPC_SELFTEST is not set Not having binderfs support is breaking Anbox Cloud support. What is the reason for not having the config aligned between the kernels here? Thanks! [Test Plan] After installing the extra modules package, binderfs should be available via mount. [Where problems could occur] It could cause issues to any existing users of the existing binder_linux module. However this module is currently shipped as extra and should not affect regular users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1925246/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943070] Re: linux-aws: Missing check for CONFIG_SUSPEND in amdgpu_acpi.c
Tagging verification done by virtue of the fact that the kernel compiles (which was the problem this bug addresses). ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1943070 Title: linux-aws: Missing check for CONFIG_SUSPEND in amdgpu_acpi.c Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Hirsute: Fix Committed Bug description: SRU Justification [Impact] A missing check in drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.c causes a link error when CONFIG_SUSPEND=n ERROR: modpost: "pm_suspend_target_state" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined! This issue was introduced by an upstream stable update (commit 5706cb3c910cc8283f344bc37a889a8d523a2c6d upstream). [Test Plan] Successfully build and link. [Where problems could occur] This is a build time issue. No run time regression is possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1943070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878389] Re: tpci from kernel_misc in ubuntu_ltp failed with Test-case '12'/'13'
This issue was fixed however if you still see Test-case 12 failures, e.g. on s390x, please check lp:1943259 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878389 Title: tpci from kernel_misc in ubuntu_ltp failed with Test-case '12'/'13' Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Bug description: With bug 1868707 fixed, the tpci test can finish now, and it's reporting another issue here: test_pci 489 TFAIL : tpci.c:73: PCI bus 01 slot 01 : Test-case '13' Please find attachment for dmesg log and the full test log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: User Name 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 10:08 seq crw-rw 1 root audio 116, 33 May 13 10:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Wed May 13 10:19:01 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.product.sku: 780020-S01 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1878389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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])
** Attachment added: "lscpu_gulpin" https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+attachment/5524415/+files/lscpu_gulpin -- You 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 Hirsute: New 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 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])
** Attachment added: "lscpu_thiel" https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+attachment/5524414/+files/lscpu_thiel -- You 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 Hirsute: New 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 1930188] Re: Acer Aspire 5 sound driver issues
Sure will do. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5 machine, if it could introduce regression, it will make the audio like internal mic and internal spk stop working. But this possibility is very low. Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with ALC255. I will list all of them below and what I have tried so far. 1. Headphones appears always plugged in even if they are physically not 2. When actually plugging in headset/earphones it does not auto switch from speakers/internal mic to headphones/headset microphone automatically and vice versa, have to manually switch everytime. 3. External headset/earphones microphone won't work at all After, logs of trial and error I have found a temporary fix. This seems to use legacy intel drivers which solves all 3 issues mentioned above but the internal/dmic mic is completely gone (which seems intentional when using this). Both depreciated dmic_detect and dsp_driver works, I have been using dsp_driver for now as I need external microphone at any cost. End of /etc/modprobe.d/alsa-base.conf # Headset mic fix options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1 options snd-hda-intel model=alc255-acer In another thread similar to this I got some support and at least fixed the external microphone without using the alsa-base.conf change in custom modified kernel. I will attach it here. Now, hoping to fix other issues as well slowly like making headphones unplugged when physically removing as well as auto switching like the legacy driver one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943086] Re: linux-modules-nvidia-470-generic-hwe-20.04 dependency cant be installed
I can confirm that right after a system update I am no longer able to view the login screen or access the desktop. It's stuck at a black screen with a blinking cursor. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1943086 Title: linux-modules-nvidia-470-generic-hwe-20.04 dependency cant be installed Status in linux-restricted-modules-hwe-5.11 package in Ubuntu: Confirmed Bug description: linux-modules-nvidia-470-generic-hwe-20.04=5.11.0-34.36~20.04.1 depends on nvidia-kernel-common-470 (>= 470.63.01) but that version is not published, the latest one available today is 470.57.02-0ubuntu0.20.04.1 That means that installing latest hwe kernel for 20.04 breaks nvidia driver. This is problematic in distros like Elementary OS 6 as they dont expose the grub menu, so you have the latest kernel version installed only, which will not be able to boot on the graphical interface because there is no driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.11/+bug/1943086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943250] Re: package linux-image-5.11.0-34-generic 5.11.0-34.36~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1943250 Title: package linux-image-5.11.0-34-generic 5.11.0-34.36~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: See attachement ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-34-generic 5.11.0-34.36~20.04.1 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 CasperMD5CheckResult: skip Date: Fri Sep 10 13:25:29 2021 ErrorMessage: installed linux-image-5.11.0-34-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-06-19 (83 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-signed-hwe-5.11 Title: package linux-image-5.11.0-34-generic 5.11.0-34.36~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1943250/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943250] [NEW] package linux-image-5.11.0-34-generic 5.11.0-34.36~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: See attachement ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-34-generic 5.11.0-34.36~20.04.1 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 CasperMD5CheckResult: skip Date: Fri Sep 10 13:25:29 2021 ErrorMessage: installed linux-image-5.11.0-34-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-06-19 (83 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-signed-hwe-5.11 Title: package linux-image-5.11.0-34-generic 5.11.0-34.36~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal ** Attachment added: "linux-image-5.11.0-34-generic.0.crash" https://bugs.launchpad.net/bugs/1943250/+attachment/5524378/+files/linux-image-5.11.0-34-generic.0.crash -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1943250 Title: package linux-image-5.11.0-34-generic 5.11.0-34.36~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: See attachement ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-34-generic 5.11.0-34.36~20.04.1 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 CasperMD5CheckResult: skip Date: Fri Sep 10 13:25:29 2021 ErrorMessage: installed linux-image-5.11.0-34-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-06-19 (83 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-signed-hwe-5.11 Title: package linux-image-5.11.0-34-generic 5.11.0-34.36~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1943250/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942701] Re: Touchpad not working Ubuntu 20.04 focal fossa
Hi all, any update on this? Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1942701 Title: Touchpad not working Ubuntu 20.04 focal fossa Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 Laptop model: Lenovo-IdeaPad-S145-15IIL Touchpad not working since I installed Ubuntu 20.04. This is the first time I installed ubuntu on this computer. $ xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ PixArt Dell MS116 USB Optical Mouse id=9[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Ideapad extra buttons id=11 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-27-generic 5.11.0-27.29~20.04.1 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 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Sep 5 14:35:11 2021 InstallationDate: Installed on 2021-09-04 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1942701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894407] Re: linux-tools: can perf be linked against libbfd, maybe statically?
I've prepared a patch that uses a single long-running instance of addr2line for each dso, instead of one per address request. It dramatically speeds up e.g. `perf script` operation (I don't know if it solves OP's problem but it could be relevant!). Discussion on linux-perf-users mailing list: https://lore.kernel.org/linux-perf- users/20210910102307.2055484-1-to...@leastfixedpoint.com/ Background: https://eighty-twenty.org/2021/09/09/perf-addr2line-speed- improvement -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894407 Title: linux-tools: can perf be linked against libbfd, maybe statically? Status in linux package in Ubuntu: Won't Fix Bug description: The perf tool has an optional dependency on libbfd. Per Debian policy, and due to some situation involving parallel installations of this library, no packages should link dynamically against libbfd. In the past, bugs have been filed to link perf statically against libbfd in bug 783660 (from 2011) and then to just not link against it at all in bug 1748922 (from 2018) and bug 1828234 (from 2019). The argument was made that perf does not need this dependency, as perf can use libiberty as an alternative to demangle C++ names. However, that is not the only thing perf is using libbfd for: the other is to implement an inlined version of addr2line. This was part of an important patchset from 2013 that strove to improve the performance of perf. In my case, I ran my program for all of 30 seconds, generating a 163M large trace, and have been waiting almost an hour for the events to process... and it is only a third of the way done; what I see it doing is spawning, over and over and over again, addr2line, which it wouldn't do if linked against libbfd. https://lore.kernel.org/patchwork/patch/413455/ Is it possible to link perf statically against libbfd, in order to let it use the in-process implementation of addr2line? That is the solution that I've understood for other packages, such as oprofile in bug 426614 and bug 588033. Doing a quick grep of the code of perf for HAVE_LIBBFD_SUPPORT, it seems like bpf disassembly support is also dependent on libbfd (and so while it is great that Ubuntu's build of perf has been compiled against libbpf, it seems like that functionality is being hampered by the lack of linking libbfd). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943033] Re: ubuntu_kvm_smoke_test: uvt-kvm: error: libvirt: XML error: No PCI buses available on s390x
** Tags added: 4.4
** Tags added: sru-20210906
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu Xenial)
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/1943033
Title:
ubuntu_kvm_smoke_test: uvt-kvm: error: libvirt: XML error: No PCI
buses available on s390x
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Confirmed
Bug description:
02:56:35 DEBUG| stdout:
02:56:35 DEBUG| INFO: /dev/kvm exists
02:56:35 DEBUG| KVM acceleration can be used
02:56:35 DEBUG| stderr:
02:56:35 DEBUG| + SUT=bjf-test
02:56:35 DEBUG| + SSH_KEY=/home/ubuntu/.ssh/id_rsa
02:56:35 DEBUG| + SSH_OPTIONS='-o StrictHostKeyChecking=no -o
UserKnownHostsFile=/dev/null -o LogLevel=quiet -i /home/ubuntu/.ssh/id_rsa'
02:56:35 DEBUG| ++ lsb_release -c
02:56:35 DEBUG| ++ awk '{print$2}'
02:56:35 DEBUG| + DISTRO=xenial
02:56:35 DEBUG| + ARCHITECTURE=s390x
02:56:35 DEBUG| + trap cleanup EXIT
02:56:35 DEBUG| + '[' -z s390x ']'
02:56:35 DEBUG| + kvm-ok
02:56:35 DEBUG| + '[' 0 '!=' 0 ']'
02:56:35 DEBUG| + set -e
02:56:35 DEBUG| + '[' '!' -f /home/ubuntu/.ssh/id_rsa ']'
02:56:35 DEBUG| + '[' s390x = ppc64el ']'
02:56:35 DEBUG| ++ uvt-simplestreams-libvirt query
02:56:35 DEBUG| ++ grep -P 'xenial.*s390x'
02:56:35 DEBUG| + image='release=xenial arch=s390x label=daily (20210203)'
02:56:35 DEBUG| + '[' -z 'release=xenial arch=s390x label=daily (20210203)'
']'
02:56:35 DEBUG| + uvt-kvm create bjf-test release=xenial arch=s390x
02:56:35 DEBUG| uvt-kvm: error: libvirt: XML error: No PCI buses available
02:56:35 DEBUG| + cleanup
02:56:35 DEBUG| + uvt-kvm destroy bjf-test
02:56:36 INFO | ERROR ubuntu_kvm_smoke_test.kvm_smoke_test
ubuntu_kvm_smoke_test.kvm_smoke_testtimestamp=1630983396localtime=Sep
07 02:56:36 Command
failed, rc=1, Command returned non-zero exit status
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1943033/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1760087] Re: net test in ubuntu_kernel_selftest failed on linux-kvm
Still failing with xenial/linux 4.4.0-215.247, but only on s390x systems. ** Tags added: sru-20210906 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1760087 Title: net test in ubuntu_kernel_selftest failed on linux-kvm Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Steps: 1. Deploy a KVM node with Xenial, install linux-kvm on it. 2. git clone --depth 1 https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial linux 3. Run the "net" sub set in the kernel_selftest Result: * test: TPACKET_V1 with PACKET_RX_RING open: No such file or directory * test_bpf: [FAIL] * selftests: test_bpf.sh [FAIL] Output: $ sudo make -C linux/tools/testing/selftests/net all run_tests make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' make: Nothing to be done for 'all'. running socket test [PASS] selftests: run_netsocktests [PASS] running psock_fanout test test: control single socket test: control multiple sockets test: datapath 0x0 info: count=0,0, expect=0,0 info: count=15,5, expect=15,5 info: count=20,5, expect=20,5 test: datapath 0x1000 info: count=0,0, expect=0,0 info: count=15,5, expect=15,5 info: count=20,15, expect=20,15 test: datapath 0x1 info: count=0,0, expect=0,0 info: count=10,10, expect=10,10 info: count=18,17, expect=18,17 test: datapath 0x3 info: count=0,0, expect=0,0 info: count=15,5, expect=15,5 info: count=20,15, expect=20,15 test: datapath 0x6 info: count=0,0, expect=0,0 info: count=5,15, expect=15,5 info: count=20,15, expect=15,20 test: datapath 0x7 bpf: Function not implemented bpf verifier: ���ߟ [FAIL] running psock_tpacket test test: TPACKET_V1 with PACKET_RX_RING open: No such file or directory [FAIL] selftests: run_afpackettests [PASS] test_bpf: [FAIL] selftests: test_bpf.sh [FAIL] make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24 ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98 Uname: Linux 4.4.0-1019-kvm x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Mar 30 12:12:46 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1760087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809701] Re: cpu_hotplug test in ubuntu_kernel_selftest failed on Moonshot ARM64
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809701 Title: cpu_hotplug test in ubuntu_kernel_selftest failed on Moonshot ARM64 Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Disco: Won't Fix Bug description: Test failed with "Operation not supported" when trying to offline a CPU: echo 0 > $SYSFS/devices/system/cpu/cpu$1/online This issue cannot be reproduced on CaviumThunderX ARM64 server, just the moonshots. $ sudo make -C linux/tools/testing/selftests TARGETS=cpu-hotplug run_tests make: Entering directory '/home/ubuntu/linux/tools/testing/selftests' make[1]: Entering directory '/home/ubuntu/linux/tools/testing/selftests/cpu-hotplug' make[1]: Nothing to be done for 'all'. make[1]: Leaving directory '/home/ubuntu/linux/tools/testing/selftests/cpu-hotplug' make[1]: Entering directory '/home/ubuntu/linux/tools/testing/selftests/cpu-hotplug' TAP version 13 selftests: cpu-hotplug: cpu-on-off-test.sh pid 8132's current affinity mask: ff pid 8132's new affinity mask: 1 CPU online/offline summary: Cpus in online state: 0-7 Cpus in offline state: 0 Limited scope test: one hotplug cpu (leaves cpu in the original state): online to offline to online: cpu 7 ./cpu-on-off-test.sh: line 92: echo: write error: Operation not supported offline_cpu_expect_success 7: unexpected fail not ok 1..1 selftests: cpu-hotplug: cpu-on-off-test.sh [FAIL] make[1]: Leaving directory '/home/ubuntu/linux/tools/testing/selftests/cpu-hotplug' make: Leaving directory '/home/ubuntu/linux/tools/testing/selftests' The CPU hotplug config was enabled on this SUT: $ cat /boot/config-`uname -r` | grep HOTPLUG | grep CPU CONFIG_HOTPLUG_CPU=y CONFIG_ACPI_HOTPLUG_CPU=y # CONFIG_CPU_HOTPLUG_STATE_CONTROL is not set ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: User Name 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 25 04:01 seq crw-rw 1 root audio 116, 33 Dec 25 04:01 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.1 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Dec 25 04:54:54 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1809701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905591] Re: no brightness control in {455, 460} after update from 450
Now, it works for me (ubuntu 20.04.3) with the kernel (v5.11.0.34.36)
parameter
nvidia.NVreg_RegistryDwords=EnableBrightnessControl=1
And nvidia drivers 460.91.03. No need to do anything else.
The parameter is mentioned in arch wiki
https://wiki.archlinux.org/title/NVIDIA#Enabling_brightness_control
This is all for discrete mode. Credits to @Chaplan from legion discord
for finding this.
For hybrid mode, there is different kernel parameter (for AMD)
amdgpu.backlight=0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1905591
Title:
no brightness control in {455,460} after update from 450
Status in OEM Priority Project:
New
Status in nvidia-graphics-drivers-455 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
Confirmed
Bug description:
On my Lenovo X1 Extreme with GPU: NVIDIA Corporation GP107M [GeForce
GTX 1050 Ti Mobile]:
WORKS FINE:
nvidia-driver-450: 450.102.04-0ubuntu0.18.04.1
NO BRIGHTNESS CONTROL:
nvidia-driver-455: 455.38-0ubuntu0.18.04.1
nvidia-driver-460: 460.32.03-0ubuntu0.18.04.1
nvidia-driver-460: 460.39-0ubuntu0.18.04.1
*WORKAROUND: See comment #11 (add nvidia drivers to initramfs).
*Note that 460 fixes it for a 20.04 ThinkPad P73 per comment #6, but
not for my 18.04.5 Lenovo ThinkPad X1 per comment #5.
Updating to nvidia-driver-455 (or -460) results in loss of brightness
control. On boot, the laptop display brightness is somewhat less than
fully bright and cannot be changed. The brightness up/down keys do
pop up the gnome gui brightness widget, and
/sys/class/backlight/nvidia_0/* values do change, but the actual
display's brightness does not.
Problem occurs with either version of nvidia-driver-455 (the archive
or the ~graphics-drivers/PPA) or any version of -460.
Normal functionality returns if I downgrade to any version of nvidia-
driver-450.
Also observed: 455 and 460 temporarily display some pixel garbage
while mode-switching during the graphic login sequence. Only a minor
glitch, but note that 450 does not exhibit that issue either.
Note also that manually applying this to
/lib/systemd/system/nvidia-persistenced.service has no effect on the problem:
https://github.com/hugh712/nvidia-graphics-drivers/commit/bccad5ee6444dd8c5c47ba19ea0232106a1086f5
Distributor ID: Ubuntu
Description: Ubuntu 18.04.5 LTS
Release: 18.04
Codename: bionic
kernel: 5.4.0-54-generic #60~18.04.1-Ubuntu SMP Fri Nov 6 17:25:16 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1905591/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues
@Bijay, About the new issue, please file a new bug against it. thx. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5 machine, if it could introduce regression, it will make the audio like internal mic and internal spk stop working. But this possibility is very low. Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with ALC255. I will list all of them below and what I have tried so far. 1. Headphones appears always plugged in even if they are physically not 2. When actually plugging in headset/earphones it does not auto switch from speakers/internal mic to headphones/headset microphone automatically and vice versa, have to manually switch everytime. 3. External headset/earphones microphone won't work at all After, logs of trial and error I have found a temporary fix. This seems to use legacy intel drivers which solves all 3 issues mentioned above but the internal/dmic mic is completely gone (which seems intentional when using this). Both depreciated dmic_detect and dsp_driver works, I have been using dsp_driver for now as I need external microphone at any cost. End of /etc/modprobe.d/alsa-base.conf # Headset mic fix options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1 options snd-hda-intel model=alc255-acer In another thread similar to this I got some support and at least fixed the external microphone without using the alsa-base.conf change in custom modified kernel. I will attach it here. Now, hoping to fix other issues as well slowly like making headphones unplugged when physically removing as well as auto switching like the legacy driver one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943079] Re: Installing latest linux-firmware (1.187.16) causes wifi interface to disappear
Yes, I believe it is an Intel AX210. * I booted into Windows, and AX210 is the driver name in Windows device manager. * Also, in the dmesg output, you'll also see AX210 detected message, on line 1137 in the attachment. ** Attachment added: "dmesg output from Lenovo T15 G2" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1943079/+attachment/5524368/+files/dmesg_len_t15g2.txt -- 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/1943079 Title: Installing latest linux-firmware (1.187.16) causes wifi interface to disappear Status in linux-firmware package in Ubuntu: New Bug description: Summary === Installing linux-firmware 1.187.16, which became available on 17th Aug 2021, caused my wifi interface to disappear after reboot. My machine: Lenovo T15 Gen2 CPU: 11th Gen Intel(R) Core(TM) i7-1165G7 I tried force installing previous version 1.187.15, but that version isn't available! So, in the end, I rebooted into a live CD and re-installed the OS! In the newly installed OS, I just made sure to NOT select linux- firmware package in the list of available upgrades, and I will stick with version 1.187.15 till I have confidence there is better and working version. NOTE: On an older machine, with an older chipset, I did NOT experience this issue. Older machine: Lenovo x230 CPU: Intel(R) Core(TM) i5-3210M CPU Wifi: Centrino Advanced-N 6205 System == I'm running Linux Mint Edge, based on Ubuntu 20.04, but with upgraded kernel (5.11.0.34): lsb_release -rd Description: Linux Mint 20.2 Release: 20.2 Package === apt-cache policy linux-firmware linux-firmware: Installed: 1.187.16 Candidate: 1.187.16 Version table: *** 1.187.16 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages Expected Upgrade to linux-firmware=1.187.16 Reboot. Wifi network Interface must continue to be available and functioning. What Happened = Upgrade to linux-firmware=1.187.16 Reboot. Wifi network interface disappeared. Therefore, cannot use wifi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1943079/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930754] Re: e1000e extremly slow
** Tags added: fossa-edge-staging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1930754 Title: e1000e extremly slow Status in OEM Priority Project: Confirmed Status in linux-oem-5.10 package in Ubuntu: Confirmed Bug description: We have dell latitude 5420 & 5520 laptops with onboard intel ethernet controller. Problem is that the ethernet port is extremely slow. about 100kbyte/s download throughput while on a gigabit connection. Upload seems to work just fine. Also when I pxe boot the system it's also painfully slow. But here comes the funny part. When I attach a usb memory stick the throughput of the networkcontroller is as expected. I've used latest ubuntu 20.04.2 kernel 5.8.0-55 I've used latest ubuntu 20.04.2 kernel 5.10.0-1029-oem Turns out this problem is not showing up when I manually install the 5.8.18 kernel. Also when I create my own iso with the help of Cubic and install the 5.8.18 kernel in it the pxe boot is working as expected with high throughput system: Dell latitude 5420 + 5520 nic: Ethernet Connection (13) I219-LM ubuntu 20.04.2 module: e1000e Please assist. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1930754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943239] Re: second monitor
Thanks for the bug report. Your second monitor is not working apparently because you are using the 'fbdev' Xorg driver, which shouldn't happen. It looks like that happened because the proper 'modesetting' driver failed to find a graphics device at /dev/dri/card0. So it would appear this is a kernel bug. Please try removing the 'biosdevname=0' kernel parameter and tell us if that resolves the problem. Please also try booting an older kernel version and tell us if that fixes it. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Summary changed: - second monitor + [amdgpu] second monitor ** Summary changed: - [amdgpu] second monitor + [amdgpu] /dev/dri/card0 is missing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943239 Title: [amdgpu] /dev/dri/card0 is missing Status in linux package in Ubuntu: Incomplete Bug description: the second monitor is not connected on laptop MSI Modern 14 B4MW ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 10 11:52:09 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Renoir [1462:12c8] InstallationDate: Installed on 2021-09-09 (1 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) MachineType: Micro-Star International Co., Ltd. Modern 14 B4MW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-84-generic root=UUID=54f1902f-8670-4bf3-9b25-b3ae9ba6e80c ro net.ifnames=0 biosdevname=0 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2021 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E14DKAMS.114 dmi.board.asset.tag: Default string dmi.board.name: MS-14DK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE14DKAMS.114:bd06/02/2021:svnMicro-StarInternationalCo.,Ltd.:pnModern14B4MW:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14DK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: Modern dmi.product.name: Modern 14 B4MW dmi.product.sku: 14DK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. 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/+bug/1943239/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943154] Re: [i915] My resolution has changed to 800x600, it was 1600x900 before
Weirdly, this sounds just like bug 1943239. But the kernel version is different and the GPU type is different. -- 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/1943154 Title: [i915] My resolution has changed to 800x600, it was 1600x900 before Status in linux-hwe-5.11 package in Ubuntu: Incomplete Bug description: My resolution has suddenly changed from a higher resolution from to low resolution to 800x600 and it is now showing only one resolution option 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 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 9 20:32:10 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:2042] ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=78d7ef17-370f-42ec-839a-ad90938c65fb ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: HOH6110H.86A.0010.2012.0424.1632 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH61HO dmi.board.vendor: Intel Corporation dmi.board.version: AAG62445-102 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrHOH6110H.86A.0010.2012.0424.1632:bd04/24/2012:svn:pn:pvr:sku:rvnIntelCorporation:rnDH61HO:rvrAAG62445-102:cvn:ct3:cvr: 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 21.0.3-0ubuntu0.3~20.04.1 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/1943154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943239] [NEW] second monitor
You have been subscribed to a public bug: the second monitor is not connected on laptop MSI Modern 14 B4MW ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 10 11:52:09 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Renoir [1462:12c8] InstallationDate: Installed on 2021-09-09 (1 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) MachineType: Micro-Star International Co., Ltd. Modern 14 B4MW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-84-generic root=UUID=54f1902f-8670-4bf3-9b25-b3ae9ba6e80c ro net.ifnames=0 biosdevname=0 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2021 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E14DKAMS.114 dmi.board.asset.tag: Default string dmi.board.name: MS-14DK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE14DKAMS.114:bd06/02/2021:svnMicro-StarInternationalCo.,Ltd.:pnModern14B4MW:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14DK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: Modern dmi.product.name: Modern 14 B4MW dmi.product.sku: 14DK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. 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 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- second monitor https://bugs.launchpad.net/bugs/1943239 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942633] Re: Can not boot impish in Cavium ThunderX
** Attachment added: "System.map-5.14.0-9-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942633/+attachment/5524363/+files/System.map-5.14.0-9-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/1942633 Title: Can not boot impish in Cavium ThunderX Status in linux package in Ubuntu: Confirmed Bug description: Hi I am trying to deploy a Impish server (Ubuntu 5.11.0-13.14-generic 5.11.7) in arm64 description: Computer product: Cavium ThunderX CN88XX board width: 64 bits I tried 2 releases: - 20210817 ( https://images.maas.io/ephemeral-v3/stable/impish/arm64/20210817/ga-21.10/ ) - 20210830 ( https://images.maas.io/ephemeral-v3/candidate/impish/arm64/20210830/ ) 20210817: Ends the deploy successfully but fails to boot from disk: ``` [0.00] Booting Linux on physical CPU 0x00 [0x431f0a11] [0.00] Linux version 5.13.0-14-generic (buildd@bos02-arm64-018) (gcc (Ubuntu 10.3.0-6ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.37) #14-Ubuntu SMP Mon Aug 2 12:40:58 UTC 2021 (Ubuntu 5.13.0-14.14-generic 5.13.1) [0.00] Machine model: Cavium ThunderX CN88XX board [ 139.896752] raid6: xor() 1224 MB/s, rmw enabled [ 139.957046] raid6: using neon recovery algorithm [ 140.020937] xor: measuring software checksum speed [ 140.085571]8regs : 2432 MB/sec [ 140.149834]32regs : 2687 MB/sec [ 140.212202]arm64_neon : 4390 MB/sec [ 140.271985] xor: using function: arm64_neon (4390 MB/sec) [ 140.335013] async_tx: api initialized (async) done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... [ 140.569847] Btrfs loaded, crc32c=crc32c-generic, zoned=yes Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... mdadm: No devices listed in conf file were found. done. mdadm: No devices listed in conf file were found. ``` 20210830 Fails the network boot: ``` [ 140.351066] async_tx: api initialized (async) done. Begin: Running /scripts/init-premount ... cloud-initramfs-dyn-netconf: did no find a nic with 1c:1b:0d:0d:52:7c done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Begin: Waiting up to 180 secs for BOOTIF to become available ... Failure: Interface BOOTIF did not appear in time done. ipconfig: BOOTIF: SIOCGIFINDEX: No such device ipconfig: no devices to configure ``` I will attach full logs of each try. JFYI, this is the same machine as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942633] Re: Can not boot impish in Cavium ThunderX
** Attachment added: "System.map-5.13.0-14-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942633/+attachment/5524361/+files/System.map-5.13.0-14-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/1942633 Title: Can not boot impish in Cavium ThunderX Status in linux package in Ubuntu: Confirmed Bug description: Hi I am trying to deploy a Impish server (Ubuntu 5.11.0-13.14-generic 5.11.7) in arm64 description: Computer product: Cavium ThunderX CN88XX board width: 64 bits I tried 2 releases: - 20210817 ( https://images.maas.io/ephemeral-v3/stable/impish/arm64/20210817/ga-21.10/ ) - 20210830 ( https://images.maas.io/ephemeral-v3/candidate/impish/arm64/20210830/ ) 20210817: Ends the deploy successfully but fails to boot from disk: ``` [0.00] Booting Linux on physical CPU 0x00 [0x431f0a11] [0.00] Linux version 5.13.0-14-generic (buildd@bos02-arm64-018) (gcc (Ubuntu 10.3.0-6ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.37) #14-Ubuntu SMP Mon Aug 2 12:40:58 UTC 2021 (Ubuntu 5.13.0-14.14-generic 5.13.1) [0.00] Machine model: Cavium ThunderX CN88XX board [ 139.896752] raid6: xor() 1224 MB/s, rmw enabled [ 139.957046] raid6: using neon recovery algorithm [ 140.020937] xor: measuring software checksum speed [ 140.085571]8regs : 2432 MB/sec [ 140.149834]32regs : 2687 MB/sec [ 140.212202]arm64_neon : 4390 MB/sec [ 140.271985] xor: using function: arm64_neon (4390 MB/sec) [ 140.335013] async_tx: api initialized (async) done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... [ 140.569847] Btrfs loaded, crc32c=crc32c-generic, zoned=yes Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... mdadm: No devices listed in conf file were found. done. mdadm: No devices listed in conf file were found. ``` 20210830 Fails the network boot: ``` [ 140.351066] async_tx: api initialized (async) done. Begin: Running /scripts/init-premount ... cloud-initramfs-dyn-netconf: did no find a nic with 1c:1b:0d:0d:52:7c done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Begin: Waiting up to 180 secs for BOOTIF to become available ... Failure: Interface BOOTIF did not appear in time done. ipconfig: BOOTIF: SIOCGIFINDEX: No such device ipconfig: no devices to configure ``` I will attach full logs of each try. JFYI, this is the same machine as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942633] Re: Can not boot impish in Cavium ThunderX
** Attachment added: "System.map-5.13.0-16-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942633/+attachment/5524362/+files/System.map-5.13.0-16-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/1942633 Title: Can not boot impish in Cavium ThunderX Status in linux package in Ubuntu: Confirmed Bug description: Hi I am trying to deploy a Impish server (Ubuntu 5.11.0-13.14-generic 5.11.7) in arm64 description: Computer product: Cavium ThunderX CN88XX board width: 64 bits I tried 2 releases: - 20210817 ( https://images.maas.io/ephemeral-v3/stable/impish/arm64/20210817/ga-21.10/ ) - 20210830 ( https://images.maas.io/ephemeral-v3/candidate/impish/arm64/20210830/ ) 20210817: Ends the deploy successfully but fails to boot from disk: ``` [0.00] Booting Linux on physical CPU 0x00 [0x431f0a11] [0.00] Linux version 5.13.0-14-generic (buildd@bos02-arm64-018) (gcc (Ubuntu 10.3.0-6ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.37) #14-Ubuntu SMP Mon Aug 2 12:40:58 UTC 2021 (Ubuntu 5.13.0-14.14-generic 5.13.1) [0.00] Machine model: Cavium ThunderX CN88XX board [ 139.896752] raid6: xor() 1224 MB/s, rmw enabled [ 139.957046] raid6: using neon recovery algorithm [ 140.020937] xor: measuring software checksum speed [ 140.085571]8regs : 2432 MB/sec [ 140.149834]32regs : 2687 MB/sec [ 140.212202]arm64_neon : 4390 MB/sec [ 140.271985] xor: using function: arm64_neon (4390 MB/sec) [ 140.335013] async_tx: api initialized (async) done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... [ 140.569847] Btrfs loaded, crc32c=crc32c-generic, zoned=yes Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... mdadm: No devices listed in conf file were found. done. mdadm: No devices listed in conf file were found. ``` 20210830 Fails the network boot: ``` [ 140.351066] async_tx: api initialized (async) done. Begin: Running /scripts/init-premount ... cloud-initramfs-dyn-netconf: did no find a nic with 1c:1b:0d:0d:52:7c done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Begin: Waiting up to 180 secs for BOOTIF to become available ... Failure: Interface BOOTIF did not appear in time done. ipconfig: BOOTIF: SIOCGIFINDEX: No such device ipconfig: no devices to configure ``` I will attach full logs of each try. JFYI, this is the same machine as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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])
Can you repeat tests with latest kernels? I could not reproduce it on Focal with following configurations: 1. Power8: P8LPAR05 MAAS 2. Power9: QEMU with 4 or 128 CPUs (and 4 GB of RAM) Tested kernels: F/5.4.0-84-generic F/5.11.0-34-generic Tried steps: 1. Freshly boot machine. 2. Log in via ssh. 3. sudo ./autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/cpu-hotplug/cpu-on-off-test.sh 4. for i in `seq 100`; do echo $i ; sleep 2 ; sudo ./autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf_cpu ; done -- You 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 Hirsute: New 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 1943237] [NEW] My touchpad driver - Synaptics stuck after login - Ubuntu 18.04
Public bug reported: When I login to my computer , My touchpad sometimes work and sometimes it is stuck. Also same thing happens with keyboard. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-81-generic 5.4.0-81.91~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-81.91~18.04.1-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 10 13:29:49 2021 InstallationDate: Installed on 2019-04-03 (891 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.4 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1943237 Title: My touchpad driver - Synaptics stuck after login - Ubuntu 18.04 Status in linux-signed-hwe-5.4 package in Ubuntu: New Bug description: When I login to my computer , My touchpad sometimes work and sometimes it is stuck. Also same thing happens with keyboard. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-81-generic 5.4.0-81.91~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-81.91~18.04.1-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 10 13:29:49 2021 InstallationDate: Installed on 2019-04-03 (891 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1943237/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
hirsute' to 'verification-done-hirsute'. If the problem still exists,
change the tag 'verification-needed-hirsute' to 'verification-failed-
hirsute'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-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 1943070] Re: linux-aws: Missing check for CONFIG_SUSPEND in amdgpu_acpi.c
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1943070 Title: linux-aws: Missing check for CONFIG_SUSPEND in amdgpu_acpi.c Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Hirsute: Fix Committed Bug description: SRU Justification [Impact] A missing check in drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.c causes a link error when CONFIG_SUSPEND=n ERROR: modpost: "pm_suspend_target_state" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined! This issue was introduced by an upstream stable update (commit 5706cb3c910cc8283f344bc37a889a8d523a2c6d upstream). [Test Plan] Successfully build and link. [Where problems could occur] This is a build time issue. No run time regression is possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1943070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941741] Re: Bluetooth not working
WLAN does not work if the access point supports VHT160. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1941741 Title: Bluetooth not working Status in linux-signed-oem-5.13 package in Ubuntu: New Bug description: I made a fresh install on a XPS 13 9310 with ubuntu-20.04.2.0-desktop- amd64.iso. It installed the Kernel from linux-image-5.6.0-1047-oem and upgrades to linux-image-5.10.0-1044-oem automatically. With the later kernel, WiFi and Bluetooth stopped working. There were also issues at shutdown. I then installed linux-image-5.13.0-1010-oem which solved the WiFi problem, but Bluetooth still doesn't work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-1010-oem 5.13.0-1010.11 ProcVersionSignature: Ubuntu 5.13.0-1010.11-oem 5.13.1 Uname: Linux 5.13.0-1010-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 26 13:31:41 2021 InstallationDate: Installed on 2021-08-25 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.13/+bug/1941741/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939996] Re: kernel BUG at mm/zswap.c:1275
The fix is not in upstream 5.11 stable... So maybe send SRU to ubuntu kernel to include the fix: https://wiki.ubuntu.com/Kernel/Dev/StablePatchFormat -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939996 Title: kernel BUG at mm/zswap.c:1275 Status in linux package in Ubuntu: Confirmed Bug description: I have just found the following lines in dmesg. I do not know what caused the bug. But mentioned PIDs are now labeled as zombie. Apps running by these process have hang. [37300.978014] [ cut here ] [37300.978020] kernel BUG at mm/zswap.c:1275! [37300.978027] invalid opcode: [#2] SMP PTI [37300.978032] CPU: 2 PID: 2735 Comm: marco Tainted: P DOE 5.11.0-25-generic #27-Ubuntu [37300.978035] Hardware name: Acer Extensa 2520G/BA50_SL , BIOS V1.15 05/13/2016 [37300.978037] RIP: 0010:zswap_frontswap_load+0x273/0x280 [37300.978044] Code: 9c 3d 01 f3 48 ab 83 aa 68 13 00 00 01 eb 84 48 8d 7b 10 e8 df 55 97 00 c7 43 10 00 00 00 00 44 8b 6b 30 e9 47 ff ff ff 0f 0b <0f> 0b e8 e6 ba 96 00 66 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 [37300.978047] RSP: :ba3a42f2bbc0 EFLAGS: 00010282 [37300.978051] RAX: 0200 RBX: da3a3fd03390 RCX: 0017c000 [37300.978054] RDX: e151ced99400 RSI: 8d52b25299c0 RDI: 0db0 [37300.978056] RBP: ba3a42f2bc48 R08: 0490 R09: e151ceda5f40 [37300.978058] R10: R11: ba3a4057c000 R12: 8d50c18e42a0 [37300.978060] R13: ffea R14: 8d4f52597628 R15: 8d4f52597620 [37300.978063] FS: 7f2d60ec2a80() GS:8d52b250() knlGS: [37300.978066] CS: 0010 DS: ES: CR0: 80050033 [37300.978068] CR2: 7f9b24d275a0 CR3: 00010fbc2005 CR4: 003706e0 [37300.978071] Call Trace: [37300.978076] __frontswap_load+0x80/0xd0 [37300.978079] swap_readpage+0x148/0x270 [37300.978084] swap_cluster_readahead+0x1c2/0x310 [37300.978089] swapin_readahead+0x2a/0x30 [37300.978093] do_swap_page+0x401/0x760 [37300.978098] handle_pte_fault+0x1ff/0x260 [37300.978102] __handle_mm_fault+0x599/0x7c0 [37300.978106] ? timerqueue_add+0x68/0xa0 [37300.978111] handle_mm_fault+0xd7/0x2b0 [37300.978115] do_user_addr_fault+0x1a3/0x450 [37300.978120] exc_page_fault+0x6c/0x150 [37300.978123] ? asm_exc_page_fault+0x8/0x30 [37300.978128] asm_exc_page_fault+0x1e/0x30 [37300.978132] RIP: 0033:0x7f2d617dc1b4 [37300.978135] Code: 05 c3 0f 1f 40 00 31 c0 48 83 7e 08 00 0f 95 c0 c3 0f 1f 44 00 00 f3 0f 1e fa 31 c0 48 39 3e 75 0d 48 8b 46 08 48 85 c0 74 04 <48> 8b 40 08 c3 0f 1f 80 00 00 00 00 f3 0f 1e fa 48 39 3e 74 07 31 [37300.978138] RSP: 002b:7ffd61f7bd68 EFLAGS: 00010202 [37300.978141] RAX: 55e753ce7f70 RBX: RCX: [37300.978143] RDX: RSI: 7ffd61f7be30 RDI: 55e753bf0e70 [37300.978145] RBP: 7ffd61f7be00 R08: 55e753f51730 R09: 55e753f51730 [37300.978147] R10: 011c R11: ff21 R12: [37300.978149] R13: 55e753c89f90 R14: 55e753c89f70 R15: [37300.978152] Modules linked in: uas usb_storage usbhid rfcomm cmac algif_hash algif_skcipher af_alg bnep vboxnetadp(OE) vboxnetflt(OE) xfrm_user xfrm_algo vboxdrv(OE) l2tp_ppp l2tp_netlink l2tp_core ip6_udp_tunnel udp_tunnel pppox ccm joydev hid_multitouch hid_generic uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 ath3k videobuf2_common btusb rtsx_usb_ms btrtl btbcm btintel memstick bluetooth rtsx_usb_sdmmc videodev ecdh_generic mc ecc rtsx_usb snd_hda_codec_hdmi snd_soc_skl snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_soc_acpi snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation soundwire_cadence snd_hda_codec snd_hda_core snd_hwdep soundwire_bus snd_soc_core intel_rapl_msr snd_compress intel_rapl_common ac97_bus x86_pkg_temp_thermal snd_pcm_dmaengine intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel binfmt_misc snd_pcm [37300.978220] rapl intel_cstate snd_seq_midi snd_seq_midi_event intel_xhci_usb_role_switch mei_hdcp ath9k snd_rawmidi acer_wmi intel_wmi_thunderbolt at24 wmi_bmof ath9k_common sparse_keymap ath9k_hw ath nf_log_ipv4 snd_seq nf_log_common ipt_REJECT mac80211 snd_seq_device nf_reject_ipv4 xt_LOG snd_timer nls_iso8859_1 xt_multiport cfg80211 snd intel_lpss_pci i2c_i801 intel_lpss nft_limit mei_me xhci_pci idma64 i2c_smbus soundcore libarc4 intel_pch_thermal xhci_pci_renesas efi_pstore virt_dma mei i2c_hid hid xt_limit xt_addrtype xt_tcpudp wmi xt_conntrack acpi_pad nft_compat nft_counter nvidia_uvm(POE) nf_conntrack_netbios_ns
[Kernel-packages] [Bug 1942427] Re: [Lenovo Thunderbolt 3 Dock] Upgrade to 5.11.0-31-generic #33 breaks use of external displays with i915
The system now runs 5.11.0-34-generic which still has the bug. Looking in my /boot the oldest I have is 5.11.0-31-generic which introduced the bug as far as I can tell (thanks apt autoremove). I do however update whenever the thing prompts me to so I would venture a guess that whatever preceded 5.11.0-31 worked. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942427 Title: [Lenovo Thunderbolt 3 Dock] Upgrade to 5.11.0-31-generic #33 breaks use of external displays with i915 Status in linux package in Ubuntu: Incomplete Bug description: upgrading to latest packages, my setup with 3 displays (internal plus 2 external, plugged into Lenovo USB-c base station) no longer works. the Settings -> Displays app does find all displays, but the system only displays on the internal one. Attempting to enable all displays fails, the third disappears from view in the Displays app just before it presents the "Keep settings" dialog. However no output appears on any of the external displays other than the display's own firmware messages. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None Date: Thu Sep 2 10:54:09 2021 DistUpgraded: 2021-06-14 13:24:54,764 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-08-13 (384 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20L6S30S00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to hirsute on 2021-06-14 (79 days ago) dmi.bios.date: 08/10/2020 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET60W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L6S30S00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrN24ET60W(1.35):bd08/10/2020:br1.35:efr1.20:svnLENOVO:pn20L6S30S00:pvrThinkPadT480:rvnLENOVO:rn20L6S30S00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L6S30S00 dmi.product.sku: LENOVO_MT_20L6_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942427/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942952] Re: Kernel Call Trace on Secure Boot
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.14/amd64/ Headers are not needed. ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1942952 Title: Kernel Call Trace on Secure Boot Status in linux package in Ubuntu: Incomplete Bug description: Could the call traces in dmesg be related to UEFI secure boot? 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 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: js1 948 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Sep 7 21:05:54 2021 InstallationDate: Installed on 2021-09-06 (1 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:b00b Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/9p, 480M |__ Port 8: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 8: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-34-generic root=/dev/mapper/vgkubuntu-root ro ipv6.disable=1 elevator=deadline splash vt.handoff=7 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2021 dmi.bios.release: 15.63 dmi.bios.vendor: Insyde dmi.bios.version: F.63 dmi.board.name: 84B6 dmi.board.vendor: HP dmi.board.version: KBC Version 76.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 76.32 dmi.modalias: dmi:bvnInsyde:bvrF.63:bd03/25/2021:br15.63:efr76.32:svnHP:pn:pvr:sku:rvnHP:rn84B6:rvrKBCVersion76.32:cvnHP:ct10:cvrChassisVersion: dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942952/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942008] Re: Kubuntu 20.04.2 update causes shutdown corrupt bios, reboot hangs, won't wake from sleep
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.14/amd64/ Headers are not needed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942008 Title: Kubuntu 20.04.2 update causes shutdown corrupt bios, reboot hangs, won't wake from sleep Status in linux package in Ubuntu: Confirmed Bug description: Installed Kubuntu from the 20.04.2 LTS ISO. Shutdown, reboot, wake from sleep worked fine. Updates for 20.04.2 caused issues where it wouldn't wake from sleep, rebooting hangs, and never actually shutdowns for the reboot, and shutdown causes an audible hardware clicking noise (somewhere to the left side of the computer underneath the keyboard) and corrupts the BIOS. The corrupted BIOS causes the computer to not boot at all and I have to do a BIOS reset via CMOS (Hold the power button for 2-3 sec while pressing the WIN+v keys until it begins to boot). This gets more difficult each time it's done, where I have to wait longer before trying it and it seems to take longer to work. I have tried shutdown from the GUI menu, from the log- out menu, Konsole, and a TTY (CTRL+ALT+F2). I also have tried reinstalling a couple of times. Edit (also posted below): I made a post on a support site here: https://ubuntuforums.org/showthread.php?t=2466821. Even though this is clearly a bug in the 5.8+ kernels, updating to 5.11 and 20.04.3 still has this bug. The "solution" was to downgrade the kernel to 5.4, which is not a long-term solution. Hopefully, this bug will be resolved in future updates to the kernel. Computer specs: Host: HP Pavilion dv7-2180us Notebook PC Rev 1 Kernel: 5.8.0-59-generic Resolution: 1600x900 CPU: Intel Core 2 Quad Q9000 (4) @ 2.001GHz GPU: AMD ATI Mobility Radeon HD 4650/5165 Memory: 6 GB --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kah1382 F pulseaudio /dev/snd/controlC1: kah1382 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-18 (13 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=a99a5c85-bf23-4afe-b6aa-eb4f086dcbbb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-27-generic N/A linux-backports-modules-5.11.0-27-generic N/A linux-firmware 1.187.16 Tags: focal Uname: Linux 5.11.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2009 dmi.bios.release: 15.51 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.33 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3624 dmi.board.vendor: Quanta dmi.board.version: 18.42 dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.ec.firmware.release: 24.66 dmi.modalias: dmi:bvnHewlett-Packard:bvrF.33:bd08/31/2009:br15.51:efr24.66:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrRev1:rvnQuanta:rn3624:rvr18.42:cvnQuanta:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.sku: NV022UA#ABA dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942633] Re: Can not boot impish in Cavium ThunderX
5.14.0-9.9 exhibits kernel stack corruption on boot. ** Attachment added: "phanpy.bootlog" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942633/+attachment/5524292/+files/phanpy.bootlog -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942633 Title: Can not boot impish in Cavium ThunderX Status in linux package in Ubuntu: Confirmed Bug description: Hi I am trying to deploy a Impish server (Ubuntu 5.11.0-13.14-generic 5.11.7) in arm64 description: Computer product: Cavium ThunderX CN88XX board width: 64 bits I tried 2 releases: - 20210817 ( https://images.maas.io/ephemeral-v3/stable/impish/arm64/20210817/ga-21.10/ ) - 20210830 ( https://images.maas.io/ephemeral-v3/candidate/impish/arm64/20210830/ ) 20210817: Ends the deploy successfully but fails to boot from disk: ``` [0.00] Booting Linux on physical CPU 0x00 [0x431f0a11] [0.00] Linux version 5.13.0-14-generic (buildd@bos02-arm64-018) (gcc (Ubuntu 10.3.0-6ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.37) #14-Ubuntu SMP Mon Aug 2 12:40:58 UTC 2021 (Ubuntu 5.13.0-14.14-generic 5.13.1) [0.00] Machine model: Cavium ThunderX CN88XX board [ 139.896752] raid6: xor() 1224 MB/s, rmw enabled [ 139.957046] raid6: using neon recovery algorithm [ 140.020937] xor: measuring software checksum speed [ 140.085571]8regs : 2432 MB/sec [ 140.149834]32regs : 2687 MB/sec [ 140.212202]arm64_neon : 4390 MB/sec [ 140.271985] xor: using function: arm64_neon (4390 MB/sec) [ 140.335013] async_tx: api initialized (async) done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... [ 140.569847] Btrfs loaded, crc32c=crc32c-generic, zoned=yes Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... mdadm: No devices listed in conf file were found. done. mdadm: No devices listed in conf file were found. ``` 20210830 Fails the network boot: ``` [ 140.351066] async_tx: api initialized (async) done. Begin: Running /scripts/init-premount ... cloud-initramfs-dyn-netconf: did no find a nic with 1c:1b:0d:0d:52:7c done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Begin: Waiting up to 180 secs for BOOTIF to become available ... Failure: Interface BOOTIF did not appear in time done. ipconfig: BOOTIF: SIOCGIFINDEX: No such device ipconfig: no devices to configure ``` I will attach full logs of each try. JFYI, this is the same machine as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942427] Re: [Lenovo Thunderbolt 3 Dock] Upgrade to 5.11.0-31-generic #33 breaks use of external displays with i915
What was the last working kernel version? ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1942427 Title: [Lenovo Thunderbolt 3 Dock] Upgrade to 5.11.0-31-generic #33 breaks use of external displays with i915 Status in linux package in Ubuntu: Incomplete Bug description: upgrading to latest packages, my setup with 3 displays (internal plus 2 external, plugged into Lenovo USB-c base station) no longer works. the Settings -> Displays app does find all displays, but the system only displays on the internal one. Attempting to enable all displays fails, the third disappears from view in the Displays app just before it presents the "Keep settings" dialog. However no output appears on any of the external displays other than the display's own firmware messages. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None Date: Thu Sep 2 10:54:09 2021 DistUpgraded: 2021-06-14 13:24:54,764 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-08-13 (384 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20L6S30S00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to hirsute on 2021-06-14 (79 days ago) dmi.bios.date: 08/10/2020 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET60W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L6S30S00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrN24ET60W(1.35):bd08/10/2020:br1.35:efr1.20:svnLENOVO:pn20L6S30S00:pvrThinkPadT480:rvnLENOVO:rn20L6S30S00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L6S30S00 dmi.product.sku: LENOVO_MT_20L6_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942427/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943079] Re: Installing latest linux-firmware (1.187.16) causes wifi interface to disappear
So it's Intel AX210. Can you please also attach dmesg here? Thanks! -- 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/1943079 Title: Installing latest linux-firmware (1.187.16) causes wifi interface to disappear Status in linux-firmware package in Ubuntu: New Bug description: Summary === Installing linux-firmware 1.187.16, which became available on 17th Aug 2021, caused my wifi interface to disappear after reboot. My machine: Lenovo T15 Gen2 CPU: 11th Gen Intel(R) Core(TM) i7-1165G7 I tried force installing previous version 1.187.15, but that version isn't available! So, in the end, I rebooted into a live CD and re-installed the OS! In the newly installed OS, I just made sure to NOT select linux- firmware package in the list of available upgrades, and I will stick with version 1.187.15 till I have confidence there is better and working version. NOTE: On an older machine, with an older chipset, I did NOT experience this issue. Older machine: Lenovo x230 CPU: Intel(R) Core(TM) i5-3210M CPU Wifi: Centrino Advanced-N 6205 System == I'm running Linux Mint Edge, based on Ubuntu 20.04, but with upgraded kernel (5.11.0.34): lsb_release -rd Description: Linux Mint 20.2 Release: 20.2 Package === apt-cache policy linux-firmware linux-firmware: Installed: 1.187.16 Candidate: 1.187.16 Version table: *** 1.187.16 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages Expected Upgrade to linux-firmware=1.187.16 Reboot. Wifi network Interface must continue to be available and functioning. What Happened = Upgrade to linux-firmware=1.187.16 Reboot. Wifi network interface disappeared. Therefore, cannot use wifi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1943079/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942427] Re: [Lenovo Thunderbolt 3 Dock] Upgrade to 5.11.0-31-generic #33 breaks use of external displays with i915
I would urge you to reconsider the importance of this bug. This change broke a working setup, with no apparent user-visible workaround available. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942427 Title: [Lenovo Thunderbolt 3 Dock] Upgrade to 5.11.0-31-generic #33 breaks use of external displays with i915 Status in linux package in Ubuntu: Confirmed Bug description: upgrading to latest packages, my setup with 3 displays (internal plus 2 external, plugged into Lenovo USB-c base station) no longer works. the Settings -> Displays app does find all displays, but the system only displays on the internal one. Attempting to enable all displays fails, the third disappears from view in the Displays app just before it presents the "Keep settings" dialog. However no output appears on any of the external displays other than the display's own firmware messages. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None Date: Thu Sep 2 10:54:09 2021 DistUpgraded: 2021-06-14 13:24:54,764 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-08-13 (384 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20L6S30S00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to hirsute on 2021-06-14 (79 days ago) dmi.bios.date: 08/10/2020 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET60W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L6S30S00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrN24ET60W(1.35):bd08/10/2020:br1.35:efr1.20:svnLENOVO:pn20L6S30S00:pvrThinkPadT480:rvnLENOVO:rn20L6S30S00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L6S30S00 dmi.product.sku: LENOVO_MT_20L6_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942427/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
