[Kernel-packages] [Bug 1925739] Re: [Dell Vostro 3668] Strange sound when speaker is muted
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925739 Title: [Dell Vostro 3668] Strange sound when speaker is muted Status in linux package in Ubuntu: Expired Bug description: when everything is off even sound is muted I am getting sound like connecting 3.5mm jack. It's not sure why this sound is coming to my headphone. It's coming unevenly few seconds later. It's not case with ubuntu 20.10 usb stick. It begin when I upgrade pkgs. ubuntu 20.10 all updated. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bapi 1453 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-22 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.2-1ubuntu2.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Tags: groovy Uname: Linux 5.8.0-50-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: 09/30/2020 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.1 dmi.board.name: 0VFD52 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.1:bd09/30/2020:br1.14:svnDellInc.:pnVostro3668:pvr:rvnDellInc.:rn0VFD52:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3668 dmi.product.sku: 0760 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925739/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926974] Re: The graphics drivers ppa dropped the 32bit compat libs needed by steam
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926974 Title: The graphics drivers ppa dropped the 32bit compat libs needed by steam Status in linux package in Ubuntu: Expired Bug description: Steam doesn't start after installing nvidia-driver-465. It works with nvidia-driver-460, however. ``` Running Steam on linuxmint 20.1 64-bit STEAM_RUNTIME is enabled automatically Pins up-to-date! Steam client's requirements are satisfied WARNING: Using default/fallback debugger launch /home/cuysaurus/.steam/debian-installation/ubuntu12_32/steam -nominidumps -nobreakpad [2021-05-02 20:23:00] Startup - updater built Apr 12 2021 18:51:36 SteamUpdateUI: An X Error occurred X Error of failed request: GLXBadContext SteamUpdateUI: An X Error occurred X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 151 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 45 xerror_handler: X failed, continuing Major opcode of failed request: 151 (GLX) Minor opcode of failed request: 6 (X_GLXIsDirect) Serial number of failed request: 46 xerror_handler: X failed, continuing [2021-05-02 20:23:03] Using the following download hosts for Public, Realm steamglobal [2021-05-02 20:23:03] 1. https://cdn.cloudflare.steamstatic.com, /client/, Realm 'steamglobal', weight was 100, source = 'update_hosts_cached.vdf' [2021-05-02 20:23:03] 2. https://cdn.akamai.steamstatic.com, /client/, Realm 'steamglobal', weight was 100, source = 'update_hosts_cached.vdf' [2021-05-02 20:23:03] 3. http://media.steampowered.com, /client/, Realm 'steamglobal', weight was 1, source = 'baked in' [2021-05-02 20:23:03] Verifying installation... [2021-05-02 20:23:04] Verification complete ``` results from `apt policy libnvidia-gl-465 libnvidia-gl-465:i386`: ``` libnvidia-gl-465: Installed: 465.24.02-0ubuntu0~0.20.04.1 Candidate: 465.24.02-0ubuntu0~0.20.04.1 Version table: *** 465.24.02-0ubuntu0~0.20.04.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status libnvidia-gl-465:i386: Installed: (none) Candidate: (none) Version table: ``` results from `sudo apt install libnvidia-gl-465:i386`: ``` Reading package lists... Done Building dependency tree Reading state information... Done Package libnvidia-gl-465:i386 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: libnvidia-common-465 E: Package 'libnvidia-gl-465:i386' has no installation candidate ``` I would like to add that I tested a game outside steam and it works normally. I'm using Linux Mint 20.1 x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926974/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934548] Re: RISC-V: Illegal instruction
** Package changed: linux (Ubuntu) => linux-riscv (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1934548 Title: RISC-V: Illegal instruction Status in Ubuntu: New Status in linux-riscv package in Ubuntu: New Bug description: When booting the Ubuntu Server image on the SiFive HiFive Unmatched I am getting the following error. The last known working version was 1012. The issue is being tracked on the SiFive forums at https://forums.sifive.com/t/u-boot-says-unhandled-exception-illegal-instruction/4898 ``` Starting kernel ... [0.00] Linux version 5.11.0-1014-generic (buildd@riscv64-qemu-lcy01-084) (gcc (Ubuntu 10.3.0-1ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.36.1) #14-Ubuntu SMP Wed Jun 30 17:56:50 UTC 2021 (Ubuntu 5.11.0-1014.14-generic 5.11.22) [0.00] OF: fdt: Ignoring memory range 0x8000 - 0x8020 [0.00] earlycon: sifive0 at MMIO 0x1001 (options '') [0.00] printk: bootconsole [sifive0] enabled [0.00] efi: UEFI not found. [0.00] Initial ramdisk at: 0x(ptrval) (183422976 bytes) [0.00] cma: Reserved 32 MiB at 0xfe00 [0.00] Zone ranges: [0.00] DMA32[mem 0x8020-0x] [0.00] Normal [mem 0x0001-0x00047fff] [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x8020-0x00047fff] [0.00] Initmem setup node 0 [mem 0x8020-0x00047fff] [0.00] DMA32 zone: 512 pages in unavailable ranges [0.00] SBI specification v0.2 detected [0.00] SBI implementation ID=0x1 Version=0x9 [0.00] SBI v0.2 TIME extension detected [0.00] SBI v0.2 IPI extension detected [0.00] SBI v0.2 RFENCE extension detected [0.00] software IO TLB: mapped [mem 0xfa00-0xfe00] (64MB) [0.00] SBI v0.2 HSM extension detected [0.00] CPU with hartid=0 is not available [0.00] CPU with hartid=0 is not available [0.00] riscv: ISA extensions acdfim [0.00] riscv: ELF capabilities acdfim [0.00] percpu: Embedded 26 pages/cpu s69272 r8192 d29032 u106496 [0.00] Built 1 zonelists, mobility grouping on. Total pages: 4128264 [0.00] Kernel command line: root=/dev/nvme0n1p1 ro earlycon [0.00] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear) [0.00] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear) [0.00] Sorting __ex_table... [0.00] mem auto-init: stack:off, heap alloc:on, heap free:off [0.00] Memory: 16165452K/16775168K available (9854K kernel code, 5763K rwdata, 8192K rodata, 2519K init, 997K bss, 576948K reserved, 32768K cma-reserved) [0.00] random: get_random_u64 called from kmem_cache_open+0x36/0x338 with crng_init=0 [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [0.00] ftrace: allocating 38893 entries in 152 pages [0.00] Oops - illegal instruction [#1] [0.00] Modules linked in: [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 5.11.0-1014-generic #14-Ubuntu [0.00] epc: ffe0920e ra : ffe09384 sp : ffe001803d30 [0.00] gp : ffe001a14240 tp : ffe00180f440 t0 : ffe07fe38000 [0.00] t1 : ffe0019cd338 t2 : s0 : ffe001803d70 [0.00] s1 : a0 : ffe095aa a1 : 0001 [0.00] a2 : 0002 a3 : a4 : [0.00] a5 : a6 : 0004 a7 : 52464e43 [0.00] s2 : 0002 s3 : 0001 s4 : [0.00] s5 : s6 : s7 : [0.00] s8 : ffe001a170c0 s9 : 0001 s10: 0001 [0.00] s11: fffcc5d0 t3 : 0068 t4 : 000b [0.00] t5 : ffe0019cd3e0 t6 : ffe001803cd8 [0.00] status: 00020100 badaddr: 0513f187 cause: 0002 [0.00] ---[ end trace f67eb9af4d8d492b ]--- [0.00] Kernel panic - not syncing: Attempted to kill the idle task! [0.00] ---[ end Kernel panic - not syncing: Attempted to kill the idle task! ]--- ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1934548/+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 1786013] Autopkgtest regression report (linux-meta/5.4.0.79.82)
All autopkgtests for the newly accepted linux-meta (5.4.0.79.82) for focal have finished running. The following regressions have been reported in tests triggered by the package: systemd/245.4-4ubuntu3.7 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: 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 1934548] Re: RISC-V: Illegal instruction
** Project changed: charm-nrpe => linux-kernel-headers ** Also affects: ubuntu Importance: Undecided Status: New ** Tags added: sifive ** Tags added: rv64 rv64gc ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-kernel-headers -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934548 Title: RISC-V: Illegal instruction Status in Ubuntu: New Status in linux package in Ubuntu: New Bug description: When booting the Ubuntu Server image on the SiFive HiFive Unmatched I am getting the following error. The last known working version was 1012. The issue is being tracked on the SiFive forums at https://forums.sifive.com/t/u-boot-says-unhandled-exception-illegal-instruction/4898 ``` Starting kernel ... [0.00] Linux version 5.11.0-1014-generic (buildd@riscv64-qemu-lcy01-084) (gcc (Ubuntu 10.3.0-1ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.36.1) #14-Ubuntu SMP Wed Jun 30 17:56:50 UTC 2021 (Ubuntu 5.11.0-1014.14-generic 5.11.22) [0.00] OF: fdt: Ignoring memory range 0x8000 - 0x8020 [0.00] earlycon: sifive0 at MMIO 0x1001 (options '') [0.00] printk: bootconsole [sifive0] enabled [0.00] efi: UEFI not found. [0.00] Initial ramdisk at: 0x(ptrval) (183422976 bytes) [0.00] cma: Reserved 32 MiB at 0xfe00 [0.00] Zone ranges: [0.00] DMA32[mem 0x8020-0x] [0.00] Normal [mem 0x0001-0x00047fff] [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x8020-0x00047fff] [0.00] Initmem setup node 0 [mem 0x8020-0x00047fff] [0.00] DMA32 zone: 512 pages in unavailable ranges [0.00] SBI specification v0.2 detected [0.00] SBI implementation ID=0x1 Version=0x9 [0.00] SBI v0.2 TIME extension detected [0.00] SBI v0.2 IPI extension detected [0.00] SBI v0.2 RFENCE extension detected [0.00] software IO TLB: mapped [mem 0xfa00-0xfe00] (64MB) [0.00] SBI v0.2 HSM extension detected [0.00] CPU with hartid=0 is not available [0.00] CPU with hartid=0 is not available [0.00] riscv: ISA extensions acdfim [0.00] riscv: ELF capabilities acdfim [0.00] percpu: Embedded 26 pages/cpu s69272 r8192 d29032 u106496 [0.00] Built 1 zonelists, mobility grouping on. Total pages: 4128264 [0.00] Kernel command line: root=/dev/nvme0n1p1 ro earlycon [0.00] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear) [0.00] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear) [0.00] Sorting __ex_table... [0.00] mem auto-init: stack:off, heap alloc:on, heap free:off [0.00] Memory: 16165452K/16775168K available (9854K kernel code, 5763K rwdata, 8192K rodata, 2519K init, 997K bss, 576948K reserved, 32768K cma-reserved) [0.00] random: get_random_u64 called from kmem_cache_open+0x36/0x338 with crng_init=0 [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [0.00] ftrace: allocating 38893 entries in 152 pages [0.00] Oops - illegal instruction [#1] [0.00] Modules linked in: [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 5.11.0-1014-generic #14-Ubuntu [0.00] epc: ffe0920e ra : ffe09384 sp : ffe001803d30 [0.00] gp : ffe001a14240 tp : ffe00180f440 t0 : ffe07fe38000 [0.00] t1 : ffe0019cd338 t2 : s0 : ffe001803d70 [0.00] s1 : a0 : ffe095aa a1 : 0001 [0.00] a2 : 0002 a3 : a4 : [0.00] a5 : a6 : 0004 a7 : 52464e43 [0.00] s2 : 0002 s3 : 0001 s4 : [0.00] s5 : s6 : s7 : [0.00] s8 : ffe001a170c0 s9 : 0001 s10: 0001 [0.00] s11: fffcc5d0 t3 : 0068 t4 : 000b [0.00] t5 : ffe0019cd3e0 t6 : ffe001803cd8 [0.00] status: 00020100 badaddr: 0513f187 cause: 0002 [0.00] ---[ end trace f67eb9af4d8d492b ]--- [0.00] Kernel panic - not syncing: Attempted to kill the idle task! [0.00] ---[ end Kernel panic - not syncing: Attempted to kill the idle task! ]--- ``` To manage notifications about this bug go to:
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-bluefield/5.4.0.1015.16)
All autopkgtests for the newly accepted linux-meta-bluefield (5.4.0.1015.16) for focal have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/unknown (arm64) glibc/unknown (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-bluefield [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 1786013] Autopkgtest regression report (linux-meta-raspi/5.4.0.1040.75)
All autopkgtests for the newly accepted linux-meta-raspi (5.4.0.1040.75) for focal have finished running. The following regressions have been reported in tests triggered by the package: lttng-modules/unknown (arm64) iptables-netflow/unknown (arm64) mali-midgard/unknown (arm64) west-chamber/unknown (arm64) wireguard/unknown (arm64) glibc/unknown (arm64) adv-17v35x/unknown (arm64) xtables-addons/unknown (arm64) dm-writeboost/unknown (arm64) langford/unknown (arm64) dpdk/unknown (arm64) wireguard-linux-compat/unknown (arm64) r8168/unknown (arm64) jool/unknown (arm64) evdi/unknown (arm64) gost-crypto/unknown (arm64) v4l2loopback/unknown (arm64) zfs-linux/unknown (arm64) nat-rtsp/unknown (arm64) systemd/245.4-4ubuntu3.7 (arm64, armhf) glibc/2.31-0ubuntu9.2 (armhf) openrazer/unknown (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-raspi [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 1786013] Autopkgtest regression report (linux-meta-kvm/5.4.0.1043.41)
All autopkgtests for the newly accepted linux-meta-kvm (5.4.0.1043.41) for focal have finished running. The following regressions have been reported in tests triggered by the package: sl-modem/2.9.11~20110321-16ubuntu1 (amd64) v4l2loopback/0.12.3-1ubuntu0.4 (amd64) nvidia-graphics-drivers-450-server/450.119.04-0ubuntu0.20.04.2 (amd64) rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.2 (amd64) nvidia-graphics-drivers-460/460.80-0ubuntu0.20.04.2 (amd64) virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (amd64) virtualbox/6.1.16-dfsg-6~ubuntu1.20.04.2 (amd64) evdi/1.7.0+dfsg-1ubuntu1~20.04.3 (amd64) lttng-modules/2.12.2-1ubuntu1~20.04.2 (amd64) oss4/4.2-build2010-5ubuntu6~20.04.2 (amd64) glibc/2.31-0ubuntu9.2 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 (amd64) nvidia-graphics-drivers-460-server/460.73.01-0ubuntu0.20.04.1 (amd64) backport-iwlwifi-dkms/8324-0ubuntu3~20.04.3 (amd64) rtl8821ce/5.5.2.1-0ubuntu4~20.04.3 (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-kvm [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 1931584] Re: PKA: Fix NULL pointer kfree() issue
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- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1931584 Title: PKA: Fix NULL pointer kfree() issue Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] * Should not free NULL pointer. If the pointer is NULL as a result of memory allocation (kmalloc()), only return an error code and don't free (kfree()) a NULL pointer. Even though kfree() won't perform any operation if NULL is passed, this is not a good practice. [Fix] * Don't free NULL pointer "pka: Fix NULL pointer kfree() issue" [Test Case] * No change in functionality. [Regression Potential] * Regression can be considered very low as the pointer won't be kfree()'d only in the case of it being NULL. This is functionally equivalent to passing NULL pointer to kfree() as no operation will be performed in this case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1931584/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932042] Re: Change CONFIG_NF_CONNTRACK to y
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- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1932042 Title: Change CONFIG_NF_CONNTRACK to y Status in linux-bluefield package in Ubuntu: In Progress Status in linux-bluefield source package in Focal: Fix Committed Bug description: == Impact == NVIDIA would like to have CONFIG_NF_CONNTRACK as y instead of m. == Fix == CONFIG_NF_CONNTRACK=y The feature is already enabled as a module. Since it would always get loaded because they would enable firewall by default, changing it to builtin shouldn't make any harm. == Risk of Regression == Low. This is already enabled as a module. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1932042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932035] Re: Enable features for supporting PXE installer
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- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1932035 Title: Enable features for supporting PXE installer Status in linux-bluefield package in Ubuntu: In Progress Status in linux-bluefield source package in Focal: Fix Committed Bug description: == Impact == The PXE installer requires some features available in order to run. == Fix == * CONFIG_ISO9660_FS=m * CONFIG_BCACHE=m * enable zfs == Risk of Regression == Low. These features are also enabled in the generic kernel for arm64, and has been tested on the target platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1932035/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932065] Re: Upstream v5.9 introduced 'module' patches that removed exported symbols
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- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1932065 Title: Upstream v5.9 introduced 'module' patches that removed exported symbols Status in linux package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Bug description: SRU Justification: [Impact] * The following patches removed an exported symbol that will cause potential disruption and breakage for customers modules: inherit TAINT_PROPRIETARY_MODULE modules: return licensing information from find_symbol modules: rename the licence field in struct symsearch to license modules: unexport __module_address modules: unexport __module_text_address modules: mark each_symbol_section static modules: mark find_symbol static modules: mark ref_module static [Fix] * Temporarily revert as SAUCE patches to allow customers time to make necessary changes to support eventual patch changes. [Test Plan] * none [Where problems could occur] * The new functionality provided by patches will be removed, since we aren't removing existing functionality the risk should be low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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-raspi/5.4.0.1039.74)
All autopkgtests for the newly accepted linux-meta-raspi (5.4.0.1039.74) for focal have finished running. The following regressions have been reported in tests triggered by the package: dpdk/unknown (arm64) r8168/unknown (arm64) lime-forensics/unknown (arm64) langford/unknown (arm64) gost-crypto/unknown (arm64) systemd/unknown (arm64) mali-midgard/unknown (arm64) wireguard/unknown (arm64) nat-rtsp/unknown (arm64) evdi/unknown (arm64) systemd/245.4-4ubuntu3.7 (armhf) wireguard-linux-compat/unknown (arm64) iptables-netflow/unknown (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-raspi [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 1934414] Re: test_bpf.sh from ubuntu_kernel_selftests.net from linux ADT test failure with linux/4.15.0-149.153
So, test_bpf is not doing either conversion and any other use on the kernel should either be using something like sk_attach*, bpf_prog_create*, or just using a fd that was created from BPF_PROG_LOAD. Any user that accepts BPF programs without those checks are up to cause issues worse than a simple div-by-zero. So far, I could not find any such user by code inspection. I also tested that a SO_ATTACH_FILTER (classic BPF) that does a div-by- zero behaves the same way on 4.15.0-145, 4.15.0-147 and 4.15.0-149, that is, the program will have an "exception", which means it returns 0. With sockets, this means the packet is dropped. That is expected behavior. Marking this bug priority as low as a result. Cascardo. ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934414 Title: test_bpf.sh from ubuntu_kernel_selftests.net from linux ADT test failure with linux/4.15.0-149.153 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/4.15.0-149.153 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: i386: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/l/linux/20210702_010055_445cd@/log.gz 03:37:02 DEBUG| [stdout] selftests: test_bpf.sh 03:37:02 DEBUG| [stdout] 03:37:03 ERROR| [stderr] Segmentation fault 03:37:03 DEBUG| [stdout] test_bpf: [FAIL] 03:37:03 DEBUG| [stdout] not ok 1..8 selftests: test_bpf.sh [FAIL] 03:37:03 DEBUG| [stdout] selftests: netdevice.sh 03:37:03 DEBUG| [stdout] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934414/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934538] [NEW] Package linux-modules-nvidia-460-5.8.0-59-generic not included in kernel 5.8.0-59-generic upgrade
Public bug reported: Description:Ubuntu 20.04.2 LTS Release:20.04 linux-modules-nvidia-460-5.8.0-59-generic: Installed: 5.8.0-59.66~20.04.1 Candidate: 5.8.0-59.66~20.04.1 Version table: *** 5.8.0-59.66~20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages 100 /var/lib/dpkg/status During the upgrade to the 5.8.0-59-generic kernel in Ubuntu 20.04, apt showed an upgrade to the NVIDIA 460 driver as withheld. Proceeding with the 5.8.0-59-generic upgrade breaks the installed NVIDIA 460 driver and causes the Nouveau driver to load after reboot. Manually installing package linux-modules-nvidia-460-5.8.0-59-generic allows the updated NVIDIA 460.80 driver to complete installation and makes the Ubuntu 20.04 installation whole and completely up-to-date again after a subsequent reboot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-nvidia-460-5.8.0-59-generic 5.8.0-59.66~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 2 15:04:08 2021 InstallationDate: Installed on 2021-02-21 (131 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-restricted-modules-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-restricted-modules-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1934538 Title: Package linux-modules-nvidia-460-5.8.0-59-generic not included in kernel 5.8.0-59-generic upgrade Status in linux-restricted-modules-hwe-5.8 package in Ubuntu: New Bug description: Description: Ubuntu 20.04.2 LTS Release: 20.04 linux-modules-nvidia-460-5.8.0-59-generic: Installed: 5.8.0-59.66~20.04.1 Candidate: 5.8.0-59.66~20.04.1 Version table: *** 5.8.0-59.66~20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages 100 /var/lib/dpkg/status During the upgrade to the 5.8.0-59-generic kernel in Ubuntu 20.04, apt showed an upgrade to the NVIDIA 460 driver as withheld. Proceeding with the 5.8.0-59-generic upgrade breaks the installed NVIDIA 460 driver and causes the Nouveau driver to load after reboot. Manually installing package linux-modules-nvidia-460-5.8.0-59-generic allows the updated NVIDIA 460.80 driver to complete installation and makes the Ubuntu 20.04 installation whole and completely up-to-date again after a subsequent reboot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-nvidia-460-5.8.0-59-generic 5.8.0-59.66~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 2 15:04:08 2021 InstallationDate: Installed on 2021-02-21 (131 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-restricted-modules-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.8/+bug/1934538/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934537] [NEW] package linux-image-5.11.0-22-generic 5.11.0-22.23 failed to install/upgrade: Auf das Archiv »/tmp/apt-dpkg-install-NSQLwt/53-linux-image-5.11.0-22-generic_5.11.0
Public bug reported: package linux-image-5.11.0-22-generic 5.11.0-22.23 failed to install/upgrade: Auf das Archiv »/tmp/apt-dpkg-install-NSQLwt/53-linux- image-5.11.0-22-generic_5.11.0-22.23_amd64.deb« kann nicht zugegriffen werden: Datei oder Verzeichnis nicht gefunden ProblemType: Package DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-22-generic 5.11.0-22.23 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2058 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 Date: Thu Jul 1 21:03:22 2021 ErrorMessage: Auf das Archiv »/tmp/apt-dpkg-install-NSQLwt/53-linux-image-5.11.0-22-generic_5.11.0-22.23_amd64.deb« kann nicht zugegriffen werden: Datei oder Verzeichnis nicht gefunden LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20KH006DGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz persistent file=/cdrom/preseed/hostname.seed quiet splash --- PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu45 SourcePackage: linux Title: package linux-image-5.11.0-22-generic 5.11.0-22.23 failed to install/upgrade: Auf das Archiv »/tmp/apt-dpkg-install-NSQLwt/53-linux-image-5.11.0-22-generic_5.11.0-22.23_amd64.deb« kann nicht zugegriffen werden: Datei oder Verzeichnis nicht gefunden UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET76W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006DGE 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.22 dmi.modalias: dmi:bvnLENOVO:bvrN23ET76W(1.51):bd04/21/2021:br1.51:efr1.22:svnLENOVO:pn20KH006DGE:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KH006DGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KH006DGE dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package 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/1934537 Title: package linux-image-5.11.0-22-generic 5.11.0-22.23 failed to install/upgrade: Auf das Archiv »/tmp/apt-dpkg-install-NSQLwt/53 -linux-image-5.11.0-22-generic_5.11.0-22.23_amd64.deb« kann nicht zugegriffen werden: Datei oder Verzeichnis nicht gefunden Status in linux package in Ubuntu: New Bug description: package linux-image-5.11.0-22-generic 5.11.0-22.23 failed to install/upgrade: Auf das Archiv »/tmp/apt-dpkg-install-NSQLwt/53 -linux-image-5.11.0-22-generic_5.11.0-22.23_amd64.deb« kann nicht zugegriffen werden: Datei oder Verzeichnis nicht gefunden ProblemType: Package DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-22-generic 5.11.0-22.23 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2058 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 Date: Thu Jul 1 21:03:22 2021 ErrorMessage: Auf das Archiv »/tmp/apt-dpkg-install-NSQLwt/53-linux-image-5.11.0-22-generic_5.11.0-22.23_amd64.deb« kann nicht zugegriffen werden: Datei oder Verzeichnis nicht gefunden LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20KH006DGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz persistent file=/cdrom/preseed/hostname.seed quiet splash --- PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu45 SourcePackage: linux Title: package linux-image-5.11.0-22-generic 5.11.0-22.23 failed to install/upgrade: Auf das Archiv »/tmp/apt-dpkg-install-NSQLwt/53-linux-image-5.11.0-22-generic_5.11.0-22.23_amd64.deb« kann nicht zugegriffen werden: Datei oder Verzeichnis nicht gefunden UpgradeStatus: No upgrade log
[Kernel-packages] [Bug 1934535] [NEW] package linux-modules-extra-5.11.0-22-generic 5.11.0-22.23 failed to install/upgrade: Auf das Archiv »/tmp/apt-dpkg-install-NSQLwt/54-linux-modules-extra-5.11.0-2
Public bug reported: package linux-modules-extra-5.11.0-22-generic 5.11.0-22.23 failed to install/upgrade: Auf das Archiv »/tmp/apt-dpkg-install-NSQLwt/54-linux- modules-extra-5.11.0-22-generic_5.11.0-22.23_amd64.deb« kann nicht zugegriffen werden: Datei oder Verzeichnis nicht gefunden ProblemType: Package DistroRelease: Ubuntu 21.04 Package: linux-modules-extra-5.11.0-22-generic 5.11.0-22.23 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2058 F pulseaudio CasperVersion: 1.461 Date: Thu Jul 1 21:03:22 2021 ErrorMessage: Auf das Archiv »/tmp/apt-dpkg-install-NSQLwt/54-linux-modules-extra-5.11.0-22-generic_5.11.0-22.23_amd64.deb« kann nicht zugegriffen werden: Datei oder Verzeichnis nicht gefunden LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20KH006DGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz persistent file=/cdrom/preseed/hostname.seed quiet splash --- PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu45 SourcePackage: linux Title: package linux-modules-extra-5.11.0-22-generic 5.11.0-22.23 failed to install/upgrade: Auf das Archiv »/tmp/apt-dpkg-install-NSQLwt/54-linux-modules-extra-5.11.0-22-generic_5.11.0-22.23_amd64.deb« kann nicht zugegriffen werden: Datei oder Verzeichnis nicht gefunden UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET76W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006DGE 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.22 dmi.modalias: dmi:bvnLENOVO:bvrN23ET76W(1.51):bd04/21/2021:br1.51:efr1.22:svnLENOVO:pn20KH006DGE:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KH006DGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KH006DGE dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package 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/1934535 Title: package linux-modules-extra-5.11.0-22-generic 5.11.0-22.23 failed to install/upgrade: Auf das Archiv »/tmp/apt-dpkg-install-NSQLwt/54 -linux-modules-extra-5.11.0-22-generic_5.11.0-22.23_amd64.deb« kann nicht zugegriffen werden: Datei oder Verzeichnis nicht gefunden Status in linux package in Ubuntu: New Bug description: package linux-modules-extra-5.11.0-22-generic 5.11.0-22.23 failed to install/upgrade: Auf das Archiv »/tmp/apt-dpkg-install-NSQLwt/54 -linux-modules-extra-5.11.0-22-generic_5.11.0-22.23_amd64.deb« kann nicht zugegriffen werden: Datei oder Verzeichnis nicht gefunden ProblemType: Package DistroRelease: Ubuntu 21.04 Package: linux-modules-extra-5.11.0-22-generic 5.11.0-22.23 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2058 F pulseaudio CasperVersion: 1.461 Date: Thu Jul 1 21:03:22 2021 ErrorMessage: Auf das Archiv »/tmp/apt-dpkg-install-NSQLwt/54-linux-modules-extra-5.11.0-22-generic_5.11.0-22.23_amd64.deb« kann nicht zugegriffen werden: Datei oder Verzeichnis nicht gefunden LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20KH006DGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz persistent file=/cdrom/preseed/hostname.seed quiet splash --- PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu45 SourcePackage: linux Title: package linux-modules-extra-5.11.0-22-generic 5.11.0-22.23 failed to install/upgrade: Auf das Archiv »/tmp/apt-dpkg-install-NSQLwt/54-linux-modules-extra-5.11.0-22-generic_5.11.0-22.23_amd64.deb« kann nicht zugegriffen werden: Datei oder
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-raspi/5.8.0.1031.33)
All autopkgtests for the newly accepted linux-meta-raspi (5.8.0.1031.33) for groovy have finished running. The following regressions have been reported in tests triggered by the package: ddcci-driver-linux/unknown (arm64) v4l2loopback/unknown (arm64) xtables-addons/unknown (arm64) snapd/unknown (arm64) langford/unknown (arm64) acpi-call/unknown (arm64) backport-iwlwifi-dkms/unknown (arm64) iptables-netflow/unknown (arm64) gost-crypto/unknown (arm64) systemd/unknown (arm64) rtl8821ce/unknown (arm64) dpdk/unknown (arm64) zfs-linux/unknown (arm64) wireguard-linux-compat/unknown (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/groovy/update_excuses.html#linux-meta-raspi [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 1934414] Re: test_bpf.sh from ubuntu_kernel_selftests.net from linux ADT test failure with linux/4.15.0-149.153
This comes from the BPF changes done on 4.15.0-147. i386 uses the interpreter, while other arches have JIT. The JIT cannot be disabled on the arches that support it and have CONFIG_BPF_JIT_ALWAYS_ON, which is our default. The interpreter change that causes this has been identified. It doesn't check that the source register is zero anymore, relying on either eBPF fixup_bpf_calls or classic BPF bpf_convert_filter doing the job of testing for it. The test_bpf module, though, does not go through any of these conversions, which leads to the test failure. Partial revert of the interpreter changes would fix it up. We have yet to determine if any other legitimate path for either eBPF or cBPF will skip any of these conversions. If none do, we may leave this for a later cycle. Cascardo. ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (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/1934414 Title: test_bpf.sh from ubuntu_kernel_selftests.net from linux ADT test failure with linux/4.15.0-149.153 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/4.15.0-149.153 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: i386: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/l/linux/20210702_010055_445cd@/log.gz 03:37:02 DEBUG| [stdout] selftests: test_bpf.sh 03:37:02 DEBUG| [stdout] 03:37:03 ERROR| [stderr] Segmentation fault 03:37:03 DEBUG| [stdout] test_bpf: [FAIL] 03:37:03 DEBUG| [stdout] not ok 1..8 selftests: test_bpf.sh [FAIL] 03:37:03 DEBUG| [stdout] selftests: netdevice.sh 03:37:03 DEBUG| [stdout] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934414/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Might work. But I'm not sure of this setting can be done while doing a PXE boot. -- 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 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/ubuntu/+source/linux-oem-5.10/+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 1835660] Re: initramfs unpacking failed
#134: @xnox, have you re-sent it? It looks like https://lkml.org/lkml/2021/1/14/1091 got no feedback. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in grub2 source package in Focal: Invalid Status in initramfs-tools source package in Focal: Invalid Status in linux source package in Focal: Fix Released Status in grub2 source package in Groovy: Invalid Status in initramfs-tools source package in Groovy: Invalid Status in linux source package in Groovy: Fix Released Status in grub2 source package in Hirsute: Invalid Status in initramfs-tools source package in Hirsute: Invalid Status in linux source package in Hirsute: Fix Released Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. [Impact] * Decoding failure messages in dmsg with a single lz4 initrd * Multiple lz4 compressed initrds cannot be decompressed by kernel, when loaded by grub * Multiple lz4 compressed initrds cannot be decompressed by kernel, when there is padding between them [Test Case] * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4 * Create an lz4 compressed initrd with a single test-file in it with some content. I.e. echo "second-initrd" > test-file, and then pack that with cpio hewc owned by root & lz4 -l. * Create a combined padded initrd of stock initrd, pad4, and the test-marker initrd created above. * Boot above with "break=top" kernel command line. * With broken kernels, there should be dmesg error message that decoding failed, and one will observe that /test-file does not exist in the shell. * With fixed kernel, /test-file in the initrd shell should exist, and should have the expected content "second-initrd". * The alignment and padding in the above test case depends on the size of the first initrd => if a given padded initrd does not reproduce the problem, try varying the size of the first initrd or that of the padding between 0..4. [Where problems could occur] * This changes compatible lz4 decompressor in the kernel, which can also be used by other kernel modules such as cryptography, squashfs, zram, f2fs, comprssed kernel image, pstore. For example, previously rejected files with "bogus" length and extra padding may now be accepted, whereas they were previously getting rejected by the decompressor. * Ideally kernel should switch to the stable lz4 format which has better specification of end of stream. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934489] Re: Make Intel GPUs choose YCbCr420 encoding automatically when required for 4k 60Hz output
The bug still exists on 5.11. The Patchset just got merged after the 5.13 mainline release, so in mainline it will be in 5.14 onwards. ** Description changed: SRU Justification: Impact: On some setups, while the monitor and the GPU support display modes with pixel clocks of up to 600MHz, the connector might not. This prevents RGB encoding for 4k60Hz, but YCbCr420 encoding might still be possible. However, which color mode is used is decided before the pixel clock capabilities are checked, causing the check to fail and discarding 4k60Hz from the list of possible display modes. Fix: This patch fixes the problem by retrying to find a display mode with YCbCr420 enforced and using it, if it is valid. It's very similar to a patch submitted to amdgpu which fixed the same problem. Testcase: Find a PC with a current Intel iGPU, but only a hdmi 1.4 output. Connect a 4k@60Hz display supporting YCbCr420 encoding to the hdmi port. Without the patch the maximum that can be set via xrandr is 3840 × 2160 30Hz. With the Patch 3840 × 2160 60Hz can be selected which will use YCbCr420 automatically. + Prerequistie: + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3c4442aa22878091f16c8d9592f5f5b6a94d1556 + Patchset already got accepted upstream and reached the torvalds tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eacba74d4d561ea6487d944417526e1b025cbebd https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=84d95f77f4aea3f22a486cd04777afd4ab0f0ea5 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=388b863509f76f6a5ecedd7ffdaf184aa813241e and needs only a minor modifications to apply to ubuntu-focal/hwe-5.8 Commit-hashes: + 3c4442aa22878091f16c8d9592f5f5b6a94d1556 eacba74d4d561ea6487d944417526e1b025cbebd 84d95f77f4aea3f22a486cd04777afd4ab0f0ea5 388b863509f76f6a5ecedd7ffdaf184aa813241e -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934489 Title: Make Intel GPUs choose YCbCr420 encoding automatically when required for 4k 60Hz output Status in linux package in Ubuntu: New Bug description: SRU Justification: Impact: On some setups, while the monitor and the GPU support display modes with pixel clocks of up to 600MHz, the connector might not. This prevents RGB encoding for 4k60Hz, but YCbCr420 encoding might still be possible. However, which color mode is used is decided before the pixel clock capabilities are checked, causing the check to fail and discarding 4k60Hz from the list of possible display modes. Fix: This patch fixes the problem by retrying to find a display mode with YCbCr420 enforced and using it, if it is valid. It's very similar to a patch submitted to amdgpu which fixed the same problem. Testcase: Find a PC with a current Intel iGPU, but only a hdmi 1.4 output. Connect a 4k@60Hz display supporting YCbCr420 encoding to the hdmi port. Without the patch the maximum that can be set via xrandr is 3840 × 2160 30Hz. With the Patch 3840 × 2160 60Hz can be selected which will use YCbCr420 automatically. Prerequistie: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3c4442aa22878091f16c8d9592f5f5b6a94d1556 Patchset already got accepted upstream and reached the torvalds tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eacba74d4d561ea6487d944417526e1b025cbebd https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=84d95f77f4aea3f22a486cd04777afd4ab0f0ea5 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=388b863509f76f6a5ecedd7ffdaf184aa813241e and needs only a minor modifications to apply to ubuntu-focal/hwe-5.8 Commit-hashes: 3c4442aa22878091f16c8d9592f5f5b6a94d1556 eacba74d4d561ea6487d944417526e1b025cbebd 84d95f77f4aea3f22a486cd04777afd4ab0f0ea5 388b863509f76f6a5ecedd7ffdaf184aa813241e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934112] Re: Intel 100G nic get call trace for sosreport on focal ga-kenel
Can this be recreated without sosreport? e.g. can the call traces be created simply by running something like sudo ethtool /dev/DEVICE Also, which 100Gb NIC is this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934112 Title: Intel 100G nic get call trace for sosreport on focal ga-kenel Status in linux package in Ubuntu: New Bug description: On Asus Server, when it run "sosreport -a" to the network step, the console would print below call trace and the 100G Nic port became unreachable. call trace on ga-kernel ( v5.4): https://paste.ubuntu.com/p/TC5Jn6hYGF/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934414] Re: test_bpf.sh from ubuntu_kernel_selftests.net from linux ADT test failure with linux/4.15.0-149.153
Dmesg error is: [ 157.476410] test_bpf: #48 INT: ALU MIX jited:0 167 PASS [ 157.482773] test_bpf: #49 INT: shifts by register jited:0 317 PASS [ 157.488472] test_bpf: #50 INT: DIV + ABS jited:0 103 140 PASS [ 157.495519] test_bpf: #51 INT: DIV by zero jited:0 74 [ 157.496424] divide error: [#1] SMP PTI ** Attachment added: "bpf-dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934414/+attachment/5508648/+files/bpf-dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934414 Title: test_bpf.sh from ubuntu_kernel_selftests.net from linux ADT test failure with linux/4.15.0-149.153 Status in linux package in Ubuntu: New Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/4.15.0-149.153 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: i386: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/l/linux/20210702_010055_445cd@/log.gz 03:37:02 DEBUG| [stdout] selftests: test_bpf.sh 03:37:02 DEBUG| [stdout] 03:37:03 ERROR| [stderr] Segmentation fault 03:37:03 DEBUG| [stdout] test_bpf: [FAIL] 03:37:03 DEBUG| [stdout] not ok 1..8 selftests: test_bpf.sh [FAIL] 03:37:03 DEBUG| [stdout] selftests: netdevice.sh 03:37:03 DEBUG| [stdout] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934414/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932168] Re: oss4/4.2-build2010-5ubuntu6~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
** Changed in: oss4 (Ubuntu) Status: New => Invalid -- 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/1932168 Title: oss4/4.2-build2010-5ubuntu6~20.04.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: New Status in oss4 package in Ubuntu: Invalid Status in linux-hwe-5.11 source package in Focal: New Status in oss4 source package in Focal: Fix Committed Bug description: [Impact] oss4 dkms will fail to build on 5.11 kernels on focal, preventing users from using those modules on more recent kernels. [Test case] Install the package and make sure it builds. [Fix] Conditionally define a function that is not used on the Linux port when LICENSED_VERSION is undefined. [Fix risk] Licensed versions will fail to build, but we don't do those. Other ports should not fail as we only patch the Linux port. [Potential regression] The dkms package may still fail to build, install or load. Or sound might not work on systems that depend on oss4. --- This is a scripted bug report about ADT failures while running oss4 tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/o/oss4/20210611_210018_1dcc5@/log.gz [Other] NB! dkms ftbfs fixes must be built in security, such that after SRU process in -proposed & -updates it can be copied into -security pocket too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1932168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932168] Re: oss4/4.2-build2010-5ubuntu6~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Hello Kleber, or anyone else affected, Accepted oss4 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/oss4/4.2-build2010-5ubuntu6~20.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: oss4 (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- 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/1932168 Title: oss4/4.2-build2010-5ubuntu6~20.04.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: New Status in oss4 package in Ubuntu: New Status in linux-hwe-5.11 source package in Focal: New Status in oss4 source package in Focal: Fix Committed Bug description: [Impact] oss4 dkms will fail to build on 5.11 kernels on focal, preventing users from using those modules on more recent kernels. [Test case] Install the package and make sure it builds. [Fix] Conditionally define a function that is not used on the Linux port when LICENSED_VERSION is undefined. [Fix risk] Licensed versions will fail to build, but we don't do those. Other ports should not fail as we only patch the Linux port. [Potential regression] The dkms package may still fail to build, install or load. Or sound might not work on systems that depend on oss4. --- This is a scripted bug report about ADT failures while running oss4 tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/o/oss4/20210611_210018_1dcc5@/log.gz [Other] NB! dkms ftbfs fixes must be built in security, such that after SRU process in -proposed & -updates it can be copied into -security pocket too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1932168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931677] Re: [SRU][F/G/H][linux-firmware] add realtek 8852a wifi fimware
verification needed for hirsute ** Tags added: verification-needed-hirsute -- 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/1931677 Title: [SRU][F/G/H][linux-firmware] add realtek 8852a wifi fimware Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Groovy: Fix Released Status in linux-firmware source package in Hirsute: Fix Committed Bug description: [Impact] Realtek 8852A wifi can not work without proper firmware. [Fix] Add realtek 8852a wifi firmware for driver. Kernel driver will be in another SRU. [Test] Verified on hardware with wifi ap, connect with 2.4G/5G, all good. [Where problems could occur] It should be low risk for adding fw for specfic hardware chip. Hirsute already got it, only SRU fw for F/G. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1931677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929831] Re: cifs: On cifs_reconnect, resolve the hostname again
Latest version of the patch set with additional fixes from upstream: https://lists.ubuntu.com/archives/kernel-team/2021-June/121485.html -- 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/1929831 Title: cifs: On cifs_reconnect, resolve the hostname again Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: New Status in linux source package in Focal: In Progress Status in linux-azure source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Status in linux-azure source package in Groovy: In Progress Bug description: SRU Justification [Impact] The Microsoft CIFS team is requesting below patch to be backported for 5.4 Azure tuned kernel https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4e456b30f78c429b183db420e23b26cde7e03a78 A customer is encountering the bug fixed by this patch. [Fix] 7d397a034d5c45528c7bdf7fc3752c4793029cce cifs: rename reconn_inval_dfs_target() 7d6535b720421d58886d5590ffc3617d359aa871 cifs: Simplify reconnect code when dfs upcall is enabled 4e456b30f78c429b183db420e23b26cde7e03a78 cifs: On cifs_reconnect, resolve the hostname again. The first 2 patches are scaffolding to make the backport simpler. the 3rd patch is the bug fix. [Test Plan] The test kernel at https://launchpad.net/~timg-tpi/+archive/ubuntu /cifs-reconnect-sf00309672 has been found to fix the issue. [Where problems could occur] This could perturb CIFS connections in new and different ways. [Other Info] https://canonical.my.salesforce.com/5004K05pQNG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929831/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934499] Re: New BPF helpers to query conntrack and to generate/validate SYN cookies
** Description changed: Ticket for the patch series that adds new BPF helpers to query conntrack and to generate SYN cookies for forwarded connections. + + * Explain the bug(s) + + This patch series aims to accelerate iptables synproxy module with XDP. + The stage that generates and checks SYN cookies is stateless and can be + implemented in XDP. + + * Brief explanation of fixes + + This patch series adds new BPF helpers: + + * bpf_ct_lookup_tcp to lookup CT status of a TCP connection. + + * bpf_tcp_raw_gen_syncookie to generate SYN cookies without a listening + socket on the same host (to be used with iptables synproxy module). + + * bpf_tcp_raw_check_syncookie to check SYN cookies generated by the + previos helper (to be used with iptables synproxy module). + + * bpf_tcp_raw_gen_tscookie to generate timestamp cookies, which encode + additional information like SACK permission, ECN support, window scale. + The format is compatible with iptables synproxy module. + + These new helpers allow to accelerate the iptables synproxy module. This + series also includes some dependency patches backported from upstream. + + * How to test + + Use an XDP application that generates and checks SYN cookies, leveraging + the new helpers. + + * What it could break. + + Nothing should be broken, only new functionality is added, and some + patches are backported from upstream. CONFIG_NF_CONNTRACK is changed + from m to y, which is also not expected to break existing functionality. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1934499 Title: New BPF helpers to query conntrack and to generate/validate SYN cookies Status in linux-bluefield package in Ubuntu: New Bug description: Ticket for the patch series that adds new BPF helpers to query conntrack and to generate SYN cookies for forwarded connections. * Explain the bug(s) This patch series aims to accelerate iptables synproxy module with XDP. The stage that generates and checks SYN cookies is stateless and can be implemented in XDP. * Brief explanation of fixes This patch series adds new BPF helpers: * bpf_ct_lookup_tcp to lookup CT status of a TCP connection. * bpf_tcp_raw_gen_syncookie to generate SYN cookies without a listening socket on the same host (to be used with iptables synproxy module). * bpf_tcp_raw_check_syncookie to check SYN cookies generated by the previos helper (to be used with iptables synproxy module). * bpf_tcp_raw_gen_tscookie to generate timestamp cookies, which encode additional information like SACK permission, ECN support, window scale. The format is compatible with iptables synproxy module. These new helpers allow to accelerate the iptables synproxy module. This series also includes some dependency patches backported from upstream. * How to test Use an XDP application that generates and checks SYN cookies, leveraging the new helpers. * What it could break. Nothing should be broken, only new functionality is added, and some patches are backported from upstream. CONFIG_NF_CONNTRACK is changed from m to y, which is also not expected to break existing functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1934499/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
sudo ethtool -C rx-usecs 6000 (replace with the name of your network card) -- 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 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/ubuntu/+source/linux-oem-5.10/+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 1934499] [NEW] New BPF helpers to query conntrack and to generate/validate SYN cookies
Public bug reported: Ticket for the patch series that adds new BPF helpers to query conntrack and to generate SYN cookies for forwarded connections. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1934499 Title: New BPF helpers to query conntrack and to generate/validate SYN cookies Status in linux-bluefield package in Ubuntu: New Bug description: Ticket for the patch series that adds new BPF helpers to query conntrack and to generate SYN cookies for forwarded connections. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1934499/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934489] Re: Make Intel GPUs choose YCbCr420 encoding automatically when required for 4k 60Hz output
I'm currently resolving the minor merge conflict with ubuntu-5.8 kernel and then test it ** Description changed: SRU Justification: Impact: On some setups, while the monitor and the GPU support display modes with pixel clocks of up to 600MHz, the connector might not. This prevents RGB encoding for 4k60Hz, but YCbCr420 encoding might still be possible. However, which color mode is used is decided before the pixel clock capabilities are checked, causing the check to fail and discarding 4k60Hz from the list of possible display modes. Fix: This patch fixes the problem by retrying to find a display mode with YCbCr420 enforced and using it, if it is valid. It's very similar to a patch submitted to amdgpu which fixed the same problem. Testcase: Find a PC with a current Intel iGPU, but only a hdmi 1.4 output. Connect a 4k@60Hz display supporting YCbCr420 encoding to the hdmi port. Without the patch the maximum that can be set via xrandr is 3840 × 2160 30Hz. With the Patch 3840 × 2160 60Hz can be selected which will use YCbCr420 automatically. - Patchset already got accepted upstream for linux-next: + Patchset already got accepted upstream and reached the torvalds tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eacba74d4d561ea6487d944417526e1b025cbebd https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=84d95f77f4aea3f22a486cd04777afd4ab0f0ea5 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=388b863509f76f6a5ecedd7ffdaf184aa813241e and needs only a minor modifications to apply to ubuntu-focal/hwe-5.8 Commit-hashes: eacba74d4d561ea6487d944417526e1b025cbebd 84d95f77f4aea3f22a486cd04777afd4ab0f0ea5 388b863509f76f6a5ecedd7ffdaf184aa813241e -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934489 Title: Make Intel GPUs choose YCbCr420 encoding automatically when required for 4k 60Hz output Status in linux package in Ubuntu: New Bug description: SRU Justification: Impact: On some setups, while the monitor and the GPU support display modes with pixel clocks of up to 600MHz, the connector might not. This prevents RGB encoding for 4k60Hz, but YCbCr420 encoding might still be possible. However, which color mode is used is decided before the pixel clock capabilities are checked, causing the check to fail and discarding 4k60Hz from the list of possible display modes. Fix: This patch fixes the problem by retrying to find a display mode with YCbCr420 enforced and using it, if it is valid. It's very similar to a patch submitted to amdgpu which fixed the same problem. Testcase: Find a PC with a current Intel iGPU, but only a hdmi 1.4 output. Connect a 4k@60Hz display supporting YCbCr420 encoding to the hdmi port. Without the patch the maximum that can be set via xrandr is 3840 × 2160 30Hz. With the Patch 3840 × 2160 60Hz can be selected which will use YCbCr420 automatically. Patchset already got accepted upstream and reached the torvalds tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eacba74d4d561ea6487d944417526e1b025cbebd https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=84d95f77f4aea3f22a486cd04777afd4ab0f0ea5 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=388b863509f76f6a5ecedd7ffdaf184aa813241e and needs only a minor modifications to apply to ubuntu-focal/hwe-5.8 Commit-hashes: eacba74d4d561ea6487d944417526e1b025cbebd 84d95f77f4aea3f22a486cd04777afd4ab0f0ea5 388b863509f76f6a5ecedd7ffdaf184aa813241e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933716] Re: Black screen on boot after stable update
Did a BIOS update to 01.09.00 Rev.A. Did not solve the problem -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933716 Title: Black screen on boot after stable update Status in linux package in Ubuntu: Confirmed Bug description: After kernel update from 5.11.0-18-generic to 5.11.0-22-generic system boots into black screen. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcin 1374 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 26 11:55:00 2021 InstallationDate: Installed on 2021-05-02 (55 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP HP Pavilion Laptop 15-eg0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=9625a19f-eeea-4a92-ab4b-1549d4950f3b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2021 dmi.bios.release: 15.12 dmi.bios.vendor: Insyde dmi.bios.version: F.12 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 87CB dmi.board.vendor: HP dmi.board.version: 34.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 34.27 dmi.modalias: dmi:bvnInsyde:bvrF.12:bd03/17/2021:br15.12:efr34.27:svnHP:pnHPPavilionLaptop15-eg0xxx:pvrType1ProductConfigId:rvnHP:rn87CB:rvr34.27:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-eg0xxx dmi.product.sku: 2Q2T4EA#AKD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934489] [NEW] Make Intel GPUs choose YCbCr420 encoding automatically when required for 4k 60Hz output
Public bug reported: SRU Justification: Impact: On some setups, while the monitor and the GPU support display modes with pixel clocks of up to 600MHz, the connector might not. This prevents RGB encoding for 4k60Hz, but YCbCr420 encoding might still be possible. However, which color mode is used is decided before the pixel clock capabilities are checked, causing the check to fail and discarding 4k60Hz from the list of possible display modes. Fix: This patch fixes the problem by retrying to find a display mode with YCbCr420 enforced and using it, if it is valid. It's very similar to a patch submitted to amdgpu which fixed the same problem. Testcase: Find a PC with a current Intel iGPU, but only a hdmi 1.4 output. Connect a 4k@60Hz display supporting YCbCr420 encoding to the hdmi port. Without the patch the maximum that can be set via xrandr is 3840 × 2160 30Hz. With the Patch 3840 × 2160 60Hz can be selected which will use YCbCr420 automatically. Patchset already got accepted upstream and reached the torvalds tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eacba74d4d561ea6487d944417526e1b025cbebd https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=84d95f77f4aea3f22a486cd04777afd4ab0f0ea5 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=388b863509f76f6a5ecedd7ffdaf184aa813241e and needs only a minor modifications to apply to ubuntu-focal/hwe-5.8 Commit-hashes: eacba74d4d561ea6487d944417526e1b025cbebd 84d95f77f4aea3f22a486cd04777afd4ab0f0ea5 388b863509f76f6a5ecedd7ffdaf184aa813241e ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934489 Title: Make Intel GPUs choose YCbCr420 encoding automatically when required for 4k 60Hz output Status in linux package in Ubuntu: New Bug description: SRU Justification: Impact: On some setups, while the monitor and the GPU support display modes with pixel clocks of up to 600MHz, the connector might not. This prevents RGB encoding for 4k60Hz, but YCbCr420 encoding might still be possible. However, which color mode is used is decided before the pixel clock capabilities are checked, causing the check to fail and discarding 4k60Hz from the list of possible display modes. Fix: This patch fixes the problem by retrying to find a display mode with YCbCr420 enforced and using it, if it is valid. It's very similar to a patch submitted to amdgpu which fixed the same problem. Testcase: Find a PC with a current Intel iGPU, but only a hdmi 1.4 output. Connect a 4k@60Hz display supporting YCbCr420 encoding to the hdmi port. Without the patch the maximum that can be set via xrandr is 3840 × 2160 30Hz. With the Patch 3840 × 2160 60Hz can be selected which will use YCbCr420 automatically. Patchset already got accepted upstream and reached the torvalds tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eacba74d4d561ea6487d944417526e1b025cbebd https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=84d95f77f4aea3f22a486cd04777afd4ab0f0ea5 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=388b863509f76f6a5ecedd7ffdaf184aa813241e and needs only a minor modifications to apply to ubuntu-focal/hwe-5.8 Commit-hashes: eacba74d4d561ea6487d944417526e1b025cbebd 84d95f77f4aea3f22a486cd04777afd4ab0f0ea5 388b863509f76f6a5ecedd7ffdaf184aa813241e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932166] Re: openafs/1.8.4~pre1-1ubuntu2.1 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
** Description changed: - This is a scripted bug report about ADT failures while running openafs - tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is - caused by the dep8 tests of the tested source or the kernel has yet to - be determined. + [Impact] + + Openafs 1.8.4~pre1-1ubuntu2.1 FTBFS when built against Linux 5.11 + + + [Fix] + + Apply the attached debdiff (that is, in turn, a backport of upstream + Linux build fixes), build the debs, install the dkms deb and build it + against an installed 5.11 kernel: + + $ sudo dkms install openafs/1.8.4~pre1-1ubuntu2.1 -k $linux-5.11-version + + + [Regression potential] + + The previous DKMS didn't build at all against 5.11. + + -- + This is a scripted bug report about ADT failures while running openafs tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: - amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/o/openafs/20210611_211122_e1866@/log.gz - arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/o/openafs/20210612_124646_ae454@/log.gz - armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/o/openafs/20210611_212209_cd7d4@/log.gz - s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/o/openafs/20210611_210636_9cb1d@/log.gz + amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/o/openafs/20210611_211122_e1866@/log.gz + arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/o/openafs/20210612_124646_ae454@/log.gz + armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/o/openafs/20210611_212209_cd7d4@/log.gz + s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/o/openafs/20210611_210636_9cb1d@/log.gz -- 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/1932166 Title: openafs/1.8.4~pre1-1ubuntu2.1 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: New Status in openafs package in Ubuntu: New Status in linux-hwe-5.11 source package in Focal: New Status in openafs source package in Focal: Confirmed Bug description: [Impact] Openafs 1.8.4~pre1-1ubuntu2.1 FTBFS when built against Linux 5.11 [Fix] Apply the attached debdiff (that is, in turn, a backport of upstream Linux build fixes), build the debs, install the dkms deb and build it against an installed 5.11 kernel: $ sudo dkms install openafs/1.8.4~pre1-1ubuntu2.1 -k $linux-5.11-version [Regression potential] The previous DKMS didn't build at all against 5.11. -- This is a scripted bug report about ADT failures while running openafs tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/o/openafs/20210611_211122_e1866@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/o/openafs/20210612_124646_ae454@/log.gz armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/o/openafs/20210611_212209_cd7d4@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/o/openafs/20210611_210636_9cb1d@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1932166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880645] Re: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / F-OEM-5.10 / F-OEM-5.13 / F / G / H
applied to oem-5.13 via rebase ** Changed in: linux-oem-5.13 (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.6 in Ubuntu. https://bugs.launchpad.net/bugs/1880645 Title: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / F-OEM-5.10 / F-OEM-5.13 / F / G / H Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released 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.6 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.13 source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid 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.6 source package in Hirsute: Invalid Bug description: [Impact] The IPv6: mtu exception plus redirect test in icmp_redirect.sh test from kselftest/net is expected to fail due to a known bug in the IPv6 logic. When trying to run this test you will see this sub test fail with: TEST: IPv6: mtu exception plus redirect [FAIL] and thus causing non-zero return value for this script. [Fix] * 0a36a75c681880 selftests: icmp_redirect: support expected failures This fix can be cherry-picked into all affected series. And it has already landed on Unstable, test passed with Impish 5.13. Although we have this script in Focal kernel as well, but it's not being executed at all. This is another issue that will be dealt in a different bug report. [Test] Run the patched icmp_redirect.sh test manually in tools/testing/selftests/net, this sub-test will be marked as XFAIL and the return value of this script will be 0: $ sudo ./icmp_redirect.sh # Routing with nexthop objects and VRF # TEST: IPv6: mtu exception plus redirect [XFAIL] Tests passed: 36 Tests failed: 0 Tests xfailed: 4 $ echo $? 0 [Where problems could occur] Change limited to testing tool, not affecting actual kernel functionality. The only possible issue that I can think of is that as this script is no longer complaining about this failure, people might forgot there is such an issue exist in ipv6. [Original Bug Report] Issue found on Focal 5.6.0-1011.11-oem ubuntu@rizzo:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$ sudo ./icmp_redirect.sh ### Legacy routing ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL] ### Legacy routing with VRF ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect
[Kernel-packages] [Bug 1930719] Re: Replace AMD nvme workaround from oem-5.10 with upstream version
** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Confirmed => Fix Committed -- 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/1930719 Title: Replace AMD nvme workaround from oem-5.10 with upstream version Status in amd: Fix Committed 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.10 source package in Focal: Confirmed Status in linux-oem-5.13 source package in Focal: Fix Committed Bug description: The workaround carried in linux-oem-5.10 to support suspend to idle on AMD platforms: https://kernel.ubuntu.com/git/kernel-ppa/mirror/ubuntu- oem-5.10-focal.git/commit/drivers/nvme?h=oem-5.10-next=2d37b035a0f469d40ab0322b0f9dd7f2d43bc9b8 Should be replaced with what's going upstream for 5.14: http://git.infradead.org/nvme.git/commit/e21e0243e7b0f1c2a21d21f4d115f7b37175772a And please also apply it to oem-5.13. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1930719/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934462] Re: Ability to hibernate lost after update of kernel version
Thank you for taking the time to report this bug and helping to make Ubuntu better. Changing ubuntu-release-upgrader -> linux (install was bionic, it's still bionic so no release-upgrade has occurred; I believe bot-crichton was wrong) ** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934462 Title: Ability to hibernate lost after update of kernel version Status in linux package in Ubuntu: New Bug description: Hi! I have Ubuntu 18.04 installed (due to Petalinux requirement) where Hibernation so far at least worked. Recently I got an update notification, confirmed it and am now running on this version: $ uname -a Linux datatel-XMG-CORE-M19-GTX-1650 5.4.0-77-generic #86~18.04.1-Ubuntu SMP Fri Jun 18 01:23:22 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Before the update, using kernel 5.4.0.74 a "sudo hibernate" worked fine. Now it does not, instead returns a black screen for a sec and then this notice: hibernate:Warning: Tuxonice binary signature file not found. In addition the system hangs for a couple of seconds. Looking for help on that I saw several posts proposing to adapt /sys/power/state, adding "disk" and "standby" to it. I have tried that in any possible way I could think of, using vi directly on the file (as su), writing it with an "echo... > /sys/power/state" command, making up a file in my home and then copying to that location using "sudo cp ~/ /sys/power/state". Neither of this works. I always get a permission error. I have even tried to "chmod" all the directories to "777" and that was successful looking at "ls -la" but won't help either. Maybe I should mention that my Ubuntu installation resides on a USB- Stick. I posted this on Ask Ubuntu and was asked to file a bug report. So here you are. Thanks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.44 ProcVersionSignature: Ubuntu 5.4.0-77.86~18.04.1-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Jul 2 09:16:59 2021 InstallationDate: Installed on 2021-05-11 (51 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2021-05-17 11:54:33.809310 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done Log time: 2021-05-17 11:55:10.776569 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934462/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860987] Re: openvswitch: same tcp session encapsulated with different udp src port for ovs vxlan tunnel
Raising tasks for Linux as well - Groovy onwards is good so just focal
and bionic targets now.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860987
Title:
openvswitch: same tcp session encapsulated with different udp src port
for ovs vxlan tunnel
Status in linux package in Ubuntu:
Fix Released
Status in openvswitch package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
New
Status in openvswitch source package in Bionic:
Triaged
Status in linux source package in Focal:
New
Status in openvswitch source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Status in openvswitch source package in Groovy:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Status in openvswitch source package in Hirsute:
Fix Released
Status in linux source package in Impish:
Fix Released
Status in openvswitch source package in Impish:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Packets encapsulated into a vxlan tunnel with openvswitch don't have
the same udp source port for the first packet and the following ones
of the same TCP flow in a DOCKER scenario usecase.
In fact, when using the kernel datapath, the upcall don't include skb hash
info relatived. As VXLAN module uses
the skb hash to select UDP src port, the source port is different for the
first packet.
More information can be found here:
https://mail.openvswitch.org/pipermail/ovs-dev/2019-October/364062.html
This has been fixed in the next release openvswitch 2.13 by the following
upstream commits:
- 0442bfb11d6ccb ("ofproto-dpif-upcall: Echo HASH attribute back to
datapath.")
- c4d8a4e0399910 ("ofproto-dpif: Fix using uninitialized execute hash.")
- 924d94a695a6ca ("ofproto-dpif-upcall: Fix using uninitialized upcall hash.")
https://github.com/openvswitch/ovs/commit/0442bfb11d6ccbf11754ef1d6de603b970465302
https://github.com/openvswitch/ovs/commit/c4d8a4e039991030c1298dbd1335d209cb437875
https://github.com/openvswitch/ovs/commit/924d94a695a6ca54b83d4bd42ec196ba53947c6d
The bug exists since the beginning of vxlan support in openvswitch.
== Fix ==
Backport the requested patches to Focal (5.4), Disco (5.0), Bionic (4.15) and
Xenial (4.4).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860987/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860987] Re: openvswitch: same tcp session encapsulated with different udp src port for ovs vxlan tunnel
For reference - this should be usable on Focal with the HWE kernel
(rather than the 5.4 release kernel).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860987
Title:
openvswitch: same tcp session encapsulated with different udp src port
for ovs vxlan tunnel
Status in linux package in Ubuntu:
Fix Released
Status in openvswitch package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
New
Status in openvswitch source package in Bionic:
Triaged
Status in linux source package in Focal:
New
Status in openvswitch source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Status in openvswitch source package in Groovy:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Status in openvswitch source package in Hirsute:
Fix Released
Status in linux source package in Impish:
Fix Released
Status in openvswitch source package in Impish:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Packets encapsulated into a vxlan tunnel with openvswitch don't have
the same udp source port for the first packet and the following ones
of the same TCP flow in a DOCKER scenario usecase.
In fact, when using the kernel datapath, the upcall don't include skb hash
info relatived. As VXLAN module uses
the skb hash to select UDP src port, the source port is different for the
first packet.
More information can be found here:
https://mail.openvswitch.org/pipermail/ovs-dev/2019-October/364062.html
This has been fixed in the next release openvswitch 2.13 by the following
upstream commits:
- 0442bfb11d6ccb ("ofproto-dpif-upcall: Echo HASH attribute back to
datapath.")
- c4d8a4e0399910 ("ofproto-dpif: Fix using uninitialized execute hash.")
- 924d94a695a6ca ("ofproto-dpif-upcall: Fix using uninitialized upcall hash.")
https://github.com/openvswitch/ovs/commit/0442bfb11d6ccbf11754ef1d6de603b970465302
https://github.com/openvswitch/ovs/commit/c4d8a4e039991030c1298dbd1335d209cb437875
https://github.com/openvswitch/ovs/commit/924d94a695a6ca54b83d4bd42ec196ba53947c6d
The bug exists since the beginning of vxlan support in openvswitch.
== Fix ==
Backport the requested patches to Focal (5.4), Disco (5.0), Bionic (4.15) and
Xenial (4.4).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860987/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860987] Re: openvswitch: same tcp session encapsulated with different udp src port for ovs vxlan tunnel
Commit that introduces the hash to the upcall to OVS:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-
groovy.git/commit/include/uapi/linux/openvswitch.h?id=bd1903b7c4596ba6f7677d0dfefd05ba5876707d
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Groovy)
Status: New => Fix Released
** Changed in: linux (Ubuntu Hirsute)
Status: New => Fix Released
** Changed in: linux (Ubuntu Impish)
Status: New => 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/1860987
Title:
openvswitch: same tcp session encapsulated with different udp src port
for ovs vxlan tunnel
Status in linux package in Ubuntu:
Fix Released
Status in openvswitch package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
New
Status in openvswitch source package in Bionic:
Triaged
Status in linux source package in Focal:
New
Status in openvswitch source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Status in openvswitch source package in Groovy:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Status in openvswitch source package in Hirsute:
Fix Released
Status in linux source package in Impish:
Fix Released
Status in openvswitch source package in Impish:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Packets encapsulated into a vxlan tunnel with openvswitch don't have
the same udp source port for the first packet and the following ones
of the same TCP flow in a DOCKER scenario usecase.
In fact, when using the kernel datapath, the upcall don't include skb hash
info relatived. As VXLAN module uses
the skb hash to select UDP src port, the source port is different for the
first packet.
More information can be found here:
https://mail.openvswitch.org/pipermail/ovs-dev/2019-October/364062.html
This has been fixed in the next release openvswitch 2.13 by the following
upstream commits:
- 0442bfb11d6ccb ("ofproto-dpif-upcall: Echo HASH attribute back to
datapath.")
- c4d8a4e0399910 ("ofproto-dpif: Fix using uninitialized execute hash.")
- 924d94a695a6ca ("ofproto-dpif-upcall: Fix using uninitialized upcall hash.")
https://github.com/openvswitch/ovs/commit/0442bfb11d6ccbf11754ef1d6de603b970465302
https://github.com/openvswitch/ovs/commit/c4d8a4e039991030c1298dbd1335d209cb437875
https://github.com/openvswitch/ovs/commit/924d94a695a6ca54b83d4bd42ec196ba53947c6d
The bug exists since the beginning of vxlan support in openvswitch.
== Fix ==
Backport the requested patches to Focal (5.4), Disco (5.0), Bionic (4.15) and
Xenial (4.4).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860987/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934462] [NEW] Ability to hibernate lost after update of kernel version
You have been subscribed to a public bug: Hi! I have Ubuntu 18.04 installed (due to Petalinux requirement) where Hibernation so far at least worked. Recently I got an update notification, confirmed it and am now running on this version: $ uname -a Linux datatel-XMG-CORE-M19-GTX-1650 5.4.0-77-generic #86~18.04.1-Ubuntu SMP Fri Jun 18 01:23:22 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Before the update, using kernel 5.4.0.74 a "sudo hibernate" worked fine. Now it does not, instead returns a black screen for a sec and then this notice: hibernate:Warning: Tuxonice binary signature file not found. In addition the system hangs for a couple of seconds. Looking for help on that I saw several posts proposing to adapt /sys/power/state, adding "disk" and "standby" to it. I have tried that in any possible way I could think of, using vi directly on the file (as su), writing it with an "echo... > /sys/power/state" command, making up a file in my home and then copying to that location using "sudo cp ~/ /sys/power/state". Neither of this works. I always get a permission error. I have even tried to "chmod" all the directories to "777" and that was successful looking at "ls -la" but won't help either. Maybe I should mention that my Ubuntu installation resides on a USB- Stick. I posted this on Ask Ubuntu and was asked to file a bug report. So here you are. Thanks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.44 ProcVersionSignature: Ubuntu 5.4.0-77.86~18.04.1-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Jul 2 09:16:59 2021 InstallationDate: Installed on 2021-05-11 (51 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2021-05-17 11:54:33.809310 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done Log time: 2021-05-17 11:55:10.776569 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages -- Ability to hibernate lost after update of kernel version https://bugs.launchpad.net/bugs/1934462 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 1930645] Re: Fix Ethernet not working by hotplug - RTL8106E
** Changed in: linux-oem-5.13 (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.10 in Ubuntu. https://bugs.launchpad.net/bugs/1930645 Title: Fix Ethernet not working by hotplug - RTL8106E 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: New Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-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: New Status in linux-oem-5.13 source package in Hirsute: New 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: New Bug description: [Impact] After hot-plug the Ethernet cable, the status of Ethernet is always down. [Fix] Because ASPM is enabled on RTL8106E, the link change interrupt can't be fired immediately. Must wait a long time to get the link change interrupt. After discuss with maintainer, he give some suggestions 1. use PHY_POLL. 2. he send a workaround(Ref. [1]) to disable ASPM on RTL8106E. For 2, because don't know the details about operated registers in rtl_hw_aspm_clkreq_enable, it have higher risk on power usage during suspend. For 1, Use PHY_POLL have a lower risk because don't change any register operations and use polling method to query link change status. SRU the patches for 1 first. Currently keep discussing with Realtek but don't figure out yet. Will re-SRU the official solution once Realtek resolve the issue. Ref [1], https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=1ee8856de82faec9bc8bd0f2308a7f27e30ba207 [Test] Verified on machines with Realtek Ethernet device, the Ethernet works well after hotplug 30 times. [Regression Potential] Medium, use polling methond may have higher cpu usage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1930645/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928242] Re: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle
** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.13 (Ubuntu Groovy) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-oem-5.13 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Impish) 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/1928242 Title: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle Status in HWE Next: Fix Released Status in linux package in Ubuntu: Confirmed 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: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Released Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.13 source package in Groovy: Invalid Status in linux source package in Hirsute: Fix Released 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: Confirmed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] All of 3 different WD19(TB/SC/DC) docks have 3 Type-A ports and 2 Type-C ports, and there're highspeed Hubs(0bda:5487 and its substream hub 0bda:5413) and Superspeed Hubs (0bda:0487 and its downstream hub 0bda:0413). In the bug description below, we will refer the 2 highspeed hubs as Hub A and Hub A.3, and the 2 superspeed hubs as Hub B and Hub B.3. All devices connected via either Type-A or Type-C ports will connect to either Hub A.3 or Hub B.3. If we connect a wakup enabled device (keyboard) to a Type-A port, the Hub A.3 will fail to activate after exiting s2idle and all downstream devices will not be detected. If we have a superspeed device connected to other Type-A port in addition to the keyboard, this superspeed device actually connects to Hub B.3, and the Hub B.3 will also fails to work after exiting s2idle. If the wakeup enabled device connects via Type-C port, there's no such problem. As a summary, a wakeup enabled device connect to Type-A port will cause the failure of Hub A.3 and Hub B.3. Hub B.3 only fails when a wakeup enabled device and a superspeed device both connect via Type-A port. [Fix] Before the resume failure, the upstream hub(Hub A or B) will hit the timeout problem while doing SetPortFeature(PORT_SUSPEND) to the port of the downstream hub (Hub A.3 or Hub B.3). However, the PORT_SUSPEND bit of the wPortStatus is actually turned on for the Hub A.3, we simply need to make the kernel believe it's already suspended. Then the ClearPortFeature will be done during resume and the problem will go away. The Hub B.3 will be tricky. The PORT_SUSPEND bit is not on after the suspend timeout, but it needs the ClearPortFeature(PORT_SUSPEND) for Hub B.3 to avoid resume failure. It doesn't comply with the USB spec so it's hard to create a generic fix for it. Because it only happens when timeout happens on suspending Hub A.3 and there's a superspeed device connecting to Type-A port, we choose to leave it as-is and try to address it in the future. [Test Case] 1. Make sure that the WD19 connects to the laptop 2. Connect USB keyboard/mouse to USB Type-A ports. 3. Suspend the system 4. Press the Enter key or power button to wake up the system 5. Check if the USB keyboard/mouse are still working Repeat 4 and 5 for > 10 times w/o losing any USB devices. [Where problems could occur] A wakeup enabled device (keyboard) connect to Type-A port will cause the failure of Hub A.3 and Hub B.3 during resume. Hub B.3 only fails when a wakeup enabled device and a superspeed device both connect via Type-A port. All devices connects to Hub A.3 (and B.3 if superspeed device connect via Type-A port) will be lost after resume. [Regression Potential] Minimum. The fix is only triggered when timeout happens during USB port suspend and it follows the standard USB protocol to do either resume or reset_resume. == Original Bug Description == ● Summary Plug in USB mouse and USB keyboard to WD19/WD19DC USB ports near LAN port. Plug dock into SUT and check USB keyboard and mouse work. SUT enter suspend. After 1 min resume SUT, check USB keyboard/mouse function. Sometimes USB keyboard/mouse no function. Isolation: 1. VP on UMA and Discrete 2. When issue occur, both front and back port on WD19 can't work using USB keyboard/mouse
[Kernel-packages] [Bug 1934187] Re: lxd exec fails
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1934187
Title:
lxd exec fails
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Bug description:
[Impact]
lxd will not work, as lxc exec is not able to set the apparmor confinement
and bails out executing inside the container.
[Fix]
Revert upstream commit bfb819ea20ce8bbeeba17e1a6418bf8bda91fc28 ("proc: Check
/proc/$pid/attr/ writes against file opener").
[Test case]
lxd basic usage test suite was run.
On a 4.15 kernel, the whole lxd autopkgtest was run.
[Potential regression]
Unprivileged use of PID attributes may be permitted when they shouldn't.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934187/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931072] Re: USB Type-C hotplug event not handled properly in TGL-H system during s2idle
** Changed in: linux-oem-5.13 (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.10 in Ubuntu. https://bugs.launchpad.net/bugs/1931072 Title: USB Type-C hotplug event not handled properly in TGL-H system during s2idle 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: [SRU Justification] [Impact] The system will be hold by the infinite loop in ACPI method IPCS after exiting s2idle in TGL-H systems if the docking station with external display connected is unplugged when the system is still in s2idle. It's because the system is unaware of the unplug event and it seems keep something asserted which will never be released while the system trying to exit s2idle. [Fix] Disconnect TypeC PHYs during system suspend and shutdown, even with the corresponding TypeC sink still plugged to its connector. The HPD event is no longer triggered when the system is in s2idle so the resume process will not be hindered. [Test Case] 1. On all TigerLake-H and later platforms with NVIDIA GPU, make sure the NVIDIA GPU is running in either On-Demand mode or Performance mode. 2. Connect the docking station with the external display connected. 3. Suspend the system. 4. Remove the docking station when the system is suspended. 5. Press power button to wake up the system and wait > 1 minutes to make sure if the display comes back. [Where problems could occur] Low. This will only make a difference in the TypeC DP alternate mode, and the display driver will detect the display connector after resume. == Original Bug Description == [Summary] As mentioned in #1929166, the NVIDIA GPU will fall off the bus after exiting s2idle in TGL-H systems if the USB Type-C docking/dongle with external display connected is unplugged when the system is still in s2idle. The system will be hold by the infinite loop in ACPI method IPCS and then the PCIe root port of NVIDIA gpu fails the power transition from D3cold to D0. It's because the display connector hotplug event not handled properly in graphics drivers and the system will freeze for > 30 seconds to wait for ACPI method IPCS to exit. [ 154.446781] [ 154.446783] [ 154.446783] Initialized Local Variables for Method [IPCS]: [ 154.446784] Local0: 9863e365 Integer 09C5 [ 154.446790] [ 154.446791] Initialized Arguments for Method [IPCS]: (7 arguments defined for method invocation) [ 154.446792] Arg0: 25568fbd Integer 00AC [ 154.446795] Arg1: 9ef30e76 Integer [ 154.446798] Arg2: fdf820f0 Integer 0010 [ 154.446801] Arg3: 9fc2a088 Integer 0001 [ 154.446804] Arg4: 3a3418f7 Integer 0001 [ 154.446807] Arg5: 20c4b87c Integer [ 154.446810] Arg6: 8b965a8a Integer [ 154.446813] [ 154.446815] ACPI Error: Aborting method \IPCS due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446824] ACPI Error: Aborting method \MCUI due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446829] ACPI Error: Aborting method \SPCX due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446835] ACPI Error: Aborting method \_SB.PC00.PGSC due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446841] ACPI Error: Aborting method \_SB.PC00.PGON due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446846] ACPI Error: Aborting method \_SB.PC00.PEG1.NPON due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446852] ACPI Error: Aborting method \_SB.PC00.PEG1.PG01._ON due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446860] acpi device:02: Failed to change power state to D0 [ 154.690760] video LNXVIDEO:00: Cannot transition to power state D0 for parent in (unknown) [Reproduce Steps] 1. Connect either Dell WD19SC/DC/TB docking station(USB Type-C) to the system. 2. Connect to external display to HDMI/DisplayPort of the docking 3. Suspend the system 4. Unplug the USB Type-C
[Kernel-packages] [Bug 1933716] Re: Black screen on boot after stable update
@Dylan please mark in the header that you are affected as well. Thank you -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933716 Title: Black screen on boot after stable update Status in linux package in Ubuntu: Confirmed Bug description: After kernel update from 5.11.0-18-generic to 5.11.0-22-generic system boots into black screen. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcin 1374 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 26 11:55:00 2021 InstallationDate: Installed on 2021-05-02 (55 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP HP Pavilion Laptop 15-eg0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=9625a19f-eeea-4a92-ab4b-1549d4950f3b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2021 dmi.bios.release: 15.12 dmi.bios.vendor: Insyde dmi.bios.version: F.12 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 87CB dmi.board.vendor: HP dmi.board.version: 34.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 34.27 dmi.modalias: dmi:bvnInsyde:bvrF.12:bd03/17/2021:br15.12:efr34.27:svnHP:pnHPPavilionLaptop15-eg0xxx:pvrType1ProductConfigId:rvnHP:rn87CB:rvr34.27:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-eg0xxx dmi.product.sku: 2Q2T4EA#AKD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933716] Re: Black screen on boot after stable update
The Laptops display is blank (shut off), but external monitors work (HDMI and USB-C). The only workaround is to boot kernel 5.11.0-18. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933716 Title: Black screen on boot after stable update Status in linux package in Ubuntu: Confirmed Bug description: After kernel update from 5.11.0-18-generic to 5.11.0-22-generic system boots into black screen. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcin 1374 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 26 11:55:00 2021 InstallationDate: Installed on 2021-05-02 (55 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP HP Pavilion Laptop 15-eg0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=9625a19f-eeea-4a92-ab4b-1549d4950f3b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2021 dmi.bios.release: 15.12 dmi.bios.vendor: Insyde dmi.bios.version: F.12 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 87CB dmi.board.vendor: HP dmi.board.version: 34.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 34.27 dmi.modalias: dmi:bvnInsyde:bvrF.12:bd03/17/2021:br15.12:efr34.27:svnHP:pnHPPavilionLaptop15-eg0xxx:pvrType1ProductConfigId:rvnHP:rn87CB:rvr34.27:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-eg0xxx dmi.product.sku: 2Q2T4EA#AKD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
It's becoming increasingly difficult to build your own kernels on focal due to the kernel dependencies on newer tool-chain elements. You now need dwarves 1.21 (or 1.20 with this patch https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1928244 ) to build a 5.13 kernel. I have a focal based container for building mainline here: https://github.com/TuxInvader/focal-mainline-builder The container includes the build dependencies for mainline kernels, and builds the latest dwarves and libbpf source packages from 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/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS Status in linux package in Ubuntu: Confirmed Bug description: Hi all, The Mainline wiki states that the mainline kernels are built with the previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are being built with Hirsuite 21.04, and before that Groovy? If this is intentional, then the wiki should be updated to reflect the change in policy. From https://wiki.ubuntu.com/Kernel/MainlineBuilds Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On my Focal LTS system I have GCC 9.3.0. The Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The *linux-headers-generic* packages have unmet dependencies on 20.04 LTS. I could install Groovy built kernels fine, but the Hirsuite ones built with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels can't be installed on Focal (libc 2.31). Thanks, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
If you want to stay with Ubuntu 20.04 LTS with latest stable mainline, you'll need to build it. Otherwise, try openSuse-Tumbleweed or Fedora. I'm sticking with ubuntu so just building my own kernels. Runs faster now as well since it is optimised for my rig specifically now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS Status in linux package in Ubuntu: Confirmed Bug description: Hi all, The Mainline wiki states that the mainline kernels are built with the previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are being built with Hirsuite 21.04, and before that Groovy? If this is intentional, then the wiki should be updated to reflect the change in policy. From https://wiki.ubuntu.com/Kernel/MainlineBuilds Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On my Focal LTS system I have GCC 9.3.0. The Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The *linux-headers-generic* packages have unmet dependencies on 20.04 LTS. I could install Groovy built kernels fine, but the Hirsuite ones built with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels can't be installed on Focal (libc 2.31). Thanks, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934187] Re: lxd exec fails
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1934187
Title:
lxd exec fails
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
In Progress
Status in linux source package in Focal:
In Progress
Bug description:
[Impact]
lxd will not work, as lxc exec is not able to set the apparmor confinement
and bails out executing inside the container.
[Fix]
Revert upstream commit bfb819ea20ce8bbeeba17e1a6418bf8bda91fc28 ("proc: Check
/proc/$pid/attr/ writes against file opener").
[Test case]
lxd basic usage test suite was run.
On a 4.15 kernel, the whole lxd autopkgtest was run.
[Potential regression]
Unprivileged use of PID attributes may be permitted when they shouldn't.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934187/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933716] Re: Black screen on boot after stable update
I have this bug as well. With an HP Probook 450 G7 (Core i7 10thGen) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933716 Title: Black screen on boot after stable update Status in linux package in Ubuntu: Confirmed Bug description: After kernel update from 5.11.0-18-generic to 5.11.0-22-generic system boots into black screen. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcin 1374 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 26 11:55:00 2021 InstallationDate: Installed on 2021-05-02 (55 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP HP Pavilion Laptop 15-eg0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=9625a19f-eeea-4a92-ab4b-1549d4950f3b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2021 dmi.bios.release: 15.12 dmi.bios.vendor: Insyde dmi.bios.version: F.12 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 87CB dmi.board.vendor: HP dmi.board.version: 34.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 34.27 dmi.modalias: dmi:bvnInsyde:bvrF.12:bd03/17/2021:br15.12:efr34.27:svnHP:pnHPPavilionLaptop15-eg0xxx:pvrType1ProductConfigId:rvnHP:rn87CB:rvr34.27:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-eg0xxx dmi.product.sku: 2Q2T4EA#AKD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933716] Re: Black screen on boot after stable update
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933716 Title: Black screen on boot after stable update Status in linux package in Ubuntu: Confirmed Bug description: After kernel update from 5.11.0-18-generic to 5.11.0-22-generic system boots into black screen. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcin 1374 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 26 11:55:00 2021 InstallationDate: Installed on 2021-05-02 (55 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP HP Pavilion Laptop 15-eg0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=9625a19f-eeea-4a92-ab4b-1549d4950f3b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2021 dmi.bios.release: 15.12 dmi.bios.vendor: Insyde dmi.bios.version: F.12 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 87CB dmi.board.vendor: HP dmi.board.version: 34.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 34.27 dmi.modalias: dmi:bvnInsyde:bvrF.12:bd03/17/2021:br15.12:efr34.27:svnHP:pnHPPavilionLaptop15-eg0xxx:pvrType1ProductConfigId:rvnHP:rn87CB:rvr34.27:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-eg0xxx dmi.product.sku: 2Q2T4EA#AKD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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-oracle-5.11/5.11.0.1011.11~20.04.3)
All autopkgtests for the newly accepted linux-meta-oracle-5.11 (5.11.0.1011.11~20.04.3) for focal have finished running. The following regressions have been reported in tests triggered by the package: glibc/2.31-0ubuntu9.2 (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-oracle-5.11 [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 1934401] Re: Control netfilter flow table timeouts via sysctl
** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-bluefield (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-bluefield (Ubuntu Focal) Assignee: (unassigned) => Bodong Wang (bodong-wang) ** Changed in: linux-bluefield (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1934401 Title: Control netfilter flow table timeouts via sysctl Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: In Progress Bug description: * Explain the bug(s) TCP and UDP connections may be offloaded from nf conntrack to nf flow table. Offloaded connections are aged after 30 seconds of inactivity. Once aged, ownership is returned to conntrack with a hard coded tcp/udp pickup time of 120/30 seconds, after which the connection may be deleted. The current hard-coded pickup intervals may introduce a very aggressive aging policy. For example, offloaded tcp connections in established state will timeout from nf conntrack after just 150 seconds of inactivity, instead of 5 days. In addition, the hard-coded 30 second offload timeout period can significantly increase the hardware insertion rate requirements in some use cases. * Brief explanation of fixes This patchset provides the user with the ability to configure protocol specific offload timeout and pickup intervals via sysctl. The first and second patches revert the existing non-upstream solution. The next two patches introduce the sysctl configuration for tcp and udp protocols. The last patch modifies nf flow table aging mechanisms to use the configured time intervals. * How to test Control tcp/udp connection timeout using the following sysctl parameters: net.netfilter.nf_flowtable_tcp_pickup = 120 net.netfilter.nf_flowtable_tcp_timeout = 30 net.netfilter.nf_flowtable_udp_pickup = 30 net.netfilter.nf_flowtable_udp_timeout = 30 * What it could break. Existing configuration scripts – not kernel related To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1934401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934313] Re: Export xfrm_policy_lookup_bytype function
** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-bluefield (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-bluefield (Ubuntu Focal) Assignee: (unassigned) => Bodong Wang (bodong-wang) ** Changed in: linux-bluefield (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1934313 Title: Export xfrm_policy_lookup_bytype function Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: In Progress Bug description: Export policy lookup function so drivers could lookup a policy that match specific criteria. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1934313/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934464] Re: Brightness control is missing on HP Pavilion Gaming Laptop 15-dk0xxx
** Attachment added: "Screenshot from 2021-07-01 22-46-30.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934464/+attachment/5508612/+files/Screenshot%20from%202021-07-01%2022-46-30.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934464 Title: Brightness control is missing on HP Pavilion Gaming Laptop 15-dk0xxx Status in linux package in Ubuntu: New Bug description: No brightness settings. Also black screen for login if I choose not recovery mode for login. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-22-generic 5.11.0-22.23 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ter3433 F pulseaudio /dev/snd/controlC1: ter3433 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 2 10:33:31 2021 InstallationDate: Installed on 2021-06-25 (6 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=a7c41e63-e7ea-43e0-9de0-55322f489ee5 ro recovery nomodeset dis_ucode_ldr RelatedPackageVersions: linux-restricted-modules-5.11.0-22-generic N/A linux-backports-modules-5.11.0-22-generic N/A linux-firmware 1.197.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2020 dmi.bios.release: 15.33 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85FB dmi.board.vendor: HP dmi.board.version: 42.42 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 42.42 dmi.modalias: dmi:bvnInsyde:bvrF.33:bd07/16/2020:br15.33:efr42.42:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FB:rvr42.42:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx dmi.product.sku: 2C7M8EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934464/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934464] [NEW] Brightness control is missing on HP Pavilion Gaming Laptop 15-dk0xxx
Public bug reported: No brightness settings. Also black screen for login if I choose not recovery mode for login. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-22-generic 5.11.0-22.23 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ter3433 F pulseaudio /dev/snd/controlC1: ter3433 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 2 10:33:31 2021 InstallationDate: Installed on 2021-06-25 (6 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=a7c41e63-e7ea-43e0-9de0-55322f489ee5 ro recovery nomodeset dis_ucode_ldr RelatedPackageVersions: linux-restricted-modules-5.11.0-22-generic N/A linux-backports-modules-5.11.0-22-generic N/A linux-firmware 1.197.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2020 dmi.bios.release: 15.33 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85FB dmi.board.vendor: HP dmi.board.version: 42.42 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 42.42 dmi.modalias: dmi:bvnInsyde:bvrF.33:bd07/16/2020:br15.33:efr42.42:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FB:rvr42.42:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx dmi.product.sku: 2C7M8EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1934464 Title: Brightness control is missing on HP Pavilion Gaming Laptop 15-dk0xxx Status in linux package in Ubuntu: New Bug description: No brightness settings. Also black screen for login if I choose not recovery mode for login. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-22-generic 5.11.0-22.23 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ter3433 F pulseaudio /dev/snd/controlC1: ter3433 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 2 10:33:31 2021 InstallationDate: Installed on 2021-06-25 (6 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=a7c41e63-e7ea-43e0-9de0-55322f489ee5 ro recovery nomodeset dis_ucode_ldr RelatedPackageVersions: linux-restricted-modules-5.11.0-22-generic N/A linux-backports-modules-5.11.0-22-generic N/A linux-firmware 1.197.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2020 dmi.bios.release: 15.33 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85FB dmi.board.vendor: HP dmi.board.version: 42.42 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 42.42 dmi.modalias: dmi:bvnInsyde:bvrF.33:bd07/16/2020:br15.33:efr42.42:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FB:rvr42.42:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx dmi.product.sku: 2C7M8EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934464/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934460] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1934460/+attachment/5508590/+files/acpidump.txt -- 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/1934460 Title: ioremap: invalid physical address d5010fee0526b902 Status in linux-oem-5.10 package in Ubuntu: New Bug description: [4.554394] USB Video Class driver (1.1.1) [5.590819] ioremap: invalid physical address d5010fee0526b902 [5.590822] [ cut here ] [5.590826] WARNING: CPU: 0 PID: 355 at arch/x86/mm/ioremap.c:198 __ioremap_caller.cold+0xf/0x64 [5.590827] Modules linked in: uvcvideo btusb videobuf2_vmalloc btrtl videobuf2_memops btbcm videobuf2_v4l2 btintel videobuf2_common bluetooth videodev ecdh_generic mc ecc nls_iso8859_1 snd_hda_codec_ hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci snd_sof_intel_byt snd_sof_intel_ipc snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_xtensa_dsp snd_sof_intel_hda snd_sof snd_hda_ext_core sn d_soc_acpi_intel_match 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 mei_hdcp snd_soc_core intel_rapl_msr x86_pkg_temp_thermal intel_powerclamp snd_compress ac97_bus snd_pcm_dmaengine iwlmvm coretemp snd_pcm mac80211 dell_laptop snd_seq_midi snd_seq_midi_event kvm_intel snd_rawmidi joydev dell _smm_hwmon libarc4 snd_seq kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel snd_seq_device crypto_simd cryptd dell_wmi i915 snd_timer glue_helper dell_smbios dcdbas rapl intel_cstate iwlwifi [5.590861] drm_kms_helper dell_privacy_wmi cfg80211 cec input_leds rc_core i2c_algo_bit fb_sys_fops syscopyarea dell_wmi_sysman(+) sysfillrect ledtrig_audio snd serio_raw dell_wmi_descriptor efi_pst ore hid_multitouch wmi_bmof processor_thermal_device sysimgblt intel_rapl_common soundcore mei_me intel_soc_dts_iosf mei ucsi_acpi intel_pch_thermal typec_ucsi typec int3403_thermal int3402_thermal int34 00_thermal int340x_thermal_zone mac_hid intel_hid acpi_pad sparse_keymap acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul psmouse i2c_i801 nvme intel_lpss_pci nvme_core ahci i2c_smbus intel_lpss idma64 xhci_pci libahci virt_dma xhci_pci_renesas i2c_hid wmi hid video pinctrl_cannonlake [5.590891] CPU: 0 PID: 355 Comm: systemd-udevd Not tainted 5.10.0-1032-oem #33-Ubuntu [5.590892] Hardware name: Dell Inc. Inspiron 7380/, BIOS 1.1.0 08/08/2018 [5.590894] RIP: 0010:__ioremap_caller.cold+0xf/0x64 [5.590895] Code: 00 00 00 4c 89 e6 bf 04 00 00 00 0f 45 c2 0f bf d0 e8 aa a1 53 ff e9 ca bb 50 ff 48 89 fe 48 c7 c7 d8 eb 19 8b e8 4a 76 00 00 <0f> 0b 45 31 ed e9 03 c4 50 ff 48 8b 75 b8 44 8b 45 c4 44 89 e9 48 [5.590896] RSP: 0018:aab9406cf5f0 EFLAGS: 00010246 [5.590897] RAX: 0032 RBX: 000d5010fee0526b RCX: [5.590898] RDX: RSI: 8c46a7618a40 RDI: 8c46a7618a40 [5.590898] RBP: aab9406cf658 R08: 8c46a7618a40 R09: aab9406cf3c8 [5.590899] R10: 0001 R11: 0001 R12: d5010fee0526b902 [5.590899] R13: d5010fee0526b902 R14: 0008 R15: d5010fee0526b000 [5.590900] FS: 7f1bfda4f880() GS:8c46a760() knlGS: [5.590901] CS: 0010 DS: ES: CR0: 80050033 [5.590902] CR2: 7fc270b47cf0 CR3: 0001066ee004 CR4: 003706f0 [5.590902] Call Trace: [5.590906] ? acpi_os_map_iomem+0x1bc/0x1d0 [5.590907] ? _cond_resched+0x19/0x30 [5.590910] ioremap_cache+0x17/0x20 [5.590911] acpi_os_map_iomem+0x1bc/0x1d0 [5.590912] acpi_os_map_memory+0xe/0x10 [5.590915] acpi_ex_system_memory_space_handler+0x1fc/0x3aa [5.590916] acpi_ev_address_space_dispatch+0x34d/0x40e [5.590917] ? acpi_ex_prep_field_value+0x50a/0x50a [5.590919] acpi_ex_access_region+0x454/0x4ed [5.590920] acpi_ex_field_datum_io+0x18a/0x42d [5.590921] acpi_ex_extract_from_field+0xe7/0x320 [5.590922] ? acpi_ut_trace+0x28/0x6a [5.590924] acpi_ex_read_data_from_field+0x31f/0x371 [5.590925] acpi_ex_resolve_node_to_value+0x3a7/0x4dd [5.590926] acpi_ex_resolve_to_value+0x3c3/0x472 [5.590928] acpi_ds_evaluate_name_path+0xb1/0x169 [5.590930] ? acpi_db_single_step+0x1f/0x252 [5.590931] acpi_ds_exec_end_op+0x118/0x76b [5.590933] acpi_ps_parse_loop+0x84b/0x924 [5.590934] acpi_ps_parse_aml+0x1af/0x550 [5.590935] acpi_ps_execute_method+0x208/0x2ca [5.590936] acpi_ns_evaluate+0x34e/0x4f0 [5.590937] acpi_evaluate_object+0x18e/0x3b4 [5.590940] __query_block+0x184/0x1f0 [wmi] [5.590942]
[Kernel-packages] [Bug 1934460] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1934460/+attachment/5508586/+files/WifiSyslog.txt -- 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/1934460 Title: ioremap: invalid physical address d5010fee0526b902 Status in linux-oem-5.10 package in Ubuntu: New Bug description: [4.554394] USB Video Class driver (1.1.1) [5.590819] ioremap: invalid physical address d5010fee0526b902 [5.590822] [ cut here ] [5.590826] WARNING: CPU: 0 PID: 355 at arch/x86/mm/ioremap.c:198 __ioremap_caller.cold+0xf/0x64 [5.590827] Modules linked in: uvcvideo btusb videobuf2_vmalloc btrtl videobuf2_memops btbcm videobuf2_v4l2 btintel videobuf2_common bluetooth videodev ecdh_generic mc ecc nls_iso8859_1 snd_hda_codec_ hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci snd_sof_intel_byt snd_sof_intel_ipc snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_xtensa_dsp snd_sof_intel_hda snd_sof snd_hda_ext_core sn d_soc_acpi_intel_match 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 mei_hdcp snd_soc_core intel_rapl_msr x86_pkg_temp_thermal intel_powerclamp snd_compress ac97_bus snd_pcm_dmaengine iwlmvm coretemp snd_pcm mac80211 dell_laptop snd_seq_midi snd_seq_midi_event kvm_intel snd_rawmidi joydev dell _smm_hwmon libarc4 snd_seq kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel snd_seq_device crypto_simd cryptd dell_wmi i915 snd_timer glue_helper dell_smbios dcdbas rapl intel_cstate iwlwifi [5.590861] drm_kms_helper dell_privacy_wmi cfg80211 cec input_leds rc_core i2c_algo_bit fb_sys_fops syscopyarea dell_wmi_sysman(+) sysfillrect ledtrig_audio snd serio_raw dell_wmi_descriptor efi_pst ore hid_multitouch wmi_bmof processor_thermal_device sysimgblt intel_rapl_common soundcore mei_me intel_soc_dts_iosf mei ucsi_acpi intel_pch_thermal typec_ucsi typec int3403_thermal int3402_thermal int34 00_thermal int340x_thermal_zone mac_hid intel_hid acpi_pad sparse_keymap acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul psmouse i2c_i801 nvme intel_lpss_pci nvme_core ahci i2c_smbus intel_lpss idma64 xhci_pci libahci virt_dma xhci_pci_renesas i2c_hid wmi hid video pinctrl_cannonlake [5.590891] CPU: 0 PID: 355 Comm: systemd-udevd Not tainted 5.10.0-1032-oem #33-Ubuntu [5.590892] Hardware name: Dell Inc. Inspiron 7380/, BIOS 1.1.0 08/08/2018 [5.590894] RIP: 0010:__ioremap_caller.cold+0xf/0x64 [5.590895] Code: 00 00 00 4c 89 e6 bf 04 00 00 00 0f 45 c2 0f bf d0 e8 aa a1 53 ff e9 ca bb 50 ff 48 89 fe 48 c7 c7 d8 eb 19 8b e8 4a 76 00 00 <0f> 0b 45 31 ed e9 03 c4 50 ff 48 8b 75 b8 44 8b 45 c4 44 89 e9 48 [5.590896] RSP: 0018:aab9406cf5f0 EFLAGS: 00010246 [5.590897] RAX: 0032 RBX: 000d5010fee0526b RCX: [5.590898] RDX: RSI: 8c46a7618a40 RDI: 8c46a7618a40 [5.590898] RBP: aab9406cf658 R08: 8c46a7618a40 R09: aab9406cf3c8 [5.590899] R10: 0001 R11: 0001 R12: d5010fee0526b902 [5.590899] R13: d5010fee0526b902 R14: 0008 R15: d5010fee0526b000 [5.590900] FS: 7f1bfda4f880() GS:8c46a760() knlGS: [5.590901] CS: 0010 DS: ES: CR0: 80050033 [5.590902] CR2: 7fc270b47cf0 CR3: 0001066ee004 CR4: 003706f0 [5.590902] Call Trace: [5.590906] ? acpi_os_map_iomem+0x1bc/0x1d0 [5.590907] ? _cond_resched+0x19/0x30 [5.590910] ioremap_cache+0x17/0x20 [5.590911] acpi_os_map_iomem+0x1bc/0x1d0 [5.590912] acpi_os_map_memory+0xe/0x10 [5.590915] acpi_ex_system_memory_space_handler+0x1fc/0x3aa [5.590916] acpi_ev_address_space_dispatch+0x34d/0x40e [5.590917] ? acpi_ex_prep_field_value+0x50a/0x50a [5.590919] acpi_ex_access_region+0x454/0x4ed [5.590920] acpi_ex_field_datum_io+0x18a/0x42d [5.590921] acpi_ex_extract_from_field+0xe7/0x320 [5.590922] ? acpi_ut_trace+0x28/0x6a [5.590924] acpi_ex_read_data_from_field+0x31f/0x371 [5.590925] acpi_ex_resolve_node_to_value+0x3a7/0x4dd [5.590926] acpi_ex_resolve_to_value+0x3c3/0x472 [5.590928] acpi_ds_evaluate_name_path+0xb1/0x169 [5.590930] ? acpi_db_single_step+0x1f/0x252 [5.590931] acpi_ds_exec_end_op+0x118/0x76b [5.590933] acpi_ps_parse_loop+0x84b/0x924 [5.590934] acpi_ps_parse_aml+0x1af/0x550 [5.590935] acpi_ps_execute_method+0x208/0x2ca [5.590936] acpi_ns_evaluate+0x34e/0x4f0 [5.590937] acpi_evaluate_object+0x18e/0x3b4 [5.590940] __query_block+0x184/0x1f0 [wmi] [
[Kernel-packages] [Bug 1934460] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1934460/+attachment/5508573/+files/CRDA.txt -- 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/1934460 Title: ioremap: invalid physical address d5010fee0526b902 Status in linux-oem-5.10 package in Ubuntu: New Bug description: [4.554394] USB Video Class driver (1.1.1) [5.590819] ioremap: invalid physical address d5010fee0526b902 [5.590822] [ cut here ] [5.590826] WARNING: CPU: 0 PID: 355 at arch/x86/mm/ioremap.c:198 __ioremap_caller.cold+0xf/0x64 [5.590827] Modules linked in: uvcvideo btusb videobuf2_vmalloc btrtl videobuf2_memops btbcm videobuf2_v4l2 btintel videobuf2_common bluetooth videodev ecdh_generic mc ecc nls_iso8859_1 snd_hda_codec_ hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci snd_sof_intel_byt snd_sof_intel_ipc snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_xtensa_dsp snd_sof_intel_hda snd_sof snd_hda_ext_core sn d_soc_acpi_intel_match 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 mei_hdcp snd_soc_core intel_rapl_msr x86_pkg_temp_thermal intel_powerclamp snd_compress ac97_bus snd_pcm_dmaengine iwlmvm coretemp snd_pcm mac80211 dell_laptop snd_seq_midi snd_seq_midi_event kvm_intel snd_rawmidi joydev dell _smm_hwmon libarc4 snd_seq kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel snd_seq_device crypto_simd cryptd dell_wmi i915 snd_timer glue_helper dell_smbios dcdbas rapl intel_cstate iwlwifi [5.590861] drm_kms_helper dell_privacy_wmi cfg80211 cec input_leds rc_core i2c_algo_bit fb_sys_fops syscopyarea dell_wmi_sysman(+) sysfillrect ledtrig_audio snd serio_raw dell_wmi_descriptor efi_pst ore hid_multitouch wmi_bmof processor_thermal_device sysimgblt intel_rapl_common soundcore mei_me intel_soc_dts_iosf mei ucsi_acpi intel_pch_thermal typec_ucsi typec int3403_thermal int3402_thermal int34 00_thermal int340x_thermal_zone mac_hid intel_hid acpi_pad sparse_keymap acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul psmouse i2c_i801 nvme intel_lpss_pci nvme_core ahci i2c_smbus intel_lpss idma64 xhci_pci libahci virt_dma xhci_pci_renesas i2c_hid wmi hid video pinctrl_cannonlake [5.590891] CPU: 0 PID: 355 Comm: systemd-udevd Not tainted 5.10.0-1032-oem #33-Ubuntu [5.590892] Hardware name: Dell Inc. Inspiron 7380/, BIOS 1.1.0 08/08/2018 [5.590894] RIP: 0010:__ioremap_caller.cold+0xf/0x64 [5.590895] Code: 00 00 00 4c 89 e6 bf 04 00 00 00 0f 45 c2 0f bf d0 e8 aa a1 53 ff e9 ca bb 50 ff 48 89 fe 48 c7 c7 d8 eb 19 8b e8 4a 76 00 00 <0f> 0b 45 31 ed e9 03 c4 50 ff 48 8b 75 b8 44 8b 45 c4 44 89 e9 48 [5.590896] RSP: 0018:aab9406cf5f0 EFLAGS: 00010246 [5.590897] RAX: 0032 RBX: 000d5010fee0526b RCX: [5.590898] RDX: RSI: 8c46a7618a40 RDI: 8c46a7618a40 [5.590898] RBP: aab9406cf658 R08: 8c46a7618a40 R09: aab9406cf3c8 [5.590899] R10: 0001 R11: 0001 R12: d5010fee0526b902 [5.590899] R13: d5010fee0526b902 R14: 0008 R15: d5010fee0526b000 [5.590900] FS: 7f1bfda4f880() GS:8c46a760() knlGS: [5.590901] CS: 0010 DS: ES: CR0: 80050033 [5.590902] CR2: 7fc270b47cf0 CR3: 0001066ee004 CR4: 003706f0 [5.590902] Call Trace: [5.590906] ? acpi_os_map_iomem+0x1bc/0x1d0 [5.590907] ? _cond_resched+0x19/0x30 [5.590910] ioremap_cache+0x17/0x20 [5.590911] acpi_os_map_iomem+0x1bc/0x1d0 [5.590912] acpi_os_map_memory+0xe/0x10 [5.590915] acpi_ex_system_memory_space_handler+0x1fc/0x3aa [5.590916] acpi_ev_address_space_dispatch+0x34d/0x40e [5.590917] ? acpi_ex_prep_field_value+0x50a/0x50a [5.590919] acpi_ex_access_region+0x454/0x4ed [5.590920] acpi_ex_field_datum_io+0x18a/0x42d [5.590921] acpi_ex_extract_from_field+0xe7/0x320 [5.590922] ? acpi_ut_trace+0x28/0x6a [5.590924] acpi_ex_read_data_from_field+0x31f/0x371 [5.590925] acpi_ex_resolve_node_to_value+0x3a7/0x4dd [5.590926] acpi_ex_resolve_to_value+0x3c3/0x472 [5.590928] acpi_ds_evaluate_name_path+0xb1/0x169 [5.590930] ? acpi_db_single_step+0x1f/0x252 [5.590931] acpi_ds_exec_end_op+0x118/0x76b [5.590933] acpi_ps_parse_loop+0x84b/0x924 [5.590934] acpi_ps_parse_aml+0x1af/0x550 [5.590935] acpi_ps_execute_method+0x208/0x2ca [5.590936] acpi_ns_evaluate+0x34e/0x4f0 [5.590937] acpi_evaluate_object+0x18e/0x3b4 [5.590940] __query_block+0x184/0x1f0 [wmi] [5.590942] ?
[Kernel-packages] [Bug 1934460] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1934460/+attachment/5508577/+files/Lspci-vt.txt -- 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/1934460 Title: ioremap: invalid physical address d5010fee0526b902 Status in linux-oem-5.10 package in Ubuntu: New Bug description: [4.554394] USB Video Class driver (1.1.1) [5.590819] ioremap: invalid physical address d5010fee0526b902 [5.590822] [ cut here ] [5.590826] WARNING: CPU: 0 PID: 355 at arch/x86/mm/ioremap.c:198 __ioremap_caller.cold+0xf/0x64 [5.590827] Modules linked in: uvcvideo btusb videobuf2_vmalloc btrtl videobuf2_memops btbcm videobuf2_v4l2 btintel videobuf2_common bluetooth videodev ecdh_generic mc ecc nls_iso8859_1 snd_hda_codec_ hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci snd_sof_intel_byt snd_sof_intel_ipc snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_xtensa_dsp snd_sof_intel_hda snd_sof snd_hda_ext_core sn d_soc_acpi_intel_match 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 mei_hdcp snd_soc_core intel_rapl_msr x86_pkg_temp_thermal intel_powerclamp snd_compress ac97_bus snd_pcm_dmaengine iwlmvm coretemp snd_pcm mac80211 dell_laptop snd_seq_midi snd_seq_midi_event kvm_intel snd_rawmidi joydev dell _smm_hwmon libarc4 snd_seq kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel snd_seq_device crypto_simd cryptd dell_wmi i915 snd_timer glue_helper dell_smbios dcdbas rapl intel_cstate iwlwifi [5.590861] drm_kms_helper dell_privacy_wmi cfg80211 cec input_leds rc_core i2c_algo_bit fb_sys_fops syscopyarea dell_wmi_sysman(+) sysfillrect ledtrig_audio snd serio_raw dell_wmi_descriptor efi_pst ore hid_multitouch wmi_bmof processor_thermal_device sysimgblt intel_rapl_common soundcore mei_me intel_soc_dts_iosf mei ucsi_acpi intel_pch_thermal typec_ucsi typec int3403_thermal int3402_thermal int34 00_thermal int340x_thermal_zone mac_hid intel_hid acpi_pad sparse_keymap acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul psmouse i2c_i801 nvme intel_lpss_pci nvme_core ahci i2c_smbus intel_lpss idma64 xhci_pci libahci virt_dma xhci_pci_renesas i2c_hid wmi hid video pinctrl_cannonlake [5.590891] CPU: 0 PID: 355 Comm: systemd-udevd Not tainted 5.10.0-1032-oem #33-Ubuntu [5.590892] Hardware name: Dell Inc. Inspiron 7380/, BIOS 1.1.0 08/08/2018 [5.590894] RIP: 0010:__ioremap_caller.cold+0xf/0x64 [5.590895] Code: 00 00 00 4c 89 e6 bf 04 00 00 00 0f 45 c2 0f bf d0 e8 aa a1 53 ff e9 ca bb 50 ff 48 89 fe 48 c7 c7 d8 eb 19 8b e8 4a 76 00 00 <0f> 0b 45 31 ed e9 03 c4 50 ff 48 8b 75 b8 44 8b 45 c4 44 89 e9 48 [5.590896] RSP: 0018:aab9406cf5f0 EFLAGS: 00010246 [5.590897] RAX: 0032 RBX: 000d5010fee0526b RCX: [5.590898] RDX: RSI: 8c46a7618a40 RDI: 8c46a7618a40 [5.590898] RBP: aab9406cf658 R08: 8c46a7618a40 R09: aab9406cf3c8 [5.590899] R10: 0001 R11: 0001 R12: d5010fee0526b902 [5.590899] R13: d5010fee0526b902 R14: 0008 R15: d5010fee0526b000 [5.590900] FS: 7f1bfda4f880() GS:8c46a760() knlGS: [5.590901] CS: 0010 DS: ES: CR0: 80050033 [5.590902] CR2: 7fc270b47cf0 CR3: 0001066ee004 CR4: 003706f0 [5.590902] Call Trace: [5.590906] ? acpi_os_map_iomem+0x1bc/0x1d0 [5.590907] ? _cond_resched+0x19/0x30 [5.590910] ioremap_cache+0x17/0x20 [5.590911] acpi_os_map_iomem+0x1bc/0x1d0 [5.590912] acpi_os_map_memory+0xe/0x10 [5.590915] acpi_ex_system_memory_space_handler+0x1fc/0x3aa [5.590916] acpi_ev_address_space_dispatch+0x34d/0x40e [5.590917] ? acpi_ex_prep_field_value+0x50a/0x50a [5.590919] acpi_ex_access_region+0x454/0x4ed [5.590920] acpi_ex_field_datum_io+0x18a/0x42d [5.590921] acpi_ex_extract_from_field+0xe7/0x320 [5.590922] ? acpi_ut_trace+0x28/0x6a [5.590924] acpi_ex_read_data_from_field+0x31f/0x371 [5.590925] acpi_ex_resolve_node_to_value+0x3a7/0x4dd [5.590926] acpi_ex_resolve_to_value+0x3c3/0x472 [5.590928] acpi_ds_evaluate_name_path+0xb1/0x169 [5.590930] ? acpi_db_single_step+0x1f/0x252 [5.590931] acpi_ds_exec_end_op+0x118/0x76b [5.590933] acpi_ps_parse_loop+0x84b/0x924 [5.590934] acpi_ps_parse_aml+0x1af/0x550 [5.590935] acpi_ps_execute_method+0x208/0x2ca [5.590936] acpi_ns_evaluate+0x34e/0x4f0 [5.590937] acpi_evaluate_object+0x18e/0x3b4 [5.590940] __query_block+0x184/0x1f0 [wmi] [5.590942]
[Kernel-packages] [Bug 1934461] Re: Nvidia driver 460 fails in install on 21.04
** Attachment added: "Screenshot from 2021-07-01 22-55-12.png" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1934461/+attachment/5508571/+files/Screenshot%20from%202021-07-01%2022-55-12.png -- 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/1934461 Title: Nvidia driver 460 fails in install on 21.04 Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: I cannot use nvidia. If I choose nvidia, then I have a black screen and I cannot log in. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nvidia-driver-460 (not installed) ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 2 10:27:44 2021 InstallationDate: Installed on 2021-06-25 (6 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: nvidia-graphics-drivers-460 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1934461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934460] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1934460/+attachment/5508585/+files/UdevDb.txt -- 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/1934460 Title: ioremap: invalid physical address d5010fee0526b902 Status in linux-oem-5.10 package in Ubuntu: New Bug description: [4.554394] USB Video Class driver (1.1.1) [5.590819] ioremap: invalid physical address d5010fee0526b902 [5.590822] [ cut here ] [5.590826] WARNING: CPU: 0 PID: 355 at arch/x86/mm/ioremap.c:198 __ioremap_caller.cold+0xf/0x64 [5.590827] Modules linked in: uvcvideo btusb videobuf2_vmalloc btrtl videobuf2_memops btbcm videobuf2_v4l2 btintel videobuf2_common bluetooth videodev ecdh_generic mc ecc nls_iso8859_1 snd_hda_codec_ hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci snd_sof_intel_byt snd_sof_intel_ipc snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_xtensa_dsp snd_sof_intel_hda snd_sof snd_hda_ext_core sn d_soc_acpi_intel_match 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 mei_hdcp snd_soc_core intel_rapl_msr x86_pkg_temp_thermal intel_powerclamp snd_compress ac97_bus snd_pcm_dmaengine iwlmvm coretemp snd_pcm mac80211 dell_laptop snd_seq_midi snd_seq_midi_event kvm_intel snd_rawmidi joydev dell _smm_hwmon libarc4 snd_seq kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel snd_seq_device crypto_simd cryptd dell_wmi i915 snd_timer glue_helper dell_smbios dcdbas rapl intel_cstate iwlwifi [5.590861] drm_kms_helper dell_privacy_wmi cfg80211 cec input_leds rc_core i2c_algo_bit fb_sys_fops syscopyarea dell_wmi_sysman(+) sysfillrect ledtrig_audio snd serio_raw dell_wmi_descriptor efi_pst ore hid_multitouch wmi_bmof processor_thermal_device sysimgblt intel_rapl_common soundcore mei_me intel_soc_dts_iosf mei ucsi_acpi intel_pch_thermal typec_ucsi typec int3403_thermal int3402_thermal int34 00_thermal int340x_thermal_zone mac_hid intel_hid acpi_pad sparse_keymap acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul psmouse i2c_i801 nvme intel_lpss_pci nvme_core ahci i2c_smbus intel_lpss idma64 xhci_pci libahci virt_dma xhci_pci_renesas i2c_hid wmi hid video pinctrl_cannonlake [5.590891] CPU: 0 PID: 355 Comm: systemd-udevd Not tainted 5.10.0-1032-oem #33-Ubuntu [5.590892] Hardware name: Dell Inc. Inspiron 7380/, BIOS 1.1.0 08/08/2018 [5.590894] RIP: 0010:__ioremap_caller.cold+0xf/0x64 [5.590895] Code: 00 00 00 4c 89 e6 bf 04 00 00 00 0f 45 c2 0f bf d0 e8 aa a1 53 ff e9 ca bb 50 ff 48 89 fe 48 c7 c7 d8 eb 19 8b e8 4a 76 00 00 <0f> 0b 45 31 ed e9 03 c4 50 ff 48 8b 75 b8 44 8b 45 c4 44 89 e9 48 [5.590896] RSP: 0018:aab9406cf5f0 EFLAGS: 00010246 [5.590897] RAX: 0032 RBX: 000d5010fee0526b RCX: [5.590898] RDX: RSI: 8c46a7618a40 RDI: 8c46a7618a40 [5.590898] RBP: aab9406cf658 R08: 8c46a7618a40 R09: aab9406cf3c8 [5.590899] R10: 0001 R11: 0001 R12: d5010fee0526b902 [5.590899] R13: d5010fee0526b902 R14: 0008 R15: d5010fee0526b000 [5.590900] FS: 7f1bfda4f880() GS:8c46a760() knlGS: [5.590901] CS: 0010 DS: ES: CR0: 80050033 [5.590902] CR2: 7fc270b47cf0 CR3: 0001066ee004 CR4: 003706f0 [5.590902] Call Trace: [5.590906] ? acpi_os_map_iomem+0x1bc/0x1d0 [5.590907] ? _cond_resched+0x19/0x30 [5.590910] ioremap_cache+0x17/0x20 [5.590911] acpi_os_map_iomem+0x1bc/0x1d0 [5.590912] acpi_os_map_memory+0xe/0x10 [5.590915] acpi_ex_system_memory_space_handler+0x1fc/0x3aa [5.590916] acpi_ev_address_space_dispatch+0x34d/0x40e [5.590917] ? acpi_ex_prep_field_value+0x50a/0x50a [5.590919] acpi_ex_access_region+0x454/0x4ed [5.590920] acpi_ex_field_datum_io+0x18a/0x42d [5.590921] acpi_ex_extract_from_field+0xe7/0x320 [5.590922] ? acpi_ut_trace+0x28/0x6a [5.590924] acpi_ex_read_data_from_field+0x31f/0x371 [5.590925] acpi_ex_resolve_node_to_value+0x3a7/0x4dd [5.590926] acpi_ex_resolve_to_value+0x3c3/0x472 [5.590928] acpi_ds_evaluate_name_path+0xb1/0x169 [5.590930] ? acpi_db_single_step+0x1f/0x252 [5.590931] acpi_ds_exec_end_op+0x118/0x76b [5.590933] acpi_ps_parse_loop+0x84b/0x924 [5.590934] acpi_ps_parse_aml+0x1af/0x550 [5.590935] acpi_ps_execute_method+0x208/0x2ca [5.590936] acpi_ns_evaluate+0x34e/0x4f0 [5.590937] acpi_evaluate_object+0x18e/0x3b4 [5.590940] __query_block+0x184/0x1f0 [wmi] [5.590942] ?
[Kernel-packages] [Bug 1934460] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1934460/+attachment/5508575/+files/IwConfig.txt -- 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/1934460 Title: ioremap: invalid physical address d5010fee0526b902 Status in linux-oem-5.10 package in Ubuntu: New Bug description: [4.554394] USB Video Class driver (1.1.1) [5.590819] ioremap: invalid physical address d5010fee0526b902 [5.590822] [ cut here ] [5.590826] WARNING: CPU: 0 PID: 355 at arch/x86/mm/ioremap.c:198 __ioremap_caller.cold+0xf/0x64 [5.590827] Modules linked in: uvcvideo btusb videobuf2_vmalloc btrtl videobuf2_memops btbcm videobuf2_v4l2 btintel videobuf2_common bluetooth videodev ecdh_generic mc ecc nls_iso8859_1 snd_hda_codec_ hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci snd_sof_intel_byt snd_sof_intel_ipc snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_xtensa_dsp snd_sof_intel_hda snd_sof snd_hda_ext_core sn d_soc_acpi_intel_match 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 mei_hdcp snd_soc_core intel_rapl_msr x86_pkg_temp_thermal intel_powerclamp snd_compress ac97_bus snd_pcm_dmaengine iwlmvm coretemp snd_pcm mac80211 dell_laptop snd_seq_midi snd_seq_midi_event kvm_intel snd_rawmidi joydev dell _smm_hwmon libarc4 snd_seq kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel snd_seq_device crypto_simd cryptd dell_wmi i915 snd_timer glue_helper dell_smbios dcdbas rapl intel_cstate iwlwifi [5.590861] drm_kms_helper dell_privacy_wmi cfg80211 cec input_leds rc_core i2c_algo_bit fb_sys_fops syscopyarea dell_wmi_sysman(+) sysfillrect ledtrig_audio snd serio_raw dell_wmi_descriptor efi_pst ore hid_multitouch wmi_bmof processor_thermal_device sysimgblt intel_rapl_common soundcore mei_me intel_soc_dts_iosf mei ucsi_acpi intel_pch_thermal typec_ucsi typec int3403_thermal int3402_thermal int34 00_thermal int340x_thermal_zone mac_hid intel_hid acpi_pad sparse_keymap acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul psmouse i2c_i801 nvme intel_lpss_pci nvme_core ahci i2c_smbus intel_lpss idma64 xhci_pci libahci virt_dma xhci_pci_renesas i2c_hid wmi hid video pinctrl_cannonlake [5.590891] CPU: 0 PID: 355 Comm: systemd-udevd Not tainted 5.10.0-1032-oem #33-Ubuntu [5.590892] Hardware name: Dell Inc. Inspiron 7380/, BIOS 1.1.0 08/08/2018 [5.590894] RIP: 0010:__ioremap_caller.cold+0xf/0x64 [5.590895] Code: 00 00 00 4c 89 e6 bf 04 00 00 00 0f 45 c2 0f bf d0 e8 aa a1 53 ff e9 ca bb 50 ff 48 89 fe 48 c7 c7 d8 eb 19 8b e8 4a 76 00 00 <0f> 0b 45 31 ed e9 03 c4 50 ff 48 8b 75 b8 44 8b 45 c4 44 89 e9 48 [5.590896] RSP: 0018:aab9406cf5f0 EFLAGS: 00010246 [5.590897] RAX: 0032 RBX: 000d5010fee0526b RCX: [5.590898] RDX: RSI: 8c46a7618a40 RDI: 8c46a7618a40 [5.590898] RBP: aab9406cf658 R08: 8c46a7618a40 R09: aab9406cf3c8 [5.590899] R10: 0001 R11: 0001 R12: d5010fee0526b902 [5.590899] R13: d5010fee0526b902 R14: 0008 R15: d5010fee0526b000 [5.590900] FS: 7f1bfda4f880() GS:8c46a760() knlGS: [5.590901] CS: 0010 DS: ES: CR0: 80050033 [5.590902] CR2: 7fc270b47cf0 CR3: 0001066ee004 CR4: 003706f0 [5.590902] Call Trace: [5.590906] ? acpi_os_map_iomem+0x1bc/0x1d0 [5.590907] ? _cond_resched+0x19/0x30 [5.590910] ioremap_cache+0x17/0x20 [5.590911] acpi_os_map_iomem+0x1bc/0x1d0 [5.590912] acpi_os_map_memory+0xe/0x10 [5.590915] acpi_ex_system_memory_space_handler+0x1fc/0x3aa [5.590916] acpi_ev_address_space_dispatch+0x34d/0x40e [5.590917] ? acpi_ex_prep_field_value+0x50a/0x50a [5.590919] acpi_ex_access_region+0x454/0x4ed [5.590920] acpi_ex_field_datum_io+0x18a/0x42d [5.590921] acpi_ex_extract_from_field+0xe7/0x320 [5.590922] ? acpi_ut_trace+0x28/0x6a [5.590924] acpi_ex_read_data_from_field+0x31f/0x371 [5.590925] acpi_ex_resolve_node_to_value+0x3a7/0x4dd [5.590926] acpi_ex_resolve_to_value+0x3c3/0x472 [5.590928] acpi_ds_evaluate_name_path+0xb1/0x169 [5.590930] ? acpi_db_single_step+0x1f/0x252 [5.590931] acpi_ds_exec_end_op+0x118/0x76b [5.590933] acpi_ps_parse_loop+0x84b/0x924 [5.590934] acpi_ps_parse_aml+0x1af/0x550 [5.590935] acpi_ps_execute_method+0x208/0x2ca [5.590936] acpi_ns_evaluate+0x34e/0x4f0 [5.590937] acpi_evaluate_object+0x18e/0x3b4 [5.590940] __query_block+0x184/0x1f0 [wmi] [5.590942]
[Kernel-packages] [Bug 1934460] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1934460/+attachment/5508579/+files/Lsusb-v.txt -- 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/1934460 Title: ioremap: invalid physical address d5010fee0526b902 Status in linux-oem-5.10 package in Ubuntu: New Bug description: [4.554394] USB Video Class driver (1.1.1) [5.590819] ioremap: invalid physical address d5010fee0526b902 [5.590822] [ cut here ] [5.590826] WARNING: CPU: 0 PID: 355 at arch/x86/mm/ioremap.c:198 __ioremap_caller.cold+0xf/0x64 [5.590827] Modules linked in: uvcvideo btusb videobuf2_vmalloc btrtl videobuf2_memops btbcm videobuf2_v4l2 btintel videobuf2_common bluetooth videodev ecdh_generic mc ecc nls_iso8859_1 snd_hda_codec_ hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci snd_sof_intel_byt snd_sof_intel_ipc snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_xtensa_dsp snd_sof_intel_hda snd_sof snd_hda_ext_core sn d_soc_acpi_intel_match 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 mei_hdcp snd_soc_core intel_rapl_msr x86_pkg_temp_thermal intel_powerclamp snd_compress ac97_bus snd_pcm_dmaengine iwlmvm coretemp snd_pcm mac80211 dell_laptop snd_seq_midi snd_seq_midi_event kvm_intel snd_rawmidi joydev dell _smm_hwmon libarc4 snd_seq kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel snd_seq_device crypto_simd cryptd dell_wmi i915 snd_timer glue_helper dell_smbios dcdbas rapl intel_cstate iwlwifi [5.590861] drm_kms_helper dell_privacy_wmi cfg80211 cec input_leds rc_core i2c_algo_bit fb_sys_fops syscopyarea dell_wmi_sysman(+) sysfillrect ledtrig_audio snd serio_raw dell_wmi_descriptor efi_pst ore hid_multitouch wmi_bmof processor_thermal_device sysimgblt intel_rapl_common soundcore mei_me intel_soc_dts_iosf mei ucsi_acpi intel_pch_thermal typec_ucsi typec int3403_thermal int3402_thermal int34 00_thermal int340x_thermal_zone mac_hid intel_hid acpi_pad sparse_keymap acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul psmouse i2c_i801 nvme intel_lpss_pci nvme_core ahci i2c_smbus intel_lpss idma64 xhci_pci libahci virt_dma xhci_pci_renesas i2c_hid wmi hid video pinctrl_cannonlake [5.590891] CPU: 0 PID: 355 Comm: systemd-udevd Not tainted 5.10.0-1032-oem #33-Ubuntu [5.590892] Hardware name: Dell Inc. Inspiron 7380/, BIOS 1.1.0 08/08/2018 [5.590894] RIP: 0010:__ioremap_caller.cold+0xf/0x64 [5.590895] Code: 00 00 00 4c 89 e6 bf 04 00 00 00 0f 45 c2 0f bf d0 e8 aa a1 53 ff e9 ca bb 50 ff 48 89 fe 48 c7 c7 d8 eb 19 8b e8 4a 76 00 00 <0f> 0b 45 31 ed e9 03 c4 50 ff 48 8b 75 b8 44 8b 45 c4 44 89 e9 48 [5.590896] RSP: 0018:aab9406cf5f0 EFLAGS: 00010246 [5.590897] RAX: 0032 RBX: 000d5010fee0526b RCX: [5.590898] RDX: RSI: 8c46a7618a40 RDI: 8c46a7618a40 [5.590898] RBP: aab9406cf658 R08: 8c46a7618a40 R09: aab9406cf3c8 [5.590899] R10: 0001 R11: 0001 R12: d5010fee0526b902 [5.590899] R13: d5010fee0526b902 R14: 0008 R15: d5010fee0526b000 [5.590900] FS: 7f1bfda4f880() GS:8c46a760() knlGS: [5.590901] CS: 0010 DS: ES: CR0: 80050033 [5.590902] CR2: 7fc270b47cf0 CR3: 0001066ee004 CR4: 003706f0 [5.590902] Call Trace: [5.590906] ? acpi_os_map_iomem+0x1bc/0x1d0 [5.590907] ? _cond_resched+0x19/0x30 [5.590910] ioremap_cache+0x17/0x20 [5.590911] acpi_os_map_iomem+0x1bc/0x1d0 [5.590912] acpi_os_map_memory+0xe/0x10 [5.590915] acpi_ex_system_memory_space_handler+0x1fc/0x3aa [5.590916] acpi_ev_address_space_dispatch+0x34d/0x40e [5.590917] ? acpi_ex_prep_field_value+0x50a/0x50a [5.590919] acpi_ex_access_region+0x454/0x4ed [5.590920] acpi_ex_field_datum_io+0x18a/0x42d [5.590921] acpi_ex_extract_from_field+0xe7/0x320 [5.590922] ? acpi_ut_trace+0x28/0x6a [5.590924] acpi_ex_read_data_from_field+0x31f/0x371 [5.590925] acpi_ex_resolve_node_to_value+0x3a7/0x4dd [5.590926] acpi_ex_resolve_to_value+0x3c3/0x472 [5.590928] acpi_ds_evaluate_name_path+0xb1/0x169 [5.590930] ? acpi_db_single_step+0x1f/0x252 [5.590931] acpi_ds_exec_end_op+0x118/0x76b [5.590933] acpi_ps_parse_loop+0x84b/0x924 [5.590934] acpi_ps_parse_aml+0x1af/0x550 [5.590935] acpi_ps_execute_method+0x208/0x2ca [5.590936] acpi_ns_evaluate+0x34e/0x4f0 [5.590937] acpi_evaluate_object+0x18e/0x3b4 [5.590940] __query_block+0x184/0x1f0 [wmi] [5.590942] ?
[Kernel-packages] [Bug 1934460] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1934460/+attachment/5508574/+files/CurrentDmesg.txt -- 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/1934460 Title: ioremap: invalid physical address d5010fee0526b902 Status in linux-oem-5.10 package in Ubuntu: New Bug description: [4.554394] USB Video Class driver (1.1.1) [5.590819] ioremap: invalid physical address d5010fee0526b902 [5.590822] [ cut here ] [5.590826] WARNING: CPU: 0 PID: 355 at arch/x86/mm/ioremap.c:198 __ioremap_caller.cold+0xf/0x64 [5.590827] Modules linked in: uvcvideo btusb videobuf2_vmalloc btrtl videobuf2_memops btbcm videobuf2_v4l2 btintel videobuf2_common bluetooth videodev ecdh_generic mc ecc nls_iso8859_1 snd_hda_codec_ hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci snd_sof_intel_byt snd_sof_intel_ipc snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_xtensa_dsp snd_sof_intel_hda snd_sof snd_hda_ext_core sn d_soc_acpi_intel_match 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 mei_hdcp snd_soc_core intel_rapl_msr x86_pkg_temp_thermal intel_powerclamp snd_compress ac97_bus snd_pcm_dmaengine iwlmvm coretemp snd_pcm mac80211 dell_laptop snd_seq_midi snd_seq_midi_event kvm_intel snd_rawmidi joydev dell _smm_hwmon libarc4 snd_seq kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel snd_seq_device crypto_simd cryptd dell_wmi i915 snd_timer glue_helper dell_smbios dcdbas rapl intel_cstate iwlwifi [5.590861] drm_kms_helper dell_privacy_wmi cfg80211 cec input_leds rc_core i2c_algo_bit fb_sys_fops syscopyarea dell_wmi_sysman(+) sysfillrect ledtrig_audio snd serio_raw dell_wmi_descriptor efi_pst ore hid_multitouch wmi_bmof processor_thermal_device sysimgblt intel_rapl_common soundcore mei_me intel_soc_dts_iosf mei ucsi_acpi intel_pch_thermal typec_ucsi typec int3403_thermal int3402_thermal int34 00_thermal int340x_thermal_zone mac_hid intel_hid acpi_pad sparse_keymap acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul psmouse i2c_i801 nvme intel_lpss_pci nvme_core ahci i2c_smbus intel_lpss idma64 xhci_pci libahci virt_dma xhci_pci_renesas i2c_hid wmi hid video pinctrl_cannonlake [5.590891] CPU: 0 PID: 355 Comm: systemd-udevd Not tainted 5.10.0-1032-oem #33-Ubuntu [5.590892] Hardware name: Dell Inc. Inspiron 7380/, BIOS 1.1.0 08/08/2018 [5.590894] RIP: 0010:__ioremap_caller.cold+0xf/0x64 [5.590895] Code: 00 00 00 4c 89 e6 bf 04 00 00 00 0f 45 c2 0f bf d0 e8 aa a1 53 ff e9 ca bb 50 ff 48 89 fe 48 c7 c7 d8 eb 19 8b e8 4a 76 00 00 <0f> 0b 45 31 ed e9 03 c4 50 ff 48 8b 75 b8 44 8b 45 c4 44 89 e9 48 [5.590896] RSP: 0018:aab9406cf5f0 EFLAGS: 00010246 [5.590897] RAX: 0032 RBX: 000d5010fee0526b RCX: [5.590898] RDX: RSI: 8c46a7618a40 RDI: 8c46a7618a40 [5.590898] RBP: aab9406cf658 R08: 8c46a7618a40 R09: aab9406cf3c8 [5.590899] R10: 0001 R11: 0001 R12: d5010fee0526b902 [5.590899] R13: d5010fee0526b902 R14: 0008 R15: d5010fee0526b000 [5.590900] FS: 7f1bfda4f880() GS:8c46a760() knlGS: [5.590901] CS: 0010 DS: ES: CR0: 80050033 [5.590902] CR2: 7fc270b47cf0 CR3: 0001066ee004 CR4: 003706f0 [5.590902] Call Trace: [5.590906] ? acpi_os_map_iomem+0x1bc/0x1d0 [5.590907] ? _cond_resched+0x19/0x30 [5.590910] ioremap_cache+0x17/0x20 [5.590911] acpi_os_map_iomem+0x1bc/0x1d0 [5.590912] acpi_os_map_memory+0xe/0x10 [5.590915] acpi_ex_system_memory_space_handler+0x1fc/0x3aa [5.590916] acpi_ev_address_space_dispatch+0x34d/0x40e [5.590917] ? acpi_ex_prep_field_value+0x50a/0x50a [5.590919] acpi_ex_access_region+0x454/0x4ed [5.590920] acpi_ex_field_datum_io+0x18a/0x42d [5.590921] acpi_ex_extract_from_field+0xe7/0x320 [5.590922] ? acpi_ut_trace+0x28/0x6a [5.590924] acpi_ex_read_data_from_field+0x31f/0x371 [5.590925] acpi_ex_resolve_node_to_value+0x3a7/0x4dd [5.590926] acpi_ex_resolve_to_value+0x3c3/0x472 [5.590928] acpi_ds_evaluate_name_path+0xb1/0x169 [5.590930] ? acpi_db_single_step+0x1f/0x252 [5.590931] acpi_ds_exec_end_op+0x118/0x76b [5.590933] acpi_ps_parse_loop+0x84b/0x924 [5.590934] acpi_ps_parse_aml+0x1af/0x550 [5.590935] acpi_ps_execute_method+0x208/0x2ca [5.590936] acpi_ns_evaluate+0x34e/0x4f0 [5.590937] acpi_evaluate_object+0x18e/0x3b4 [5.590940] __query_block+0x184/0x1f0 [wmi] [
[Kernel-packages] [Bug 1934460] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1934460/+attachment/5508584/+files/RfKill.txt -- 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/1934460 Title: ioremap: invalid physical address d5010fee0526b902 Status in linux-oem-5.10 package in Ubuntu: New Bug description: [4.554394] USB Video Class driver (1.1.1) [5.590819] ioremap: invalid physical address d5010fee0526b902 [5.590822] [ cut here ] [5.590826] WARNING: CPU: 0 PID: 355 at arch/x86/mm/ioremap.c:198 __ioremap_caller.cold+0xf/0x64 [5.590827] Modules linked in: uvcvideo btusb videobuf2_vmalloc btrtl videobuf2_memops btbcm videobuf2_v4l2 btintel videobuf2_common bluetooth videodev ecdh_generic mc ecc nls_iso8859_1 snd_hda_codec_ hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci snd_sof_intel_byt snd_sof_intel_ipc snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_xtensa_dsp snd_sof_intel_hda snd_sof snd_hda_ext_core sn d_soc_acpi_intel_match 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 mei_hdcp snd_soc_core intel_rapl_msr x86_pkg_temp_thermal intel_powerclamp snd_compress ac97_bus snd_pcm_dmaengine iwlmvm coretemp snd_pcm mac80211 dell_laptop snd_seq_midi snd_seq_midi_event kvm_intel snd_rawmidi joydev dell _smm_hwmon libarc4 snd_seq kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel snd_seq_device crypto_simd cryptd dell_wmi i915 snd_timer glue_helper dell_smbios dcdbas rapl intel_cstate iwlwifi [5.590861] drm_kms_helper dell_privacy_wmi cfg80211 cec input_leds rc_core i2c_algo_bit fb_sys_fops syscopyarea dell_wmi_sysman(+) sysfillrect ledtrig_audio snd serio_raw dell_wmi_descriptor efi_pst ore hid_multitouch wmi_bmof processor_thermal_device sysimgblt intel_rapl_common soundcore mei_me intel_soc_dts_iosf mei ucsi_acpi intel_pch_thermal typec_ucsi typec int3403_thermal int3402_thermal int34 00_thermal int340x_thermal_zone mac_hid intel_hid acpi_pad sparse_keymap acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul psmouse i2c_i801 nvme intel_lpss_pci nvme_core ahci i2c_smbus intel_lpss idma64 xhci_pci libahci virt_dma xhci_pci_renesas i2c_hid wmi hid video pinctrl_cannonlake [5.590891] CPU: 0 PID: 355 Comm: systemd-udevd Not tainted 5.10.0-1032-oem #33-Ubuntu [5.590892] Hardware name: Dell Inc. Inspiron 7380/, BIOS 1.1.0 08/08/2018 [5.590894] RIP: 0010:__ioremap_caller.cold+0xf/0x64 [5.590895] Code: 00 00 00 4c 89 e6 bf 04 00 00 00 0f 45 c2 0f bf d0 e8 aa a1 53 ff e9 ca bb 50 ff 48 89 fe 48 c7 c7 d8 eb 19 8b e8 4a 76 00 00 <0f> 0b 45 31 ed e9 03 c4 50 ff 48 8b 75 b8 44 8b 45 c4 44 89 e9 48 [5.590896] RSP: 0018:aab9406cf5f0 EFLAGS: 00010246 [5.590897] RAX: 0032 RBX: 000d5010fee0526b RCX: [5.590898] RDX: RSI: 8c46a7618a40 RDI: 8c46a7618a40 [5.590898] RBP: aab9406cf658 R08: 8c46a7618a40 R09: aab9406cf3c8 [5.590899] R10: 0001 R11: 0001 R12: d5010fee0526b902 [5.590899] R13: d5010fee0526b902 R14: 0008 R15: d5010fee0526b000 [5.590900] FS: 7f1bfda4f880() GS:8c46a760() knlGS: [5.590901] CS: 0010 DS: ES: CR0: 80050033 [5.590902] CR2: 7fc270b47cf0 CR3: 0001066ee004 CR4: 003706f0 [5.590902] Call Trace: [5.590906] ? acpi_os_map_iomem+0x1bc/0x1d0 [5.590907] ? _cond_resched+0x19/0x30 [5.590910] ioremap_cache+0x17/0x20 [5.590911] acpi_os_map_iomem+0x1bc/0x1d0 [5.590912] acpi_os_map_memory+0xe/0x10 [5.590915] acpi_ex_system_memory_space_handler+0x1fc/0x3aa [5.590916] acpi_ev_address_space_dispatch+0x34d/0x40e [5.590917] ? acpi_ex_prep_field_value+0x50a/0x50a [5.590919] acpi_ex_access_region+0x454/0x4ed [5.590920] acpi_ex_field_datum_io+0x18a/0x42d [5.590921] acpi_ex_extract_from_field+0xe7/0x320 [5.590922] ? acpi_ut_trace+0x28/0x6a [5.590924] acpi_ex_read_data_from_field+0x31f/0x371 [5.590925] acpi_ex_resolve_node_to_value+0x3a7/0x4dd [5.590926] acpi_ex_resolve_to_value+0x3c3/0x472 [5.590928] acpi_ds_evaluate_name_path+0xb1/0x169 [5.590930] ? acpi_db_single_step+0x1f/0x252 [5.590931] acpi_ds_exec_end_op+0x118/0x76b [5.590933] acpi_ps_parse_loop+0x84b/0x924 [5.590934] acpi_ps_parse_aml+0x1af/0x550 [5.590935] acpi_ps_execute_method+0x208/0x2ca [5.590936] acpi_ns_evaluate+0x34e/0x4f0 [5.590937] acpi_evaluate_object+0x18e/0x3b4 [5.590940] __query_block+0x184/0x1f0 [wmi] [5.590942] ?
[Kernel-packages] [Bug 1934460] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1934460/+attachment/5508581/+files/ProcCpuinfoMinimal.txt -- 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/1934460 Title: ioremap: invalid physical address d5010fee0526b902 Status in linux-oem-5.10 package in Ubuntu: New Bug description: [4.554394] USB Video Class driver (1.1.1) [5.590819] ioremap: invalid physical address d5010fee0526b902 [5.590822] [ cut here ] [5.590826] WARNING: CPU: 0 PID: 355 at arch/x86/mm/ioremap.c:198 __ioremap_caller.cold+0xf/0x64 [5.590827] Modules linked in: uvcvideo btusb videobuf2_vmalloc btrtl videobuf2_memops btbcm videobuf2_v4l2 btintel videobuf2_common bluetooth videodev ecdh_generic mc ecc nls_iso8859_1 snd_hda_codec_ hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci snd_sof_intel_byt snd_sof_intel_ipc snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_xtensa_dsp snd_sof_intel_hda snd_sof snd_hda_ext_core sn d_soc_acpi_intel_match 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 mei_hdcp snd_soc_core intel_rapl_msr x86_pkg_temp_thermal intel_powerclamp snd_compress ac97_bus snd_pcm_dmaengine iwlmvm coretemp snd_pcm mac80211 dell_laptop snd_seq_midi snd_seq_midi_event kvm_intel snd_rawmidi joydev dell _smm_hwmon libarc4 snd_seq kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel snd_seq_device crypto_simd cryptd dell_wmi i915 snd_timer glue_helper dell_smbios dcdbas rapl intel_cstate iwlwifi [5.590861] drm_kms_helper dell_privacy_wmi cfg80211 cec input_leds rc_core i2c_algo_bit fb_sys_fops syscopyarea dell_wmi_sysman(+) sysfillrect ledtrig_audio snd serio_raw dell_wmi_descriptor efi_pst ore hid_multitouch wmi_bmof processor_thermal_device sysimgblt intel_rapl_common soundcore mei_me intel_soc_dts_iosf mei ucsi_acpi intel_pch_thermal typec_ucsi typec int3403_thermal int3402_thermal int34 00_thermal int340x_thermal_zone mac_hid intel_hid acpi_pad sparse_keymap acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul psmouse i2c_i801 nvme intel_lpss_pci nvme_core ahci i2c_smbus intel_lpss idma64 xhci_pci libahci virt_dma xhci_pci_renesas i2c_hid wmi hid video pinctrl_cannonlake [5.590891] CPU: 0 PID: 355 Comm: systemd-udevd Not tainted 5.10.0-1032-oem #33-Ubuntu [5.590892] Hardware name: Dell Inc. Inspiron 7380/, BIOS 1.1.0 08/08/2018 [5.590894] RIP: 0010:__ioremap_caller.cold+0xf/0x64 [5.590895] Code: 00 00 00 4c 89 e6 bf 04 00 00 00 0f 45 c2 0f bf d0 e8 aa a1 53 ff e9 ca bb 50 ff 48 89 fe 48 c7 c7 d8 eb 19 8b e8 4a 76 00 00 <0f> 0b 45 31 ed e9 03 c4 50 ff 48 8b 75 b8 44 8b 45 c4 44 89 e9 48 [5.590896] RSP: 0018:aab9406cf5f0 EFLAGS: 00010246 [5.590897] RAX: 0032 RBX: 000d5010fee0526b RCX: [5.590898] RDX: RSI: 8c46a7618a40 RDI: 8c46a7618a40 [5.590898] RBP: aab9406cf658 R08: 8c46a7618a40 R09: aab9406cf3c8 [5.590899] R10: 0001 R11: 0001 R12: d5010fee0526b902 [5.590899] R13: d5010fee0526b902 R14: 0008 R15: d5010fee0526b000 [5.590900] FS: 7f1bfda4f880() GS:8c46a760() knlGS: [5.590901] CS: 0010 DS: ES: CR0: 80050033 [5.590902] CR2: 7fc270b47cf0 CR3: 0001066ee004 CR4: 003706f0 [5.590902] Call Trace: [5.590906] ? acpi_os_map_iomem+0x1bc/0x1d0 [5.590907] ? _cond_resched+0x19/0x30 [5.590910] ioremap_cache+0x17/0x20 [5.590911] acpi_os_map_iomem+0x1bc/0x1d0 [5.590912] acpi_os_map_memory+0xe/0x10 [5.590915] acpi_ex_system_memory_space_handler+0x1fc/0x3aa [5.590916] acpi_ev_address_space_dispatch+0x34d/0x40e [5.590917] ? acpi_ex_prep_field_value+0x50a/0x50a [5.590919] acpi_ex_access_region+0x454/0x4ed [5.590920] acpi_ex_field_datum_io+0x18a/0x42d [5.590921] acpi_ex_extract_from_field+0xe7/0x320 [5.590922] ? acpi_ut_trace+0x28/0x6a [5.590924] acpi_ex_read_data_from_field+0x31f/0x371 [5.590925] acpi_ex_resolve_node_to_value+0x3a7/0x4dd [5.590926] acpi_ex_resolve_to_value+0x3c3/0x472 [5.590928] acpi_ds_evaluate_name_path+0xb1/0x169 [5.590930] ? acpi_db_single_step+0x1f/0x252 [5.590931] acpi_ds_exec_end_op+0x118/0x76b [5.590933] acpi_ps_parse_loop+0x84b/0x924 [5.590934] acpi_ps_parse_aml+0x1af/0x550 [5.590935] acpi_ps_execute_method+0x208/0x2ca [5.590936] acpi_ns_evaluate+0x34e/0x4f0 [5.590937] acpi_evaluate_object+0x18e/0x3b4 [5.590940] __query_block+0x184/0x1f0
[Kernel-packages] [Bug 1934460] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1934460/+attachment/5508580/+files/ProcCpuinfo.txt -- 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/1934460 Title: ioremap: invalid physical address d5010fee0526b902 Status in linux-oem-5.10 package in Ubuntu: New Bug description: [4.554394] USB Video Class driver (1.1.1) [5.590819] ioremap: invalid physical address d5010fee0526b902 [5.590822] [ cut here ] [5.590826] WARNING: CPU: 0 PID: 355 at arch/x86/mm/ioremap.c:198 __ioremap_caller.cold+0xf/0x64 [5.590827] Modules linked in: uvcvideo btusb videobuf2_vmalloc btrtl videobuf2_memops btbcm videobuf2_v4l2 btintel videobuf2_common bluetooth videodev ecdh_generic mc ecc nls_iso8859_1 snd_hda_codec_ hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci snd_sof_intel_byt snd_sof_intel_ipc snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_xtensa_dsp snd_sof_intel_hda snd_sof snd_hda_ext_core sn d_soc_acpi_intel_match 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 mei_hdcp snd_soc_core intel_rapl_msr x86_pkg_temp_thermal intel_powerclamp snd_compress ac97_bus snd_pcm_dmaengine iwlmvm coretemp snd_pcm mac80211 dell_laptop snd_seq_midi snd_seq_midi_event kvm_intel snd_rawmidi joydev dell _smm_hwmon libarc4 snd_seq kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel snd_seq_device crypto_simd cryptd dell_wmi i915 snd_timer glue_helper dell_smbios dcdbas rapl intel_cstate iwlwifi [5.590861] drm_kms_helper dell_privacy_wmi cfg80211 cec input_leds rc_core i2c_algo_bit fb_sys_fops syscopyarea dell_wmi_sysman(+) sysfillrect ledtrig_audio snd serio_raw dell_wmi_descriptor efi_pst ore hid_multitouch wmi_bmof processor_thermal_device sysimgblt intel_rapl_common soundcore mei_me intel_soc_dts_iosf mei ucsi_acpi intel_pch_thermal typec_ucsi typec int3403_thermal int3402_thermal int34 00_thermal int340x_thermal_zone mac_hid intel_hid acpi_pad sparse_keymap acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul psmouse i2c_i801 nvme intel_lpss_pci nvme_core ahci i2c_smbus intel_lpss idma64 xhci_pci libahci virt_dma xhci_pci_renesas i2c_hid wmi hid video pinctrl_cannonlake [5.590891] CPU: 0 PID: 355 Comm: systemd-udevd Not tainted 5.10.0-1032-oem #33-Ubuntu [5.590892] Hardware name: Dell Inc. Inspiron 7380/, BIOS 1.1.0 08/08/2018 [5.590894] RIP: 0010:__ioremap_caller.cold+0xf/0x64 [5.590895] Code: 00 00 00 4c 89 e6 bf 04 00 00 00 0f 45 c2 0f bf d0 e8 aa a1 53 ff e9 ca bb 50 ff 48 89 fe 48 c7 c7 d8 eb 19 8b e8 4a 76 00 00 <0f> 0b 45 31 ed e9 03 c4 50 ff 48 8b 75 b8 44 8b 45 c4 44 89 e9 48 [5.590896] RSP: 0018:aab9406cf5f0 EFLAGS: 00010246 [5.590897] RAX: 0032 RBX: 000d5010fee0526b RCX: [5.590898] RDX: RSI: 8c46a7618a40 RDI: 8c46a7618a40 [5.590898] RBP: aab9406cf658 R08: 8c46a7618a40 R09: aab9406cf3c8 [5.590899] R10: 0001 R11: 0001 R12: d5010fee0526b902 [5.590899] R13: d5010fee0526b902 R14: 0008 R15: d5010fee0526b000 [5.590900] FS: 7f1bfda4f880() GS:8c46a760() knlGS: [5.590901] CS: 0010 DS: ES: CR0: 80050033 [5.590902] CR2: 7fc270b47cf0 CR3: 0001066ee004 CR4: 003706f0 [5.590902] Call Trace: [5.590906] ? acpi_os_map_iomem+0x1bc/0x1d0 [5.590907] ? _cond_resched+0x19/0x30 [5.590910] ioremap_cache+0x17/0x20 [5.590911] acpi_os_map_iomem+0x1bc/0x1d0 [5.590912] acpi_os_map_memory+0xe/0x10 [5.590915] acpi_ex_system_memory_space_handler+0x1fc/0x3aa [5.590916] acpi_ev_address_space_dispatch+0x34d/0x40e [5.590917] ? acpi_ex_prep_field_value+0x50a/0x50a [5.590919] acpi_ex_access_region+0x454/0x4ed [5.590920] acpi_ex_field_datum_io+0x18a/0x42d [5.590921] acpi_ex_extract_from_field+0xe7/0x320 [5.590922] ? acpi_ut_trace+0x28/0x6a [5.590924] acpi_ex_read_data_from_field+0x31f/0x371 [5.590925] acpi_ex_resolve_node_to_value+0x3a7/0x4dd [5.590926] acpi_ex_resolve_to_value+0x3c3/0x472 [5.590928] acpi_ds_evaluate_name_path+0xb1/0x169 [5.590930] ? acpi_db_single_step+0x1f/0x252 [5.590931] acpi_ds_exec_end_op+0x118/0x76b [5.590933] acpi_ps_parse_loop+0x84b/0x924 [5.590934] acpi_ps_parse_aml+0x1af/0x550 [5.590935] acpi_ps_execute_method+0x208/0x2ca [5.590936] acpi_ns_evaluate+0x34e/0x4f0 [5.590937] acpi_evaluate_object+0x18e/0x3b4 [5.590940] __query_block+0x184/0x1f0 [wmi] [
[Kernel-packages] [Bug 1934460] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1934460/+attachment/5508578/+files/Lsusb-t.txt -- 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/1934460 Title: ioremap: invalid physical address d5010fee0526b902 Status in linux-oem-5.10 package in Ubuntu: New Bug description: [4.554394] USB Video Class driver (1.1.1) [5.590819] ioremap: invalid physical address d5010fee0526b902 [5.590822] [ cut here ] [5.590826] WARNING: CPU: 0 PID: 355 at arch/x86/mm/ioremap.c:198 __ioremap_caller.cold+0xf/0x64 [5.590827] Modules linked in: uvcvideo btusb videobuf2_vmalloc btrtl videobuf2_memops btbcm videobuf2_v4l2 btintel videobuf2_common bluetooth videodev ecdh_generic mc ecc nls_iso8859_1 snd_hda_codec_ hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci snd_sof_intel_byt snd_sof_intel_ipc snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_xtensa_dsp snd_sof_intel_hda snd_sof snd_hda_ext_core sn d_soc_acpi_intel_match 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 mei_hdcp snd_soc_core intel_rapl_msr x86_pkg_temp_thermal intel_powerclamp snd_compress ac97_bus snd_pcm_dmaengine iwlmvm coretemp snd_pcm mac80211 dell_laptop snd_seq_midi snd_seq_midi_event kvm_intel snd_rawmidi joydev dell _smm_hwmon libarc4 snd_seq kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel snd_seq_device crypto_simd cryptd dell_wmi i915 snd_timer glue_helper dell_smbios dcdbas rapl intel_cstate iwlwifi [5.590861] drm_kms_helper dell_privacy_wmi cfg80211 cec input_leds rc_core i2c_algo_bit fb_sys_fops syscopyarea dell_wmi_sysman(+) sysfillrect ledtrig_audio snd serio_raw dell_wmi_descriptor efi_pst ore hid_multitouch wmi_bmof processor_thermal_device sysimgblt intel_rapl_common soundcore mei_me intel_soc_dts_iosf mei ucsi_acpi intel_pch_thermal typec_ucsi typec int3403_thermal int3402_thermal int34 00_thermal int340x_thermal_zone mac_hid intel_hid acpi_pad sparse_keymap acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul psmouse i2c_i801 nvme intel_lpss_pci nvme_core ahci i2c_smbus intel_lpss idma64 xhci_pci libahci virt_dma xhci_pci_renesas i2c_hid wmi hid video pinctrl_cannonlake [5.590891] CPU: 0 PID: 355 Comm: systemd-udevd Not tainted 5.10.0-1032-oem #33-Ubuntu [5.590892] Hardware name: Dell Inc. Inspiron 7380/, BIOS 1.1.0 08/08/2018 [5.590894] RIP: 0010:__ioremap_caller.cold+0xf/0x64 [5.590895] Code: 00 00 00 4c 89 e6 bf 04 00 00 00 0f 45 c2 0f bf d0 e8 aa a1 53 ff e9 ca bb 50 ff 48 89 fe 48 c7 c7 d8 eb 19 8b e8 4a 76 00 00 <0f> 0b 45 31 ed e9 03 c4 50 ff 48 8b 75 b8 44 8b 45 c4 44 89 e9 48 [5.590896] RSP: 0018:aab9406cf5f0 EFLAGS: 00010246 [5.590897] RAX: 0032 RBX: 000d5010fee0526b RCX: [5.590898] RDX: RSI: 8c46a7618a40 RDI: 8c46a7618a40 [5.590898] RBP: aab9406cf658 R08: 8c46a7618a40 R09: aab9406cf3c8 [5.590899] R10: 0001 R11: 0001 R12: d5010fee0526b902 [5.590899] R13: d5010fee0526b902 R14: 0008 R15: d5010fee0526b000 [5.590900] FS: 7f1bfda4f880() GS:8c46a760() knlGS: [5.590901] CS: 0010 DS: ES: CR0: 80050033 [5.590902] CR2: 7fc270b47cf0 CR3: 0001066ee004 CR4: 003706f0 [5.590902] Call Trace: [5.590906] ? acpi_os_map_iomem+0x1bc/0x1d0 [5.590907] ? _cond_resched+0x19/0x30 [5.590910] ioremap_cache+0x17/0x20 [5.590911] acpi_os_map_iomem+0x1bc/0x1d0 [5.590912] acpi_os_map_memory+0xe/0x10 [5.590915] acpi_ex_system_memory_space_handler+0x1fc/0x3aa [5.590916] acpi_ev_address_space_dispatch+0x34d/0x40e [5.590917] ? acpi_ex_prep_field_value+0x50a/0x50a [5.590919] acpi_ex_access_region+0x454/0x4ed [5.590920] acpi_ex_field_datum_io+0x18a/0x42d [5.590921] acpi_ex_extract_from_field+0xe7/0x320 [5.590922] ? acpi_ut_trace+0x28/0x6a [5.590924] acpi_ex_read_data_from_field+0x31f/0x371 [5.590925] acpi_ex_resolve_node_to_value+0x3a7/0x4dd [5.590926] acpi_ex_resolve_to_value+0x3c3/0x472 [5.590928] acpi_ds_evaluate_name_path+0xb1/0x169 [5.590930] ? acpi_db_single_step+0x1f/0x252 [5.590931] acpi_ds_exec_end_op+0x118/0x76b [5.590933] acpi_ps_parse_loop+0x84b/0x924 [5.590934] acpi_ps_parse_aml+0x1af/0x550 [5.590935] acpi_ps_execute_method+0x208/0x2ca [5.590936] acpi_ns_evaluate+0x34e/0x4f0 [5.590937] acpi_evaluate_object+0x18e/0x3b4 [5.590940] __query_block+0x184/0x1f0 [wmi] [5.590942] ?
[Kernel-packages] [Bug 1934460] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1934460/+attachment/5508576/+files/Lspci.txt -- 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/1934460 Title: ioremap: invalid physical address d5010fee0526b902 Status in linux-oem-5.10 package in Ubuntu: New Bug description: [4.554394] USB Video Class driver (1.1.1) [5.590819] ioremap: invalid physical address d5010fee0526b902 [5.590822] [ cut here ] [5.590826] WARNING: CPU: 0 PID: 355 at arch/x86/mm/ioremap.c:198 __ioremap_caller.cold+0xf/0x64 [5.590827] Modules linked in: uvcvideo btusb videobuf2_vmalloc btrtl videobuf2_memops btbcm videobuf2_v4l2 btintel videobuf2_common bluetooth videodev ecdh_generic mc ecc nls_iso8859_1 snd_hda_codec_ hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci snd_sof_intel_byt snd_sof_intel_ipc snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_xtensa_dsp snd_sof_intel_hda snd_sof snd_hda_ext_core sn d_soc_acpi_intel_match 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 mei_hdcp snd_soc_core intel_rapl_msr x86_pkg_temp_thermal intel_powerclamp snd_compress ac97_bus snd_pcm_dmaengine iwlmvm coretemp snd_pcm mac80211 dell_laptop snd_seq_midi snd_seq_midi_event kvm_intel snd_rawmidi joydev dell _smm_hwmon libarc4 snd_seq kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel snd_seq_device crypto_simd cryptd dell_wmi i915 snd_timer glue_helper dell_smbios dcdbas rapl intel_cstate iwlwifi [5.590861] drm_kms_helper dell_privacy_wmi cfg80211 cec input_leds rc_core i2c_algo_bit fb_sys_fops syscopyarea dell_wmi_sysman(+) sysfillrect ledtrig_audio snd serio_raw dell_wmi_descriptor efi_pst ore hid_multitouch wmi_bmof processor_thermal_device sysimgblt intel_rapl_common soundcore mei_me intel_soc_dts_iosf mei ucsi_acpi intel_pch_thermal typec_ucsi typec int3403_thermal int3402_thermal int34 00_thermal int340x_thermal_zone mac_hid intel_hid acpi_pad sparse_keymap acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul psmouse i2c_i801 nvme intel_lpss_pci nvme_core ahci i2c_smbus intel_lpss idma64 xhci_pci libahci virt_dma xhci_pci_renesas i2c_hid wmi hid video pinctrl_cannonlake [5.590891] CPU: 0 PID: 355 Comm: systemd-udevd Not tainted 5.10.0-1032-oem #33-Ubuntu [5.590892] Hardware name: Dell Inc. Inspiron 7380/, BIOS 1.1.0 08/08/2018 [5.590894] RIP: 0010:__ioremap_caller.cold+0xf/0x64 [5.590895] Code: 00 00 00 4c 89 e6 bf 04 00 00 00 0f 45 c2 0f bf d0 e8 aa a1 53 ff e9 ca bb 50 ff 48 89 fe 48 c7 c7 d8 eb 19 8b e8 4a 76 00 00 <0f> 0b 45 31 ed e9 03 c4 50 ff 48 8b 75 b8 44 8b 45 c4 44 89 e9 48 [5.590896] RSP: 0018:aab9406cf5f0 EFLAGS: 00010246 [5.590897] RAX: 0032 RBX: 000d5010fee0526b RCX: [5.590898] RDX: RSI: 8c46a7618a40 RDI: 8c46a7618a40 [5.590898] RBP: aab9406cf658 R08: 8c46a7618a40 R09: aab9406cf3c8 [5.590899] R10: 0001 R11: 0001 R12: d5010fee0526b902 [5.590899] R13: d5010fee0526b902 R14: 0008 R15: d5010fee0526b000 [5.590900] FS: 7f1bfda4f880() GS:8c46a760() knlGS: [5.590901] CS: 0010 DS: ES: CR0: 80050033 [5.590902] CR2: 7fc270b47cf0 CR3: 0001066ee004 CR4: 003706f0 [5.590902] Call Trace: [5.590906] ? acpi_os_map_iomem+0x1bc/0x1d0 [5.590907] ? _cond_resched+0x19/0x30 [5.590910] ioremap_cache+0x17/0x20 [5.590911] acpi_os_map_iomem+0x1bc/0x1d0 [5.590912] acpi_os_map_memory+0xe/0x10 [5.590915] acpi_ex_system_memory_space_handler+0x1fc/0x3aa [5.590916] acpi_ev_address_space_dispatch+0x34d/0x40e [5.590917] ? acpi_ex_prep_field_value+0x50a/0x50a [5.590919] acpi_ex_access_region+0x454/0x4ed [5.590920] acpi_ex_field_datum_io+0x18a/0x42d [5.590921] acpi_ex_extract_from_field+0xe7/0x320 [5.590922] ? acpi_ut_trace+0x28/0x6a [5.590924] acpi_ex_read_data_from_field+0x31f/0x371 [5.590925] acpi_ex_resolve_node_to_value+0x3a7/0x4dd [5.590926] acpi_ex_resolve_to_value+0x3c3/0x472 [5.590928] acpi_ds_evaluate_name_path+0xb1/0x169 [5.590930] ? acpi_db_single_step+0x1f/0x252 [5.590931] acpi_ds_exec_end_op+0x118/0x76b [5.590933] acpi_ps_parse_loop+0x84b/0x924 [5.590934] acpi_ps_parse_aml+0x1af/0x550 [5.590935] acpi_ps_execute_method+0x208/0x2ca [5.590936] acpi_ns_evaluate+0x34e/0x4f0 [5.590937] acpi_evaluate_object+0x18e/0x3b4 [5.590940] __query_block+0x184/0x1f0 [wmi] [5.590942] ?
[Kernel-packages] [Bug 1934460] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1934460/+attachment/5508583/+files/ProcModules.txt -- 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/1934460 Title: ioremap: invalid physical address d5010fee0526b902 Status in linux-oem-5.10 package in Ubuntu: New Bug description: [4.554394] USB Video Class driver (1.1.1) [5.590819] ioremap: invalid physical address d5010fee0526b902 [5.590822] [ cut here ] [5.590826] WARNING: CPU: 0 PID: 355 at arch/x86/mm/ioremap.c:198 __ioremap_caller.cold+0xf/0x64 [5.590827] Modules linked in: uvcvideo btusb videobuf2_vmalloc btrtl videobuf2_memops btbcm videobuf2_v4l2 btintel videobuf2_common bluetooth videodev ecdh_generic mc ecc nls_iso8859_1 snd_hda_codec_ hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci snd_sof_intel_byt snd_sof_intel_ipc snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_xtensa_dsp snd_sof_intel_hda snd_sof snd_hda_ext_core sn d_soc_acpi_intel_match 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 mei_hdcp snd_soc_core intel_rapl_msr x86_pkg_temp_thermal intel_powerclamp snd_compress ac97_bus snd_pcm_dmaengine iwlmvm coretemp snd_pcm mac80211 dell_laptop snd_seq_midi snd_seq_midi_event kvm_intel snd_rawmidi joydev dell _smm_hwmon libarc4 snd_seq kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel snd_seq_device crypto_simd cryptd dell_wmi i915 snd_timer glue_helper dell_smbios dcdbas rapl intel_cstate iwlwifi [5.590861] drm_kms_helper dell_privacy_wmi cfg80211 cec input_leds rc_core i2c_algo_bit fb_sys_fops syscopyarea dell_wmi_sysman(+) sysfillrect ledtrig_audio snd serio_raw dell_wmi_descriptor efi_pst ore hid_multitouch wmi_bmof processor_thermal_device sysimgblt intel_rapl_common soundcore mei_me intel_soc_dts_iosf mei ucsi_acpi intel_pch_thermal typec_ucsi typec int3403_thermal int3402_thermal int34 00_thermal int340x_thermal_zone mac_hid intel_hid acpi_pad sparse_keymap acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul psmouse i2c_i801 nvme intel_lpss_pci nvme_core ahci i2c_smbus intel_lpss idma64 xhci_pci libahci virt_dma xhci_pci_renesas i2c_hid wmi hid video pinctrl_cannonlake [5.590891] CPU: 0 PID: 355 Comm: systemd-udevd Not tainted 5.10.0-1032-oem #33-Ubuntu [5.590892] Hardware name: Dell Inc. Inspiron 7380/, BIOS 1.1.0 08/08/2018 [5.590894] RIP: 0010:__ioremap_caller.cold+0xf/0x64 [5.590895] Code: 00 00 00 4c 89 e6 bf 04 00 00 00 0f 45 c2 0f bf d0 e8 aa a1 53 ff e9 ca bb 50 ff 48 89 fe 48 c7 c7 d8 eb 19 8b e8 4a 76 00 00 <0f> 0b 45 31 ed e9 03 c4 50 ff 48 8b 75 b8 44 8b 45 c4 44 89 e9 48 [5.590896] RSP: 0018:aab9406cf5f0 EFLAGS: 00010246 [5.590897] RAX: 0032 RBX: 000d5010fee0526b RCX: [5.590898] RDX: RSI: 8c46a7618a40 RDI: 8c46a7618a40 [5.590898] RBP: aab9406cf658 R08: 8c46a7618a40 R09: aab9406cf3c8 [5.590899] R10: 0001 R11: 0001 R12: d5010fee0526b902 [5.590899] R13: d5010fee0526b902 R14: 0008 R15: d5010fee0526b000 [5.590900] FS: 7f1bfda4f880() GS:8c46a760() knlGS: [5.590901] CS: 0010 DS: ES: CR0: 80050033 [5.590902] CR2: 7fc270b47cf0 CR3: 0001066ee004 CR4: 003706f0 [5.590902] Call Trace: [5.590906] ? acpi_os_map_iomem+0x1bc/0x1d0 [5.590907] ? _cond_resched+0x19/0x30 [5.590910] ioremap_cache+0x17/0x20 [5.590911] acpi_os_map_iomem+0x1bc/0x1d0 [5.590912] acpi_os_map_memory+0xe/0x10 [5.590915] acpi_ex_system_memory_space_handler+0x1fc/0x3aa [5.590916] acpi_ev_address_space_dispatch+0x34d/0x40e [5.590917] ? acpi_ex_prep_field_value+0x50a/0x50a [5.590919] acpi_ex_access_region+0x454/0x4ed [5.590920] acpi_ex_field_datum_io+0x18a/0x42d [5.590921] acpi_ex_extract_from_field+0xe7/0x320 [5.590922] ? acpi_ut_trace+0x28/0x6a [5.590924] acpi_ex_read_data_from_field+0x31f/0x371 [5.590925] acpi_ex_resolve_node_to_value+0x3a7/0x4dd [5.590926] acpi_ex_resolve_to_value+0x3c3/0x472 [5.590928] acpi_ds_evaluate_name_path+0xb1/0x169 [5.590930] ? acpi_db_single_step+0x1f/0x252 [5.590931] acpi_ds_exec_end_op+0x118/0x76b [5.590933] acpi_ps_parse_loop+0x84b/0x924 [5.590934] acpi_ps_parse_aml+0x1af/0x550 [5.590935] acpi_ps_execute_method+0x208/0x2ca [5.590936] acpi_ns_evaluate+0x34e/0x4f0 [5.590937] acpi_evaluate_object+0x18e/0x3b4 [5.590940] __query_block+0x184/0x1f0 [wmi] [
[Kernel-packages] [Bug 1934460] [NEW] ioremap: invalid physical address d5010fee0526b902
Public bug reported: [4.554394] USB Video Class driver (1.1.1) [5.590819] ioremap: invalid physical address d5010fee0526b902 [5.590822] [ cut here ] [5.590826] WARNING: CPU: 0 PID: 355 at arch/x86/mm/ioremap.c:198 __ioremap_caller.cold+0xf/0x64 [5.590827] Modules linked in: uvcvideo btusb videobuf2_vmalloc btrtl videobuf2_memops btbcm videobuf2_v4l2 btintel videobuf2_common bluetooth videodev ecdh_generic mc ecc nls_iso8859_1 snd_hda_codec_ hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci snd_sof_intel_byt snd_sof_intel_ipc snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_xtensa_dsp snd_sof_intel_hda snd_sof snd_hda_ext_core sn d_soc_acpi_intel_match 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 mei_hdcp snd_soc_core intel_rapl_msr x86_pkg_temp_thermal intel_powerclamp snd_compress ac97_bus snd_pcm_dmaengine iwlmvm coretemp snd_pcm mac80211 dell_laptop snd_seq_midi snd_seq_midi_event kvm_intel snd_rawmidi joydev dell _smm_hwmon libarc4 snd_seq kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel snd_seq_device crypto_simd cryptd dell_wmi i915 snd_timer glue_helper dell_smbios dcdbas rapl intel_cstate iwlwifi [5.590861] drm_kms_helper dell_privacy_wmi cfg80211 cec input_leds rc_core i2c_algo_bit fb_sys_fops syscopyarea dell_wmi_sysman(+) sysfillrect ledtrig_audio snd serio_raw dell_wmi_descriptor efi_pst ore hid_multitouch wmi_bmof processor_thermal_device sysimgblt intel_rapl_common soundcore mei_me intel_soc_dts_iosf mei ucsi_acpi intel_pch_thermal typec_ucsi typec int3403_thermal int3402_thermal int34 00_thermal int340x_thermal_zone mac_hid intel_hid acpi_pad sparse_keymap acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul psmouse i2c_i801 nvme intel_lpss_pci nvme_core ahci i2c_smbus intel_lpss idma64 xhci_pci libahci virt_dma xhci_pci_renesas i2c_hid wmi hid video pinctrl_cannonlake [5.590891] CPU: 0 PID: 355 Comm: systemd-udevd Not tainted 5.10.0-1032-oem #33-Ubuntu [5.590892] Hardware name: Dell Inc. Inspiron 7380/, BIOS 1.1.0 08/08/2018 [5.590894] RIP: 0010:__ioremap_caller.cold+0xf/0x64 [5.590895] Code: 00 00 00 4c 89 e6 bf 04 00 00 00 0f 45 c2 0f bf d0 e8 aa a1 53 ff e9 ca bb 50 ff 48 89 fe 48 c7 c7 d8 eb 19 8b e8 4a 76 00 00 <0f> 0b 45 31 ed e9 03 c4 50 ff 48 8b 75 b8 44 8b 45 c4 44 89 e9 48 [5.590896] RSP: 0018:aab9406cf5f0 EFLAGS: 00010246 [5.590897] RAX: 0032 RBX: 000d5010fee0526b RCX: [5.590898] RDX: RSI: 8c46a7618a40 RDI: 8c46a7618a40 [5.590898] RBP: aab9406cf658 R08: 8c46a7618a40 R09: aab9406cf3c8 [5.590899] R10: 0001 R11: 0001 R12: d5010fee0526b902 [5.590899] R13: d5010fee0526b902 R14: 0008 R15: d5010fee0526b000 [5.590900] FS: 7f1bfda4f880() GS:8c46a760() knlGS: [5.590901] CS: 0010 DS: ES: CR0: 80050033 [5.590902] CR2: 7fc270b47cf0 CR3: 0001066ee004 CR4: 003706f0 [5.590902] Call Trace: [5.590906] ? acpi_os_map_iomem+0x1bc/0x1d0 [5.590907] ? _cond_resched+0x19/0x30 [5.590910] ioremap_cache+0x17/0x20 [5.590911] acpi_os_map_iomem+0x1bc/0x1d0 [5.590912] acpi_os_map_memory+0xe/0x10 [5.590915] acpi_ex_system_memory_space_handler+0x1fc/0x3aa [5.590916] acpi_ev_address_space_dispatch+0x34d/0x40e [5.590917] ? acpi_ex_prep_field_value+0x50a/0x50a [5.590919] acpi_ex_access_region+0x454/0x4ed [5.590920] acpi_ex_field_datum_io+0x18a/0x42d [5.590921] acpi_ex_extract_from_field+0xe7/0x320 [5.590922] ? acpi_ut_trace+0x28/0x6a [5.590924] acpi_ex_read_data_from_field+0x31f/0x371 [5.590925] acpi_ex_resolve_node_to_value+0x3a7/0x4dd [5.590926] acpi_ex_resolve_to_value+0x3c3/0x472 [5.590928] acpi_ds_evaluate_name_path+0xb1/0x169 [5.590930] ? acpi_db_single_step+0x1f/0x252 [5.590931] acpi_ds_exec_end_op+0x118/0x76b [5.590933] acpi_ps_parse_loop+0x84b/0x924 [5.590934] acpi_ps_parse_aml+0x1af/0x550 [5.590935] acpi_ps_execute_method+0x208/0x2ca [5.590936] acpi_ns_evaluate+0x34e/0x4f0 [5.590937] acpi_evaluate_object+0x18e/0x3b4 [5.590940] __query_block+0x184/0x1f0 [wmi] [5.590942] ? guid_parse+0x1f/0x30 [5.590944] wmi_query_block+0x66/0x80 [wmi] [5.590947] get_instance_count+0x4c/0x90 [dell_wmi_sysman] [5.590949] alloc_str_data+0x15/0x70 [dell_wmi_sysman] [5.590951] init_bios_attributes+0x53/0x2ef [dell_wmi_sysman] [5.590954] sysman_init+0x212/0x1000 [dell_wmi_sysman] [5.590955] ? 0xc0755000 [5.590956] do_one_initcall+0x48/0x1d0 [5.590957] ? _cond_resched+0x19/0x30 [5.590959] ? kmem_cache_alloc_trace+0x37a/0x430 [5.590961] ?
[Kernel-packages] [Bug 1934460] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1934460/+attachment/5508572/+files/AlsaInfo.txt -- 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/1934460 Title: ioremap: invalid physical address d5010fee0526b902 Status in linux-oem-5.10 package in Ubuntu: New Bug description: [4.554394] USB Video Class driver (1.1.1) [5.590819] ioremap: invalid physical address d5010fee0526b902 [5.590822] [ cut here ] [5.590826] WARNING: CPU: 0 PID: 355 at arch/x86/mm/ioremap.c:198 __ioremap_caller.cold+0xf/0x64 [5.590827] Modules linked in: uvcvideo btusb videobuf2_vmalloc btrtl videobuf2_memops btbcm videobuf2_v4l2 btintel videobuf2_common bluetooth videodev ecdh_generic mc ecc nls_iso8859_1 snd_hda_codec_ hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci snd_sof_intel_byt snd_sof_intel_ipc snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_xtensa_dsp snd_sof_intel_hda snd_sof snd_hda_ext_core sn d_soc_acpi_intel_match 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 mei_hdcp snd_soc_core intel_rapl_msr x86_pkg_temp_thermal intel_powerclamp snd_compress ac97_bus snd_pcm_dmaengine iwlmvm coretemp snd_pcm mac80211 dell_laptop snd_seq_midi snd_seq_midi_event kvm_intel snd_rawmidi joydev dell _smm_hwmon libarc4 snd_seq kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel snd_seq_device crypto_simd cryptd dell_wmi i915 snd_timer glue_helper dell_smbios dcdbas rapl intel_cstate iwlwifi [5.590861] drm_kms_helper dell_privacy_wmi cfg80211 cec input_leds rc_core i2c_algo_bit fb_sys_fops syscopyarea dell_wmi_sysman(+) sysfillrect ledtrig_audio snd serio_raw dell_wmi_descriptor efi_pst ore hid_multitouch wmi_bmof processor_thermal_device sysimgblt intel_rapl_common soundcore mei_me intel_soc_dts_iosf mei ucsi_acpi intel_pch_thermal typec_ucsi typec int3403_thermal int3402_thermal int34 00_thermal int340x_thermal_zone mac_hid intel_hid acpi_pad sparse_keymap acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul psmouse i2c_i801 nvme intel_lpss_pci nvme_core ahci i2c_smbus intel_lpss idma64 xhci_pci libahci virt_dma xhci_pci_renesas i2c_hid wmi hid video pinctrl_cannonlake [5.590891] CPU: 0 PID: 355 Comm: systemd-udevd Not tainted 5.10.0-1032-oem #33-Ubuntu [5.590892] Hardware name: Dell Inc. Inspiron 7380/, BIOS 1.1.0 08/08/2018 [5.590894] RIP: 0010:__ioremap_caller.cold+0xf/0x64 [5.590895] Code: 00 00 00 4c 89 e6 bf 04 00 00 00 0f 45 c2 0f bf d0 e8 aa a1 53 ff e9 ca bb 50 ff 48 89 fe 48 c7 c7 d8 eb 19 8b e8 4a 76 00 00 <0f> 0b 45 31 ed e9 03 c4 50 ff 48 8b 75 b8 44 8b 45 c4 44 89 e9 48 [5.590896] RSP: 0018:aab9406cf5f0 EFLAGS: 00010246 [5.590897] RAX: 0032 RBX: 000d5010fee0526b RCX: [5.590898] RDX: RSI: 8c46a7618a40 RDI: 8c46a7618a40 [5.590898] RBP: aab9406cf658 R08: 8c46a7618a40 R09: aab9406cf3c8 [5.590899] R10: 0001 R11: 0001 R12: d5010fee0526b902 [5.590899] R13: d5010fee0526b902 R14: 0008 R15: d5010fee0526b000 [5.590900] FS: 7f1bfda4f880() GS:8c46a760() knlGS: [5.590901] CS: 0010 DS: ES: CR0: 80050033 [5.590902] CR2: 7fc270b47cf0 CR3: 0001066ee004 CR4: 003706f0 [5.590902] Call Trace: [5.590906] ? acpi_os_map_iomem+0x1bc/0x1d0 [5.590907] ? _cond_resched+0x19/0x30 [5.590910] ioremap_cache+0x17/0x20 [5.590911] acpi_os_map_iomem+0x1bc/0x1d0 [5.590912] acpi_os_map_memory+0xe/0x10 [5.590915] acpi_ex_system_memory_space_handler+0x1fc/0x3aa [5.590916] acpi_ev_address_space_dispatch+0x34d/0x40e [5.590917] ? acpi_ex_prep_field_value+0x50a/0x50a [5.590919] acpi_ex_access_region+0x454/0x4ed [5.590920] acpi_ex_field_datum_io+0x18a/0x42d [5.590921] acpi_ex_extract_from_field+0xe7/0x320 [5.590922] ? acpi_ut_trace+0x28/0x6a [5.590924] acpi_ex_read_data_from_field+0x31f/0x371 [5.590925] acpi_ex_resolve_node_to_value+0x3a7/0x4dd [5.590926] acpi_ex_resolve_to_value+0x3c3/0x472 [5.590928] acpi_ds_evaluate_name_path+0xb1/0x169 [5.590930] ? acpi_db_single_step+0x1f/0x252 [5.590931] acpi_ds_exec_end_op+0x118/0x76b [5.590933] acpi_ps_parse_loop+0x84b/0x924 [5.590934] acpi_ps_parse_aml+0x1af/0x550 [5.590935] acpi_ps_execute_method+0x208/0x2ca [5.590936] acpi_ns_evaluate+0x34e/0x4f0 [5.590937] acpi_evaluate_object+0x18e/0x3b4 [5.590940] __query_block+0x184/0x1f0 [wmi] [5.590942]
[Kernel-packages] [Bug 1934460] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1934460/+attachment/5508582/+files/ProcInterrupts.txt -- 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/1934460 Title: ioremap: invalid physical address d5010fee0526b902 Status in linux-oem-5.10 package in Ubuntu: New Bug description: [4.554394] USB Video Class driver (1.1.1) [5.590819] ioremap: invalid physical address d5010fee0526b902 [5.590822] [ cut here ] [5.590826] WARNING: CPU: 0 PID: 355 at arch/x86/mm/ioremap.c:198 __ioremap_caller.cold+0xf/0x64 [5.590827] Modules linked in: uvcvideo btusb videobuf2_vmalloc btrtl videobuf2_memops btbcm videobuf2_v4l2 btintel videobuf2_common bluetooth videodev ecdh_generic mc ecc nls_iso8859_1 snd_hda_codec_ hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci snd_sof_intel_byt snd_sof_intel_ipc snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_xtensa_dsp snd_sof_intel_hda snd_sof snd_hda_ext_core sn d_soc_acpi_intel_match 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 mei_hdcp snd_soc_core intel_rapl_msr x86_pkg_temp_thermal intel_powerclamp snd_compress ac97_bus snd_pcm_dmaengine iwlmvm coretemp snd_pcm mac80211 dell_laptop snd_seq_midi snd_seq_midi_event kvm_intel snd_rawmidi joydev dell _smm_hwmon libarc4 snd_seq kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel snd_seq_device crypto_simd cryptd dell_wmi i915 snd_timer glue_helper dell_smbios dcdbas rapl intel_cstate iwlwifi [5.590861] drm_kms_helper dell_privacy_wmi cfg80211 cec input_leds rc_core i2c_algo_bit fb_sys_fops syscopyarea dell_wmi_sysman(+) sysfillrect ledtrig_audio snd serio_raw dell_wmi_descriptor efi_pst ore hid_multitouch wmi_bmof processor_thermal_device sysimgblt intel_rapl_common soundcore mei_me intel_soc_dts_iosf mei ucsi_acpi intel_pch_thermal typec_ucsi typec int3403_thermal int3402_thermal int34 00_thermal int340x_thermal_zone mac_hid intel_hid acpi_pad sparse_keymap acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul psmouse i2c_i801 nvme intel_lpss_pci nvme_core ahci i2c_smbus intel_lpss idma64 xhci_pci libahci virt_dma xhci_pci_renesas i2c_hid wmi hid video pinctrl_cannonlake [5.590891] CPU: 0 PID: 355 Comm: systemd-udevd Not tainted 5.10.0-1032-oem #33-Ubuntu [5.590892] Hardware name: Dell Inc. Inspiron 7380/, BIOS 1.1.0 08/08/2018 [5.590894] RIP: 0010:__ioremap_caller.cold+0xf/0x64 [5.590895] Code: 00 00 00 4c 89 e6 bf 04 00 00 00 0f 45 c2 0f bf d0 e8 aa a1 53 ff e9 ca bb 50 ff 48 89 fe 48 c7 c7 d8 eb 19 8b e8 4a 76 00 00 <0f> 0b 45 31 ed e9 03 c4 50 ff 48 8b 75 b8 44 8b 45 c4 44 89 e9 48 [5.590896] RSP: 0018:aab9406cf5f0 EFLAGS: 00010246 [5.590897] RAX: 0032 RBX: 000d5010fee0526b RCX: [5.590898] RDX: RSI: 8c46a7618a40 RDI: 8c46a7618a40 [5.590898] RBP: aab9406cf658 R08: 8c46a7618a40 R09: aab9406cf3c8 [5.590899] R10: 0001 R11: 0001 R12: d5010fee0526b902 [5.590899] R13: d5010fee0526b902 R14: 0008 R15: d5010fee0526b000 [5.590900] FS: 7f1bfda4f880() GS:8c46a760() knlGS: [5.590901] CS: 0010 DS: ES: CR0: 80050033 [5.590902] CR2: 7fc270b47cf0 CR3: 0001066ee004 CR4: 003706f0 [5.590902] Call Trace: [5.590906] ? acpi_os_map_iomem+0x1bc/0x1d0 [5.590907] ? _cond_resched+0x19/0x30 [5.590910] ioremap_cache+0x17/0x20 [5.590911] acpi_os_map_iomem+0x1bc/0x1d0 [5.590912] acpi_os_map_memory+0xe/0x10 [5.590915] acpi_ex_system_memory_space_handler+0x1fc/0x3aa [5.590916] acpi_ev_address_space_dispatch+0x34d/0x40e [5.590917] ? acpi_ex_prep_field_value+0x50a/0x50a [5.590919] acpi_ex_access_region+0x454/0x4ed [5.590920] acpi_ex_field_datum_io+0x18a/0x42d [5.590921] acpi_ex_extract_from_field+0xe7/0x320 [5.590922] ? acpi_ut_trace+0x28/0x6a [5.590924] acpi_ex_read_data_from_field+0x31f/0x371 [5.590925] acpi_ex_resolve_node_to_value+0x3a7/0x4dd [5.590926] acpi_ex_resolve_to_value+0x3c3/0x472 [5.590928] acpi_ds_evaluate_name_path+0xb1/0x169 [5.590930] ? acpi_db_single_step+0x1f/0x252 [5.590931] acpi_ds_exec_end_op+0x118/0x76b [5.590933] acpi_ps_parse_loop+0x84b/0x924 [5.590934] acpi_ps_parse_aml+0x1af/0x550 [5.590935] acpi_ps_execute_method+0x208/0x2ca [5.590936] acpi_ns_evaluate+0x34e/0x4f0 [5.590937] acpi_evaluate_object+0x18e/0x3b4 [5.590940] __query_block+0x184/0x1f0 [wmi] [
[Kernel-packages] [Bug 1934461] [NEW] Nvidia driver 460 fails in install on 21.04
Public bug reported: I cannot use nvidia. If I choose nvidia, then I have a black screen and I cannot log in. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nvidia-driver-460 (not installed) ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 2 10:27:44 2021 InstallationDate: Installed on 2021-06-25 (6 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: nvidia-graphics-drivers-460 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- 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/1934461 Title: Nvidia driver 460 fails in install on 21.04 Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: I cannot use nvidia. If I choose nvidia, then I have a black screen and I cannot log in. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nvidia-driver-460 (not installed) ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 2 10:27:44 2021 InstallationDate: Installed on 2021-06-25 (6 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: nvidia-graphics-drivers-460 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1934461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
The above does not work for me. Any update? Is it worth compile my own kernel? Or, time to switch to another distro? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS Status in linux package in Ubuntu: Confirmed Bug description: Hi all, The Mainline wiki states that the mainline kernels are built with the previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are being built with Hirsuite 21.04, and before that Groovy? If this is intentional, then the wiki should be updated to reflect the change in policy. From https://wiki.ubuntu.com/Kernel/MainlineBuilds Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On my Focal LTS system I have GCC 9.3.0. The Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The *linux-headers-generic* packages have unmet dependencies on 20.04 LTS. I could install Groovy built kernels fine, but the Hirsuite ones built with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels can't be installed on Focal (libc 2.31). Thanks, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933950] Re: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25
Please open two new bugs by running these commands from your new 21.04 installation: ubuntu-bug nvidia-driver-460 and title it "Nvidia driver 460 fails in install on 21.04", and ubuntu-bug linux and title it "Brightness control is missing on HP Pavilion Gaming Laptop 15-dk0xxx" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933950 Title: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25 Status in linux package in Ubuntu: Won't Fix Status in xorg-server package in Ubuntu: Won't Fix Bug description: There was also no brightness setting. I have reinstalled ubuntu 3 times already. This happened after the updates on June 24th. The only solution is not to install ubuntu updates. As soon as I install updates, there is a black screen. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.10) ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 29 11:22:08 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.8.0-25-generic, x86_64: installed nvidia, 460.80, 5.8.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:85fb] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU116M [GeForce GTX 1660 Ti Mobile] [103c:85fb] InstallationDate: Installed on 2021-06-25 (3 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=a7c41e63-e7ea-43e0-9de0-55322f489ee5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2020 dmi.bios.release: 15.33 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85FB dmi.board.vendor: HP dmi.board.version: 42.42 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 42.42 dmi.modalias: dmi:bvnInsyde:bvrF.33:bd07/16/2020:br15.33:efr42.42:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FB:rvr42.42:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx dmi.product.sku: 2C7M8EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-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/1933950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933950] Re: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25
What should I 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/1933950 Title: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25 Status in linux package in Ubuntu: Won't Fix Status in xorg-server package in Ubuntu: Won't Fix Bug description: There was also no brightness setting. I have reinstalled ubuntu 3 times already. This happened after the updates on June 24th. The only solution is not to install ubuntu updates. As soon as I install updates, there is a black screen. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.10) ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 29 11:22:08 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.8.0-25-generic, x86_64: installed nvidia, 460.80, 5.8.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:85fb] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU116M [GeForce GTX 1660 Ti Mobile] [103c:85fb] InstallationDate: Installed on 2021-06-25 (3 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=a7c41e63-e7ea-43e0-9de0-55322f489ee5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2020 dmi.bios.release: 15.33 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85FB dmi.board.vendor: HP dmi.board.version: 42.42 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 42.42 dmi.modalias: dmi:bvnInsyde:bvrF.33:bd07/16/2020:br15.33:efr42.42:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FB:rvr42.42:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx dmi.product.sku: 2C7M8EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-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/1933950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
